I want to know is it the genral behaviour of all UAC? because as per RFC, c=0 has not been recommended for RTCP purposes, anyway in these cases, we might need RTCP reports also,
Why cant we have one more attribute "a=hold" which indicates its meant for hold and not for one-way media audio stream, Thanks, Udit "Avasarala Ranjit-A20990" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 10/04/2005 02:23 AM To Udit Goyal/C/US/[EMAIL PROTECTED], "SIP Implementors" <[email protected]> cc SIP IETF <[email protected]> Subject RE: [Sip-implementors] Hold SDP Udit You can use c=IN IP4 0.0.0.0 to indicate hold in addition to a-sendonly. Regards Ranjit -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, October 03, 2005 10:42 PM To: SIP Implementors Cc: SIP IETF Subject: [Sip-implementors] Hold SDP Hi, As per RFC 3264, user agent indicate hold by sending "sendonly attribute (assuming sendrecv mode stream). So when UAS receives this SDP, it should respond with "recvonly" attribute. But same mechanism can be used by user agent if he wants to play announcement or music to user, so it can send "sendonly" attribute for media stream. I mean if it simply wants one-way connection (this is not hold). For 3PCC (as B2B), if it wants to provide MOH service, how can it differentiate between two SDP because it will play MOH only in the first scenario when user press hold. Is there any other way where user agent can indicate that this is hold scenario and not one-way audio. Thanks, Udit _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
