Re: [Asterisk-Users] Corrupt CDR records in Asterisk 1.2.x
Reply to self: Last week I had some time to figure out a workaround for the CDR logging problem. I used an AGI-script together with de Mysql CLI application. It is far from perfect, and I want to spend some more time to figure out a better way, but this seems to be working OK on my testmachine: This is what I do: I run a DeadAGI script in the Hangup extension like this: --- exten = h,1,Deadagi (fixcdr.sh) exten = h,2,Hangup() --- The /var/lib/asterisk/agi-bin/fixcdr.sh looks like this: -- #!/bin/bash read agi_request read agi_channel read agi_language read agi_type read agi_uniqueid read agi_callerid read agi_calleridname read agi_callingpres read agi_callingani2 read agi_callington read agi_callingtns read agi_dnid read agi_rdnsid read agi_context read agi_extension read agi_priority read agi_enhanced read agi_accountcode set -- $agi_uniqueid uniqueid='$2' set -- $agi_callerid telefoonnummer='$2' echo -e mysql --user=asterisk --password=asterisk --exec='use cdr;UPDATE cdr SET src=\042$telefoonnummer\042 WHERE uniqueid=\042$uniqueid\042' /test/runthis.sh echo -e mysql --user=asterisk --password=asterisk --exec='use cdr;UPDATE cdr SET clid=\042$telefoonnummer\042 WHERE uniqueid=\042$uniqueid\042' /test/runthis.sh -- And then I let cron run the runthis.sh script. And the runthis.sh executes the SQL strings in the file with the mysql monitor application. The place where you put the runthis.sh must be writeable for the user that Asterisk runs on (in my situation running Gentoo it is the user asterisk with group asterisk) As I already told, it is far from perfect (I have to find a way to empty the runthis.sh file after cron has taken care of the CDR updates, and it would be nicer to put the 2 SQL statements together). I don't think you can use this in a high volume environment too, because of the possible load increase on your database when running the runthis.sh. But still I wanted to share this with you, I hope it may be helpful to you people having problem with BRIStuff/CDR. Jeroen - Original Message - From: Jeroen Zwarts [EMAIL PROTECTED] To: asterisk-users@lists.digium.com Sent: Thursday, February 09, 2006 11:05 AM Subject: [Asterisk-Users] Corrupt CDR records in Asterisk 1.2.x 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
Re: [EMAIL PROTECTED]: Re: [EMAIL PROTECTED]: RE: [Asterisk-Users] Corrupt CDR records in Asterisk 1.2.x]]
Has there been an update on this issue yet? Thanks --- [EMAIL PROTECTED] wrote: Ok Thank you very much to all people !! I will wait for the patch, and perhaps in the meantime I could try to introduce the agi workaround suggested by Jeroen, when it will be available. Andrea Tzafrir Cohen [EMAIL PROTECTED] rg.il To Sent by: Asterisk Users list asterisk-users-bo asterisk-users@lists.digium.com [EMAIL PROTECTED] cc m.com Subject [EMAIL PROTECTED]: Re: 10/02/2006 12.07 [EMAIL PROTECTED]: RE: [Asterisk-Users] Corrupt CDR records in Asterisk 1.2.x]] Please respond to Asterisk Users Mailing List - Non-Commercial Discussion [EMAIL PROTECTED] ists.digium.com Kapejod is working on a fix for the CDR problem in bristuff. See below - Forwarded message from [EMAIL PROTECTED] - Resent-From: [EMAIL PROTECTED] Resent-Date: Fri, 10 Feb 2006 13:01:25 +0200 Resent-Message-ID: [EMAIL PROTECTED] Resent-To: [EMAIL PROTECTED] Envelope-to: [EMAIL PROTECTED] Delivery-date: Fri, 10 Feb 2006 05:19:50 -0500 Date: Fri, 10 Feb 2006 11:19:47 +0100 (CET) Subject: Re: [EMAIL PROTECTED]: RE: [Asterisk-Users] Corrupt CDR records in Asterisk 1.2.x] From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Hi, i have had reports about the CDR corruption from various sources. It is a bug introduced by BRIstuff (shame on me) and i am currently working on a fix. The mail server rejecting Andrea's emails is one of Germany's largest ISPs which we use as a proxy. So unfortunately we dont have an influence on that. In any case people can usually find me on MSN ([EMAIL PROTECTED]) to report BRIstuff bugs (no matter if they use our hardware or not). Can you please forward this information to the users list? (I unsubscribed months ago since i couldnt handle the mail volume.) best regards Klaus As seen on asterisk-users... And generally, where should people without Junghanns hardware and systems (plain zaphfc users) turn to? - Forwarded message from [EMAIL PROTECTED] - Envelope-to: [EMAIL PROTECTED] Delivery-date: Fri, 10 Feb 2006 04:32:49 -0500 Resent-From: [EMAIL PROTECTED] Resent-Date: Fri, 10 Feb 2006 11:32:00 +0200 Resent-Message-ID: [EMAIL PROTECTED] Resent-To: [EMAIL PROTECTED] Subject: RE: [Asterisk-Users] Corrupt CDR records in Asterisk 1.2.x To: asterisk-users@lists.digium.com From: [EMAIL PROTECTED] Date: Fri, 10 Feb 2006 10:22:19 +0100 Reply-To: Asterisk Users Mailing List - Non-Commercial Discussion asterisk-users@lists.digium.com 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] To Sent by: 'Asterisk Users Mailing List - asterisk-users-bo Non-Commercial Discussion' [EMAIL PROTECTED] asterisk-users@lists.digium.com, m.com 'Jeroen Zwarts' [EMAIL PROTECTED] cc 10/02/2006 09.51 [EMAIL PROTECTED
RE: [Asterisk-Users] Corrupt CDR records in Asterisk 1.2.x
I have an [EMAIL PROTECTED] 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] En nombre de [EMAIL PROTECTED] Enviado el: jueves, 09 de febrero de 2006 18:28 Para: Jeroen Zwarts; Asterisk Users Mailing List - Non-Commercial Discussion CC: asterisk-users@lists.digium.com; [EMAIL PROTECTED] 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 [EMAIL PROTECTED] nl To Sent by: asterisk-users@lists.digium.com asterisk-users-bo cc [EMAIL PROTECTED] m.com Subject [Asterisk-Users] Corrupt CDR records in Asterisk 1.2.x 09/02/2006 11.05 Please respond to Jeroen Zwarts [EMAIL PROTECTED] nl; Please respond to Asterisk Users Mailing List - Non-Commercial Discussion [EMAIL PROTECTED] 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
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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED]To Sent by: 'Asterisk Users Mailing List - asterisk-users-bo Non-Commercial Discussion' [EMAIL PROTECTED] asterisk-users@lists.digium.com, m.com 'Jeroen Zwarts' [EMAIL PROTECTED] cc 10/02/2006 09.51 [EMAIL PROTECTED] .com Subject Please respond to RE: [Asterisk-Users] Corrupt CDR Asterisk Users records in Asterisk 1.2.x Mailing List - Non-Commercial Discussion [EMAIL PROTECTED] ists.digium.com I have an [EMAIL PROTECTED] 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] En nombre de [EMAIL PROTECTED] Enviado el: jueves, 09 de febrero de 2006 18:28 Para: Jeroen Zwarts; Asterisk Users Mailing List - Non-Commercial Discussion CC: asterisk-users@lists.digium.com; [EMAIL PROTECTED] 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 [EMAIL PROTECTED] nl To Sent by: asterisk-users@lists.digium.com asterisk-users-bo cc [EMAIL PROTECTED] m.com Subject [Asterisk-Users] Corrupt CDR records in Asterisk 1.2.x 09/02/2006 11.05 Please respond to Jeroen Zwarts [EMAIL PROTECTED] nl; Please respond to Asterisk Users Mailing List - Non-Commercial Discussion [EMAIL PROTECTED] 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
[EMAIL PROTECTED]: Re: [EMAIL PROTECTED]: RE: [Asterisk-Users] Corrupt CDR records in Asterisk 1.2.x]]
Kapejod is working on a fix for the CDR problem in bristuff. See below - Forwarded message from [EMAIL PROTECTED] - Resent-From: [EMAIL PROTECTED] Resent-Date: Fri, 10 Feb 2006 13:01:25 +0200 Resent-Message-ID: [EMAIL PROTECTED] Resent-To: [EMAIL PROTECTED] Envelope-to: [EMAIL PROTECTED] Delivery-date: Fri, 10 Feb 2006 05:19:50 -0500 Date: Fri, 10 Feb 2006 11:19:47 +0100 (CET) Subject: Re: [EMAIL PROTECTED]: RE: [Asterisk-Users] Corrupt CDR records in Asterisk 1.2.x] From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Hi, i have had reports about the CDR corruption from various sources. It is a bug introduced by BRIstuff (shame on me) and i am currently working on a fix. The mail server rejecting Andrea's emails is one of Germany's largest ISPs which we use as a proxy. So unfortunately we dont have an influence on that. In any case people can usually find me on MSN ([EMAIL PROTECTED]) to report BRIstuff bugs (no matter if they use our hardware or not). Can you please forward this information to the users list? (I unsubscribed months ago since i couldnt handle the mail volume.) best regards Klaus As seen on asterisk-users... And generally, where should people without Junghanns hardware and systems (plain zaphfc users) turn to? - Forwarded message from [EMAIL PROTECTED] - Envelope-to: [EMAIL PROTECTED] Delivery-date: Fri, 10 Feb 2006 04:32:49 -0500 Resent-From: [EMAIL PROTECTED] Resent-Date: Fri, 10 Feb 2006 11:32:00 +0200 Resent-Message-ID: [EMAIL PROTECTED] Resent-To: [EMAIL PROTECTED] Subject: RE: [Asterisk-Users] Corrupt CDR records in Asterisk 1.2.x To: asterisk-users@lists.digium.com From: [EMAIL PROTECTED] Date: Fri, 10 Feb 2006 10:22:19 +0100 Reply-To: Asterisk Users Mailing List - Non-Commercial Discussion asterisk-users@lists.digium.com 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] To Sent by: 'Asterisk Users Mailing List - asterisk-users-bo Non-Commercial Discussion' [EMAIL PROTECTED] asterisk-users@lists.digium.com, m.com 'Jeroen Zwarts' [EMAIL PROTECTED] cc 10/02/2006 09.51 [EMAIL PROTECTED] .com Subject Please respond to RE: [Asterisk-Users] Corrupt CDR Asterisk Users records in Asterisk 1.2.x Mailing List - Non-Commercial Discussion [EMAIL PROTECTED] ists.digium.com I have an [EMAIL PROTECTED] 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] En nombre de [EMAIL PROTECTED] Enviado el: jueves, 09 de febrero de 2006 18:28 Para: Jeroen Zwarts; Asterisk Users Mailing List - Non-Commercial Discussion CC: asterisk-users@lists.digium.com; [EMAIL PROTECTED] 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 [EMAIL PROTECTED] nl To Sent by: asterisk-users@lists.digium.com asterisk-users-bo cc [EMAIL PROTECTED] m.com Subject [Asterisk-Users
Re: [Asterisk-Users] Corrupt CDR records in Asterisk 1.2.x
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: [EMAIL PROTECTED] To: asterisk-users@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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED]To Sent by: 'Asterisk Users Mailing List - asterisk-users-bo Non-Commercial Discussion' [EMAIL PROTECTED] asterisk-users@lists.digium.com, m.com 'Jeroen Zwarts' [EMAIL PROTECTED] cc 10/02/2006 09.51 [EMAIL PROTECTED] .com Subject Please respond to RE: [Asterisk-Users] Corrupt CDR Asterisk Users records in Asterisk 1.2.x Mailing List - Non-Commercial Discussion [EMAIL PROTECTED] ists.digium.com I have an [EMAIL PROTECTED] 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] En nombre de [EMAIL PROTECTED] Enviado el: jueves, 09 de febrero de 2006 18:28 Para: Jeroen Zwarts; Asterisk Users Mailing List - Non-Commercial Discussion CC: asterisk-users@lists.digium.com; [EMAIL PROTECTED] 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 [EMAIL PROTECTED] nl To Sent by: asterisk-users@lists.digium.com asterisk-users-bo cc [EMAIL PROTECTED] m.com Subject [Asterisk-Users] Corrupt CDR records in Asterisk 1.2.x 09/02/2006 11.05 Please respond to Jeroen Zwarts [EMAIL PROTECTED] nl; Please respond to Asterisk Users Mailing List - Non-Commercial Discussion [EMAIL PROTECTED] 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
Re: [Asterisk-Users] Corrupt CDR records in Asterisk 1.2.x
Hi all bristuffers... Klaus knows about this as I was hassling him about it too! He is investigating. Rgds Tim Robinson Jeroen Zwarts wrote: 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: [EMAIL PROTECTED] To: asterisk-users@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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED]To Sent by: 'Asterisk Users Mailing List - asterisk-users-bo Non-Commercial Discussion' [EMAIL PROTECTED] asterisk-users@lists.digium.com, m.com 'Jeroen Zwarts' [EMAIL PROTECTED] cc 10/02/2006 09.51 [EMAIL PROTECTED] .com Subject Please respond to RE: [Asterisk-Users] Corrupt CDR Asterisk Users records in Asterisk 1.2.x Mailing List - Non-Commercial Discussion [EMAIL PROTECTED] ists.digium.com I have an [EMAIL PROTECTED] 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] En nombre de [EMAIL PROTECTED] Enviado el: jueves, 09 de febrero de 2006 18:28 Para: Jeroen Zwarts; Asterisk Users Mailing List - Non-Commercial Discussion CC: asterisk-users@lists.digium.com; [EMAIL PROTECTED] 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 [EMAIL PROTECTED] nl To Sent by: asterisk-users@lists.digium.com asterisk-users-bo cc [EMAIL PROTECTED] m.com Subject [Asterisk-Users] Corrupt CDR records in Asterisk 1.2.x 09/02/2006 11.05 Please respond to Jeroen Zwarts [EMAIL PROTECTED] nl; Please respond to Asterisk Users Mailing List - Non-Commercial Discussion [EMAIL PROTECTED] 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
Re: [EMAIL PROTECTED]: Re: [EMAIL PROTECTED]: RE: [Asterisk-Users] Corrupt CDR records in Asterisk 1.2.x]]
Ok Thank you very much to all people !! I will wait for the patch, and perhaps in the meantime I could try to introduce the agi workaround suggested by Jeroen, when it will be available. Andrea Tzafrir Cohen [EMAIL PROTECTED] rg.il To Sent by: Asterisk Users list asterisk-users-bo asterisk-users@lists.digium.com [EMAIL PROTECTED] cc m.com Subject [EMAIL PROTECTED]: Re: 10/02/2006 12.07 [EMAIL PROTECTED]: RE: [Asterisk-Users] Corrupt CDR records in Asterisk 1.2.x]] Please respond to Asterisk Users Mailing List - Non-Commercial Discussion [EMAIL PROTECTED] ists.digium.com Kapejod is working on a fix for the CDR problem in bristuff. See below - Forwarded message from [EMAIL PROTECTED] - Resent-From: [EMAIL PROTECTED] Resent-Date: Fri, 10 Feb 2006 13:01:25 +0200 Resent-Message-ID: [EMAIL PROTECTED] Resent-To: [EMAIL PROTECTED] Envelope-to: [EMAIL PROTECTED] Delivery-date: Fri, 10 Feb 2006 05:19:50 -0500 Date: Fri, 10 Feb 2006 11:19:47 +0100 (CET) Subject: Re: [EMAIL PROTECTED]: RE: [Asterisk-Users] Corrupt CDR records in Asterisk 1.2.x] From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Hi, i have had reports about the CDR corruption from various sources. It is a bug introduced by BRIstuff (shame on me) and i am currently working on a fix. The mail server rejecting Andrea's emails is one of Germany's largest ISPs which we use as a proxy. So unfortunately we dont have an influence on that. In any case people can usually find me on MSN ([EMAIL PROTECTED]) to report BRIstuff bugs (no matter if they use our hardware or not). Can you please forward this information to the users list? (I unsubscribed months ago since i couldnt handle the mail volume.) best regards Klaus As seen on asterisk-users... And generally, where should people without Junghanns hardware and systems (plain zaphfc users) turn to? - Forwarded message from [EMAIL PROTECTED] - Envelope-to: [EMAIL PROTECTED] Delivery-date: Fri, 10 Feb 2006 04:32:49 -0500 Resent-From: [EMAIL PROTECTED] Resent-Date: Fri, 10 Feb 2006 11:32:00 +0200 Resent-Message-ID: [EMAIL PROTECTED] Resent-To: [EMAIL PROTECTED] Subject: RE: [Asterisk-Users] Corrupt CDR records in Asterisk 1.2.x To: asterisk-users@lists.digium.com From: [EMAIL PROTECTED] Date: Fri, 10 Feb 2006 10:22:19 +0100 Reply-To: Asterisk Users Mailing List - Non-Commercial Discussion asterisk-users@lists.digium.com 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] To Sent by: 'Asterisk Users Mailing List - asterisk-users-bo Non-Commercial Discussion' [EMAIL PROTECTED] asterisk-users@lists.digium.com, m.com 'Jeroen Zwarts' [EMAIL PROTECTED] cc 10/02/2006 09.51 [EMAIL PROTECTED] .com Subject Please respond to RE: [Asterisk-Users] Corrupt CDR Asterisk Users records in Asterisk 1.2.x Mailing List - Non-Commercial
[Asterisk-Users] Corrupt CDR records in Asterisk 1.2.x
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
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 [EMAIL PROTECTED] nlTo Sent by: asterisk-users@lists.digium.com asterisk-users-bo cc [EMAIL PROTECTED] m.com Subject [Asterisk-Users] Corrupt CDR records in Asterisk 1.2.x 09/02/2006 11.05 Please respond to Jeroen Zwarts [EMAIL PROTECTED] nl; Please respond to Asterisk Users Mailing List - Non-Commercial Discussion [EMAIL PROTECTED] 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
