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

2023-10-05T15:00:56Z

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

New page

{{ComponentRN
|ComponentId=0371606b-df5e-41e2-869d-2009e76b916e
|JQL=labels=WebRTCRN10000740000
|DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1, 8b480b3c-2733-433a-9166-eab2c2d0663a
|ReleaseDate=2023-09-29
|PrivateEditionReleaseDate=2023-10-05
|Highlight=*Coturn server version 4.6.2.
*Metrics in Prometheus format.
*Custom environment variables in helm charts.
*New command-line option, '''ice-addr-filter.'''
*Resolved issues.
}}
{{Issue
|TicketNumber=WRTCMS-1350
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
|Content=Now WebRTC microservice uses 4.6.2 version of Coturn serverPrevious version: 4.5.1
|LocalContent=The WebRTC microservice now uses Coturn server version 4.6.2. The previously used version was 4.5.1.
}}
{{Issue
|TicketNumber=WRTCMS-1349
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
|Content=Now Coturn can expose metrics in prometheus format. For this, Coturn must be started with “--prometheus“ command line argument that can be set with using of “WEBRTC_COTURN_CMD_ARGS” environment variable.Metrics are exposed on 9641 port as HTTP response for “/metrics“ path
|LocalContent=Now, Coturn can expose metrics in the Prometheus format. To enable this, start Coturn with the <code>--prometheus</code> command line argument that can be set using the <code>WEBRTC_COTURN_CMD_ARGS</code> environment variable.

Metrics are exposed on the '''9641''' port as an HTTP response under ''/metrics''.
}}
{{Issue
|TicketNumber=WRTCMS-1347
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|DeploymentTypeId=8b480b3c-2733-433a-9166-eab2c2d0663a
|Content=*Applicable for PrivateEdition only:* Previously, some SIP and other log messages for “stdout” logging mode were not escaped properly for correct expose in JSON format.Now all of log messages are escaped properly.
|LocalContent=All log messages are now escaped properly. Previously, some SIP and other log messages for '''stdout''' logging mode were not escaped properly for correct exposure in the JSON format.
}}
{{Issue
|TicketNumber=WRTCMS-1346
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=Previously, dynamic Call-stats of RTP quality can contain incorrect reporting in case of long answer on agent side.Now WebRTC gateway does not report Dynamic Call-stats in case if RTP is not fully established.
|LocalContent=WebRTC Gateway no longer reports dynamic call-stats if RTP is not fully established. Previously, dynamic call-stats of RTP quality could contain incorrect reporting in case of a long time to answer on the agent side.
}}
{{Issue
|TicketNumber=WRTCMS-1337
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|DeploymentTypeId=8b480b3c-2733-433a-9166-eab2c2d0663a
|Content=*Applicable for Private Edition only:* Now, in case if if option “not-reinvite-web-on-empty“ set to “true” and Webrtc Gateway receives re-INVITE from SIP-side during DTLS negotiation - this re-INVITE is processed correctly.
|LocalContent=If the <code>not-reinvite-web-on-empty</code> option is set to ''true'' and the WebRTC Gateway receives a re-INVITE from the SIP-side during a DTLS negotiation, the re-INVITE is now processed correctly.
}}
{{Issue
|TicketNumber=WRTCMS-1329
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=Now, exposed prometheus statistics for lost, error and jitter stats are processed correctly
|LocalContent=Now, exposed Prometheus statistics for lost, error, and jitter stats are processed correctly.
}}
{{Issue
|TicketNumber=WRTCMS-1325
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
|Content=Now, helm-charts allow to set custom environment variables for gateway and coturn containers.Please review gateway.envVars and coturn envVars options in values-template.yaml that demonstrates the usage
|LocalContent=Now, helm charts allow to set custom environment variables for the Gateway and Coturn containers. The <code>gateway.envVars</code> and <code>coturn.envVars</code> options in the '''values-template.yaml''' file demonstrate the usage of custom environment variables.
}}
{{Issue
|TicketNumber=WRTCMS-1323
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=Previously, if JSAPI client cannot collect any candidate from TURN server - it continuously restarted ICE timer to gather ICE candidates.Now, JSAPI client will send empty list of candidates if timer is expired and no ICE candidates are collected.
|LocalContent=Now, the JSAPI client will send an empty list of candidates if the ICE timer has expired and no ICE candidates are collected. Previously, if the JSAPI client cannot collect any candidate from the TURN server, it continuously restarted the ICE timer to gather ICE candidates.
}}
{{Issue
|TicketNumber=WRTCMS-1322
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
|Content=New monitoring message is available for case if HTTP connection with webrtc agent is experiencing delays and the queue of HTTP-requests are growing:type: "SYS", method: "HTTPQueue Grows", message "HTTP queue is 2 or more, connection with agent is unstable"
|LocalContent=A new monitoring message is available for case if an HTTP connection with the WebRTC agent is experiencing delays and the queue of HTTP-requests is growing:

Type: <code>SYS</code>

Method: <code>HTTPQueue Grows</code>

Message: ''HTTP queue is 2 or more, connection with agent is unstable''.
}}
{{Issue
|TicketNumber=WRTCMS-1315
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
|Content=New statistics are available:# counter, increased if during the call gateway received 0 bytes from WEB-legwrtc_rtp_zero_bytes{ type="gateway_rcv" }# counter, increased if during the call gateway sent 0 bytes to WEB-legwrtc_rtp_zero_bytes{ type="gateway_snd" }# counter, increased if during the call gateway received 0 bytes from SIP-legwrtc_rtp_zero_bytes{ type="sip_rcv" }# counter, increased if during the call gateway sent 0 bytes to SIP-legwrtc_rtp_zero_bytes{ type="sip_snd" }
|LocalContent=The following new statistics are available:

*<code>wrtc_rtp_zero_bytes{ type="gateway_rcv" }</code> - counter, increased if Gateway received 0 bytes from the WEB-leg during the call.
*<code>wrtc_rtp_zero_bytes{ type="gateway_snd" }</code> - counter, increased if Gateway sent 0 bytes to the WEB-leg during the call.
*<code>wrtc_rtp_zero_bytes{ type="sip_rcv" }</code> - counter, increased if Gateway received 0 bytes from the SIP-leg during the call.
*<code>wrtc_rtp_zero_bytes{ type="sip_snd" }</code> - counter, increased if Gateway sent 0 bytes to the SIP-leg during the call.
}}
{{Issue
|TicketNumber=WRTCMS-1314
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
|Content=New command-line option “ice-addr-filter“ is available, to ignore ICE candidates collected on gateway side. IP addresses of candidates that match the filer - will be ignored and not send to webrtc client.Value is CIDR block or particular IP address. Examples:-ice-addr-filter 172.17.0.1.1-ice-addr-filter 172.17.0.1/24-ice-addr-filter 172.17.0.1/16
|LocalContent=A new command-line option, '''ice-addr-filter''', is now available to ignore ICE candidates collected on the gateway side. IP addresses of candidates that match the filter will be ignored and not sent to the WebRTC client.

The value is the CIDR block or particular IP address as shown in the below examples:

<code>-ice-addr-filter 172.17.0.1.1</code>

<code>-ice-addr-filter 172.17.0.1/24</code>

<code>-ice-addr-filter 172.17.0.1/16</code>
}}

RN/WebRTCMedia Service/100.0.074.0000 - Revision history

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