Snap-in invocation for call reconstruction
During a Session Initiation Protocol dialog setup, a media gateway or container executes or initiates two or more applications that provide features during a conference call. The applications are applied to messages or data in the conference call based on a sequence order established during the setup of the conference call. The sequence order and the application identities are stored in a shared database. When a failure occurs during the conference call, the applications are reestablished in the reconstructed or reestablished conference call. The application reconstruction includes reinitiating the applications with the same sequence as previously established before the failure. As such, the user has the same features applied in the same way before and after the failure, which improves the systems performance and expected operation.
1. A method of managing a Session Initiation Protocol (SIP) dialog between two or more network elements, the method comprising:
determining that a signaling-disrupting event has occurred during a SIP conference call;
reestablishing the SIP dialog between the network element and a conference controller; and
re-initiating two or more applications, wherein the two or more applications provide features for the SIP conference call, wherein the two or more applications are associated with a sequence order, and wherein the two or more applications are re-initiated such that the sequence order is maintained.
2. The method according to claim 1 , wherein re-initiating two or more applications controller includes: receiving at the network element, a SIP message including a P-HA-ReconstructionSnapins header, wherein the P-HA-ReconstructionSnapins header includes a list of applications included in the SIP conference call and a sequence order for the applications.
3. The method according to claim 2 , wherein a first application receives the SIP message.
4. The method according to claim 3 , in response to receiving the SIP message, the first application becoming a high availability controller (HAC).
5. The method according to claim 4 , further comprising the HAC generating a list of other applications to be re-initiated.
6. The method according to claim 5 , further comprising the HAC sending two or more SIP messages to two or more applications preceding the HAC in the sequence order, wherein the two or more messages are sent to the two or more applications in reverse of the sequence order.
7. The method according to claim 5 , further comprising the HAC sending two or more SIP messages to two or more applications following the HAC in the sequence order, wherein the two or more messages are sent to the two or more applications same as the sequence order.
8. The method according to claim 1 , wherein the list of applications and the sequence order are saved in a shared data during creation of the SIP conference call.
9. The method according to claim 8 , further comprising the SIP conference controller retrieving the list of applications and the sequence order from the shared data during SIP conference call reconstruction.
10. The method according to claim 1 , further comprising creating a container associated with at least one of the network elements, wherein two or more applications are associated with the container in the SIP conference call.
11. A system comprising:
a conference controller including:
a processor; and
memory including one or more instructions that when executed by the processor, enable the conference controller to:
determine that a signaling-disrupting event has occurred during a Session Initiation Protocol (SIP) conference call;
reestablish a SIP dialog between a network element and the conference controller; and
re-initiate two or more applications providing features for the SIP conference call, wherein the two or more applications are associated with a sequence order, and wherein the two or more applications are re-initiated such that the sequence order is maintained.
12. The system of claim 11 , wherein the network element receives a SIP message including a P-HA-ReconstructionSnapins header, wherein the P-HA-ReconstructionSnapins header includes a list of applications included in the SIP conference call and a sequence order for the applications.
13. The system of claim 12 , wherein a first application receives the SIP message and, in response to receiving the SIP message, becomes a high availability controller (HAC), and wherein the HAC generates a list of other applications to be re-initiated.
14. The system according to claim 13 , wherein the HAC sends two or more SIP messages to two or more applications preceding the HAC in the sequence order, wherein the two or more messages are sent to the two or more applications in reverse of the sequence order, and wherein the HAC sends two or more SIP messages to two or more applications following the HAC in the sequence order, wherein the two or more messages are sent to the two or more applications same as the sequence order.
15. The system according to claim 11 , wherein the list of applications and the sequence order are saved in a shared data during creation of the SIP conference call, and wherein the SIP conference controller retrieves the list of applications and the sequence order from the shared data during SIP conference call reconstruction.
16. A computer readable medium having stored thereon instructions that cause a processor to execute a method, the instructions comprising:
an instruction to establish a Session Initiation Protocol (SIP) dialog between a SIP user agent and a conference controller;
an instruction to determine that a signaling-disrupting event has occurred during a SIP conference call having the established SIP dialog;
an instruction to reestablish the SIP dialog between the SIP user agent and the conference controller; and
an instruction to re-initiate two or more applications providing features for the SIP conference call, wherein the two or more applications are associated with a sequence order, and wherein the two or more applications are re-initiated such that the sequence order is maintained.
17. The computer readable medium of claim 16 , wherein SIP user agent receives a SIP message including a P-HA-ReconstructionSnapins header, wherein the P-HA-ReconstructionSnapins header includes a list of applications included in the SIP conference call and a sequence order for the applications.
18. The computer readable medium of claim 17 , wherein a first application receives the SIP message and, in response to receiving the SIP message, becomes a high availability controller (HAC), and wherein the HAC generates a list of other applications to be re-initiated.
19. The computer readable medium according to claim 18 , wherein the HAC sends two or more SIP messages to two or more applications preceding the HAC in the sequence order, wherein the two or more messages are sent to the two or more applications in reverse of the sequence order, and wherein the HAC sends two or more SIP messages to two or more applications following the HAC in the sequence order, wherein the two or more messages are sent to the two or more applications same as the sequence order.
20. The computer readable medium according to claim 16 , wherein the list of applications and the sequence order are saved in a shared data during creation of the SIP conference call, and wherein the SIP conference controller retrieves the list of applications and the sequence order from the shared data during SIP conference call reconstruction.