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: 
rgausman
New Contributor
‎09-08-2019 09:20 PM

dtran 908e SIP to Adtran 908e SIP Trunk - 503 Service Unavailable error

dtran 908e SIP to  Adtran 908e SIP Trunk  -  503 Service Unavailable error

Overall Configuration

HQ: Avaya-G3-PBX <-DS1->   rtr-2pwc(Adtran908e)  <-eth0->  ()_tunnel_()  <-pwc-lan-eth0>  rtr-pwc(Adtran908e)  <-DS1-> Avaya-8300-Gateway  

From HQ dialing site 'PWC' extension get fast busy.  Debug on rtr-2pwc shows 'SIP/2.0 503 Service Unavailable'

Any idea what service is unavailable?

RTR-2PWC#

21:51:37 SIP.STACK MSG     Tx: UDP src=192.168.1.5:5060 dst=172.16.25.1:5060

21:51:37 SIP.STACK MSG         REGISTER sip:172.16.25.1:5060 SIP/2.0

21:51:37 SIP.STACK MSG         From: <sip:2@172.16.25.1:5060;transport=UDP>;tag=2f42850-ac130105-13c4-1ceb-4489aa36-1ceb

21:51:37 SIP.STACK MSG         To: <sip:2@172.16.25.1:5060;transport=UDP>

21:51:38 SIP.STACK MSG         Call-ID: 2fb55b0-ac130105-13c4-1ceb-1f2da08a-1ceb

21:51:38 SIP.STACK MSG         CSeq: 1 REGISTER

21:51:38 SIP.STACK MSG         Via: SIP/2.0/UDP 192.168.1.5:5060;branch=z9hG4bK-1ceb-70f9de-1d212c50

21:51:38 SIP.STACK MSG         Max-Forwards: 70

21:51:38 SIP.STACK MSG         Supported: 100rel,replaces

21:51:38 SIP.STACK MSG         Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER

21:51:38 SIP.STACK MSG         User-Agent: ADTRAN_Total_Access_908e/14.07.00.E

21:51:38 SIP.STACK MSG         Contact: <sip:2@192.168.1.5:5060>

21:51:38 SIP.STACK MSG         Expires: 3200

21:51:38 SIP.STACK MSG         Content-Length: 0

21:51:38 SIP.STACK MSG

21:51:38 SIP.STACK MSG     Rx: UDP src=172.16.25.1:5060 dst=192.168.1.5:5060

21:51:38 SIP.STACK MSG         SIP/2.0 200 OK

21:51:38 SIP.STACK MSG         From: <sip:2@172.16.25.1:5060;transport=UDP>;tag=2f42850-ac130105-13c4-1ceb-4489aa36-1ceb

21:51:38 SIP.STACK MSG         To: <sip:2@172.16.25.1:5060>;tag=2f42be0-c0a80a41-13c4-1db3-486a3837-1db3

21:51:38 SIP.STACK MSG         Call-ID: 2fb55b0-ac130105-13c4-1ceb-1f2da08a-1ceb

21:51:38 SIP.STACK MSG         CSeq: 1 REGISTER

21:51:38 SIP.STACK MSG         Contact: <sip:2@192.168.1.5:5060>

21:51:38 SIP.STACK MSG         Expires: 3200

21:51:38 SIP.STACK MSG         Via: SIP/2.0/UDP 192.168.1.5:5060;branch=z9hG4bK-1ceb-70f9de-1d212c50

21:51:38 SIP.STACK MSG         Supported: 100rel,replaces

21:51:38 SIP.STACK MSG         Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER

21:51:38 SIP.STACK MSG         User-Agent: ADTRAN_Total_Access_908e/14.07.00.E

21:51:38 SIP.STACK MSG         Content-Length: 0

21:51:38 SIP.STACK MSG

21:51:38 SIP.STACK MSG     Rx: UDP src=172.16.25.1:5060 dst=192.168.1.5:5060

21:51:38 SIP.STACK MSG         NOTIFY sip:2@192.168.1.5 SIP/2.0

21:51:38 SIP.STACK MSG         From: <sip:mwi@172.16.25.1>;tag=2f42da8-c0a80a41-13c4-1db3-4d7411cd-1db3

21:51:38 SIP.STACK MSG         To: <sip:2@172.16.25.1>

21:51:38 SIP.STACK MSG         Call-ID: 2f42da8-c0a80a41-13c4-1db3-7b3cf387-1db3@172.16.25.1

21:51:38 SIP.STACK MSG         CSeq: 1 NOTIFY

21:51:38 SIP.STACK MSG         Via: SIP/2.0/UDP 172.16.25.1:5060;branch=z9hG4bK-1db3-740692-6b2c70d2

21:51:38 SIP.STACK MSG         Event: message-summary

21:51:38 SIP.STACK MSG         Subscription-State: active

21:51:38 SIP.STACK MSG         Max-Forwards: 70

21:51:38 SIP.STACK MSG         Supported: 100rel,replaces

21:51:38 SIP.STACK MSG         Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER

21:51:38 SIP.STACK MSG         User-Agent: ADTRAN_Total_Access_908e/14.07.00.E

21:51:38 SIP.STACK MSG         Content-Type: application/simple-message-summary

21:51:38 SIP.STACK MSG         Content-Length: 42

21:51:38 SIP.STACK MSG

21:51:38 SIP.STACK MSG         Messages-Waiting: no

21:51:38 SIP.STACK MSG         Voice-Message: 0/0

21:51:38 SIP.STACK MSG

21:51:38 SIP.STACK MSG     Tx: UDP src=192.168.1.5:5060 dst=172.16.25.1:5060

21:51:38 SIP.STACK MSG         SIP/2.0 503 Service Unavailable

21:51:38 SIP.STACK MSG         From: <sip:mwi@172.16.25.1>;tag=2f42da8-c0a80a41-13c4-1db3-4d7411cd-1db3

21:51:38 SIP.STACK MSG         To: <sip:2@172.16.25.1>;tag=2f42a18-ac130105-13c4-1cec-6c0ee534-1cec

21:51:38 SIP.STACK MSG         Call-ID: 2f42da8-c0a80a41-13c4-1db3-7b3cf387-1db3@172.16.25.1

21:51:38 SIP.STACK MSG         CSeq: 1 NOTIFY

21:51:38 SIP.STACK MSG         Via: SIP/2.0/UDP 172.16.25.1:5060;branch=z9hG4bK-1db3-740692-6b2c70d2

21:51:38 SIP.STACK MSG         Supported: 100rel,replaces

21:51:38 SIP.STACK MSG         Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER

21:51:38 SIP.STACK MSG         User-Agent: ADTRAN_Total_Access_908e/14.07.00.E

21:51:38 SIP.STACK MSG         Content-Length: 0

21:51:38 SIP.STACK MSG

Thank you,

Bob g.

Labels (1)
Labels
0 Kudos
Reply
1 Reply
jayh
Honored Contributor
Honored Contributor
‎09-09-2019 03:58 PM

Re: dtran 908e SIP to Adtran 908e SIP Trunk - 503 Service Unavailable error

This 503 message is sent in response to a NOTIFY sent for message waiting to extension "2". I suspect that you don't actually have an extension with the single digit "2" hence service is unavailable. Odds are that the device on 172.16.25.1 is misconfigured and trying to set a message waiting indication to an invalid extension.

For a phone call, there should be a SIP INVITE message, and that doesn't appear in your debug. Are you sure that the other side is sending an INVITE to you when the call is initiated? Debugging sip stack messages on the sending end may be useful.

Can you post configurations with passwords, etc. redacted?

0 Kudos
Accept as Solution Reply