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 system comprising:
a media gateway including:
a processor; and
a memory including one or more instructions that when executed by the processor, enable the media gateway 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 media gateway; 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.
2. The system of claim 1 , wherein the network element receives a SIP message including a P-HA-ReconstructionSnapins header, and wherein the P-HA-ReconstructionSnapins header includes a list of the two or more applications included in the SIP conference call and the sequence order for the two or more applications.
3. The system of claim 2 , 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.
4. The system according to claim 3 , wherein the HAC sends a SIP message to each application preceding the HAC in the sequence order, wherein each SIP message is sent to each application of the two or more applications preceding the HAC in reverse of the sequence order, wherein the HAC sends a SIP message to each application of the two or more applications following the HAC in the sequence order, and wherein each SIP message is sent to each application of the two or more applications following the HAC in a same order as the sequence order.
5. The system according to claim 1 , wherein a list of the two or more applications and the sequence order are saved in a shared data during creation of the SIP conference call, and wherein the media gateway retrieves the list of the two or more applications and the sequence order from the shared data during SIP conference call reconstruction.
6. A machine readable memory 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 media gateway;
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 media gateway; 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.
7. The machine readable memory of claim 6 , wherein the SIP user agent receives a SIP message including a P-HA-ReconstructionSnapins header, wherein the P-HA-ReconstructionSnapins header includes a list of the two or more applications included in the SIP conference call and the sequence order for the two or more applications.
8. The machine readable memory of claim 7 , 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.
9. The machine readable memory according to claim 8 , wherein the HAC sends a SIP message to each application of the two or more applications preceding the HAC in the sequence order, wherein each SIP message is sent to each application of the two or more applications preceding the HAC in reverse of the sequence order, wherein the HAC sends a SIP message to each application of the two or more applications following the HAC in the sequence order, and wherein each SIP message is sent to each application of the two or more applications following the HAC in a same order as the sequence order.
10. The machine readable memory according to claim 6 , wherein a list of two or more applications and the sequence order are saved in a shared data during creation of the SIP conference call, and wherein the media gateway retrieves the list of the two or more applications and the sequence order from the shared data during SIP conference call reconstruction.
11. A method of managing a Session Initiation Protocol (SIP) dialog between a media gateway and one 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 one or more network elements and the media gateway; 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.
12. The method according to claim 11 , wherein re-initiating the two or more applications includes: receiving at the one or more network elements, a SIP message including a P-HA-ReconstructionSnapins header, wherein the P-HA-ReconstructionSnapins header includes a list of the two or more applications included in the SIP conference call and sequence order for the two or more applications.
13. The method according to claim 12 , wherein a first application receives the SIP message.
14. The method according to claim 13 , further comprising in response to receiving the SIP message, the first application becoming a high availability controller (HAC).
15. The method according to claim 14 , further comprising the HAC generating a list of other applications to be re-initiated.
16. The method according to claim 15 , further comprising the HAC sending a SIP message to each application of the two or more applications preceding the HAC in the sequence order, wherein each SIP message is sent to each application of the two or more applications proceeding the HAC in reverse of the sequence order.
17. The method according to claim 15 , further comprising the HAC sending a SIP message to each application of the two or more applications following the HAC in the sequence order, wherein each SIP message is sent to each application of the two or more applications following the HAC in a same order as the sequence order.
18. The method according to claim 11 , wherein a list of the two or more applications and the sequence order are saved in a shared data during creation of the SIP conference call.
19. The method according to claim 18 , further comprising the media gateway retrieving the list of the two or more applications and the sequence order from the shared data during SIP conference call reconstruction.
20. The method according to claim 11 , further comprising creating a container associated with at least one of the one or more network elements, wherein the two or more applications are associated with the container in the SIP conference call.