Hi Johan, Yes, you're right, it is the case of no gap (sequenced or high density lost/discarded frames in a short term) that's not handled correctly. Ticket #722 (http://trac.pjsip.org/repos/ticket/722) tried to fix that along with some other cases (no burst, no lost/discarded frames). Thanks for the report. Regards, nanang On Tue, Feb 3, 2009 at 4:47 PM, Johan Lantz <johan.lantz at genaker.net> wrote: > Hi > > I tried to activate rtcp_xr and after the call is disconnected I call > pjsua_call_dump(..). When doing some calculations inside > pjmedia_rtcp_build_rtcp_xr(..) the c13 value is 0 leading to a crash on the > line below. > > This is only FYI, I do not need this value and maybe there is some prereq in > my kind of call that is not fullfilled in order to actually calculate the XR > values. I just wanted to inform you about the crash in case there is room > for improvments. > > /* Calculate burst and gap durations in ms */ > sess->stat.rx.voip_mtc.gap_dur = (pj_uint16_t)((c11+c14+c13)*m/c13); > > The values when entering the /* Voip Metrics Block */ are: > pj_uint32_t c11 = 112 > pj_uint32_t c13 = 0 > pj_uint32_t c14 = 2 > pj_uint32_t c22 = 2 > pj_uint32_t c23 = 1 > pj_uint32_t c31 = 0 > pj_uint32_t c32 = 1 > pj_uint32_t c33 = 0 > > Best Regards > > Johan > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >
