Adtran
Help
The Adtran community holiday season is starting next week! The holiday period will span from December 21, 2024 to January 6, 2025. During this time, responses to feedback form submissions may be delayed. If you are encountering product issues, you can reach out to Adtran support at any time.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
cyclesounds
New Contributor
‎07-19-2012 10:30 AM

908 Issues

Jump to solution

I have an Adtran 908 connected to a Toshiba IPedge system. SIP trunks to the Toshiba and a PRI connected to the LEC. When dialing out to certain cell carriers (Tmobile and AT&T) we do not hear a ringback tone. The call goes through but no ringback tone. When I call a Verizon cell number it works fine. Any ideas?

Labels (2)
Labels
0 Kudos
Reply
1 Solution

Accepted Solutions
Anonymous
Not applicable
‎07-23-2012 08:47 AM

Re: 908 Issues

Jump to solution

Hello and thanks for posting to our forum.

The signaling here is all correct.  As the call progresses the ADTRAN receives a Call Proceeding followed by a Progress message that contains Information Element (IE) Progress Indicator with Inband Audio Available from the PRI Provider.  This means the PRI provider side will be providing ringback toward the ADTRAN and the talkpath will need to be cut through or open so the user behind the ADTRAN hears the ringback.  The ADTRAN thus sends a SIP 183 Session Progress toward the Toshiba. 

Shortly after the Progress message, the ADTRAN receives an Alerting message from the PRI provider.  The ADTRAN now sends a SIP 180 Ringing toward the Toshiba.  At this point, the 180 Ringing means the Toshiba will now have to provide ringback for the user behind the ADTRAN.

I am not sure why the ringing/Progress changes on the PRI provider side, but the call sequence is not invalid.  SIP devices have to be able to adapt on the fly in cases like this when a 180 follows a 183.  You will need to check with Toshiba to check whether or not the PBX can handle this scenario.

Let me know if you have any questions.

Regards,

Geoff

View solution in original post

0 Kudos
Reply
10 Replies
Anonymous
Not applicable
‎07-19-2012 10:40 AM

Re: 908 Issues

Jump to solution

Hello cyclesounds,

Send the output of "debug isdn l2-formatted" and "debug sip stack messages".

Start the debug before the call and leave it active until the call completes.

I want to confirm that the carrier is sending the proper signaling.

It is also possible that the carrier is just not sending a ring tone on certain gateways and you will have to open a ticket with them.

I have seen this with a large carrier in the North East.

Thank you,

0 Kudos
Accept as Solution Reply
cyclesounds
New Contributor
‎07-19-2012 12:37 PM

Re: 908 Issues

Jump to solution
12:31:03.131 SIP.STACK MSG Rx: UDP src=10.207.134.2:5060 dst=10.207.134.3:5060
12:31:03.132 SIP.STACK MSG     INVITE sip:8326545576@10.207.134.3 SIP/2.0
12:31:03.132 SIP.STACK MSG     Via: SIP/2.0/UDP 10.207.134.2:5060;branch=z9hG4bK02bc88f59a342da1dc75fcff7eb5a372
12:31:03.133 SIP.STACK MSG     Max-Forwards: 70
12:31:03.133 SIP.STACK MSG     From: <sip:7134393900@10.207.134.3>;tag=884500844bcab60a
12:31:03.134 SIP.STACK MSG     To: sip:8326545576@10.207.134.3
12:31:03.135 SIP.STACK MSG     Call-ID: 4b1500844bc@10.207.134.2
12:31:03.135 SIP.STACK MSG     CSeq: 1 INVITE
12:31:03.136 SIP.STACK MSG     Contact: sip:7134393900@10.207.134.2:5060
12:31:03.136 SIP.STACK MSG     Allow: INVITE,ACK,CANCEL,BYE,OPTIONS,PRACK,UPDATE
12:31:03.137 SIP.STACK MSG     Supported: 100rel
12:31:03.137 SIP.STACK MSG     Content-Type: application/sdp
12:31:03.138 SIP.STACK MSG     Content-Length: 275
12:31:03.138 SIP.STACK MSG
12:31:03.139 SIP.STACK MSG     v=0
12:31:03.139 SIP.STACK MSG     o=7134393900 1342719164 1 IN IP4 10.207.134.82
12:31:03.140 SIP.STACK MSG     s=-
12:31:03.140 SIP.STACK MSG     c=IN IP4 10.207.134.82
12:31:03.141 SIP.STACK MSG     t=0 0
12:31:03.142 SIP.STACK MSG     m=audio 49154 RTP/AVP 0 18 101
12:31:03.142 SIP.STACK MSG     a=rtpmap:0 PCMU/8000
12:31:03.143 SIP.STACK MSG     a=ptime:20
12:31:03.143 SIP.STACK MSG     a=rtpmap:18 G729/8000
12:31:03.143 SIP.STACK MSG     a=ptime:40
12:31:03.144 SIP.STACK MSG     a=fmtp:18 annexb=no
12:31:03.144 SIP.STACK MSG     a=rtpmap:101 telephone-event/8000
12:31:03.145 SIP.STACK MSG     a=fmtp:101 0-15
12:31:03.145 SIP.STACK MSG     a=sendrecv
12:31:03.146 SIP.STACK MSG
12:31:03.158 SIP.STACK MSG Tx: UDP src=10.207.134.3:5060 dst=10.207.134.2:5060
12:31:03.158 SIP.STACK MSG     SIP/2.0 100 Trying
12:31:03.159 SIP.STACK MSG     From: <sip:7134393900@10.207.134.3>;tag=884500844bcab60a
12:31:03.159 SIP.STACK MSG     To: <sip:8326545576@10.207.134.3>
12:31:03.160 SIP.STACK MSG     Call-ID: 4b1500844bc@10.207.134.2
12:31:03.160 SIP.STACK MSG     CSeq: 1 INVITE
12:31:03.161 SIP.STACK MSG     Via: SIP/2.0/UDP 10.207.134.2:5060;branch=z9hG4bK02bc88f59a342da1dc75fcff7eb5a372
12:31:03.162 SIP.STACK MSG     Contact: <sip:8326545576@10.207.134.3:5060;transport=UDP>
12:31:03.162 SIP.STACK MSG     Supported: 100rel,replaces
12:31:03.163 SIP.STACK MSG     Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER, UPDATE
12:31:03.163 SIP.STACK MSG     User-Agent: ADTRAN_Total_Access_908_2nd_Gen/A5.02.00.E
12:31:03.164 SIP.STACK MSG     Content-Length: 0
12:31:03.164 SIP.STACK MSG

