Implemented Ability to set a Caller ID for Outbound Calls

craigreilly

Free User
Joined
Feb 1, 2012
Messages
4,134
Reaction score
577
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.
 
Upvote 194
Although promised,I think we will not see this in 15.X The focus is clearly on other things since we have not heard anything for a long time. It is marked as "in progress" for 2 years now and in SP5 they missed the opportunity when they introduced this for only Emergency (911) numbers.
 
  • Like
Reactions: converging1
I need this so much!!! Please 3CX, please!?!?
 
  • Like
Reactions: converging1
Having this feature would make our deployment much more efficient.

We do e911 for the specific office/room/building. With over 500 unique e911 DIDs to manage, it was disappointing to learn emergency CID was not configurable for each extension.
 
It's honestly insane that this isn't basic functionality.

Outbound rules need a setting for Caller ID so we can change the CID dynamically based on a prefix.
 
  • Like
Reactions: converging1
Please, please and please!
Need that badly.
 
  • Like
Reactions: converging1
I'm a brand new 3CX customer and I'm having a hard time figuring out how a request as important, and as I see it, simple, can be taking so long in development. I see the primary use for this as emergency dialing but I see dozens of other possible uses.

As many have mentioned before, I want each extension to have its DID number as its CID, but when calling 911 I want the main company number. I've read a bunch of kluge workarounds, from paying $3 additional for every DID number to put E911 on them, purchasing an additional trunk for 911, some type of loopback trunking scheme. All sound too expensive or too complicated.

As I mentioned I'm brand new to 3CX, I'm on 15.5, I think it's SP6 because the version ends in .6. When setting up a trunk there is a Caller ID tab where you can apply inbound and outbound caller ID rewrite rules.

Couldn't this request be as simple as adding the exact same functionality to inbound and outbound rules. So on my 911 outbound rule I would put (.*) replace with 1234567800? If you wanted several different 911 replacements you would create several 911 outbound rules, each assigned to a "Group" of extensions, with whatever 911 CID you need for that group.

You could do the same thing if you were calling on a specific customer and you wanted to be one company and if you were calling on a different customer and wanted to be a different company. Just create two or more outbound rules that apply to the destination you are calling with a caller ID rewrite.

I'm hoping our business will someday grow to the point where we need more than 16 SIM calls and we'll be a license paying customer. But I'm not sure if I want to be paying for a system that can't manage something basic like this. How can the long list of customers (American Express, Pepsi, Mitsubishi, Boeing, Harley-Davidson, etc) be dealing with this? At a prior employer where I managed telephony we had over 1500 employees on 8 floors of two different Chicago hi-rise buildings. Our 911 setup was extremely complex as we needed to identify which building, floor and quadrant each employee was located in with over 30 different E911 numbers, all at the same time as each employee sending their DID as their normal caller ID.
 
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.
 
Thanks for replying Nick. It's nice to see it back on the planning. Looking forward to it.
 
  • Like
Reactions: converging1
I'm a brand new 3CX customer and I'm having a hard time figuring out how a request as important, and as I see it, simple, can be taking so long in development. I see the primary use for this as emergency dialing but I see dozens of other possible uses.

As many have mentioned before, I want each extension to have its DID number as its CID, but when calling 911 I want the main company number. I've read a bunch of kluge workarounds, from paying $3 additional for every DID number to put E911 on them, purchasing an additional trunk for 911, some type of loopback trunking scheme. All sound too expensive or too complicated...

We decided adding a second trunk for e911 was worth it so we have a secondary provider on all systems for outgoing calls that is used for e911 and the trunk forces the 911 CID. A couple bucks a month per site. Yes, it adds some complexity and takes time to setup, but even if they add the 911 override for CID we'll continue adding a backup trunk.
 
  • Like
Reactions: converging1
Hi Nick Galea, is 1.5 years later. what is the eta?
 
Hi Nick Galea, is 1.5 years later. what is the eta?

Looking at the Call Flow Designer for v16, I suspect this is imminent. The new CFD gives much more ability to manipulate each stage of the call. I've not downloaded it yet so I've not seen it for myself, but the announcement looks promising.
 
Hi Nick Galea, is 1.5 years later. what is the eta?
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.

He updated the time frame a couple posts ahead of you. I'm guessing around the end of Q2 at this point
 
Looking at the Call Flow Designer for v16, I suspect this is imminent. The new CFD gives much more ability to manipulate each stage of the call. I've not downloaded it yet so I've not seen it for myself, but the announcement looks promising.

What call flow designer for v16?
 
Is there any time frame for when this be available ?
 

Forum statistics

Threads
111,988
Messages
590,158
Members
164,923
Latest member
2B_JPS