Need help connecting 3CX to Avaya IPO Server Edition

[jmatano]

Hey everyone. We are in the process of attempting to try out 3CX in our call center environment. Currently we are on Avaya IPO 10.1 SE and I'm trying to connect 3CX via a SIP trunk and rules to make and receive calls using a line in IPO. I followed the guide that I found posted here, however I can't make, receive, or do an extension call between systems.

Any insight would be helpful. Here is what I have done so far:
Configured Generic SIP trunk. (IP blanked out is IPO IP)

I then set an ICR for DID 2000 as set in the trunk to deliver to my test extension:

Here are the two outbound rules. One for 10 digit dial of an external number, the other for 8+ 4 digit extension to connect to Avaya extensions

That's everything I did on the 3CX side. Now here is what I did in Avaya IPO:
Created a SIP line with ITSP as the Avaya IPO

Set ITSP Proxy as 3CX and selected LAN1 connection which is the network 3CX currently resides.

Set URI to auto and inbound / outbound line groups as 17

VOIP Settings...

And in the ARS of our actual production SIP line, set the following short codes. To note, we do have a couple lines setup here as we use a couple SIP providers, but for testing this is the line we would like to use:

I know this post is super lengthy, but any advice as to what I could be missing would be greatly appreciated. For now I'd like to complete an extension (3CX) to extension (IPO) call and visa versa. I think once I complete those settings, I can figure out external dialing from 3CX and the ICR from the DID to Avaya to 3CX. Thanks in advance.

 

[jmatano]

A little update, if I dial the short code to engage the outbound calling of that line (5) and then follow it with a 3 which is the short code I have in ARS, it will ring the line in 3CX and show the proper extension CID!

However when I try to dial back the extension, I receive this:

SIP Server/Call Manager ID: 12294
Call or Registration to 8379@(Ln.10001@SIP Connection to Somerset Avaya) has failed. 192.168.x.x replied: 404 Not Found; from IP:192.168.x.x:5060

 

[YiannisH_3CX]

Hello @jmatano

Is the issue only with outbound calls from 3CX to Ayava? If so try to simplify your outbound rules.
Create a new outbound rule and only set the prefix you will use to pass calls to Ayava. Then remember to strip the prefix and select the correct route. Move the outbound rule to the top of the list and try again.