RN/WebRTCMedia Service/100.0.067.0000 - Revision history

WikiSysop at 09:31, April 5, 2023

2023-04-05T09:31:47Z

WikiSysop at 10:01, March 21, 2023

2023-03-21T10:01:04Z

WikiSysop: Created page with "{{ComponentRN |ComponentId=0371606b-df5e-41e2-869d-2009e76b916e |JQL=labels=webrtcrn067 |DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389..."

2023-03-21T09:31:02Z

Created page with "{{ComponentRN |ComponentId=0371606b-df5e-41e2-869d-2009e76b916e |JQL=labels=webrtcrn067 |DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389..."

New page

{{ComponentRN
|ComponentId=0371606b-df5e-41e2-869d-2009e76b916e
|JQL=labels=webrtcrn067
|DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1
|ReleaseDate=2023-03-23
|Highlight=Support for Ambassador cloud design pattern on Azure.

New bandwidth-related metrics.

Other improvements and resolved issues.
}}
{{Issue
|TicketNumber=WRTCMS-1237
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|DeploymentTypeId=5439f1be-1868-4091-b058-1667389b6ce1
|Content=Azure: KEDA autoscaler now created with ignoreNullValues: "false" to make KEDA show warning instead of transferring 0 to HPAAlso name of metric in KEDA ScaledObject is changed - added color into metricName
|LocalContent=The KEDA autoscaler is now created with <code>ignoreNullValues</code> set to '''false''' to enable KEDA to show a warning instead of transferring 0 to HPA. Also, the name of the metric in <code>KEDA ScaledObject</code> is changed; <code>color</code> is added into the <code>metricName</code>.
}}
{{Issue
|TicketNumber=WRTCMS-1186
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
|Content=WebRTC now retry SIP REGISTER in case of error/timeout - In cases when SIP Registration fails due to the network disruption, SIP Proxy instance unavailability, webrtc gateway will attempt to retry/recover SIP registration.
|LocalContent=WebRTC now retries sending a SIP REGISTER request in case of an error or timeout when SIP Registration fails due to a network disruption or the SIP Proxy instance is unavailable. Previously, when a SIP REGISTER transaction failed for some reason, WebRTC Gateway immediately terminated the corresponding session, that may have resulted in unexpected call terminations. This functionality is turned off by default.
}}
{{Issue
|TicketNumber=WRTCMS-1185
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
|Content=WebRTC gateway now supports RTP inactivity timeout to detect dropped/no-audio calls. By default its turned off
|LocalContent=WebRTC Gateway now supports RTP inactivity timeout to detect dropped or no-audio calls. This is turned off by default.
}}
{{Issue
|TicketNumber=WRTCMS-1145
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
|Content=New bandwidth-related metrics were added for webrtc gateway:wrtc_current_audio_bandwidth_web_inbound_kbpswrtc_current_audio_bandwidth_web_outbound_kbpswrtc_current_audio_bandwidth_sip_inbound_kbpswrtc_current_audio_bandwidth_sip_outbound_kbps
|LocalContent=The following new bandwidth-related metrics are added for the WebRTC Gateway:

*<code>wrtc_current_audio_bandwidth_web_inbound_kbps</code>
*<code>wrtc_current_audio_bandwidth_web_outbound_kbps</code>
*<code>wrtc_current_audio_bandwidth_sip_inbound_kbps</code>
*<code>wrtc_current_audio_bandwidth_sip_outbound_kbps</code><br>
}}
{{Issue
|TicketNumber=WRTCMS-1077
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
|DeploymentTypeId=5439f1be-1868-4091-b058-1667389b6ce1
|Content=Azure: helm-charts are updated to support of Ambassador in Azure
|LocalContent=Helm-charts are updated to support the Ambassador design pattern in Azure.
}}
{{Issue
|TicketNumber=WRTCMS-981
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a
|Content=AWS: now WebRTC uses log streaming to Grafana Cloud Loki for Docker based services in Engage Cloud on AWS.
|LocalContent=WebRTC now uses log streaming to Grafana Cloud Loki for Docker based services in Engage Cloud on AWS.
}}
{{Issue
|TicketNumber=WRTCMS-915
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=Now, session cookie is cleared on sign-out API request
|LocalContent=Now, session cookies are cleared on receiving a <code>sign-out</code> API request.
}}
{{Issue
|TicketNumber=WRTCMS-861
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=Now webrtc clients will be able to automatically re-signin at new active WebRTC deployment after cutover.
|LocalContent=WebRTC clients can now automatically re-login at a new active WebRTC deployment after cutover.
}}

@@ Line 2: / Line 2: @@
 |ComponentId=0371606b-df5e-41e2-869d-2009e76b916e
 |JQL=labels=webrtcrn067
-|DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1
+|DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1, 8b480b3c-2733-433a-9166-eab2c2d0663a
 |ReleaseDate=2023-03-23
 |Highlight=Support for Ambassador cloud design pattern on Azure.

@@ Line 21: / Line 21: @@
 |IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
 |Content=WebRTC now retry SIP REGISTER in case of error/timeout - In cases when SIP Registration fails due to the network disruption, SIP Proxy instance unavailability, webrtc gateway will attempt to retry/recover SIP registration.
-|LocalContent=WebRTC now retries sending a SIP REGISTER request in case of an error or timeout when SIP Registration fails due to a network disruption or the SIP Proxy instance is unavailable. Previously, when a SIP REGISTER transaction failed for some reason, WebRTC Gateway immediately terminated the corresponding session, that may have resulted in unexpected call terminations. This functionality is turned off by default.
+|LocalContent=WebRTC now retries sending a SIP REGISTER request in case of an error or timeout when SIP Registration fails due to a network disruption or the SIP Proxy instance is unavailable. Previously, when a SIP REGISTER transaction failed, WebRTC Gateway immediately terminated the corresponding session and that may have resulted in unexpected call terminations. This functionality is turned off by default.
 }}
 {{Issue