> In RFC 3261 sec 14.1 "UAC Behavior" > describes why the re-INVITE will not be forked. > > "The reason a re-INVITE will never fork > is that the Request-URI identifies the > target as the UA instance it established > the dialog with, rather than identifying an > address-of-record for the user. "
The statement is not normative and conflicts with other statements within RFC3261 and RFC3263 which allow forking within the dialog during error situations when a 503 response or no response is received. If a device supplies a Contact or Record-Route entry which resolves to more than 1 location, forking of a re-INVITE can occur. _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
