Solved Outbound Caller ID remapping

[Molan21]

Is it possible to remap the outbound caller ID when a specific number is dialed.

We are an IT support group with a Toll Free DID - There is a software vendor we have contracts with and frequently need to call they also use a Toll Free DID. except there Toll Free number won't accept calls from other toll free numbers.

When we dial their number I would like to present our local DID so the call will complete. For all other calls we still need to present our toll free number as the caller ID

Thanks

 

[craigreilly]

Who is the provider? Do they allow multiple registrations?
Currently can not set Caller ID based on outbound rule...
but using multiple registrations to provider may work . ie: 1 IP based and 1 Password based.

 

[VoIPTools]

Once again Craigreilly has beaten me to the punch. The only out-of-the-box way of dynamically changing your outbound caller ID is by directing the desired call out the SIP trunk configured with the correct caller ID. Your outbound rules can route the call based on the number dialed (in this case) out the correct trunk... but your SIP carrier must allow multiple registrations (set up the same SIP connection twice).

As an alternative, you could take a look at our "3CX Caller ID" add-on which allows the end user to easily change their outbound caller ID on the fly.

 

[Molan21]

I use voip.ms I could easily create a second SUB account and register a 2nd Trunk through the provider if that is the solution.

Thanks

 

[Molan21]

Setting up a second SIP trunk under my provider with a different outbound caller ID and then using an outbound rule for the phone number to route it via the 2nd sip trunk worked

Thanks for the suggestion

 

[YiannisH_3CX]

Hello @Molan21

Glad to see the issue has been resolved however since Voip.ms has a static SI that means that you can use only one account. If you register more than one account of the same trunk you may have source identification issues with inbound calls so run a few tests with inbound calls to make sure everything routes correctly. https://www.3cx.com/partners/sip-trunks/canada/

 

[Molan21]

Sorry I am unsure what SI stands for but it seems you are correct. While the change did do what I wanted on outbound my inbound routing no longer worked correctly on the 3cx side. The calls came through from VOIP.ms and into my 3cx but no longer routed according to my rules.

 

[YiannisH_3CX]

SI stands for source identification. Regarding the inbound calls issue try the following:
Read our Voip.ms guide and make sure that your DIDs are in the correct format and only included in one trunk. Then navigate to trunk settings / Inbound parameters and under the Call Source Identification section and also enable the "Use both "Call Source Identification" rules and "Caller Number/Name -> CalledNum" field mappings (Note: Disables catch all routing capability)" option.

See if that works for you