Sprint PRI Help

Asterisk Asterisk Support
1

Hi Guys/Gals,

Currently we’ve got a PRI setup with Sprint and I’ve had them switch one of our analog numbers over to the PRI for testing. Currently we can make outbound calls with our softphones just fine, however when someone tries to dial our old analog number(which sprint claims is now pointed at the PRI) we get a “this number is not in service” message. Sprint claims that this is a problem with our PRI, the tech then requested a conference call with our “vendor”.

I wanted to know if there is anyway of seeing if the call is actually coming from the PRI, ive tried pri debug span 1 and pri intense debug span 1 and i am seeing nothing in the CLI when i dial the number. Is there anyway to debug this or verify the connection?

Thanks a million,
-mave

2

wich digum card are you using? you should see something. Check lights on the digium card to make sure they go green when you plug the pri in.
if you sart astersik with asterisk -vvvvc then you should see alarm messages when ever you plug or unplug the pri.

3

Hi Rusty,

We’re using the 110 card, the pri is UP, green, and we can make outbound calls with it.

What I’m asking is — if i make an inbound call to the pri from say… a cell phone. Is there anyway to see if there is actually a call inbound hitting our asterisk box (meaning there is a problem with our setup) or if the call isnt making it this far and there is a problem with Sprints end.

Thanks again!
-mave

4

this is what mine does

pri show span 1
Primary D-channel: 24
Status: Provisioned, Up, Active
Switchtype: National ISDN
Type: CPE
Window Length: 0/7
Sentrej: 0
SolicitFbit: 0
Retrans: 0
Busy: 0
Overlap Dial: 0

below is when a call comes in
pri debug span1
Protocol Discriminator: Q.931 (8) len=5
< Call Ref: len= 2 (reference 3/0x3) (Originator)
< Message type: CONNECT ACKNOWLEDGE (15)
– Remote UNIX connection
< Protocol Discriminator: Q.931 (8) len=46
< Call Ref: len= 2 (reference 4/0x4) (Originator)
< Message type: SETUP (5)
< [04 03 90 90 a2]
< Bearer Capability (len= 5) [ Ext: 1 Q.931 Std: 0 Info transfer capability: 3.1kHz audio (16)
< Ext: 1 Trans mode/rate: 64kbps, circuit-mode (16)
< Ext: 1 User information layer 1: u-Law (34)
< [18 03 a9 83 84]
< 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: 4 ]
< [1e 02 82 83]
< Progress Indicator (len= 4) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0 Location: Public network serving the local user (2)
< Ext: 1 Progress Description: Calling equipment is non-ISDN. (3) ]
< [6c 0c 21 83 37 33 31 38 38 35 33 34 38 33]
< Calling Number (len=14) [ Ext: 0 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1)
< Presentation: Presentation allowed of network provided number (3) ‘7318853483’ ]
< [70 0b a1 37 33 31 36 39 38 30 30 30 38]
< Called Number (len=13) [ Ext: 1 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan (E.164/E.163) (1) ‘7316980008’ ]
– Making new call for cr 4
– Processing Q.931 Call Setup
– Processing IE 4 (cs0, Bearer Capability)
– Processing IE 24 (cs0, Channel Identification)
– Processing IE 30 (cs0, Progress Indicator)
– Processing IE 108 (cs0, Calling Party Number)
– Processing IE 112 (cs0, Called Party Number)

Protocol Discriminator: Q.931 (8) len=10
Call Ref: len= 2 (reference 32772/0x8004) (Terminator)
Message type: CALL PROCEEDING (2)
[18 03 a9 83 84]
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: 4 ]
– Executing SetCallerID(“Zap/4-1”, “<7316980005>”) in new stack
– Executing Goto(“Zap/4-1”, “macro-stdexten|s|1”) in new stack
– Goto (macro-stdexten,s,1)

5

Sweet, I’m not crazy. Thanks for your help Rusty!

6

you can also ask them to capture the Q.931 message on the PRI, as well as an SS7 trap, when you place a call to your test number. just make sure the source of that call is not on the sprint network (try a non-sprint cell phone). if the call is placed on the same sprint switch, they wouldn’t need SS7 for the call setup.

google q.931 for more info on that – it’s pretty useful