Robert Sparks wrote:
Here's one I don't know the answer to off the top of my head:
Right now, we can offer the same SDP we've offered before (not changing
the o line). This is used, for instance, with session-timer when we want
to use
a re-INVITE but don't really want to change the session.
However, the specs allow the answer to such a non-changed offer to be
different from the previous answer.
What was the motivation? There were a few attendees at SIPit 21 arguing
that implementation would be simpler for them if this answer had to be a
copy of the previous answer as well. Did we allow it to change just
because we could? Or is there an application I'm not remembering that
really needs this flexibility? If not, would we be willing to add this
restriction?
3PCC is a source of an almost unlimited set of corner cases. :-)
A 3pcc controller doing a transfer may well send an offerless invite to
one UA and then send the offer it gets back to an entirely different UA
than had been in the session before. So of course the answer will be
entirely different.
There are probably other reasons, but I need more time to think of them.
Thanks,
Paul
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
_______________________________________________
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
