Problem with call error 503 or NAT/ALG

Discussion in '3CX Phone System - General' started by sebastian_rojas, Jan 16, 2017.

Tags:
Thread Status:
Not open for further replies.
  1. sebastian_rojas

    Joined:
    Jan 16, 2017
    Messages:
    5
    Likes Received:
    0
    Hello!

    i'm looking to discover what a heck is going on with this, because i have implemented 3cx
    in other customer and just fine, but now i installed in a new customer, but i'm getting this error

    so i understand that failed because 503 Service Unavailable/INVITE
    of the voip gateway, reading the mediatrix gateway it says that could be the SDP options,
    but in the last part it says that it NAT/ALG check:L:86.1[Extn:119] REQUEST 'INVITE'



    16-ene-2017 16:43:39.663 Leg L:86.1[Extn:119] is terminated: Cause: BYE from PBX
    16-ene-2017 16:43:39.612 [CM503020]: Call(C:86): Normal call termination. Call originator: Extn:119. Reason: Server Failure
    16-ene-2017 16:43:39.612 L:86.1[Extn:119] failed to reach Line:90001>>990930064, reason Server Failure
    16-ene-2017 16:43:39.611 Leg L:86.2[Line:90001>>990930064] is terminated: Cause: 503 Service Unavailable/INVITE from 130.0.10.70:5060
    16-ene-2017 16:43:39.611 Call to T:Line:90001>>990930064@[Dev:sip:90001@130.0.10.70:5060;transport=udp] from L:86.1[Extn:119] failed, cause: Cause: 503 Service Unavailable/INVITE from 130.0.10.70:5060
    16-ene-2017 16:43:39.606 [CM503003]: Call(C:86): Call to <sip:990930064@130.0.10.70:5060> has failed; Cause: 503 Service Unavailable/INVITE from 130.0.10.70:5060
    16-ene-2017 16:43:39.478 [CM503025]: Call(C:86): Calling T:Line:90001>>990930064@[Dev:sip:90001@130.0.10.70:5060;transport=udp] for L:86.1[Extn:119]
    16-ene-2017 16:43:39.471 [CM503027]: Call(C:86): From: Extn:119 ("gustavo vilsaint" <sip:119@130.0.10.83:5060>) to T:Line:90001>>990930064@[Dev:sip:90001@130.0.10.70:5060;transport=udp]
    16-ene-2017 16:43:39.471 [CM503004]: Call(C:86): Route 1: from L:86.1[Extn:119] to T:Line:90001>>990930064@[Dev:sip:90001@130.0.10.70:5060;transport=udp]
    16-ene-2017 16:43:39.471 Line limit check: Current # of calls for line Lc:90001(@mediatrix[<sip:90001@130.0.10.70:5060>]) is 0; limit is 1
    16-ene-2017 16:43:39.470 Call(C:86): Call from Extn:119 to 990930064 matches outbound rule 'Rule for mediatrix'
    16-ene-2017 16:43:39.468 [CM503001]: Call(C:86): Incoming call from Extn:119 to <sip:990930064@130.0.10.83:5060>
    16-ene-2017 16:43:39.468 NAT/ALG check:L:86.1[Extn:119] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop
    SIP contact header is not equal to the SIP packet source(IP:port):
    Contact address:130.0.10.63:59758
    Received from :130.0.10.63:59766



    Best Regards
     
  2. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    5,486
    Likes Received:
    357
    Hello @sebastian_rojas

    Please navigate to trunks, edit your gateway and make sure that under options allow inbound and allow outbound calls is enabled.
     
  3. sebastian_rojas

    Joined:
    Jan 16, 2017
    Messages:
    5
    Likes Received:
    0
    Hello,
    i verify the trunk and it was enabled, but in the section of the : SIP trunk capabilities
    the option of
    re-invite: disable
    replaces: disable
    require registration for: in and outgoing calls

    Should i enable that option for re-invite?


    Best Regards
     

    Attached Files:

    • c1.PNG
      c1.PNG
      File size:
      27.3 KB
      Views:
      19
    • c2.PNG
      c2.PNG
      File size:
      35.6 KB
      Views:
      16
  4. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    5,486
    Likes Received:
    357
    Is you whole installation full public? PBX, phones, gateway? As i understand it the service unavailable comes from 130.0.10.70 which is the gateway, the pbx sends the call out as it should. Also from the screenshots your config seems correct so i would focus on the gateway side.
     
  5. sebastian_rojas

    Joined:
    Jan 16, 2017
    Messages:
    5
    Likes Received:
    0
    thanks a lot men, no in this business, they have this public range of ip address as a private range
    they are not using RFC1918, that is the reason both device are in the same vlan

    from the voip gw i receive this info, so i believe it's a type of configuration on that side
    thanks for your help, i will continue to verifying the problem




    best regards
     

    Attached Files:

    • c1.PNG
      c1.PNG
      File size:
      26 KB
      Views:
      17
  6. sebastian_rojas

    Joined:
    Jan 16, 2017
    Messages:
    5
    Likes Received:
    0
    hello, i finally get the asnwer, thanks a lot for your help
    Best Regards
     
Thread Status:
Not open for further replies.