Can Unity auto-forward messages to non-Exchange mail servers? In other words, can you have voice mail on the Exchange portion of the Unity box set up to auto-forward the messages to mailboxes on a non-Exchange POP3 mail server?<br><br>
Unity has a built in object just for such an operation called an Internet Subscriber. When you go to create a subscriber its available as a radio button there. This builds a custom recipient in Exchange (a mail user without a local message store basically) and we add Unity subscriber properties for it. In short this guy appears to other subscribers and outside callers as a normal subscriber: they have greetings, a voice name, you can do transfers with them etc The only real difference is the messages taken for this guy are not stored in Exchange, theyre sent off to the email address you provide when you create the internet subscriber.
If thats not what youre looking for, you can create rules in Exchange that will copy or move messages of particular types (or that use particular Outlook forms ViewMail for Outlook in the case of voice mail messages) to other mailboxes or to off-Exchange mailboxes via SMTP. Youd do this if you wanted just voice mail messages moved but you wanted the user to have a local mail repository for email not sure why this would be desirable, but you never know.
Thanks for the info. I do have one other question. When unity forwards the message to the external email server, how is the message indicator light on a call manager handled? Will it be turned off if the message is checked by the end user?
Unity does MWI (and notification dialouts) based on the message state of an Exchange mailbox. If you're moving voice mail messages out of an Exchange box to an off box email store, Unity will truck out to the Exchange mailbox, do a filter for unread voice mail messages, come up empty and turn off the MWI for that user.
If you're asking about MWIs for internet subscribers, Unity doesn't do that. These guys have no Exchange mail store for us to monitor so MWIs and notifications wouldn't make any sense.
I'm not entirely sure where you're going with this...
If you're sending messages off site as you mentioned earlier in the thread, you'll be using SMTP with the Exchange IMC and the container information obviously wouldn't have any bearing here. This is the case if you're going to be using Internet Subscribers (custom recipients in Exchange).
If you're setting the Exchange mailbox to forward all messages or some messages to another Exchange user, it's only necessary that the destination Exchange server be in the same organization if you want to use the MTA transport mechanism... but of course you can always use SMTP again here and send it wherever you want.
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...