503 system unavailable message

Discussion in 'General' started by thorpe5278, Oct 19, 2010.

  1. thorpe5278

    Joined:
    Jan 10, 2010
    Messages:
    50
    Likes Received:
    0
    We are using Verizon as our SIP provider on a private MPLS network. We have to certify Asterisk/Elastix with Verizon to do that we have to run several tests. One of the test is to have an inbound route going to a phone that is not registered (like the phone is unplugged etc.) make a call to that number from outside and use WireShark to capture the call. When phone is not registered and I call that number Asterisk returns a 503 system unavailable message back to the provider (Verizon).
    Verizon is telling me that the 503 message is not correct and that is should be sending a 40x code. They say the 503 code is a code for the entire system being down.
    Have any of you ran into this problem or have a way I can change the error code Asterisk sends?
     
  2. thorpe5278

    Joined:
    Jan 10, 2010
    Messages:
    50
    Likes Received:
    0
    Well got some help and figured out my own problem in case anyone ever runs into the same issue

    If we see this part of the capture:

    SSASTERISK01*CLI>
    -- Executing [s@macro-exten-vm:15] NoOp("SIP/VerizonSIP-0003fcaf", "Voicemail is novm") in new stack SSASTERISK01*CLI>
    -- Executing [s@macro-exten-vm:16] GotoIf("SIP/VerizonSIP-0003fcaf", "1?s-CHANUNAVAIL|1") in new stack SSASTERISK01*CLI>
    -- Goto (macro-exten-vm,s-CHANUNAVAIL,1) SSASTERISK01*CLI>
    -- Executing [s-CHANUNAVAIL@macro-exten-vm:1] NoOp("SIP/VerizonSIP-0003fcaf", "IVR_RETVM: IVR_CONTEXT: ") in new stack
    -- Executing [s-CHANUNAVAIL@macro-exten-vm:2] GotoIf("SIP/VerizonSIP-0003fcaf", "0?exit|1") in new stack
    -- Executing [s-CHANUNAVAIL@macro-exten-vm:3] PlayTones("SIP/VerizonSIP-0003fcaf", "congestion") in new stack
    -- Executing [s-CHANUNAVAIL@macro-exten-vm:4] Congestion("SIP/VerizonSIP-0003fcaf", "10") in new stack SSASTERISK01*CLI>
    <--- Reliably Transmitting (no NAT) to 172.30.218.49:5162 ---> SIP/2.0 503 Service Unavailable
    Via: SIP/2.0/UDP 172.30.218.49:5162;br

    We can notice that the last application that Asterisk ran before it send the "503 Service Unavailable" is "congestion". This application is the reason that Asterisk sends 503.

    In order to fix this issue please modify macro "macro-exten-vm" (In your dialplan) and change "congestion" for "HangUp(1)". According to the rfc3398 (http://www.ietf.org/rfc/rfc3398.txt - page 24) HangUp(1) should send a "404 Not found"
     

Share This Page