12:31:03.173 ISDN.L2_FMT PRI  1  ==============================================

12:31:03.173 ISDN.L2_FMT PRI  1  Sent  Sapi:00 C/R:R Tei:00 INFO Ns:62  Nr:6   P:0

12:31:03.174 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:155D
12:31:03.174 ISDN.L2_FMT PRI  1    M - 05 SETUP 
12:31:03.174 ISDN.L2_FMT PRI  1     IE - 04 BEARER CAPABILITY   Len=3
12:31:03.175 ISDN.L2_FMT PRI  1          80 Xfer Cap.:SPEECH      
12:31:03.175 ISDN.L2_FMT PRI  1          90 Xfer Rate:64k  
12:31:03.175 ISDN.L2_FMT PRI  1          A2 Layer 1:u-Law    
12:31:03.175 ISDN.L2_FMT PRI  1     IE - 18 CHANNEL ID      Len=3
12:31:03.176 ISDN.L2_FMT PRI  1          A1 Primary Rate
12:31:03.176 ISDN.L2_FMT PRI  1             Intfc ID:IMPLICIT
12:31:03.176 ISDN.L2_FMT PRI  1             Pref/Excl:PREFERRED
12:31:03.177 ISDN.L2_FMT PRI  1             D-Chan Indicated:NO
12:31:03.177 ISDN.L2_FMT PRI  1             Chan. Sel:FOLLOWS
12:31:03.177 ISDN.L2_FMT PRI  1          83 Numb/Map:NUMBER
12:31:03.177 ISDN.L2_FMT PRI  1          97 Channel:23
12:31:03.178 ISDN.L2_FMT PRI  1     IE - 6C CALLING PARTY # Len=12
12:31:03.178 ISDN.L2_FMT PRI  1          21 Numb. Type:NATIONAL
12:31:03.178 ISDN.L2_FMT PRI  1             Numb. Plan:E.164    
12:31:03.179 ISDN.L2_FMT PRI  1          80 Presentation:ALLOWED
12:31:03.179 ISDN.L2_FMT PRI  1             Ph.# 7134393900
12:31:03.179 ISDN.L2_FMT PRI  1     IE - 70 CALLED PARTY #  Len=11
12:31:03.180 ISDN.L2_FMT PRI  1          A1 Numb. Type:NATIONAL
12:31:03.180 ISDN.L2_FMT PRI  1             Numb. Plan:E.164    
12:31:03.180 ISDN.L2_FMT PRI  1             Ph.# 8326545576

12:31:03.409 ISDN.L2_FMT PRI  1  ==============================================

12:31:03.410 ISDN.L2_FMT PRI  1  Recd  Sapi:00 C/R:C Tei:00 INFO Ns:6   Nr:63  P:0

12:31:03.410 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:955D
12:31:03.410 ISDN.L2_FMT PRI  1    M - 02 CALL_PROC  
12:31:03.411 ISDN.L2_FMT PRI  1     IE - 18 CHANNEL ID      Len=3
12:31:03.411 ISDN.L2_FMT PRI  1          A9 Primary Rate
12:31:03.411 ISDN.L2_FMT PRI  1             Intfc ID:IMPLICIT
12:31:03.412 ISDN.L2_FMT PRI  1             Pref/Excl:EXCLUSIVE
12:31:03.412 ISDN.L2_FMT PRI  1             D-Chan Indicated:NO
12:31:03.412 ISDN.L2_FMT PRI  1             Chan. Sel:FOLLOWS
12:31:03.412 ISDN.L2_FMT PRI  1          83 Numb/Map:NUMBER
12:31:03.413 ISDN.L2_FMT PRI  1          97 Channel:23

12:31:04.837 ISDN.L2_FMT PRI  1  ==============================================

12:31:04.838 ISDN.L2_FMT PRI  1  Recd  Sapi:00 C/R:C Tei:00 INFO Ns:7   Nr:63  P:0

