Draft:RN/WebRTCMedia Service/100.0.069.0000 - Revision history

WikiSysop: Redirected page to Draft:RN/WebRTCMedia Service/100.0.072.0000

2023-06-20T06:30:39Z

Redirected page to Draft:RN/WebRTCMedia Service/100.0.072.0000

WikiSysop at 06:00, June 20, 2023

2023-06-20T06:00:41Z

WikiSysop at 10:30, June 19, 2023

2023-06-19T10:30:58Z

WikiSysop at 21:01, May 10, 2023

2023-05-10T21:01:06Z

WikiSysop at 16:01, May 9, 2023

2023-05-09T16:01:06Z

WikiSysop at 15:01, May 9, 2023

2023-05-09T15:01:10Z

WikiSysop at 16:00, May 8, 2023

2023-05-08T16:00:51Z

WikiSysop: Created page with " {{ComponentRN|ComponentId=0371606b-df5e-41e2-869d-2009e76b916e|JQL=labels=WebRTCRN10000690000|ReleaseNumber=}}{{Issue|JiraType=Defect|Content=Previously, WebRTC Gateway inco..."

2023-05-05T10:30:49Z

Created page with " {{ComponentRN|ComponentId=0371606b-df5e-41e2-869d-2009e76b916e|JQL=labels=WebRTCRN10000690000|ReleaseNumber=}}{{Issue|JiraType=Defect|Content=Previously, WebRTC Gateway inco..."

New page

{{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}}

← Older revision		Revision as of 06:30, June 20, 2023
Line 1:		Line 1:
−	~~{{ComponentRN~~	+	#REDIRECT [[Draft:RN/WebRTCMedia Service/100.0.072.0000]]
−	~~\|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-15~~
−	~~\|PrivateEditionReleaseDate=2023-05-15~~
−	~~\|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{ type="failedice" }
−	~~\|LocalContent=The following new traces are added for ICE failures~~:
−
−	*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{type="failedice"}<~~/~~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.~~
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=WRTCMS-1280~~
−	~~\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1~~
−	\|LocalContent=Previously, WebRTC Gateway experienced 10ms gaps in jitter calculation. Now, jitter calculation is more reliable. Also, call stats are reported in monitoring messages for calls every 10 seconds.
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=WRTCMS-1281~~
−	~~\|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72~~
−	~~\|LocalContent=Gateway jitter is now also reported as a histogram for the '''wrtc_rtp_gateway_jitter_ms_bucket''' metric.~~
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=WRTCMS-1297~~
−	~~\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1~~
−	\|LocalContent=Now, <code>http-request GET/options</code> to the monitoring port shows all current options in plain text format. For example, <code>curl http://localhost:10052/options</code>. Also, at startup, WebRTC Gateway pushes a monitoring message with type <code>SYS</code> and method <code>Options</code>, and a message that contains the complete set of options in JSON format.
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=WRTCMS-1298~~
−	~~\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1~~
−	\|LocalContent=In case of connectivity issues with GAuth, Environment or Config services of GWS, WebRTC Gateway now pushes monitoring messages with type <code>SYS</code> and methods <code>Auth Service Failed</code>, <code>Env Service ~~Failed<~~/~~code>, <code>Cfg Service Failed</code>, and messages that contain the info about the failure, which can help understand the reason for the connectivity issue without having to download logs.~~
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=WRTCMS-1302~~
−	~~\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1~~
−	~~\|LocalContent=The JSON format for the dashboard located in the helm chart now shows correctly updated metrics~~.
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=WRTCMS-1310~~
−	~~\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1~~
−	~~\|LocalContent=WebRTC Gateway no longer crashes if the DN or Agent Name contains '''%s'''~~. ~~Previously, WebRTC Gateway could crash in such cases~~.
−	}}

@@ Line 58: / Line 58: @@
 |TicketNumber=WRTCMS-1297
 |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
