Integrating Cisco Extensions with Avaya Modular Messaging

[gunaji]

Hi everyone,

I am working on a project where we have a solid Avaya CM5.2.1 integration with Modular Messaging over an E1 PRI trunk group using QSIG. It works great for Avaya endpoints. We recently installed a Cisco Unified Communications PBX and have a T1 PRI trunk, also using QSIG, to our Avaya switch. When a Cisco endpoint calls the pilot number directly, MM answers the call integrated (that is it goes into the end users mailbox directly). When another extension tries to call a Cisco endpoint and then redirects on call forward/no answer or call forward/all calls, the Modular Messaging system answers non-integrated (that is the general attendant answers the call). After a couple of rounds with Cisco and Avaya engineers it is clear that the issue lies with the redirect format coming from Cisco or how the redirect message is crossing the Avaya PBX from the Cisco Trunk to the MM trunk. The symptom I see on the MM is the called party extension shows the MM pilot number and not the called Cisco extension number. Has anyone out there had issues with this integration? Does anyone know how I can manipulate the fields in the messages across the QSIG trunks? Any help or guidance would be greatly appreciated.

Shannon

 

[texeric]

Avaya does not support users on a different PBX other than what MM is integrated with. In your case, the supported way would be to integrate both PBXs to MM using MM's Multi-site method.