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.
Finden Sie diese FAQ hilfreich?
Mit Ihrer Rückmeldung tragen Sie dazu bei, dass wir unsere Webpräsenz verbessern.
Was ist Ihr Bedenken bei diesem Artikel?
- Mit Produkt unzufrieden
- Zu kompliziert
- Irreführende Titel
- Betrifft mich nicht
- Zu ungenau
- Was anderes
Vielen Dank.
Vielen Dank für Ihr Feedback.
Recommend Products
Von United States?
Erhalten Sie Produkte, Events und Leistungen speziell für Ihre Region
Diese Webseite verwendet Cookies, um die Websitenavigation zu verbessern, Online-Aktivitäten zu analysieren und die bestmögliche Nutzererfahrung auf unseren Webseiten zu haben. Sie können der Verwendung von Cookies jederzeit Widersprechen. Nähere Informationen finden Sie in unseren Datenschutzhinweisen.
Diese Webseite verwendet Cookies, um die Websitenavigation zu verbessern, Online-Aktivitäten zu analysieren und die bestmögliche Nutzererfahrung auf unseren Webseiten zu haben. Sie können der Verwendung von Cookies jederzeit Widersprechen. Nähere Informationen finden Sie in unseren Datenschutzhinweisen.
Notwendige Cookies
Diese Cookies sind zur Funktion der Website erforderlich und können in Ihren Systemen nicht deaktiviert werden.
TP-Link
SESSION, JSESSIONID, 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
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
Zendesk
OptanonConsent, __cf_bm, __cfruid, _cfuvid, _help_center_session, _pendo___sg__.<container-id>, _pendo_meta.<container-id>, _pendo_visitorId.<container-id>, _zendesk_authenticated, _zendesk_cookie, _zendesk_session, _zendesk_shared_session, ajs_anonymous_id, cf_clearance
Analyse- und Marketing-Cookies
Analyse-Cookies ermöglichen es uns, Ihre Aktivitäten auf unserer Website zu analysieren, um die Funktionsweise unserer Website zu verbessern und anzupassen.
Die Marketing-Cookies können über unsere Website von unseren Werbepartnern gesetzt werden, um ein Profil Ihrer Interessen zu erstellen und Ihnen relevante Anzeigen auf anderen Websites zu zeigen.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au