Lync Voice Mail Survivability (SA) with Exchange Unified Messaging

-

The SBA is aware of the centrally configured Exchange Unified Messaging component. Additional it is important to understand the process of Voice Mail Survivability. While the VoicemailReroutingConfiguration in Lync provides the SBA with an alternative path, rerouted via PSTN to the central Exchange UM site.

The SBA is continuously check the SIP availability of the Exchange UM component, using the SIP OPTION based health checking. (Indeed, both SBA and non SBA Lync registrars act in the same way for all components, e.g. Exchange UM and other Gateway-SBC). Once the SIP OPTION command is sent, the sender expects an SIP 200 OK answer. Lync tries this health check several time even after it do NOT receive a 200 OK. As result of not receiving, the registrar will mark this target as DOWN and stop sending calls.

Note:You can drill down this process, if you us OCSLogger and Snooper catching the OPTION and 200 OK communication directly on the SBA.

Back to the Exchange UM, if Exchange is not responding, the SBA marks the UM SIP path as down and activated the configured PSTN reroute.

Note:

If a user SBA homed user is remotely connected to central site (his backup registrar), incoming PSTN call to this user will also be rerouted to Exchange UM VoiceMail.

A PSTN cannot be rerouted this this (backup) registered user!

Voice Mail Deposit

If a WAN outage occurs, the SBA has detected that UM connectivity is down, all unanswered or ignored call for effected user homed on this SBA will be routed over the PSTN to the assigned UM Auto Attendant (AA).

There is one change in user experience: Once the UM pickup this call, the AA will ask the calling party (either via speech or extension number) and then a voice mail can be recorded. This behavior is different to the native user mailbox response.

Voice Mail Retrieval


During a WAN outage, there are other service truly effected too, e.g. Exchange Server connection. But Exchange Subscriber Access is still available via PSTN calls. Therefor an effected user is NOT able to use his Lync Client for Voice Mail Preview, instead, the normal “Call Voice Mail” will place a PSTN call to the Exchange Server Subscriber Access Number (SA).

As long the user is assigned in AD and Lync with an E.164 phone number, Exchange is able to do a Reverse Number Lookup and can identify the users work number. Exchange then answer directly instead of asking for the user’s mailbox PIN.

Configuration


Voicemail rerouting configuration must be established for all Branch Site equipped with a SBA

New-CsVoicemailReroutingConfiguration -Identity Site:Ingolstadt

For each Voicemail Rerouting, the Exchange Auto Attendant (AA) and the Subscriber Access Number (SA) has to be published.

Set-CsVoicemailReroutingConfiguration -Identity Site:Ingolstadt -SubscriberAccessNumber “+49899090123″ -AutoAttendantNumber “+49899090456″ -Enabled $true

Thanks to Justin Morris for his detailed explanation

Author:

Comments

Post a Comment

Popular posts from this blog

How to hide users from GAL if they are AD Connect synchronized

-
Image
How to hide and un-hide users from Global Address List (GAL) in Exchange Online if they are AD Connect synchronized Hiding User from GAL isn't possible if those are synchronized form On-Premises Active Directory. The local AD is the leading system for all important attributes, like SMTP, UPN and hiding from GAL. Especially during a cross-tenant migration, you do not want to see not migrated user in the GAL. Those User aren't actively working until their cut-over day. Since the Exchange Online attribute  msExchHideFromAddressList s is an AD on-premises parameter, we have two possible ways hiding user in BME from GAL.   Modify the AD Connect for your teant with a custom rule, by using a extensionAttribute to set the HidefromGAL. In this rule, for users which have an entry in the extensionAttribute, hiding / un-hiding will be controlled by AD Connect This is the best option for Cross-Tenant Migration, if you run 2 or more AD Connect system We direct modif...
Read more

Cannot join external Lync Meeting: Lync Edge Server Single IP Address (Lync Edge Server Single IP Web Conferenceing Problem)

-
Image
Lync Edge Server FQDN and IP PORTS (Version 1.2, Update 26.11.2014) As we all know, we can configure Lync Edge Server in several way. 1) Single Edge Server with a SINGLE IP ADDRESS 2) Single Edge Server with MULTIPLE IP ADDRESSES (3x IPs) 3) Multiple Edge Server in a Pool, with MULTIPLE IP ADDRESSES (Zx 3 IPs) Regardless what we are going to configure, there are common / well-known TCP Port necessary making Lync work, which are: Access: Port: 443 and 5061 Conferencing: Port: 443 and (444) AV: Port: 443 (I have not listed other ports, e.g. STUN or the dynamic port range. This is not required for the topic discussed here) External FQDN with single IP address: What can we see here? If we are going to choose a single IP address, we would have TCP Port overlapping. Therefore the only way avoiding this is assigning other ports. Additionally we will also see and are reminded that Lync highly depends on DNS. If we have single IP, we must have use single, uniqu...
Read more

MFA with Guest Access and different tenants settings

-
Image
There is an update regarding MFA Multi Factor Authentication. If you are guest with a different Tenant, the MFA Settings are now reflecting the settings of all tenants in a different way. Each MFA setting is reflected and you can setup your MFA device as per tenant and the admin settings allow. Login to your Profile in Office 365/ Azure AD: https://account.activedirectory.windowsazure.com/r/#/profile or https://myapps.microsoft.com Go to your PROFILE: Sign in to https://myapps.microsoft.com Select your account name in the top right, then select profile. Select Additional security verification. If might be happen, your admin hast configured MFA, so you wouldn't see this menu. Simply switch the tenant to the guest tenant where you need to configure MFA. Once you go back to your profile and you will find the MFA device and other settings a usual:
Read more