Lot of clients are now moving away from on premises Exchange and in to O365 these days. Exchange online came a long way and grown up a lot. In terms of Unified Communications, how should we get Voicemail out of O365 exchange?. And what will be the configuration that involves in?. To answer those questions, let’s have a look at what the prerequisites are and what the configuration should be.
Before moving forwards, there’s several critical points need to be addressed and understood;
- On premises Lync Server 2013 deployment must have Edge servers installed and federation enabled
- Edge server DNS resolution should be done via the External interface and not over the internal. It must have public DNS servers configured instead of internal DNS.
- _sipfederationtls._tcp.domain.com SRV record must be configured in public DNS and resolve against the access edge FQDN (sip.domain.com)
- The O365 Tennent domain must be set to “Authoritative” accepted domain
Form above mentioned 2 points, I cannot stress the importance of proper DNS configuration enough. If the DNS wasn’t properly configured, the whole partner federation component will get broken as a result and it will not be a pleasant experience.
To check if the domain is accepted and authoritative within O365, below command can be used
Get-AcceptedDomain | Format-List
Next, a Hosting Provider needs to be configured. To configure this, run the command; New-CsHostingProvider -Identity “Exchange Online” -Enabled $True -EnabledSharedAddressSpace $True -HostsOCSUsers $False -ProxyFQDN “exap.um.outlook.com” -IsLocal $False -VereficationLevel UseSourceVerification
Now, create a Hosted Voicemail Policy. This is the policy that get assigned to a user who needs to be enabled for O365 Unified Messaging. To configure the policy, run the command; New-CsHostedVoicemailPolicy -Identity “CloudUMPolicy” -Destination exap.um.outlook.com -Description “Hosted Voicemail Policy for Lync Users” -Organization “contosoltd.onmicrosoft.com”
In above command, the Organization parameter must be specified as the tenant name and not the shared name space. Ex, contoso.com (shared name space), contosoltd.conmicrosoft.com (Tenant Name). Then run; Invoke-CsmanagementStoreReplication to replicate the changes.
Now to create UM contact object for Subscriber access and Voicemail. Usually for on-premises Exchange, we use OCSUMUtil.exe tool to create these objects. But in O365 UM scenario, we have to use Lync Server management Shell to create these objects. In order to create the contact object for Subscriber Access, the command; New-CsExUmContact -SipAddress sip:firstname.lastname@example.org -RegistrarPool lyncPool.domain.com -OU “OU=ExUmContacts,DC=domain,DC=com” -DisplayNumber -AutoAttendant $False -IsSubscriberAccess $True can be used.
Now we are done with Lycn server bits and move on to O365 portal to configure the UM Dial Plan. Log in to the O365 portal using https://portal.office.com and go to the Admin Centre.
Go to “Exchange” and select “UM Dial Plans”. Select “+” to create a new dial plan. Configure the dial plan name, number of digits of an extension. Select “SIP URI” from the drop down for “Dial plan type”. Set the language, the country code and save the configuration.
Move to “Outlook Voice Access” tab and configure the DID number for the Subscriber Access in E.164 format as shown below. If you want to use a custom greeting, the audio file can be uploaded in to the “Default Greeting” configuration.
Next to configure the “Dialling Rules”. Dialling rules are configured to dictate which number or number patterns can be routed via the subscriber access as well as the auto attendant. Usually, the dialling rules are configured to route all digits without any restriction, unless if there’s a special requirement that need to configure specific numbers. Configure the dialling rules as mentioned below. This dialling rule will be later on assigned to the Um Mailbox policy as well.
Now to assigned the dialling rule to the dialling authorization table. Configuring this will allow users who are coming in to the Subscriber Access and Auto Attendant to reach out to internal user extensions. Assign the dialling rule to the authorization table and check “Calls in the same dial plan” and “Allow calls to any extension” components.
In The “Pin Policy” tab, you can change the number of digits that are required for the PIN and whether to allow the common patterns for the PIN. Usually, the PIN would be set to 4 digits length and allow common patterns.
The “Dialling Authorization” is the most important part within the UM Mailbox policy. If not configured with a number policy, it will not allow calls to be routed to internal extensions from the subscriber access or auto attendant. Assign the previously configured number policy to allow all digits and “Calls within the same UM dial plan” and “Call to any Extension” should be checked.
This is all that is to the Subscriber Access component of the Exchange UM in O365. The same steps can be followed to configure the Auto Attendant. It will require to configure a UM Object for the Auto Attendant in Lync Server and then need to configure the Auto Attendant within O365.