When adding ONVIF Bridge to XProtect 2025 R2 and attempting to stream via RTSP, an error (401 Unauthorized) occurs.

MIP
,
1

When adding ONVIF Bridge to XProtect 2025 R2 and attempting to stream via RTSP, an error (401 Unauthorized) occurs. rtsp://:@:554/live/

Therefore, I performed the following configuration steps for receiving RTSP with XProtect 2025 R2 + ONVIF Bridge. Please confirm whether the procedure is correct.

  1. Install XProtect 2025 R2

  2. Install ONVIF Bridge and restart the server

  3. Create the and that were entered during the ONVIF Bridge installation

  • Security > Basic Users > Create Basic User
  1. Set the role for the Basic User

  1. In the site navigation screen, click on “Roles”

  2. In the Roles screen, click “Administrators”

  3. In the role settings screen, select the basic user from the “Add” dropdown menu

  4. In the dialog “Select basic user to add to the role,” check the entered during ONVIF Bridge installation

  5. Save the settings

5)Add the created to the ONVIF user authentication information of the ONVIF Bridge

6)Execute rtsp://:@:554/live/ => 401 Unauthorized

Best Regards.

2

Additional information.

After the issue occurred, the following logs were output to [C:\ProgramData\Milestone\Milestone](file:C:/ProgramData/Milestone/Milestone) ONVIF Bridge Server\Logs.

In addition, there were no problems with the same settings in the environment using XProtect 2024 R2 + ONVIF. This issue started occurring after upgrading that environment to XProtect 2025 R2.

18-09-2025 08-41-04.014: Error - LoginToServer: exception, VideoOS.Platform.MIPException: Not logged in to any servers

at VideoOS.Platform.SDK.MultiUserEnvironment.LoginUserContext(UserContext userContext, String clientType)

at VideoOS.OnvifGateway.OnvifMipLibrary.OnvifMipLibraryClass.LoginToServer(String aUsername, String aPassword, Boolean aUsingAd, UserContext& aContext, String& aErrorLog)Login Failure from Login-1.

18-09-2025 08-41-04.143: Error - LoginToServer: exception, VideoOS.Platform.MIPException: Not logged in to any servers

at VideoOS.Platform.SDK.MultiUserEnvironment.LoginUserContext(UserContext userContext, String clientType)

at VideoOS.OnvifGateway.OnvifMipLibrary.OnvifMipLibraryClass.LoginToServer(String aUsername, String aPassword, Boolean aUsingAd, UserContext& aContext, String& aErrorLog)Login Failure from Login-1.

18-09-2025 08-41-04.251: Error - LoginToServer: exception, VideoOS.Platform.MIPException: Not logged in to any servers

at VideoOS.Platform.SDK.MultiUserEnvironment.LoginUserContext(UserContext userContext, String clientType)

at VideoOS.OnvifGateway.OnvifMipLibrary.OnvifMipLibraryClass.LoginToServer(String aUsername, String aPassword, Boolean aUsingAd, UserContext& aContext, String& aErrorLog)Login Failure from Login-1.

18-09-2025 08-41-04.251: Error - ImplementerHelper::GetRecorderServerUrl: GetRecorderServerUrl failure, hr:0, result:0, recorderURLIsNull:true

18-09-2025 08-41-04.253: Warning - RtspConnection::ProcessClientInput, bytes length provided by recv() is 0

18-09-2025 08-41-06.282: Warning - RtspConnection::ProcessClientInput, bytes length provided by recv() is 0

18-09-2025 08-41-08.292: Warning - RtspConnection::ProcessClientInput, bytes length provided by recv() is 0

Best Regards.

3

I have changed the title.

This issue concerns the inability to stream RTSP with XProtect 2025 R2 and the ONVIF Bridge. Since RTSP streaming was possible with XProtect 2024 R2 and the ONVIF Bridge, I am unable to upgrade XProtect and am experiencing difficulties.

Please let me know the cause and how to resolve this issue.

4

Please inform us about the current situation.

Due to this issue, we are unable to evaluate the solution based on XProtect 2025 R2, which poses a risk of delaying the release. We are quite concerned about this.

Even if there is no significant progress, we would appreciate it if you could at least report on the status of the investigation.

5

I would like to receive some kind of response.

Even if it is just “under investigation,” “unable to investigate,” or “not yet investigated,” that would be fine.

Thank you in advance.

Best Regards.

6

We compared the RTSP communication sequences of XProtect 2025 R2 and 2024 R2 using Wireshark.

In both cases, RTSP exchanges continued after receiving 401 Unauthorized, and subsequent RTSP packets (e.g., CSeq: 4) included an Authorization header, so authentication succeeded.

