Midlands Technology Centre, Broadlands, Wolverhampton Business Park, WV10 6TA
0845 241 6370 info@msvconsultancy.co.uk
Enable, Entrust & Educate Through IT

Lync 2013 Voicemail Configuration

Lync 2013 Voicemail Configuration

So we have our new Lync 2013 deployment configured and we have done the initial integration with Exchange 2013 to allow us to use the Unified Contacts Store (UCS) and the various archiving options (see my previous article).   We now need to move on to setting up Lync 2013 voicemail enabled users.

Pre-requisites

Lab Setup

Server Name IP Address Description
EXCH-FE 10.20.12.21 Exchange 2013 Front End Server
EXCH-BE 10.20.12.22 Exchange 2013 Back End Server
LYNC-01 10.20.12.31 Lync 2013 Enterprise Front End Server
LYNC-02 10.20.12.32 Lync 2013 Enterprise Front End Server
SQL-01 10.20.12.41 SQL 2012 Server

 

 

 

 

 

DNS Records

These additional DNS records were created

Record Name Record Type Record Value
Autodiscover A 10.20.12.21
LyncDiscoverInternal CNAME LyncPool
LyncPool A 10.20.12.31
LyncPool A 10.20.12.32

 

 

 

 

Voicemail

Before anything can be configured for voicemail we must have Server to Server authentication configured and working correctly - see previous article

An Exchange dial plan is then necessary to allow Lync 2013 to call the voicemail on our Exchange Server.

The plan must be first created with some of the required settings, then amended for the additional settings necessary.

New-UMDialPlan -Name "LyncDialPlan" -VoIPSecurity "Secured" -NumberOfDigitsInExtension 3 -URIType "SipName" -CountryOrRegionCode 44

Set-UMDialPlan "LyncDialPlan" -ConfiguredInCountryOrRegionGroups "Anywhere,*,*,*" -AllowedInCountryOrRegionGroups "Anywhere"

Lets explain some of these settings:

  • VoIPSecurity - Secured means we are going to use TLS
  • NumberOfDigitsInExtension - Sets up our number of digits in Voicemail extensions
  • URIType - SipName indicates we are going to use SIP as our protocol
  • CountryRegionCode - sets our region dial code - 44 is UK, 1 is US
  • ConfiguredInCountryOrRegionGroups -
  • AllowedInCountryOrRegionGroups -

Set the UM service on our back end server to dual and associate or dial plan

Set-UmService -Identity "exch-be.domain.com" -DialPlans "LyncDialPlan" -UMStartupMode "Dual"

Assign our back end certificate to the various services so that they will start

Enable-ExchangeCertificate -Server "exch-be.domain.com" -Thumbprint "THUMBPRINTSTRING" -Services "SMTP","IIS","UM"

Set the UM Call Router service on our front end server to dual and associate or dial plan

Set-UMCallRouterSettings -Server "exch-fe.domain.com" -UMStartupMode "Dual" -DialPlans "LyncDialPlan"

Assign our front end certificate to the various services so that they will start correctly

Enable-ExchangeCertificate -Server "exch-fe.domain.com" -Thumbprint "THUMBPRINTSTRING" -Services "IIS","UMCallRouter"

Now we have our UM and UM Call Router services configured, just give them a quick restart as we have changed the start-up modes.

Create a UM Mailbox policy

New-UMMailboxPolicy -Name "UMMailboxPolicy" -AllowedInCountryOrRegionGroups "Anywhere"

Voicemail enable a user using this newly defined policy

Enable-UMMailbox -Extensions 100 -SIPResourceIdentifier "testuser1@domain.com" -Identity "domain\TestUser1" -UMMailboxPolicy "UMMailboxPolicy"

We now need to ensure that Lync has access to our dial plans, that we have an IP gateway and hunt group defined for Lync.

cd “C:\Program Files\Microsoft\Exchange Server\V15\Scripts\”
.\ExchUCUtil.ps1

With all the configuration done all that is left is for us to do is some testing

$credential = Get-Credential "domain\TestUser1"
Test-CsExUMConnectivity -TargetFqdn "lyncpool.domain.com" -UserSipAddress "sip:testuser1@domain.com" -UserCredential $credential
Test-CsExUMVoiceMail -TargetFqdn "lyncpool.domain.com" -ReceiverSipAddress "sip:testuser2@domain.com" -SenderSipAddress "sip:testuser1@domain.com" -SenderCredential $credential

2 Responses

  1. James

    Do you know if it is possible to use Unity Connections as the voicemail server in a Lync 2013 environment? Thanks.

    • Hi James,
      The answer is kind of yes and no. Microsoft support no other VM solution for integration with Lync however you could have Cisco Call Manager simultaneously ring both its own and the Lync extension and when there is no answer forward to the Cisco Unity VM. There are a few caveats in that you need to ensure that the time to forward to voicemail on the Call Manager side is less than the ring timeout on Lync otherwise you will just get a disconnect. A better solution would be to use Exchange as the Voicemail for both Lync and Call Manager as it is supported by both platforms.
      Regards,
      Matt

Leave a comment