Is it possible to prevent internal outbound calls destined to for a DID on the system from going out the SIP trunk and back in?

[Jesse Amos]

I've seen similar posts on here from several years ago but they all seemed to refer to V14 or V16 configurations. Setting the scene, the client has one 3cx for multiple physical locations, and no matter how hard we try to train the users they always end up calling the DID for other locations, rather than the internal extension/RG/Queue that they want to reach, and the receiving users are getting frustrated because this strips out the caller ID info and sets it to the department CLID info instead of the individual user, and I'm frustrated because of the inefficiency of using 2 concurrent sessions throught the trunk for an internal call. Is there a way in V20 to intercept/redirect/forward these internal calls made to an external DIDs directly to the appropriate destination? Is there some type of source identification setting I'm not familiar with to identify internal calls to system DIDs?

I read through the Source ID doc here but that deals with incoming calls, not outgoing calls so I don't think so, but could be mistaken.

A loopback trunk may do the trick but how would that work exactly? Would I need to create a loopback for each external number of each site? Would the internal CLID info remain the same for all calls from a site or would the extension CLID info be retained?

Some guidance would be most appreciated.

 

[fxbastler]

Hello @Jesse Amos and welcome to the admin club of ignorant users.

As far as I know, what you want cannot be implemented.

But it is still possible to block calls to known numbers of the other trunks in the outgoing rules of the respective SIP trunks. This can only prevent the calls that are supposed to take place internally from taking place via the external number. The call fails and is blocked.