IPO Server Edition - Outgoing calls using IPOV2 Gateway's trunks 2

[hcmbmt]

We have IPO Server Edition R.11 with 1 main server, 1 secondary and 3 IPO V2 Gateway - Number 1, 2, and 3.
It's no problem with Incoming calls (can route call to any destination in system) and Internal.
However, I got trouble with Outgoing call:
- Users of Main Server/IPO V2 Gateway Number 1/Number 2, cannot access to Trunk of Gateway Number 3 for outgoing call. Phone shows that Incompatible, no line....
But It's ok for users from Gateway 3.... I already create short code on each system map to Outgoing Group ID of Trunk on Gateway No.3. But seems like system doesn't get it.


Anyone knows how to configure then Users can access any trunk for outgoing call.

Thanks,

 

[TouchToneTommy]

On each unit, SE and Expansion units, you need to have an ARS table that receives your outgoing number, adds the dial out code for gateway 3, and used the outgoing line group of the IP Office line from that unit to unit number 3.


For example, I'm on the SE. The IP Office line from the SE to the Expansion unit is 99001.
The Dial Out Code on the SE is 9, on the Expansion it is also 9
On the SE, 9N / Dial / N / 51:ARS Unit 3, where
ARS:51 has an entry N; / Dial / 9N / 99001
This sends the number (N), preceded by 9, over to the Expansion unit
On the Expansion unit, 9N / Dial / N / 50:Main
Which is N; / Dial3K1 / N / 100
which is the Outgoing Line Group for a PRI

With some preplanning, and shortcodes between units, you can route calls through all of your expansion units, sending outbound caller ID and fallback to alternate ARS tables that might target a completely different expansion unit

 

[hcmbmt]

@TouchToneTommy
Follow your instruction and it works. Thank you so much.