On 14/05/2021 15:47, Juha Heinanen wrote:

I don't know if it matters, but in modparams you prefix the avp names with "s:", and don't do it in the xlog call.

I actually copied and pasted your code in just to be sure, but no result.

To Barry: I have never shown any mos code for copying. So you must have mixed people up.

I have never used dialog module, since I don't believe it is the job of sip proxy to deal with dialogs.

I just did a simple test where placed the xinfo call after rtpengine_delete() call and got to syslog:

May 14 17:59:01 lohi /usr/bin/sip-proxy[29816]: INFO: ===== rtpengine_delete() May 14 17:59:01 lohi /usr/bin/sip-proxy[29816]: INFO: mos_avg=4.3 packetloss_avg=0 jitter_avg=4 roudtrip_avg=6814

-- Juha

Hi Richard!

On 14/05/2021 16:08, Richard Fuchs wrote:

Are your RTP clients sending RTCP? MOS calculation depends on RTCP. You can look in rtpengine's log, at the end of the call the MOS score is logged together with other stream stats.

OK, this could be the issue. I don't control the clients here.

In more recent versions of rtpengine you can enable local RTCP generation and this should give you stats even if the clients don't send RTCP.

I am running rtpengine 8.5.3.2 - how would I enable this feature or what version would I need?

Thanks

-Barry

Cheers

On 14/05/2021 09.52, [ EXT ] Barry Flanagan wrote:

...

Hi

Using Kamailio 5.4.4 on Debian Buster. I am trying to get feedback of the MOS scores at call end. However the variables are always <null>.

I have the modparams set as follows:

# ----- rtpengine params ----- modparam("rtpengine", "rtpengine_sock", "udp:localhost:2223") modparam("rtpengine", "rtpengine_disable_tout", -1) modparam("rtpengine", "rtpengine_tout_ms", 2000) modparam("rtpengine", "rtpengine_allow_op", 1) modparam("rtpengine", "mos_min_pv", "$avp(s:mos_min)") modparam("rtpengine", "mos_max_pv", "$avp(s:mos_max)") modparam("rtpengine", "mos_average_pv", "$avp(s:mos_avg)") modparam("rtpengine", "mos_average_packetloss_pv", "$avp(s:mos_avg_packetloss)") modparam("rtpengine", "mos_average_jitter_pv", "$avp(s:mos_avg_jitter)") modparam("rtpengine", "mos_average_roundtrip_pv", "$avp(s:mos_avg_roundtrip)")

I am trying to log the values from within the dialog:end event_route:

event_route[dialog:end] {     rtpengine_delete();     xlog("L_INFO","mos_avg=$avp(mos_avg), packetloss_avg=$avp(mos_avg_packetloss), jitter_avg=$avp(mos_avg_jitter), latency_avg=$avp(mos_avg_roundtrip), sip_last_reply=$rs   - $ci\n");     return; }

Am I missing something? I have tried rtpengine_query and rtpengine_manage in place of the _delete and also tried placing this in the BYE handling section of WITHIN_DIALOG but no joy.

Any assistance much appreciated!

-Barry

---

Kamailio - Users Mailing List - Non Commercial Discussions *sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: *https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

---

Kamailio - Users Mailing List - Non Commercial Discussions

• sr-users@lists.kamailio.org

Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:

• https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

On 14/05/2021 17:04, Richard Fuchs wrote:

On 14/05/2021 11.57, [ EXT ] Barry Flanagan wrote:

...

...

In more recent versions of rtpengine you can enable local RTCP generation and this should give you stats even if the clients don't send RTCP.

I am running rtpengine 8.5.3.2 - how would I enable this feature or what version would I need?

This is available from 9.2 onwards. Simply add `generate-RTCP` to your offer or answer flags and this will switch from RTCP passthrough to locally generated RTCP for that call.

OK, great. That might be just what is required.

Many thanks.

-Barry

Cheers

On 17/05/2021 06:57, Hans-Jürgen Brand wrote:

Hello Barry, maybe this helps a littel. https://telecom.altanai.com/2018/04/17/voip-call-metric-monitoring/

Thanks for that. Useful document. Hopefully the "generate-RTCP" flag Richard advised will do the trick.

-Barry