VIH-11028 redirect to service error on primary device when participant connects on a secondary device

[shaed-parkar]

Jira link

VIH-11028

Change description

There is an outstanding issue involving users who connect to the same hearing with the same account on multiple devices. This typically results in a disconnect of the former connection. However, this overlaps with a retry connection logic which attempts to dial back into the conference after a period of time. This causes both logged in browsers to battle for who is connected and results in a bad experience.

A solution is to capture the reason from the supplier, and if the reason contains the message 'connected on another device' and the participant's call tag, then redirect the user away from the hearing room.

Capture the reason from the callback event and publish it to the participant status message.

Participant Status Message Enhancements:

• VideoWeb/VideoWeb.EventHub/Handlers/Core/EventHandlerBase.cs: Added a reason parameter to the PublishParticipantStatusMessage method and updated its calls.

Interface and Unit Test Updates:

• VideoWeb/VideoWeb.EventHub/Hub/IEventHubClient.cs: Added a reason parameter to the ParticipantStatusMessage method.

Dependency Updates:

• VideoWeb/VideoWeb/ClientApp/package-lock.json: Updated puppeteer from version 23.2.0 to 23.5.1 and @puppeteer/browsers from version 2.3.1 to 2.4.0. [1] [2]

[sonarqubecloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud