[Kamailio-Users] Accounting: How to avoid a fraudulent BYE with lower CSeq?

[Iñaki Baz Castillo]

El Domingo, 21 de Diciembre de 2008, Daniel-Constantin Mierla escribió:
> Then it comes the billing application that implements the logic to deal
> with different cases. Easiest one is when you have one STOP event, but
> if you have more, then you have to check for reply code, cseq, etc...

Well, as I said I don't need dealing with it if I use radius ACC since only 
one BYE matching the dialog can trigger a SQL STOP action (other BYE's 
matching this dialog will trigger radius STOP action, but not SQL action due 
to "WHERE" clausules the SQL query).

So the only I need is the proxy ensures that the BYE is not fraudulent, for 
example, it's not a spoofed BYE from the user with RURI=same_user.

Anyway, it seems really complex and a post-accounting process should be needed 
as you say. I will try to avoid needing it doing the billing in a B2BUA.

Tahnks.

-- 
Iñaki Baz Castillo