Juan Pablo Mendoza
2006-Jan-31 12:17 UTC
[Asterisk-Users] E1 PRI Error: Provider error messages.
Hi, Hey people, i have a TE210P with a ISDN PRI in M?xico. It is working just fine with Asterisk, I just have a minor glinch. When I dial a number that doesn't exists the Zap channel is imediatly hungup, instead of putting my trougth the providers message: "Sorry, the number that you dialed does not exists, etc". I have a call center and the people there really need to be able to tell a busy number from a not exists number, otherwise they would be called the same dead number over and over again. Thanks.
Michael Collins
2006-Jan-31 13:57 UTC
[Asterisk-Users] E1 PRI Error: Provider error messages.
Juan, This is a typical problem with PRI providers. I'm dealing with the same issue. When a PRI call gets terminated, there's a "hangup cause" that gets sent to Asterisk on the D channel. Frequently you'll see hangup cause 16, which is "unknown." It's been my experience (in California) that hangup cause 16 is frequently, but not always, a disconnected number. Here is some information on the wiki that I have found helpful: http://www.voip-info.org/wiki/view/PRI http://www.voip-info.org/wiki-Asterisk+variable+hangupcause Here's a sample PRI debug message for a phone number I dialed with my A@H system. I turned on PRI debugging on the command line and captured this information. Note the DISCONNECT message toward the end of this log. The hangup cause is "unknown (16)" which is almost always what I get when I dial a disconnected number. You could always make a modification to your dialplan and create your own "this number has been disconnected" message to play to anyone who dials a number and receives this hangup cause. The number dialed is a disconnected number - 818-518-4557: -- Executing Dial("SIP/1160-3666", "ZAP/g0/8185184557") in new stack -- Making new call for cr 32785 -- Requested transfer capability: 0x00 - SPEECH> Protocol Discriminator: Q.931 (8) len=42 > Call Ref: len= 2 (reference 17/0x11) (Originator) > Message type: SETUP (5) > [04 03 80 90 a2] > Bearer Capability (len= 5) [ Ext: 1 Q.931 Std: 0 Info transfer capability: Speech (0) > Ext: 1 Trans mode/rate: 64kbps, circuit-mode (16) > Ext: 1 User information layer 1: u-Law (34) > [18 03 a9 83 81] > Channel ID (len= 5) [ Ext: 1 IntID: Implicit, PRI Spare: 0, Exclusive Dchan:0 > ChanSel: Reserved > Ext: 1 Coding: 0 Number Specified Channel Type: 3 > Ext: 1 Channel: 1 ] > [6c 0c 21 80 35 35 39 33 30 32 31 33 37 39] > Calling Number (len=14) [ Ext: 0 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) > Presentation: Presentation permitted, user number not screened (0) '5593021379' ] > [70 0b a1 38 31 38 35 31 38 34 35 35 37] > Called Number (len=13) [ Ext: 1 TON: National Number (2) NPI: ISDN/TelephonyNumbering Plan (E.164/E.163) (1) '8185184557' ] -- Called g0/8185184557 < Protocol Discriminator: Q.931 (8) len=10 < Call Ref: len= 2 (reference 17/0x11) (Terminator) < Message type: CALL PROCEEDING (2) < [18 03 a9 83 81] < Channel ID (len= 5) [ Ext: 1 IntID: Implicit, PRI Spare: 0, Exclusive Dchan:0 < ChanSel: Reserved < Ext: 1 Coding: 0 Number Specified Channel Type: 3 < Ext: 1 Channel: 1 ] -- Processing IE 24 (cs0, Channel Identification) -- Zap/1-1 is proceeding passing it to SIP/1160-3666 < Protocol Discriminator: Q.931 (8) len=9 < Call Ref: len= 2 (reference 17/0x11) (Terminator) < Message type: PROGRESS (3) < [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: Inband information or appropriate pattern now available. (8) ] -- Processing IE 30 (cs0, Progress Indicator) -- Zap/1-1 is making progress passing it to SIP/1160-3666 < Protocol Discriminator: Q.931 (8) len=9 < Call Ref: len= 2 (reference 17/0x11) (Terminator) < Message type: DISCONNECT (69) < [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) ] -- Processing IE 8 (cs0, Cause) -- Channel 0/1, span 1 got hangup request NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Disconnect Indication, peerstate Disconnect Request> Protocol Discriminator: Q.931 (8) len=16 > Call Ref: len= 2 (reference 17/0x11) (Originator) > 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) ] > [7e 05 04 40 5e 86 09] > User-User Information (len= 7) [ 04 40 5e 06 09 ]-- Hungup 'Zap/1-1' -----Original Message----- From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Juan Pablo Mendoza Sent: Tuesday, January 31, 2006 11:18 AM To: asterisk-users@lists.digium.com Subject: [Asterisk-Users] E1 PRI Error: Provider error messages. Hi, Hey people, i have a TE210P with a ISDN PRI in M?xico. It is working just fine with Asterisk, I just have a minor glinch. When I dial a number that doesn't exists the Zap channel is imediatly hungup, instead of putting my trougth the providers message: "Sorry, the number that you dialed does not exists, etc". I have a call center and the people there really need to be able to tell a busy number from a not exists number, otherwise they would be called the same dead number over and over again. Thanks. _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users