3.2.6 Timer Events
RTPME has the following RTCP-related timer event processing rules, in addition to those specified in [RFC3550] and [RFC3551].
RTCP Send timer expires: A new RTCP probe and a new RTCP Compound packet are prepared and sent to the network destination. Both packets MUST be sent back to back, that is, the second one immediately after the first one. Restart the timer. If the RTCPSendingRate is "normal", compute a new value for this timer according to [RFC3550] Section 6.2. If the RTCPSendingRate is "fast", set the timer to 250 milliseconds, increment FastRTCPPacketPairCount by 1, and if that counter reaches 40, set RTCPSendingRate to "normal". If a report is being sent in the compound packet and a bandwidth measurement (by RTCP packet pairs or any other method) was done in the last 30 seconds, a bandwidth estimation profile extension SHOULD be attached to each report. If the bandwidth estimate has not converged, the profile extension SHOULD send 0xfffffffd as bandwidth (see section 2.2.7.1). The sender MAY stop sending RTCP probe packets (that is, begin sending only RTCP Compound packets) if it determines that the receiver does not support processing of these packets.
RTCP Bye timer expires: The information associated with the SSRC that started this timer is deleted. If any packet from the same SSRC arrives after the timer has expired, this SSRC will be treated as a new participant.