IPO <-> CM 1

[bostong3]

Hi, I recently inherited an IPO 4.2 (IPO Manager 9.1.3.0) that hasn't been well maintained for years. I'm well versed in CM and know enough SM to get me in trouble, but IPO is completely foreign to me, so please bear with me...

I have a need to take certain incoming #s to the IPO and send them to extensions on the CM. I have a SIP trunk going through my SM and delivering these calls to the CM extensions, however, I can not get the original caller ID to follow. End up seeing the transferring #. This isn't a huge deal, but if it's fixable, I'd love to know!

My main problem is that the CM extension needs to send the call back out of the E1 on the IPO. I believe the routing on the CM and SM are correct (or close), but the call is being rejected on the IPO. I don't know enough about incoming call routes, ars or short codes to have a clue what I'm doing on this side.

Any help would be greatly appreciated. TIA!

 

[Okkie26]

Build a H.323 trunk between the IPO and CM.

Make sure you enable QSIG on this trunk.

 

[bostong3]

Hi, Thanks for your response. Even with an H323 qsig trunk, won't there need to be some routing programmed on the IPO? What do do with calls coming from this trunk?

Thx

 

[Okkie26]

Yes of course you need to setup routes..

 

[bostong3]

OK, that's the part I don't know how to do... thx

 

[Okkie26]

shortcodes

xxx , Dial, N, yyy

where xxx is the numer you want to route (3 digits in this case).
N is justr N (repeat xxx)
yyy is the outgoint ID to the CM.

 

[amriddle01]

You won't need to add routes on the IPO for calls coming in, it will match extns and system shortcodes by default

 

[Okkie26]

Of course I meant outgoing route....

 

[montyzummer]

https://support.avaya.com/css/P8/documents/003880269

ACSS (UC/SBCE/SM/SME)

Not that they mean a thing anymore , get a brain dump pass the test crash the system.

 

[montyzummer]

apologies

actually this one

https://downloads.avaya.com/css/P8/documents/100164747

ACSS (UC/SBCE/SM/SME)

Not that they mean a thing anymore , get a brain dump pass the test crash the system.

 

[amriddle01]

I know you did Okkie, the OP however said:

Even with an H323 qsig trunk, won't there need to be some routing programmed on the IPO? What do do with calls coming from this trunk

 

[intrigrant]

To forward the original caller ID try this

xxx ,Dial, Nss, yyy

A Qsig trunk on IP Office does not look at the Incoming Call Route table that is why each incoming call must match a extension number, group number or shortcode.

And the extension numbers in IPO may not overlap the extension numbers on CM.

 

[bostong3]

Hi All, Thank you so much for your help!! It took a while, but I think it's working well enough that the group that needs this will be happy. As of now, the only "issue" is that the incoming call on the CM shows the incoming CID as both the # and name. I'm fine with that, unless it's an easy fix. All this rebooting to make changes to trunk groups makes me anxious!!

Thank you again!!

 

[montyzummer]

On page 3 of the trunk screen on CM play with the send name and number fileds (assuming you have set up a h.323 trunk) , personaly if you are licensed i would go with SIP trunks.

ACSS (UC/SBCE/SM/SME)

Not that they mean a thing anymore , get a brain dump pass the test crash the system.

 

[Okkie26]

Why go for SIP instead of a Avaya H323 protocol?