Audicodes Lync 2013 IVR manual activation

Hello,

This post is to clear up some confusion concerning the manual deployment for the Lync 2013 AudioCodes IVR.

#Background

I work at a Global company where topology changes can only be performed on designated days. The external vendor that was assisting with the IVR deployment insisted that we had to run the script that auto-provisioned the IVR. The issue with the script is that it invokes the Enable-Cstopology cmdlet which is a big NO in our environment. After dissecting the script, I realized it was just creating a trusted application pool, application, and endpoint.

The steps for manual activation are listed below:


1. Create the trusted app pool (See sample code):

#Creates IVR pool

New-CsTrustedApplicationPool -Identity ivr-pool.mydomain.com -Site 1 -Registrar sba1.mydomain.com -ComputerFqdn ivr1.mydomain.com

#Creates IVR application

New-CsTrustedApplication -ApplicationId "urn:application:ivr" -TrustedApplicationPoolFqdn ivr-pool.mydomain.com  -Port 15001 (See update below)

Enable-CsTopology

#Creates IVR endpoint AD object

New-CsTrustedApplicationEndpoint -ApplicationId ivr -SipAddress "sip:ivr-pool1.mydomain.com " -TrustedApplicationPoolFqdn ivr-pool.mydomain.com  -DisplayName "Audiocodes IVR application endpoint"

2. Create DNS A record for the IVR computer. Following the example, I would create the host (A) record for ivr1.mydomain.com. NOTE: This step was not needed for the Lync 2010 IVR

3. Ensure that network firewalls are allowing TCP 445 for the new IVR server (ivr1.mydomain.com) to communicate with Central Management Store (CMS)

4. Install the Central Management Store replication service, Enable Central Management store replication, and Set certificate. Steps found here, 

https://msdn.microsoft.com/EN-US/library/office/dn466123.aspx

From my experience, the IVR service will not activate until CMS replication is TRUE. 

I hope this helps!!!

UPDATE 1-26-2017: You might want to think about a different port to use for the trusted application other than the default 15001. I had an SBA fail that was also using an IVR server hosted locally, at a branch location. Users reported immediately that inbound calls were not working. The issue was the the parent site, where the users failed over to, was behind a GWAN firewall that did not contain an allow rule for TCP port 15001 as our security team didn't deem it a standard Lync/Skype port. I had to request an emergency firewall rule to allow the port temporarily in order to restore inbound call functionality. Needless to say, we now use TCP port 5061 as the port for the IVR Trusted Application.