MM with CUCM or CM with Cisco Unity?

[jmac9068]

Hello,

I am trying to configure my MM 5.2 system to work with my Cisco CUCM system. The MM has a SIP trunk configured to CM 6. CM has a SIP trunk to CUCM Session Manager. Session Manager has a SIP trunk to CUCM. Call flow is Avaya phone thru SM to CUCM/VM pilot back to Avaya CM thru SM and ultimately to MM.

The calls work perfectly. I am able to leave a voicemail for the Cisco phone on MM and I can retrieve the call from Cisco phone without a problem. The only thing that does not work is MWI. Has anyone tried this and gotten MWI?

If not, has anyone tried the same scenario with an Avaya phone using Cisco Unity voicemail? All works except for MWI. I am trying to centralize on one VM platform and this is the last step.

Thanks!

 

[KenMeans]

You do not want to change any of that then.

I would review the document below in detail and make sure the PBX is setup per the config note below as well as the MM

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

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[jmac9068]

I have verified that my setup is configured the same way as the document that you sent the link for with one exception. On page 11 the node name for the MM server is shown as having a type of MM instead of IP or AUDIX. That is not an option on my system. It is either IP or AUDIX.

 

[KenMeans]

Not sure but i think you add the node name and type when you build them. i am a little weak on the PBX side any more.



Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[jmac9068]

I can enter "change node-names" on the PBX and my only options after that are IP or AUDIX. I cannot add anything as an MM type, however I doubt that would be the crux of the problem with getting the MWI across to an H.323 phone registered to the PBX.

 

[KenMeans]

i think you are correct

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[jmac9068]

I was able to find the answer. It turns out that having the MM SIP trunk to Avaya CM was a bad idea since it was not forwarding all of the SIP messages from MM to Cisco. I created a SIP trunk from MM to Avaya Session Manager and routed the calls to both Cisco and Avaya CM through it. That got lamps to light for both Cisco and Avaya.

Since we are not using the Avaya Session Manager for call routing, but we are using Cisco Session Manager, we built a SIP trunk from Cisco SM to MM. This scenario also allows us to light lamps for both Cisco and Avaya phones. Thank you for all of your help on this.