Support
Community

Anonymous · ‎01-18-2017

I have a 924e configured as an SBC between AT&T and a 3CX PBX. Outbound calls are not receiving any ringback. I have tried the ringback override 180 and 183 commands on both the AT&T and 3CX trunks with no effect.

Below is the sanitized output of "debug sip stack messages" along with the config. At one point I see that the Adtran is sending a SIP 180 Ringing message which I've underlined below. I notice that this message shows up a few seconds after the call has begun and I feel like it should ring before that point but it never does. Other than this problem, everything else is working fine.

Any help is appreciated!

172.16.100.6 is the PBX

172.16.100.7 is the inside interface of the Adtran 924e

20.20.20.100 is the outside interface of the Adtran 924e

30.30.30.100 is the AT&T SIP IP

11:14:06.897 SIP.STACK MSG Rx: UDP src=172.16.100.6:5060 dst=172.16.100.7:5060

11:14:06.897 SIP.STACK MSG INVITE sip:4445556666@172.16.100.7:5060 SIP/2.0

11:14:06.897 SIP.STACK MSG Via: SIP/2.0/UDP 172.16.100.6:5060;branch=z9hG4bK-d8754z-a252767e7475986e-1---d8754z-;rport

11:14:06.897 SIP.STACK MSG Max-Forwards: 70

11:14:06.898 SIP.STACK MSG Contact: <sip:1112223333@172.16.100.6:5060>

11:14:06.898 SIP.STACK MSG To: <sip:4445556666@172.16.100.7:5060>

11:14:06.898 SIP.STACK MSG From: "7778889999"<sip:7778889999@172.16.100.7:5060>;tag=3542da46

11:14:06.898 SIP.STACK MSG Call-ID: MzY4MmJmZTVkNGJlMzhkNTkzNzE5YTgzNDY2MGE2ZWM.

11:14:06.898 SIP.STACK MSG CSeq: 1 INVITE

11:14:06.898 SIP.STACK MSG Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE

11:14:06.899 SIP.STACK MSG Content-Type: application/sdp

11:14:06.899 SIP.STACK MSG Supported: replaces

11:14:06.899 SIP.STACK MSG User-Agent: 3CXPhoneSystem 14.0.49169.513 (48654)

11:14:06.899 SIP.STACK MSG Content-Length: 370

11:14:06.899 SIP.STACK MSG Remote-Party-ID: "7778889999"<sip:7778889999@172.16.100.7:5060>;party=calling

11:14:06.900 SIP.STACK MSG

11:14:06.900 SIP.STACK MSG v=0

11:14:06.900 SIP.STACK MSG o=3cxPS 367320367104 114202509313 IN IP4 172.16.100.6

11:14:06.900 SIP.STACK MSG s=3cxPS Audio call

11:14:06.900 SIP.STACK MSG c=IN IP4 172.16.100.6

11:14:06.901 SIP.STACK MSG b=AS:84

11:14:06.901 SIP.STACK MSG t=0 0

11:14:06.901 SIP.STACK MSG a=X-nat:0

11:14:06.901 SIP.STACK MSG m=audio 7020 RTP/AVP 0 8 3 96

11:14:06.901 SIP.STACK MSG c=IN IP4 172.16.100.6

11:14:06.902 SIP.STACK MSG b=TIAS:64000

11:14:06.902 SIP.STACK MSG b=AS:84

11:14:06.902 SIP.STACK MSG a=rtpmap:0 PCMU/8000

11:14:06.902 SIP.STACK MSG a=rtpmap:8 PCMA/8000

11:14:06.902 SIP.STACK MSG a=rtpmap:3 GSM/8000

11:14:06.903 SIP.STACK MSG a=rtpmap:96 telephone-event/8000

11:14:06.903 SIP.STACK MSG a=fmtp:96 0-15

11:14:06.903 SIP.STACK MSG a=sendrecv

11:14:06.903 SIP.STACK MSG m=video 0 RTP/AVP 31

11:14:06.903 SIP.STACK MSG c=IN IP4 127.0.0.1

11:14:06.903 SIP.STACK MSG

