There are some messages that suppose to go to the subscribers mailbox goes to unaddressed messages(To Example Administrator) which are very hard to find out whom actually it belongs to, unless they mention the name in the message. Why do messages goes as unaddressed messages(To Example Administrator) and how to minimize this kind of messages?<br><br><br>
First, why do messages go to the Unaddressed Messaged distribution list?
The short answer is any time Exchange cannot deliver a message to someone weve asked it to, it returns the message to the sender as Non Delivery Receipt (NDR). For subscribers leaving messages for other subscribers this is no problem. If the message cant be delivered for some reason (Exchange account removed, message store size exceeded etc ) the NDR ends up in the inbox of the person who sent it letting them know it didnt get there. In the case of an outside caller (i.e. a non subscriber) these messages are left from the Unity Messaging System account we create at install time. If the message cant be delivered, its returned to this account as an NDR by Exchange, of course. Every several minutes we check the inbox of this account and if a message is found there, we forward it to the Unaddressed Messaged public distribution list to make sure someone is looking at them.
Second, why cant you see who theyre addressed to? This one is easy, you can. When the NDR shows up in Example Administrators inbox its a forwarded message. When you open it, youll see another email as an attachment. When you open that email attachment you should see the original message itself, including the person it was originally addressed to and the attached WAV file.
Finally, how to minimize the number of these messages. Well, first we have to find out why theyre not be delivered. Theres a couple of common scenarios I run into fairly frequently. If the subscribers inbox is full (as defined in the Exchange administrator) all messages sent to that inbox will bounce back to the sender. Just like if you sent them an email from the desktop, it bounces back at you works the same for voice mails. Make sure your folks have appropriate message limits defined.
Folks sometimes delete Exchange accounts and leave stranded call handlers out there that are set to leave messages for folks that no longer exists which can also result in NDRs like these. Unity 2.4.0 and later has a utility called SysCheck that can find these types of illegal links for you easily. If youre on a version of Unity earlier than that, you can download the DBWalker utility off my web page which does the same types of checks on your system and reports any inconsistencies for you.
The network being down or a link to one or more other Exchange servers in the site being broken for a period of time can also cause this. The MTA in Exchange will try to get the message to its addressed destination for 24 hours, after that it will fail it and send it back as non deliverable.
Finally, Ive also seen folks use the Unaddressed Messages Distribution list as the primary message recipient for, say, the Operator Box or a public interview box or something. This is a bad idea this Distribution List is intended to be used only for handling messages left from unknown callers that Exchange could not deliver properly. You might check for this that would be consistent with you not seeing who the message was addressed to since it was sent DIRECTLY to the unaddressed messages DL.
Hope that helps
Jeff Lindborg Unity Product Architect Active Voice Corp email@example.com
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...