locked
Multiple EE pool communication RRS feed

  • Question

  • We are looking to install multiple EE pools in the US, Europe and the Far East.

    Therefore we will have a USpool.company.com a Eurpool.company.com and a fareastpool.company.com.  Will the User Replicator service running on each front end server route each user to the proper home server automatically or do you need DNS and SRV records setup properly for the clients Automatic Configuration to work?   I guess I am looking for how this all will work.  We will be deploying IM and Web Conferencing servers.

    Tuesday, June 12, 2007 7:18 PM

Answers

  • Hello,

     

    Each AD domain should add its HOST RR to the DNS partition that is being used automatically. There is not problem with that. Now each SIP domain that you host will require a "A" or host record in the DNS that is local to the OCS 2007 server that is hosting it. Each Pool FQDN will require a HOST or "A" record in the local DNS also. The Pool FQDN can be mapped to an IP address that is the VIP for a hardware load balancer that is configured to work with OCS Access servers in scaled topology. The DNS auto sign for each pool will require a SRV record in the local DNS _sipinternaltls._TCP.<internal AD domain FQDN> this reord will be mapped to port 5061 and it will point to the "A" record for the Pool FQDN. Because of the limitation of the _sipinternaltls SRV record the DNS automatic logon model is limited to working with just one pool. If you wanted to use several pools you could enforce the use of TLS manual authentication with the use of OUs that manage the user sign on using a per pool basis. The name of the group policy is Transport. Manual TLS sign on  will require HOST record that is a FQDN that will map to an IP address that can be assigned to the NIC on the OCS server or the VIP address f a hardware load balancer.

     

    Thanks,

     

    Mike Adkins

    Thursday, June 14, 2007 7:14 PM

All replies

  • Hi,

     

    I am not sure whether I understand your question in the right way. If not, feel free to clarify :-)

     

    For Automatic Configuration you will always need the corresponding DNS (SRV and A) records. Did you check the OCS_Planning_Guide.doc? There is a section about DNS records you need:

    • A DNS SRV record for each SIP domain that is served by an Enterprise pool
    • An A record for each SIP domain that is served by an Enterprise pool

    Does that answer your question?

     

    Thanks

    Bernd

    Wednesday, June 13, 2007 2:32 PM
  • We will have only one SIP domain in the form that all accounts will have their SIP account as firstname.lastname@ourcompany.com.  There will be 3 Enterprise Pools potentially.  USPool.corp.ourcompany.com, EurPool.corp.ourcompany.com and APPool.corp.ourcompany.com.  Do I need SRV & A records for each pool or just one for the SIP domain?
    Thursday, June 14, 2007 1:09 PM
  • Hello,

     

    Each AD domain should add its HOST RR to the DNS partition that is being used automatically. There is not problem with that. Now each SIP domain that you host will require a "A" or host record in the DNS that is local to the OCS 2007 server that is hosting it. Each Pool FQDN will require a HOST or "A" record in the local DNS also. The Pool FQDN can be mapped to an IP address that is the VIP for a hardware load balancer that is configured to work with OCS Access servers in scaled topology. The DNS auto sign for each pool will require a SRV record in the local DNS _sipinternaltls._TCP.<internal AD domain FQDN> this reord will be mapped to port 5061 and it will point to the "A" record for the Pool FQDN. Because of the limitation of the _sipinternaltls SRV record the DNS automatic logon model is limited to working with just one pool. If you wanted to use several pools you could enforce the use of TLS manual authentication with the use of OUs that manage the user sign on using a per pool basis. The name of the group policy is Transport. Manual TLS sign on  will require HOST record that is a FQDN that will map to an IP address that can be assigned to the NIC on the OCS server or the VIP address f a hardware load balancer.

     

    Thanks,

     

    Mike Adkins

    Thursday, June 14, 2007 7:14 PM