Thanks you!
10.04.2019 10:28, Jan-Hendrik Dörner пишет:
Hello,
i was working on a similar problem. I followed the acc-dialog ->
(r)syslog approach.
In rsyslog I piped the message to a script, which appends the message
as a xml-record to a file in "/var/log/kamailio-call.log“.
(This script
Hello,
i was working on a similar problem. I followed the acc-dialog -> (r)syslog
approach.
In rsyslog I piped the message to a script, which appends the message as a
xml-record to a file in "/var/log/kamailio-call.log“.
(This script might be useful for you to adapt to your needs.)
Hello,
some starting points:
- use dlg_manage() or set a dialog flag in the cfg to start dialog tracking
- setup the dialog event routes (section 11 in README) and put your
logging logic there
Best regards,
Henning
Am 06.04.19 um 11:29 schrieb Yu Boot:
> How to make something on dialog
How to make something on dialog event? Just can't figure it out after
reading module docs :(
06.04.2019 2:09, David Villasmil пишет:
You can always export the cdr table periodically.
Take a look at siremis. And when the trigger fires every 5 minutes to
create the cdrs, just export them.
You can always export the cdr table periodically.
Take a look at siremis. And when the trigger fires every 5 minutes to
create the cdrs, just export them.
Also, as it’s been said, you can use the dialog and when the call ends
gather all the info and just print it out. You can direct it to
The time params for acc are related to writing the event-based
(transaction) accounting records -- the native mode for acc module (with
no dialog involved).
The cdrs are controlled by dialog module, call_start being stored in the
dialog structure and with that is also computed the call_end.
I
Hi,
As Daniel said, you may want to look to the Dialog module here. You can use an
xlog statement, database call, api, or whatever you would like to customize
this for your needs.
This list isn’t to do the work for you, but to steer you in the right
direction.
It may be helpful to tell the
Anyone? I can't believe that nobody of Kami users don't have these
problems with CDR.
03.04.2019 16:03, Yu Boot пишет:
You didn't catch my idea. Here's what Kami writes to syslog:
NOTICE: acc [acc_cdr.c:352]: log_write_cdr():
start_time=1554295999.014; end_time=1554296092.164;
You didn't catch my idea. Here's what Kami writes to syslog:
NOTICE: acc [acc_cdr.c:352]: log_write_cdr():
start_time=1554295999.014; end_time=1554296092.164; duration=93.150;
src_user=4956885645; src_domain=65.181.181.218; src_ip=65.181.181.218;
dst_ouser=9956885645; dst_user=6004440;
You can direct the syslog messages printed by acc module by setting the
parameter:
-
https://www.kamailio.org/docs/modules/5.2.x/modules/acc.html#acc.p.log_facility
to a specific value and then configure the syslog application to write
the messages with that facility to a specific file. In
Thanks for a reply
I need CDR easily "greppable", so it must be in regular text file. Very
easy to parse, generate stats, and again, it can be "tail-f'ed".
And I want time in human readable format.
Now iI use acc/dialog, result is horrible syslog output which is 50%
meaningless syslog
The dialog+acc can also write the cdrs to database, afaik. If
documentation says different, maybe it was forgotten to be updated.
Or you look for something different than using dialog+acc?
Cheers,
Daniel
On 03.04.19 13:27, Yu Boot wrote:
>
> Is there any other way to retrieve CDRs from Kami
Is there any other way to retrieve CDRs from Kami other than dialog/acc
modules and writing CDRs to syslog only?
Thanks.
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
13 matches
Mail list logo
