Changes between Version 8 and Version 9 of SIP_Redirection

Timestamp:

Nov 27, 2008 1:01:34 PM (15 years ago)

Author:

bennylp

Comment:

--

SIP_Redirection

@@ -16 +16 @@
  - must allow application to defer the decision to accept or reject the redirection request (for example, to ask for user confirmation to accept or reject the target)
  - the subsequent INVITE requests sent after the 3xx response must have the same To, From, and Call-ID as used by the original INVITE. While RFC 3261 only put this at RECOMMENDED strength (see section 8.1.3.4), in practice there are many servers out there that relies on this property.
+
+
+== Alternative Way to Handle Redirect Response ==
+
+As alternative to the mechanism described in this article, application can also handle redirection call with the following approach:
+ - extract the URI in the Contact header(s) in the SIP redirect/3xx response
+ - for each URI, create a new invite session/call and send INVITE to this target, trying the targets sequentially and sorting the preference based on the q-value of the Contact.
+
+However this this approach, each call will have a different Call-ID, From, and To headers, hence the applicability probably is more limited.