|
|
| (6 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | | + | #REDIRECT [[Draft:RN/WebRTCMedia Service/100.0.072.0000]] |
| − | | |
| − | {{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{ type="failedice" }|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{ type="failedice" }|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}}
| |
Latest revision as of 06:30, June 20, 2023
This is a draft page; it has not yet been published.