12:31:04.838 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:955D
12:31:04.838 ISDN.L2_FMT PRI  1    M - 03 PROGRESS   
12:31:04.838 ISDN.L2_FMT PRI  1     IE - 1E PROGRESS INDICATOR  Len=2
12:31:04.839 ISDN.L2_FMT PRI  1          84 Location:RLN
12:31:04.839 ISDN.L2_FMT PRI  1          88 Description:INBAND AUDIO AVAIL
12:31:04.859 SIP.STACK MSG Tx: UDP src=10.207.134.3:5060 dst=10.207.134.2:5060
12:31:04.860 SIP.STACK MSG     SIP/2.0 183 Session Progress
12:31:04.860 SIP.STACK MSG     From: <sip:7134393900@10.207.134.3>;tag=884500844bcab60a
12:31:04.861 SIP.STACK MSG     To: <sip:8326545576@10.207.134.3>;tag=251e8f0-7f000001-13c4-151f45-9b0717dd-151f45
12:31:04.862 SIP.STACK MSG     Call-ID: 4b1500844bc@10.207.134.2
12:31:04.862 SIP.STACK MSG     CSeq: 1 INVITE
12:31:04.863 SIP.STACK MSG     Via: SIP/2.0/UDP 10.207.134.2:5060;branch=z9hG4bK02bc88f59a342da1dc75fcff7eb5a372
12:31:04.863 SIP.STACK MSG     Contact: <sip:8326545576@10.207.134.3:5060;transport=UDP>
12:31:04.864 SIP.STACK MSG     Supported: 100rel,replaces
12:31:04.864 SIP.STACK MSG     Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER, UPDATE
12:31:04.865 SIP.STACK MSG     User-Agent: ADTRAN_Total_Access_908_2nd_Gen/A5.02.00.E
12:31:04.865 SIP.STACK MSG     Content-Type: application/sdp
12:31:04.866 SIP.STACK MSG     Content-Length: 217
12:31:04.866 SIP.STACK MSG
12:31:04.867 SIP.STACK MSG     v=0
12:31:04.867 SIP.STACK MSG     o=- 1342719063 1342719063 IN IP4 10.207.134.3
12:31:04.868 SIP.STACK MSG     s=-
12:31:04.868 SIP.STACK MSG     c=IN IP4 10.207.134.3
12:31:04.869 SIP.STACK MSG     t=0 0
12:31:04.869 SIP.STACK MSG     m=audio 10000 RTP/AVP 0 101
12:31:04.870 SIP.STACK MSG     a=rtpmap:0 PCMU/8000
12:31:04.871 SIP.STACK MSG     a=silenceSupp:off - - - -
12:31:04.871 SIP.STACK MSG     a=rtpmap:101 telephone-event/8000
12:31:04.872 SIP.STACK MSG     a=fmtp:101 0-15
12:31:04.872 SIP.STACK MSG

12:31:07.817 ISDN.L2_FMT PRI  1  ==============================================

12:31:07.817 ISDN.L2_FMT PRI  1  Recd  Sapi:00 C/R:C Tei:00 INFO Ns:8   Nr:63  P:0

12:31:07.817 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:955D
12:31:07.818 ISDN.L2_FMT PRI  1    M - 01 ALERTING   
12:31:07.838 SIP.STACK MSG Tx: UDP src=10.207.134.3:5060 dst=10.207.134.2:5060
12:31:07.839 SIP.STACK MSG     SIP/2.0 180 Ringing
12:31:07.839 SIP.STACK MSG     From: <sip:7134393900@10.207.134.3>;tag=884500844bcab60a
12:31:07.840 SIP.STACK MSG     To: <sip:8326545576@10.207.134.3>;tag=251e8f0-7f000001-13c4-151f45-9b0717dd-151f45
12:31:07.840 SIP.STACK MSG     Call-ID: 4b1500844bc@10.207.134.2
12:31:07.841 SIP.STACK MSG     CSeq: 1 INVITE
12:31:07.841 SIP.STACK MSG     Via: SIP/2.0/UDP 10.207.134.2:5060;branch=z9hG4bK02bc88f59a342da1dc75fcff7eb5a372
12:31:07.842 SIP.STACK MSG     Contact: <sip:8326545576@10.207.134.3:5060;transport=UDP>
12:31:07.842 SIP.STACK MSG     Supported: 100rel,replaces
12:31:07.843 SIP.STACK MSG     Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER, UPDATE
12:31:07.844 SIP.STACK MSG     User-Agent: ADTRAN_Total_Access_908_2nd_Gen/A5.02.00.E
12:31:07.844 SIP.STACK MSG     Content-Length: 0
12:31:07.845 SIP.STACK MSG
12:31:18.519 SIP.STACK MSG Rx: UDP src=10.207.134.2:5060 dst=10.207.134.3:5060
12:31:18.520 SIP.STACK MSG     OPTIONS sip:10.207.134.3 SIP/2.0
12:31:18.521 SIP.STACK MSG     Via: SIP/2.0/UDP 10.207.134.2:5060;branch=z9hG4bKfab3bd9c1458129cff3b2a28744b8771
12:31:18.521 SIP.STACK MSG     Max-Forwards: 70
12:31:18.522 SIP.STACK MSG     From: <sip:3900@10.207.134.3>;tag=749500844cc16403
12:31:18.522 SIP.STACK MSG     To: sip:10.207.134.3
12:31:18.523 SIP.STACK MSG     Call-ID: 26500844cc@10.207.134.2
12:31:18.523 SIP.STACK MSG     CSeq: 1 OPTIONS
12:31:18.524 SIP.STACK MSG     Content-Length: 0
12:31:18.524 SIP.STACK MSG
12:31:18.530 SIP.STACK MSG Tx: UDP src=10.207.134.3:5060 dst=10.207.134.2:5060
12:31:18.531 SIP.STACK MSG     SIP/2.0 200 OK
12:31:18.531 SIP.STACK MSG     From: <sip:3900@10.207.134.3>;tag=749500844cc16403
12:31:18.532 SIP.STACK MSG     To: <sip:10.207.134.3>;tag=251ec60-7f000001-13c4-151f53-b545c641-151f53
12:31:18.532 SIP.STACK MSG     Call-ID: 26500844cc@10.207.134.2
12:31:18.533 SIP.STACK MSG     CSeq: 1 OPTIONS
12:31:18.533 SIP.STACK MSG     Via: SIP/2.0/UDP 10.207.134.2:5060;branch=z9hG4bKfab3bd9c1458129cff3b2a28744b8771
12:31:18.534 SIP.STACK MSG     Supported: 100rel,replaces
12:31:18.534 SIP.STACK MSG     Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER
12:31:18.535 SIP.STACK MSG     User-Agent: ADTRAN_Total_Access_908_2nd_Gen/A5.02.00.E
12:31:18.535 SIP.STACK MSG     Content-Length: 0
12:31:18.536 SIP.STACK MSG
12:31:22.360 SIP.STACK MSG Rx: UDP src=10.207.134.2:5060 dst=10.207.134.3:5060
12:31:22.360 SIP.STACK MSG     BYE sip:12018885063@10.207.134.3 SIP/2.0
12:31:22.361 SIP.STACK MSG     Via: SIP/2.0/UDP 10.207.134.2:5060;branch=z9hG4bKae79231f02741027e83fca9314ae639d
12:31:22.361 SIP.STACK MSG     Max-Forwards: 70
12:31:22.362 SIP.STACK MSG     From: <sip:7134393900@10.207.134.3>;tag=8845008441a55cd9
12:31:22.362 SIP.STACK MSG     To: <sip:12018885063@10.207.134.3>;tag=251bdf8-7f000001-13c4-151ea2-c8df8adc-151ea2
12:31:22.363 SIP.STACK MSG     Call-ID: 1015008441a@10.207.134.2
12:31:22.363 SIP.STACK MSG     CSeq: 2 BYE
12:31:22.364 SIP.STACK MSG     Content-Length: 0
12:31:22.364 SIP.STACK MSG
12:31:22.371 SIP.STACK MSG Tx: UDP src=10.207.134.3:5060 dst=10.207.134.2:5060
12:31:22.371 SIP.STACK MSG     SIP/2.0 200 OK
12:31:22.372 SIP.STACK MSG     From: <sip:7134393900@10.207.134.3>;tag=8845008441a55cd9
12:31:22.372 SIP.STACK MSG     To: <sip:12018885063@10.207.134.3>;tag=251bdf8-7f000001-13c4-151ea2-c8df8adc-151ea2
12:31:22.373 SIP.STACK MSG     Call-ID: 1015008441a@10.207.134.2
12:31:22.373 SIP.STACK MSG     CSeq: 2 BYE
12:31:22.374 SIP.STACK MSG     Via: SIP/2.0/UDP 10.207.134.2:5060;branch=z9hG4bKae79231f02741027e83fca9314ae639d
12:31:22.374 SIP.STACK MSG     Supported: 100rel,replaces
12:31:22.375 SIP.STACK MSG     Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER, UPDATE
12:31:22.375 SIP.STACK MSG     User-Agent: ADTRAN_Total_Access_908_2nd_Gen/A5.02.00.E
12:31:22.376 SIP.STACK MSG     Content-Length: 0
12:31:22.376 SIP.STACK MSG

12:31:22.394 ISDN.L2_FMT PRI  1  ==============================================

12:31:22.394 ISDN.L2_FMT PRI  1  Sent  Sapi:00 C/R:R Tei:00 INFO Ns:63  Nr:9   P:0

12:31:22.395 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:1557
12:31:22.395 ISDN.L2_FMT PRI  1    M - 45 DISCONNECT 
12:31:22.395 ISDN.L2_FMT PRI  1     IE - 08 CAUSE           Len=2
12:31:22.395 ISDN.L2_FMT PRI  1          80 Location:U
12:31:22.396 ISDN.L2_FMT PRI  1          90 Cause:16 (NORMAL_CLEARING)

12:31:22.417 ISDN.L2_FMT PRI  1  ==============================================

12:31:22.417 ISDN.L2_FMT PRI  1  Recd  Sapi:00 C/R:C Tei:00 INFO Ns:9   Nr:64  P:0

12:31:22.417 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:9557
12:31:22.418 ISDN.L2_FMT PRI  1    M - 4D RELEASE

12:31:22.434 ISDN.L2_FMT PRI  1  ==============================================

12:31:22.434 ISDN.L2_FMT PRI  1  Sent  Sapi:00 C/R:R Tei:00 INFO Ns:64  Nr:10  P:0

12:31:22.435 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:1557
12:31:22.435 ISDN.L2_FMT PRI  1    M - 5A RELEASE_CMP

12:31:29.707 ISDN.L2_FMT PRI  1  ==============================================

12:31:29.708 ISDN.L2_FMT PRI  1  Recd  Sapi:00 C/R:C Tei:00 INFO Ns:10  Nr:65  P:0

12:31:29.708 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:955D
12:31:29.708 ISDN.L2_FMT PRI  1    M - 07 CONNECT
12:31:29.709 ISDN.L2_FMT PRI  1     IE - 1E PROGRESS INDICATOR  Len=2
12:31:29.709 ISDN.L2_FMT PRI  1          84 Location:RLN
12:31:29.709 ISDN.L2_FMT PRI  1          82 Description:DEST. NOT ISDN   

12:31:29.714 ISDN.L2_FMT PRI  1  ==============================================

12:31:29.714 ISDN.L2_FMT PRI  1  Sent  Sapi:00 C/R:R Tei:00 INFO Ns:65  Nr:11  P:0

