Avaya Inbound PRI to Outbound SIP Trunk (to internal IVR)

[adc110]

I have an Avaya IP Office V2 9.1.9. with a full PRI for inbound calls and some SIP trunks outbound to an IVR (this is how our)
IVR works unfortunately. Our IVR has the ability to flash call information based on the DID that was called inbound on the PRI.
That being said I am looking for the most efficient way of handling inbound calls on the PRI such that I can pass the called party (DID)
4-digit information out onto the SIP trunk and into IVR. Here is a breakdown of my configuration where I can get this to work:

1. PRI 4-digit inbound (series 2300-2399)from carrier. I need to pass 2300-2499 to IVR over SIP trunk

2. I configured PRI with inbound/outbound ID of 0

3. I created SIP Trunk #17 with inbound/outbound ID of 1

4. I created a shortcode of 8N which dials an ARS table I createded called SIPOUT

5. The ARS table called SIPOUT and has a single entry with a code of XN; and telephone number of N, Dial line Line group ID#17 (which is SIP Trunk #17)"SIPOUT" has some test entries wherein when the telephone number (for example DID #2300 is received) it will dial my SIP Trunk
#17 with Line Group ID of 1. This entry allows me to dial the SIP Trunk 17 with the original DID and pass it to the IVR.

As a recap, an inbound call to DID# 2300 is received by an incoming call route with ID0, Incoming Number of 2300, Destination of 82300,
which hits the ARS Table "SIPOUT" and dials line ID#17 which is SIP Trunk #17 and the IVR receives inbound call id of 2300.

This works great but was wondering if anyone new of a way of capturing the original inbound DID (possibly with some Avaya variable)
and passing it back out to the SIP Trunk without making incoming call routes for all 200 DIDS?

To allow the IVR to dial outbound I created an incoming call route for SIP Trunk #17 with no incoming number and a destination of "."
so that the entire number that is received by the IVR (i.e. 91800xxxxxxx) would be received and IP Office would use the 9N shortcode and
process the outbound call which works nicely but is anyone aware of a "better" way?


Just passing this configuration along in the event it helps anyone but also to see if someone might have a more desirable way of
capturing inbound DID and passing it to the SIP Trunks.

Last quesion, I have dual IVR's (one active and one fail-over). My failover responds with a SIP Message "604 Does Not Exist Anywhere"
which when used in my ARS fail-over tables works nicely but I could not find any documentation that specifically states that IP Office
will automatically roll over to a another ARS table if this message is received. Apparently this is how our IVR responds when it
is not the active IVR but developer cannot confirm this (although it does work!).

 

[adc110]

I was able to accomplish what I needed. So perhaps this may help someone else:

I created an incoming call route that has the incoming number set to XXXX (4 X's as our carrier is sending in 4-DIGIT on PRI). Then I set the Destination to point to 7# (# captures the digits within the 4 X's & 7 is for a shortcode I created which is a dial action with a code 7N which points to my ARS table, which in turn has entries that dial out on the SIP Trunk to the IVR). This absolutely works perfectly and captures the appropriate DID information and re-sends it to the IVR.

I then did the reverse of this with the IVR. When the IVR calls out I created incoming call routes that have the incoming number set to 9XXXXXXX as well as a call route for 9XXXXXXXXXXX (this allows me to handle local 7 digit telephone numbers and long distance with 11 digits [needed to account for the 1]). These incoming call routes have a destination of 9# which uses the default shortcode of 9N and passes out to the default ARS table and sends the dialed number that the IVR sent outbound to the PRI.

All though it took a bit to figure this out - it saves a bunch of time in not having to create individual incoming call routes for a bunch of DID's as I simply re-pass the original DID information to IVR.