11:14:06.909 SIP.STACK MSG Tx: UDP src=172.16.100.7:5060 dst=172.16.100.6:5060

11:14:06.909 SIP.STACK MSG SIP/2.0 100 Trying

11:14:06.910 SIP.STACK MSG From: "7778889999"<sip:7778889999@172.16.100.7:5060>;tag=3542da46

11:14:06.910 SIP.STACK MSG To: <sip:4445556666@172.16.100.7:5060>

11:14:06.910 SIP.STACK MSG Call-ID: MzY4MmJmZTVkNGJlMzhkNTkzNzE5YTgzNDY2MGE2ZWM.

11:14:06.910 SIP.STACK MSG CSeq: 1 INVITE

11:14:06.910 SIP.STACK MSG Via: SIP/2.0/UDP 172.16.100.6:5060;rport=5060;branch=z9hG4bK-d8754z-a252767e7475986e-1---d8754z-

11:14:06.910 SIP.STACK MSG Contact: <sip:4445556666@172.16.100.7:5060;transport=UDP>

11:14:06.911 SIP.STACK MSG Supported: 100rel,replaces

11:14:06.911 SIP.STACK MSG Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER

11:14:06.911 SIP.STACK MSG User-Agent: ADTRAN_Total_Access_924e_2nd_Gen/R11.10.5.E

11:14:06.911 SIP.STACK MSG Content-Length: 0

11:14:06.911 SIP.STACK MSG

11:14:06.919 SIP.STACK MSG Tx: UDP src=20.20.20.100:5060 dst=30.30.30.100:5060

11:14:06.919 SIP.STACK MSG INVITE sip:4445556666@30.30.30.100:5060 SIP/2.0

11:14:06.919 SIP.STACK MSG From: "7778889999" <sip:7778889999@30.30.30.100:5060;transport=UDP>;tag=4dfae60-7f000001-13c4-3eae73-9d7a0fb8-3eae73

11:14:06.919 SIP.STACK MSG To: <sip:4445556666@30.30.30.100:5060>

11:14:06.919 SIP.STACK MSG Call-ID: 4e50e90-7f000001-13c4-3eae73-9f35e390-3eae73@30.30.30.100

11:14:06.919 SIP.STACK MSG CSeq: 1 INVITE

11:14:06.920 SIP.STACK MSG Via: SIP/2.0/UDP 20.20.20.100:5060;branch=z9hG4bK-3eae73-f4d971c3-46af9c2b

11:14:06.920 SIP.STACK MSG Max-Forwards: 70

11:14:06.920 SIP.STACK MSG Supported: 100rel,replaces

11:14:06.920 SIP.STACK MSG Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER

11:14:06.920 SIP.STACK MSG User-Agent: ADTRAN_Total_Access_924e_2nd_Gen/R11.10.5.E

11:14:06.921 SIP.STACK MSG Contact: <sip:7778889999@20.20.20.100:5060;transport=UDP>

11:14:06.921 SIP.STACK MSG Content-Type: application/sdp

11:14:06.921 SIP.STACK MSG Content-Length: 291

11:14:06.921 SIP.STACK MSG

11:14:06.921 SIP.STACK MSG v=0

11:14:06.922 SIP.STACK MSG o=3cxPS 367320367104 114202509313 IN IP4 20.20.20.100

11:14:06.922 SIP.STACK MSG s=3cxPS Audio call

11:14:06.922 SIP.STACK MSG c=IN IP4 20.20.20.100

11:14:06.922 SIP.STACK MSG b=AS:84

11:14:06.922 SIP.STACK MSG t=0 0

11:14:06.922 SIP.STACK MSG a=X-nat:0

11:14:06.923 SIP.STACK MSG m=audio 12984 RTP/AVP 0 96

11:14:06.923 SIP.STACK MSG c=IN IP4 20.20.20.100

11:14:06.923 SIP.STACK MSG b=TIAS:64000

11:14:06.923 SIP.STACK MSG b=AS:84

11:14:06.923 SIP.STACK MSG a=sendrecv

11:14:06.924 SIP.STACK MSG a=rtpmap:0 PCMU/8000

