<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by linkingvision on Medium]]></title>
        <description><![CDATA[Stories by linkingvision on Medium]]></description>
        <link>https://medium.com/@linkingvision?source=rss-2eee62ff15c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*dYbSX3ROYfAFtLWs</url>
            <title>Stories by linkingvision on Medium</title>
            <link>https://medium.com/@linkingvision?source=rss-2eee62ff15c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 22:39:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@linkingvision/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Introduction to ONVIF Profile V Uplink Authentication Modes]]></title>
            <link>https://medium.com/@linkingvision/introduction-to-onvif-profile-v-uplink-authentication-modes-00d07e0ca146?source=rss-2eee62ff15c------2</link>
            <guid isPermaLink="false">https://medium.com/p/00d07e0ca146</guid>
            <dc:creator><![CDATA[linkingvision]]></dc:creator>
            <pubDate>Fri, 13 Nov 2026 09:56:44 GMT</pubDate>
            <atom:updated>2026-11-13T09:56:44.964Z</atom:updated>
            <content:encoded><![CDATA[<p>The authentication mechanisms in ONVIF Profile V are quite extensive, and organizing all these modes during testing turned out to be quite a brain-twister.<br>The documentation covers both OAuth2 and Uplink authentication. Here, we will use Uplink as the main thread for our analysis. Uplink supports the following two modes:<br>1. mTLS requires pre-configuring corresponding certificates on both the device and the cloud. Of course, the cloud can use a single unified certificate for all devices, while device certificates require a “one-certificate-per-device” (unique per-device credential) setup.<br>xml<br>&lt;SetUplink xmlns=”<a href="http://www.onvif.org/ver10/uplink/wsdl">http://www.onvif.org/ver10/uplink/wsdl</a>&quot;&gt;<br> &lt;Configuration&gt;<br> &lt;RemoteAddress&gt;wss://10.168.1.195:21574&lt;/RemoteAddress&gt;<br> &lt;CertificateID&gt;Cert-faeb526c-df37–11f1-b259-e454e89daf79&lt;/CertificateID&gt;<br> &lt;UserLevel&gt;Administrator&lt;/UserLevel&gt;<br> &lt;CertPathValidationPolicyID&gt;Policy-f79ca0fc-df37–11f1–91ca-e454e89daf79&lt;/CertPathValidationPolicyID&gt;<br> &lt;/Configuration&gt;<br>&lt;/SetUplink&gt;<br>Use code with caution.<br>2. OAuth2 is further divided into the following three sub-modes:<br> • a. client_secret_basic<br> • b. private_key_jwt<br> • c. mtls (tls_client_auth)<br>Among these three modes: Mode a does not require pre-configuring corresponding certificates on the server, though it does require setting a clientID and clientSecret. There are multiple ways to implement this, such as sharing one client_secret across a batch of devices, or assigning one client_secret per device (unique per-device credentials). Mode b requires pre-configuring the corresponding device public key certificates on the server, and of course, each device must also have its own certificate set up in advance — this must strictly follow a unique per-device credential approach. Mode c requires both the device and the server to have their respective certificates pre-configured.<br>xml<br>&lt;SetUplink xmlns=”<a href="http://www.onvif.org/ver10/uplink/wsdl">http://www.onvif.org/ver10/uplink/wsdl</a>&quot;&gt;<br> &lt;Configuration&gt;<br> &lt;RemoteAddress&gt;wss://10.168.1.195:21650&lt;/RemoteAddress&gt;<br> &lt;UserLevel&gt;Administrator&lt;/UserLevel&gt;<br> &lt;CertPathValidationPolicyID&gt;Policy-1efac5e8-df38–11f1–9b55-e454e89daf79&lt;/CertPathValidationPolicyID&gt;<br> &lt;AuthorizationServer&gt;AuthSrv-1ed32f42-df38–11f1–8ef9-e454e89daf79&lt;/AuthorizationServer&gt;<br> &lt;/Configuration&gt;<br>&lt;/SetUplink&gt;</p><p>&lt;CreateAuthorizationServerConfiguration xmlns=”<a href="http://www.onvif.org/ver10/advancedsecurity/wsdl">http://www.onvif.org/ver10/advancedsecurity/wsdl</a>&quot;&gt;<br> &lt;Configuration Type=”OAuthClientCredentials” ClientAuth=”client_secret_basic”&gt;<br> &lt;ServerUri&gt;<a href="https://10.168.1.195:20885/.well-known/openid-configuration">https://10.168.1.195:20885/.well-known/openid-configuration</a>&lt;/ServerUri&gt;<br> &lt;ClientID&gt;client1&lt;/ClientID&gt;<br> &lt;ClientSecret&gt;client-secret1&lt;/ClientSecret&gt;<br> &lt;Scope&gt;scope1&lt;/Scope&gt;<br> &lt;CertPathValidationPolicyID&gt;Policy-d61ad61c-df35–11f1–8b0b-e454e89daf79&lt;/CertPathValidationPolicyID&gt;<br> &lt;/Configuration&gt;<br>&lt;/CreateAuthorizationServerConfiguration&gt;<br>Use code with caution.<br>Summary<br>Aside from the client_secret_basic mode — which bypasses having to configure a certificate for every single device on the server — all other methods require unique per-device credentials. Since client_secret_basic is not recommended, you should aim for a unique per-device credential design as much as possible when architecting for Profile V.<br>When scaling a service to handle tens of thousands, or even hundreds of thousands to millions of devices, performance becomes critical. You can leverage OAuth2’s scope for partitioning to boost server performance — partitioning is much harder to achieve without OAuth2. Therefore, our recommended approaches are private_key_jwt and mtls (tls_client_auth), allowing the server to partition based on scope to improve lookup speeds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*7un4eooMNaBHNbHn338URg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=00d07e0ca146" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is ONVIF’s Intention in Releasing Profile V?]]></title>
            <link>https://medium.com/@linkingvision/what-is-onvifs-intention-in-releasing-profile-v-1c76896b18c4?source=rss-2eee62ff15c------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c76896b18c4</guid>
            <dc:creator><![CDATA[linkingvision]]></dc:creator>
            <pubDate>Mon, 31 Aug 2026 02:27:08 GMT</pubDate>
            <atom:updated>2026-08-31T02:27:53.961Z</atom:updated>
            <content:encoded><![CDATA[<p>ONVIF recently released the release controller (RC) version of Profile V, revealing some details. Today, we’ll discuss Profile V and its relationship with Profile S/Profile T/Profile G/Profile M, as well as Profile A/Profile C/Profile D.</p><p>ONVIF Profile V was designed to support the increasingly popular VSaaS (Virtual Private Server) architecture. China’s GB28181 standard inherently supports the VSaaS architecture, including the later-defined GB35114. However, ONVIF’s client/server architecture cannot meet this requirement. In the past few years, ONVIF also defined Uplink, but it hasn’t gained much traction. One company, VXG (<a href="https://www.videoexpertsgroup.com/">https://www.videoexpertsgroup.com/</a>), did a lot of work, implementing VSaaS based on the Uplink approach and providing device-side code (<a href="https://github.com/VideoExpertsGroup/VXG.Uplink.SDK">https://github.com/VideoExpertsGroup/VXG.Uplink.SDK</a>). However, supporting each device individually proved difficult, and ultimately, this company was acquired by Octave. According to information released by VXG, Profile V’s approach is very similar to VXG’s, employing the S3 cloud storage model and supporting frame-by-frame playback of data from cloud storage. This is implemented in the browser based on HTML5, a remarkable feature. The author believes this is also a trend, as some Chinese companies have gradually returned to plugin technology during the Chrome era, completely abandoning HTML5.</p><p>Many companies specialize in VSaaS, such as Verkada, EEN, 3deye, and Videoloft, as well as Genetec MileStone. The author previously worked with FocusAI (<a href="https://www.qualcomm.com/internet-of-things/device-finder/focus-ai-focus-ai-vantage">https://www.qualcomm.com/internet-of-things/device-finder/focus-ai-focus-ai-vantage</a>), which was later acquired by Qualcomm. These companies all use proprietary protocols. As mentioned in the ONVIF Profile V announcement, if a user switches service providers, their camera becomes unusable. With Profile V, however, they can continue using the camera even after switching providers — sounds wonderful, right? Profile S/Profile T fulfilled a similar mission.</p><p>After ONVIF defeated PSIA, it released many profiles, but few were implemented for A, C, and D access control. A search in the ONVIF compatibility library will reveal this. Profile Q was also released, but it’s basically obsolete. Currently, the most influential are STGM. ONVIF officially hopes that Profile V can achieve the same level of influence as Profile S and Profile T.</p><p>Profile V is primarily designed for cameras, storing all video in the cloud via the S3 protocol. It lacks a standard for uplink playback, meaning NVRs are not within the scope of Profile V. Furthermore, Profile V implements authentication based on OAuth2/mTLS, requiring an IAM service.</p><p>It seems that half of Profile V’s functionality consists of modern network security features, making its development significantly more complex than STG.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LhA_FTgTUE7zmMuQ5dxzNw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c76896b18c4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[USC Security Platform Multi Node Cluster]]></title>
            <link>https://medium.com/@linkingvision/usc-security-platform-multi-node-cluster-c2182d2be975?source=rss-2eee62ff15c------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2182d2be975</guid>
            <dc:creator><![CDATA[linkingvision]]></dc:creator>
            <pubDate>Thu, 07 May 2026 07:12:03 GMT</pubDate>
            <atom:updated>2026-05-07T07:12:03.155Z</atom:updated>
            <content:encoded><![CDATA[<p>USC, based on a microservices architecture, can easily implement multi-node clusters. The following describes its usage:</p><p>When the number of monitoring device channels exceeds 5000, the performance of a single server will be limited. Horizontal node addition can be used to increase worker nodes. The default installation is a single node, and its working mode is USC_SERVER_MAIN. There is only one USC_SERVER_MAIN type worker node in the entire cluster. USC_SERVER_SUB is in worker node mode. Multiple worker nodes are possible in the system. USC_SERVER_MAIN and USC_SERVER_SECONDARY1/USC_SERVER_SECONDARY2 have worker node functionality by default. The worker nodes connect to the database of the USC_SERVER_MAIN node.</p><p>The following configuration represents a system with one USC_SERVER_MAIN node and two USC_SERVER_SUB nodes:</p><p>ServerMain USC_SERVER_MAIN 10.168.1.108</p><p>Server1.101 USC_SERVER_SUB 10.168.1.101</p><p>Server1.161 USC_SERVER_SUB 10.168.1.161</p><p>Edit this in System -&gt; Cluster -&gt; Cluster Configuration</p><ol><li>First, configure ServerMain, then restart the service. Only configure the numbered parts 1, 2, 3, and 4.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YymnqGG6wAOUDlNXpR9KbQ.png" /></figure><p>2. Then configure the Server1.101 node, and restart the service after configuration. Only the numbered parts (1, 2, 3, 4) need to be configured. See below for reference.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p61VDpxRNTIlr5M1RvvPaQ.png" /></figure><p>3. Then configure the Server1.161 node, and restart the service after configuration. Only configure the numbered parts 1, 2, 3, and 4. See below for reference.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gUh4mvE8ifqF_dQyScyP2w.png" /></figure><p>After configuration, you can log in from any node to view the overall system status. You can see a list of all nodes under System -&gt; Cluster -&gt; Cluster Configuration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F20n9dCQPtewCZK_ox_sOQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2182d2be975" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[EPRO AI NVR for OEM and ODM]]></title>
            <link>https://medium.com/@linkingvision/epro-ai-nvr-for-oem-and-odm-4d0d7af3f174?source=rss-2eee62ff15c------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d0d7af3f174</guid>
            <dc:creator><![CDATA[linkingvision]]></dc:creator>
            <pubDate>Wed, 08 Apr 2026 02:16:42 GMT</pubDate>
            <atom:updated>2026-04-08T02:16:42.533Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rnGIj_npkBjLPIQx.png" /></figure><p>The EPRO AI NVR is equipped with industry-leading software functions, perfectly supported by Intel, RK3588, and Novatek chips, designed to provide a comprehensive, reliable, and intelligent surveillance solution. Focusing on advanced software capabilities, which are fully optimized for Intel, RK3588, and Novatek chip platforms, it integrates high-performance video processing, flexible storage management, intelligent analytics, and seamless network connectivity, ensuring complete video recording, efficient monitoring, and convenient remote management. The chip support ensures stable software operation, enhanced processing efficiency, and full compatibility with all core software features. Suitable for residential, commercial, enterprise, and industrial scenarios of all scales, the EPRO AI NVR’s software system, backed by Intel, RK3588, and Novatek chips, delivers stable, efficient, and secure performance, while maintaining cost-effectiveness and easy integration with existing IP cameras and surveillance systems.EPRO AI NVR is ready for OEM and ODM.</p><p><strong>Core Software Features</strong></p><p>Equipped with industry-leading software technologies, fully supported by Intel, RK3588, and Novatek chips, the EPRO AI NVR boasts a full range of advanced software features, combining intelligence, flexibility, and user-friendliness — including the highlighted ANR (Automatic Network Replenishment) function to ensure complete video recording, N+1 hot spare mode to guarantee system continuity, and support for LVGL and Qt UI libraries for flexible interface customization. The three chip platforms provide powerful hardware foundation, enabling the software to exert its full performance and realize high-efficiency video processing, intelligent analytics, and stable network connectivity.</p><p><strong>Advanced Video Processing &amp; Management</strong></p><p>Supports multiple video compression formats (H.265+/H.265/H.264+/H.264) via software optimization, perfectly adapted to Intel, RK3588, and Novatek chips, which provide powerful hardware support to reduce bandwidth and storage consumption by up to 50% while maintaining crystal-clear video quality and faster compression speed.</p><p>Software-driven ultra-high-resolution processing, fully supported by Intel, RK3588, and Novatek chips, supporting up to 8K live view and playback, and maximum recording resolution up to 32MP. The three chip platforms ensure smooth processing of ultra-high-definition video, ensuring every detail is captured accurately for critical surveillance scenarios.</p><p><strong>Intelligent Video Analytics (IVA) Software</strong></p><p>Intelligent event filtering software to reduce false alarms, with customizable alert rules and multiple software-driven alarm linkage methods (email alerts, audio buzzers, mobile app push notifications) for quick response to abnormal events.</p><p>Built-in advanced IVA algorithms and intelligent monitoring software tools, powered by Intel, RK3588, and Novatek chips, supporting line crossing detection, intrusion detection, object left/lost detection, people counting, and ANPR (Automatic Number Plate Recognition). The powerful computing capability of the three chips ensures high-precision and real-time intelligent analytics, enabling proactive alerting and significantly enhancing surveillance efficiency.</p><p><strong>Intelligent Storage Management</strong></p><p>Powerful software decoding capability, backed by Intel, RK3588, and Novatek chips, supporting up to 48-ch@1080p synchronous decoding and multi-group independent video output (HDMI, VGA, DP) with 8K/4K high-definition display options. The chip support ensures stable and low-latency decoding, adapting to diverse monitoring display needs.</p><p>Advanced software-based storage management, supporting RAID 0/1/5/6/10/N+1 protection and seamless integration with SSD/HDD storage devices. Combined with the N+1 hot spare mode, it forms a dual-reliability guarantee, preventing data loss and ensuring 24/7 uninterrupted storage and monitoring.</p><p>Adaptive recording software function, automatically adjusting bitrate based on motion activity, and supporting camera-wise recording retention settings to maximize storage efficiency and extend storage lifecycle.</p><p>Software-enabled hot-swappable storage support (compatible with hardware), enabling convenient maintenance and uninterrupted operation without system downtime.</p><p><strong>Seamless Network Compatibility &amp; Remote Management Software</strong></p><p>Complies with ONVIF Profile S/G/T via software integration, ensuring seamless compatibility with third-party IP cameras, VMS platforms, and security devices, reducing integration costs and complexity.</p><p>Comprehensive network protocol support (TCP/IP, DHCP, DNS, DDNS, NTP, UPnP, RTSP, P2P) through software, enabling remote access, live view, playback, and management via web browsers, mobile apps, and centralized VMS platforms.</p><p><strong>Advanced N+1 Hot Spare Mode</strong></p><p>A core reliability feature of the EPRO AI NVR, the software-enabled N+1 hot spare mode enables redundant backup for multiple EPRO AI NVR devices, fully supported by Intel, RK3588, and Novatek chips. One designated EPRO AI NVR acts as the standby unit, while N EPRO AI NVRs serve as active units. The chip platforms provide fast response capability, ensuring that when any active NVR fails, the standby NVR’s software will automatically take over all functions within seconds. This ensures zero downtime of the surveillance system, avoids video recording interruptions, and significantly enhances overall stability — critical for high-demand enterprise and industrial scenarios.</p><p><strong>Advanced ANR (Automatic Network Replenishment)</strong></p><p>A key highlight of the EPRO AI NVR, the ANR software ensures zero video loss even during network interruptions, with stable support from Intel, RK3588, and Novatek chips. When the network between the NVR and IP cameras is disconnected, the software triggers cameras to store video locally (via built-in SD card or local storage). Once the network is restored, the NVR software, backed by the three chip platforms, automatically synchronizes and supplements the locally stored video with zero latency, ensuring complete and continuous video recording without missing segments — ideal for unstable network environments.</p><p><strong>User-Friendly &amp; Secure Software Operation</strong></p><p>Intuitive GUI software interface with shortcut operations, supporting multi-user access control (up to 128 remote users simultaneously) for convenient management across multiple locations, with customizable user permission settings.</p><p>Built-in software-based cyber-security features, including data encryption, access control, and firmware encryption, protecting surveillance data from unauthorized access and tampering, complying with global data protection regulations.</p><p>Software-enabled remote configuration and maintenance, allowing administrators to adjust settings, update firmware, and troubleshoot issues remotely, reducing on-site maintenance costs.</p><p><strong>Dual UI Library Support</strong></p><p>Fully supports two mainstream UI libraries — LVGL (Light and Versatile Graphics Library) or Qt, providing flexible UI customization options. LVGL offers lightweight, high-performance graphics rendering, ideal for resource-constrained scenarios, while Qt enables rich, interactive, and cross-platform UI design, catering to diverse user interface needs and application scenarios.</p><p><strong>Ready for OEM and ODM</strong></p><p>We offer comprehensive OEM and ODM services for the EPRO AI NVR, fully leveraging the stable hardware support of Intel and Novatek chips and the flexible, scalable software framework to meet the customized needs of global partners. Our OEM/ODM solutions are designed to help partners quickly launch their own branded NVR products with reduced R&amp;D costs, shortened time-to-market, and full control over product positioning and branding.</p><p><a href="https://linkingvision.com/eproainvr">https://linkingvision.com/eproainvr</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d0d7af3f174" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HPro Secure Player (RTSPS(RTSP over TLS)/SRTP ) user guide]]></title>
            <link>https://medium.com/@linkingvision/hpro-secure-player-rtsps-rtsp-over-tls-srtp-user-guide-f045b9361424?source=rss-2eee62ff15c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f045b9361424</guid>
            <dc:creator><![CDATA[linkingvision]]></dc:creator>
            <pubDate>Mon, 22 Dec 2025 13:00:17 GMT</pubDate>
            <atom:updated>2025-12-22T13:00:17.689Z</atom:updated>
            <content:encoded><![CDATA[<ol><li>Download the windows install package hsp-win64-rx.xx.xx.xx.exe<br><a href="https://linkingvision.com/hprodownload">HPro Download | linkingvision</a></li></ol><p>2. Install the package</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*tw7xOcj2bsjBa3a9fJRfBA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/495/1*_9oc38B4w0fMUJZtZIyyUw.png" /></figure><p>3. open Network Stream with user password and URL</p><p>the URL can be RTSPS or RTSP<br>rtsps://10.168.1.142:322/axis-media/media.amp<br>rtsp://192.168.100.125</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/785/1*Hky79SFbeQe_LyrmozfWaw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/1*OoyQdZun2SX7VuS9GGee-w.png" /></figure><p>4. The Video start play</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/784/1*9JtjPV7e_TdS5YCTKcBvJQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/781/1*RyKIcDmDSp7kb78SwSrhjA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f045b9361424" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HPro AI NVR/ USC Text and image similarity search]]></title>
            <link>https://medium.com/@linkingvision/hpro-ai-nvr-usc-text-and-image-similarity-search-2af3728452e1?source=rss-2eee62ff15c------2</link>
            <guid isPermaLink="false">https://medium.com/p/2af3728452e1</guid>
            <dc:creator><![CDATA[linkingvision]]></dc:creator>
            <pubDate>Wed, 17 Dec 2025 01:53:18 GMT</pubDate>
            <atom:updated>2025-12-17T01:53:18.677Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6aBGFqoarANICvT82Rlblg.png" /></figure><p>By utilizing a multimodal large model, cross modal information retrieval applications between natural language and video images can be achieved. By inputting a sentence or a word, target images can be retrieved in seconds, making target retrieval wider, more accurate, faster, and easier. This allows security video backtracking to no longer be limited to traditional methods such as spatiotemporal and alarm retrieval, greatly improving the efficiency of target and event search, and making security business management more efficient and intelligent. Can help users quickly retrieve captured images and video clips that meet custom criteria. Support multiple search conditions such as keyword and time, and can perform text search and image search.<br>Here are some example, user search white car /motor /Benz car</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7T6OG2KvrmwxCRH1DvhYKQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cKv9lwcc8YLY_5qQ27Ozkg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JEAf0vw0ztctLNMdEVTKiw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Opi2KV-BfCoebFwX9c9aGw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2af3728452e1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to get RTSP low latency video from Avigilon Unity Video and ACC7/ACC6?]]></title>
            <link>https://medium.com/@linkingvision/how-to-get-rtsp-low-latency-video-from-avigilon-unity-video-and-acc7-acc6-72307fb059aa?source=rss-2eee62ff15c------2</link>
            <guid isPermaLink="false">https://medium.com/p/72307fb059aa</guid>
            <dc:creator><![CDATA[linkingvision]]></dc:creator>
            <pubDate>Tue, 16 Dec 2025 02:39:53 GMT</pubDate>
            <atom:updated>2025-12-16T02:39:53.560Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently, our project required integration with Avigilon ACC7. After some effort, we finally obtained Avigilon partners access. Avigilon Unity Video and ACC7 provide a RESTful API, but it seems somewhat limited, unable to retrieve low-latency video data. After some searching, we found Unity Video Media Gateway 8.6, but upon closer inspection, we discovered that this component is only used for transcoding and still cannot achieve low-latency video stream integration.</p><p>With no other options, we reverted to the Avigilon .NET SDK for ACC. This SDK is compatible with both Unity Video and ACC, but our products are based on native C++, while the manufacturer’s SDK is for a .NET environment. After some effort, we solved the problem using managed C++, making it easy to integrate Avigilon Unity Video and ACC7/ACC6 into H5S/USC. It allows for forwarding using RTSP/HLS/RTMP/WEBRTC protocols and direct video viewing in web, iOS, and Android environments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*Zw3F4ItSrnwmzSjy4goMSw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72307fb059aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to connect RTSPS(RTSP over TLS)/SRTP camera]]></title>
            <link>https://medium.com/@linkingvision/how-to-connect-rtsps-rtsp-over-tls-srtp-camera-807cf3190473?source=rss-2eee62ff15c------2</link>
            <guid isPermaLink="false">https://medium.com/p/807cf3190473</guid>
            <dc:creator><![CDATA[linkingvision]]></dc:creator>
            <pubDate>Tue, 16 Dec 2025 00:56:51 GMT</pubDate>
            <atom:updated>2025-12-16T01:56:03.569Z</atom:updated>
            <content:encoded><![CDATA[<p>In recent years, some camera and hard disk video recorder manufacturers have begun to support RTSPS (RTSP over TLS)/SRTP, but the universal player VLC currently does not support it. It is unknown whether there are plans for future support. This article takes Axis cameras as an example to introduce the process of configuring RTSPS/SRTP for H5S.</p><ol><li>First go to axis camera plainconfig to enable RTSPS. Copy the Certificate id name from Certificates Page.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/1*Y7do8MX877VFmdctnDt8QQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8n_PjxnM8vRSLsLPmXHgww.png" /></figure><p>2. Add the RTSPS address to H5S</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WRxThUj-TGDU4vqsmsUxBA.png" /></figure><p>3. Live view the camera video.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JeeRoDRof7ROalms_RAq9g.png" /></figure><p>4. Check the data is TLS based.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4l9RARNnSQXhNlPE4CuWOw.png" /></figure><p>5. Last let we check the SDP and Setup message, the message is SAVP.</p><p>o=- 11343850218222093006 1 IN IP4 192.168.100.155<br>s=Session streamed with GStreamer<br>i=rtsp-server<br>t=0 0<br>a=tool:GStreamer<br>a=type:broadcast<br>a=range:npt=now-<br>a=control:rtsp://192.168.100.155:322/axis-media/media.amp<br>m=video 0 RTP/SAVP 96<br>c=IN IP4 0.0.0.0<br>b=AS:50000<br>a=rtpmap:96 H264/90000<br>a=fmtp:96 packetization-mode=1;profile-level-id=420029;sprop-parameter-sets=Z0IAKeKQDwBE/LgLcBAQGlAAbd0AGb/MAPEiKg==,aM48gA==<br>a=key-mgmt:mikey AQAFAFUF/c4BAACA4miHAAAAAAsA7OspWXq5wwQKEBcknoFa8xBys6kR5cqK3JUBAAAAFQABAQEBEAIBAQMBCgcBAQgBAQoBAQAAACIAIAAepbnlvK4dPo4UUdtSdIUZ6QzlqXSO+NzRHQefk5TGAA==<br>a=ts-refclk:local<br>a=mediaclk:sender<br>a=recvonly<br>a=control:rtsp://192.168.100.155:322/axis-media/media.amp/stream=0<br>a=framerate:30.000000<br>a=transform:-1.000000,0.000000,0.000000;0.000000,-1.000000,0.000000;0.000000,0.000000,1.000000<br>m=audio 0 RTP/SAVP 0<br>c=IN IP4 0.0.0.0<br>b=AS:64<br>a=rtpmap:0 PCMU/8000<br>a=key-mgmt:mikey AQAFAFCcvxwBAABcD5nfAAAAAAsA7OspWXs0pEwKELRJYm2aBjIz4FUkeKoxNH8BAAAAFQABAQEBEAIBAQMBCgcBAQgBAQoBAQAAACIAIAAeNRZO8EuIqVuO0x/RqO2ydNFon+QehKtwsq4kOVENAA==<br>a=ts-refclk:local<br>a=mediaclk:sender<br>a=recvonly<br>a=control:rtsp://192.168.100.155:322/axis-media/media.amp/stream=1</p><p>SETUP rtsp://192.168.100.155:322/axis-media/media.amp/stream=1 RTSP/1.0<br>CSeq: 6<br>Authorization: Digest username=”root”, realm=”AXIS_ACCC8E6C4BF0&quot;, nonce=”000003deY585181f50aea0e72985ceaad4923e05d793c25&quot;, uri=”rtsp://192.168.100.155:322/axis-media/media.amp/”, response=”d15b70efe03b24d66236c28c9b442074&quot;<br>Transport: RTP/SAVP/TCP;unicast;interleaved=2–3<br>Session: .+GwPivnIsjOL2Mh<br>KeyMgmt: prot=mikey; uri=”rtsp://192.168.100.155:322/axis-media/media.amp/stream=1&quot;; data=”AQAFAH6TI0wBAACI6+7WAAAAAAsA7OspUf4JAt4KENxSkQ45q7XcXC+xbh2gUBQBAAAAGwABAQEBEAIBAQMBFAQBDgcBAQgBAQoBAQsBCgAAACcAIQAerjVFRvdx34mJkCVhPN7XQ7ucAdaIRvAr6W+79ImABLEaU6YA”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=807cf3190473" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>