3CX and Allworx Coexistence/Migration Pilot: Routing and Extension Ringing Advice

[jpauley]

Our client wants to be the pilot for 3CX migration but he will be the only one on the tenant currently. Trying to figure out how we can make the Allworx and 3CX coexist to be able to make calls from 3CX through Allworx outbound calls and then local extension calls. If this person's extension is dialed, their current Allworx phone rings, but then ring the user's Yealink phone on 3CX as well. Does anyone have any advice or guide that would help facilitate the connection between the Allworx appliance and hosted 3CX tenant to work as if I was making calls work between the systems?

 

[Alejandro_3CX]

Hi @jpauley to achieve coexistence and seamless routing between a 3CX PBX and an on-premise Allworx appliance, you need to use a bridge in the 3cx and use a sip trunk in the allworx, please find more details about it in this post.

Then since you will use the same extension range, then configure a prefix in the outbound rule, for example 8, if in the allwork they need to contact user 100 that is in the 3cx, they could dial 8100 and delete the prefix in the outbound rule. In this way you can avoid any loop.

 

[jpauley]

Thanks @Alejandro_3CX. I was able to bridge both together, but I ran into a new issue. When I make external calls from 3CX through the Allworx appliance, it wants to treat them as internal calls only, even though I matched the outbound rules with ASR routing for Allworx.

Do you have any advice on how I can prevent the calls from acting as incoming calls to the Allworx, or should I explore a different avenue?

 

[Alejandro_3CX]

So you are dialing an external number from the 3CX and it is being routed properly via the bridge, isnt it?

The other system should read the TO USER PART and understand that is is an external number and process the call with any of your outbound rules where you have the pstn lines, so that must be reviewed in the other system...