11:14:06.924 SIP.STACK MSG a=rtpmap:96 telephone-event/8000

11:14:06.924 SIP.STACK MSG a=fmtp:96 0-15

11:14:06.924 SIP.STACK MSG

11:14:06.955 SIP.STACK MSG Rx: UDP src=30.30.30.100:5060 dst=20.20.20.100:5060

11:14:06.955 SIP.STACK MSG SIP/2.0 100 Trying

11:14:06.955 SIP.STACK MSG From: "7778889999" <sip:7778889999@30.30.30.100:5060;transport=UDP>;tag=4dfae60-7f000001-13c4-3eae73-9d7a0fb8-3eae73

11:14:06.955 SIP.STACK MSG To: <sip:4445556666@30.30.30.100:5060>

11:14:06.955 SIP.STACK MSG Call-ID: 4e50e90-7f000001-13c4-3eae73-9f35e390-3eae73@30.30.30.100

11:14:06.956 SIP.STACK MSG CSeq: 1 INVITE

11:14:06.956 SIP.STACK MSG Via: SIP/2.0/UDP 20.20.20.100:5060;branch=z9hG4bK-3eae73-f4d971c3-46af9c2b

11:14:06.956 SIP.STACK MSG

11:14:11.587 SIP.STACK MSG Rx: UDP src=30.30.30.100:5060 dst=20.20.20.100:5060

11:14:11.587 SIP.STACK MSG SIP/2.0 183 Session Progress

11:14:11.587 SIP.STACK MSG From: "7778889999" <sip:7778889999@30.30.30.100:5060;transport=UDP>;tag=4dfae60-7f000001-13c4-3eae73-9d7a0fb8-3eae73

11:14:11.587 SIP.STACK MSG To: <sip:4445556666@30.30.30.100:5060>;tag=42411032-1484796830606

11:14:11.587 SIP.STACK MSG Call-ID: 4e50e90-7f000001-13c4-3eae73-9f35e390-3eae73@30.30.30.100

11:14:11.588 SIP.STACK MSG CSeq: 1 INVITE

11:14:11.588 SIP.STACK MSG Via: SIP/2.0/UDP 20.20.20.100:5060;branch=z9hG4bK-3eae73-f4d971c3-46af9c2b

11:14:11.588 SIP.STACK MSG Supported: timer

11:14:11.588 SIP.STACK MSG Contact: <sip:30.30.30.100:5060;transport=udp>

11:14:11.588 SIP.STACK MSG Session: Media

11:14:11.588 SIP.STACK MSG Call-Info: <sip:50.50.50.100>;appearance-index=1

11:14:11.589 SIP.STACK MSG Allow: INVITE,ACK,CANCEL,BYE,REFER,INFO,NOTIFY,PRACK,OPTIONS

11:14:11.589 SIP.STACK MSG Content-Length: 214

11:14:11.589 SIP.STACK MSG Content-Disposition: session; handling=required

11:14:11.589 SIP.STACK MSG Content-Type: application/sdp

11:14:11.589 SIP.STACK MSG

11:14:11.590 SIP.STACK MSG v=0

11:14:11.590 SIP.STACK MSG o=BroadWorks 71932260 1 IN IP4 30.30.30.100

11:14:11.590 SIP.STACK MSG s=-

11:14:11.590 SIP.STACK MSG c=IN IP4 30.30.30.100

11:14:11.590 SIP.STACK MSG t=0 0

11:14:11.591 SIP.STACK MSG m=audio 30908 RTP/AVP 0 96

11:14:11.591 SIP.STACK MSG a=rtpmap:0 PCMU/8000

11:14:11.591 SIP.STACK MSG a=rtpmap:96 telephone-event/8000

11:14:11.591 SIP.STACK MSG a=fmtp:96 0-15

11:14:11.591 SIP.STACK MSG a=sendrecv

11:14:11.591 SIP.STACK MSG a=maxptime:20

11:14:11.592 SIP.STACK MSG

11:14:11.598 SIP.STACK MSG Tx: UDP src=172.16.100.7:5060 dst=172.16.100.6:5060

11:14:11.598 SIP.STACK MSG SIP/2.0 183 Session Progress

