Refer section 8.4 in RFC 3264. If you want to do this then use a c line with IP 0.0.0.0.
"RFC 2543 [10] specified that placing a user on hold was accomplished by setting the connection address to 0.0.0.0. Its usage for putting a call on hold is no longer recommended, since it doesn't allow for RTCP to be used with held streams, doesn't work with IPv6, and breaks with connection oriented media. However, it can be useful in an initial offer when the offerer knows it wants to use a particular set of media streams and formats, but doesn't know the addresses and ports at the time of the offer. Of course, when used, the port number MUST NOT be zero, which would specify that the stream has been disabled. 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." -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Szabo, Barna Sent: Wednesday, March 28, 2007 1:16 PM To: [email protected] Subject: [Sip-implementors] Receiving unnecessary RTCP Hallo, I would like to accept a call sending 200 OK with a=inactive in the SDP, because I don't want to send or receive at this time any media, but in the RFC 3264 ยง 5.1 stays: "Note that in the case of the Real Time Transport Protocol (RTP) [4], RTCP is still sent and received for sendonly, recvonly, and inactive streams.". I think this is bad, how can I stop the RTCP from caller to me? thanks Barna _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