12:31:29.715 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:155D
12:31:29.715 ISDN.L2_FMT PRI  1    M - 0F CONNECT_ACK
12:31:29.720 SIP.STACK MSG Tx: UDP src=10.207.134.3:5060 dst=10.207.134.2:5060
12:31:29.721 SIP.STACK MSG     SIP/2.0 200 OK
12:31:29.721 SIP.STACK MSG     From: <sip:7134393900@10.207.134.3>;tag=884500844bcab60a
12:31:29.722 SIP.STACK MSG     To: <sip:8326545576@10.207.134.3>;tag=251e8f0-7f000001-13c4-151f45-9b0717dd-151f45
12:31:29.722 SIP.STACK MSG     Call-ID: 4b1500844bc@10.207.134.2
12:31:29.723 SIP.STACK MSG     CSeq: 1 INVITE
12:31:29.723 SIP.STACK MSG     Via: SIP/2.0/UDP 10.207.134.2:5060;branch=z9hG4bK02bc88f59a342da1dc75fcff7eb5a372
12:31:29.724 SIP.STACK MSG     Contact: <sip:8326545576@10.207.134.3:5060;transport=UDP>
12:31:29.725 SIP.STACK MSG     Supported: 100rel,replaces
12:31:29.725 SIP.STACK MSG     Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER, UPDATE
12:31:29.726 SIP.STACK MSG     User-Agent: ADTRAN_Total_Access_908_2nd_Gen/A5.02.00.E
12:31:29.726 SIP.STACK MSG     Content-Type: application/sdp
12:31:29.727 SIP.STACK MSG     Content-Length: 217
12:31:29.728 SIP.STACK MSG
12:31:29.728 SIP.STACK MSG     v=0
12:31:29.729 SIP.STACK MSG     o=- 1342719063 1342719063 IN IP4 10.207.134.3
12:31:29.729 SIP.STACK MSG     s=-
12:31:29.730 SIP.STACK MSG     c=IN IP4 10.207.134.3
12:31:29.730 SIP.STACK MSG     t=0 0
12:31:29.731 SIP.STACK MSG     m=audio 10000 RTP/AVP 0 101
12:31:29.731 SIP.STACK MSG     a=rtpmap:0 PCMU/8000
12:31:29.732 SIP.STACK MSG     a=silenceSupp:off - - - -
12:31:29.732 SIP.STACK MSG     a=rtpmap:101 telephone-event/8000
12:31:29.733 SIP.STACK MSG     a=fmtp:101 0-15
12:31:29.733 SIP.STACK MSG
12:31:29.778 SIP.STACK MSG Rx: UDP src=10.207.134.2:5060 dst=10.207.134.3:5060
12:31:29.779 SIP.STACK MSG     ACK sip:8326545576@10.207.134.3 SIP/2.0
12:31:29.780 SIP.STACK MSG     Via: SIP/2.0/UDP 10.207.134.2:5060;branch=z9hG4bKa0f06ed33dd93d7905dc4d7a528d2d87
12:31:29.780 SIP.STACK MSG     Max-Forwards: 70
12:31:29.781 SIP.STACK MSG     From: <sip:7134393900@10.207.134.3>;tag=884500844bcab60a
12:31:29.781 SIP.STACK MSG     To: <sip:8326545576@10.207.134.3>;tag=251e8f0-7f000001-13c4-151f45-9b0717dd-151f45
12:31:29.782 SIP.STACK MSG     Call-ID: 4b1500844bc@10.207.134.2
12:31:29.782 SIP.STACK MSG     CSeq: 1 ACK
12:31:29.783 SIP.STACK MSG     Content-Length: 0
12:31:29.783 SIP.STACK MSG
12:31:35.419 SIP.STACK MSG Rx: UDP src=10.207.134.2:5060 dst=10.207.134.3:5060
12:31:35.419 SIP.STACK MSG     BYE sip:8326545576@10.207.134.3 SIP/2.0
12:31:35.420 SIP.STACK MSG     Via: SIP/2.0/UDP 10.207.134.2:5060;branch=z9hG4bK685cab379ab62270465bc2bb1a720901
12:31:35.421 SIP.STACK MSG     Max-Forwards: 70
12:31:35.421 SIP.STACK MSG     From: <sip:7134393900@10.207.134.3>;tag=884500844bcab60a
12:31:35.422 SIP.STACK MSG     To: <sip:8326545576@10.207.134.3>;tag=251e8f0-7f000001-13c4-151f45-9b0717dd-151f45
12:31:35.422 SIP.STACK MSG     Call-ID: 4b1500844bc@10.207.134.2
12:31:35.423 SIP.STACK MSG     CSeq: 2 BYE
12:31:35.423 SIP.STACK MSG     Content-Length: 0
12:31:35.423 SIP.STACK MSG
12:31:35.430 SIP.STACK MSG Tx: UDP src=10.207.134.3:5060 dst=10.207.134.2:5060
12:31:35.430 SIP.STACK MSG     SIP/2.0 200 OK
12:31:35.431 SIP.STACK MSG     From: <sip:7134393900@10.207.134.3>;tag=884500844bcab60a
12:31:35.431 SIP.STACK MSG     To: <sip:8326545576@10.207.134.3>;tag=251e8f0-7f000001-13c4-151f45-9b0717dd-151f45
12:31:35.432 SIP.STACK MSG     Call-ID: 4b1500844bc@10.207.134.2
12:31:35.432 SIP.STACK MSG     CSeq: 2 BYE
12:31:35.433 SIP.STACK MSG     Via: SIP/2.0/UDP 10.207.134.2:5060;branch=z9hG4bK685cab379ab62270465bc2bb1a720901
12:31:35.433 SIP.STACK MSG     Supported: 100rel,replaces
12:31:35.434 SIP.STACK MSG     Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER, UPDATE
12:31:35.434 SIP.STACK MSG     User-Agent: ADTRAN_Total_Access_908_2nd_Gen/A5.02.00.E
12:31:35.435 SIP.STACK MSG     Content-Length: 0
12:31:35.436 SIP.STACK MSG

12:31:35.454 ISDN.L2_FMT PRI  1  ==============================================

12:31:35.454 ISDN.L2_FMT PRI  1  Sent  Sapi:00 C/R:R Tei:00 INFO Ns:66  Nr:11  P:0

12:31:35.455 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:155D
12:31:35.455 ISDN.L2_FMT PRI  1    M - 45 DISCONNECT 
12:31:35.455 ISDN.L2_FMT PRI  1     IE - 08 CAUSE           Len=2
12:31:35.455 ISDN.L2_FMT PRI  1          80 Location:U
12:31:35.456 ISDN.L2_FMT PRI  1          90 Cause:16 (NORMAL_CLEARING)

