• Contents

Configure IC server for RCC

        On this page Hide

  1. Click Lines container in Interaction Administrator.

  2. Create a line to be used for RCC, right click in the lines grid and then click New.

  3. In the SIP Line Configuration tab, click Line on the left.

    Verify that Line Usage is set to Microsoft Lync Remote Call Control.

  4. To enable the SIP Session Timer (SIP Session Keep-Alive) for the RCC SIP line, click Session on the left and set the SIP Session Timeout <n> seconds.

    The default is 60 seconds. A setting of 0 (zero) will disable the keep-alive functionality. If the keep-alive feature is enabled, an INFO message is sent by the CIC server to the Lync Server every n seconds. This keep-alive feature helps keep the connection between the CIC server and the Lync Server steady. The setting must be kept under 20 minutes (1200 seconds).

  5. In the SIP Line Configuration tab, click Transport on the left.

    The Receive Port is now configurable. The 11001 port is the default and it is best to keep this default. Transport can be either TCP or TLS/MTLS. (UDP is given as an option, but should not be used.)

  6. If using TLS/MTLS:

    1. On the Lync Server, generate a certificate to use with CIC. Refer to the Lync documentation for this task.

    2. Export the CIC server's Trusted Certificate from the Lync Server, including all certificates in the certificate path to include the Root CA Certificate. Export it in PKCS#12 (.PFX) format. Export the private key also.

    3. On the CIC server, we need to extract the public and private keys. The extract is accomplished by using openSSL or ssl_app-w32r-1-2.exe:

      1. Extract the private key:

        ssl_app-w32r-1-2.exe pkcs12 -in <pfx_file_name>.pfx -nocerts -nodes -out priv.pem

      2. Extract the public key:

        ssl_app-w32r-1-2.exe x509 -inform pem -in privpub.pem -pubkey -out pub.pem -outform pem

  7. In the SIP Line Configuration tab, click TLS Security on the left.

    If checking the Require mutual authentication check box (for MTLS), make sure the certificate that Lync uses to connect to CIC has Client Authentication X509 Extended Key Usage (client EKU). Instructions for how to configure the Lync certificate can be found in the following articles:

  8. In the SIP Line Configuration tab, click the Configure certificates and port mappings link at the bottom of the screen.

    1. In the SIP/TLS Line Certificates Configuration window on the Line Certificates tab, click Import.

    2. Add the CIC server certificate created on the Lync Server on the line certificates to the Path: box. Set Type: to X509 and Format: to PEM.

    3. Click OK.

    4. Import the Root Certificate Authority (CA), and all intermediate CAs used to sign the Lync Certificate.

  9. On the Port-To-Certificate Mappings tab, in the Line Certificate: box choose the CIC server Certificate created on the Lync Server and select Port: 11001 (the port we chose for the Lync RCC line). Click Add. Click Close.

  10. In the Line Configuration window, in the SIP Line Configuration tab, click Modify.

    1. Select the Root CA certificate in the Available list.

    2. Click Add to move it to the Currently Selected list.

    3. Click OK.

    4. Click OK.

    Any change of the RCC SIP line settings in Interaction Administrator will be picked up by the RCCServer only after restarting the RCCServer.

Enable the RCCServer subsystem in CIC

  1. Open the IC System Manager.

  2. Under View, clear the Disabled Subsystems check box.

  3. In the disabled list, locate RCCServer.

  4. Double-click RCCServer, then change the startup type to Automatic.

  5. Start the RCCServer subsystem.