Changes between Version 13 and Version 14 of SIP_Redirection


Ignore:
Timestamp:
Nov 28, 2008 2:46:56 PM (10 years ago)
Author:
bennylp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SIP_Redirection

    v13 v14  
    1818 - must allow application to accept or reject the redirection request on a per-target basis (by means of callback) 
    1919 - 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) 
     20 - must be able to follow multiple targets in 3xx response (and targets that are returned in 3xx response of subsequent INVITE). 
     21 - must be able to remember which targets have been sent INVITE to and not retry the INVITE to these targets 
     22 - must be able to prioritize targets based on the q-value 
    2023 - 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. 
    2124