External PBX connected via SIP trunk to R11 IPOffice, looking to dial out 2

[cbsage]

Can anyone help with a question, possibly an issue, with IPO R10.1? I have a customer with an external PBX need that will want to allow extensions on that PBX to make outbound calls to the outside world. The other PBX is a simple "RCare" nursecall system for use on smartphones via an app. They register to a 'headend' of RCare software and then route to the IP Office over a SIP trunk in order to call extn-to-extn. The IP Office is a simple IP500v2 with a PRI connected to it, just one processor, one site, multiple expansions. Extensions on the IPO have access to call out via the PRI (locally connected), whenever they want (via SystemShortCode/UserRights/ARS.) The external PBX is connected via a SIP trunk to the IPO. I can setup, and have setup before, an Incoming Call Route to allow extension-to-extension dialing. That works fine. My issue is with setting up those external PBX extensions to be able to dial outbound to/via/using the IP Office's PRI circuit. Essentially a SIP trunk-to-PRI-trunk transfer which preserves the digits they dialed so their calls go out the PRI to whomever they want. What codes or 'destinations' are needed in the Incoming Call Routes that will gather the "dialed digits" of those external PBX extensions and allow them to make calls based on what they dial??

I hate sounding like a 'noob' here, because I'm not, just in "SIP language-land". I've used IP trunks and the associated "Short Codes" tab and entries to route this way, but SIP trunks don't show the same availability to me. I've just never set one up this way and I NEVER FAIL to have problems finding anything in Avaya's documentation on things. Tek Tips has always been my go to for good info. I'm just not seeing anything specific to this on here right now.

Fyi, standard settings on the SIP trunk as of now. Not a lot of customizing other than the target IP (see my above lack of travel in "SIP language-land". IPO is release 10.1.04, build 7

BTW, this site has bailed me out with info quite a few times, at least confirming what I knew, or steering me in the right direction. Always happy to lend a STAR. Any help or re-direct to an existing thread would be greatly appreciated.

Thanks,
cbsage

ACSS since 2006, (even when they change the alphabet soup of certs, I re-up)

 

[TouchToneTommy]

One of the simplest ways is a single incoming call route for the SIP trunk, nothing in the Incoming Number field, and a single period in the destination. So whatever digits come in from the SIP will be routed to whatever extension, group, or system short code that matches.

Have the SIP trunk send just the digits of extensions for phone to phone calling.

Have the SIP trunk send 9 followed by 1 AreaCode TelephoneNumber, and have your regular 9N system short code route the call to the ARS table that sends the call to the PRI.

 

[Qzwsa]

If you set the ICR of the incoming SIP trunk with no received number and a destination of "." - a single period - then it will route calls to whatever they dialed. So your nurse call sends 202 - it routes the call to x202. If your nurse call sends 9XXXXXXXXXX then it will route calls to the 9N system short code and out to the number via your ARS table. You will need to ensure that the nurse call is set up to allow outgoing calls to the IPO to be more than just the local extensions.

-Qz

EDIT: Ninja'd.

 

[cbsage]

And BOOM, the lights go on!! Thank you TTT and Q for the knowledge and insight. I was aware of these settings, but as usual, only until they are pointed out in my case. Thank you both for pitching in. This sounds like it will work as advertised!

cbsage

ACSS since 2006, (even when they change the alphabet soup of certs, I re-up)