To connect your internal servers to your Edge Servers and configure the internal servers to route outbound traffic to the Edge Servers, you need to run the Configure Server Wizard or Configure Pool Wizard on each server or pool in your organization, as well as on the Director (that is, if you deployed a Director).

Before You Begin

When you created your Enterprise pools and Standard Edition servers, you had the option to configure an external Web farm fully qualified domain name (FQDN) on the Web Farm FQDNspage in the Create Pool wizard or the Deploy Server wizard. If you did not configure this URL when you ran these wizards, you need to manually configure these settings. To do this, open a command prompt and run the following command at the command line:

lcscmd.exe /web /action:updatepoolurls /externalwebfqdn:<ext web farm FQDN> /poolname:<pool name>

Where <ext web farm FQDN>is the FQDN for the Web farm and <pool name>is the name of the Enterprise pool.

Configure a Director

When you run the Configure Pool or Server Wizard and configure external access on a Director, you configure the following settings:

  • Add your Director as the next hop server through which all external Session Initiation Protocol (SIP) traffic is routed.

  • Add your Edge Server to the authorized Edge Server list.

  • Override the "next hop" setting that is used globally by internal servers and pools so that the Director routes all outbound traffic directly to the Edge Server.

To configure your Director for external user access

  1. Log on to your Director with an account that is a member of the RtcUniversalServerAdmins group.

  2. Start the Deployment Wizard by going to setup\amd64 and then double-clicking setupEE.exeor setupSE.exe.

  3. Do one of the following:

    • On a Standard Edition server, click Deploy Standard Edition Server.

    • On an Enterprise Edition server, click Deploy Pool in a Consolidated Topology or Deploy Pool in an Expanded Topology.

  4. Next to Configure Server, click Runor Run Again.

  5. On the Welcome to the Configure Pool/Server Wizardpage, click Next.

  6. On the Server or Pool to Configurepage, select the pool from the list, and then click Next.

  7. Accept the default settings until you reach the External User Access Configurationpage.

  8. On the External User Access Configurationpage, click Configure for external user access now, and then click Next.

  9. On the Route External SIP Trafficpage, click Route traffic through a Director, and then click the Use this pool or server as the Director for routing external trafficcheck box.

  10. Click Next.

  11. On the Trusted Access Edge Servers and Web Conferencing Edge Serverspage, type the internal FQDNs required for your Access Edge service and Web Conferencing Edge service and click Addafter each.

    Note:
    The FQDNs that you enter on this page are added to the list of authorized Edge Servers on the Edge Servertab in Global Properties.

    If you are using an array of load balanced Edge Servers, type the FQDN of the virtual IP (VIP) of the internal load balancer.

  12. Under Specify the Access Edge Server that internal servers will use for outbound traffic, select the FQDN of the Access Edge service to which you want all outbound traffic routed from your internal servers.

    Note:
    If your Edge Servers are load balanced, use the FQDN of the VIP on the internal load balancer used by the Access Edge service of your Edge Servers.

  13. Click Next.

  14. On the Web Conferencing Edge Serverpage, click Next.

    Note:
    You configure each internal server and pool to route to the Web Conferencing Edge service on the appropriate Edge Server. Directors do not route Web Conferencing traffic.

  15. On the Trusted A/V Edge Serverspage, type the internal FQDN of the A/V Edge Service on each Edge Server authorized to connect to your internal servers.

    Note:
    The FQDNs that you enter on this page are added to the list of authorized Edge Servers on the Edge Servertab in Global Properties.

  16. On the A/V Edge Server Used by This Server or Poolpage, click Next.

    Note:
    You configure each internal server and pool to route to the A/V Edge service on the appropriate Edge Server. Directors do not route A/V traffic.

  17. On the Ready to Configure Server or Poolpage, review the settings that you specified, and then click Next.

  18. When the files have been installed and the wizard has completed, verify that the View the log when you click Finishcheck box is selected, and then click Finish.

  19. In the log file, verify that < Success> appears under the Execution Resultcolumn. Look for < Success> Execution Resultat the end of each task to verify that pool configuration completed successfully. Close the log window when you finish.

