Caller ID exceptions

[Mike94]

Hello Team,

I have very interesting problem which I'm trying to deal with. Basically when I'm calling my customers from any of the extensions I want them to see my main trunk number which is obvious to configure and works fine, but in some cases when I'm calling my colleagues from the office I want them to see the actual extension's DDI rather then the main trunk number. Sometimes they are confused and they don't know who called them as they see the main trunk number instead of the extension's DDI from which call was placed, if you know what I mean.

I would like to apply this policy for let's say 5 different mobile numbers, so only my colleagues with any of this 5 mobile numbers will see the actual extension's DDI who called them rather than the main trunk number.

I know it might sound little bit confusing but feel free to ask my questions so I can try to explain it in a different way!

Thank you so much in advance

 

[Saqqara]

You can not be selective, the setting is for all outgoing calls per extension,

Why not install the 3CX mobile application, then you can call them by 3CX extension number.

 

[VoIPTools]

You are probably already aware that to use the default outbound caller ID defined on the trunk, leave the extension's CID setting blank. To override the default caller ID and use a extension specific DID, edit the extension's CID setting. I can not think of any other automated option for setting the CID on a call-by-call basis.

Our VoIPTools "3CX Caller ID" tool would make it a little easier.

 

[leejor]

You could do this IF you had a second trunk group, that was optioned to use the DID number, set against the extension. You would also have to create outbound rules, that routed the "selected" numbers (that you wanted to receive your DID), over that trunk group.

A second linekey (extension), on the set, with the DID number set, would also work. The first line key having no external CID datafilled. That means a custom template.

 

[Mike94]

You could do this IF you had a second trunk group, that was optioned to use the DID number, set against the extension. You would also have to create outbound rules, that routed the "selected" numbers (that you wanted to receive your DID), over that trunk group.

A second linekey (extension), on the set, with the DID number set, would also work. The first line key having no external CID datafilled. That means a custom template.

Thank you @leejor

I like this idea, I am going to try it and will let you know does it work

 

[leejor]

The original trunk group would have to be optioned to always send the "main" trunk number, or any extension, that had the outbound caller ID number set (DID number), would override. You may have to do some trial and error testing.
Many providers allow a sub-account , on a different trunk, for very little, or no additional cost.

 

[Mike94]

Hi @leejor,

I have tried the first option and it works really nice after applying all necessary settings on the sip trunks. There is only one limitation, the sip trunk needs to have a CLI Flex feature in order to assign a DDI which is not sitting on that trunk.

Thank you for your advises