Calling a PSTN number assigned to 3CX

[mls.nicolas]

Hello,

We've noticed that when a user makes an outbound call to a PSTN number that is configured as a DID on a SIP trunk on the same 3CX server, the call is still sent to the ITSP according to the outbound rules.
Of course, users should in general call internally using extensions and not DID, but sometimes they're using PSTN numbers (E164).
This is generating cost for the customer as they are making outbound calls according to the ITSP.

Is there any way to keep the call internally in 3CX and not route it to the SIP trunk ?
Thanks

 

[leejor]

You could create a loop trunk...

1. create a SIP trunk with 127.0.0.1:5060
2. create outbound rule(s) for this trunk. They should intercept all DID numbers
3. attach existing inbound DIDs rules to this trunk

Your outbound rules for these numbers should be placed above the catch all route normally used.

Each call will use two simultaneous call licenses.

 

[NicholasP_3CX]

Hello,

We've noticed that when a user makes an outbound call to a PSTN number that is configured as a DID on a SIP trunk on the same 3CX server, the call is still sent to the ITSP according to the outbound rules.
Of course, users should in general call internally using extensions and not DID, but sometimes they're using PSTN numbers (E164).
This is generating cost for the customer as they are making outbound calls according to the ITSP.

Is there any way to keep the call internally in 3CX and not route it to the SIP trunk ?
Thanks

Start billing the users that use the DID. See how quickly the calls to DIds instead of extensions stops!