"Andreas Bystr�m" <[EMAIL PROTECTED]> writes:
>I'm a bit confused regarding Call Hold service using SIP. I have seen two
>differnet approaches to solve this:
>1. Send a re-Invite with "0.0.0.0" as the IP address in the sdp data
This is the way recommended in RFC 2543 (Appendix B.5)
>2. Send a re-Invite with the parameter a=sendonly set in the sdp data
This is the way recommended in RFC 3264 (section 8.4), which
obsoletes RFC 2543.
>Is there some draft or RFC about this? Which one is preferred? I guess it is
>best to have support for both ways (at least receiveng call hold) but when I
>send the call hold I need to know which way to use.
>Do you see any pros/cons about the two different solutions?
In one hand a=sendonly is the way recommended by current RFC. On
the one hand, you can use the fingers of that hand to count
implementations that support a=sendonly. If you use 0.0.0.0, the
recipient can not send RTCP to you (if you, for instance, send
muzak to keep the held person on line).
Pekka
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
