Shawn Kelley
2006-Jul-05 08:35 UTC
[asterisk-users] Troubleshooting Random PRI disconnects
Hi all, We are having an issue with Random Disconnects wit our PRI connection. We are going into a T100P card from a Cisco IAD. Below is a copy of our PRI Debug. We will be talking on the phone and all the sudden the line will go dead. It acts as if the remote party hungup. However, the remote party is not hanging up. Can anyone give me some hints on where to look for the cause of this? -- Zap/25-1 is ringing> Protocol Discriminator: Q.931 (8) len=9> Call Ref: len= 2 (reference 44/0x2C) (Terminator)> Message type: ALERTING (1)> [1e 02 81 88]> Progress Indicator (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0:0 Location: Private network serving the local user (1)> Ext: 1 Progress Description: Inbandinformation or appropriate pattern now available. (8) ] -- Zap/25-1 is ringing -- Zap/25-1 is ringing -- Zap/25-1 answered Zap/1-1> Protocol Discriminator: Q.931 (8) len=14> Call Ref: len= 2 (reference 44/0x2C) (Terminator)> Message type: CONNECT (7)> [18 03 a9 83 81]> Channel ID (len= 5) [ Ext: 1 IntID: Implicit, PRI Spare: 0, ExclusiveDchan: 0> ChanSel: Reserved> Ext: 1 Coding: 0 Number Specified Channel Type:3> Ext: 1 Channel: 1 ]> [1e 02 81 82]> Progress Indicator (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0:0 Location: Private network serving the local user (1)> Ext: 1 Progress Description: Calledequipment is non-ISDN. (2) ] < Protocol Discriminator: Q.931 (8) len=5 < Call Ref: len= 2 (reference 44/0x2C) (Originator) < Message type: CONNECT ACKNOWLEDGE (15) < Protocol Discriminator: Q.931 (8) len=9 < Call Ref: len= 2 (reference 44/0x2C) (Originator) < Message type: DISCONNECT (69) < [08 02 82 90] < Cause (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location: Public network serving the local user (2) < Ext: 1 Cause: Unknown (16), class = Normal Event (1) ] -- Processing IE 8 (cs0, Cause) -- Channel 0/1, span 1 got hangup request -- Hungup 'Zap/25-1' == Spawn extension (from-mcleod-pri, 1693, 4) exited non-zero on 'Zap/1-1' == End MixMonitor Recording Zap/1-1 NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Disconnect Indication, peerstate Disconnect Request> Protocol Discriminator: Q.931 (8) len=9> Call Ref: len= 2 (reference 44/0x2C) (Terminator)> Message type: RELEASE (77)> [08 02 81 90]> Cause (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location:Private network serving the local user (1)> Ext: 1 Cause: Unknown (16), class = Normal Event (1) ]-- Hungup 'Zap/1-1' < Protocol Discriminator: Q.931 (8) len=5 < Call Ref: len= 2 (reference 44/0x2C) (Originator) < Message type: RELEASE COMPLETE (90) NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Null, peerstate Null NEW_HANGUP DEBUG: Destroying the call, ourstate Null, peerstate Null -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060705/3b8e6c1b/attachment.htm
Watkins, Bradley
2006-Jul-05 09:20 UTC
[asterisk-users] Troubleshooting Random PRI disconnects
My first advice is to double and triple-check that your switchtype settings match. We had an issue that looked *exactly* the same from a PRI debug standpoint and it turned out that while the carrier said we were NI2, it was actually DMS100. Regards, - Brad ________________________________ From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Shawn Kelley Sent: Wednesday, July 05, 2006 11:35 AM To: asterisk-users@lists.digium.com Subject: [asterisk-users] Troubleshooting Random PRI disconnects Hi all, We are having an issue with Random Disconnects wit our PRI connection. We are going into a T100P card from a Cisco IAD. Below is a copy of our PRI Debug. We will be talking on the phone and all the sudden the line will go dead. It acts as if the remote party hungup. However, the remote party is not hanging up. Can anyone give me some hints on where to look for the cause of this? -- Zap/25-1 is ringing> Protocol Discriminator: Q.931 (8) len=9> Call Ref: len= 2 (reference 44/0x2C) (Terminator)> Message type: ALERTING (1)> [1e 02 81 88]> Progress Indicator (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0)0: 0 Location: Private network serving the local user (1)> Ext: 1 Progress Description: Inbandinformation or appropriate pattern now available. (8) ] -- Zap/25-1 is ringing -- Zap/25-1 is ringing -- Zap/25-1 answered Zap/1-1> Protocol Discriminator: Q.931 (8) len=14> Call Ref: len= 2 (reference 44/0x2C) (Terminator)> Message type: CONNECT (7)> [18 03 a9 83 81]> Channel ID (len= 5) [ Ext: 1 IntID: Implicit, PRI Spare: 0, ExclusiveDchan: 0> ChanSel: Reserved> Ext: 1 Coding: 0 Number Specified ChannelType: 3> Ext: 1 Channel: 1 ]> [1e 02 81 82]> Progress Indicator (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0)0: 0 Location: Private network serving the local user (1)> Ext: 1 Progress Description: Calledequipment is non-ISDN. (2) ] < Protocol Discriminator: Q.931 (8) len=5 < Call Ref: len= 2 (reference 44/0x2C) (Originator) < Message type: CONNECT ACKNOWLEDGE (15) < Protocol Discriminator: Q.931 (8) len=9 < Call Ref: len= 2 (reference 44/0x2C) (Originator) < Message type: DISCONNECT (69) < [08 02 82 90] < Cause (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location: Public network serving the local user (2) < Ext: 1 Cause: Unknown (16), class = Normal Event (1) ] -- Processing IE 8 (cs0, Cause) -- Channel 0/1, span 1 got hangup request -- Hungup 'Zap/25-1' == Spawn extension (from-mcleod-pri, 1693, 4) exited non-zero on 'Zap/1-1' == End MixMonitor Recording Zap/1-1 NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Disconnect Indication, peerstate Disconnect Request> Protocol Discriminator: Q.931 (8) len=9> Call Ref: len= 2 (reference 44/0x2C) (Terminator)> Message type: RELEASE (77)> [08 02 81 90]> Cause (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0Location: Private network serving the local user (1)> Ext: 1 Cause: Unknown (16), class = Normal Event (1)] -- Hungup 'Zap/1-1' < Protocol Discriminator: Q.931 (8) len=5 < Call Ref: len= 2 (reference 44/0x2C) (Originator) < Message type: RELEASE COMPLETE (90) NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Null, peerstate Null NEW_HANGUP DEBUG: Destroying the call, ourstate Null, peerstate Null The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060705/dfc0c9fb/attachment.htm
Check your setting in your zapata.conf file and try the following. busydetect=no priindication=outofband James Hawks -----Original Message----- From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Shawn Kelley Sent: Wednesday, July 05, 2006 8:35 AM To: asterisk-users@lists.digium.com Subject: [asterisk-users] Troubleshooting Random PRI disconnects Hi all, We are having an issue with Random Disconnects wit our PRI connection. We are going into a T100P card from a Cisco IAD. Below is a copy of our PRI Debug. We will be talking on the phone and all the sudden the line will go dead. It acts as if the remote party hungup. However, the remote party is not hanging up. Can anyone give me some hints on where to look for the cause of this? ??? -- Zap/25-1 is ringing> Protocol Discriminator: Q.931 (8)? len=9 > Call Ref: len= 2 (reference 44/0x2C) (Terminator) > Message type: ALERTING (1) > [1e 02 81 88] > Progress Indicator (len= 4) [ Ext: 1? Coding: CCITT (ITU) standard (0) 0:0?? Location: Private network serving the local user (1)>?????????????????????????????? Ext: 1? Progress Description: Inbandinformation or appropriate pattern now available. (8) ] ??? -- Zap/25-1 is ringing ??? -- Zap/25-1 is ringing ??? -- Zap/25-1 answered Zap/1-1> Protocol Discriminator: Q.931 (8)? len=14 > Call Ref: len= 2 (reference 44/0x2C) (Terminator) > Message type: CONNECT (7) > [18 03 a9 83 81] > Channel ID (len= 5) [ Ext: 1? IntID: Implicit, PRI Spare: 0, ExclusiveDchan: 0>??????????????????????? ChanSel: Reserved >?????????????????????? Ext: 1? Coding: 0?? Number Specified?? Channel Type:3>?????????????????????? Ext: 1? Channel: 1 ] > [1e 02 81 82] > Progress Indicator (len= 4) [ Ext: 1? Coding: CCITT (ITU) standard (0) 0:0?? Location: Private network serving the local user (1)>?????????????????????????????? Ext: 1? Progress Description: Calledequipment is non-ISDN. (2) ] < Protocol Discriminator: Q.931 (8)? len=5 < Call Ref: len= 2 (reference 44/0x2C) (Originator) < Message type: CONNECT ACKNOWLEDGE (15) < Protocol Discriminator: Q.931 (8)? len=9 < Call Ref: len= 2 (reference 44/0x2C) (Originator) < Message type: DISCONNECT (69) < [08 02 82 90] < Cause (len= 4) [ Ext: 1? Coding: CCITT (ITU) standard (0) 0: 0?? Location: Public network serving the local user (2) <????????????????? Ext: 1? Cause: Unknown (16), class = Normal Event (1) ] -- Processing IE 8 (cs0, Cause) ??? -- Channel 0/1, span 1 got hangup request ??? -- Hungup 'Zap/25-1' ? == Spawn extension (from-mcleod-pri, 1693, 4) exited non-zero on 'Zap/1-1' ? == End MixMonitor Recording Zap/1-1 NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Disconnect Indication, peerstate Disconnect Request> Protocol Discriminator: Q.931 (8)? len=9 > Call Ref: len= 2 (reference 44/0x2C) (Terminator) > Message type: RELEASE (77) > [08 02 81 90] > Cause (len= 4) [ Ext: 1? Coding: CCITT (ITU) standard (0) 0: 0?? Location:Private network serving the local user (1)>????????????????? Ext: 1? Cause: Unknown (16), class = Normal Event (1) ]??? -- Hungup 'Zap/1-1' < Protocol Discriminator: Q.931 (8)? len=5 < Call Ref: len= 2 (reference 44/0x2C) (Originator) < Message type: RELEASE COMPLETE (90) NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Null, peerstate Null NEW_HANGUP DEBUG: Destroying the call, ourstate Null, peerstate Null