APPLICATION OF ENTERPRISE POLICIES TO WEB REAL-TIME COMMUNICATIONS (WebRTC) INTERACTIVE SESSIONS USING AN ENTERPRISE SESSION INITIATION PROTOCOL (SIP) ENGINE, AND RELATED METHODS, SYSTEMS, AND COMPUTER-READABLE MEDIA

• US 20150304359A1
• Filed: 04/17/2014
• Published: 10/22/2015
• Est. Priority Date: 04/17/2014
• Status: Active Grant

• Current Assignee: Avaya Incorporated
• Original Assignee: Avaya Incorporated
• Inventors: Balasaygun, Mehmet, Ezell, Joel, Yoakum, John H.
• Granted Patent: US 9,749,363 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 65/1045 Proxies, e.g. for session initiation protocol [SIP]
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/1108 Web based protocols, e.g. webRTC

Abstract

Application of enterprise policies to Web Real-Time Communications (WebRTC) interactive sessions using an enterprise Session Initiation Protocol (SIP) engine, and related methods, systems, and computer-readable media are disclosed. In one embodiment, a method comprises receiving, by session token converter of enterprise device, an incoming WebRTC session description token. The method comprises generating, by session token converter, outgoing SIP request message. The method comprises sending, by session token converter, outgoing SIP request message to enterprise SIP engine and applying, by enterprise SIP engine, enterprise policies based on outgoing SIP request message. The method comprises, responsive to applying enterprise policies, sending incoming SIP request message to enterprise device. The method comprises converting, by session token converter, incoming SIP request message into outgoing WebRTC session description token, and sending outgoing WebRTC session description token to a target device.

Claims

1. A method for applying enterprise policies to Web Real-Time Communications (WebRTC) interactive sessions using an enterprise Session Initiation Protocol (SIP) engine, comprising:

receiving, by a session token converter of an enterprise device within an enterprise network, an incoming WebRTC session description token;

generating, by the session token converter, an outgoing SIP request message, wherein the outgoing SIP request message comprises;

the incoming WebRTC session description token;

a return destination of the enterprise device; and

an indicator that the outgoing SIP request message originated from an enterprise user;

sending, by the session token converter, the outgoing SIP request message to an enterprise SIP engine;

applying, by the enterprise SIP engine, one or more enterprise policies based on the outgoing SIP request message;

responsive to applying the one or more enterprise policies, sending an incoming SIP request message to the enterprise device;

converting, by the session token converter, the incoming SIP request message into an outgoing WebRTC session description token; and

sending the outgoing WebRTC session description token to a target device.

2. The method of claim 1, wherein applying, by the enterprise SIP engine, the one or more enterprise policies comprises:

sending, by the enterprise SIP engine, the incoming WebRTC session description token to a media server;

generating, by the media server, a media WebRTC session description token;

sending the media WebRTC session description token to the enterprise SIP engine; and

including, by the enterprise SIP engine, the media WebRTC session description token in the incoming SIP request message.

3. The method of claim 1, wherein:

the enterprise device comprises an enterprise WebRTC client initiating a WebRTC interactive flow;

the outgoing WebRTC session description token comprises a WebRTC offer of a WebRTC offer/answer exchange; and

the target device comprises an external device.

4. The method of claim 1, wherein:

the enterprise device comprises an enterprise WebRTC client receiving a request to initiate a WebRTC interactive flow;

the outgoing WebRTC session description token comprises a WebRTC offer of a WebRTC offer/answer exchange; and

the target device comprises the enterprise device.

5. The method of claim 1, wherein the one or more enterprise policies comprises origination policies, termination policies, or a combination thereof, of the enterprise SIP engine.

6. The method of claim 1, further comprising, responsive to applying the one or more enterprise policies, sending a SIP error code to the enterprise device, wherein the SIP error code indicates a rejection of the outgoing SIP request message by the enterprise SIP engine.

7. The method of claim 6, further comprising, responsive to the enterprise device receiving the SIP error code, ending, by the session token converter, an attempted WebRTC interactive session.

8. The method of claim 1, further comprising:

receiving, by the session token converter, an incoming WebRTC session description response token;

generating, by the session token converter, an outgoing SIP response message, wherein the outgoing SIP response message comprises;

the incoming WebRTC session description response token; and

an acknowledgment that a WebRTC interactive session sought by the incoming WebRTC session description response token is accepted;

sending, by the session token converter, the outgoing SIP response message to the enterprise SIP engine;

completing, by the enterprise SIP engine, establishment of an interactive session;

sending, by the enterprise SIP engine, an incoming SIP response message to the enterprise device; and

converting, by the session token converter, the incoming SIP response message into an outgoing WebRTC session description response token.

9. The method of claim 8, wherein completing, by the enterprise SIP engine, establishment of the interactive session comprises:

sending, by the enterprise SIP engine, the incoming WebRTC session description response token to a media server;

completing, by the media server, establishment of one or more media capabilities of the interactive session;

sending a media WebRTC session description response token to the enterprise SIP engine; and

including, by the enterprise SIP engine, the media WebRTC session description response token in the incoming SIP response message.

10. A system for applying enterprise policies to Web Real-Time Communications (WebRTC) interactive sessions using an enterprise Session Initiation Protocol (SIP) engine, comprising:

at least one communications interface; and

an enterprise device within an enterprise network associated with the at least one communications interface and comprising a session token converter, the session token converter configured to;

