Thanks Jan, that made it work!

Also, it seems that if loose_route processing is applied at the beginning of the route {} statement (as it was my case), BYE's or CANCEL's got processed there and did not get flagged for accounting.

Jaime

Hello,

my quick guess is that you set the accounting flag only for INVITE requests. Make sure that the flag is set also for BYE requests.

By default it is flag 1 (i.e. use setflag(1)) if you didn't change it using modparam.

Jan.

On 25-07 16:48, jaime@umtstrial.co.uk wrote:

...

Hello all,

I have been going through the archives, but could not see any question on the same subject, so here it goes:

After putting together a freeradius server and a CVS version of SER, the server can authenticate users using RADIUS. Now I'm trying to do accounting on certain events, mainly calling and sending messages between clients.

Radius Accounting Start messages are created and sent to the RADIUS server when calling from one User Agent to the other, but no Stop messages are created once the two end points finish the conversation. SIP dialogs are record-routed, so SER is able to see all the transactions.

My questions are:

• What triggers the generation of radius accounting requests?
• Can we configure these triggers somehow (on a per method/filter

basis)?

Any hints on this would be very appreciated.

Jaime

---

Serdev mailing list serdev@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serdev

On 25-07 12:37, Juan J. Sierralta P. wrote:

Based on your experiences guys do the majority of SIP UAs honours RR messages ?

Yes, they must, it is mandatory. The other thing is the loose routing is from time to time not implemented correctly (this is due to complications caused by backwards compatibility with strict routing).

Ignoring Record-Route headers could screw up everything so UAs must honour it.

Because I have an ATA188 which works with RR fine, but a PolyCom 600 doesn't. My PSTN Gateway (Cisco PGW + AS5350) when starts a call against SER and SER then forwards it to my ATA clients with the corresponding RR so the ATAs replies the 200 OK with the RR on it and then back to the PGW it seems that the RR HF isn't acquainted by the PGW and even it doesn't understand the subsequent BYEs which is awfull since the channels aren't free. I'll try to get some dumps later, since we're trying a Cisco BTS as the MG controller now.

Try to use modparam("rr", "enable_full_lr", 1) in your script. If it still doesn't work then, please, send me dumps.

Jan.