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.

 

[leejor]

Nick, what do you mean by "Note that some trunks will not accept certain caller IDS - if they dont match the outbound number" ?

I think what Nick means (and please correct me if I'm wrong),is that not all providers allow you to change the outbound caller ID, and, if you attempt to, then calls may not go through. It is up to you to test to see if this will work in your case, not accept that it will by default simply because the option is provided.

 

[JasonNadeau]

Is this still in the works for V15??

 

[optixuk]

We just lost a sale as this feature is still not available in V15 SP1, and news on availability for SP2?

 

[cwoller]

Hi all.

I support the request for more flexibility with outbound caller IDs. We have a small call center and want to put 3cx in place but can't because we can only set one CID per extension.

Our problem is that if Customer #1 gets called (eg. if a call is routed from our call center to Customer #1), outbound CID has to be different than if Customer #2 is called, and so on.

It would be great to have a customization field within an extension or global on "outbound rules" that can reformat source-CID on destination basis like this:

outbound call to Customer #1:
destination number starts with: 123-456-*
3CX sets outbound CID for all 3CX extensions to: 123-456-0
-
outbound call to Customer #2:
destination number starts with: 321-654-*
3CX sets outbound CID for all 3CX extensions to: 321-654-333
-
and so on.

Regards, Christian

 

[CentrexJ]

I support the request for more flexibility with outbound caller IDs. We have a small call center and want to put 3cx in place but can't because we can only set one CID per extension.

In the meantime what we have done for clients who's extensions need to be able to dial out with different CID info is set them up with SIP trunks that are IP based not registration based. We create additional trunks for the different CIDs and then use outbound rules to target them. While not ideal to do this it works well. It means that if the customer has a limited number of simultaneous calls with the SIP provider 3CX can't properly keep track of them across different trunks but regardless the SIP provider will send a response if we exceed the SC.

E.g. dial out with a prefix of 9 and you are showing Company A's CID information, dial out with a prefix of 8 and you are showing Company B's CID information.

Many customers the extensions generally only need to show one company's CID information so we set extension groups so each extension has a default company and can dial normally without a prefix. Then we use # (#1, #2, #3 for Company 1,2,3) as a prefix character to make sure those outbound rules don't interfere with non-prefixed calls.

 

[cwoller]

We create additional trunks for the different CIDs and then use outbound rules to target them. While not ideal to do this it works well. It means that if the customer has a limited number of simultaneous calls with the SIP provider 3CX can't properly keep track of them across different trunks but regardless the SIP provider will send a response if we exceed the SC.

I could do it within the BeroFix Gateway. But I like doing things in one place so all outbound formating rules should be done by the instance that handles all other formating rules (=> 3CX).

Regards, Christian

 

[altitude]

Also looking for this feature. I wish to have have our Australian number displayed for all calls to Australia and our US number displayed with all calls to the US.

If there was just a field in the outbound rules where a number could be entered and the option to select outbound called ID taken from outbound rule, that would do the trick.

For our primary SIP I have had to create different SIP logins to achieve this (not optimal), but for our secondary SIP it is a heap of effort to create multiple SIP logins.

Any other suggestions?

 

[WiSo]

Hi all,

The rivalry between different regions is well known in Spain, (Real Madrid vs. F.C.Barcelona , which means that call centers dedicated to the sale of products and services required that if a call sent to a potential customer in Barcelona (93xxxxxx) the Caller ID must be also of Barcelona (93xxxxxxx) and the same if the customer is located in Madrid or wherever, since it considerably increases the possibility that the call is answered.

Therefore, the ability to set the Caller ID in outbound rules is a key functionality for call centers and the use of multiple SIP accounts in the terminals or several SIP trunks are not the best solution to solve the problem...

Please Nick, could you please give us an update?

Thanks ...

 

[altitude]

Agreed, it would be great to get an update. Thanks,

 

[jscherb]

It would be great to have the ability to override the SIP trunk’s outbound parameters (most specifically CallerID) in the ‘Outbound Rules’ configuration. This would be especially handy for 911 call routing – so that any calls from an extension group (a specific branch office) will have the proper outbound callerID. We have the main branch number that rings everybody and has the proper E911 information with our carrier, and we want to use that when making an emergency call.

Any updates on this?

 

[cobaltit]

C, I like the idea of pushing more info - but in the USA, we can only push a phone number - not the name (as far as I know).

These ideas are all great - but a simple solution to start - of adding an Outbound Caller ID option on the rules is what we need.
1) Trunk Number
2) Extension CID
3) Custom CID

@craigreilly

Sorry yes I didn't mean pushing that info specifically. Rather I was implying that by being able to push a specific CID registered with that info is the goal. And I don't think adding it to the Outbound Rules is the best place, rather on the extension level like FreePBX does specifically for emergency calls. Most of the other outbound CID scenarios are already capable in 3CX (if the provider allows).

 

[ian79]

Hi

May I know when will this be implemented?

We have 2 companies sharing the same trunk.
We want to use outbound rules to dial a prefix to choose the DID we want to use.

We could dial 11 88889999 and 11 will be removed and choose DID A.
if we dial 12 88889999, 12 will be removed and DID B will be chosen as caller ID.

 

[craigreilly]

ian79,
What provider are you using?
Do any of the users have a specific DID - or just the 2 mentioned?

 

[giwm]

So... I guess this didn't make it into v15? Maybe SP5!?!?!

 

[craigreilly]

So... I guess this didn't make it into v15? Maybe SP5!?!?!

i don't see it in 15.5

 

[phil.wade]

I need the CID set on outbound_rules page too.

 

[Kevnich2]

Is there any date that 3cx can provide as to when this feature will be implemented? I see this was created a year ago and Nick said it's in progress and still nothing over a year later? I have several other businesses that I was planning on migrating to 3cx but that will be a no go with this. I have a switchvox system that is several years old that has had this feature from day 1.

I was surprised when I'm messing with my test install and couldn't see where I could alter outgoing caller ID rules based on the number dialed. The only area you can modify caller ID is permanently on the extension level or trunk level. Several business I work with have lots of remote employees who require setting emergency services number to the employee's home phone or other number that has e911 so they can use their work phone for 911 dialing. This also applies to schools and multiple location businesses. It looks like I'll have to brush up on freepbx stuff until 3cx gets this very important feature going.

 

[Andrzej Pierscionek]

This is a desperately needed feature.
Most of our customers (we also have such) has special queue with external agents (mobile numbers) for helpdesk/support outside of office hours.
If we could modify caller ID we could set this queue to present with support number and not main office number so people would know this is a call they have to answer.
It would be very powerful feature.

3CX already has mechanics for reformatting - "Reformat Incoming or Outgoing Caller Identification". This mechanics could be used for outbound rules. Just be sure we can change this for system initiated calls - outbound from IVR, queue to mobile, CFD initiated calls.

 

[N_G]

Better outbound call ID configuration is in progress

 

[ghalan]

Same here. One primary Outbound CID for everyone, but we would need to have our DIDs as CIDs when we call our agents on the road.
Would love to hear "next feature in 15.5 SP2"