AAM SIP MWI issue

[CherokeeBob]

Hello everyone,

I'm having a weird issue with MWI in CM 7 & AAM 7. Here's the scenario..

Customer has recently been deploying sip phones (j1xx, vantage, equinox soft-phone clients, etc) instead of H.323.

MWI will light for H.323 phones roughly 2-3 seconds after a voicemail has been left. Great!

SIP phones will only have MWI lit when they are rebooted/log out and log back in.

Logs shows that AAM is sending the subscribe/notify immediately and that CM receives it.

However CM is not sending to the SIP phones.

Not sure why and cant find much on this problem. Any help would be appreciated.

 

[ZeroZeroOne]

I suggest going through the checklist in this thread as a starting point:

https://www.tek-tips.com/viewthread.cfm?qid=1723411

It's just a guess but it certainly won't hurt to double check these settings.

 

[avayaguy23]

So several things changed from AAM 6.3 to 7.x. The major change was around mwi. In 6.3 mwi was served by the app servers. That has completely changed in 7 where your axc is now your mwi engine. It sounds like you have your sip trunk built because it works fine on h323 but did you include your aura messaging servers in their own system manager location? Locations come in to play when it comes to SIP.