Configure Other Internal Servers and Pools for External User Access

Use the following procedure to configure your internal servers or pools for external access. The procedure will vary slightly depending on whether you use a Director.

To connect your internal server with your Edge Servers

  1. Log on to your internal Standard Edition server or Enterprise pool with an account that is a member of the RTCUniversalServerAdmins group.

  2. Start the Deployment Wizard by going to setup\amd64\ and double-clicking setupEE.exeor setupSE.exe.

  3. Do one of the following:

    • On a Standard Edition server, click Deploy Standard Edition Server.

    • On an Enterprise Edition server, click Deploy Pool in a Consolidated Topology or Deploy Pool in an Expanded Topology.

  4. Next to Configure Server or Configure Pool, click Run.

  5. On the Welcomepage of the Pool/Server Configuration Wizard, click Next.

  6. On the Server or Pool to Configurepage, in the list, click the pool or server that you want to configure, and then click Next.

  7. Continue through the wizard, specifying the settings that are appropriate to your pool or server configuration, until you reach the External User Accesspage.

  8. On the External User Access Configurationpage, click Configure for external user access now.

  9. On the Routing External SIP Trafficpage, do one of the following:

    • If you plan to route all traffic sent to and from the Edge Servers through a Director, click Route traffic through a Directorand, if this is the Director, select the Use this pool or server as the Director for routing external trafficcheck box, click Next, and then perform the remaining steps in this procedure.

    • If you do not plan to route all traffic sent to and from the Edge Servers through a Director, click Route directly to and from internal pools and servers.

  10. Click Next.

  11. On the Trusted Access Edge and Web Conferencing Edge Serverspage, do one of the following:

    • If you are using a Director and are running the wizard on the Director to configure external user access, the entries on this page are not displayed. Proceed to step 13.

    • If you do not use a Director, you must enter the internal FQDNs required for your Access Edge service and Web Conferencing Edge service and click Addafter each. The FQDNs that you enter on this page are added to the list of authorized Edge Servers on the Edge Servertab in Global Properties.

    • If you are using a load balanced array of Edge Servers, type the FQDN of the VIP of the internal load balancer.

  12. Under Specify the Access Edge Server that internal servers will use to route traffic, do one of the following:

    • If you are using a Director, you do not need to specify the Edge Server.

    • If you are not using a Director, select the FQDN of the Access Edge service on the Edge Server to which you want all outbound traffic routed from your internal servers.

    • If you are using an Edge Server array, enter the FQDN of the VIP that the Access Edge service uses on the internal load balancer.

  13. Click Next.

  14. On the Web Conferencing Edge Serverpage, do the following:

    • In Internal FQDN, type the FQDN of each internal interface that the internal servers will use to connect to the Web Conferencing Edge service.

    • In External FQDN, type the FQDN of each external interface that the external users will use to connect to the Web Conferencing Edge service.

    • Click Addafter typing each pair of FQDNs.

  15. Click Next.

  16. On the Trusted A/V Edge Serverspage, type the FQDN of the internal interface that will be used to connect to the A/V Edge Server in the FQDNbox, type the port number to be used for the internal interface in the Portbox, and then click Add.

    Note:
    Repeat for each FQDN to be used. Servers are added to list of authorized Edge Servers on the Edge Servertab in Global Properties.

  17. On the A/V Edge Server Used by This Server or Poolpage, type the FQDN of the internal interface of the A/V Edge service on the Edge Server that this server or pool will use for A/V authentication.

    Note:
    This FQDN is added to the A/V Properties at the "pool" level for an Enterprise pool or Standard Edition server.

  18. Click Next.

  19. On the Ready to Configure Server or Poolpage, review the settings that you selected, and then click Next.

  20. On the completion page, click Finish.