GB/T 28181 is being deployed in an increasing number of video surveillance camera scenarios. Thanks to its excellent networking performance, superior platform compatibility and comprehensive video surveillance functions, GB/T 28181 is widely adopted in many projects for video surveillance networking, video stream retrieval, surveillance management, and integration with streaming capabilities of third-party platforms.

During deployment, GB/T 28181 parameters of cameras need to be configured. A 20-digit national standard ID is required in this setup. Many users struggle to distinguish between the SIP user authentication ID and the video channel coding ID.

The SIP User ID is a 20-digit identifier assigned by the GB/T 28181 server to the camera. This ID must match the value allocated by the server, and paired with the corresponding password, to establish proper communication with the server. Only after both the SIP User ID and password pass verification can the camera be displayed normally on the GB/T 28181 server.

Besides the SIP User ID, there is another parameter called the video channel coding ID. In some cases, the camera works even if this ID is left unconfigured, yet its presentation on the GB/T 28181 platform varies. If the video channel coding ID is identical to the SIP User ID, the platform will identify the device as a camera.

If the video channel coding ID differs from the SIP User ID, many GB/T 28181 platforms will recognize the device as a video recorder.

The reason lies in the working mechanism of this national standard. GB/T 28181 was originally designed for networking and features inherent hierarchical interconnection. Higher-level systems can retrieve the directory structure from lower-level devices. Video, audio and alarm devices are represented by separate national standard IDs for easy access and management.

When the video channel coding ID is different from the SIP authentication ID, the GB/T 28181 platform treats the camera as a host surveillance device with subordinate endpoints, and video preview can only be accessed via the directory tree.

For single-lens cameras, introducing an extra subordinate layer creates operational inconvenience. Therefore, in project configuration, it is best practice to set the SIP User ID equal to the video channel coding ID.

So when should the two IDs be different? For multi-lens cameras, the video channel coding IDs must be configured with distinct values. This allows the GB/T 28181 platform to accurately identify and pull up the image from the specific lens you wish to view.