Cisco Cisco Meeting Server 2000
Cisco Meeting Server Release 2.0 : Scalable and Resilient Meeting Server Deployments
67
See the MMP Command Reference for details of the xmpp callbridge commands.
7.3 Deploying the Trunk and the Load Balancer
In a split deployment the XMPP server is located on the Core server for security, and connects
via a Load Balancer on an Edge server. The Core server initiates a TLS connection to the Edge
server. The Core server and Edge server mutually authenticate, and the Edge server starts to
listen on port 5222 for incoming client XMPP connections. A client XMPP connection is serviced
by the Load Balancer and relayed to the Core server using the TLS trunk.
via a Load Balancer on an Edge server. The Core server initiates a TLS connection to the Edge
server. The Core server and Edge server mutually authenticate, and the Edge server starts to
listen on port 5222 for incoming client XMPP connections. A client XMPP connection is serviced
by the Load Balancer and relayed to the Core server using the TLS trunk.
Note: the direction of traffic: the Core server connects out from the internal network to the Edge
server in the DMZ—which is the natural direction of traffic as far as firewalls are concerned and
convenient if the internal network uses NAT.
server in the DMZ—which is the natural direction of traffic as far as firewalls are concerned and
convenient if the internal network uses NAT.
Figure 18: Trunk and Load Balancer listening ports in a split deployment
A Core server hosting the XMPP service can create multiple trunks to multiple Edge servers in
different geographic locations.
different geographic locations.
7 Deploying the XMPP Server