However, in the subsequent RTSP exchange with 2025 R2, the SETUP for the URL returns 404 Not Found.

This suggests the direct cause may be that XProtect is not accepting the very URL it advertised.

Since 2024 R2 accepted streamid=0, please let us know if there were any implementation changes in 2025 R2.

■XProtect 2024 R2(XProtect2024R2_RTSP.pcapng)

No.2878: from client to XProtect: Protocol=RTSP OPTIONS rtsp://192.168.1.150:554/live/073f4570-5649-4f82-bde7-837627c3f8f4/ RTSP/1.0 (CSeq:2)

No.2880: from XProtect to client: Protocol=RTSP RTSP/1.0 200 OK

No.2882: from client to XProtect: Protocol=RTSP DESCRIBE rtsp://192.168.1.150:554/live/073f4570-5649-4f82-bde7-837627c3f8f4/ RTSP/1.0 (CSeq:3)

No.2884: from XProtect to client: Protocol=RTSP RTSP/1.0 401 Unauthorized

No.2886: from client to XProtect: Protocol=RTSP DESCRIBE rtsp://192.168.1.150:554/live/073f4570-5649-4f82-bde7-837627c3f8f4/ RTSP/1.0 (CSeq:4)

No.2888: from XProtect to client: Protocol=RTSP/SDP RTSP/1.0 200 OK

      Content-Base: rtsp://192.168.1.150:554/live/073f4570-5649-4f82-bde7-837627c3f8f4/

      m=video 0 RTP/AVP 96

      a=rtpmap:96 H264/90000

      a=control:streamid=0

No.2890: from client to XProtect: Protocol=RTSP SETUP rtsp://192.168.1.150:554/live/073f4570-5649-4f82-bde7-837627c3f8f4/streamid=0 RTSP/1.0 (CSeq:5)

No.2892: from XProtect to client: Protocol=RTSP RTSP/1.0 200 OK

      Transport: RTP/AVP;unicast;client\_port=61290-61291;server\_port=4000-4001

No.2894: from client to XProtect: Protocol=RTSP PLAY rtsp://192.168.1.150:554/live/073f4570-5649-4f82-bde7-837627c3f8f4/ RTSP/1.0 (CSeq:6)

No.2896: from XProtect to client: Protocol=RTSP RTSP/1.0 200 OK

■XProtect 2025 R2(XProtect2025R2_RTSPerr.pcapng)

No.3621: from client to XProtect: Protocol=RTSP OPTIONS rtsp://172.16.3.170:554/live/849989a6-6c52-4cba-b0e6-9d1cc0320fb7/ RTSP/1.0 (CSeq:2)

No.3623: from XProtect to client: Protocol=RTSP RTSP/1.0 200 OK

No.3625: from client to XProtect: Protocol=RTSP DESCRIBE rtsp://172.16.3.170:554/live/849989a6-6c52-4cba-b0e6-9d1cc0320fb7/ RTSP/1.0 (CSeq:3)

No.3627: from XProtect to client: Protocol=RTSP RTSP/1.0 401 Unauthorized

No.3629: from client to XProtect: Protocol=RTSP DESCRIBE rtsp://172.16.3.170:554/live/849989a6-6c52-4cba-b0e6-9d1cc0320fb7/ RTSP/1.0 (CSeq:4)

No.3770: from XProtect to client: Protocol=RTSP/SDP RTSP/1.0 200 OK

      Content-Base: rtsp://172.16.3.170:554/live/849989a6-6c52-4cba-b0e6-9d1cc0320fb7/

      m=video 0 RTP/AVP 96

      a=rtpmap:96 H264/90000

      a=control:streamid=0

No.3772: from client to XProtect: Protocol=RTSP SETUP rtsp://172.16.3.170:554/live/849989a6-6c52-4cba-b0e6-9d1cc0320fb7/streamid=0 RTSP/1.0 (CSeq:5)

No.3990: from XProtect to client: Protocol=RTSP RTSP/1.0 404 Not Found

Best Regards.

7

I have also attached XProtect2024R2_RTSP.pcapng.

8

Additional note: Each “No.” refers to the packet number in Wireshark.

Thank you in advance.

9

I installed Open Network Bridge 2025 R2 on XProtect Professional+ 2025 R2.

I also added a user and password in Tray Manager.

By specifying the added user and password, I was able to obtain the video at: rtsp://:@:554/live/

My understanding is that the issue was resolved by using Open Network Bridge 2025 R2 instead of the ONVIF Bridge.

Can this be considered an officially supported solution?

If so, please explain the differences between the ONVIF Bridge and the Open Network Bridge.