120 likes | 236 Vues
VMO and SMTP TOI. Aaron Belcher. VMO for Unity Connection Similarities. Works with Outlook 2003 and 2007. Same user interface you know and love from Unity. Same media player with same features speed control slider, pause, location slider, accessibility hotkeys, ect..
E N D
VMO and SMTP TOI Aaron Belcher
VMO for Unity Connection Similarities • Works with Outlook 2003 and 2007. • Same user interface you know and love from Unity. • Same media player with same features speed control slider, pause, location slider, accessibility hotkeys, ect.. • Same features set including secure messaging and Trap record/playback.
VMO for Unity Connection differences • Secure messaging and Trap record/playback uses HTTPS • Newer more modern setup. • SMTP routing improvements to work around Outlook’s address books. No need for duplicate entries like “John Doe” and “John Doe – Voicemail” (Discussed in detail in the next slide.)
End user difference between Unity and Unity Connection’s Integrated messaging model. • In Unity Integrated messaging users have two entries in the directory. The user has to pick the correct one so the message shows up in the voice mailbox. For example, “Aaron Belcher” and “Aaron Belcher – Voicemail” • In Unity Connection we don’t modify the directory so there is only one “Aaron Belcher”. The message is sent to the correct mailbox by using the correct account to send the message. If email client sends the message through the corporate email account the message ends up in the corporate email box. If email client sends the message through the voicemail account it ends up in the voice mailbox. • This model is mostly transparent to end users, because email clients default to sending forwards and replies to a messages through the account the message arrived in, so forwards and replies to voicemails end up as voicemails. • The model is also transparent to end users when generating new voice messages from the email client. In order to generate a new voicemail end users have to use VMO and VMO sends all messages through the voicemail account. • If the user chooses someone from the directory who isn’t a voicemail user, the message will either end up being NDR’d or delivered to the recipient’s corporate email mailbox.
New concepts to support addressing messages from email clients. • SMTP Proxy addresses: Additional SMTP addresses that each subscriber can have. Message sent to either the subscribers primary or proxy addresses are delivered to the subscriber’s mailbox. The subscriber’s SMTP proxy addresses usually match the subscriber’s corporate email addresses. Examples: • firstname.lastname@example.org • John.Doe@cisco.com • Message Actions: Configures how the system handles messages of specific types. • Types: Voicemail, Email, Fax, Delivery and Receipts. • Actions: Accept the Message, Relay the message, or reject the message. SMTP Proxy addresses and Message Actions are per subscriber settings that can be configured in build with Bulk Edit or Bulk Administration Tool.
New server settings to support receiving emails through SMTP • System Settings->SMTP Configuration->Server • Allow Connections From untrusted IP Addresss: If it is enabled, SMTP connections are allowed from any IP addresses. (Trusted IP addresses are ones specifically allowed in the access list, authentication and TLS is never required from them.) • Require Authentication from Untrusted IP addresses: If it is enabled, we require for the SMTP “Auth Login” command to complete successfully before we allow the connect to send a message. • Transport Layer Security From untrusted IP Addresses: • Required: If the connection doesn’t use TLS, the server will not allow it to authenticate • Optional: The server will allow in either TLS or a none TLS connections (Recommended) • Disabled: The server doesn’t offer TLS. • System Settings->General Configuration • “When a recipient can not be found”: • “Send a non-deliverable receipt”: When this option is selected the connection server sends an NDR when the recipient can’t be found • “Relay message to smart host”: When this option is selected and the recipient is not found the message is sent to the smart host to be delivered to that recipient. This is usually done so it can be delivered to a remote user’s email mailbox.
Addressing and Messaging Routing flow There are also message handling properties that can reject, relay, or accept messages based on message types. Reject: NDR’s Relay: Sends message to different email address. Accept: Adds it to mailbox. For example, a user may want email messages and NDR’s in their corporate account instead. If authentication is turned off and the sender doesn’t have an SMTP address in our system this will fail and the message will be sent to badmail. If the recipient doesn’t have a proxy address we NDR it by default. There is also an option to forward messages to unknown recipients on to the smart host to be delivered in their email accounts... If authentication is turned on then the sender is checked here.
None-VMO Email Clients • Same features as 2.X UCXN. • Plus ability to “reply to” and “forward” a voicemail with Text and additional attachments • More limited then VMO: no secure messaging, no TRAP, ect...
Deploying VMO and None-VMO clients • Create proxy addresses for each users corporate address with either the Bulk Administration Tool or Bulk Edit. • Turning on the “allow access from untrusted IP addresses” option. • Setup a custom keypad mapping that allows users to list the messages attachment over the telephone if they exists. • Setup an IMAP and authenticated SMTP connection back to the server on each email client. • Install VMO if using Outlook and it’s desired.
Miscellaneous Trouble shooting Tips… • VMO traces: • Enable:Tools->ViewMail for Outlook Options->Diagnostic tab (Check all boxes.) • Can be collected in: %ALLUSERSPROFILE%\Application Data\Cisco Systems\VMO\1.0\Logs • Server side traces: • Service: “Connection SMTP Server”, Component: “SMTP”, (All traces) • Service: “Connection Message Transfer Agent”, Component: “MTA” (All traces) • Common issues: • Symptom: SMTP messages stay in the outbox. • Causes: • The sender doesn’t match a SMTP proxy address or primary SMTP address of a subscriber. • The message is larger then the max message size in the SMTP server configuration (defaults to 10 megs). • The address of the SMTP server is incorrect or blocked by firewal. • Trouble shooting: Hit the send/receive button in Outllook. It will include the SMTP error. Turn on the SMTP logs and the server and view them. • Symptom: VMO form doesn’t appear after an install. • Cause: • The Outlook process may not have exited. • Only new messages will be marked with the form. • The VMOExchangeExtension has been disabled by Outllook. Lookin in Help->About Microsoft Office Outlook->Disabled Items.