If you have decided to integrate your Unity server with Exchange 2010 environment for unified messaging, and you have also decided to configure your Exchange 2010 server cluster to include an array of Client Access Servers (CAS) interfaced by a Network Load Balancer (NLB) appliance, then you should consider the following caveats.
Make sure you have followed all of the steps outlined in the Guide:
Using Microsoft Exchange 2010 with Cisco Unity Versions 8.0, 7.0, and 5.0
To communicate with the Exchange envrionment, Unity leverages Microsoft's Messaging API, MAPI. Part of that communication process involves opening a MAPI connection between the Unity server and an available Exchange CAS server. Once this communication path is established, the Exchange CAS server will use this session to field requests from the Unity server. You must configure your NLB to always relay packets from the Unity server in this session to the same CAS server until the session is terminated. This behavior is often referred to as "Session Persistence" or "Port Affinity" or "Sticky".
If you're currently using a Unity server and Exchange 2010 server and NLB in the configuration described above already and you're experiencing problems with that communication path, verify the following.
Check the Unity server's application event log and/or Unity diagnostic logs for instances of error code 0x80040115 or MAPI_E_NETWORK_ERROR. If this return code is being returned by the Exchange 2010 environment, you may be experiencing a problem with the NLB session persistence or port affinity.
Use a packet sniffer to determine if MAPI from the Unity server is consistently being forwarded to the same CAS server.
What breaks the communication with MAPI is when a connection is established thru the NLB and it routes it to say CAS1, then while still using the same MAPI connection the NLB round-robins it over to another CAS server other than CAS1. Since the other CAS servers are not in the same MAPI state as CAS1 any MAPI request made from that point forward will be invalid thus causing a E-MAPI NETWORK ERROR.
We have CCM 11.5 along with gateway 2811 cube, C2800NM-ADVENTERPRISEK9-M), Version 15.1(4)M10 configured as CUBE gw. All sip.I had similar issue https://community.cisco.com/t5/unified-communications/redirected-calls-doesn-t-show-external-phone-mask-a...
Hello,I hope I'm asking this question in the correct forum.We are looking at using Cisco WebEX for our telephony solution (very small SMB). We were just wondering if Cisco is using Cisco Unity Connection as the voice messaging service??? We we...
Guys, can someone please help me out I just wana have the Call.CallingLineID on my routing script, i know the reservation call passes through the script but it does not have any ANI to it, is there a way i can get that onto my script?? Any help or cl...
Hi, we recenlty integrated our AD to call manager, however a we left he Phone number attribute to telephone. this has messed our corporate directory. we need to change the phone number attribute to IPphone now and perform a sync, we are un...