Outbound Caller ID

[Phillip Horn]

Using a generic sip trunk (Windstream), having trouble getting the outbound caller ID to show up for our users.
There are 600 DID's (361 assigned) across around 30 buildings. By default, everyone calls out with the 'Main Trunk No' as their CID, but when an emergency happens, the extension DID needs to be sent.
This might be a feature request, but for now I'm trying to get the extension to be able to be sent as the CID without entering the number in the Caller ID field on each ext.

The SIP trunk uses To: User Part as the CID field. I can change it to different parameters and the change goes through, but I can't seem to get it to use the ["CallerNum" caller's number] (possibly because it's too short?)
If I set to "OutboundCallerID", it works if there's a number in the Caller ID on the extension, and if I set it to "OutboundLineID", that works for whatever number is in the Caller ID tab on that trunk.

Can we use variables on the Caller ID tab in the trunk settings, or is there a better way to set the outbound CID? For example Caller ID is (123)456-%extensionID%

Ultimately we have got to get something working so that if someone dials 911, the operator gets that extension so that they can go to the correct building. A bonus would be to use a default number for everything else. The ideal situation would be to group outbound calls by department (each department is a Group and has specific rights, so adding a CID outbound field to this area would be very helpful.)

 

[YiannisH_3CX]

Hello @Phillip Horn

Currently to set this up you will need a second trunk that will be used for emergency calls. You will also need to add the outbound caller ID of each extension under extension settings.
The default trunk will be set to send the OutboundLineID so it always sends the main trunk number where the second trunk will be set to send the OutboundCallerID which will be taken from the extension settings.

 

[VoIPTools]

YiannisH_3CX, I "liked" your approach -- that's a good idea. Phillip, I encourage you to take a look at our Emergency 911 Notifier add-on. It can perform notifications via phone (text-t0-speech), email, SMS and Desktop popup. And notifications can be specific to geographical location too.

 

[craigreilly]

@YiannisH_3CX This request was put into Ideas a long time ago - and said it was in progress and was implemented for 911 only. I have not tested it - but I am assuming 911 (emergency calls), if programmed in the Trunk, will show the main trunk caller id instead of the extension?
Really hoping for more flexibility here in the near future to have different caller ID's for outbound calls based on the outbound rules.

 

[leejor]

It would be nice to see (at least, as a start) an "override" caller ID option, available for both a rule, and a route. If more than one were encountered, the last being used.

 

[YiannisH_3CX]

@YiannisH_3CX This request was put into Ideas a long time ago - and said it was in progress and was implemented for 911 only. I have not tested it - but I am assuming 911 (emergency calls), if programmed in the Trunk, will show the main trunk caller id instead of the extension?
Really hoping for more flexibility here in the near future to have different caller ID's for outbound calls based on the outbound rules.

The emergency number will override the normal outbound rules and will allow you to perform a call in case the emergency number is called. It will however follow the trunks outbound parameters. So if you need all your users displaying the main trunk number when making calls then that will also be displayed when the same users dial the emergency number.

 

[craigreilly]

In my eyes - besides overriding the number of simultaneous calls - this didn’t do what was asked for in the idea... it still doesn’t let us change caller ID of outbound calls.