Solved Outbound Rules (Same Provider)

[benreilly]

I have 4 SIP numbers with 4 different passwords, under same IP. Since its impossible to have each number under a single trunk as DID (because of different credentials) i have to create 4 separate turnks and identical outbound rule per each.

Now when 4 outbound rules are created following issue occurs. Only first caller can make a call as when someone else tries to call simultaneously 3CX does not switch to the next available trunk and still tries to use first outbound rule only.



Another idea was to create a single outbound rule and put each trunk as Route 1, Route 2 etc...but in this case if a caller make a call on mobile and recipient rejects it (408 Request Timeout) then 3CX makes another call without closing the line from Route 1 then Route 2 up to the last Route which means 4 calls in a row, only when rejected.

Question: Did anyone had similar issues with having a bunch of trunks with same outbound rules? Please help.

 

[leejor]

You say "under the same IP", so this is one trunk group, one provider, with four numbers assigned?

Is the idea is that callers can call out using different caller ID over the same trunk group? Please clarify this.

You could require a different prefix, depending on the required route, then any extension could call out over any number using the rule with that prefix, then that caller ID.

Or, you could restrict each rule, to certain extensions, then no one else would use them

 

[benreilly]

so this is one trunk group, one provider, with four numbers assigned?

This is one provider that gives 4 different numbers with different passwords under single IP\Server.

Is the idea is that callers can call out using different caller ID over the same trunk group?

Idea is for all extensions (15) to make a call outside simultaneously over available trunks. In this case, 4 sim calls.

You could require a different prefix

Unfortunately current provider does not give additional prefixes. All outside calls start from "0". That's why i am forced to have the same outbound rules per trunk.

Thank you for your reply.

 

[ClaudioBassani]

HI,
I would say it is a very strange case. The second configuration, the four routes, could be used, dedicating the first to calls only for cell phone prefixes. If the number dialed by an extension is not for cell phones, it will use the second, third or fourth route. Better if the trunk associated with the first route has a number of SIM calls greater than one. I think it can work.

 

[benreilly]

Hi,

The second configuration, the four routes, could be used

This sounds legit but each number comes without additional channels, which means when the line is busy no other extension will make a call using the same outbound rule (even if specified trunk is different), 3CX does not distinguish outbound calls from different trunks when prefix and digit length are the same. As a compelled solution i can request 10~15 channels for the 1st number and have a few separate outbound rules per prefix. This will make sim calls always possible, but i wonder why this task can't be handled by such advanced system. Even in grandstream you can create a group of numbers with different credentials under the same trunk. Thanks anyway.

 

[leejor]

This is one provider that gives 4 different numbers with different passwords under single IP\Server.

View attachment 21077


Idea is for all extensions (15) to make a call outside simultaneously over available trunks. In this case, 4 sim calls.


Unfortunately current provider does not give additional prefixes. All outside calls start from "0". That's why i am forced to have the same outbound rules per trunk.

Thank you for your reply.

The provider does not have to provide different prefixes, you set that up in 3CX.

So.....as an example, to place calls on the first trunk, the caller would start the number with a 6, on the second trunk, a 7, on the third an 8, and so on. In the outbound rules, you create a rule that starts with 6 (and 7, and 8, etc.) and is the correct length. Strip off the first digit, and send the ones you normally would on the desired trunk.

The prefix could be two, or more digits long, as yuo strip them before sending to the provider.

 

[benreilly]

The provider does not have to provide different prefixes, you set that up in 3CX.

Ok, i tried that but can't make a call if additional digit stands before zero (even if stripped) correct me if i'm wrong, your idea is to differentiate each outbound rule for 3CX per trunk but stripped digit still will be dialed and the sequence will break. Check the rule please.



stripped 9 is paced before zero to call on mobiles, however its possible only when 9 is removed otherwise you cant make a call.

 

[YiannisH_3CX]

Hi @benreilly

I would recommend moving to a supported provider for this list. Providers should be able to provider multiple numbers under the same credentials with multiple channels so this won't be a problem.
Also please check out our academy presentation on outbound rules. You can structure your outbound rules many different ways and always send the same number to the provider.

We can only verify that the above example you provided is correct if we know what number your dialed. Otherwise it might or might not be correct.

In your first port the outbound rules have a number length of 7 which suggests that you are dialing a 7 digit number which starts with 0. But in your latest screenshot you have a number length of 10 and you are stripping one digit so 9 digits will be sent to the provider. So something does not add up here.

 

[benreilly]

Hi YiannisH_3CX

Thank you for clarification.

Providers should be able to provider multiple numbers under the same credentials

In my case each number has different credentials, is it possible to have one trunk with multiple numbers and different passwords, when server IP is the same?

In your first port the outbound rules have a number length of 7 which suggests that you are dialing a 7 digit number which starts with 0.

Length was not correct only because of demonstrations purposes. Real rule list is below. 3CX does not switch to "City 2" or "Mobile 2" when "City 1" or "Mobile 1" are used.

 

[ClaudioBassani]

Hi benreilly,
Of course you know, but I remind you that 3CX phone system does not continue the search in the set rules when it finds the first condition that satisfies it. This means that the order of the rules is very important. Sorry if I reminded you but it seemed right to emphasize this behavior of the PBX.

 

[YiannisH_3CX]

In my case each number has different credentials, is it possible to have one trunk with multiple numbers and different passwords, when server IP is the same?

No, this is not possible because this should not be necessary.

Length was not correct only because of demonstrations purposes. Real rule list is below. 3CX does not switch to "City 2" or "Mobile 2" when "City 1" or "Mobile 1" are used.

As @ClaudioBassani mentioned outbound rules are processed from the top down so the PBX will stop searching when it finds a match. In your case since all rules are the same it will always match the first one.

As i said my recommendation is to switch to a supported provider which supports multiple numbers and channels with a single trunk.

 

[benreilly]

As i said my recommendation is to switch to a supported provider which supports multiple numbers and channels with a single trunk.

This is the only way, I have to admit.

I would like to thank you all for assistance! Have a nice day!