Session reconstruction using proactive redirect
A method, server, and communication system are described that, among other things, enable a server in a server cluster to assume control of any “early” Session Initiation Protocol (SIP) dialogs previously handled by another server in the server cluster when that server fails or otherwise becomes unable to continue handling a communication session. The replacement server in the server cluster is able to generate one or more messages that include an identification of the dialog identifiers used by the now failed server as well as new dialog identifiers to replace the dialog identifiers used by the now failed server.
1. A method, comprising:
determining that a first server in a server cluster has failed and at least one communication session was under control of the first server when the first server failed;
in response to determining that the first server has failed, initiating a session reconstruction process to enable a replacement server from the server cluster to take over the communication session for the first server, wherein the session reconstruction process comprises:
generating one or more session reconstruction messages, at least one of which includes session reconstruction data therein; and
transmitting the one or more session reconstruction messages to all communication components still involved in the at least one communication session to set up a new communication session that correlates to the at least one communication session.
2. The method of claim 1 , wherein the one or more session reconstruction messages comprise a Session Initiation Protocol (SIP) INVITE with Replaces message.
3. The method of claim 2 , wherein the SIP INVITE with Replaces message comprises an identifier of a first dialog ID used in the at least one communication session by the first server as well as a new dialog ID to replace the first dialog ID.
4. The method of claim 3 , wherein the one or more session reconstruction messages further include at least one Session Description Protocol (SDP) offer to replace an SDP used in the at least one communication session before the first server in the server cluster failed.
5. The method of claim 3 , wherein the new dialog ID is included in a Replaces header of the SIP INVITE with Replaces message.
6. The method of claim 1 , wherein the one or more session reconstruction messages comprise a Session Initiation Protocol (SIP) 300 or 301 redirect response message.
7. The method of claim 6 , wherein the SIP 300 or 301 redirect response message uses an original dialog identifier assigned to the communication session being reconstructed by the replacement server so that a communication component views the SIP 300 or 301 redirect response message as an in-dialog response to a SIP INVITE message and wherein the SIP 300 or 301 redirect response message comprises a Contact Universal Resource Identifier (URI) that includes an address of the replacement server as well as a correlation identifier that allows the replacement server to associate a new SIP INVITE message with the communication session being reconstructed by the replacement server.
8. The method of claim 1 , wherein the session reconstruction process is initiated by the replacement server.
9. The method of claim 1 , wherein the session reconstruction process is initiated by a snap-in involved in the at least one communication session.
10. The method of claim 1 , wherein the at least one communication session included at least one media server and wherein the session reconstruction process further comprises generating at least one of a Session Initiation Protocol (SIP) INVITE message and a SIP REFER message that includes a dummy Session Description Protocol (SDP) offer and transmitting the at least one SIP INVITE message to the at least one media server.
11. A communication system, comprising:
a first server, wherein the first server is in a server cluster including the first server and a second server, the first server being configured to receive an indication that the second server has failed or otherwise become unable to continue servicing at least one call that was previously being serviced by the second server prior to the failure or unavailability of the second server and in response thereto perform a session reconstruction process that includes:
generating a message that contains information enabling the first server to impersonate the second server; and
transmitting the message to a User Agent Client (UAC) involved in the at least one call to initiate, by the UAC, a new session, wherein the information contained in the message enables the new session to have reconstructed session state from the at least one call that was previously being serviced by the second server prior to the failure of the second server.
12. The communication system of claim 11 , wherein the session reconstruction process is initiated by the first server.
13. The communication system of claim 11 , wherein the session reconstruction process is initiated by a snap-in.
14. The communication system of claim 11 , wherein the message comprises a Session Initiation Protocol (SIP) INVITE with Replaces message.
15. The communication system of claim 14 , wherein the SIP INVITE with Replaces message comprises an identifier of a first dialog ID used in the at least one call as well as a new dialog ID to replace the first dialog ID.
16. The communication system of claim 15 , wherein the message comprises at least one Session Description Protocol (SDP) offer to replace an SDP used in the at least one call.
17. The communication system of claim 15 , wherein the new dialog ID is included in a Replaces header of the SIP INVITE with Replaces message.
18. The communication system of claim 11 , wherein the at least one call included at least one media server and wherein the session reconstruction process further comprises generating at least one of a Session Initiation Protocol (SIP) INVITE message and a SIP REFER message that includes a dummy Session Description Protocol (SDP) offer and transmitting the at least one SIP INVITE message to the at least one media server.
19. The communication system of claim 11 , wherein the message comprises a Session Initiation Protocol (SIP) 300 or 301 redirect response message.
20. A non-transitory computer-readable medium comprising processor-executable instructions, the instructions comprising:
instructions configured to receive an indication that a first server in a server cluster has failed or otherwise become unable to continue servicing at least one call that was previously being serviced by the first server prior to the failure of the first server;
instructions configured to, in response to receiving the indication, cause a second server in the server cluster to generate a message that contains information enabling the second server to impersonate the first server; and
instructions configured to cause the message to be transmitted to a User Agent Client (UAC) to initiate, by the UAC, a new session, wherein the information contained in the message enables the new session to have reconstructed session state from the at least one call that was previously being serviced by the first server prior to the failure of the first server.
21. The computer-readable medium of claim 20 , wherein the message comprises a Session Initiation Protocol (SIP) INVITE with Replaces message.
22. The computer-readable medium of claim 21 , wherein the SIP INVITE with Replaces message comprises an identifier of a first dialog ID used in the at least one call as well as a new dialog ID to replace the first dialog ID.
23. The computer-readable medium of claim 20 , wherein the at least one call included at least one media server and wherein the instruction further include instructions configured to generate at least one of a SIP INVITE message and a SIP REFER message that includes a dummy Session Description Protocol (SDP) offer.