Hi! I think Rtcp is only one of the options to solve this problem. Normally, session timers should be used for this purpose. However, I haven't checked whether or not using session timers would disable the dead RTP timer...
Jon, would that be an option for you? -Raphael. Am 05.06.2012 um 10:24 schrieb Vladimir Broz <[email protected]>: > Hello Jon, > > I'm afraid that RTCP is not supported in SEMS. It's on a roadmap, but I > cannot say when it will be implemented. We need to discuss it with Raphael... > > Thanks, > -Vladimir > > Dne 05/31/2012 03:25 PM, Jon Bonilla (Manwe) napsal(a): >> Hi all >> >> I'm using the conference app. Soemtimes there are too many people and I mute >> my >> microphone resulting in sems sending a BYE because rtptimeout after 300 >> seconds. >> >> [nextPacket, AmRtpStream.cpp:702] WARNING: RTP Timeout detected. Last >> received >> packet is too old (diff.tv_sec = 301 >> >> >> I see the configuration option dead_rtp_time >> >> But while muted my softphone sends rtcp packets. Shouldn't sems timeout only >> when no rtp and rtcp is received from the other endpoint? An agressive vad or >> somebody like me muting the micro will make sems timeout. >> >> I'm using 1.4.2 btw. >> >> >> cheers, >> >> Jon >> >> _______________________________________________ >> Sems mailing list >> [email protected] >> http://lists.iptel.org/mailman/listinfo/sems > _______________________________________________ > Sems mailing list > [email protected] > http://lists.iptel.org/mailman/listinfo/sems _______________________________________________ Sems mailing list [email protected] http://lists.iptel.org/mailman/listinfo/sems
