[Asterisk-Users] 911 and ISDN PRI

Wed Feb 8 16:56:24 MST 2006

Joe,

It is entirely possible, even probable, that you spoke with someone who
doesn't know the difference between PRI and good ol' fashion T1 trunks.
If he insists that "the channel never comes up" then he is definitely
looking in the wrong place.  Assuming he's talking about the B channel,
obviously it's not coming up because that's what you're troubleshooting.
If he's insisting that the D channel isn't coming up then obviously none
of your calls would be working, DID or otherwise.  

Sounds like you've got a case of "vendor wheel-of-blame" going on.
Please contact me off list and I'll be happy to help you out.  I used to
be a vendor so I know the routine.   I've got a dozen T1's, half of
which are PRI's, from 3 different telcos so I'm used to this kind of
stuff.

-MC

  _____  

From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Joe
Pukepail
Sent: Wednesday, February 08, 2006 3:31 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] 911 and ISDN PRI

I've talked to the carrier (verizon), what they said is that the call is
not leaving my phone equipment. I tried to tell him that I'm getting an
error back from his system, but he insists that the channel never comes
up.  Their answers was "talk to your telco vendor, its on their end".
So I guess I'm pretty much SOL when it comes to using 911 with the PRI.

Below is the debug, they wanted me to try all the DID numbers to see if
it worked on any of them (40 numbers) and the billing number, wouldn't
work with any of them. 

    -- Executing SetCallerID("IAX2/sycam-16384", "8157548823") in new
stack
    -- Executing Dial("IAX2/sycam-16384", "Zap/g2/911") in new stack
-- Making new call for cr 33385 
    -- Requested transfer capability: 0x00 - SPEECH
> Protocol Discriminator: Q.931 (8)  len=39
> Call Ref: len= 2 (reference 617/0x269) (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 ]
> [1e 02 80 83]I>
> Progress Indicator (len= 4) [ Ext: 1  Coding: CCITT (ITU) standard (0)
0: 0   Location: User (0)
>                               Ext: 1  Progress Description: Calling
equipment is non-ISDN. (3) ] 
> [6c 0c 41 80 38 31 35 37 35 34 38 38 32 33]
> Calling Number (len=14) [ Ext: 0  TON: Subscriber Number (4)  NPI:
ISDN/Telephony Numbering Plan (E.164/E.163) (1)
>                           Presentation: Presentation permitted, user
number not screened (0) '8157548823' ] 
> [70 04 a1 39 31 31]
> Called Number (len= 6) [ Ext: 1  TON: National Number (2)  NPI:
ISDN/Telephony Numbering Plan (E.164/E.163) (1) '911' ]
    -- Called g2/911
< Protocol Discriminator: Q.931 (8)  len=9 
< Call Ref: len= 2 (reference 617/0x269) (Terminator)
< Message type: RELEASE COMPLETE (90)
< [08 02 82 9c]
< Cause (len= 4) [ Ext: 1  Coding: CCITT (ITU) standard (0) 0: 0
Location: Public network serving the local user (2) 
<                  Ext: 1  Cause: Invalid number format (28), class =
Normal Event (1) ]
-- Processing IE 8 (cs0, Cause)
    -- Channel 0/1, span 2 got hangup
NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Null, peerstate Null 
NEW_HANGUP DEBUG: Destroying the call, ourstate Null, peerstate Null
    -- Hungup 'Zap/25-1'

On 2/8/06, Watkins, Bradley <Bradley.Watkins at compuware.com> wrote: 

It looks like the outbound caller ID is not being set properly.  Most of
the carriers that I've dealt with will act exactly as you said if you do
not set it to what is expected at the 911 center. 

In particular:

> Calling Number (len= 8) [ Ext: 0  TON: Subscriber Number (4)  NPI:
ISDN/Telephony Numbering Plan (E.164/E.163) (1)
>                           Presentation: Presentation permitted, user
number not screened (0) '3251' ] 

Your user number being sent is just the caller ID of the SIP channel.

Regards,

- Brad

-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com ] On Behalf Of Joe
Pukepail

Sent: Tuesday, February 07, 2006 3:26 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] 911 and ISDN PRI 

I have a call in with the carrier, below is the PRI debug, looks like it
is getting hungup because of "Invalid Number format", I did try to use
Setcallerid to change the callerID to a DID number in a previous
attempt, but it still didn't go through.   Not sure if that "invalid
number format" is the calling number or the number I'm calling.  I'll
let the list know the result.  

