Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Solved Multiple SIP DID routing problem

Discussion in '3CX Phone System - General' started by mgb2, Nov 7, 2017.

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

    Joined:
    Aug 2, 2017
    Messages:
    12
    Likes Received:
    0
    I'm fairly new to 3CX and have been learning on the free license so we can do a full rollout later. I ordered a SIP DID from Vitelity, and have it working well with account-based authentication.

    In order to expand my testing, I added a second SIP DID. I want each DID to go to a different extension. I set and inbound rule for the second number, but it always follows the rule specified for the 'main' number.

    I have a suspicion that this may be a field mapping issue, but I'm not sure what needs to be changed. If I look at the logs, I don't actually see the DID number anywhere in the INVITE.

    Does anyone have any insight?
     
  2. mgb2

    Joined:
    Aug 2, 2017
    Messages:
    12
    Likes Received:
    0
    Solved! When I first set up Vitelity, I had some issues, and had set their routing to be a phone, rather than a PBX. I switched it specify PBX, and it's now sending the DID in the INVITE, and everything works!
     
  3. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    7,400
    Likes Received:
    535
    Glad the issue is resolved and thank you for sharing your solution. However please note that 3CX has tested and supports only IP based trunks from Vitelity and the template included in the PBX is constructed around Vitelity's IP based trunks
     
  4. mgb2

    Joined:
    Aug 2, 2017
    Messages:
    12
    Likes Received:
    0
    Thanks for the clarification. I'm new to SIP overall, and at some point that distinction wasn't clear to me.
     
Thread Status:
Not open for further replies.