Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 
New Member

Unity and exchange

What happens in either Voice only messaging and UM environment if exchange server goes down. And CCM is up and running what will happen to Auto Attendant configured on unity server and Voice messages or email messages. What the caller will get as a response.

How many ports will unity use if single person wannna send for multiple subscribers for example 1000 subscribers. And how much time it will take for unity to send 5mins msg to all 1000 subscribers.

Cisco Employee

Re: Unity and exchange

You have a couple of very different questions tucked into this one post here...

first, if the Exchange server Unity is connected to is unavaialble (it's off line or our connection to it is broken or whatever) Unity will continue to function in "UMR mode" (Unity Message Repository). Unity stores messages from outside callers locally on the Unity box until the Exchange server is on line. The auto attendant continues to function normally in this case, the only difference is subscribers calling in to get messages can only get at those voice mail messages on the local box (i.e. those left since the connection was broken) and not at their Exchange inbox, of course.

Sending a message to a large distribution list works just as it does if you send an email from the Outlook client. Unity is sending the message in the same way and Excange takes care of getting it to the addressed users... this happens in a second... Unity doesn't make 1000 copies of the message to send out. Exchange uses a "single instance messaging scheme" where by a single copy of the message is stored on each server that houses on or more recipients and each of those recipients gets a link to the one copy of the message. This is an Exchange function, Unity is not involved directly in this process...

New Member

Re: Unity and exchange

With Unity 3.x, if Exchange goes down at any point, Unity will continue to take messages. These messages will be stored in the /commserver/unitymta folder. The autoattendant will function properly as well. When a subscriber goes to check his messages, he'll only be able to access messages which were left after Exchange went down (the messages in the unitymta folder). MWI won't work, and subscribers won't be able to delete messages. When Exchange comes back up, the messages will flush out of the folder and into the users' mailboxes.

As far as sending a message to 1000 users, only the one port the subscriber is calling in on will be used. And only one copy of the message per mailstore (I think it's per mailstore, but it could be per server) is kept. A pointer to the message is put in each destination mailbox. When the subscriber listens to the message, that pointer is marked read. When the subscriber deletes the message, he's actually only deleting the pointer.

CreatePlease to create content