New SIP Trunk, New Issues!

Discussion in '3CX Phone System - General' started by olivermsubadra, Mar 30, 2016.

Thread Status:
Not open for further replies.
  1. olivermsubadra

    Joined:
    Feb 18, 2016
    Messages:
    33
    Likes Received:
    0
    Hi,

    We've recently switched SIP providers, from sipgate to Southern Comms. The only thing we've changed is the SIP trunk, and now no external calls work. Here are some (I hope) useful details:

    - We're using v14 of the phone system.
    - Our new SIP trunk is 'green' and our provider says it's fully operational.
    - tartarus.tipicall.net (with the IP '91.146.112.10') new SIP server hostname.
    - The new SIP provider does not use an authentication ID or password.
    - The firewall checker says all of the ports have been configured correctly.
    - I've tried out all of the available codecs.
    - The '603 Declined/INVITE' message is returned for both in and outbound calls (example outbound call below):

    Code:
    30-Mar-2016 10:12:54.993   Call to T:Line:10000>>01296******@[Dev:sip:tartarus.tipicall.net:5060] from L:24.1[Extn] failed, cause: Cause: 603 Declined/INVITE from 91.146.112.10:5060
    30-Mar-2016 10:12:54.990   [CM503003]: Call(C:24): Call to <sip:01296*****@tartarus.tipicall.net:5060> has failed; Cause: 603 Declined/INVITE from 91.146.112.10:5060
    30-Mar-2016 10:12:54.852   Call to T:Line:10000>>01296*****@[Dev:sip:tartarus.tipicall.net:5060] from L:24.1[Extn] failed, cause: Cause: 603 Declined/INVITE from 91.146.112.10:5060
    30-Mar-2016 10:12:54.849   [CM503003]: Call(C:24): Call to <sip:01296******@tartarus.tipicall.net:5060> has failed; Cause: 603 Declined/INVITE from 91.146.112.10:5060
    30-Mar-2016 10:12:54.713   Call to T:Line:10000>>01296*****@[Dev:sip:tartarus.tipicall.net:5060] from L:24.1[Extn] failed, cause: Cause: 603 Declined/INVITE from 91.146.112.10:5060
    30-Mar-2016 10:12:54.710   [CM503003]: Call(C:24): Call to <sip:01296*****@tartarus.tipicall.net:5060> has failed; Cause: 603 Declined/INVITE from 91.146.112.10:5060
    (I might be misremembering, but I seem to recall that the FDQN used to be displayed in the log with our old trunk, not the SIP name ... why would this change?)

    EDIT: To add to the confusion, it transpires that the calls are connecting to our old sip trunk, not our new one. ... How? We left no trace of our old trunk in the PBX, and switched over to the new trunk about a week ago.
     
  2. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,061
    Likes Received:
    56
    Not sure that there is enough info to show about connecting to old provider as I only see outbound calls to new. Can you elaborate? Your info does not show any inbound calls, so I assume you dial the number and do not get thru, but what happens?

    You may want to completely reboot the system and see if the issue resolves itself. You may also want to review the advanced settings or troubleshooting parameters (depending on version) and see if any remnants exist of old or other readily identifiable issue show up and need changing.

    From what I can see in the log, the provider is rejecting the call and you may need to call them and have them trace a call so they can advise what it is that they do not like.

    A wireshark may provide more detail.
     
  3. NickD_3CX

    NickD_3CX Support Team
    Staff Member 3CX Support

    Joined:
    Jun 2, 2014
    Messages:
    1,253
    Likes Received:
    63
    The part "603 Declined/INVITE from 91.146.112.10:5060" in the following line implies that an attempt to make a call from the PBX was made and the SIP Server of the Provider did reply back with 603.

    Code:
    30-Mar-2016 10:12:54.849   [CM503003]: Call(C:24): Call to <sip:01296******@tartarus.tipicall.net:5060> has failed; Cause: 603 Declined/INVITE from 91.146.112.10:5060
    Generally I would recommend giving your Provider and asking them why they are replying with 603. Their take on the issue might provide insight for something that may be wrong as far as the settings go.
    Could it be that the number porting has not yet completed?
     
Thread Status:
Not open for further replies.