CUC 8.5 MWI with Single Inbox Exchange 2010 seems slow and sometimes unreliable

[Roman Rodichev]

Hi,

I have some issues with MWI for Single Inbox Exchange 2010 + CUC 8.5-HA (latest). When leaving voicemails, sometimes it takes up to 10-20 seconds for Exchange to deliver MWI message. Sometimes it doesn't work at all. CUC mailbox shows that the MWI should be on, but the Exchange Inbox has no unread voicemails. It's either an issue with Exchange not delivering notification (doubt it), or CUC not working.

The message delivery into Exchange works perfectly fine. MWI ON is fast (but that's because CUC turns it on right away). It's EWS syncing back to CUC is very flaky.

Has anyone else had issues and found a good way to troubleshoot it?

On Exch2010 in event viewer I see events like this:

A notification for subscription [HABzdi1hcHBzMDUucmZ0ZWNobm9sb2dpZXMuY29tEAAAAEXPGeSxS3VJiTdeopQts9diaTpYTOXNCA==] against endpoint [http://10.0.16.11:7080/NotificationService/services/NotificationService?id=7682d009-ad26-4644-a323-eb4f198792bd&pid=8104] couldn't be sent. (Send attempts: 2) Details: WebException: The remote server returned an error: (503) Server Unavailable. StatusCode: ServiceUnavailable javax.servlet.ServletException: org.apache.axis2.AxisFault: The system is attempting to engage a module that is not available: addressing    at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)

   at Microsoft.Exchange.Services.Core.NotificationServiceClient.HandleResponse(IAsyncResult responseAsyncResult)

After 5 unsuccessful attempts to send a notification for subscription [HABzdi1hcHBzMDUucmZ0ZWNobm9sb2dpZXMuY29tEAAAAL0DSwmaIBVKo+9/O78sdvlCIvCgS+XNCA==] against endpoint [http://10.0.16.11:7080/NotificationService/services/NotificationService?id=d180f943-1401-4a24-9eb0-19f3b1b5b997&pid=8104], the subscription has been removed. Details: WebException: The remote server returned an error: (503) Server Unavailable. StatusCode: ServiceUnavailable javax.servlet.ServletException: org.apache.axis2.AxisFault: The system is attempting to engage a module that is not available: addressing    at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)

   at Microsoft.Exchange.Services.Core.NotificationServiceClient.HandleResponse(IAsyncResult responseAsyncResult)

This is the full error that I see when going to that link from the web browser on Exchange server:

HTTP ERROR 503

Problem accessing /NotificationService/services/NotificationService. Reason:

    javax.servlet.ServletException: org.apache.axis2.AxisFault: The system is attempting to engage a module that is not available: addressing

Caused by:

javax.servlet.UnavailableException: javax.servlet.ServletException: org.apache.axis2.AxisFault: The system is attempting to engage a module that is not available: addressing
     at org.eclipse.jetty.servlet.ServletHolder.makeUnavailable(ServletHolder.java:394)
     at org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:432)
     at org.eclipse.jetty.servlet.ServletHolder.doStart(ServletHolder.java:245)
     at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55)
     at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:694)
     at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:193)
     at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:913)
     at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:584)
     at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:341)
     at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55)
     at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:164)
     at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:161)
     at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55)
     at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:164)
     at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55)
     at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:92)
     at org.eclipse.jetty.server.Server.doStart(Server.java:232)
     at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55)
     at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:990)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:955)

---

Powered by Jetty://

Update:

I'm running 8.5.1ES16.11900-16

They are apparently up to ES44 now, TAC will provide me with it, and I'll let you know if it solves the problem.

[Roman Rodichev]

ES44 might have resolved it, but it's too early to say. ES16 was working for a while too.

[DAVID CHADWICK]

We are having a similar issue, however the MWI never gets updated from exchange 2010 to Unity and when we delete the VM the VM is not removed from Unity.

[craig.pollitt]

Same here...glad to see I'm not the only one having this issue.  I've tried both Accept/Relay Message Actions under UM Service and my MWI doesn't get updated from my Outlook client.

Anyone have any ideas?  Looking at other posts, it appears as though others have the single inbox feature to work as I would expect it.

Thanks.

Craig L. Pollitt

[DAVID CHADWICK]

Hello,

    MWI will turn on or off during the normal sync times that unity performs. The problem we found is I did not understand what unrestricted meant when downloading and installing the product. Unrestricted has nothing to do with the featureset of the product and becuase I installed the unrestricted version the service responsible for turing off the MWI is not installed. I am now in the process of backing up the users, messages, etc... and will be rebuilding the server from scratch.  I hope this helps.

[Brad Magnani]

Hi David,

I just wanted to clarify that whoever told you that the Unrestricted version of code doesn't dial MWI is wrong.  The Unrestricted version has to do with certan countries who enforce strict security laws with the use of encryption.  The Unrestricted version is meant for these countries.  This version has absolutely nothing to do with MWI working or not.  Both Restricted and Unrestricted have functioning MWI.  Here is an explanation of what Unrestricted has vs. Restricted for anyone looking to understand the differences:

http://www.cisco.com/en/US/docs/voice_ip_comm/connection/7x/release/notes/715cucrn.html#wp582698

Hope that helps,

Brad

[DAVID CHADWICK]

Cisco TAC said the service that exchange 2010 notifies on the server does not get installed. The notification is sent to a web address that Jetty is supposed to respond to and the service just does not exist. I was told to install the restricted version to resolve this problem.  I have requested copies of the documentation from Cisco to verify these results and find whether or not the statement was true.

[DAVID CHADWICK]

Cisco SRN 618018365

[Brad Magnani]

Hi David,

When you mentioned "I installed the unrestricted version the service responsible for turing off the MWI is not installed.", this service is actually the Connection Notifier service, which exists on all systems.  This is the service I was under the impression you were referring to with regards to MWI.  Now that you're referring to something else, it changes the situation a bit.

The Connection Jetty and Connection Exchange Notification Web Service both should exist regardless of Restricted/Unrestricted.  Something must have happened with your installation if the Connection Exchange Notification Web Service does not exist.  If you're in the US, you should be running the Restricted version of the software, so it's still in your best interest to move to the proper version of the software.

Brad

[DAVID CHADWICK]

I called into the TAC to get a verification on this issue with another engineer. The service that did not get installed was the Connection Exchange Notification Web Service. Rebuild Server was the answer.

[DAVID CHADWICK]

Resolved. This service was deprecated in version 8.5.1-43. The features are not built in to other services. The problem turned out to be Exchange 2010 and having Rollup Update 3 installed.

[DAVID CHADWICK]

Rebuilt Server. No service. Service does exist in the CLI service list, but not activated. Does not show in the Base Services under the web interface and at this point no one knows the answer on how to get the service to work.  I love this cisco development falling on its dairy airy.

[BEN ROBINSON]

We are having the MWI/voicemail sync issue with Exchange 2003 - anyone have ideas on that?

[benbollinger]

Did you ever get resolution on this problem?  We're having the same thing with Exchange 2007 and Unity connection 8.6.

[DAVID CHADWICK]

The service is no longer needed in 8.5-4x and up. 8.6 does not need it as well. The problem is that you must have update rollup 2 or higher on exchange 2010 pre-sp1, sp1 and higher.