Call Forwarding External Numbers from Extension to specific SIP trunk

[mickymac]

Hi All, hopefully someone may be able to help me with this, or confirm whether it would be even possible.

Firstly we've got 2 SIP trunks:
Provider A - Our main carrier which houses our inbound DID's and provides free outbound calling, however doesn't allow Caller ID forwarding (but will pass through Caller ID for internal extensions).
Provider B - Our Additional carrier which charges per minute on outbound calls, however allows Caller ID forwarding from any number.

Our preference is for all outbound calls to use Provider A for the cheaper outbound rates but only when "external calls" are forwarded to their mobiles to use Provider B to pass through the Caller ID. At present we've just created an Outbound rule in 3CX that recognises a prefix (99 in this case) and by prefixing 99 to the 3CX employee Mobile Phones in extension settings seems to result in outbound calls going over Provider B with Provider A used for everything else, which is perfect, or so we thought.

The only problem that we've found out today is that even for internal calls (i.e. if a receptionist calls a persons extension to find that they are not at their desk and the call is then passed onto their mobile) it is going over Provider B instead of Provider A (which would make sense given that the 99 has been prefixed to the employees mobile number).

Is there anyway to maybe specify for those external calls to specify a specific outbound trunk it or am I completely stuck having to pay the significant cost difference?

Appreciate in advance any help you can offer.

 

[cobaltit]

A second outbound rule should suffice. Inbound calls that are forwarded should technically be coming from a system extension which is excluded when you put conditions on the rule. So if you had one rule with the leading 99 scoped to your internal extension range and then another rule with 99 and no restrictions that should do the trick. Internal calls will match the first rule and external calls should skip the first rule and match the second rule.

 

[mickymac]

Thanks Cobaltit for your reply. Gave that a go, but alas seems to be the same issue (only now it goes via Provider A so I loose the external caller ID).

 

[mickymac]

Ok, I think I've managed to get a working solution. From what I've found it appears that when forwarding calls from the extension in 3CX it just uses whatever outbound rule is applicable for the extension.

What I ended up finding that works is keeping the 99 prefix for calls to the secondary trunk, then for the extension settings having the regular mobile number entered under the general tab. I then went to the Forwarding Rules tab under Internal Calls and selected Forward to Mobile, but for external calls selected Forward to Number, then entered in the mobile number with the 99 in front.

So far from testing it with a couple of extensions it seems to be working well.

 

[YiannisH_3CX]

The way you have set it up should do the trick. Let us know if you run into any issues

 

[mickymac]

Thanks Yiannis,

Out of interest, is there any other way to do it?

 

[YiannisH_3CX]

Out of interest, is there any other way to do it?

I cannot think of another way on the top of my head. The way you are doing it seems to be optimum for your scenario

 

[mickymac]

Ok cool, good to know. So far from our testing this afternoon it’s been flawless, so we might leave it the way it is and see how we go