Choose Your Outbound Caller ID in 3CX V20 Update 10

[KyriacosS_3CX]

Select an assigned DID before each external call, with no extra outbound rules to maintain.​

Calling from the right business number matters when users represent multiple brands, offices or services. With V20 Update 10, Admins can let users choose which of their assigned DIDs to use before placing an external call. This means one user ca...

Continue reading the Original Blog Post.

 

[Dan_TD_BirmTel]

This is definitely a step in the right direction, however the majority of use cases for our customers will not be a user's assigned DID but a group/queue/DR DID. It could even be a number that is not on the SIP Trunk at all.

Will this ever be implemented to allow numbers outside of assigned user DID's?

 

[Alphabetic]

This is definitely a step in the right direction, however the majority of use cases for our customers will not be a user's assigned DID but a group/queue/DR DID. It could even be a number that is not on the SIP Trunk at all.

Will this ever be implemented to allow numbers outside of assigned user DID's?

I cant see why this wouldnt be implemented in the future, it seems logical to.

It would be really great too, if the DID names could be taken across for easier identification (Again, suspect this will come)

 

[SweetAction]

This is definitely a step in the right direction, however the majority of use cases for our customers will not be a user's assigned DID but a group/queue/DR DID. It could even be a number that is not on the SIP Trunk at all.

Will this ever be implemented to allow numbers outside of assigned user DID's?

There's significant conversation about this in the other (alpha) thread, but since (last I checked) you can already chose a DID for SMS (when starting a new convo) that's assigned to a queue you are a member of, I suspect that same logic will come here.

 

[richiewhite]

It's unclear to me how the bypass outbound rules works. If your outbound rules include your normalisation, ie if you have multiple providers that have different requirements around CLD presentation, does selecting a specific route then pass the call to the trunk without any normalisation?

 

[N_G]

To use another outbound caller ID it must be assigned to the extension, this can not be bypassed. Re calling using a queue DID if the person is part of that queue and the DID is assigned to the queue is something we will look at but its not something quick to do.

 

[Benedikt Machens]

To use another outbound caller ID it must be assigned to the extension, this can not be bypassed. Re calling using a queue DID if the person is part of that queue and the DID is assigned to the queue is something we will look at but its not something quick to do.

In our customer base using the DID of a queue is the more common use-case (agent has multiple hotlines). The OutboundDID by user is also used, so still a good feature.

Would be great to see a checkbox in a queue, "Allow agents to set DID of queue" to control this. Someday in Update 11, V21... whatever

Best regards

 

[KyriacosS_3CX]

It's unclear to me how the bypass outbound rules works. If your outbound rules include your normalisation, ie if you have multiple providers that have different requirements around CLD presentation, does selecting a specific route then pass the call to the trunk without any normalisation?

Hello,

The caller and called numbers would be passed to the trunk associated with the DID as seen in the dialer.

You can use the settings found in the Trunk config Options section (E164 conversion, caller ID reformatting ) to ensure numbers are consistent across Trunks.