[Asterisk-Users] Corrupt CDR records in Asterisk 1.2.x

Jeroen Zwarts bdjeroen at xs4all.nl
Fri Feb 10 04:21:18 MST 2006


I will try to e-mail Junghanns with this problem. I'll put in a link to the
Google Groups thread that archives this mail.

In the meanwhile I have an idea for a workaround:

Create an AGI script that runs in the hangup extension, reads the
telephonenumber and the unique ID from the AGI variables and updates the
mysql CDR table with the correct telephone number.
I don't know if it's going to work, but that is what I came up with on the
way to my work this morning. I'll keep you posted about the progress, and if
I receive an e-mail back from junghanns.

Jeroen


----- Original Message ----- 
From: <asterisk at frameweb.it>
To: <asterisk-users at lists.digium.com>
Sent: Friday, February 10, 2006 10:22 AM
Subject: RE: [Asterisk-Users] Corrupt CDR records in Asterisk 1.2.x


> Yes, everybody of us use zaphfc.
> No problem at all with zap channel that I have installed in several other
*
> Box (PRI E1, Quad Analog, Chan_capi on 1.0 * series....)
>
> So the problem, I think, is the zaphfc, or the patch to the * and zaptel
> provided by the bristuff.
>
> I tried to post a question to support at junghanns.net but the mail was
> refused with a status code of 550 5.0.0, Dial-Up IP address rejected
> The public ip address I am using is from a newly buyed (3 days ago) set of
> 8 IP Address, so maybe in the past was used for spam...by the way,
> junghanns is the only domain refusing my mail....
>
> If somebody else could ask to junghanns.....
>
> Andrea
>
>
>
>
>
>              Sergio Garcia
>              Murillo
>              <sgm254 at tid.es>                                            To
>              Sent by:                  "'Asterisk Users Mailing List -
>              asterisk-users-bo         Non-Commercial Discussion'"
>              unces at lists.digiu         <asterisk-users at lists.digium.com>,
>              m.com                     "'Jeroen Zwarts'"
>                                        <bdjeroen at xs4all.nl>
>                                                                         cc
>              10/02/2006 09.51          asterisk-users-bounces at lists.digium
>                                        .com
>                                                                    Subject
>              Please respond to         RE: [Asterisk-Users] Corrupt CDR
>               Asterisk Users           records in Asterisk 1.2.x
>               Mailing List -
>               Non-Commercial
>                 Discussion
>              <asterisk-users at l
>              ists.digium.com>
>
>
>
>
>
>
> I have an asterisk at home installed and then upgraded to 1.2.4 with bristuff
> and i have the same problem.
> If you see the logs the INSERT trace has wrong values before the comand is
> executed.
> By the way, everyone of us that have this problem use HFC cards?
>
>
> > -----Mensaje original-----
> > De: asterisk-users-bounces at lists.digium.com
> > [mailto:asterisk-users-bounces at lists.digium.com] En nombre de
> > asterisk at frameweb.it
> > Enviado el: jueves, 09 de febrero de 2006 18:28
> > Para: Jeroen Zwarts; Asterisk Users Mailing List -
> > Non-Commercial Discussion
> > CC: asterisk-users at lists.digium.com;
> > asterisk-users-bounces at lists.digium.com
> > Asunto: Re: [Asterisk-Users] Corrupt CDR records in Asterisk 1.2.x
> >
> > You are in my same situation.
> > I thought I solved the problem (if you look at tomorrow post)
> > but it isn't My situation is a bit different: I have the last
> > bristuffed version of asterisk 1.2.4 (released yesterday) And
> > I also have 2 zaphfc cards.
> > but the behaviour is absolutely the same If you restart
> > asterisk, you get one or two calls ok, the again the problem
> >
> > On the first zaphfc, the problem is almost immediate (1 or
> > two calls) the second is stronger, and is ok for a longer
> > period ( 1 day ??) then it also falls in problem on clid and src
> >
> > It seems to me some buffer overwrite problem. the clid is
> > trasmitted ok to the internal phones.
> >
> > So I am not alone on this side.......
> >
> > Andrea
> >
> >
> >
> >
> >
> >
> >
> >
> >              "Jeroen Zwarts"
> >
> >              <bdjeroen at xs4all.
> >
> >              nl>
> >           To
> >              Sent by:
> > <asterisk-users at lists.digium.com>
> >              asterisk-users-bo
> >           cc
> >              unces at lists.digiu
> >
> >              m.com
> >      Subject
> >                                        [Asterisk-Users]
> > Corrupt CDR
> >                                        records in Asterisk
> > 1.2.x
> >              09/02/2006 11.05
> >
> >
> >
> >
> >
> >              Please respond to
> >
> >                Jeroen Zwarts
> >
> >              <bdjeroen at xs4all.
> >
> >                 nl>; Please
> >
> >                 respond to
> >
> >               Asterisk Users
> >
> >               Mailing List -
> >
> >               Non-Commercial
> >
> >                 Discussion
> >
> >              <asterisk-users at l
> >
> >              ists.digium.com>
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > I have a problem with CDR recording in Asterisk 1.2.x. This is the
> > situation:
> >
> > An Asterisk 1.2.0 (BRIstuffed-0.3.0-PRE-1 with florz) machine
> > with a single HFC-S ISDN BRI card. I log the call records to
> > both the Master.csv and MySQL.
> >
> > The problem is that when an incoming call from the ISDN line
> > is logged to the CDR, the "src" and the "clid" field show up
> > as something like 'h?
'
> > (random weird ASCII characters). This is in the MySQL table
> > as well as the Master.csv, so my guess is that it is not a
> > MySQL problem. Furthermore, I don't think it is a
> > zaptel/bristuff problem, because my AGI scripts get the
> > incoming number without problems all the time.
> > The internal SIP calls are logged without a problem all the
> > time. It's only ISDN calls from the outside world that are corrupt.
> >
> >
> > When I stop Asterisk with "stop now" and restart it, the
> > "src" and "clid"
> > fields are OK for a while, but after a few calls, or as some
> > time passes by (I don't know what triggers it), it goes back
> > to the 'random ASCII weirdness'.
> >
> > I also tested this with Asterisk 1.2.4
> > (BRIstuffed-0.3.0-PRE-1h with florz) and I have the same
> > problem. Again, when I start Asterisk, everything is OK for a
> > while, and then suddenly, the src and clid fields are like 'ÀÜ'
> >
> > Anybody has a clue as where to start looking for a solution
> > for this problem? I can't seem to find a single post, list
> > e-mail or bug related to this problem.
> >
> > Thanks,
> >
> > Jeroen Zwarts
> >
> > _______________________________________________
> > --Bandwidth and Colocation provided by Easynews.com --
> >
> > Asterisk-Users mailing list
> > To UNSUBSCRIBE or update options visit:
> >    http://lists.digium.com/mailman/listinfo/asterisk-users
> >
>
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> Asterisk-Users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>


----------------------------------------------------------------------------
----


> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> Asterisk-Users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>




More information about the asterisk-users mailing list