How could it possibly work to have a different contact for each dialog
usage? These are all sharing a common dialog. They share things like the
CSeq. If they have different Contacts, then things in different places
are going to be trying to maintain the dialog state.
Frankly it is hard enough to see how a target refresh can be made to
work at all.
Paul
Jeroen van Bemmel wrote:
Perhaps the interpretation should be that there is a contact per
dialog usage?
No, no, no. 3261 is very clear that the target belongs to the dialog,
not the dialog usage. There is no way that having separate ones could
work.
Well... 3261 is also very clear on that BYE terminates the dialog, and
yet some people argue that it should only terminate a single usage...
It's just that the notion of a "dialog usage" is not very well defined
in rfc3261
I'm not saying that Contact per usage is necessarily a good idea, just
trying to see if there are any use cases for it. For example, what you
could do is specify a different transport for NOTIFYs (TCP) while still
using UDP for session refresh, etc.
Jeroen
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
