Thank you so much. I will test it!
On Tue, Nov 1, 2016 at 1:55 PM, Daniel-Constantin Mierla
wrote:
> An alternative, which I haven't tried it to be 100% sure, but it should
> work as the accounting should happen when a reply is sent out -- anyhow,
> the idea is:
>
> - set an onreply_route for th
An alternative, which I haven't tried it to be 100% sure, but it should
work as the accounting should happen when a reply is sent out -- anyhow,
the idea is:
- set an onreply_route for the BYE requests and inside it, if the code
is 481, the reset the accounting flag(ie., resetflag(FLT_ACC)).
If s
On 11/01/2016 02:58 AM, Gholamreza Sabery wrote:
Is there an option in the ACC module for this, or I should handle
dialog tracking using dialog module?
No, there's no option for it in the ACC module.
Using dialog tracking is one option. Adding a database constraint or
trigger that would prev
Is there an option in the ACC module for this, or I should handle dialog
tracking using dialog module?
On Tue, Nov 1, 2016 at 10:24 AM, Alex Balashov
wrote:
> On 11/01/2016 02:43 AM, Gholamreza Sabery wrote:
>
> If you enable acc module to log CDR data into a database a user can send
>> an infin
On 11/01/2016 02:43 AM, Gholamreza Sabery wrote:
If you enable acc module to log CDR data into a database a user can send
an infinite number of BYE requests to the server and all of them will be
logged into the database as "481 Call/transaction does not exist"! How
can we prevent this?
Don't d
If you enable acc module to log CDR data into a database a user can send an
infinite number of BYE requests to the server and all of them will be
logged into the database as "481 Call/transaction does not exist"! How can
we prevent this?
___
SIP Express R
