Crossed-invite call handling
A method and devices for handling crossed-invite situations in set-up of IP-based sessions. A local device receives an incoming session invite after sending an outgoing session invite before the outgoing session invite has been accepted. It then determines that the incoming session invite was sent by the remote device to which the outgoing session invite is also addressed. The method includes determining a remote device priority value from identifying information contained in the incoming session invite, comparing the remote device priority value with a local device priority value to determine whether the remote device or the local device is higher priority and, if the remote device is higher priority, canceling the outgoing session invite and displaying an incoming call answer screen for the incoming session invite, and if the local device is higher priority, waiting for cancelation of the incoming session invite and acceptance of the outgoing session invite.
1. A method implemented at a local device for handling crossed-invites during set-up of an IP-based session with a remote device, the method comprising:
receiving an incoming session invite after sending an outgoing session invite before the outgoing session invite has been accepted;
determining that the incoming session invite was sent by the remote device to which the outgoing session invite is also addressed;
determining a remote device priority value from identifying information contained in the incoming session invite;
comparing the remote device priority value with a local device priority value to determine whether the remote device or the local device is higher priority;
determining that the local device is higher priority; and
while waiting for cancelation of the incoming session invite and acceptance of the outgoing session invite, detecting a busy signal in response to the outgoing session invite and, on that basis, displaying an incoming call answer screen for the incoming session invite.
2. The method claimed in claim 1 , wherein the identifying information comprises a user-part of a remote device address.
3. The method claimed in claim 2 , wherein the remote device priority value is derived from the user-part of the remote device address, and wherein the local device priority value is derived from a user-part of a local device address.
4. The method claimed in claim 3 , wherein the remote device address and the local device address comprise SIP URIs.
5. The method claimed in claim 1 , further comprising:
determining that the local device's identity was not hidden in the outgoing session invite and determining that the remote device is a voice-over-LTE device based on a characteristic of the incoming session invite prior to comparing the remote device priority values.
6. A local device configured to handle crossed-invites during set-up of an IP-based session with a remote device, the local device comprising:
a processor;
memory;
a communication subsystem to communicate with a network over one or both wired and wireless connections to, under control of the processor, send and receive messages; and
a session handling module to establish sessions with other devices, the session handling module including processor-executable instructions that, when executed by the processor, cause the processor to:
receive an incoming session invite after sending an outgoing session invite before the outgoing session invite has been accepted,
determine that the incoming session invite was sent by the remote device to which the outgoing session invite is also addressed,
determine a remote device priority value from identifying information contained in the incoming session invite,
compare the remote device priority value with a local device priority value to determine whether the remote device or the local device is higher priority;
determine that the local device is higher priority; and
while waiting for cancelation of the incoming session invite and acceptance of the outgoing session invite, detect a busy signal in response to the outgoing session invite and, on that basis, display an incoming call answer screen for the incoming session invite.
7. The local device claimed in claim 6 , wherein the identifying information comprises a user-part of a remote device address.
8. The local device claimed in claim 7 , wherein the remote device priority value is derived from the user-part of the remote device address, and wherein the local device priority value is derived from a user-part of a local device address.
9. The local device claimed in claim 8 , wherein the remote device address and the local device address comprise SIP URIs.
10. The local device claimed in claim 6 , wherein the instructions, when executed, further cause the processor to:
determine that the local device's identity was not hidden in the outgoing session invite and determine that the remote device is a voice-over-LTE device based on a characteristic of the incoming session invite prior to comparing the remote device priority values.
11. A non-transitory processor-readable medium storing processor-executable instructions for handling crossed-invites during set-up of an IP-based session with a remote device, wherein the processor-executable instructions, when executed by a processor in a local device, cause the processor to:
receive an incoming session invite after sending an outgoing session invite before the outgoing session invite has been accepted;
determine that the incoming session invite was sent by the remote device to which the outgoing session invite is also addressed;
determine a remote device priority value from identifying information contained in the incoming session invite;
compare the remote device priority value with a local device priority value to determine whether the remote device or the local device is higher priority;
determine that the local device is higher priority; and
while waiting for cancelation of the incoming session invite and acceptance of the outgoing session invite, detect a busy signal in response to the outgoing session invite and, on that basis, display an incoming call answer screen for the incoming session invite.