1 / 7

Unity Connection 7.1 Accept and Relay

Unity Connection 7.1 Accept and Relay. Aaron Belcher. Message Actions in 7.0: background. Unity Connection 7.0 supports the following Message actions: “Accept”, “Relay” or “Reject” incoming messages. They can be configured independently for each message type, voice, email, fax or receipt.

violet-jones
Download Presentation

Unity Connection 7.1 Accept and Relay

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Unity Connection 7.1 Accept and Relay Aaron Belcher

  2. Message Actions in 7.0: background Unity Connection 7.0 supports the following Message actions: “Accept”, “Relay” or “Reject” incoming messages. They can be configured independently for each message type, voice, email, fax or receipt. “Accept”: Messages are delivered to the recipient’s voice mailbox. “Relay”: Messages are sent to a single relay address. “Reject”: Messages are NDR’d. Unity Connection 7.0 supports “accepting” or “relaying” a message, but not both.

  3. Message Actions in 7.0: Example In this example the recipient is configured to: Delivery voicemails to their voicemail box. NDR email messages that are sent to the voicemail box. Send fax messages to the users corporate email account of “aaronb@cisco.com”

  4. Message Actions for 7.1: “Accept and Relay” Unity Connection 7.1 adds the “Accept and Relay” message action. “Accept and Relay”: Messages are delivered to the recipient’s mailbox and sent to the relay address. If the message can’t be delivered to the recipients mailbox it will be NDR’d and no relay message will be sent. Even if the message is delivered to the recipients voice mailbox, the corporate email system can still NDR the message so the sender may receive an NDR if the message was partially delivered. Since this is confusing to the sender, we recommend relaying messages to addresses that are unlikely to generate NDRs like the corporate email system and not external email addresses.

  5. Main use cases… It’s primary use case is to allow users of Outlook Web Access or email synchronization tools like Blackberry to see a copy of the message. (If the client supports IMAP directly it’s usually a better option.) This use case is better then not having the feature, but it isn’t ideal because the user will have to delete the messages twice and their MWI light will only go off after they have read or delete it in their voice mailbox.

  6. Additional Configuration options… There are two configuration options in this web page in the Unity Connection Administration pages: “System Settings”->”Advanced”->”Messaging” “Allow Relaying of Private Messages” (Default: Enable) “Allow Relaying of Secure Messages” (Default: Disable) If relaying of a message type is configured, but “relaying” is disallowed by one of these settings the message will be NDR’d and not delivered at all.

More Related