Hi,

yes, that's the right way to use it - multi leg accounting will log same acc record for each call leg, but having the src and dst different (reflecting what you configured from the script). Normally the multi leg accounting should be visible only for INVITE (as initial request).

regards, bogdan

Fedor Kiselev wrote:

Hi All, I have the following configuration:

...

modparam("acc", "log_level", 1) modparam("acc", "log_flag", 1) modparam("acc", "multi_leg_enabled", 1) modparam("acc", "src_leg_avp_id", 110) modparam("acc", "dst_leg_avp_id", 111) modparam("acc", "db_flag", 1) modparam("acc", "log_missed_flag", 1) modparam("acc", "db_missed_flag", 1)

In the main route:

...

avp_printf("i:110", "<$fu>"); avp_printf("i:111", "<$ru>"); setflag(1);

In the failure route:

...

if (isflagset(26) && t_check_status("408") ) { avp_pushto("$ruri", "s:fwd_noanswer"); resetdsturi(); lookup("location"); resetflag(26); avp_printf("i:110", "<$fu>"); avp_printf("i:111", "<$ru>"); t_relay(); }

After making a call which has been forwarded I have several similar strings in mysql but with the different src_leg and dst_leg. Is it the right behavior of multi leg accountng ?

---

| sip_method | +------------+ | INVITE | | INVITE | | INVITE | | INVITE | | ACK | | ACK | | BYE | +------------+

---

Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users