12:31:35.475 ISDN.L2_FMT PRI  1  ==============================================

12:31:35.475 ISDN.L2_FMT PRI  1  Recd  Sapi:00 C/R:C Tei:00 INFO Ns:11  Nr:67  P:0

12:31:35.476 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:955D
12:31:35.476 ISDN.L2_FMT PRI  1    M - 4D RELEASE

12:31:35.494 ISDN.L2_FMT PRI  1  ==============================================

12:31:35.494 ISDN.L2_FMT PRI  1  Sent  Sapi:00 C/R:R Tei:00 INFO Ns:67  Nr:12  P:0

12:31:35.495 ISDN.L2_FMT PRI  1    Prot:08  CRL:2  CRV:155D
12:31:35.495 ISDN.L2_FMT PRI  1    M - 5A RELEASE_CMP
0 Kudos
Accept as Solution Reply
cyclesounds
New Contributor
‎07-19-2012 12:59 PM

Re: 908 Issues

Jump to solution

12:51:19.198 ISDN.L2_FMT PRI  1  ==============================================

12:51:19.199 ISDN.L2_FMT PRI  1  Sent  Sapi:00 C/R:R Tei:00 INFO Ns:7   Nr:87  P:0

12:51:19.199 ISDN.L2_FMT PRI  1        Prot:08  CRL:2  CRV:1562

12:51:19.199 ISDN.L2_FMT PRI  1        M - 05 SETUP      

12:51:19.199 ISDN.L2_FMT PRI  1         IE - 04 BEARER CAPABILITY   Len=3

12:51:19.200 ISDN.L2_FMT PRI  1              80 Xfer Cap.:SPEECH           

12:51:19.200 ISDN.L2_FMT PRI  1              90 Xfer Rate:64k  

12:51:19.200 ISDN.L2_FMT PRI  1              A2 Layer 1:u-Law         

12:51:19.201 ISDN.L2_FMT PRI  1         IE - 18 CHANNEL ID          Len=3

12:51:19.201 ISDN.L2_FMT PRI  1              A1 Primary Rate

12:51:19.201 ISDN.L2_FMT PRI  1                 Intfc ID:IMPLICIT

12:51:19.201 ISDN.L2_FMT PRI  1                 Pref/Excl:PREFERRED

12:51:19.202 ISDN.L2_FMT PRI  1                 D-Chan Indicated:NO

12:51:19.202 ISDN.L2_FMT PRI  1                 Chan. Sel:FOLLOWS

12:51:19.202 ISDN.L2_FMT PRI  1              83 Numb/Map:NUMBER

12:51:19.203 ISDN.L2_FMT PRI  1              92 Channel:18

12:51:19.203 ISDN.L2_FMT PRI  1         IE - 6C CALLING PARTY #     Len=12

12:51:19.203 ISDN.L2_FMT PRI  1              21 Numb. Type:NATIONAL     

12:51:19.204 ISDN.L2_FMT PRI  1                 Numb. Plan:E.164         

12:51:19.204 ISDN.L2_FMT PRI  1              80 Presentation:ALLOWED    

12:51:19.204 ISDN.L2_FMT PRI  1                 Ph.# 7134393900

12:51:19.204 ISDN.L2_FMT PRI  1         IE - 70 CALLED PARTY #      Len=11

12:51:19.205 ISDN.L2_FMT PRI  1              A1 Numb. Type:NATIONAL     

12:51:19.205 ISDN.L2_FMT PRI  1                 Numb. Plan:E.164         

12:51:19.205 ISDN.L2_FMT PRI  1                 Ph.# 8326545576

12:51:19.415 ISDN.L2_FMT PRI  1  ==============================================

12:51:19.415 ISDN.L2_FMT PRI  1  Recd  Sapi:00 C/R:C Tei:00 INFO Ns:87  Nr:8   P:0

12:51:19.416 ISDN.L2_FMT PRI  1        Prot:08  CRL:2  CRV:9562

12:51:19.416 ISDN.L2_FMT PRI  1        M - 02 CALL_PROC  

12:51:19.416 ISDN.L2_FMT PRI  1         IE - 18 CHANNEL ID          Len=3

12:51:19.416 ISDN.L2_FMT PRI  1              A9 Primary Rate

12:51:19.417 ISDN.L2_FMT PRI  1                 Intfc ID:IMPLICIT

12:51:19.417 ISDN.L2_FMT PRI  1                 Pref/Excl:EXCLUSIVE

12:51:19.417 ISDN.L2_FMT PRI  1                 D-Chan Indicated:NO

12:51:19.418 ISDN.L2_FMT PRI  1                 Chan. Sel:FOLLOWS

12:51:19.418 ISDN.L2_FMT PRI  1              83 Numb/Map:NUMBER

12:51:19.418 ISDN.L2_FMT PRI  1              92 Channel:18

12:51:20.861 ISDN.L2_FMT PRI  1  ==============================================

12:51:20.861 ISDN.L2_FMT PRI  1  Recd  Sapi:00 C/R:C Tei:00 INFO Ns:88  Nr:8   P:0

12:51:20.861 ISDN.L2_FMT PRI  1        Prot:08  CRL:2  CRV:9562

12:51:20.862 ISDN.L2_FMT PRI  1        M - 03 PROGRESS   

12:51:20.862 ISDN.L2_FMT PRI  1         IE - 1E PROGRESS INDICATOR  Len=2

12:51:20.862 ISDN.L2_FMT PRI  1              84 Location:RLN

12:51:20.863 ISDN.L2_FMT PRI  1              88 Description:INBAND AUDIO AVAIL

