Subbu, RFC3264 has stated 0.0.0.0 is not only used in call hold.
And you should not send any RTP/RTCP data to stream of 0.0.0.0 RFC3264 sec 8.4 <snip> An agent MUST be capable of receiving SDP with a connection address of 0.0.0.0, in which case it means that neither RTP nor RTCP should be sent to the peer. </snip> Regards, -Rockson -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Subbu Rajendran Sent: Friday, October 24, 2008 6:11 PM To: sip-implementors@lists.cs.columbia.edu Subject: [Sip-implementors] SIP media change - Is the precedence forc=0.0.0.0 or a= attribute? Hi, SIP RFC 2543 uses c=0.0.0.0 method to put a call on hold. RFC 3264 has introduced a=sendonly/recvonly/inactive/sendrecv attributes that can be used put media to one way, hold and 2-way. However what should be the precedence to be followed? Consider the case below A Re-INVITE with SDP v=0 o=user1 53655765 2353687637 IN IP4 192.168.1.100 s=- c=IN IP4 0.0.0.0 t=0 0 m=audio 6001 RTP/AVP 0 a=rtpmap:0 PCMU/8000 a=recvonly How should the SIP endpoint receiving this Re-INVITE interpret the SDP, w.r.t the flow of media. Which method should be given preference. Any help in this context is very much appreciated. Thanks & Regards, Subbu _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
