COMMUNICATION NODE AND METHOD FOR HANDLING SIP COMMUNICATION

• US 20090238168A1
• Filed: 03/18/2008
• Published: 09/24/2009
• Est. Priority Date: 03/18/2008
• Status: Abandoned Application

• Current Assignee: Paraxip Technologies (Sangoma Technologies Corporation)
• Original Assignee: Paraxip Technologies (Sangoma Technologies Corporation)
• Inventors: Lavoie, Dominic, Goulet, Stephan, Trottier, Sebastien
• Application Number:
  US12/050,323
• Publication Number:
  US 20090238168A1
• Time in Patent Office: Days
• US Class Current: 370/352
• CPC Class Codes: H04L 65/1046 Call controllers; Call servers
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]

Abstract

The present invention relates to a communication node and method for connecting and maintaining a call between a caller device and a callee device. The communication node comprises a session controller module and a plurality of internal SIP UA (Session Initiation Protocol User Agent) servers. The session controller module is adapted to remain in communication with the caller device and the callee device through a whole duration of the call. The plurality of internal SIP UA servers is adapted to communicate with the session controller module by open protocol.

Claims

1. A communication node for connecting and maintaining a call session between a caller device and a callee device, the communication node comprising:

a session controller module adapted to interpose itself between the caller device and callee device through a whole duration of the call session there between; and

a plurality of internal Session Initiation Protocol User Agent (SIP UA) servers, each of the internal SIP UA servers being adapted to communicate with the session controller module by open protocol for providing at least one service during the call session.

2. The communication node of claim 1 wherein the at least one service is for resolving media compatibility issues between the caller device and the callee device.

3. The communication node of claim 2 wherein the at least one service is for resolving signaling conflict issues between the caller device and the callee device.

4. The communication node of claim 1, wherein the session controller module is adapted to dispatch a task to at least one of the plurality of internal SIP UA servers.

5. The communication node of claim 4, wherein the communication node further comprises a registry storing information and status for the plurality of internal SIP UA servers, and wherein the session controller module is adapted to access the registry.

6. The communication node of claim 1, wherein at least one of the plurality of internal SIP UA servers is adapted to communicate with at least another one of the plurality of internal SIP UA servers by open protocol.

7. The communication node of claim 1, wherein the session controller is further adapted for withdrawing the communication node from a media path during the call session.

8. The communication node of claim 1, wherein some of the plurality of internal SIP UA servers are grouped as a class.

9. The communication node of claim 1, wherein the at least one service is for resolving RFC3261 SIP standard compatibility issues between the caller device and the callee device.

10. A communication node for handling SIP communication, the communication node comprising:

a session controller module capable of supporting SIP (Session Initiation Protocol) communication, the session controller module being adapted to remain in communication with a caller device and a callee device through a whole duration of a call session there between, the session controller module further acting as an internal B2BUA (Back to Back User Agent);

a plurality of internal SIP UA (User Agents) servers for providing services to the caller device and the callee device, the plurality of internal SIP UA servers communicating with the session controller module through open protocol.

11. The communication node of claim 10 wherein the at least one service is for resolving signaling conflict issues between the caller device and the callee device.

12. The communication node of claim 11 wherein one of the at least one service is for resolving media compatibility issues between the caller device and the callee device.

13. The communication node of claim 10, wherein the session controller is adapted for withdrawing the communication node from a media path during the call session.

14. A method for handling SIP communication between a session controller module and at least one internal SIP UA (User Agent) server comprising:

delegating at least one task to at least one internal SIP UA server by the session controller module; and

maintaining communication by the session controller module with a caller and a callee through a whole duration of a call session.

15. The method for handling SIP communication of claim 14 further comprising:

updating a registry for storing an identity of the at least one internal SIP UA server that is available and adapted to execute the at least one task; and

accessing the registry for identifying the at least one internal SIP UA server that is available and adapted to execute the at least one task.

16. The method for handling SIP communication of claim 15 further comprising:

establishing communication between at least two internal SIP UA servers for executing the at least one task.

17. The method for handling SIP communication of claim 16 further comprising:

withdrawing the communication node from a media path during the call session.