receive an incoming WebRTC session description token;

generate an outgoing SIP request message, wherein the outgoing SIP request message comprises;

the incoming WebRTC session description token;

a return destination of the enterprise device; and

an indicator that the outgoing SIP request message originated from an enterprise user; and

send the outgoing SIP request message to an enterprise SIP engine;

the enterprise SIP engine configured to;

apply one or more enterprise policies based on the outgoing SIP request message; and

responsive to applying the one or more enterprise policies, send an incoming SIP request message to the enterprise device; and

the session token converter of the enterprise device further configured to;

convert the incoming SIP request message into an outgoing WebRTC session description token; and

send the outgoing WebRTC session description token to a target device.

11. The system of claim 10, wherein the one or more enterprise policies comprises origination policies, termination policies, or a combination thereof, of the enterprise SIP engine.

12. The system of claim 10, further comprising:

a media server;

the enterprise SIP engine configured to apply the one or more enterprise policies based on the outgoing SIP request message by;

sending the incoming WebRTC session description token to the media server; and

including a media WebRTC session description token in the incoming SIP request message; and

the media server configured to;

generate the media WebRTC session description token; and

send the media WebRTC session description token to the enterprise SIP engine.

13. The system of claim 10, further comprising:

the enterprise SIP engine, responsive to applying the one or more enterprise policies, further configured to send a SIP error code to the enterprise device, wherein the SIP error code indicates a rejection of the outgoing SIP request message by the enterprise SIP engine.

14. The system of claim 13, further comprising:

the session token converter, responsive to the enterprise device receiving the SIP error code, configured to end an attempted WebRTC interactive session.

15. The system of claim 10, further comprising:

the session token converter, further configured to;

receive an incoming WebRTC session description response token; and

generate an outgoing SIP response message, wherein the outgoing SIP response message comprises;

the incoming WebRTC session description response token; and

an acknowledgment that a WebRTC interactive session sought by the incoming WebRTC session description response token is accepted; and

send the outgoing SIP response message to the enterprise SIP engine;

the enterprise SIP engine further configured to;

complete establishment of an interactive session; and

send an incoming SIP response message to the enterprise device; and

the session token converter further configured to convert the incoming SIP response message into an outgoing WebRTC session description response token.

16. The system of claim 15, further comprising:

a media server;

the enterprise SIP engine further configured to complete establishment of the interactive session by;

sending the incoming WebRTC session description response token to the media server; and

including a media WebRTC session description response token in the incoming SIP response message; and

the media server further configured to;

complete establishment of one or more media capabilities of the interactive session; and

send a media WebRTC session description response token to the enterprise SIP engine.

17. A non-transitory computer-readable medium having stored thereon computer-executable instructions to cause a processor to implement a method, comprising:

receiving, by a session token converter of an enterprise device within an enterprise network, an incoming Web Real-Time Communications (WebRTC) session description token;

generating, by the session token converter, an outgoing Session Initiation Protocol (SIP) request message, wherein the outgoing SIP request message comprises;

the incoming WebRTC session description token;

a return destination of the enterprise device; and

an indicator that the outgoing SIP request message originated from an enterprise user;

sending, by the session token converter, the outgoing SIP request message to an enterprise SIP engine;

applying, by the enterprise SIP engine, one or more enterprise policies based on the outgoing SIP request message;

responsive to applying the one or more enterprise policies, sending an incoming SIP request message to the enterprise device;

converting, by the session token converter, the incoming SIP request message into an outgoing WebRTC session description token; and

sending the outgoing WebRTC session description token to a target device.

18. The non-transitory computer-readable medium of claim 17 having stored thereon the computer-executable instructions to cause the processor to implement the method, wherein applying, by the enterprise SIP engine, the one or more enterprise policies comprises:

sending, by the enterprise SIP engine, the incoming WebRTC session description token to a media server;

generating, by the media server, a media WebRTC session description token;

sending the media WebRTC session description token to the enterprise SIP engine; and

including, by the enterprise SIP engine, the media WebRTC session description token in the incoming SIP request message.

19. The non-transitory computer-readable medium of claim 17 having stored thereon the computer-executable instructions to cause the processor to implement the method, further comprising:

receiving, by the session token converter, an incoming WebRTC session description response token;

generating, by the session token converter, an outgoing SIP response message, wherein the outgoing SIP response message comprises;

the incoming WebRTC session description response token; and

an acknowledgment that a WebRTC interactive session sought by the incoming WebRTC session description response token is accepted;

sending, by the session token converter, the outgoing SIP response message to the enterprise SIP engine;

completing, by the enterprise SIP engine, establishment of an interactive session;

sending, by the enterprise SIP engine, an incoming SIP response message to the enterprise device; and

converting, by the session token converter, the incoming SIP response message into an outgoing WebRTC session description response token.

20. The non-transitory computer-readable medium of claim 19 having stored thereon the computer-executable instructions to cause the processor to implement the method, wherein completing, by the enterprise SIP engine, establishment of the interactive session comprises:

sending, by the enterprise SIP engine, the incoming WebRTC session description response token to a media server;

completing, by the media server, establishment of one or more media capabilities of the interactive session;

sending a media WebRTC session description response token to the enterprise SIP engine; and

including, by the enterprise SIP engine, the media WebRTC session description response token in the incoming SIP response message.