11:14:11.598 SIP.STACK MSG From: "7778889999"<sip:7778889999@172.16.100.7:5060>;tag=3542da46

11:14:11.598 SIP.STACK MSG To: <sip:4445556666@172.16.100.7:5060>;tag=4dde968-7f000001-13c4-3eae77-d4b425fd-3eae77

11:14:11.598 SIP.STACK MSG Call-ID: MzY4MmJmZTVkNGJlMzhkNTkzNzE5YTgzNDY2MGE2ZWM.

11:14:11.599 SIP.STACK MSG CSeq: 1 INVITE

11:14:11.599 SIP.STACK MSG Via: SIP/2.0/UDP 172.16.100.6:5060;rport=5060;branch=z9hG4bK-d8754z-a252767e7475986e-1---d8754z-

11:14:11.599 SIP.STACK MSG Contact: <sip:4445556666@172.16.100.7:5060;transport=UDP>

11:14:11.599 SIP.STACK MSG Supported: 100rel,replaces

11:14:11.599 SIP.STACK MSG Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER

11:14:11.600 SIP.STACK MSG User-Agent: ADTRAN_Total_Access_924e_2nd_Gen/R11.10.5.E

11:14:11.600 SIP.STACK MSG Content-Type: application/sdp

11:14:11.600 SIP.STACK MSG Content-Length: 230

11:14:11.600 SIP.STACK MSG

11:14:11.600 SIP.STACK MSG v=0

11:14:11.601 SIP.STACK MSG o=BroadWorks 71932260 1 IN IP4 172.16.100.7

11:14:11.601 SIP.STACK MSG s=-

11:14:11.601 SIP.STACK MSG c=IN IP4 172.16.100.7

11:14:11.601 SIP.STACK MSG t=0 0

11:14:11.601 SIP.STACK MSG m=audio 12986 RTP/AVP 0 96

11:14:11.602 SIP.STACK MSG a=sendrecv

11:14:11.602 SIP.STACK MSG a=maxptime:20

11:14:11.602 SIP.STACK MSG a=rtpmap:0 PCMU/8000

11:14:11.603 SIP.STACK MSG a=rtpmap:96 telephone-event/8000

11:14:11.603 SIP.STACK MSG a=fmtp:96 0-15

11:14:11.603 SIP.STACK MSG m=video 0 RTP/AVP 31

11:14:11.603 SIP.STACK MSG

11:14:11.605 SIP.STACK MSG Tx: UDP src=172.16.100.7:5060 dst=172.16.100.6:5060

11:14:11.605 SIP.STACK MSG SIP/2.0 180 Ringing

11:14:11.605 SIP.STACK MSG From: "7778889999"<sip:7778889999@172.16.100.7:5060>;tag=3542da46

11:14:11.605 SIP.STACK MSG To: <sip:4445556666@172.16.100.7:5060>;tag=4dde968-7f000001-13c4-3eae77-d4b425fd-3eae77

11:14:11.606 SIP.STACK MSG Call-ID: MzY4MmJmZTVkNGJlMzhkNTkzNzE5YTgzNDY2MGE2ZWM.

11:14:11.606 SIP.STACK MSG CSeq: 1 INVITE

11:14:11.606 SIP.STACK MSG Via: SIP/2.0/UDP 172.16.100.6:5060;rport=5060;branch=z9hG4bK-d8754z-a252767e7475986e-1---d8754z-

11:14:11.606 SIP.STACK MSG Contact: <sip:4445556666@172.16.100.7:5060;transport=UDP>

11:14:11.606 SIP.STACK MSG Supported: 100rel,replaces

11:14:11.607 SIP.STACK MSG Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER

11:14:11.607 SIP.STACK MSG User-Agent: ADTRAN_Total_Access_924e_2nd_Gen/R11.10.5.E

11:14:11.607 SIP.STACK MSG Content-Length: 0

11:14:11.607 SIP.STACK MSG

11:14:14.337 SIP.STACK MSG

11:14:20.231 SIP.STACK MSG Rx: UDP src=172.16.100.6:5060 dst=172.16.100.7:5060

