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.

Outbound Caller ID override in outbound rules

Discussion in 'Ideas' started by the60, May 1, 2017.

Outbound Caller ID override in outbound rules 5 5 7votes
5/5, 7 votes

  1. the60

    the60 New Member

    Joined:
    Oct 21, 2011
    Messages:
    117
    Likes Received:
    61
    Please consider adding a field to the outbound rules that allows the ability to override the default outbound caller ID based on an entry in the outbound rules.

    Currently, if a company wants to set up multiple entities on a 3CX box, we need to set up a separate trunk for each entity, and then modify the trunk's "Remote Party ID - Calling Party : User Part" parameter to reflect the caller ID of the entity. then, we need to create a special outbound rule, such as "calls with starting prefix 000" to use the alternate trunk.

    Having multiple trunks to the same provider can be tricky, especially when they are IP based. Inbound calls can get confusing to 3CX, and a great deal of extra care need to be applied.

    Having this option built in to the outbound rules just makes plain sense.

    Thanks!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    thinvox and jed like this.
  2. craigreilly

    craigreilly Well-Known Member

    Joined:
    Feb 1, 2012
    Messages:
    3,575
    Likes Received:
    303
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. confidence

    Joined:
    Jan 2, 2013
    Messages:
    1
    Likes Received:
    0
    This is an essential feature that is missing. If the trunk supports multiple DIDs which it does, then why can't we expose these for outbound caller IDs in outbound rules?
     
  4. the60

    the60 New Member

    Joined:
    Oct 21, 2011
    Messages:
    117
    Likes Received:
    61
    1. set up a separate outbound trunk with the same provider (assuming it's IP-based and not registration-based).
    2. In the trunk, set the caller ID to be the alternate caller ID you want.
    3. Set up an outbound rule that captures calls made with a prefix of "xxx" (i.e., "123")
    4. when the rule sees the dialed number that has a length of 13 (10 digits plus the "123" prefix), strip the first 3 digits and route the call via the alternate trunk.
    There's also a 3rd-party app to facilitate this via a simple web interface.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. voiptoys

    voiptoys Active Member

    Joined:
    Feb 13, 2013
    Messages:
    893
    Likes Received:
    154
    No doubt this would be a nice enhancement, and I understand it is being looked at by 3CX. Thanks the60 for mentioning our tool (https://www.VoIPTools.com) for manipulating the outbound caller ID. Our tool does help with this issue when you want to select from a list of caller IDs, and avoids the hassle of setting up multiple trunks, but if you have just a few entities to switch between, an outbound rule setting might be easier for customers.

    I pondered whether a CFD app could be another approach. It too would eliminate the need for multiple trunks. For example, you dial "8" for the CFD extension (we can make single digit extensions with the Call Control API), it says "For company A press 1, for company B press 2, for company C press 3, then the CFD places the call with the correct Caller ID. You could also have a shortcut option where you dial "8", wait for the beep, then press <entity number> ** <phone number> and it places the call for you. This doesn't sound much better than just dialing the prefix, but it would eliminate the need for multiple trunks.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    accentlogic likes this.