3cx integration w/ AVaya IP Office 500v2

[Dominique_CH]

Hi,
I'm aware of various other threads about this topic, but I still can't get this setup to work:
- on the 3cx, created a master bridge
- on the IP500, create a new SIP line registering on the 3cx master bridge
- both systems connect
- Avaya: created an inbound call route for calls arriving via the 3cx-bridge
- 3cx: created an outbound rule to route 2-digits numbers strting by 2-5 to the masterbridge (2x to 5x is the remote internal numbering plan)
- 3cx: when making a call, I can see on the activity log that the call is being routed correctly to the master bridge (see attachment) but the Avaya log doesn't even show such call arriving on the other end. Furthermore, there's no ring signal on the 3cx-extension making the call

So, I suspect, the call not even being sent out from the 3cx. Any ideas are welcome !

 

[ChrisC_3CX]

First off, do bear in mind that the 3CX Bridge was designed to bridge 3CX PBXs together only. You might actually be better off adding the other end as a Generic SIP Trunk rather than a bridge.

I did have a quick look though and, based on the provided screenshot 3CX did select Line 10010 meaning that it went through the Outbound Rule just fine. You might want to edit the bridge and make sure that 10010 is actually the virtual extension number of that bridge. If that is correct, only thing I could suggest then is performing a packet capture on the other end while attempting a call to check if any SIP traffic for that call is being received. This will at least tell you if it's the other end that's having issues.

 

[Dominique_CH]

Hello Chris,
Thanks for replying. This solution is only temporary as the other end will be replaced by a 3cx as well.
The other end doesn't get any traffic although the line is up and connected, which is why I suspect the call isn't even leaving the 3cx for some unknown reason. The virtual extension 10010 is correct

 

[ChrisC_3CX]

The other end doesn't get any traffic although the line is up and connected

In that case you might want to try performing a packet capture on the 3CX PBX instead so to determine if it is indeed leaving 3CX.

As previously mentioned though, I would recommend considering adding it as a SIP Trunk instead.