Unity Connection 8.X, Exchange 2010 and Blackberry Enterprise Server Express

[keithknowles]

Hello All,

I am using Unity Connection 8.5 with Unified Messaging enabled for Exchange 2010 and am running into an issue where voicemails are taking 5 to 15 minutes to be delivered to Blackberry smartphones that are integrated to the same Exchange 2010 environment using Blackberry Enterprise Server and/or BES Express.

Things to note:

1.  All other messages are delivered to the Blackberry instantly, only voicemails are taking time to appear on the devices.

2.  Voicemails show up in Outlook and Web Exchange immediately, and if the Blackberry is accessing Exchange email via IMAP rather than BES/BES Express they show up in the same time frame as any other message.

3.  This occurs on both Exchange 2010 and Exchange 2003 environments when using a BES or BES Express server for Blackberry access.

4.  Once message has been delivered the read/unread effect on the MWI is instant, as well deleteing the message from the email inbox instantly removes it from the voicemail inbox as expected, its just the initial delivery that ius affected.

I suspect that Unity Connection is "placing" the message into the users Exchange Inbox rather than sending it as an email and this may be why the BES / BES Express server is taking a while to pick it up, however, we used the same setup with our Unity server and never had this occur though it does single-inbox differently than Unity Connection.

If anyone can shed some light on the occurance it would be greatly appreciated, thanks.

Keith Knowles

[sidharthjain]

Hi Keith

We are facing the same exact issues with Blackberry devices. I have seen some other posts as well pointing to the same issue. Let's see what feedback I get from Cisco

Another problem I ran into was with Digital Networking. Digital Networking requres unique location and smtp host names. I have 2 Connection clusters in the Enterprise, I was able to use @CompanyDomain.com as SMTP for one cluster, but I can't use the same for the other cluster as that violates the Digital Networking requirements. Hence I have to use @appliance.CompanyDomain.com. This results in having us to manage multiple domain names in the Enterprise.

Hopefully Cisco comes out with a SR to address both issues.

[Brad Magnani]

Hi Keith,

Please see the following doc and tracking defect for your BES delay:

http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/unified_messaging/guide/85xcucumg020.html#wp1245103

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCto23780&from=summary

Hope that helps,

Brad

[tonyperla · Accepted solution]

If you haven't found out yet,  there has been a fix for this issue.  Let me start out by saying that  the BES environment has to be at version 5.0.3 MR5.  Then on the UCONN  side you can either upgrade to version 8.5.1su3 depending on the version  you are on or you can contact Cisco TAC and request ES 65 for UCONN  8.5.1su2.  You will then have to apply the ES and then run some commands  via the CLI in order to "activate" the ES.  Here is the Cisco bug  information.  I hope this helps.

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtk52978