You should
test the network components fi rst before poking around with your Edge confi guration.
The fi rst thing you should do is make sure name resolution is working from the outside.
Try to ping sip.company.com from a command prompt. Make sure it resolves to the right IP address.
If the correct public IP address comes back, you know DNS is working. Oftentimes, fi rewall
administrators will not allow ping or other ICMP traffi c through, so your ping may fail even
if the name resolved to the correct public IP address.
If you are using NAT on your fi rewall, make sure you have the correct NAT rule set up
to translate from your public IP address to your private IP address. Also make sure the fi rewall
is confi gured to allow port 443 traffi c into your private IP address.
The way to verify that your server is online and listening for requests is to use the
command-line utility telnet to connect to sip.company.com on port 443. The Edge Server is
listening for client connections on port 443 and by using telnet, we can test to see whether
any connections are allowed through the fi rewall to the Edge Server.
TIP
You set the URL that clients use to download the address book during the
Standard Server confi guration (or front-end pool, if you are using Enterprise
Edition). Misleadingly, the wizard calls this the External Web Farm FQDN. This
is really the external URL for the address book download as well as a few
other components. Many people breeze right through this step without
understanding exactly what it is.
Pages:
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222