Which ports do VMS use?

VIGI VMS
Recent updates may have expanded access to feature(s) discussed in this FAQ. Visit your product's support page, select the correct hardware version for your device, and check either the Datasheet or the firmware section for the latest improvements added to your product. Please note that product availability varies by region, and certain models may not be available in your region.
VMS will use designated TCP and UDP ports to send and receive data over a network.
These ports are limited to a range of 1 to 65535. Port collisions can occur when a program attempts to use a port that is already occupied by another program on the host.
From this article, you can learn which ports VMS uses, and how to modify the default ports.
1. An overview of the default ports
The default ports used by the VMS are listed in the table below.
Ports |
TCP/UDP |
When the port is required |
5001 |
UDP |
When VIGI VMS actively discover VIGI devices via private protocol. |
8081 |
TCP |
When customer access the VIGI VMS web service via https. |
8082 |
TCP |
When VIGI devices report events to VIGI VMS. |
8091 |
TCP |
When customers watch live views or playback, VIGI VMS manages VIGI devices through this port. |
10123 |
TCP |
When VIGI devices connect to the VIGI VMS, establish the remote control terminal session between VIGI VMS and VIGI devices. |
10556 |
TCP |
When customer watch live view or playback from the VIGI VMS. |
13134 |
TCP |
VIGI VMS coordinates multiple services through this port simultaneously. |
27017 |
TCP |
VIGI VMS accesses the MongoDB database through this port. |
2. Examples of VMS using ports
This section explains how VMS uses ports, using the example of how it discovers and adds VIGI devices.
Firstly, VMS broadcasts discovery packets on the subnet via UDP port 5001.
Secondly, VIGI devices listen to the port and receive the discovery message, then reply to the VMS via the same port.
Thirdly, VIGI devices connect to VMS via TCP port 10123.
Finally, VMS and VIGI devices create a TLS tunnel and adopt VIGI devices with device account.
3. Port Forwarding Settings
If a router is performing NAT (Network Address Translation) between the VMS and the VIGI devices, the VIGI devices cannot connect directly to the VMS. In this case, Port Forwarding rules must be created to enable proper communication between the VMS and the VIGI devices.
The source and destination ports of the Port Forwarding rules should be the same as the VMS ports mentioned above. For example, if the device connect port is being used, the settings should be as shown below.
4. How to change the ports used by VMS
The VMS server ports can be changed by accessing the 'Port Config' option on the setup page.
5. Q & A
Q: How can I change the RCP Register Port?
A: The RCP Register Port is enabled when the VMS is running, if you want to change this port, please stop the VMS service and then change this port.
Q: What should I do if "Port is occupied" is displayed when VMS is enabled?
A: The VMS default ports have been used by another service on the server, please refer to section 4 to change the VMS default ports or stop the services that have been using the default ports.
Q: If my VMS is behind NAT, which ports do I need to forward to public?
A: You will need to set port forward rules on port 8081, port 8082, port 10123 and port 10556.
¿Es útil esta pregunta frecuente?
Sus comentarios nos ayudan a mejorar este sitio.
What’s your concern with this article?
- Dissatisfied with product
- Too Complicated
- Confusing Title
- Does not apply to me
- Too Vague
- Other
Gracias
Agradecemos sus comentarios.
Haga clic aquí para comunicarse con el soporte técnico de TP-Link.
Recommend Products
Este sitio web utiliza cookies para mejorar la navegación en el sitio web, analizar las actividades en línea y tener la mejor experiencia de usuario posible en nuestro sitio web. Puedes oponerte al uso de cookies en cualquier momento. Puede encontrar más información en nuestra política de privacidad . No volver a mostrar
Este sitio web utiliza cookies para mejorar la navegación en el sitio web, analizar las actividades en línea y tener la mejor experiencia de usuario posible en nuestro sitio web. Puedes oponerte al uso de cookies en cualquier momento. Puede encontrar más información en nuestra política de privacidad . No volver a mostrar
Basic Cookies
These cookies are necessary for the website to function and cannot be deactivated in your systems.
TP-Link
accepted_local_switcher, tp_privacy_base, tp_privacy_marketing, tp_smb-select-product_scence, tp_smb-select-product_scenceSimple, tp_smb-select-product_userChoice, tp_smb-select-product_userChoiceSimple, tp_smb-select-product_userInfo, tp_smb-select-product_userInfoSimple, tp_top-banner, tp_popup-bottom, tp_popup-center, tp_popup-right-middle, tp_popup-right-bottom, tp_productCategoryType
Livechat
__livechat, __lc2_cid, __lc2_cst, __lc_cid, __lc_cst, CASID
Youtube
id, VISITOR_INFO1_LIVE, LOGIN_INFO, SIDCC, SAPISID, APISID, SSID, SID, YSC, __Secure-1PSID, __Secure-1PAPISID, __Secure-1PSIDCC, __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDCC, 1P_JAR, AEC, NID, OTZ
Analysis and Marketing Cookies
Analysis cookies enable us to analyze your activities on our website in order to improve and adapt the functionality of our website.
The marketing cookies can be set through our website by our advertising partners in order to create a profile of your interests and to show you relevant advertisements on other websites.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au
Meta Pixel
_fbp
Crazy Egg
cebsp_, _ce.s, _ce.clock_data, _ce.clock_event, cebs
lidc, AnalyticsSyncHistory, UserMatchHistory, bcookie, li_sugr, ln_or