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.

Certain features need to be with Trunk instead of global

Discussion in 'Ideas' started by slilie, Feb 13, 2017.

Certain features need to be with Trunk instead of global 5 5 1votes
5/5, 1 vote

  1. slilie

    Joined:
    Oct 26, 2016
    Messages:
    2
    Likes Received:
    2
    We run one PBX for all our European sites. We have one or more SIP trunks per site. Users are assigned to groups according to their main site. There are certain features that in 3CX are handled globally but should be part of the SIP Trunk configuration.
    1. E164 conversion - this feature needs to be SIP trunk specific as you'll have to determine the country the call is originating from
    2. Operator - the voice mail standard message states "or press star for an operator". You can only configure one (1) global operator per site.
    3. Outbound caller ID - different trunk providers need different Outbound caller ID's. I know there is a rule engine at SIP trunk level to generate this according to the needs. This is quite complicated. Consider having a field at extension lever where you can see or even set what outbound caller ID is sent per trunk
     
    OUTsider likes this.
  2. OUTsider

    Joined:
    Sep 25, 2012
    Messages:
    11
    Likes Received:
    2
    Option 1: Yes, indeed, especially if you have trunks in multiple countries, now you need to actually turn of E164 processing globally and do a lot of Outbound Rules in order to get this 'organized'.

    Option 3: Perhaps, IF that should change, then you should be able to edit this in the Extension setting, e.g. if you assign a DID to the account, then use that DID as callerid for the specified DID trunk.