Implemented Ability to set a Caller ID for Outbound Calls

[craigreilly]

Ability to set my Caller ID for Outbound Calls, specifically for calls to 911.

Right now, I can not program any DID's except the main number as an Outbound Caller ID in case of circumstances to call 911.

 

[malex]

Any updates, Nick?

 

[Jeffrey Gerlings]

+1

 

[dandenson]

+1, really needing this feature. I'm getting numerous requests for specific outbound numbers and it's a real hassle to do this via multiple trunks.

 

[Osney Santos]

+1

 

[Nick W]

Had this requested today. Specifically a call centre with need for agents set Caller ID, or better yet a set of outbound rules that can change the callerid.

From looking a few posts back it seems that this may be with us very soon. Would it be fair to say withing 3 months? (I need to give the customer something)

 

[Evolute IT]

This is something in the pipeline and will not be done for initial version v16 but in an update soon after. Its not long now, a few more months approximately.

Is this to be included in Update 2 or more for U3?

 

[craigreilly]

And now with some new/enhanced 911/Emergency Services rules - this probably needs more work.
Perhaps a Main outbound Caller ID and an Emergency Services Caller ID for every extension.

 

[mkubitza]

+1
Call-Center Basic Feature

 

[JimmyUK]

+1

 

[Bastien Flament]

And now with some new/enhanced 911/Emergency Services rules - this probably needs more work.
Perhaps a Main outbound Caller ID and an Emergency Services Caller ID for every extension.

This!

 

[hyperscale]

+1

This is often requested by call centers.

Prospects will often call it "CallerID proximity matching / Dynamic CallerID" where the outbound callerID will need to be changed depending on the area where the call campaign is targeted.

Ideally it could be done through an API allowing the query and update of the effective outbound caller ID (name and number) of an agent's extension.
Other ideas is to also allow the update of the extension's outbound callerID via either the webclient or the standard 3CX client.

Sure it is going beyond the current feature focus, but a full-fledged official external REST API for phone/extension provisioning as well as call control would be awesome.

 

[FS_Mathieu]

+1

 

[604]

+1

 

[urofi]

+1

why is this not implemented yet?

 

[revilo951]

Any news on this one?

 

[seantp]

Last November it was "a few more months". In a little over a month it will have been a year since that statement was made. I want to love 3CX and sell it to everyone, but I keep on running into client requirements where 3CX falls short. The logic to change CID is already in the system, how hard is it to add rule-sets that would allow us to have this ability?

 

[Evolute IT]

Last November it was "a few more months". In a little over a month it will have been a year since that statement was made. I want to love 3CX and sell it to everyone, but I keep on running into client requirements where 3CX falls short. The logic to change CID is already in the system, how hard is it to add rule-sets that would allow us to have this ability?

That ruleset should include the CNAM too.

Right now I need 2 trunks simply to change the Caller ID Name depending on the number.

 

[fa1]

This is just another crazy limitation of what would be an amazing platform. We push 3CX all the time, but it seems every time I post here it's because a promised feature hasn't been delivered in a timely manner. This request is over 2 years old, and is hardly the only important feature that has been promised and not delivered.

We have since given up on pushing 3CX for call centre deployments as we have been stuck telling clients "it's coming, it's coming" only to be left with egg on our faces.

 

[bbredewold]

We now have 5 trunks to resolve this issue... When this is implemented we can go back to 1...
It would be great if 3CX exposes some kind of timeline with features to be released...

 

[Itel628]

+1