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.

 

[craigreilly]

This request is over 2 years old

Actually almost 4 years old. I posted this request in October, 2015.

 

[Andreas Olenitzack]

We need this Basic feature, when do you will release it?
This feature is crucial for the purchaseing of 3CX.

 

[nseatonedu]

Crickets chirping

 

[dandenson]

well, you basically can do this a couple ways.

1) for each individual extension put it in their outbound caller id field

2) setup different trunks for each caller id you want to have, put extensions in extension groups, then setup outbound routes for each extension group to that trunk. Probably only works on IP based trunks. A 3CXer just confirmed this config for me with bandwidth.com (IP based).

 

[bbredewold]

well, you basically can do this a couple ways.

1) for each individual extension put it in their outbound caller id field

2) setup different trunks for each caller id you want to have, put extensions in extension groups, then setup outbound routes for each extension group to that trunk. Probably only works on IP based trunks. A 3CXer just confirmed this config for me with bandwidth.com (IP based).

So I'll need 10 trunks to call out with 10 different numbers. That will cost me about 100,- extra each month...

 

[dandenson]

So I'll need 10 trunks to call out with 10 different numbers. That will cost me about 100,- extra each month...

In scenario 1 you just put it in each extension config

In scenario 2, you would be IP authenticated and the number of configured trunk setups wouldn't matter. If you have to register your trunks then this one probably isn't going to work.

 

[Andreas Olenitzack]

scenario 1 is crap for Call Center with over 100 Outbound Numbers
scenario 2 is not a feature, but it works.

 

[dandenson]

How is scenario 1 crap? How would you expect to handle this in another way? You need to set the outbound caller ID somewhere, why not the extension?

If you use scenario 2, you could use a prepend digit so reps could select the outbound caller-id when they dial, though having hundreds is an obvious issue...

I guess it would be best if you explained your use case here so we aren't guessing at how you need outbound caller id to be selected.

 

[Andreas Olenitzack]

We have over 100 outbound caller ids and every extension musst have the possibility to use them.
So it should be a dial code that every one can dial to use an outbound call id.
Like:
*901 = 0800 1234567
*902 = 0201 1234567
*903 = 0000 1234567

Dial Code: *901+Number

Something like that.

But it is not importent to make for every outbound call id an extra sip trunk.
So a new input field in "outbound Rules" to set an Outbound call id would be the best way.

 

[man416]

+1

 

[cparker_RCT]

+1

 

[LariFari]

+1
We need to be able to change outgoing CID on the fly. Otherwise the customer would have to use multiple phones per desk, which is not at all feasible.

It should be possible to define a list of allowed outgoing CIDs for each extension
that the user can pick one from by BLF key. The state of the BLF key should represent, which CID is currently selected.

The allowed CID list per extension could also include the CID properties of groups and queues that the extension is a member of.

 

[fatenone]

+1
We really need this function as well (i.e. setting the CID in each outbound rule). Thanks!

 

[Macinator]

I hate to ask this - it appears to have been beaten to death in this thread for years. However looking at new VOIP systems and interested in 3CX. I have reached out to a partner but not had a chance to talk yet.

I am looking for system to replace a non-compliant E911 system for 7 schools. We need zones at a minimum but want to do E911 to the classroom level. It appears that this does not currently exist in 3CX but is it possible via third party - looking at VoipTools - it appears that is targeted to enhanced notifications but it can't change the DID info sent.

Sending individual DID numbers is not acceptable for us - the CID must show the Schools main number. Am I wasting my time and a partners time looking here? Can a SIP provider pick off the MAC address of the phones (another provider said they could) and send the DID based on their database?

We are coming off POTS/PRI and moving to SIP but SIP is new to me so I do not know its capabilities yet.

Thank you,

Scott

 

[craigreilly]

@Macinator -
set the extension outbound caller id to the school's main number.
but then this presents issue with 911 caller id you inquire about.

I do not think it can do as you would like it to via Mac. But, have a second trunk that sends 911 via this trunk and sends the extensions caller id, instead of the schools id. In this case, each school would have 2 trunks - 1 for 911, and 1 for regular calls.
also you would have to pay for 911 for every outbound caller id.

 

[Macinator]

Craig -

Thank you for the quick response, and I may not be understanding exactly what you mean. But this does not meet our E911 needs. Due to the size of our buildings - we can't simply report a single DID for the building address. It has to be building + room number, as I understand it 911 needs to be able to ring directly back to the phone that makes the call as well. So 911 needs to see the real DID but all other calls need to see only the school phone number.

Thanks,

Scott

 

[craigreilly]

So 2 trunks per location.
1 for the regular calls outbound number “the main school number” and a trunk for 911 calls. One trunk uses a common number for calls and the other trunk uses the extension outbound caller id for 911 calls. You will have to also register every did with 911 so the number can be attributed to an address with room number.

 

[Macinator]

Thank you - that helped clarify.

Much appreciated.

Scott

 

[TechCheck]

So 2 trunks per location.
1 for the regular calls outbound number “the main school number” and a trunk for 911 calls. One trunk uses a common number for calls and the other trunk uses the extension outbound caller id for 911 calls. You will have to also register every did with 911 so the number can be attributed to an address with room number.

This is an interesting option. In the example of a school district with 4 buildings, I would need 5 trunks, 4 to send the building CID for a common number and one to send the extension CID when 911 is dialed. All CIDs would be registered with our local E911 database company.

Is that correct?

Thanks,
Brian

 

[SteveITS]

So I saw https://www.3cx.com/docs/multiple-outbound-caller-ids/ has info on doing this with multiple trunks. https://www.3cx.com/docs/cid-reformatting/ talks about rewriting the outbound caller ID so could that be used or am I misunderstanding? To change (dialcode)(destinationNumber) to (secondCallerID)? Or is that just for changing the outbound called number not the outbound caller ID? (an example for outbound would help on that page)