11:14:20.231 SIP.STACK MSG CANCEL sip:4445556666@172.16.100.7:5060 SIP/2.0

11:14:20.231 SIP.STACK MSG Via: SIP/2.0/UDP 172.16.100.6:5060;branch=z9hG4bK-d8754z-a252767e7475986e-1---d8754z-;rport

11:14:20.231 SIP.STACK MSG Max-Forwards: 70

11:14:20.231 SIP.STACK MSG To: <sip:4445556666@172.16.100.7:5060>

11:14:20.232 SIP.STACK MSG From: "7778889999"<sip:7778889999@172.16.100.7:5060>;tag=3542da46

11:14:20.232 SIP.STACK MSG Call-ID: MzY4MmJmZTVkNGJlMzhkNTkzNzE5YTgzNDY2MGE2ZWM.

11:14:20.232 SIP.STACK MSG CSeq: 1 CANCEL

11:14:20.232 SIP.STACK MSG User-Agent: 3CXPhoneSystem 14.0.49169.513 (48654)

11:14:20.232 SIP.STACK MSG Content-Length: 0

11:14:20.233 SIP.STACK MSG

11:14:20.235 SIP.STACK MSG Tx: UDP src=172.16.100.7:5060 dst=172.16.100.6:5060

11:14:20.235 SIP.STACK MSG SIP/2.0 200 OK

11:14:20.236 SIP.STACK MSG From: "7778889999"<sip:7778889999@172.16.100.7:5060>;tag=3542da46

11:14:20.236 SIP.STACK MSG To: <sip:4445556666@172.16.100.7:5060>;tag=4dde968-7f000001-13c4-3eae77-d4b425fd-3eae77

11:14:20.236 SIP.STACK MSG Call-ID: MzY4MmJmZTVkNGJlMzhkNTkzNzE5YTgzNDY2MGE2ZWM.

11:14:20.236 SIP.STACK MSG CSeq: 1 CANCEL

11:14:20.236 SIP.STACK MSG Via: SIP/2.0/UDP 172.16.100.6:5060;rport=5060;branch=z9hG4bK-d8754z-a252767e7475986e-1---d8754z-

11:14:20.236 SIP.STACK MSG Supported: 100rel,replaces

11:14:20.237 SIP.STACK MSG Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER

11:14:20.237 SIP.STACK MSG User-Agent: ADTRAN_Total_Access_924e_2nd_Gen/R11.10.5.E

11:14:20.237 SIP.STACK MSG Content-Length: 0

11:14:20.237 SIP.STACK MSG

11:14:20.239 SIP.STACK MSG Tx: UDP src=172.16.100.7:5060 dst=172.16.100.6:5060

11:14:20.239 SIP.STACK MSG SIP/2.0 487 Request Terminated

11:14:20.239 SIP.STACK MSG From: "7778889999"<sip:7778889999@172.16.100.7:5060>;tag=3542da46

11:14:20.240 SIP.STACK MSG To: <sip:4445556666@172.16.100.7:5060>;tag=4dde968-7f000001-13c4-3eae77-d4b425fd-3eae77

11:14:20.240 SIP.STACK MSG Call-ID: MzY4MmJmZTVkNGJlMzhkNTkzNzE5YTgzNDY2MGE2ZWM.

11:14:20.240 SIP.STACK MSG CSeq: 1 INVITE

11:14:20.240 SIP.STACK MSG Via: SIP/2.0/UDP 172.16.100.6:5060;rport=5060;branch=z9hG4bK-d8754z-a252767e7475986e-1---d8754z-

11:14:20.240 SIP.STACK MSG Supported: 100rel,replaces

11:14:20.241 SIP.STACK MSG Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER

11:14:20.241 SIP.STACK MSG User-Agent: ADTRAN_Total_Access_924e_2nd_Gen/R11.10.5.E

11:14:20.241 SIP.STACK MSG Content-Length: 0

11:14:20.241 SIP.STACK MSG

11:14:20.243 SIP.STACK MSG Rx: UDP src=172.16.100.6:5060 dst=172.16.100.7:5060

11:14:20.243 SIP.STACK MSG ACK sip:4445556666@172.16.100.7:5060 SIP/2.0

