Exchange 2013 UM Features and Architecture


Voicemail Preview

– Due to UCMA 4.0 and the Microsoft Speech Platform there are many enhancements to Voicemail Preview
– Voicemail Preview feature uses automatic speech recognition to convert the spoken voicemail into text
– Voicemail Preview is updated in Exchange 2013 to be more accurate and provide better performance
– Transcription now happens to all messages
Thanks to UCMAP 4.0 and the Microsoft Speech Platform (ver 11.0), there are many enhancements to Voicemail Preview.   The Voicemail Preview feature was introduced in Exchange 2010 and uses automatic speech recognition (ASR) to convert the spoken voicemail into text.  Voicemail Preview is beaning updated in Exchange 2013 to be more accurate and provide better performance.   Transcription now happens to all messages even if they are over 75 sec unlike previous versions.  If a message is over 75 sec, it is transcribed, but the text for the message isn’t included
Call Answering Rules
– Call Answering Rules were first introduced in Exchange 2010 , These rules can be setup based if you are on vacation or if a specific caller is trying to reach you, you can have UM forward the call to a different number as a few examples.  Parts of this feature have changed with UM 2013
– Feature empowered UM subscribers to control their Unified Messaging mailbox with rules
– UM can forward a call to a different number as an examples
– For GA, we will support ‘personas’ – persona is abstract representation of the various contacts for one person. Most like the contacts linking
Enhanced Caller ID support
– Previously if you were not in the same dial plan and someone called and left a voicemail you would get “Voicemail from Anonymous Caller“
– Exchange 2010 sp1 made some improvements on the heuristics of matching name to number
– Exchange 2013 looks in the default personal contacts folder and also in user and system created personal contacts folders
– This is important since Exchange 2013 supports Unified Contact Store with Lync server
 
Enhancements to Speech Platform and Speech Recognition
– In Exchange Server 2013 the speech GAL grammar generation no longer happens on the server
– Generation happens periodically using the Mailbox Assistant, on the Mailbox server running the Microsoft Exchange Unified Messaging
– GAL speech grammar file is stored in the arbitration mailbox for an organization
– Grammar file downloaded to all Mailbox servers
– Mailbox Assistant runs every 24 hours

Exchange 2013 now uses the Microsoft Speech Platform version 11.0.  This helps to provide a more accurate Voice Mail Preview experience for subscribers.  It also helps with the global address list (GAL) grammar generation that has been changed with Exchange 2013.  This GAL grammar is used to help determine spoken commands and names of contacts in the users mailbox and in the organization.

In Exchange Server 2013, to address ASR grammar generation scalability issues for UM, the speech GAL grammar generation no longer happens on the server with the Unified Messaging server role installed. Instead, it happens periodically using the Mailbox Assistant, on the Mailbox server running the Microsoft Exchange Unified Messaging service that hosts the organization’s arbitration mailbox. The GAL speech grammar file is stored in the arbitration mailbox for an organization and then later downloaded to all Mailbox servers in that Exchange organization. By default, the Mailbox
Assistant runs every 24 hours

Protect Voicemail using AD RMS

– Prevent forwarding of voicemail

– Integration with AD RMS and Exchange unified messaging

– Permissions designated by sender (by marking the message as private) or by administrative policy

Exchange 2013 UM Architecture 

  

If you notice here, the connection points from CAS to MBX is always going to be the same protocol that the client uses to connect to CAS.

CAS will proxy requests from clients on the appropriate protocol to the appropriate back-end MBX server.

For SMTP- once the CAS decides to accept the message, the SMTP session is then proxied.

One unique difference is Exchange UM.  The nature of real time traffic in the RTP media stream does not lend itself to a proxy scenario.  The signaling traffic (SIP) is used to redirect
the RTP stream to the back-end mailbox server

?All calls are front-ended by CAS servers ?Point SIP Trunks to CAS (or CAS Load Balanced FQDN), not Mailbox Servers ?Unified Messaging role is now a service on the Mailbox Server. 
?Unified Messaging Call Router Service running on CAS redirects the call to a specific Mailbox server, we put UM direct to Mailbox role is because the media stream should be fast to delivery
 
Basic Unanswered Call Flow Diversion to UM


Comments (6)

  1. paul says:

    Are you serious? Have you seen the output of voice transcription? It’s terrible and almost never accurate.

  2. Quentin says:

    "Transcription now happens to all messages even if they are over 75 sec unlike previous versions. If a message is over 75 sec, it is transcribed, but the text for the message isn’t included"

    Then why waste the resources to transcribe it?

  3. prash says:

    Does transcription happen for UM only or it can happen if voice message is submitted via SMTP/EWS ?
    Thanks.

  4. DAT800 says:

    Question, does this mean that the 2013 UM server can redirect to 2010/2007 UM servers if the users mailbox is hosted within 2010/2007 ?

  5. Anonymous says:

    こんばんは。Lync サポートの久保です。
    Lync と Exchange UM の連携、第二回目です。 第一回はこちら 。
    Lync Server 2013 と Exchange 2013

  6. Yassine Zeroual says:

    Reply to DAT800
    To get the full features of the UM we need to have the Exchange Server 2013

    But if you are running an older version, such as Exchange 2007 or Exchange 2010? Or indeed, what if you are in the middle of migrating from an older version and have users based on both platforms? In that case, all may not be lost because several features are
    still available. However, we would recommend that some serious testing is carried out and that potentially you leave features disabled until users are on the most modern platform to ease complexity.
    As you will see, Lync makes extensive use of features in newer Exchange versions, such as voice mail and web services. Th at said, Lync can also integrate in some ways with versions as early as Exchange 2007 SP1.
    The diff erences between Exchange 2007 and 2010 support are pretty small. Essentially, Exchange 2010 adds the ability to provide Message Waiting Indicator (MWI) information when used with Unified Messaging (UM) and also provides a contact sync feature, which
    allows Lync to create a personal contact in Outlook for each person on a user’s Lync contacts list. Exchange 2013 provides the updated Unifi ed Contact Store, Exchange archiving, and High-Resolution Photos support, which no previous versions support.
    One other area for consideration is that it is now possible to deploy Exchange in the cloud using Microsoft Offi ce 365. There are various supported scenarios for running parts of your organization in the cloud, including having either Lync Online or Exchange
    Online with its respective on-premises system.

Skip to main content