Hi Tanguy,
the INVITE timestamp is at 200 OK and for ACK when request is received,
so the difference is very,very small (as time). Also the timestamp has
accuracy at second limit, so in most of the cases the INVITE and ACK
will have the same timestamp.
regards,
bogdan
Tanguy Bouzéloc wrote:
Hi Bodgan,
Superb it works like a charm, thanks a lot ;-)
I've another question about openser accouting, a regular call log is
composed by 3 db lines (INVITE, ACK, BYE). I remark that the timestamps
between the INVITE and ACK lines are the same, I think I've miss
something in my configuration anyone have an idea about this ?
Regards,
Tanguy Bouzéloc
Init-Sys
Bogdan-Andrei Iancu a écrit :
Hi Tanguy,
for the statefully processed requests, use the
"failed_transaction_flag" to enable acc for non-2xx. For statelessly
requests, you will have to use acc_db_request().
regards,
bogdan
Tanguy Bouzéloc wrote:
Hello,
I've some issues with my mysql accounting, I can only log successful
calls in the acc table and I've no informations about missed calls. In
mysql accounting I've only sip 200 ok and no errors. I've not this
behavior in my syslog.
It's very important for us for evaluate the performance of our providers
and we can only do it with a database accouting.
For example, If I pass a call and I let it ring til operator timeout,
I've no trace of this call in the accounting table.
I've also another question, the lcr and gw tables have very small fixed
limits (256 for lcr and 32 for gw), since we have much more gateways and
sdas I've updated theses limits to a value which fit our needs, do you
thinks it can be a problem ?
Thanks in advance,
Tanguy Bouzéloc
Init-Sys
_______________________________________________
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users
