Changing Outbound CID based on number dialed.

[MHRAdmin]

Is there any way to do this?
I would like to for instance:
Call goes out to a local customer in area code 616.
System sees that the call is going out to 616 and changes the OCID to 6165551234

I see the principles at "https://www.3cx.com/docs/cid-reformatting/", but it only makes brief mention of outbound CID.
It says "Outbound Caller ID reformatting requires the use of the “OriginatorCallerID” to be active in the SIP Trunk “Outbound Parameters” settings."

It appears to be active.... all over the place. Which field is it saying i need to change to “OriginatorCallerID”?
When I open up my "Outbound Parameters", this is what I see...........

 

[cobaltit]

That's a question for your carrier as far as which field they expect the CID in. If you are using a 3CX approved provider (and template) then this is already configured for you. What's stopping you from just testing it?

 

[MHRAdmin]

That's a question for your carrier as far as which field they expect the CID in. If you are using a 3CX approved provider (and template) then this is already configured for you. What's stopping you from just testing it?

I cannot find any screen that allows Outbound CID configuration. Could you show me a screenshot of WHERE I would set this up?

 

[cobaltit]

Besides the one in the guide you already linked?




But realistically you'll want to setup multiple trunks and force the outbound CID there and then use outbound rules to match the outgoing call to the appropriate trunk. Or @voiptoys has a call center app that will let you choose your CID at the time of the call.

 

[MHRAdmin]

I I believe you might be onto something with forcing calls out different trunks. If all the trunks are coming from the same provider they wont have issues with routing?

 

[Evolute IT]

I I believe you might be onto something with forcing calls out different trunks. If all the trunks are coming from the same provider they wont have issues with routing?

They might. Depends on the provider and if Call Source Identification is used. You might need to play with some params to make it work.

The issue I had was the DID was in multiple trunks (register based) so 3CX had a hard time finding where the calls came from.

 

[cmp1]

voxtelesys has a Dynamic CID product I use in my dialer application, and last I remember seeing they had some mention that it worked with 3cx as well.

https://www.voxtelesys.com/blog/3cx-dynamic-caller-id/

 

[leejor]

This has been around for (almost) 2 years, and "In Progress" for not much less.

https://www.3cx.com/community/threads/ability-to-set-a-caller-id-for-outbound-calls.42840/page-5

 

[cobaltit]

If your provider will do IP authenticated trunks that's usually the easiest path.

 

[MHRAdmin]

They might. Depends on the provider and if Call Source Identification is used. You might need to play with some params to make it work.

The issue I had was the DID was in multiple trunks (register based) so 3CX had a hard time finding where the calls came from.

I talked to Vitelity. They said there should be no problem connecting all the DIDs as trunks if I chose to do so. However, still no way to change the outbound CID from the phone......

The example I listed above was a basic example of what we want to accomplish. Basically we have multiple branches of our company that need to show up. And the CSRs call all of them. Much like a call center but with MUCH less call volume.

in our previous system the CSRs could punch in a 3 digit code or hit a BLF to change their outbound CID to match the branch they are representing.

 

[MHRAdmin]

voxtelesys has a Dynamic CID product I use in my dialer application, and last I remember seeing they had some mention that it worked with 3cx as well.

https://www.voxtelesys.com/blog/3cx-dynamic-caller-id/

Do they require you to purchase your SIP Trunks through them?