How to use VIGI Cameras with Third-party NVR or NAS
VIGI C400HP , InSight S345 , VIGI C340HPWSM , VIGI C440-W , EasyCam C540S , InSight S445ZI , InSight S485 , InSight S345-4G , InSight S385 , VIGI C340S , VIGI C540V , VIGI C540S , VIGI C250 , VIGI NK4P-T4425-2T , VIGI C540-W , VIGI C230 , VIGI C450 , VIGI C350 , VIGI C300P , VIGI C430 , VIGI C330 , VIGI C355 , VIGI C330I , VIGI C320I , VIGI C455 , VIGI C340I , VIGI C420I , InSight S355 , InSight S455 , VIGI C230I Mini , VIGI C300HP , VIGI C340 , VIGI C540-4G , VIGI C240 , VIGI C340-W , VIGI C540 , VIGI C485 , VIGI C400P , VIGI C440 , VIGI C385 , VIGI C440I , VIGI C445 , VIGI C430I , VIGI C220I , VIGI C345 , VIGI C230I , VIGI C240I
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.
Contents
Objective
Clients may sometimes choose not to use VIGI NVR but other management platform to manage VIGI Cameras when they already have a third-party storage device. VIGI Cameras support ONVIF Profile S and can be added to the third-party management device that also supports the ONVIF protocol. When ONVIF Profile S is not supported on the third-party device, VIGI Cameras can also allow for live streaming on the third-party platform via the RTSP protocol.
Requirements
- VIGI Camera
- Third-Party NVR or NAS
Introduction
It is recommended to use VIGI Cameras with VIGI NVR for easy access and management in batches. However, VIGI Cameras can also work with NVR or NAS of other brands that supports the ONVIF and RTSP protocols. This article will describe steps to use VIGI Cameras with a third-party NVR.
Configuration.
Step 1. Connect the VIGI Cameras with the third-party NVR according to the network topology below and make sure they are in the same network.
Step 2. When only a few VIGI Cameras need to be configured, log in to the Web Management Interface of each camera for initialization. When a large number of VIGI Cameras are to be initialized, configure them in batches using VIGI Config Tool.
Web Management Interface
1. Use the IP address of the VIGI Camera to access its Web Management Interface. The default IP address is 192.168.0.60.
2. Set the management password for the camera in the initialization page.
3. Go to Settings > Network Settings > Connect and mark down the current IP address.
4. To add the VIGI Camera to the third-party device, refer to FAQ-3718. Note that the ONVIF port for VIGI Cameras is 2020, and the RTSP port is 554. The username is admin by default and cannot be changed.
VIGI Config Tool
1. Go to the TP-Link website to download VIGI Config Tool. Here is the download link.
2. Install VIGI Config Tool on a Windows PC and connect the PC to the same network as the VIGI Camera.
3. Launch VIGI Config Tool and select all the VIGI Cameras to be configured.
4. Click Batch Action and choose Batch Initialize.
5. Initialize the cameras in batches and mark down their IP addresses after initialization.
6. To add the VIGI Cameras to the third-party device, refer to FAQ-3718. Note that the ONVIF port for VIGI Cameras is 2020, and the RTSP port is 554. The username is admin by default and cannot be changed.
Step 3. Log in to the third-party NVR or NAS and check if the VIGI Cameras have been under management.
Conclusion
You have now successfully added VIGI Cameras to the third party NVR or NAS.
Get to know more details of each function and configuration please go to Download Center to download the manual of your product.
Related FAQs
Is this faq useful?
Your feedback helps improve this site.
What’s your concern with this article?
- Dissatisfied with product
- Too Complicated
- Confusing Title
- Does not apply to me
- Too Vague
- Other
We'd love to get your feedback, please let us know how we can improve this content.
Thank you
We appreciate your feedback.
Click here to contact TP-Link technical support.
TP-Link Community
Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy . Don’t show again
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy . Don’t show again
Basic Cookies
These cookies are necessary for the website to function and cannot be deactivated in your systems.
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
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