TELECOMMUNICATION SYSTEM AND METHOD FOR TRAVERSING AN APPLICATION LAYER GATEWAY FIREWALL DURING THE ESTABLISHMENT OF AN RTC COMMUNICATION CONNECTION BETWEEN AN RTC CLIENT AND AN RTC SERVER
A telecommunications assembly and a method for traversing an application layer gateway firewall during the establishment of an RTC communication connection between an RTC client and an RTC server using a proprietary RTC signalling protocol, wherein the firewall has no specific knowledge of the proprietary RTC signalling protocol. The RTC client and the RTC server can negotiate during the establishment of the RTC communication connection which of the ports of the firewall are required for the data packets to be exchanged via the RTC communication connection, wherein they use at least one standardised message element as a component of the proprietary RTC signalling protocol, with which information relating to the ports to be used can be found. by the firewall.
1 - 8 . (canceled)
9 . A computer-implemented method, comprising:
negotiating a port for media data packet exchange using a standardized message element of a proprietary Real Time Communication (RTC) protocol that a firewall has no specific knowledge about, wherein the standardized message element includes port information; and
upon establishing an RTC connection, enabling the firewall to dynamically open and close the port for media data packet exchange using the standardized message element.
10 . The computer-implemented method of claim 9 , wherein enabling the firewall comprises enabling the firewall to dynamically open and close the port with no specific knowledge of the proprietary RTC protocol.
11 . The computer-implemented method of claim 9 , further comprising:
establishing a Hypertext Transfer Protocol (HTTP) connection prior to negotiating the port for media data packet exchange; and
upgrading the HTTP connection to a WebSocket connection.
12 . The computer-implemented method of claim 11 , wherein negotiating the port for media data packet exchange is responsive to upgrading the HTTP connection to the WebSocket connection.
13 . The computer-implemented method of claim 9 , wherein negotiating the port for media data packet exchange comprises exchanging a signal protocol variation.
14 . The computer-implemented method of claim 13 , wherein exchanging the signal protocol variation occurs through a defined field in a header of an add-on.
15 . The computer-implemented method of claim 9 , wherein the media data packets are for audio data or video data.
16 . A non-transitory, computer-readable medium storing instructions that, when executed by a processor, cause:
negotiating a port for media data packet exchange using a standardized message element of a proprietary Real Time Communication (RTC) protocol that a firewall has no specific knowledge about, wherein the standardized message element includes port information; and
upon establishing an RTC connection, enabling a firewall to dynamically open and close the port for media data packet exchange using the standardized message element.
17 . The non-transitory, computer-readable medium of claim 16 , wherein enabling the firewall comprises enabling the firewall to dynamically open and close the port with no specific knowledge of the proprietary RTC protocol.
18 . The non-transitory, computer-readable medium of claim 16 , storing further instructions that, when executed by the processor, cause:
establishing a Hypertext Transfer Protocol (HTTP) connection prior to negotiating the port for media data packet exchange; and
upgrading the HTTP connection to a WebSocket connection.
19 . The non-transitory, computer-readable medium of claim 18 , wherein negotiating the port for media data packet exchange is responsive to upgrading the HTTP connection to the WebSocket connection.
20 . The non-transitory, computer-readable medium of claim 16 , wherein negotiating the port for media data packet exchange comprises exchanging a signal protocol variation.
21 . The non-transitory, computer-readable medium of claim 20 , wherein exchanging the signal protocol variation occurs through a defined field in a header of an add-on.
22 . The non-transitory, computer-readable medium of claim 16 , wherein the media data packets are for audio data or video data.
23 . A WebRTC server, comprising:
a processor;
a memory storing instructions that, when executed by the processor, cause:
negotiating a port for media data packet exchange using a standardized message element of a proprietary Real Time Communication (RTC) protocol that a firewall has no specific knowledge about, wherein the standardized message element includes port information; and
upon establishing an RTC connection, enabling a firewall to dynamically open and close the port for media data packet exchange using the standardized message element.
24 . The WebRTC server of claim 23 , wherein enabling the firewall comprises enabling the firewall to dynamically open and close the port with no specific knowledge of the proprietary RTC protocol.
25 . The WebRTC server of claim 23 , wherein the memory stores further instructions that, when executed by the processor, cause:
establishing a Hypertext Transfer Protocol (HTTP) connection prior to negotiating the port for media data packet exchange; and
upgrading the HTTP connection to a WebSocket connection.
26 . The WebRTC server of claim 25 , wherein negotiating the port for media data packet exchange is responsive to upgrading the HTTP connection to the WebSocket connection.
27 . The WebRTC server of claim 23 , wherein negotiating the port for media data packet exchange comprises exchanging a signal protocol variation.
28 . The WebRTC server of claim 23 , wherein exchanging the signal protocol variation occurs through a defined field in a header of an add-on.