[detavitca]

To get 3CX to choose the correct SIP trunk for outbound calls, I plan to use a prefix for the SIP-trunk, for example
Prefix 1: SIP account 1
Prefix 2: SIP account 2, etc.

But when a call is coming in via SIP trunk 1, from caller id 22222222, it is shown as 22222222 and not 122222222. So if I put the caller id into the phone book, 3CX would not know the prefix, and make an outbound call using SIP account 2 if a call is generated via the phone book!?

Is there a way to manage this or have I misunderstood something?

[danhriscanu]

Hi,

You should use 3cxMyPhone for this feature. In settings of Myphone you have a section called Prefix where you can specify number patterns and prefixes to be added automatically. So when you will call a number from your phonebook like 22222222, and you want this number to be dialed through trunk 1, you can specify that all number starting with 2222 should prepend Outbound prefix 1. You can ply with this outbound rules however you want.

[leejor]

So if I put the caller id into the phone book, 3CX would not know the prefix, and make an outbound call using SIP account 2 if a call is generated via the phone book!?

Any 3CX user that makes use of a prefix, would have the same issue. You can either add the prefix when you enter the number or become more "creative" with your outbound rules and not use a prefix.

Why are you using two routes? Is one for certain types of calls, certain prefixes, long distance? You can separate (route) calls based on prefixes or number length without requiring a prefix (using the "raw" caller ID). The outbound rules give you a lot of flexibility. If you add a lot of CID's to the phone book 'as is" and you insist that they use specific routes, then making use of the outbound rules, while more work (and planning) initially, may save you time overall.

[detavitca]

We are based in Denmark, but when calling UK/spanish Spanish contacts we want to call out via our UK/Spanish sip providers. Likewise contacts in these two countries call in via these UK/Spanish sip accounts.

To a certain extent I could of course say that a Danish tlf.no. is normally 8 long, a spanish 9 and a british 11, but there are special numbers and deviations from this rule. However, point taken, so it might be - in our situation - a viable route to follow. But not perfect, and should we get a sip account in another country with 8, 9 or 11 characters, then the system would collapse.

Or are there other ways?

[leejor]

Make use of the numbers (prefixes) to differentiate. If you wanted calls to the UK to go out on provider 2, then create a rule for numbers that begin with 0044, (if the call requires 00 as an international access code). 44 is the UK country code so all calls to the UK would use whichever route you specified. The same could be done with any country code/city code. You can have a "catch all" rule farther down the list to route any numbers that don't match a previous rules.

If you wanted to block , say, UK mobile numbers, you could with a rule 00447 before the 0044, that would route the more expensive mobile calls to no route, to block them.

Outbound rules are very flexible and act like an "if, then" statement as you go from top to bottom. The first match, is where the call will go.