12:51:23.998 ISDN.L2_FMT PRI  1  ==============================================

12:51:23.998 ISDN.L2_FMT PRI  1  Recd  Sapi:00 C/R:C Tei:00 INFO Ns:89  Nr:8   P:0

12:51:23.998 ISDN.L2_FMT PRI  1        Prot:08  CRL:2  CRV:9562

12:51:23.999 ISDN.L2_FMT PRI  1        M - 01 ALERTING   

12:51:45.240 ISDN.L2_FMT PRI  1  ==============================================

12:51:45.240 ISDN.L2_FMT PRI  1  Recd  Sapi:00 C/R:C Tei:00 INFO Ns:90  Nr:8   P:0

12:51:45.240 ISDN.L2_FMT PRI  1        Prot:08  CRL:2  CRV:9562

12:51:45.241 ISDN.L2_FMT PRI  1        M - 07 CONNECT    

12:51:45.241 ISDN.L2_FMT PRI  1         IE - 1E PROGRESS INDICATOR  Len=2

12:51:45.241 ISDN.L2_FMT PRI  1              84 Location:RLN

12:51:45.241 ISDN.L2_FMT PRI  1              82 Description:DEST. NOT ISDN   

12:51:45.249 ISDN.L2_FMT PRI  1  ==============================================

12:51:45.249 ISDN.L2_FMT PRI  1  Sent  Sapi:00 C/R:R Tei:00 INFO Ns:8   Nr:91  P:0

12:51:45.250 ISDN.L2_FMT PRI  1        Prot:08  CRL:2  CRV:1562

12:51:45.250 ISDN.L2_FMT PRI  1        M - 0F CONNECT_ACK

12:51:51.329 ISDN.L2_FMT PRI  1  ==============================================

12:51:51.329 ISDN.L2_FMT PRI  1  Sent  Sapi:00 C/R:R Tei:00 INFO Ns:9   Nr:91  P:0

12:51:51.330 ISDN.L2_FMT PRI  1        Prot:08  CRL:2  CRV:1562

12:51:51.330 ISDN.L2_FMT PRI  1        M - 45 DISCONNECT 

12:51:51.330 ISDN.L2_FMT PRI  1         IE - 08 CAUSE               Len=2

12:51:51.330 ISDN.L2_FMT PRI  1              80 Location:U

12:51:51.331 ISDN.L2_FMT PRI  1              90 Cause:16 (NORMAL_CLEARING)

12:51:51.350 ISDN.L2_FMT PRI  1  ==============================================

12:51:51.351 ISDN.L2_FMT PRI  1  Recd  Sapi:00 C/R:C Tei:00 INFO Ns:91  Nr:10  P:0

12:51:51.351 ISDN.L2_FMT PRI  1        Prot:08  CRL:2  CRV:9562

12:51:51.351 ISDN.L2_FMT PRI  1        M - 4D RELEASE    

12:51:51.369 ISDN.L2_FMT PRI  1  ==============================================

12:51:51.369 ISDN.L2_FMT PRI  1  Sent  Sapi:00 C/R:R Tei:00 INFO Ns:10  Nr:92  P:0

12:51:51.370 ISDN.L2_FMT PRI  1        Prot:08  CRL:2  CRV:1562

12:51:51.370 ISDN.L2_FMT PRI  1        M - 5A RELEASE_CMP

0 Kudos
Accept as Solution Reply
cyclesounds
New Contributor
‎07-19-2012 01:00 PM

Re: 908 Issues

Jump to solution

I put a couple logs on the discussion. Let me know what you think. Thanks

0 Kudos
Accept as Solution Reply
Anonymous
Not applicable
‎07-19-2012 02:02 PM

Re: 908 Issues

Jump to solution

The signaling looks OK.

Can you post a copy of your config? (remove any sensitive data)

You may also want to contact your provider.

0 Kudos
Accept as Solution Reply
cyclesounds
New Contributor
‎07-19-2012 02:59 PM

Re: 908 Issues

Jump to solution

!

!

! ADTRAN, Inc. OS version A2.06.00.E

! Boot ROM version 14.04.00

! Platform: Total Access 908 (2nd Gen), part number 4212908L1

! Serial number CFG0961821

!

!

hostname "TA908"

enable password xxxxx

!

!

ip subnet-zero

ip classless

ip routing

!

!

ip domain-proxy

!

!

no auto-config

!

event-history on

no logging forwarding

no logging email

!

no service password-encryption

!

username "admin" password "password"

!

banner motd #

        Important 

       

Web username/password is configured to admin/password.

Enable and Telnet passwords are configured to "password".

Please change them immediately.

The ethernet 0/1 interface is enabled with an address of 192.168.1.34

Telnet/SSH access is also enabled.

#

!

!

no ip firewall alg msn

no ip firewall alg mszone

no ip firewall alg h323

!

!

!

!

!

no dot11ap access-point-control

!

!

!

!

!

!

!

!

!

!

!

!

interface eth 0/1

  ip address  x.x.x.x  255.255.255.0

  media-gateway ip primary

  no shutdown

!

!

!

!

interface t1 0/1

  shutdown

!

interface t1 0/2

  description PRI

  tdm-group 1 timeslots 1-24 speed 64

  no shutdown

!

!

interface pri 1

  description pri 1

  connect t1 0/2 tdm-group 1

  role user

  no shutdown

!

!

interface fxs 0/1

  no shutdown

!

interface fxs 0/2

  no shutdown

!

interface fxs 0/3

  no shutdown

!

interface fxs 0/4

  no shutdown

!

interface fxs 0/5

  no shutdown

!

interface fxs 0/6

  no shutdown

!

interface fxs 0/7

  no shutdown

!

interface fxs 0/8

  no shutdown