-|LocalContent=Now, <code>http-request GET/options</code> to monitoring port shows all current options in plain text format. For example, <code>curl http://localhost:10052/options</code>. Also, at startup, WebRTC Gateway pushes a monitoring message with type <code>SYS</code> and method <code>Options</code>, and a message that contains the complete set of options in JSON format.
+|LocalContent=Now, <code>http-request GET/options</code> to the monitoring port shows all current options in plain text format. For example, <code>curl http://localhost:10052/options</code>. Also, at startup, WebRTC Gateway pushes a monitoring message with type <code>SYS</code> and method <code>Options</code>, and a message that contains the complete set of options in JSON format.
 }}
 {{Issue
 |TicketNumber=WRTCMS-1298
 |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
-|LocalContent=In case of connectivity issues with GAuth, Environment or Config services of GWS, WebRTC Gateway now pushes monitoring messages with type <code>SYS</code> and methods <code>Auth Service Failed</code>, <code>Env Service Failed</code>, <code>Cfg Service Failed</code>, and messages that contains the info about the failure, which can help understand the reason for the connectivity issue without having to download logs.
+|LocalContent=In case of connectivity issues with GAuth, Environment or Config services of GWS, WebRTC Gateway now pushes monitoring messages with type <code>SYS</code> and methods <code>Auth Service Failed</code>, <code>Env Service Failed</code>, <code>Cfg Service Failed</code>, and messages that contain the info about the failure, which can help understand the reason for the connectivity issue without having to download logs.
 }}
 {{Issue
 |TicketNumber=WRTCMS-1302
 }}

@@ Line 37: / Line 37: @@
 *SYS, ICEFailed, ICE Failed during established connection
-Also, a new metric, <code>wrtc_system_errors&amp;#10100; type="failedice" &amp;#10101;</code>, is added for ICE failures.
+Also, a new metric, <code>wrtc_system_errors{type="failedice"}</code>, is added for ICE failures.
 }}
 {{Issue

@@ Line 37: / Line 37: @@
 *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.
+Also, a new metric, <code>wrtc_system_errors&amp;#10100; type="failedice" &amp;#10101;</code>, is added for ICE failures.
 }}
 {{Issue

@@ Line 3: / Line 3: @@
 |JQL=labels=WebRTCRN10000690000
 |DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1, 8b480b3c-2733-433a-9166-eab2c2d0663a
-|ReleaseDate=2023-05-12
+|ReleaseDate=2023-05-15
-|PrivateEditionReleaseDate=2023-05-12
+|PrivateEditionReleaseDate=2023-05-15
-|Highlight=* New traces for ICE failures.
+|Highlight=*New traces for ICE failures.
-* Resolved issues.
+*Resolved issues.
 }}
 {{Issue
@@ Line 33: / Line 33: @@
 |LocalContent=The following new traces are added for ICE failures:
-* SYS, ICEFailed, ICE State moved to FAILED, remote candidates are present
+*SYS, ICEFailed, ICE State moved to FAILED, remote candidates are present
-* SYS, ICEFailed, ICE State moved to FAILED, no remote candidates
+*SYS, ICEFailed, ICE State moved to FAILED, no remote candidates
-* SYS, ICEFailed, ICE Failed during established connection
+*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.

← Older revision		Revision as of 10:30, June 19, 2023
Line 45:		Line 45:
	\|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.		\|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.
	}}		}}
		+	{{Issue
		+	\|TicketNumber=WRTCMS-1280
		+	\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
		+	\|LocalContent=Previously, WebRTC Gateway experienced 10ms gaps in jitter calculation. Now, jitter calculation is more reliable. Also, call stats are reported in monitoring messages for calls every 10 seconds.
		+	}}
		+	{{Issue
		+	\|TicketNumber=WRTCMS-1281
		+	\|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
		+	\|LocalContent=Gateway jitter is now also reported as a histogram for the '''wrtc_rtp_gateway_jitter_ms_bucket''' metric.
		+	}}
		+	{{Issue
		+	\|TicketNumber=WRTCMS-1297
		+	\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
		+	\|LocalContent=Now, <code>http-request GET/options</code> to monitoring port shows all current options in plain text format. For example, <code>curl http://localhost:10052/options</code>. Also, at startup, WebRTC Gateway pushes a monitoring message with type <code>SYS</code> and method <code>Options</code>, and a message that contains the complete set of options in JSON format.
		+	}}
		+	{{Issue
		+	\|TicketNumber=WRTCMS-1298
		+	\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
		+	\|LocalContent=In case of connectivity issues with GAuth, Environment or Config services of GWS, WebRTC Gateway now pushes monitoring messages with type <code>SYS</code> and methods <code>Auth Service Failed</code>, <code>Env Service Failed</code>, <code>Cfg Service Failed</code>, and messages that contains the info about the failure, which can help understand the reason for the connectivity issue without having to download logs.
		+	}}
		+	{{Issue
		+	\|TicketNumber=WRTCMS-1302
		+	}}
		+	{{Issue}}

← Older revision		Revision as of 16:00, May 8, 2023
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{ type="failedice" }
		+	\|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{ 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~~}}	+	* 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{ type="failedice" }</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.
		+	}}