[EMAIL PROTECTED] wrote:
Hello,
I've tried to find from the Draft(/RFC) without success that how a server is supposed to work when it receives a request with "no-fork" but it has addresses with equal q value. I mean in what cases can it happen that the server does not accept the "no-fork" directive?
In this case, if the proxy wants to honor the no-fork, it would pick one of the contacts to use - presumably one of the ones with the highest q-value.
Generally, what is the best way for gateway type of UAs to indicate that no forking should happen as e.g. parallel early media may confuse the user? Does it help if Proxy-Require is set to indicate that pref extension need to be supported?
Remember - caller prefs are indeed *preferences*. They are not binding on the proxy even if there is a proxy-require.
There is nothing a UAC can do to *guarantee* that its request won't be forked. It must be prepared to deal with that case, somehow.
Paul
_______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
