Difference between revisions of "Draft: RN/WebRTCMedia Service/100.0.069.0000"

From Genesys Documentation
Jump to: navigation, search
(Created page with " {{ComponentRN|ComponentId=0371606b-df5e-41e2-869d-2009e76b916e|JQL=labels=WebRTCRN10000690000|ReleaseNumber=}}{{Issue|JiraType=Defect|Content=Previously, WebRTC Gateway inco...")
 
Line 1: Line 1:
 +
{{ComponentRN
 +
|ComponentId=0371606b-df5e-41e2-869d-2009e76b916e
 +
|JQL=labels=WebRTCRN10000690000
 +
|DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1, 8b480b3c-2733-433a-9166-eab2c2d0663a
 +
|ReleaseDate=2023-05-12
 +
|PrivateEditionReleaseDate=2023-05-12
 +
|Highlight=* New traces for ICE failures.
  
 +
* Resolved issues.
 +
}}
 +
{{Issue
 +
|TicketNumber=WRTCMS-1278
 +
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 +
|Content=Previously, WebRTC Gateway incorrectly handled responses from GWS Configuration Service if “Content-length“ header in lower case.Now, “Content-length“ header in lower case is processed correctly.
 +
|LocalContent=WebRTC Gateway now correctly processes the <code>Content-length</code>  header irrespective of the casing of the text it contains. Previously, WebRTC Gateway incorrectly handled responses from GWS Configuration Service if the <code>Content-length</code>  header contained text in lower case.
 +
}}
 +
{{Issue
 +
|TicketNumber=WRTCMS-1273
 +
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 +
|Content=Log messages from different threads interrupts each other because of \r\n in SIP or other messages and one single message takes few lines.Now in case of output of logs into stdout these chars \r and \n are escaped and multiline messages take single line
 +
|LocalContent=If log messages are written to stdout, the ''\r'' and ''\n'' characters are escaped and multiline messages now occupy only a single line. Previously, log messages from different threads overlapped with  each other because of the ''\r'' and ''\n'' characters in SIP or other messages, causing a single line message to span multiple lines.
 +
}}
 +
{{Issue
 +
|TicketNumber=WRTCMS-1218
 +
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 +
|Content=WebRTC Gateway metrics were reworked and new tenant dimension was added to tenant-related metrics
 +
|LocalContent=WebRTC Gateway metrics have been reworked and a new tenant dimension has been added to the tenant-related metrics.
 +
}}
 +
{{Issue
 +
|TicketNumber=WRTCMS-1214
 +
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
 +
|Content=New traces are added for case if ICE failure "SYS", "ICEFailed", "ICE State moved to FAILED, remote candidates are present""SYS", "ICEFailed", "ICE State moved to FAILED, no remote candidates""SYS", "ICEFailed", "ICE Failed during established connection"Also new metric is added for ICE failed case:wrtc_system_errors&lbrace; type="failedice" &rbrace;
 +
|LocalContent=The following new traces are added for ICE failures:
  
{{ComponentRN|ComponentId=0371606b-df5e-41e2-869d-2009e76b916e|JQL=labels=WebRTCRN10000690000|ReleaseNumber=}}{{Issue|JiraType=Defect|Content=Previously, WebRTC Gateway incorrectly handled responses from GWS Configuration Service if “Content-length“ header in lower case.Now, “Content-length“ header in lower case is processed correctly.|LocalContent=Previously, WebRTC Gateway incorrectly handled responses from GWS Configuration Service if “Content-length“ header in lower case.Now, “Content-length“ header in lower case is processed correctly.|LastUpdated=May 05, 2023 3:50 PM|TicketNumber=WRTCMS-1278|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1}}{{Issue|JiraType=Task|Content=Log messages from different threads interrupts each other because of \r\n in SIP or other messages and one single message takes few lines.Now in case of output of logs into stdout these chars \r and \n are escaped and multiline messages take single line|LocalContent=Log messages from different threads interrupts each other because of \r\n in SIP or other messages and one single message takes few lines.Now in case of output of logs into stdout these chars \r and \n are escaped and multiline messages take single line|LastUpdated=May 05, 2023 3:50 PM|TicketNumber=WRTCMS-1273|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1}}{{Issue|JiraType=Task|Content=N/A, internal change for CloudFormation template|LocalContent=N/A, internal change for CloudFormation template|LastUpdated=May 05, 2023 3:50 PM|TicketNumber=WRTCMS-1267|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1}}{{Issue|JiraType=Task|Content=WebRTC Gateway metrics were reworked and new tenant dimension was added to tenant-related metrics|LocalContent=WebRTC Gateway metrics were reworked and new tenant dimension was added to tenant-related metrics|LastUpdated=May 05, 2023 3:50 PM|TicketNumber=WRTCMS-1218|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1}}{{Issue|JiraType=Improvement|Content=New traces are added for case if ICE failure "SYS", "ICEFailed", "ICE State moved to FAILED, remote candidates are present""SYS", "ICEFailed", "ICE State moved to FAILED, no remote candidates""SYS", "ICEFailed", "ICE Failed during established connection"Also new metric is added for ICE failed case:wrtc_system_errors&lbrace; type="failedice" &rbrace;|LocalContent=New traces are added for case if ICE failure "SYS", "ICEFailed", "ICE State moved to FAILED, remote candidates are present""SYS", "ICEFailed", "ICE State moved to FAILED, no remote candidates""SYS", "ICEFailed", "ICE Failed during established connection"Also new metric is added for ICE failed case:wrtc_system_errors&lbrace; type="failedice" &rbrace;|LastUpdated=May 05, 2023 3:50 PM|TicketNumber=WRTCMS-1214|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72}}{{Issue|JiraType=Task|Content=Now, in case of SIP registration failure. webrtc gateway will not drop active call but preserve RTP stream to allow agent continue to talk with customer.|LocalContent=Now, in case of SIP registration failure. webrtc gateway will not drop active call but preserve RTP stream to allow agent continue to talk with customer.|LastUpdated=May 05, 2023 3:50 PM|TicketNumber=WRTCMS-1178|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1}}
+
* SYS, ICEFailed, ICE State moved to FAILED, remote candidates are present
 +
* SYS, ICEFailed, ICE State moved to FAILED, no remote candidates
 +
* SYS, ICEFailed, ICE Failed during established connection
 +
 
 +
Also, a new metric, <code>wrtc_system_errors&lbrace; type="failedice" &rbrace;</code>, is added for ICE failures.
 +
}}
 +
{{Issue
 +
|TicketNumber=WRTCMS-1178
 +
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 +
|Content=Now, in case of SIP registration failure. webrtc gateway will not drop active call but preserve RTP stream to allow agent continue to talk with customer.
 +
|LocalContent=Now, in case of a SIP registration failure. WebRTC Gateway does not drop an active call but preserves the RTP stream to allow agents to continue talking with customer.
 +
}}

Revision as of 16:00, May 8, 2023

This is a draft page; it has not yet been published.

Component RN Definition[edit source]

Component WebRTC Media Service
Deployment Type Genesys CX on AWS, Genesys CX on Azure, Private Edition
Release Number 100.0.069.0000 (Change release number)
Release Type
Highlight * New traces for ICE failures.
  • Resolved issues.
Boilerplate(s) Used
Release Date 2023-05-12
Private Edition Release Date 2023-05-12
Mixed Mode Release ReleaseDate
Private Edition Containers List
JQL labels=WebRTCRN10000690000
Links Links to customer-facing pages in use:
Test Links Links to test pages (for RN Admins only)

None yet!

No results