Now you need to enter the name of the Edge Server as a trusted server. You need to
enter only one name here, because our Edge Server is both an Access Edge and a Web
Conferencing Edge. If we had broken the Edge into multiple servers, each with a different
role, you would enter both server names here. Notice that I have entered the internal
interface name here, even though the wizard is asking for Access Edge and Web Conferencing
Edge FQDNs (see Figure 5.19). Do not enter the external names here; enter only the
internal FQDN.
156 Chapter 5 ??? Confi guring the Edge Server
Click Next to continue.
Confi gure the internal and external names of your Web Conferencing Edge server. For
the internal FQDN, enter the internal name of the Edge Server: ocsedge.contoso.com.
Externally, users will connect to conference.contoso.com (see Figure 5.20).
Figure 5.19 Adding the Edge to the Front-End Server
Figure 5.20 Adding the Web Conferencing Servers to the Edge
Configuring the Edge Server ??? Chapter 5 157
Click Next to continue.
At the next screen, you need to enter the name and port of your A/V Edge server
(see Figure 5.21).
Figure 5.21 Adding the A/V Edge Server
Unlike the previous screen, this is asking only for the internal name of the Edge Server
hosting the A/V Edge service. Enter the FQDN: OCSEDGE.contoso.com. The A/V
Edge service listens on port 5062 by default.
WARNING
Do not enter the A/V Edge??™s external name here; the wizard is only looking
for the internal FQDN of the Edge Server.
Pages:
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210