Difference between revisions of "RN/WebRTC/100.0.011.0000"

From Genesys Documentation
Jump to: navigation, search
(Published)
 
(Published)
 
(2 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
|JQL=project = "WebRTC Media Service"  AND issue = WRTCMS-792
 
|JQL=project = "WebRTC Media Service"  AND issue = WRTCMS-792
 
|DeploymentTypeId=8b480b3c-2733-433a-9166-eab2c2d0663a, ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1
 
|DeploymentTypeId=8b480b3c-2733-433a-9166-eab2c2d0663a, ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1
−
|ReleaseDate=2021-09-21
+
|ReleaseDate=2021-09-30
−
|PrivateEditionReleaseDate=2021-09-21
+
|PrivateEditionReleaseDate=2021-09-22
−
|Highlight={{PrivateEditionBoilerplate|Boilerplate=4}}<br>DN@SwitchName format handled properly now.
+
|Highlight=v 100.0.011.0000 <br>
−
|Containers=* webrtc-service-100.0.010+0000.tgz
+
{{PrivateEditionBoilerplate|Boilerplate=4}}<br>Call hold operation handled properly now.
−
* webrtc:100.0.011.0000
+
|Containers=*webrtc-service-100.0.010+0000.tgz
−
* coturn:100.0.011.0000
+
*webrtc:100.0.011.0000
−
}}
+
*coturn:100.0.011.0000
−
{{Issue
 
−
|TicketNumber=WRTCMS-792
 
−
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
−
|LocalContent=WebRTC Media Service now handles the <tt>DN@SwitchName</tt> format properly in sign-in request. Previously, WebRTC Media Service incorrectly handled the <tt>DN@SwitcName</tt> format for JSON-based signaling protocol, resulting in an invalid SIP DN being registered.
 
 
}}
 
}}
 
{{Issue
 
{{Issue
Line 26: Line 22:
 
&nbsp;
 
&nbsp;
 
|SupportingDocumentation={{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|topic=ConfigSecurity}}<br />
 
|SupportingDocumentation={{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|topic=ConfigSecurity}}<br />
 +
}}
 +
{{Issue
 +
|TicketNumber=WRTCMS-798
 +
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 +
|LocalContent=The WebRTC Media Service JavaScript library now correctly processes call hold operations. Previously, when an agent tried to put a consultation call on hold, the library silently ignored the request from SIP Server. As a result, the call hold and its subsequent operations were delayed for 30 seconds due to the hold operation timeout.
 
}}
 
}}

Latest revision as of 01:15, October 20, 2021

Component RN Definition[edit source]

Component WebRTC Media Service
Deployment Type Private Edition, Genesys CX on AWS, Genesys CX on Azure
Release Number 100.0.011.0000 (Change release number)
Release Type
Highlight v 100.0.011.0000

Support for arbitrary UIDs in private edition deployments on OpenShift.
Call hold operation handled properly now.

Boilerplate(s) Used
Release Date 2021-09-30
Private Edition Release Date 2021-09-22
Mixed Mode Release ReleaseDate
Private Edition Containers List
  • webrtc-service-100.0.010+0000.tgz
  • webrtc:100.0.011.0000
  • coturn:100.0.011.0000
JQL project = "WebRTC Media Service" AND issue = WRTCMS-792
Links Links to customer-facing pages in use:
Test Links Links to test pages (for RN Admins only)

None yet!

Issue Issue Category Description SupportingDocumentation
Issue Issue Category Description SupportingDocumentation
WRTCMS-798 Resolved Issue The WebRTC Media Service JavaScript library now correctly processes call hold operations. Previously...
WRTCMS-764 Private Edition WebRTC now supports the use of arbitrary, or random, user IDs (UIDs) in OpenShift.
  • The Dockerfile ...
 OpenShift security settings
Retrieved from "https://all.docs.genesys.com/RN/WebRTC/100.0.011.0000 (2025-06-21 23:20:43)"
Comments or questions about this documentation? Contact us for support!