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

[Daniel-Constantin Mierla]

On 12/18/08 22:36, Iñaki Baz Castillo wrote:
> El Jueves, 18 de Diciembre de 2008, Daniel-Constantin Mierla escribió:
>   
>>> The call hasn't finished, but Kamailio has ended the accounting for
>>> this call since it received a BYE. And this BYE will generate a
>>> correct ACC Stop action (since it matches From_tag, To_tag and
>>> Call-ID).
>>>  
>>>       
>> If you use the flags, the BYE will be accounted only if it gets a 200OK.
>> If you set the failed transaction flag, then BYEs with negative replies
>> are accounted as well.
>>     
>
> Ok, I just imagine failed transaction flag for INVITE requests, but clearly 
> it's also util for BYE accouting :)
>
>
>   
>> However, this does not stop kamailio to account another BYE, which may
>> have 200ok or other reply code. It is the job of your billing
>> application to select the right BYE for computing the call duration.
>>     
>
> Yeah. With radius it should be easy, since the SQL query for SOP action will 
> ensure that it wasn't a previous matching BYE.
>   
I don't really get it ... would it select the first or last BYE for a 
call? Will it accept many BYEs for same call or will trigger failure?

Cheers,
Daniel

-- 
Daniel-Constantin Mierla
http://www.asipto.com