Cisco Acano X-series
Cisco Meeting Server Release 2.0 : Single Split Meeting Server Deployments
20
TURN server now listens on TCP port 3478 for communication from the Call Bridge, rather
than TCP port 443 as in previous releases. TCP port 3478 and UDP port 3478 are used in
the event that ports 32768-65535 are blocked by the internal firewall.
than TCP port 443 as in previous releases. TCP port 3478 and UDP port 3478 are used in
the event that ports 32768-65535 are blocked by the internal firewall.
o
UDP Port 50000-51000 from Call Bridge to TURN server (for media). Although the range
between the TURN server and the external Cisco Meeting Apps is shown as 50000-
51000, future releases may require a wider range of 32768-65535.
between the TURN server and the external Cisco Meeting Apps is shown as 50000-
51000, future releases may require a wider range of 32768-65535.
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 Load Balancer (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
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.
n
The necessary ports need to be open on the firewall between Core and Edge components to
allow the media UDP traffic to pass (UDP ports 32768 - 65535) and the trunk between the
Load Balancer and the XMPP server. The Web Bridge uses port 443 (and optionally port 80).
allow the media UDP traffic to pass (UDP ports 32768 - 65535) and the trunk between the
Load Balancer and the XMPP server. The Web Bridge uses port 443 (and optionally port 80).
n
Separate internal and external SRV records for the XMPP service need to be configured,
directed to the two interfaces on the Core server/virtualized server that the XMPP server is
listening on. The Call Bridge to XMPP connection should also use the XMPP server’s internal
address.
directed to the two interfaces on the Core server/virtualized server that the XMPP server is
listening on. The Call Bridge to XMPP connection should also use the XMPP server’s internal
address.
2.6 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 split deployment the database is created and managed automatically by the Call
Bridge and does not require an activation key or being enabled.
Bridge and does not require an activation key or being enabled.
2 General concepts for deployment