Cisco Cisco Meeting Server 2000
Cisco Meeting Server Release 2.0 : Single Combined Meeting Server Deployments
19
o
TCP Port 443 (HTTPS) from Call Bridge to Web Bridge (for guest login. The Web Bridge is
required for Cisco Meeting Apps to look up guest login when using a web browser that
does not support WebRTC (for example Internet Explorer).
required for Cisco Meeting Apps to look up guest login when using a web browser that
does not support WebRTC (for example Internet Explorer).
n
From version 2.0.4, the TURN server now listens on TCP port 3478 for communication from
the Call Bridge, rather than TCP port 443 as in previous releases. You do not need to open
UDP port 3478 or TCP port 3478 as they are internal to the Meeting Server.
the Call Bridge, rather than TCP port 443 as in previous releases. You do not need to open
UDP port 3478 or TCP port 3478 as they are internal to the Meeting Server.
n
Internal clients connect directly to the XMPP server on port 5222 and media connects directly
between the Cisco Meeting App and the Call Bridge.
between the Cisco Meeting App and the Call Bridge.
n
External Cisco Meeting Apps establish a control connection to the XMPP server (black line).
Media can go directly from the Cisco Meeting App to the Call Bridge (dashed red line) or be
relayed via the TURN server if required (red line).
Media can go directly from the Cisco Meeting App to the Call Bridge (dashed red line) or be
relayed via the TURN server if required (red line).
n
Another deployment option is to enable the XMPP server on a second interface and connect
that interface to the private network. Then internal clients can connect directly to the XMPP
server. Separate internal and external SRV records for the XMPP service need to be
configured, directed to the two interfaces that the XMPP server is listening on.
that interface to the private network. Then internal clients can connect directly to the XMPP
server. Separate internal and external SRV records for the XMPP service need to be
configured, directed to the two interfaces that the XMPP server is listening on.
n
Both internal and external Cisco Meeting Apps use ICE/TURN to find suitable candidates for
connectivity and choose the best: in the case of internal clients this will always be the local
host candidates on the internal network.
connectivity and choose the best: in the case of internal clients this will always be the local
host candidates on the internal network.
2.5 Database
The Call Bridge reads from and writes to the database storing the space information, for
example the members of spaces, chat messages occuring between members of a space,
recent activity within a space.
example the members of spaces, chat messages occuring between members of a space,
recent activity within a space.
In a single combined deployment the database is created and managed automatically by the
Call Bridge and does not require an activation key or being enabled.
Call Bridge and does not require an activation key or being enabled.
2.6 H323 Gateway
The H.323 Gateway enables an H.323 call to connect to the Call Bridge. The H.323 Gateway
does not provide firewall traversal or call control, you are recommended to deploy an H.323
Gatekeeper to perform these functions. With the H.323 Gateway enabled, you can make the
following calls:
does not provide firewall traversal or call control, you are recommended to deploy an H.323
Gatekeeper to perform these functions. With the H.323 Gateway enabled, you can make the
following calls:
H.323 call > H.323 GW > space
H.323 call > H.323 GW > Call Bridge->Lync
H.323 call > H.323 GW > Call Bridge->SIP device
H.323 call > H.323 GW > Call Bridge->Cisco Meeting App
2 General concepts for deployment