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.

Same DID/inbound rule on two (or more) different gateways

Discussion in 'Ideas' started by echoinformatica, Nov 21, 2016.

Same DID/inbound rule on two (or more) different gateways 5 5 1votes
5/5, 1 vote

  1. echoinformatica

    Joined:
    Aug 8, 2016
    Messages:
    6
    Likes Received:
    8
    Hi,

    in case you have two gateways with identical DIDs such issue may arise indeed, which is related to identifying the source of the calls.
    What you could do however is to fake an extra digit infront of each DID presented by the second gateway, with a manipulation made at the gateway config file level.
    Actually this occurs because with gateways you don't have Source identification settings as in Trunks.
    With 2 trunks of same sip server you would apply source identification on one of the fields which provide something unique such as an authentication number.
    If there was a source identification section in the inbound parameters of the gateways you could have filtered on the gateway host/port variable in one of the fields as INVIT|E from gw1 vs gw2 have different host.

    Thanks.
     
  2. the60

    the60 New Member

    Joined:
    Oct 21, 2011
    Messages:
    117
    Likes Received:
    61
    We experienced big problems when setting up our provider's backup trunk IPs in 3CX. Our provider gives us multiple IPs to peer with, for origination & termination. 3CX does not inherently handle this very well.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...