!

!

isdn-group 1

  connect pri 1

!

!

isdn-group 2

!

!

!

!

timing-source t1 0/2

!

!

!

!

!

!

!

ip route 0.0.0.0 0.0.0.0 x.x.x.x

!

no ip tftp server

no ip tftp server overwrite

ip http server

no ip http secure-server

no ip snmp agent

no ip ftp server

no ip scp server

no ip sntp server

!

!

!

!

!

!

ip sip

ip sip udp 5060

no ip sip tcp

!

!

!

voice feature-mode network

voice transfer-mode local

voice forward-mode local

!

!

!

!

isdn-number-template 1 prefix "" subscriber NXX-XXXX

isdn-number-template 2 prefix "" national NXX-NXX-XXXX

isdn-number-template 3 prefix 011 international X$

isdn-number-template 4 prefix "" national 1NXX-NXX-XXXX

!

!

!

!

voice codec-list 1

  default

  codec g711ulaw

  codec g729

!

voice codec-list G711_G729

  codec g711ulaw

  codec g729

!

!

!

voice trunk-list PBX_TRUNK

  trunk T02

!

!

voice trunk T01 type isdn

  description "PSTN"

  resource-selection circular descending

  connect isdn-group 1

  modem-passthrough

  rtp delay-mode adaptive

!

voice trunk T02 type sip

  description "PBX"

  sip-server primary x.x.x.x

  codec-group G711_G729

  grammar from host local

  grammar from host override registered-users sip-server

  update-supported

  transfer-mode network

  no prefer reinvite-without-sdp 

!

!

!

!

voice grouped-trunk PBX

  no description

  trunk T02

  accept XXXX cost 0

  accept NXX-XXXX cost 0

  accept NXX-NXX-XXXX cost 0

  accept 0-NXX-NXX-XXXX cost 0

  accept 1-NXX-NXX-XXXX cost 0

  accept 411 cost 0

  accept 611 cost 0

  accept 911 cost 0

  accept 011$ cost 0

  accept *$ cost 0

  accept #$ cost 0

  accept 9NXX-XXXX cost 0

  accept 9NXX-NXX-XXXX cost 0

!

!

voice grouped-trunk PSTN

  no description

  trunk T01

  accept NXX-XXXX cost 0

  accept NXX-NXX-XXXX cost 0

  accept 0-NXX-NXX-XXXX cost 0

  accept 1-NXX-NXX-XXXX cost 0

  accept 411 cost 0

  accept 611 cost 0

  accept 911 cost 0

  accept 011-$ cost 0

  accept 1-800-NXX-XXXX cost 0

  accept 1-888-NXX-XXXX cost 0

  accept 1-877-NXX-XXXX cost 0

  accept 1-866-NXX-XXXX cost 0

  accept 1-855-NXX-XXXX cost 0

  reject 976-XXXX

  reject 1-900-NXX-XXXX

  reject 1-976-NXX-XXXX

  permit list PBX_TRUNK

  !deny all other trunks

  !deny all other ani

!

!

!

!

!

!

ip sip

!

ip sip authenticate

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

!

line con 0

  no login

!

line telnet 0 4

  login

  password adtran

  no shutdown

line ssh 0 4

  login local-userlist

  no shutdown

!

!

!

!

!

end

0 Kudos
Accept as Solution Reply
Anonymous
Not applicable
‎07-19-2012 03:14 PM

Re: 908 Issues

Jump to solution

Looks OK to me.

Maybe someone can chime in if they see anything.

Did you try contacting your provider?

Another option is to try it on the FXS port.

If the issue is still there it will remove the PBX as being the problem.

0 Kudos
Accept as Solution Reply
Anonymous
Not applicable
‎07-23-2012 08:47 AM

Re: 908 Issues

Jump to solution

Hello and thanks for posting to our forum.

The signaling here is all correct.  As the call progresses the ADTRAN receives a Call Proceeding followed by a Progress message that contains Information Element (IE) Progress Indicator with Inband Audio Available from the PRI Provider.  This means the PRI provider side will be providing ringback toward the ADTRAN and the talkpath will need to be cut through or open so the user behind the ADTRAN hears the ringback.  The ADTRAN thus sends a SIP 183 Session Progress toward the Toshiba. 

Shortly after the Progress message, the ADTRAN receives an Alerting message from the PRI provider.  The ADTRAN now sends a SIP 180 Ringing toward the Toshiba.  At this point, the 180 Ringing means the Toshiba will now have to provide ringback for the user behind the ADTRAN.

I am not sure why the ringing/Progress changes on the PRI provider side, but the call sequence is not invalid.  SIP devices have to be able to adapt on the fly in cases like this when a 180 follows a 183.  You will need to check with Toshiba to check whether or not the PBX can handle this scenario.

Let me know if you have any questions.

Regards,

Geoff

0 Kudos
Reply
mjkiela
New Contributor
‎07-23-2012 02:15 PM

Re: 908 Issues

Jump to solution

Sounds more like an ARS Table problem in your settings on your Phone Switch. Can you trace the call out to your Verizon Lines and see the route pattersn they are using to get off site and program your ARS for NPA/NXX into your ARS route table for the (Tmobile and AT&T) using the same path

0 Kudos
Accept as Solution Reply
Anonymous
Not applicable
‎08-01-2012 07:53 AM

Re: 908 Issues

Jump to solution

cyclesounds,

I went ahead and flagged this post as "Assumed Answered".  If any of the responses on this thread assisted you, please mark them as Correct or Helpful as the case may be with the applicable buttons.  This will make them visible and help other members of the community find solutions more easily.  If you still need assistance, I would be more than happy to continue working with you on this - just let me know in a reply.

Thanks!

David

0 Kudos
Accept as Solution Reply