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.

 

[SteveITS]

What about hot desking, if the user switches to a different extension?

 

[Janwillem Ronken]

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 there any update on when exactly? We really need this as we handle calls for multiple companies and when dialling out we need to present a different caller id. The only reason we are still on our old system for the majority of the calls is this.. while payin already some years for 3CX.
A realistic estimated date would be highly appreciated.

 

[TALKTELECOM]

Good Morning,

Do we know anything about this implementation in 3CX? Is that I have a client (Call Center) with 89 DIDs and I configured the exit rules as some partner indicated by the forum, but I don't know why from time to time (about 8-10 calls from a total of 60) go out by main number So if this keeps happening to me I cannot keep the configuration of that by dialing a prefix, exit by a specific trunk if sometimes it does not work.
The customer is waiting for us to solve this issue that is very bad for them, and thus be able to continue expanding the 96-Channel Enterprise switchboard that it currently has.

I would appreciate a response from a rough forecast please.

Thanks and best regards.

 

[bbaker73]

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.

Precisely what I was thinking.

An emergency services caller id setting in the extension is necessary. We already use multiple trunks for outbound calls to display the correct area code/DID caller ID when dialing a specific area code as we work in multiple areas so we cannot use the extension caller ID as that overrides the caller ID on the trunk settings (which it should).

We have tons of remote desk phone users. If I am to make 911 address accurate for each one, I need a DID for each one with the correct address, that doesn't go to a queue, be able to set emergency caller id in the extension to this DID, then just add those DID's to one trunk with the correct address at the trunk provider on the DID, add inbound DID rule for each one in case 911 returns the call so it doesn't go to queue etc. As long as all of the emergency DID's for all extensions are on one trunk then I'd just need one rule for emergency numbers to go out this trunk route.

As I see it now, to accomplish this, I'll need a new trunk and new DID (ELIN) for every remote extension that has a unique ERL, with the DID (ELIN) for that extension set as the trunk caller ID, then add an emergency number rule for each and every extension going out on their unique trunk so the correct CID is displayed for the extensions DID. A daunting task adding more room for human error and more to keep track of.

 

[Hystiff]

+1 !
From Avaya to 3CX we lost this feature, quite incredible ^^

 

[phil.wade]

I'm wasting $42 every month having extra trunks, as that is the only solution for my situation.

 

[M.B.]

Hi,
we're actually setting up a 3CX for our Call Center. We need to dial out with more than 120 different caller ids (different customers). Today i wanted to set it up but realized that it's a big problem. So sad, that members are asking for this feature since years and nothing happens.

 

[Voipuser07]

I'm wasting $42 every month having extra trunks, as that is the only solution for my situation.

Same here, i have to start wasting money for another trunk just for this. Don't know when this feature will be available.

Can anyone from 3CX please provide an update?

 

[Tim De Vos]

On 15 april 2016 3CX said:

Caller ID per outbound rule is in progress for V15 - this will allow much better flexibility. Note that some trunks will not accept certain caller IDS

On August 2 2017:

Better outbound call ID configuration is in progress

17 november 2018:

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.

We are now 27th of march 2020.

Who believes in planning? ;-)

 

[Charlito]

+1


3CX please reply

 

[PvK]

Hi, I am new to 3CX. We were used to this feature on the previous voip switch. I could select a function key to set the call ID. It basically added some digits to the dialed phone number.

In our case we have a voip provider, and can change the caller id on the fly by passing it in the call.

In the windows client, I can change the account, but this requires multiple clicks. And we can't to that from a desk phone, as far as I know.

We use different caller Id's in different situations, a bit like the Spanish regional numbers described a few years ago in this thread.

 

[Charlito]

+1

 

[PvK]

Hi, I am new to 3CX. We were used to this feature on the previous voip switch. I could select a function key to set the call ID. It basically added some digits to the dialed phone number.

In our case we have a voip provider, and can change the caller id on the fly by passing it in the call.

In the windows client, I can change the account, but this requires multiple clicks. And we can't to that from a desk phone, as far as I know.

We use different caller Id's in different situations, a bit like the Spanish regional numbers described a few years ago in this thread.

I was able to solve my problem by configuring multiple extensions, and configure these on the phone. In contrast to the web client, I can easily switch between accounts on the desk phone. Now I just need to find out how to set the account in a speed dial function button.

 

[cobaltit]

I'm wasting $42 every month having extra trunks, as that is the only solution for my situation.

Switch providers? If you have IP authenticated trunks it shouldn't cost you anything for this. While we do registration-based trunks for most installs we also offer IP authentication for use cases like this.

 

[VoIPTools]

I posted earlier in this thread, so perhaps this is spamming...

But regarding PvK's need, you should look at our Caller ID tool. It has expanded some since it's original release. Now managers can restrict the numbers an agent can choose from based on group (For example, no point showing UK phone numbers to USA agents). Or, rather than selecting a specific phone number from a predefined list, you can simply type in an add-hoc number.

Also, you can give a description to the numbers and select by name rather than the actual number. That way you don't need to memorize which number goes with each location or customer. You simply select the name. For example "Sacramento, California" or "West-Side Franchise".

To expand the discussion further, in response to the idea of setting the caller ID by looking at the number dialed, this is only a partial solution when you consider number portability. My cell has a Wisconsin phone number, but I live in Utah. If the number that shows up on my cell is from out of state, I know right away it's a spam call and I reject the call and block the number... worse that gets reported to my carrier so not only do I block the number from my phone, it leads to everyone on that carrier blocking the number.

It is true, most businesses are going to have a local number, but that is less true for residential contacts. In my opinion, getting the caller ID set to the correct number should be (when possible) based on the contact's address and not assume their phone number matches their location.

So, if you are dialing from your CRM, (for example using our VoIPTools REST API), your code should be looking at the contacts address to decide what Caller ID to use rather than matching based on the phone number. Or have a human make the decision.

 

[Charlito]

Would it be possible to make the caller id selectable by outbound rule like in the Emergency numbers list?

 

[VoIPTools]

You can change the caller ID PRIOR to placing the call. Unfortunately when you initiate the call, the caller ID is already in the SIP invite, so it is too late to change the caller ID after the call is initiated.

 

[Charlito]

3CX can place the caller id in the sip invite to the provider.
so it is possible to use the caller id that is in place in the outboundrule instead of the callerid from the extension

 

[VoIPTools]

To be more precise with my answer, 3CX can override the caller ID for their purposes, but as far as I know there is no API to override the caller ID other than what I have described above.

 

[darthvader167]

I need to be able to choose what DID to call out on by choosing a specific prefix. This should be an implemented feature.