WikiSysop at 07:45, September 21, 2022

2022-09-21T07:45:49Z

WikiSysop: Created page with "{{ComponentRN |ComponentId=0371606b-df5e-41e2-869d-2009e76b916e |JQL=project = "WebRTC Media Service" AND id = WRTCMS-1057 OR id = WRTCMS-976 OR id = WRTCMS-1066 OR id = WRTCM..."

2022-09-16T16:30:57Z

Created page with "{{ComponentRN |ComponentId=0371606b-df5e-41e2-869d-2009e76b916e |JQL=project = "WebRTC Media Service" AND id = WRTCMS-1057 OR id = WRTCMS-976 OR id = WRTCMS-1066 OR id = WRTCM..."

New page

{{ComponentRN
|ComponentId=0371606b-df5e-41e2-869d-2009e76b916e
|JQL=project = "WebRTC Media Service" AND id = WRTCMS-1057 OR id = WRTCMS-976 OR id = WRTCMS-1066 OR id = WRTCMS-1055
|DeploymentTypeId=8b480b3c-2733-433a-9166-eab2c2d0663a
|ReleaseDate=2022-09-16
|PrivateEditionReleaseDate=2022-09-16
|Highlight=Resolved issue and improvements.
}}
{{Issue
|TicketNumber=WRTCMS-1066
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=Previously, WebRTC Service incorrectly handled next scenario:# WebRTC client sends sign_in request to the WebRTC Gateway# WebRTC Gateway starts authentication procedure on GAuth service# Client is disconnected from the WebRTC Gateway# Authentication process is finishedAs result, WebRTC Gateway created a stale session without corresponding HTTP client which could affect real agent’s sessions.Now WebRTC Service does not create a stale session in case of the provided scenario.
|LocalContent=WebRTC Media Service now avoids the creation of a stale session while authenticating a <code>sign_in</code> request from a client. Previously, when WebRTC Media Service handled the scenario in the following way, it led to a situation where the WebRTC Gateway created a stale session without an HTTP client, affecting the active agent’s sessions.

#The WebRTC client sends a <code>sign_in</code> request to the WebRTC Gateway.
#The WebRTC Gateway starts the authentication procedure on GAuth service.
#The client is disconnected from the WebRTC Gateway and the authentication process is completed.<br />
}}
{{Issue
|TicketNumber=WRTCMS-1057
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=Previously, WebRTC Gateway incorrectly encoded HTTP-requests to GAuth that caused an incorrect processing on new GAuth deployment.Now WebRTC Gateway encodes correctly HTTP-requests to GAuth
|LocalContent=WebRTC Gateway now correctly encodes the HTTP requests to GAuth Service. Previously, the WebRTC Gateway incorrectly encoded the HTTP requests. This led to incorrect processing on new GAuth deployments.
}}
{{Issue
|TicketNumber=WRTCMS-1055
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=Previously, WebRTC gateway did not detect 503 error from GAuth and with this the metric Availability of GAuth was exposed incorrectly in some circumstances.Now WebRTC gateway exposes Availability of GAuth exposes correctly
|LocalContent=WebRTC Gateway now correctly exposes the availability of GAuth Service. Previously, the WebRTC Gateway was not able to detect the 503 error from the GAuth Service. This led to incorrect exposure of the GAuth metric availability.
}}
{{Issue
|TicketNumber=WRTCMS-976
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
|Content=WebRTC service now implements golden signals-based observability that enables a global view of overall service health. Four golden signals include metrics for traffic, latency, errors, saturation:See the Google SRE book ([https://sre.google/sre-book/monitoring-distributed-systems/#xref_monitoring_golden-signals
|LocalContent=WebRTC Media Service now implements observability based on golden signals that enables a global view of the overall service health. The four golden signals include metrics for traffic, latency, errors, and saturation. For more information, see [https://sre.google/sre-book/monitoring-distributed-systems/#xref_monitoring_golden-signals Google SRE book].
}}

@@ Line 6: / Line 6: @@
 |PrivateEditionReleaseDate=2022-09-16
 |Highlight=Resolved issue and improvements.
 }}
 {{Issue
@@ Line 28: / Line 18: @@
 |Content=Previously, WebRTC gateway did not detect 503 error from GAuth and with this the metric Availability of GAuth was exposed incorrectly in some circumstances.Now WebRTC gateway exposes Availability of GAuth exposes correctly
 |LocalContent=WebRTC Gateway now correctly exposes the availability of GAuth Service. Previously, the WebRTC Gateway was not able to detect the 503 error from the GAuth Service. This led to incorrect exposure of the GAuth metric availability.
 }}

RN/WebRTCMedia Service/100.0.052.0000 - Revision history

WikiSysop at 07:45, September 21, 2022

WikiSysop: Created page with "{{ComponentRN |ComponentId=0371606b-df5e-41e2-869d-2009e76b916e |JQL=project = "WebRTC Media Service" AND id = WRTCMS-1057 OR id = WRTCMS-976 OR id = WRTCMS-1066 OR id = WRTCM..."