Following on from my Exchange 2013 OWA and Lync IM integration guide I thought I’d turn my attention to the Exchange 2013 UM service and Lync integrated voicemail. For my previous blog post see here.
New-UMDialPlan –Name ‘Name’ – URIType SipName –Numberofdigitsinextension ‘x’ –countryorregioncode ‘xx’ –AccessTelephoneNumbers +00123456789
Set-UMService –identity ‘SERVER’ –DialPlans ‘Plan Name’
Perform this for the rest of your Back End servers that require to be in this Dial Plan. If you have created the Dial Plan in EAC and not used Powershell as I have, you will have to click on the Servers in the EAC and then specify Unified Messaging to add them to a Dial Plan.
In Powershell set the startup mode using Set-UMService.
Set-UmService –Identity ‘SERVER’ –UMStartUpMode ‘dual _or_ tls’
Again note the need for the certificate. Perform this action on all required Back End servers. As a side note I did say you can do this within EAC. Login and go to:
Servers | Your Server | Unified Messaging | Set the ‘UM startup mode’:
Enable-ExchangeCertificate –thumbprint ‘thumbprint’ –services UM
Repeat this for all Back End servers. If you do not set the certificate for UM then the UM service will be in a constant state of restarting when proceeding to the next step.
Enable-ExchangeCertificate –Server ‘SERVER’ –thumbprint ‘thumbprint’ –services umcallrouter
This one threw me originally as I kept trying to enable it for UM – and that kept failing, until I realised through the help of the ECP that it has been renamed for the FE role. Be aware that you can assign the cert for a Front End for the UM Call Router Service in the ECP.
Set-UMCallRouterSettings –server ‘SERVER’ –DialPlans ‘DialPlan’
Ensure this process is completed for all Front Ends.
Run it within the Exchange Management Shell .\ExchUCUtil.ps1 it should complete successfully.
Once it has loaded click on the Dial Plans and then click on ‘Add’, this will create a contact as shown:
Ensure the number is correct and matches the number you entered for the Exchange UM Dial Plan in step 1. Repeat this process for each Dial Plan you want to merge. Also be aware that should you ever add new Dial Plans or UM Servers repeat steps 9 and 10 to configure them with Lync.
That’s it! Configuration is completed and voicemail integration between Lync 2010 and Exchange 2013 UM should be working.
As you can see it is wildy different in setting up UM on both the Front End and Back End servers, but the process does share some similarities with Exchange 2010. We still need to set the UM service to dual mode or TLS and assign a certificate, the Unified Messaging role has to be a member of a Dial Plan and we still need to run ExchUCUtil.ps1 and OcsUMUtil.exe
In a further blog post coming this week I’ll move on to adding Language Packs for Exchange 2013 Unified Messaging. In the mean time you can download them here.