Attila Sipos wrote:
3. When putting someone on hold by sending a=sendonly or a=inactive, then also use the "0.0.0.0". This way, if the implementation doesn't understand the sendonly or inactive, it will still stop sending you media.
If you adhere to the above, you should be able to maximise your interoperability.
If you use "0.0.0.0", then there is no point to using a=sendonly. The purpose of a=sendonly is so that the RTCP stream can still remain active, but if you put "0.0.0.0" in the c= line then you can't do that.
If you want to reap the benefits of the new approach and yet still remain backwards compatible, then I think you must try the new way, and then retry the old way if the first attempt fails.
Perhaps we should have specified that a=sendrecv SHOULD be explicitly specified by default, so that it could be used as a hint that the endpoint that used it is also capable of understanding a=sendonly/recvonly/inactive.
But I suppose that wouldn't have been foolproof either. I have seen UAs that fail on a= lines they don't understand.
Paul
_______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