I would encourage everyone to test their 911 functionality (especially
if you have a PRI), I almost didn't check it.  The PRI is up and 411
works, so I almost assumed that 911 would work.   Make sure you call the
police station first to make sure they are not swamped by real emergency
calls and let them know you are testing . 

    -- Executing NoOp("SIP/3251-7316", "3251") in new stack
    -- Executing Dial("SIP/3251-7316", "Zap/g2/911") in new stack
-- Making new call for cr 33144
    -- Requested transfer capability: 0x00 - SPEECH 
> Protocol Discriminator: Q.931 (8)  len=44
> Call Ref: len= 2 (reference 376/0x178) (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 ]
> [1e 02 80 83]I>
> Progress Indicator (len= 4) [ Ext: 1  Coding: CCITT (ITU) standard (0)
0: 0   Location: User (0) 
>                               Ext: 1  Progress Description: Calling
equipment is non-ISDN. (3) ]
> [28 09 b1 52 65 63 70 74 69 6f 6e]
> Display (len= 9) Charset: 31 [ Recption ]
> [6c 06 41 80 33 32 35 31] 
> Calling Number (len= 8) [ Ext: 0  TON: Subscriber Number (4)  NPI:
ISDN/Telephony Numbering Plan (E.164/E.163) (1)
>                           Presentation: Presentation permitted, user
number not screened (0) '3251' ] 
> [70 04 a1 39 31 31]
> Called Number (len= 6) [ Ext: 1  TON: National Number (2)  NPI:
ISDN/Telephony Numbering Plan (E.164/E.163) (1) '911' ]
    -- Called g2/911
< Protocol Discriminator: Q.931 (8)  len=9 
< Call Ref: len= 2 (reference 376/0x178) (Terminator)
< Message type: RELEASE COMPLETE (90)
< [08 02 82 9c]
< Cause (len= 4) [ Ext: 1  Coding: CCITT (ITU) standard (0) 0: 0
Location: Public network serving the local user (2) 
<                  Ext: 1  Cause: Invalid number format (28), class =
Normal Event (1) ]
-- Processing IE 8 (cs0, Cause)
    -- Channel 0/1, span 2 got hangup

On 2/7/06, Mark Phillips <g7ltt at g7ltt.com> wrote: 

I dunno about your provider but I know that 2 of my 3 MCI PRI circuits
have no 911 abilities. MCI tells me this is becasue I have no local 
dialing plan on them.

Mark, G7LTT/KC2ENI
Randolph, NJ
http://www.g7ltt.com <http://www.g7ltt.com/> 

Michael Collins wrote: 
> 911 **should** work on a PRI.  If you are getting a hangup and you
don't 
> see a valid hangupcause, it might be best to get your carrier on the
> line and have them monitor the circuit while you dial 911.  They might

> be able to tell you what the problem is.
>
> 
>
> -MC
>
>
>
>
------------------------------------------------------------------------
>
> *From:* asterisk-users-bounces at lists.digium.com
<mailto:asterisk-users-bounces at lists.digium.com> 
> [mailto:asterisk-users-bounces at lists.digium.com
<mailto:asterisk-users-bounces at lists.digium.com> ] *On Behalf Of *Joe
Pukepail
> *Sent:* Tuesday, February 07, 2006 10:10 AM
> *To:* Asterisk Users Mailing List - Non-Commercial Discussion 
> *Subject:* [Asterisk-Users] 911 and ISDN PRI
>
>
>
> Does asterisk support this?  I have a location that I planned to only
> put a PRI line, but testing 911 (I called them first), I just get a 
> hangup.  Does 911 normally work over a PRI line?  Anything special I 
> have to setup in asterisk?
>
>
>
------------------------------------------------------------------------
>
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com
<http://easynews.com/>  --
>
> Asterisk-Users mailing list
> To UNSUBSCRIBE or update options visit: 
>     http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________ 
--Bandwidth and Colocation provided by Easynews.com
<http://easynews.com/>  --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit: 
  http://lists.digium.com/mailman/listinfo/asterisk-users
<http://lists.digium.com/mailman/listinfo/asterisk-users> 

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. 

_______________________________________________
--Bandwidth and Colocation provided by Easynews.com
<http://easynews.com/> --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060208/909a4624/attachment.htm