[SR-Users] Module acc - How to get sip_reason/code on log_write_cdr() messages
Daniel-Constantin Mierla
miconda at gmail.com
Tue Nov 5 11:31:04 CET 2019
Hello,
not that clear -- where is that data located from sip traffic point of
view (which request, header, ...)?
The subject of the email referes to the sip code and reason text, which
are in the first line of sip responses, but a dialog has many
requests/responses flowing around...
Cheers,
Daniel
On 05.11.19 10:41, David VILLAUME wrote:
>
> Hello,
>
>
>
> I’m looking for ‘Release cause’ in the dialog-based cdr.
>
>
>
> Hope It’s clearer 😉.
>
>
>
> David
>
>
>
> <http://www.sewan.fr/>
>
>
>
> *David Villaume*
> */Ingénieur VOIX/*
>
>
>
> *T *+33 (0) 1 56 37 73 21 <tel:+33%20(0)%201%2056%2037%2073%2021>
> *E *david.villaume at sewan.fr <mailto:david.villaume at sewan.fr>
>
> 2 cité Paradis, 75010 Paris
> Retrouvez-nous sur www.sewan.fr <http://www.sewan.fr>
>
> <https://www.linkedin.com/company/sewan-communications>
>
>
>
> <http://twitter.com/SewanGroupe>
>
>
>
> <http://www.sewan.fr/suivez-nous/>
>
>
>
> *De :*Daniel-Constantin Mierla <miconda at gmail.com>
> *Envoyé :* mardi 5 novembre 2019 10:00
> *À :* Kamailio (SER) - Users Mailing List
> <sr-users at lists.kamailio.org>; David VILLAUME <david.villaume at sewan.fr>
> *Objet :* Re: [SR-Users] Module acc - How to get sip_reason/code on
> log_write_cdr() messages
>
>
>
> Hello,
>
> are you looking to get the code and text for the initial INVITE? The
> dialog-based cdr is for the call, which can have several transactions
> (sip requests+responses) during its lifetime. The classic acc is per
> event/transaction.
>
> Cheers,
> Daniel
>
> On 05.11.19 09:23, David VILLAUME wrote:
>
> Hello again,
>
>
>
> Sorry for the spam, does someone have an idea about this ?
>
>
>
> Thanks.
>
>
>
> <http://www.sewan.fr/>
>
>
>
> *David Villaume*
> */Ingénieur VOIX/*
>
>
>
> *T *+33 (0) 1 56 37 73 21 <tel:+33%20(0)%201%2056%2037%2073%2021>
> *E *david.villaume at sewan.fr <mailto:david.villaume at sewan.fr>
>
> 2 cité Paradis, 75010 Paris
> Retrouvez-nous sur www.sewan.fr <http://www.sewan.fr>
>
> <https://www.linkedin.com/company/sewan-communications>
>
>
>
> <http://twitter.com/SewanGroupe>
>
>
>
> <http://www.sewan.fr/suivez-nous/>
>
>
>
> *De :*David VILLAUME
> *Envoyé :* mardi 29 octobre 2019 10:52
> *À :* sr-users at lists.kamailio.org <mailto:sr-users at lists.kamailio.org>
> *Objet :* Module acc - How to get sip_reason/code on
> log_write_cdr() messages
>
>
>
> Hello,
>
>
>
> I’m trying to get the reason in my cdrs in log_write_cdr()
> messages while I see It in acc_log_request() messages.
>
>
>
> Is there a way to retrieve it in log_write_cdr() messages ?
>
>
>
> Bellow is my config :
>
>
>
> modparam("acc", "log_level", 1)
>
> modparam("acc", "log_facility", "LOG_LOCAL3")
>
> modparam("acc", "cdr_log_enable", 1)
>
> modparam("acc", "log_flag", 1)
>
> modparam("acc", "failed_transaction_flag", 2)
>
> modparam("acc", "log_missed_flag", 3)
>
> modparam("acc", "report_cancels", 1)
>
> modparam("acc", "cdr_on_failed", 1)
>
> modparam("acc", "cdr_enable", 1)
>
> modparam("acc", "cdr_facility", "LOG_LOCAL3")
>
> modparam("acc", "cdr_expired_dlg_enable", 1)
>
> modparam("acc", "cdr_start_on_confirmed", 1)
>
> modparam("acc", "cdr_extra", "call_id=$ci;src_ip=$si;fU=$fU;")"
>
>
>
>
>
> David VILLAUME
>
>
>
> _______________________________________________
>
> Kamailio (SER) - Users Mailing List
>
> sr-users at lists.kamailio.org <mailto:sr-users at lists.kamailio.org>
>
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
> --
> Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com>
> www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda>
> Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com <http://www.kamailioworld.com>
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20191105/4b8ba3b2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 7170 bytes
Desc: not available
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20191105/4b8ba3b2/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 678 bytes
Desc: not available
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20191105/4b8ba3b2/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 1199 bytes
Desc: not available
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20191105/4b8ba3b2/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 18067 bytes
Desc: not available
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20191105/4b8ba3b2/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.jpg
Type: image/jpeg
Size: 22483 bytes
Desc: not available
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20191105/4b8ba3b2/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 678 bytes
Desc: not available
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20191105/4b8ba3b2/attachment-0002.jpg>
More information about the sr-users
mailing list