11:14:20.243 SIP.STACK MSG Via: SIP/2.0/UDP 172.16.100.6:5060;branch=z9hG4bK-d8754z-a252767e7475986e-1---d8754z-;rport

11:14:20.244 SIP.STACK MSG Max-Forwards: 70

11:14:20.244 SIP.STACK MSG To: <sip:4445556666@172.16.100.7:5060>;tag=4dde968-7f000001-13c4-3eae77-d4b425fd-3eae77

11:14:20.244 SIP.STACK MSG From: "7778889999"<sip:7778889999@172.16.100.7:5060>;tag=3542da46

11:14:20.244 SIP.STACK MSG Call-ID: MzY4MmJmZTVkNGJlMzhkNTkzNzE5YTgzNDY2MGE2ZWM.

11:14:20.244 SIP.STACK MSG CSeq: 1 ACK

11:14:20.244 SIP.STACK MSG Content-Length: 0

11:14:20.245 SIP.STACK MSG

11:14:20.246 SIP.STACK MSG Found existing transaction for the request message.

11:14:20.248 SIP.STACK MSG Tx: UDP src=20.20.20.100:5060 dst=30.30.30.100:5060

11:14:20.248 SIP.STACK MSG CANCEL sip:4445556666@30.30.30.100:5060 SIP/2.0

11:14:20.248 SIP.STACK MSG From: "7778889999" <sip:7778889999@30.30.30.100:5060;transport=UDP>;tag=4dfae60-7f000001-13c4-3eae73-9d7a0fb8-3eae73

11:14:20.248 SIP.STACK MSG To: <sip:4445556666@30.30.30.100:5060>

11:14:20.249 SIP.STACK MSG Call-ID: 4e50e90-7f000001-13c4-3eae73-9f35e390-3eae73@30.30.30.100

11:14:20.249 SIP.STACK MSG CSeq: 1 CANCEL

11:14:20.249 SIP.STACK MSG Via: SIP/2.0/UDP 20.20.20.100:5060;branch=z9hG4bK-3eae73-f4d971c3-46af9c2b

11:14:20.249 SIP.STACK MSG Max-Forwards: 70

11:14:20.249 SIP.STACK MSG Supported: 100rel,replaces

11:14:20.250 SIP.STACK MSG Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER

11:14:20.250 SIP.STACK MSG User-Agent: ADTRAN_Total_Access_924e_2nd_Gen/R11.10.5.E

11:14:20.250 SIP.STACK MSG Content-Length: 0

11:14:20.250 SIP.STACK MSG

11:14:20.281 SIP.STACK MSG Rx: UDP src=30.30.30.100:5060 dst=20.20.20.100:5060

11:14:20.281 SIP.STACK MSG SIP/2.0 200 OK

11:14:20.281 SIP.STACK MSG Via: SIP/2.0/UDP 20.20.20.100:5060;branch=z9hG4bK-3eae73-f4d971c3-46af9c2b

11:14:20.281 SIP.STACK MSG From: "7778889999" <sip:7778889999@30.30.30.100:5060;transport=UDP>;tag=4dfae60-7f000001-13c4-3eae73-9d7a0fb8-3eae73

11:14:20.281 SIP.STACK MSG To: <sip:4445556666@30.30.30.100:5060>;tag=42411032-1484796830606

11:14:20.282 SIP.STACK MSG Call-ID: 4e50e90-7f000001-13c4-3eae73-9f35e390-3eae73@30.30.30.100

11:14:20.282 SIP.STACK MSG CSeq: 1 CANCEL

11:14:20.283 SIP.STACK MSG P-Charging-Vector: icid-value=qnhfe046ihb2jsg6e9ei3n46o9c0nq9ccbq6mfpek9e0jrk6k1l4drl0;icid-generated-at=30.30.30.100

11:14:20.283 SIP.STACK MSG

11:14:20.336 SIP.STACK MSG Rx: UDP src=30.30.30.100:5060 dst=20.20.20.100:5060

11:14:20.336 SIP.STACK MSG SIP/2.0 487 Request Terminated

