[SR-Users] R: R: R: R: acc time mode 2 wrong timestamp
Daniel-Constantin Mierla
miconda at gmail.com
Thu Jun 23 09:26:02 CEST 2016
Hello,
ok -- thanks for testing. I will fix the other acc backends once I get
to the office, then backport and let you know to see if all ok for db as
well.
Cheers,
Daniel
On 23/06/16 08:43, pars3c wrote:
>
> Hello,
>
> with this patch , seem to be ok:
>
> ACC: transaction answered:
> timestamp=1466663709;seconds=1466663709.167;method=INVITE;from_tag=as5f8e4c96;to_tag=as0e316f3c;call_id=2ea0367730d8102848646d56382060ea at x.x.x;code=200;reason=OK
>
>
> ACC: transaction answered:
> timestamp=1466663731;seconds=1466663731.039;method=INVITE;from_tag=349DF52C-13A5;to_tag=as16fd5372;call_id=7992B156-384311E6-8064D5B7-E954FB1D at xxxxx;code=200;reason=OK
>
>
> ACC: transaction answered:
> timestamp=1466663790;seconds=1466663790.238;method=INVITE;from_tag=2F788510-11B2;to_tag=as53814cc1;call_id=9AC1B8B8-384311E6-B88E9F4B-A334AC0D at xxxx;code=200;reason=OK
>
>
> ACC: transaction answered:
> timestamp=1466663819;seconds=1466663819.543;method=BYE;from_tag=2F788510-11B2;to_tag=as53814cc1;call_id=9AC1B8B8-384311E6-B88E9F4B-A334AC0D;code=200;reason=OK
>
>
> ACC: transaction answered:
> timestamp=1466663821;seconds=1466663821.497;method=BYE;from_tag=349DF52C-13A5;to_tag=as16fd5372;call_id=7992B156-384311E6-8064D5B7-E954FB1D@;code=200;reason=OK
>
>
> ACC: transaction answered:
> timestamp=1466663933;seconds=1466663933.434;method=INVITE;from_tag=as62da8249;to_tag=as7bd14809;call_id=0acbd0ef759c06f418dd648e6c564d9c@;code=200;reason=OK
>
>
>
>
>
>
> Thnaks
>
>
>
> *Da:*Daniel-Constantin Mierla [mailto:miconda at gmail.com]
> *Inviato:* giovedì 23 giugno 2016 07:29
> *A:* pars3c; 'Kamailio (SER) - Users Mailing List'
> *Oggetto:* Re: R: R: R: [SR-Users] acc time mode 2 wrong timestamp
>
>
>
> Hello,
>
> can you try with git master branch or backport the next patch?
>
> https://github.com/kamailio/kamailio/commit/0c6653bf1c3ee7b64e811bc752e03fa0adfb0dfe
>
> It is only for the syslog accounting part, if all ok, I will use the
> same fix for db accounting.
>
> Cheers,
> Daniel
>
>
>
> On 22/06/16 23:19, pars3c wrote:
>
> Hi this is the log:
>
> NOTICE: acc [acc.c:298]: acc_log_request(): ACC: transaction
> answered:
> timestamp=1466629783;seconds=2045935.177;method=INVITE;from_tag=3871718769-3859922232-620794507-3935490448;to_tag=as0b2be1eb;call_id=71bdc60e38bd11e68b92002590d192ea at x.x.x.x;code=200;reason=OK
> <mailto:timestamp=1466629783;seconds=2045935.177;method=INVITE;from_tag=3871718769-3859922232-620794507-3935490448;to_tag=as0b2be1eb;call_id=71bdc60e38bd11e68b92002590d192ea at x.x.x.x;code=200;reason=OK>
>
>
>
>
>
>
> *Da:*Daniel-Constantin Mierla [mailto:miconda at gmail.com]
> *Inviato:* mercoledì 22 giugno 2016 21:33
> *A:* pars3c; 'Kamailio (SER) - Users Mailing List'
> *Oggetto:* Re: R: R: [SR-Users] acc time mode 2 wrong timestamp
>
>
>
> Hello,
>
> so you don't get the accounting record in syslog because acc is
> not configured for that.
>
> You need to add:
>
> modparam("acc", "log_flag", FLAG_ACC_CALL)
>
> Then do again a call and see the syslog for the log message with
> acc details.
>
> Cheers,
> Daniel
>
> On 22/06/16 20:09, pars3c wrote:
>
> Hi, these are all the param fora cc module:
>
>
>
> modparam("acc", "db_flag", FLAG_ACC_CALL)
>
> modparam("acc", "db_missed_flag", FLAG_ACC_MISSED_CALL)
>
> modparam("acc", "failed_transaction_flag", FLAG_ACC_FAILED_CALL)
>
> modparam("acc", "db_table_acc", "acc")
>
> modparam("acc", "db_table_missed_calls", "missed_calls")
>
> modparam("acc", "db_extra",
> "src_user=$fU;src_ip=$si;src_domain=$fd;src_port=$sp;dst_user=$rU;dst_domain=$rd;
>
>
> invite_time=$dlg_var(invite_time);c_time=$dlg_var(c_time);hangup_time=$avp(s:hangup);
>
>
> duration=$dlg_var(duration);uniqueid=$dlg_var(uniqueid);a_id_operator=$dlg_var(a_id_operator);b_id_operator=$dlg_var(b_id_operator);
>
>
> alert_time=$dlg_var(alert_time);progress_time=$dlg_var(progress_time);techprefix_len=$dlg_var(lenprefix);
>
>
> parameters=$avp(s:parameters)")
>
> modparam("acc", "detect_direction",
> 1)
>
> modparam("acc", "report_cancels", 1)
>
> modparam("acc", "early_media", 0)
>
> modparam("acc", "time_mode", 2)
>
> modparam("acc", "time_attr", "seconds")
>
>
>
> Thanks
>
>
>
> *Da:*Daniel-Constantin Mierla [mailto:miconda at gmail.com]
> *Inviato:* mercoledì 22 giugno 2016 19:28
> *A:* pars3c; 'Kamailio (SER) - Users Mailing List'
> *Oggetto:* Re: R: [SR-Users] acc time mode 2 wrong timestamp
>
>
>
> Hello,
>
> what are the parameters you set for acc module? Paste all
> modparams for acc here.
>
> Cheers,
> Daniel
>
>
>
> On 22/06/16 10:31, pars3c wrote:
>
> Hi Daniel,
>
> thanks for your support, each instance has your own
> database.In each table the coloumn is double.
>
> I tried to enable the log , in debug level , but i havent
> found any accounting record, only this type:
>
>
>
> DEBUG: acc [acc_logic.c:644]: tmcb_func(): acc callback
> called for t(0x979e5af8) event type 2, reply code 200
>
> May be , i don’t know where to find it.
>
>
>
> The server where i ‘ve this problem use Centos5.4 386
>
>
>
> Thanks
>
>
>
> *Da:*sr-users
> [mailto:sr-users-bounces at lists.sip-router.org] *Per conto
> di *Daniel-Constantin Mierla
> *Inviato:* mercoledì 22 giugno 2016 07:27
> *A:* Kamailio (SER) - Users Mailing List
> *Oggetto:* Re: [SR-Users] acc time mode 2 wrong timestamp
>
>
>
> Hello,
>
> is the same database server used for both kamailio
> instances or each kamailio instance has its own kamailio
> server?
>
> Can you enable logging to syslog the accounting record and
> see if the values are likes in the database? I am trying
> to isolate if the issue is in code or somehow in the
> database column type.
>
> Cheers,
> Daniel
>
> On 21/06/16 10:19, pars3c wrote:
>
> Hello,
>
> i’ve installled the new version of kamailio 4.4.1 . in
> 2 different server , with acc module and these parameters:
>
> modparam("acc", "time_mode", 2)
>
> modparam("acc", "time_attr", "seconds") should be
> seconds.millisec
>
>
>
> On the first server in acc table , in field seconds i
> have values like this 1466493457.85, this is correct
> timestamp ( this server have centos 86_64)
>
> In the other server , i have values like 1913113.702 ,
> that is wrong timestamp . (this is old centos 32 bit )
>
>
>
> What can be the problem? The different version 32,64
> bit ? or some compiler option ?
>
>
>
> Thanks
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
>
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>
> sr-users at lists.sip-router.org
> <mailto:sr-users at lists.sip-router.org>
>
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
>
>
>
>
> --
>
> Daniel-Constantin Mierla
>
> http://www.asipto.com - http://www.kamailio.org
>
> http://twitter.com/#!/miconda
> <http://twitter.com/#%21/miconda> - http://www.linkedin.com/in/miconda
>
>
>
>
>
> --
>
> Daniel-Constantin Mierla
>
> http://www.asipto.com - http://www.kamailio.org
>
> http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> - http://www.linkedin.com/in/miconda
>
>
>
>
> --
>
> Daniel-Constantin Mierla
>
> http://www.asipto.com - http://www.kamailio.org
>
> http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> - http://www.linkedin.com/in/miconda
>
>
>
> --
> Daniel-Constantin Mierla
> http://www.asipto.com - http://www.kamailio.org
> http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> - http://www.linkedin.com/in/miconda
--
Daniel-Constantin Mierla
http://www.asipto.com - http://www.kamailio.org
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20160623/b5666eef/attachment.html>
More information about the sr-users
mailing list