This makes the
Edge services more ???portable??? to a new server when you need to upgrade
hardware or move an Edge service to its own server. By choosing a name
138 Chapter 5 ??? Confi guring the Edge Server
If you want your external clients to be able to automatically connect to your Edge Server
without manually specifying a server name, you need to create an external DNS SRV record.
The SRV record that the OCS clients look for is _sip._tls.contoso.com pointing to sip.contoso.
com on port 443. If you are using a Windows DNS server to manage your external DNS, the
entry would look like the screenshot in Figure 5.1.
such as sip.company.com rather than server01.company.com for the Access
Edge service, you will be making it much easier on yourself in the future.
Figure 5.1 External DNS Entry for Auto-Confi guration
If you are planning to federate with other companies, you may want to consider an SRV
record that enables ???enhanced??? federation. This record will automatically direct federated
partners to your Edge Server without them having to know the name of your Edge Server.
The record for enhanced federation would be _sipfederationtls._tcp.contoso.com pointing to
sip contoso.com on port 5061.
Configuring the Edge Server ??? Chapter 5 139
You will create only one internal DNS record for the Edge Server: the record for the
internal interface. This should be a record with the FQDN in your internal DNS namespace,
such as edge01.company.local, and it should resolve to an internal, private IP address.
Pages:
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197