Print

Configuring Remote Call Control

About this task

The Lync Server Management Shell is used to add an Remote Call Control (RCC) gateway. It is recommended that RCC configuration be performed by or in coordination with the Lync Server System Administrator.

In the following procedure, RCC is set up using the Microsoft Lync Management Shell for Lync Server 2010. The same steps apply to setting up RCC for Lync Server 2013.

In step 5, avaessrv is a unique name chosen for the new application ID. It does not map to any previous configuration.

Procedure

  1. Select Start > All Programs > Microsoft Lync Server > Lync Server Management Shell to start the Lync Server Management Shell using the appropriate credentials. From the command prompt, enter the command specified at each step.
  2. Run the following commands to capture any pre-existing configuration data if any for reference and copy to Notepad:PS C:\Users> Get-CsStaticRoutingConfiguration (should return null results unless a static route has previously been configured)

    Identity : Global

    Route : {}

    PS C:\Users> Get-CsSipDomain (To view configured SIP domain(s). This will not be modified during RCC configuration in this example.)

    PS C:\Users> Get-CsTrustedApplicationPool (Retrieves settings for one or more pools that contain the computers that host trusted applications).

    PS C:\Users> Get-CsSite (Retrieves site related configuration information.)

    For help with the Lync Server management Shell: PS C:\Users> Get-Help

  3. To create a static route, first set the variable $TLSRoute:
    1. PS C:\Users> $TLSRoute = New-CsStaticRoute -TLSRoute -Destination avaessrv.aes.lync2010.local -Port 4723 -UseDefaultCertificate $true -MatchUri aes.lync2010.local
      noteNote

      In step 3a, avaessrv.aes.lync2010.local is the Fully Qualified Domain Name (FQDN) for the AE Services server; aes.lync2010.local is a sub-domain of your SIP domain.

    2. PS C:\Users> Set-CsStaticRoutingConfiguration -Route @{Add=$TLSRoute}
  4. Create a new trusted application entry. Type the following at the command prompt:

    PS C:\Users> New-CsTrustedApplicationPool -Identity avaessrv.aes.lync2010.local -Registrar lyncss.lync2010.local -Site 1 -TreatAsAuthenticated $true -ThrottleAsServer $true -RequiresReplication $false

    noteNote

    In step 4, lyncss.lync2010.local is the FQDN of the Microsoft Lync Standard Server; 1 is a SiteID that was configured during Lync Server Deployment. See output of Get-CsSite for the SiteID field value.

  5. Add the trusted application to the pool. Type the following at the command prompt:

    PS C:\Users> New-CsTrustedApplication -ApplicationID avaessrv -TrustedApplicationPoolFqdn avaessrv.aes.lync2010.local -Port 4723

  6. Use Get-CsStaticRoutingConfiguration and Get-CsTrustedApplicationPool to view the changes:

    PS C:\Users> Get-CsStaticRoutingConfiguration

    Identity : Global

    Route : {MatchUri=*aes.lync2010.local;MatchOnlyPhoneUri=False;Enabled=True; ReplaceHostInRequestUri=False}

    PS C:\Users> Get-CsTrustedApplicationPool

    Identity : TrustedApplicationPool:avaessrv.aes.lync2010.local

    Registrar : Registrar:lyncss.lync2010.local

    FileStore :

    ThrottleAsServer : True

    TreatAsAuthenticated : True

    OutboundOnly : False

    RequiresReplication : False

    AudioPortStart :

    AudioPortCount : 0

    AppSharingPortStart :

    AppSharingPortCount : 0

    VideoPortStart :

    VideoPortCount : 0

    Applications : {urn:application:avaessrv}

    DependentServiceList : {}

    ServiceId : 1-ExternalServer-1

    SiteId : Site:westy

    PoolFqdn : avaessrv.aes.lync2010.local

    Version : 5

    Role : TrustedApplicationPool

  7. To implement the published changes you have made to the topology, type the command:PS C:\Users> Enable-CsTopology