System and method for distributed multi-party call control

• US 20020089938A1
• Filed: 09/24/2001
• Published: 07/11/2002
• Est. Priority Date: 09/22/2000
• Status: Active Grant

• Current Assignee: Genband US LLC (Ribbon Communications, Inc.)
• Original Assignee: Santera Systems LLC
• Inventors: Perry, Matthew C.
• Granted Patent: US 7,110,368 B2
• Time in Patent Office: Days
• US Class Current: 370/260
• 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/1101 Session protocols
• CPC Class Codes: H04M 2203/5018 Initiating a conference during a two-party conversation, i.e. three-party-service or three-way-call computer conference organisation arrangements H04L12/1818
• CPC Class Codes: H04M 3/428 Arrangements for placing incoming calls on hold
• CPC Class Codes: H04M 3/56 Arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities video conference systems H04N7/15
• CPC Class Codes: H04M 3/562 where the conference facilities are distributed
• CPC Class Codes: H04M 3/567 Multimedia conference systems
• CPC Class Codes: H04M 7/1225 Details of core network interconnection arrangements

Abstract

A system and method of distributed multi-party call control are provided. The method includes the steps of establishing a first leg of a multi-party call, adding a second leg of the multi-party call, associating the second leg with the first leg of the multi-party call, determining which of the first leg or the second leg to be the controlling or controlled legs of the multi-party call, and requesting a voice path to the controlled leg by the controlling leg to establish the multi-party call.

Claims

1. A method of inter-call manager messaging protocol, comprising:

establishing a first leg of a multi-party call;

adding a second leg of the multi-party call;

associating the second leg with the first leg of the multi-party call;

determining which of the first leg or the second leg to be the controlling or controlled legs of the multi-party call; and

requesting a voice path to the controlled leg by the controlling leg to establish the multi-party call.

2. The method, as set forth in claim 1, further comprising informing the controlled leg, by the controlling leg, that it is detaching from the multi-party call.

3. The method, as set forth in claim 1, further comprising informing the controlling leg, by the controlled leg, that it is releasing the multi-party call.

4. The method, as set forth in claim 1, further comprising:

sending, by the second leg, a request to attach the second leg to the first leg; and

determining the second leg as the controlling leg.

5. The method, as set forth in claim 1, further comprising:

sending, by the first leg, a request to initiate the second leg; and

determining the second leg as the controlling leg.

6. The method, as set forth in claim 1, wherein requesting the voice path comprises requesting the controlled leg to apply an alert tone to a shared channel between the first and second legs.

7. The method, as set forth in claim 1, wherein requesting the voice path comprises requesting the controlled leg to move a shared channel between the first and second legs to a connection context of the controlling leg.

8. The method, as set forth in claim 7, wherein requesting the voice path comprises requesting the controlled leg to move a shared channel between the first and second legs back to its own context.

9. The method, as set forth in claim 1, wherein requesting the voice path comprises requesting, by the controlling leg, the controlled leg to add a channel into a connection with a shared channel between the first leg and the second leg.

10. A method of setting up a multi-party call, comprising:

establishing a two-party call between an originator and a terminator, the two-party call forming a first leg of a multi-party call;

creating a second leg of the multi-party call involving the originator or terminator of the two-party call and a new terminator or a new originator of the second leg;

determining which of the first leg or the second leg to be the controlling or controlled legs of the multi-party call; and

requesting a voice path to the controlled leg by the controlling leg to establish the multi-party call.

11. The method, as set forth in claim 10, further comprising informing the controlled leg, by the controlling leg, that it is detaching from the multi-party call.

12. The method, as set forth in claim 10, further comprising informing the controlling leg, by the controlled leg, that it is releasing the multi-party call.

13. The method, as set forth in claim 10, further comprising:

sending, by the second leg, a request to attach the second leg to the first leg; and

determining the second leg as the controlling leg.

14. The method, as set forth in claim 10, further comprising:

sending, by the first leg, a request to initiate the second leg; and

determining the second leg as the controlling leg.

15. The method, as set forth in claim 10, wherein requesting the voice path comprises requesting the controlled leg to apply an alert tone to a shared channel between the first and second legs.

16. The method, as set forth in claim 10, wherein requesting the voice path comprises requesting the controlled leg to move a shared channel between the first and second legs to a connection context of the controlling leg.

17. The method, as set forth in claim 16, wherein requesting the voice path comprises requesting the controlled leg to move a shared channel between the first and second legs back to its own context.

18. The method, as set forth in claim 10, wherein requesting the voice path comprises requesting, by the controlling leg, the controlled leg to add a channel into a connection with a shared channel between the first leg and the second leg.

19. The method, as set forth in claim 10, further comprising:

designating the terminator of the second call leg as the controller of the multi-party call; and

disconnecting by the controller results in a ring-back to the controller to bring the controller back into the multi-party call.

20. The method, as set forth in claim 10, further comprising:

designating the originator of the second call leg as the controller of the multi-party call; and

disconnecting by the controller results in a two-party call between the terminator of the second call leg and the remaining party of the original two-party call.

21. A distributed call manager architecture, comprising:

a first call manager residing on a first processor and processing an original leg of the multi-party call between an originator and a terminator;

a second call manager residing on a second processor and processing a new leg of the multi-party call, and sending to the first call manager a request to attach to the original leg of the multi-party call, the second call manager further sending to the first call manager a request to play an alert tone to a new terminator of the new leg of the multi-party call, the second call manager further sending to the first call manager a request to make a voice path from the new leg to the original leg of the multi-party call.

22. A distributed call manager architecture, comprising:

a first call manager residing on a first processor and processing an original leg of the multi-party call between an originator and a terminator, the first call manager requesting an initiation of a new leg of the multi-party call; and

a second call manager residing on a second processor and processing the new leg of the multi-party call, and sending to the first call manager a request to make a voice path from the new leg to the original leg of the multi-party call to a new terminator.