Reestablishment of session initiation protocol (SIP) dialogs
A communication session is established between a first communication device and a second communication device. The communication session comprises a first dialog between an application server and the first communication device. The first communication device uses a first network address in the first dialog. In response to an event, such as a first network interface failing, a SIP INVITE with replaces header message is received by the application server with a second address of the first communication device. In response to receiving the SIP INVITE with replaces header message from the first communication device with a second address of the first communication device, the first dialog between the application server and the first device is reestablished using the second network address.
1. A method comprising:
establishing, by a processor, a communication session between a first communication device and a second communication device, wherein the communication session comprises a first dialog between an application server and the first communication device and wherein the first communication device uses a first network address in the first dialog;
receiving, by the processor, a SIP INVITE with replaces header message from the first communication device with a second network address of the first communication device; and
in response to receiving the SIP INVITE with replaces header message from the first communication device with the second network address of the first communication device, reestablishing, by the processor, the first dialog between the application server and the first communication device using the second network address.
2. The method of claim 1 , wherein the SIP INVITE with replaces header message further comprises a takeover tag that identifies to the application server that the SIP INVITE with replaces header message is to be handled differently than a normal SIP INVITE with replaces header message, wherein the takeover tag tells the application server that it does not need to reestablish a second dialog between the application server and the second communication device.
3. The method of claim 2 , wherein the communication session also comprises a second dialog between the second communication device and the application server and wherein the application server does not reestablish the second dialog in response to receiving the SIP INVITE with replaces header message with the takeover tag.
4. The method of claim 1 , wherein the communication session also comprises a second dialog between the second communication device and the application server and further comprising:
determining if the SIP INVITE with replaces header message comprises a takeover tag;
determining if there is a media server involved in the communication session;
in response to determining that the media server is not involved in the communication session and the SIP INVITE with replaces header message comprises the takeover tag, sending, to the second communication device, a SIP RE-INVITE message to reestablish the second dialog, wherein the SIP RE-INVITE message contains the second network address and wherein the second network address is used to reestablish a media stream between the first communication device and the second communication device.
5. The method of claim 1 , wherein the SIP INVITE with replaces header message is received in response to a change in signal strength from a first network that uses the first network address to a second network that uses the second network address.
6. The method of claim 1 , wherein the first communication device has a plurality of different network interfaces, wherein the SIP INVITE with replaces header message is received in response to one of the plurality of different network interfaces failing and/or the one of the plurality of different network interfaces being unable to communicate with the application server.
7. The method of claim 1 , wherein the first communication device has a plurality of different network interfaces and wherein the SIP INVITE with replaces header message is received based on a user input to move the communication session from a first one of the plurality of different network interfaces to a second one of the plurality of different network interfaces.
8. The method of claim 1 , wherein the first network address is a first Internet Protocol (IP) address on a first subnet and the second network address is a second IP address on a second subnet.
9. A system comprising:
a communication processor that establishes a communication session between a first communication device and a second communication device, wherein the communication session comprises a first dialog between an application server and the first communication device and wherein the first communication device uses a first network address in the first dialog, and reestablishes the first dialog between the application server and the first communication device using a second network address in response to receiving a SIP INVITE with replaces header message from the first communication device with the second network address of the first communication device; and
an application server that receives the SIP INVITE with replaces header message from the first communication device with the second network address.
10. The system of claim 9 , wherein the SIP INVITE with replaces header message further comprises a takeover tag that identifies to the application server that the SIP INVITE with replaces header message is to be handled differently than a normal SIP INVITE with replaces header message, wherein the takeover tag tells the application server that it does not need to reestablish a second dialog between the application server and the second communication device.
11. The system of claim 10 , wherein the communication session also comprises a second dialog between the second communication device and the application server and wherein the application server does not reestablish the second dialog in response to receiving the SIP INVITE with replaces header message with the takeover tag.
12. The system of claim 9 , wherein the communication session also comprises a second dialog between the second communication device and the application server and wherein:
the application server determines if the SIP INVITE with replaces header message comprises a takeover tag; determines if there is a media server involved in the communication session; and sends, to the second communication device, a SIP RE-INVITE message to reestablish the second dialog in response to determining that the media server is not involved in the communication session and the SIP INVITE with replaces header message comprises the takeover tag, wherein the SIP RE-INVITE message contains the second network address and wherein the second network address is used to reestablish a media stream between the first communication device and the second communication device.
13. The system of claim 9 , wherein the SIP INVITE with replaces header message is received in response to a change in signal strength from a first network that uses the first network address to a second network that uses the second network address.
14. The system of claim 9 , wherein the first communication device has a plurality of different network interfaces, wherein the SIP INVITE with replaces header message is received in response to one of the plurality of different network interfaces failing and/or the one of the plurality of different network interfaces being unable to communicate with the application server.
15. The system of claim 9 , wherein the first communication device has a plurality of different network interfaces and wherein the SIP INVITE with replaces header message is received based on a user input to move the communication session from a first one of the plurality of different network interfaces to a second one of the plurality of different network interfaces.
16. The system of claim 9 , wherein the first network address is a first Internet Protocol (IP) address on a first subnet and the second network address is a second IP address on a second subnet.
17. A first communication device comprising:
a processor that executes a communication module that establishes a communication session with a second communication device, wherein the first communication device uses a first network address to establish the communication session and sends a SIP INVITE with replaces header message with a second network address of the first communication device in response to the first communication device needing to use a different network address.
18. The first communication device of claim 17 , wherein the SIP INVITE with replaces header message is sent in response to a change in signal strength from a first network that uses the first network address to a second network that uses the second network address.
19. The first communication device of claim 17 , wherein the first communication device has a plurality of different network interfaces, wherein SIP INVITE with replaces header message is sent in response to one of the plurality of different network interfaces failing and/or the one of the plurality of different network interfaces being unable to communicate.
20. The first communication device of claim 17 , wherein the SIP INVITE with replaces header message further comprises a takeover tag that identifies to an application server that the SIP INVITE with replaces header message is to be handled differently than a normal SIP INVITE with replaces header message, wherein the takeover tag tells the application server that it does not need to reestablish a second dialog between the application server and the second communication device.