Topic Last Modified: 2010-07-18
Microsoft Communications Server 2010 supports three simple URLs for conferencing—Meet, Dial-In, and Admin. You are required to set up simple URLs for Meet and Dial-In, and the Admin simple URL is optional. The DNS records you need to support simple URLs depend on how you have defined these simple URLs. There are three general options for how you define the URLs.
The first option creates a new SIP domain name for each simple URL.
 Note: |
|---|
| When a user clicks a simple URL meeting link, the server that the DNS A record resolves to determines the correct client software to launch. Once the client software is launched, it automatically communicates with the pool where the conference is hosted. This way, users are directed to the appropriate server for meeting content no matter which server or pool the simple URL DNS A records resolve to. |
Simple URL Option 1
|
Simple URL |
Example |
|
Meet |
https://meet.contoso.com, https://meet.fabrikam.com, and so on (one for each SIP domain in your organization) |
|
Dial-in |
https://dialin.contoso.com |
|
Admin |
https://admin.contoso.com |
If you use this style, you must define the following:
- For each Meet simple URL, you need a DNS A record that resolves
the URL to the IP address of the Director, if you have one
deployed. Otherwise, it should resolve to the IP address of the
load balancer of an enterprise pool. If you have only Standard
Edition Server, the DNS A record must resolve to the IP address of
one Standard Edition Server in your organization.
If you have more than one SIP domain in your organization and you use this option, you must Meet simple URLs for each SIP domain, and thus need a DNS A record for each of these. For example, if you have both contoso.com and fabrikam.com, you will create DNS A records for both https://meet.contoso.com and https://meet.fabrikam.com.
Alternatively, if you have multiple SIP domains and you want to minimize the DNS record and certificate requirements for these simple URLs, use Option 3 below.
- For the Dial-in simple URL, you need a DNS A record that
resolves the URL to the IP address of the Director, if you have one
deployed. Otherwise, it should resolve to the IP address of the
load balancer of an enterprise pool. If you have only Standard
Edition Server, the DNS A record must resolve to the IP address of
one Standard Edition Server in your organization.
- The Admin-in simple URL is internal only. It requires a DNS A
record that resolves the URL to the virtual IP address of an
Enterprise pool. If you have only Standard Edition Server, the DNS
A record must resolve to the IP address of one Standard Edition
Server in your organization.
Simple URL Option 2
|
Simple URL |
Example |
|
Meet |
https://cs.contoso.com/Meet, https://cs.fabrikam.com/Meet, and so on (one for each SIP domain in your organization) |
|
Dial-in |
https://cs.contoso.com/Dialin |
|
Admin |
https://cs.contoso.com/Admin |
With this option, all simple URLs are based on the domain name cs.contoso.com. Therefore, you need only one DNS A record, which resolves cs.contoso.com to the IP address of the load balancer of an enterprise pool. If you have only Standard Edition Server, the DNS A record must resolve to the IP address of one Standard Edition Server in your organization.
Simple URL Option 3
|
Simple URL |
Example |
|
Meet |
https://cs.contoso.com/contosoSIPdomain/Meet https://cs.contoso.com/fabrikamSIPdomain/Meet |
|
Dial-in |
https://cs.contoso.com/contosoSIPdomain/Dialin https://cs.contoso.com/fabrikamSIPdomain/ Dialin |
|
Admin |
https://cs.contoso.com/contosoSIPdomain/Admin https://cs.contoso.com/fabrikamSIPdomain/Admin |
This option is most useful if you have many SIP domains, and you want them to have separate simple URLs but want to minimize the DNS record and certificate requirements for these simple URLs.