01-11-2013 07:32 AM - edited 03-18-2019 12:25 AM
Hi All,
I keep bumping into some problems regarding ports within the Telepresence portfolio. If i read the documentation portlist are always given, but not in a usable form. In order to convince the network administrators we need to list the ports different.
E.g:
Description | Source Device | Source Port | Destination Device | Destination Port | Remark | Transport |
VCS Control to MCU | VCS Control | >1024 | MCU | 5060 | Sip Signalling | TCP |
VCS Control | >1024 | MCU | 5060 | Sip Signalling | UDP | |
VCS Control | >1024 | MCU | 1719 | RAS H.323 | UDP | |
VCS Control | >1024 | MCU | 5061 | SIP Signalling | TCP | |
MCU to VCS Control | MCU | >1024 | VCS Control | 1720 | H.323 signaling | TCP |
MCU | 50000:54999 | VCS Control | 50000:54999 | H.323 / H.245 | TCP | |
MCU | >1024 | VCS Control | 5060 | SIP Signalling | TCP |
This list for every system, like Lync integration, MXP, C-Series, CUCM, etc..
Is there a list like this?
Many thanks!
01-13-2013 11:08 PM
You could have a look at VCS Port Usage on the web gui. There are all inbound and outbound ports listed and of if applicable a link to change port ranges.
Sent from Cisco Technical Support iPad App
01-17-2013 07:27 AM
Hi Paul,
That is actualy quite handy. But i am looking for the full list.
Right now its compiled as a flat list, but I would like to see to where the ports are going. So where does port 500 go to, where does port range 50000-54999 go to. These are obviouse ones, but i hope you know what i mean.
Its more easy for network administrators if we can provide them with a list that resambles my example above.
01-18-2013 01:46 AM
Hi Pieter,
I understand your problem , however you need to be little specific on which particular ports you require when deploying TP setup for customer or for your own network . The reason I am writing this down is , Cisco recommends and have published different guides for particular deployment scenario. For Eg -
Hence, you can search for particular those guides when deploying TP Solution.
Thanks,
Saurabh
01-18-2013 02:06 AM
Hi Pieter,
it depends on what list you want to sent to your firewall admins.
I think it's quite a good list, if you send them the VCS Outbund and Inbound Ports, because there are all IP addresses listed, which are needed. So there is the Source IP & Destination and Port range specified.
You could also find the purpose of that ports, so you could tell your fw admins, why you need that port.
As Saurabh said, it's good to look at the Admin, Install and Deployment Guides to understand in more detail what the ports are for.
01-20-2013 02:42 PM
Hello!
I agree with Pieter that the documentation could be optimized, some better and streamlined overview
in the admin guides of all components and a tp firewall guide collecting all info would be a great help for many users.
Just as an example of his list,
MCU | 50000:54999 | VCS Control | 50000:54999 | H.323 / H.245 | TCP |
that does not fit. The dst for the VCS is correct, the port range itself is for media and not h323/h245.
Media for the MCU could come from/to the codians ephemeral ports which are: 49152 to 65535 and its udp not tcp (see:
It would also be needed to exist in the other direction from the VCS to the MCU.
As Paul mentioned working together with the firewall admin is always a good idea. Most firewalls have a capability to
show you what gets blocked, that can also help you here.
I can also recommend to review the mentioned documents or as this can become quite complex
to contact your Cisco partner or an external consultant to help you.
Please remember to rate helpful responses and identify
01-21-2013 12:12 AM
Hi Guys,
I am aware that every port is listed in some sort of documentation, but i thought there would be one document with the whole listing. I already started to compile a list for myself, But it's a lot of research, also dependant on versions.
@Martin, unfortunately I am the consultant people are turning to for firewall advice
Thanks for the replys!
01-21-2013 12:43 AM
Hi Pieter.
Most telepresence devices is mentioned in this link
http://www.cisco.com/en/US/docs/telepresence/security_solutions/ctss_app_a.html
//Marius
01-21-2013 01:15 AM
Hi Marius,
Thank you for that link. It contains the sort of lists i am looking for. But it does not contain the former Tandberg portolio like VCS, MCU etc.
If sombody got those lists for VCS, MCU, TP Server, TMS, Endpoints than i am a happy man.
01-21-2013 12:42 PM
Hi Peter,
this is the base list, I use for installations.
SIP / H323 all internal Jabber Client Networks to VCS Control
SIP
UDP 5060
TCP 5060-5061
H323
UDP 1718-1719
TCP 1720
TCP 15000-15499
Media Ports between Video endpoints, VCS Control and MCU (both directions)
RTP & RTCP UDP 50000 - 54999 (>= X7.2, before: 50000 - 52399)
// Comment: normally endpoints use 2326 to 2486, but I use the same port range on all device to ease firewall configuration
from TMS to Cisco Endpoints
SNMP UDP 161
HTTP TCP 80
HTTPS TCP 443
SSH TCP 22
from Cisco Endpoints tom TMS
HTTP TCP 80
HTTPS TCP 443
SNMP Traps UDP 161
from Cisco VCS Control to VCS Expressway
H323 UDP 6001
RTP UDP 2776 - 2777
H323/RTCP TCP 2776 - 2777
SIP TCP 7001
from TMS to VCS Expressway
TCP 80
TCP 443
TCP 22
UDP 161
VCS Expressway to TMS
TCP 80
TCP 443
Internet to VCS Expressway
SIP
TCP 5060-5061
H323
UDP 1718-1719
TCP 1720
TCP 15000-15499
Assent (FW Traversal for Cisco Endpoints)
UDP & TCP 2776-2777
RTP & RTCP
UDP 50000 - 54999 (>= X7.2, before: 50000 - 52399)
TURN Relay
UDP 3478
UDP 60000-61399
VCS Expressway to Internet
UDP > 1024
TCP > 1024
01-24-2013 03:15 AM
Great list, thanks for posting Paul.
My customer will have the following separated by a firewall:
VCS-C / TMS / MCU / VC endpoints
Given the above will the following apply?
CUCM <> VCS-C
5060 TCP UDP
VCS <> TelePresence Server
SIP
5060 TCP UDP
H323
UDP 1718-1719
TCP 1720
Media Ports between Video endpoints and TelePresence Server (both directions)
RTP & RTCP UDP 50000 - 54999 (>= X7.2, before: 50000 - 52399)
Have I missed anything?
Many thanks
Trevyn
05-16-2013 10:37 AM
This is a good doc for all ports too.
http://www.cisco.com/web/DK/assets/docs/presentations/Video_Update_Video_ports_31mar11.pdf
I'm seeing an endpoint try to communicate with TMS from port 161 to port 2010. What is port 2010 used for?
Endpoints to VCS-C
UDP/1719 (H323 RAS signaling)
TCP/5060 (SIP signaling)
TCP/5061 (SIP TLS signaling)
TCP/5070 (SIP BFCP)
TCP/1720 (Q931/H.225 call connect signaling) TCP/15000-19999 (H.245 signaling) UDP/50000-52399 (RTP/RTCP traversal media)
VCS-C to endpoints
UDP/1719 (H323 RAS signaling)
TCP/5060 (SIP signaling)
TCP/5061 (SIP TLS signaling)
TCP/5070 (SIP BFCP)
TCP/1720 (Q931/H.225 call connect signaling) TCP/5555-6555 (H.245 signaling) UDP/2326-2487 (RTP/RTCP media endpoints) UDP/21000-21900 (RTP/RTCP media Movi/PC)
TCP/1720 (H323 signaling) *
TCP/5555-6555 (H.245 signaling) *
TCP/5070 (SIP BFCP)
UDP/2326-2487 (RTP/RTCP media for H323)
UDP/46000-49000 (RTP/RTCP media for SIP)
UDP/21000-21900 (RTP/RTCP media Movi/PC)
Endpoints MUST have H323 ports set to
static (for using 5555-6555/tcp and
2326-2487/udp), not dynamic, then 11000-65000/udp is used for media).
11-01-2017 12:33 PM
Is port 1720 required?
MCU to VCS Control | MCU | >1024 | VCS Control | 1720 | H.323 signaling | TCP |
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide