Choose Different Trunk for Outbound Calls

Status
Not open for further replies.

mji

Bronze Partner
Basic Certified
Joined
Jun 24, 2020
Messages
17
Reaction score
1
Dear All:
We have two SIP trunks from 2 different SIP providers set up in our 3CX PBX. Can a user of an extension selects one for an outbound call?

Minda
 
As per the guide posted above, you can have a dialling prefix to choose the outbound trunk.
 
As per the guide posted above, you can have a dialling prefix to choose the outbound trunk.

Hi, John:
Thanks a lot! Your post should be very helpful to resolve this issue.

Minda
 
As per the guide posted above, you can have a dialling prefix to choose the outbound trunk.

Hi, John:
Just tried it by following the instructions. it fails to call using different SIP trunk. It returns "Internal Server Error".
 
It returns that, where, on the set? Have you checked the 3CX Activity Log?

Post your outbound rules. Rules may have some restrictions set on them that are preventing certain extensions from using them. Rules are read from top to bottom, so the first match, is used. When using a prefix, you can become more specific in the rule, which means you don't have to use the digit length alone.

Old, but still relevant...

https://www.3cx.com/blog/voip-howto/outbound-rules-a-complete-example/
 
  • Like
Reactions: accentlogic
I checked following log:
Call or Registration to 9@(Ln.10000@Skyetel) has failed. 52.8.201.128 replied: 503 Service not available, no gateways found; from IP:52.8.201.128:5060

It looks like the rule never gets triggered at all because I set 9 for using flowroute SIP trunk instead of Skyetel. It keeps triggering Skyetel's trunck.

Minda
 
The log you posted would appear to be another issue altogether. You are sending only a 9, but the gateway cannot be found, apparently.

If you have 9 as the prefix for flowroute, then you can use 8 as the prefix for your second provider. But, the number sent to the gateway must be the full number (as you previously sent), with the leading digit (the 9 or 8) removed.

I don't know where you're located, or the number format used so I will use North America numbers as an example.

Local number are usually 10 digits (with an areacode). So for local calls you'd have 2 rules numbers beginning with 9, 11 digits long, strip 1 digit and send to provider 1. The second would be numbers beginning with 8, 11 digits long, strip 1 digit and send to provider 2.
For national calls...calls beginning with 91, 12 digits long, strip 1 digit (or two, if your provider does not want the leading 1). Then a second rule using the 81.

Then repeat for international calls with an 8 and a 9 leading digit. You must also accommodate "special", shorter numbers as well. The outbound rules can also be restricted to only certain extensions, if you wish to block some from using one of the providers , or placing international calls.

You can also place the second trunk group as a backup, if all trunks on the first are busy.

And remember , rules are read top to bottom.
 
Thanks a lot! Rules read top to bottom works for us. We've moved it to the top. The other one with no prefix set. That's why it did not trigger the one with 9 as prefix.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,953
Messages
589,915
Members
164,851
Latest member
DrunkeMeister