This article relates to the Cisco TelePresence MCU 4203, Cisco TelePresence MCU MSE 8420, Cisco TelePresence IP VCR 2210, Cisco TelePresence VCR MSE 8220, Cisco TelePresence ISDN GW 3241, Cisco TelePresence ISDN GW MSE 8321, Cisco TelePresence IP GW 3510, Cisco TelePresence MCU 4505, Cisco TelePresence Supervisor MSE 8050 and Cisco TelePresence MCU MSE 8510 products.
A. All TANDBERG Codian products make TCP and UDP IP connections. This article describes the ports used for both connection types.
Ports used by Codian products
Incoming ports
Outgoing ports
FTP - TCP:21 + TCP ephemeral (i.e. dynamic rather than fixed) ports used for passive mode
HTTP - TCP:80
HTTPS - TCP:443
H.323 - TCP:1720 + TCP ephemeral ports for incoming calls
RTSP - TCP:554
Windows Media Player streaming - TCP:1755
SNMP - UDP:161
Outgoing H.323 calls involve TCP connections from TCP ephemeral ports to TCP:1720 and a number of TCP ephemeral ports
Outgoing SIP TCP calls involve connections from TCP ephemeral ports to TCP:5060
Outgoing SIP TCP calls involve connections from TCP ephemeral ports to TCP:5061
Outgoing SNMP traps are sent from UDP ephemeral ports to port 162
Media (including audio, video and FECC messages) is UDP from ephemeral ports to ephemeral ports.
The TANDBERG Codian products allocate ephemeral ports in the range 49152 to 65535. It is possible to change the ports on which Codian products receive and establish connections. For instance, by default Codian products listen for H.323 calls to port 1720 and web browser connections to port 80 but these can be changed. Go to Network > Services.
RAS - UDP:2222 for gatekeeper client messages and UDP:1719 for the built-in gatekeeper server (if enabled)
Ports used by ConferenceMe
Signaling, including call setup, uses port 80 on the Codian MCU, and an arbitrary port on the PC running ConferenceMe. ConferenceMe will try UDP first for the RTP transport, which uses port 5082 on both the Codian MCU and on the PC running ConferenceMe, but if this connection fails for whatever reason then the client will use TCP (using the same ports as UDP) for the signaling process.
Note: To allow ConferenceMe to use TCP if the UDP connection fails, select Allow fall back to media using TCP on the Settings > Streaming page.
The UDP port is configurable both on the PC client (refer to the PC's documentation) and on the Codian MCU. To configure the UDP service used by ConferenceMe, go to Network > Services and in the UDP service section, edit the Tunneled media option.
Revision | Publish Date | Comments |
---|---|---|
1.0 |
23-Apr-2015 |
Initial Release |