Summary:	ASTERISK-04871: External Incoming CDRs not logged in database
Reporter:	Nick Wong (nick_kancharla)	Labels:
Date Opened:	2005-08-22 11:50:53	Date Closed:	2011-06-07 14:10:39
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	CDR/cdr_odbc
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	We are using: RedHat MySQL 3.23.54 Asterisk CVS Jul 2nd Incoming calls that originate from outside the pbx aren't logging into the database, but calls from extension to extension are logged fine. The logs found in /var/log/asterisk/cdr-csv/Master.csv are complete and contain both external incoming calls and extension to extension incoming calls. I can't find any bug related to this issue in cdr_odbc, cdr_mysql, or All. I also can't find any fault in the configuration files of the server. Example Scenarios: Phone off PBX to Cell Phone = Logged in Database, Logged in Master.csv Phone off PBX to Phone off PBX = Logged in Database, Logged in Master.csv Cell Phone to Phone off PBX = NOT Logged in Database, Logged in Master.csv ****** ADDITIONAL INFORMATION ****** --- cdr_odbc.conf --- dsn=asterisk-cdr username=<username> password=<password> loginuniqueid=yes table=cdr
Comments:	By: Nick Wong (nick_kancharla) 2005-08-23 11:37:35 Let me clarify this example with some better terms. VoIP User connected to Asterisk makes an outgoing call to a Cell Phone = Logged in Database as an outgoing call to the second party, Logged in Master.csv the same VoIP User connected to Asterisk makes an outgoing call to another VoIP User connected to the same Asterisk box = Logged in Database as an incoming call to second party, Logged in Master.csv the same Cell Phone places a call to a VoIP User connected to Asterisk = NOT Logged in Database, Logged in Master.csv as an incoming call to the asterisk user. By: Kevin P. Fleming (kpfleming) 2005-08-23 11:45:13 If it's being logged in Master.csv, then the failure must be occurring in the database connectivity. Can you add some debugging to the MySQL CDR module to determine whether it is actually being called with the records in question? By: Nick Wong (nick_kancharla) 2005-08-23 16:32:27 Sure. I'll get back to you with that ASAP. By: Kevin P. Fleming (kpfleming) 2005-08-26 17:28:01 Sorry, I see you are using cdr_odbc, not cdr_addon_mysql. Obviously the debugging information will need to go into cdr_odbc. Please get us more information as soon as you can; if this is a problem with cdr_odbc I'd like to get it fixed ASAP. By: Nick Wong (nick_kancharla) 2005-08-29 08:25:06 I'm covered up here with another app. I will probably have a chance to look at it by wednesday. Sorry about the delay. Nick By: Brian West (bkw918) 2005-08-29 23:02:04 I don't see how it could miss the event at all.  You failed to mention if it was Zap -> {IAX,SIP} /b By: Michael Jerris (mikej) 2005-08-30 00:06:48 I have a sneaking suspicion that you have some sort of constraint on the database causing this.  we really need that debug information to troublshoot this further.  In the mean time, I am going to suspend this bug pending your response with debug information.  Please re-open when you have the debug information available.