<div dir="ltr">I have an AGI system that works off of a calling card system. I have very verbose logging for this AGI system and I store the caller_id and account_number for every log entry. I find it extremely useful for working out what they are doing wrong, or what the system has done in certain circumstances.<br>
<br>If Asterisk could have a similar feature built into its CDR database, that would be a massive help in troubleshooting and debugging, and it would help the support techs as well.<br><br>Ralfe<br clear="all"><br><br>--<br>
"He attacked everything in life with a mix of extraordinary genius and naive incompetence, and it was often difficult to tell which was which."<br>- Douglas Adams<br>==================================<br><br> R a l f e P o i s s o n <br>
<a href="mailto:ralfepoisson@gmail.com">ralfepoisson@gmail.com</a><br><br>==================================<br>
<br><br><div class="gmail_quote">On Tue, Sep 9, 2008 at 3:22 PM, Russell Bryant <span dir="ltr"><<a href="mailto:russell@digium.com">russell@digium.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Johan Wilfer wrote:<br>
> What if we could tie (almost) every event that got logged to the specific<br>
> call id? Sip history dump, notice's, whatever. Then you could dump it<br>
> into a database, and when<br>
> the customer calls again you could easily find the relevant information<br>
> from the log. As of now I spend some<br>
> amount of time in my /var/asterisk/logs/ comparing call numbers and try<br>
> to understand what my customer did.<br>
><br>
> Also - you could easily delete info that is too old to be saved and so on.<br>
><br>
> What do you think? Let's do some brainstorming..<br>
> Is this possible and how can it be implemented?<br>
<br>
</div>This would absolutely be useful, and has been discussed a number of<br>
times. The first step is a _huge_ one, and that is to add an argument<br>
to all of the calls to ast_log and ast_verbose to include the relevant<br>
ast_channel if there is one. Then, logging mechanisms could take<br>
advantage of having access to channel data.<br>
<br>
I guess we could make the API changes in trunk, and then have the mass<br>
conversion be a janitor project ...<br>
<font color="#888888"><br>
--<br>
Russell Bryant<br>
Senior Software Engineer<br>
Open Source Team Lead<br>
Digium, Inc.<br>
</font><div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
--Bandwidth and Colocation Provided by <a href="http://www.api-digital.com--" target="_blank">http://www.api-digital.com--</a><br>
<br>
AstriCon 2008 - September 22 - 25 Phoenix, Arizona<br>
Register Now: <a href="http://www.astricon.net" target="_blank">http://www.astricon.net</a><br>
<br>
asterisk-dev mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br>
</div></div></blockquote></div><br></div>