Here's a really interesting one.
Lots of people are sending REFER with a Refer-To URI that has an
embedded Replaces header.
This is what we're specifying in cc-transfer.
Nobody puts Require: replaces in the REFER request (and I don't think
they should - does anybody disagree?)
However, very few implementations are putting Require: replaces in
the triggered INVITE. They're copying the Replaces header into
the INVITE though.
This will cause very wrong things to happen if that triggered INVITE
forks.
From talking to people at SIPit 21, I don't think leaving the
Require off of the INVITE was done on purpose - just that the code
path followed blindly copied the headers from the URI into the
triggered request and didn't check to see if it needed to explicitly
signal an extension.
We might look for places to tighten up the text on extensions so that
implementors get this one right.
One implementor was including the Require: replaces as an imbedded
header in the Refer-To URI. That shouldn't break anything,
but it also shouldn't be required.
What can we do to make this better?
RjS
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