11:14:20.336 SIP.STACK MSG From: "7778889999" <sip:7778889999@30.30.30.100:5060;transport=UDP>;tag=4dfae60-7f000001-13c4-3eae73-9d7a0fb8-3eae73

11:14:20.336 SIP.STACK MSG To: <sip:4445556666@30.30.30.100:5060>;tag=42411032-1484796830606

11:14:20.336 SIP.STACK MSG Call-ID: 4e50e90-7f000001-13c4-3eae73-9f35e390-3eae73@30.30.30.100

11:14:20.337 SIP.STACK MSG CSeq: 1 INVITE

11:14:20.337 SIP.STACK MSG Via: SIP/2.0/UDP 20.20.20.100:5060;branch=z9hG4bK-3eae73-f4d971c3-46af9c2b

11:14:20.337 SIP.STACK MSG Content-Length: 0

11:14:20.337 SIP.STACK MSG

11:14:20.339 SIP.STACK MSG Tx: UDP src=20.20.20.100:5060 dst=30.30.30.100:5060

11:14:20.340 SIP.STACK MSG ACK sip:4445556666@30.30.30.100:5060;transport=UDP SIP/2.0

11:14:20.340 SIP.STACK MSG From: "7778889999" <sip:7778889999@30.30.30.100:5060;transport=UDP>;tag=4dfae60-7f000001-13c4-3eae73-9d7a0fb8-3eae73

11:14:20.340 SIP.STACK MSG To: <sip:4445556666@30.30.30.100:5060>;tag=42411032-1484796830606

11:14:20.340 SIP.STACK MSG Call-ID: 4e50e90-7f000001-13c4-3eae73-9f35e390-3eae73@30.30.30.100

11:14:20.340 SIP.STACK MSG CSeq: 1 ACK

11:14:20.341 SIP.STACK MSG Via: SIP/2.0/UDP 20.20.20.100:5060;branch=z9hG4bK-3eae73-f4d971c3-46af9c2b

11:14:20.341 SIP.STACK MSG Max-Forwards: 70

11:14:20.341 SIP.STACK MSG Supported: 100rel,replaces

11:14:20.342 SIP.STACK MSG Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER

11:14:20.342 SIP.STACK MSG User-Agent: ADTRAN_Total_Access_924e_2nd_Gen/R11.10.5.E

11:14:20.342 SIP.STACK MSG Contact: <sip:7778889999@20.20.20.100:5060;transport=UDP>

11:14:20.342 SIP.STACK MSG Content-Length: 0

11:14:20.342 SIP.STACK MSG

And here are the relevant portions of the config:

interface eth 0/1

description Inside Interface

ip address 172.16.100.7 255.255.255.0

ip access-policy Private

media-gateway ip primary

no shutdown

!

interface eth 0/2

description To AT&T Router

ip address 20.20.20.100 255.255.255.248

ip access-policy Public

media-gateway ip primary

no shutdown

!

ip rtp media-anchoring

!

voice trunk T01 type sip

description "AT&T - Primary"

sip-server primary 12.194.99.181

!

voice trunk T04 type sip

description "3CX"

sip-server primary 172.16.100.6

grammar from host local

transfer-mode network

!

voice grouped-trunk AT&T

trunk T01

accept NXX-XXXX cost 0

accept 1-NXX-NXX-XXXX 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

accept 411 cost 0

accept 611 cost 0

accept 911 cost 0

accept NXX-NXX-XXXX cost 0

reject 976-XXXX

reject 1-900-NXX-XXXX

reject 1-976-NXX-XXXX

reject 1-NXX-976-XXXX

!

voice grouped-trunk 3CX

trunk T04

accept 77788899XX cost 0

jayh · ‎01-19-2017

Found it! It's a bug. Fixed in R11.10.6 (extended maintenance train).

From release notes here https://supportforums.adtran.com/docs/DOC-8304 page 13:

This section highlights the Voice specific bug fixes in products running AOS version R11.10.6.

• When running R11.10.5 or R12.2.0.SA, if inband call progress tones were presented on a SIP-to-SIP or a SIP-to-ISDN call, an unexpected 180 Ringing response without SDP was sent by the unit, which prevented the inband call progress tones from being heard.

