Looking into source code I see that the START event is generated for INVITE or ACK and STOP event for BYE or CANCEL, also, the BYE has the code 8.
In your case, maybe the values in RADIUS dictionary are not good, double check that.
If you have enabled report_ack parameters, then most probably the second START event is generated by the ACK -- it is your decision to consider INVITE or ACK as the beginning of the call.
Daniel
On 10/07/04 14:11, SER Users wrote:
Yes this is what I have expected, but I get (in the same time) two Start identical packets except for: Sip-Method = Invite and Sip-Method = Bye
and one Stop packet at the end of the call with: Sip-Method = 8
What I am interested in is if this is the normal behaviour and I should screen out one of the start packets or is my configuration broken.
thanks, Razvan Radu
Daniel-Constantin Mierla writes:
I never used myself RADIUS accounting ... but it should be similar to how database accounting works and you should get events for INVITE and BYE which then have to be correlated in order to get call length. On 10/06/04 15:31, SER Users wrote:
hello, I have ser configured with radius accounting and for each call I get two Start packets and one Stop packet. Is this the correct behaviour or I have miss-configured something ? The only difference between the two Start Packets is the "Sip-Method" attribute which in one is "Invite" and in the other one is "Bye"
What is in the Stop packet? Maybe is more or less same as Start packet with BYE in Sip-Method, but triggered internally by RADIUS server -- SER sends the INVITE and BYE events. Daniel
In my configuration I have: ... modparam("acc", "radius_flag", 2) modparam("acc", "radius_missed_flag", 3) ... setflag(2); if (!t_relay()) { sl_reply_error(); }; ... thanks, Razvan Radu _______________________________________________ Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers