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.

 

[rayfield]

I have a business. I have 100 users each with a DID. To register each DID for 911 emergency to my work address will cost $1.25 / month for each number. So, $125 month.
If I can assign an outbound number to the outbound rule called 911 Emergency, then I only need to pay for 1 911 assignment - and still use the Extension Assigned DID for normal outbound calling.
If you start at the top of this thread, I think the concept is quite clear.

I see what you're talking about. You mean one global Outbound Caller ID, rather than a separate Caller ID for each extension, just to be used for 911 calls..

Yes, having one global Outbound Caller ID would definitely save money with some VoIP service providers and still allow each extension to use their own Outbound Caller ID to match their DID number.

John Rayfield, Jr.

 

[cwoller]

We have a small call center that needs to set the outbound caller id in dependency of what customer they calling out.

For example, customer A has an extension 123 defined on the TA for inbound calls. So after office hours, customer A routes his inbound calls to our call center with extension 123 and this gets counted (and later billed).

When our call center staff tries to call back customer A during office hours, they want to display outgoing number 123 to customer A's staff.

Our call center has about 50+ customers, each with own extension. Currently the call center is on a linux based TA but the service fees are way to expensive so we want them to switch to 3CX. But therefore we need to set outbound caller id in a more flexible way.

Best regards,

Christian

 

[Jack150]

in a call center we need to send out different CLI's per campaign we cannot statically assign a cli per user/device

 

[Brad Allison]

facepalm... looks like 3cx missed the boat in new beta release.

https://www.3cx.com/blog/releases/update-5-pbx-crm-integration/

Emergency dialing (911)
Although 15.5 already supported emergency dialing, we have made two notable improvements:

You can now configure per group – or range of extensions – which emergency number they should use in the outbound rule. This greatly simplifies configuration.
Emergency calls no longer go against the license limit – they can always be made (providing your SIP trunk has the capacity).​

this sounds like what we are asking of the per group or range of extensions, however when you watch the video it is just selecting which trunk those extension (groups) go out when calling 911 and not changing outbound Caller ID...

FYI, we could already do this all you did is move where we do it for emergency calls this simplifies nothing!!!

Also, how does this help for PRI deployments?
Let me help with the statement of "shouldn't be using old PRI for new VoIP PBX deployment".
its called being in a contract.

The ability to set outbound Caller ID should be a basic feature that any phone system should have.


Good to know that emergency calls aren't counted towards license again, anymore?

 

[ODD Network BV]

This will be Great for our customers too.
Customers want to send different Caller ids.

 

[cobaltit]

facepalm... looks like 3cx missed the boat in new beta release.

https://www.3cx.com/blog/releases/update-5-pbx-crm-integration/

Emergency dialing (911)
Although 15.5 already supported emergency dialing, we have made two notable improvements:

You can now configure per group – or range of extensions – which emergency number they should use in the outbound rule. This greatly simplifies configuration.
Emergency calls no longer go against the license limit – they can always be made (providing your SIP trunk has the capacity).​

this sounds like what we are asking of the per group or range of extensions, however when you watch the video it is just selecting which trunk those extension (groups) go out when calling 911 and not changing outbound Caller ID...

FYI, we could already do this all you did is move where we do it for emergency calls this simplifies nothing!!!

Also, how does this help for PRI deployments?
Let me help with the statement of "shouldn't be using old PRI for new VoIP PBX deployment".
its called being in a contract.

The ability to set outbound Caller ID should be a basic feature that any phone system should have.


Good to know that emergency calls aren't counted towards license again, anymore?

I just watched the video and had the same reaction....

How hard is it to do it they way FreePBX has done it for as long as I can remember? Put another field at the extension level for emergency and call it a day.

 

[Brad Allison]

I just watched the video and had the same reaction....

How hard is it to do it they way FreePBX has done it for as long as I can remember? Put another field at the extension level for emergency and call it a day.

View attachment 7880

Yep, extra E911 CID field under the extension is the common approach.

3CX is the only one of five VoIP phone systems that i have administered that does not have this capability.

 

[cwoller]

A big please to the 3CX team: Make this option more flexible and not only related to Emergency / 911 calls. There are a lot call center who need a more flexible way of handling outgoing numbers.

Thanks & regards,

Christian

 

[Tim De Vos]

It is marked "in progress" for 2 years and promised it will come to v15 but it would indeed be great to have some news about when it will actually be available. As a callcenter user it is crucual for us since we work for many customers.

So please 3CX team, you're doing a great job on several features but do you have any update on this one?

It's becomming more and more difficult to convince management with the sentence "it is scheduled for a future release".

 

[cwoller]

Hi 3CX - anything new on this old topic?

Maybe within the next SP?

Christian

 

[TP_]

It is marked "in progress" for 2 years and promised it will come to v15 but it would indeed be great to have some news about when it will actually be available. As a callcenter user it is crucual for us since we work for many customers.

So please 3CX team, you're doing a great job on several features but do you have any update on this one?

It's becomming more and more difficult to convince management with the sentence "it is scheduled for a future release".

+1

 

[dandenson]

bumping this topic also. e911 fees are a bit costly so it's usually preferred to have a single e911 number on outbound even if there are multiple DIDs in use at a site.

please address this asap.

 

[infohit]

Also bumping. But don't forget, it's not all about E911. We need to change outbound CID based on a rule. For example dial *123*01234567 and get CID 3333123, dial *456*01234567 and get CID 3333567 and so on... Adding an option to existing Outbound rules settings to be able to change CID would be perfect in my opinion.

Maybe something like this in the attached picture?

 

[lightwire]

We really need this for our 100+ deployments.

 

[clarity2]

3CX, any update on this?

We are currently experimenting with configuring additional SIP trunks and sending 911 to those trunks and then overriding the CID using trunk CID pattern re-formatting. But this is a kludge workaround that seems like it really should not be necessary.

Has anyone tried anything like this?

 

[craigreilly]

I have flowroute and they allow a password reg and an IP reg.
The password reg I use for normal calls.
The IP reg for 911. No magic. Just set that one to use the callerId of the trunk instead of the extension.

 

[clarity2]

Good to hear. We are currently evaluating flowroute. I'm assuming you are happy with them?

Sometimes we have multiple E911 locations, with for example 5 DIDs in one, 5 in another and 20 in the main office, so that's where I'm hoping the cid-reformatting will work.

Again though, an override on the outbound rule would be ideal as in the above situation we would group the phones and use one rule for each group.

 

[craigreilly]

Agree that the override would be perfect. Just working with what I have. I do have 1 remote office with 3 users... They all use the same outbound caller id so no issue.

 

[cwoller]

It seams to me, that 3CX missed again this feature for V15.5 SP6!?! I did not read about this in the changelog.

Could someone from 3CX please give a hint, when we can expect this "in progress" request will be delivered?

Christian

 

[PeterLim]

Bump

Missed SP6. Can we get this in please?