Upgrade to R11.10.6 and you should be good.

View solution in original post

jayh · ‎01-19-2017

The 180 Ringing you're sending to the PBX has no SDP, and it looks like it is originated by the TA924 as there is no 180 Ringing received from the carrier and it gets sent 2 milliseconds after the 183 is received from the carrier.

Was that call example with either "ringback override" command on the trunk? Because you're getting SDP from the carrier on the 183 Session Progress you probably don't want ringback override configured. If they're sending SDP they're probably providing ringback.

If you want to provide local ringback, you should ensure that you've configured the correct set of tone files and set that up correctly.

What is the result of debug voice toneservices or debug voice verbose?

Curiously, the carrier never sends a 180 Ringing message. If you stay on the line and the call is answered, do you have two-way audio?

Anonymous · ‎01-19-2017

jayh thank you for your assistance. The example provided was without any ringback override commands in place.

If we stay on the call, we do get two-way audio.

We're in the middle of production and the debugs are extremely noisy right now. I'd need to wait until after-hours before I could provide a useful "deb voice verbose" log. When I run "deb voice toneservices" I only see logging from FXS ports and nothing from the SIP to SIP calls.

Since the carrier isn't providing 180 Ringing I will contact them. If you have any other thoughts on this I am open to suggestions. Thank you for your help!

jayh · ‎01-19-2017

The issue seems to be that the Adtran is sending 180 Ringing to the PBX on its own, and without SDP.

Note that at timestamp 11:14:11.598 it relays the 183 Session Progress with SDP correctly. This very likely has ringback provided by the carrier, as there is media in the SIP message. Then at 11:14:11.605 it sends the highlighted 180 Ringing to the PBX with no SDP or media. This is generated by the TA924 itself, not relayed from the carrier side. It's curious that it would do so without ringback override being configured.

This 180 Ringing without media is going to be interpreted by the PBX as superseding the 183 Session Progress so the PBX will no longer listen to the media described in the previous 183. If we can get the Adtran to stop sending the gratuitous 180, or to send it with locally-generated ringback media, that will fix it.

The carrier not sending a 180 Ringing isn't necessarily a deal-breaker. They are providing media with the 183 which is presumably ringback tone, but it could be an intercept or a "please wait" message. In any case, if we can get the TA924 to not send the gratuitous 180 with no media, that should fix it.

If you do get the carrier to send a 180 Ringing with SDP, that will probably also fix it as far as the customer is concerned, but it seems wrong that the TA924 is generating one on its own without media.

jayh · ‎01-19-2017

Found it! It's a bug. Fixed in R11.10.6 (extended maintenance train).

From release notes here https://supportforums.adtran.com/docs/DOC-8304 page 13:

This section highlights the Voice specific bug fixes in products running AOS version R11.10.6.

• When running R11.10.5 or R12.2.0.SA, if inband call progress tones were presented on a SIP-to-SIP or a SIP-to-ISDN call, an unexpected 180 Ringing response without SDP was sent by the unit, which prevented the inband call progress tones from being heard.

Upgrade to R11.10.6 and you should be good.

Anonymous · ‎01-19-2017

Good find! I'll upgrade the firmware and report back. Thank you!

Anonymous · ‎01-19-2017

The firmware update fixed the problem. Thank you!

Support
Community

No ringback on 924e acting as an SBC

SIP

Re: No ringback on 924e acting as an SBC

Re: No ringback on 924e acting as an SBC

Re: No ringback on 924e acting as an SBC

Re: No ringback on 924e acting as an SBC

Re: No ringback on 924e acting as an SBC

Re: No ringback on 924e acting as an SBC

Re: No ringback on 924e acting as an SBC

SupportCommunity

No ringback on 924e acting as an SBC

SIP

Re: No ringback on 924e acting as an SBC

Re: No ringback on 924e acting as an SBC

Re: No ringback on 924e acting as an SBC

Re: No ringback on 924e acting as an SBC

Re: No ringback on 924e acting as an SBC

Re: No ringback on 924e acting as an SBC

Re: No ringback on 924e acting as an SBC

Support
Community