Which ports are used by Cisco acquired TANDBERG/Codian Conferencing Products, Cisco TelePresence Serial Gateway Series, and Cisco TelePresence ConferenceMe?
All Cisco acquired TANDBERG/Codian products and the Cisco TelePresence Serial Gateway Series make TCP and UDP IP connections. This article describes the ports used for both connection types.
Ports used by Cisco acquired Codian Conferencing Products and the Cisco TelePresence Serial Gateway Series
- 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 Cisco acquired TANDBERG/Codian products and the Cisco TelePresence Serial Gateway Series allocate ephemeral ports in the range 49152 to 65535*. It is possible to change the ports on which these products receive and establish connections. For instance, by default Cisco acquired 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 Cisco TelePresence ConferenceMe
Default port allocations
Signaling (including call setup) uses an arbitrary port on the PC that runs ConferenceMe, and by default the following port on the Cisco TelePresence MCU:
- Port 80 in configurations with MCU version 4.1(1.59) or earlier. Port 80 is also used for the HTTP web service.
- Port 81 in configurations with MCU version 4.2(1.43) or later.
Changing the MCU port allocation
You can optionally change the MCU port allocation for ConferenceMe (go to Network > Services).
Important! With MCU version 4.1(1.59) or earlier, ConferenceMe shares the HTTP web port and cannot be configured separately. So if you change the default port number for ConferenceMe then it will also change for the web port.
From MCU version 4.2(1.43) the web port and the ConferenceMe port can be configured separately. By default ConferenceMe can use either the web port or the ConferenceMe specific port. You can optionally override this and specify that only the ConferenceMe specific port may be used (go to Settings > Streaming and uncheck Allow ConferenceMe to use web service).
ConferenceMe will try UDP first for the RTP transport, which uses port 5082 on both the Cisco TelePresence 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 Cisco TelePresence MCU. To configure the UDP service used by ConferenceMe, go to Network > Services and in the UDP service section, edit the Tunneled media option.
This article applies to the following products:
- Cisco TelePresence IP GW 3500 / MSE IPGW blade
- Cisco TelePresence IP VCR 2200 / MSE VCR blade
- Cisco TelePresence ISDN GW 3200 and 3241 / MSE 8310 and 8321 ISDN blades
- Cisco TelePresence Serial GW 3340 and Serial GW MSE 8330
- Cisco TelePresence MCU 4200 / MSE 8420
- Cisco TelePresence MCU 4500
- Cisco TelePresence MSE 8050 Supervisor
- Cisco TelePresence MSE 8510 blade
- Cisco TelePresence Server 8710 and 7010
- Cisco TelePresence ConferenceMe
|March 6th, 2012||TAA_KB_3|