On Tue, 2010-01-05 at 10:09 -0500, Raymond Dans wrote:
> Daniel wrote:
> >Subject: RE: [sipX-dev] Populating the CDR pages
> >
> >Thank you and Happy new year!
> >
> >Indeed it is about a development installation (not ISO)
> >
> >- I have tried to change the path LibOdbcDir to /usr/lib in
> >sipxcallresolver.sh (I have also made the softlink), restarted
> >the sipx but I have not seeting the data into the cdr tables (or page)
> >
> >- The sipXproxy.log is saying that:
> >
> >....
> >"2010-01-05T14:49:15.062380Z":83:ODBC:DEBUG:bart.itcnetworks:pi
> >d-17923:B7F59740:SipXProxy:"odbcConnect: Connected to database
> >DATABASE=SIPXCDR;SERVER=localhost;UID=postgres;PWD=;DRIVER={Pos
> >tgreSQL};READONLY=0;, OdbcHandle 0x85791b8"
> >"2010-01-05T14:49:15.062444Z":84:CDR:DEBUG:bart.itcnetworks:pid
> >-17923:B7F59740:SipXProxy:"CallStateEventWriter_DB::openLog
> >connected to database SIPXCDR"
> >"2010-01-05T14:49:15.064104Z":85:ODBC:DEBUG:bart.itcnetworks:pi
> >d-17923:B7F59740:SipXProxy:"odbcExecute: statement INSERT INTO
> >observer_state_events VALUES
> >(DEFAULT,'11.126.12.13:-1',0,timestamp '2010-01-05
> >14:49:15.051',101,'SipXProxyCseObserver'); succeeded"
> >"2010-01-05T14:49:15.064203Z":86:CDR:DEBUG:bart.itcnetworks:pid
> >-17923:B7F59740:SipXProxy:"CallStateEventWriter_DB::writeLog"
> >"2010-01-05T14:49:15.064367Z":88:SIP:DEBUG:bart.itcnetworks:pid
> >-17923:B7F59740:SipXProxy:"SipUserAgent::allowMethod this =
> >'SipUserAgent-2', methodName = 'BYE', bAllow = 1"
> >"2010-01-05T14:49:15.064366Z":87:KERNEL:WARNING:bart.itcnetwork
> >s:OsTimer-9:B77FBB90:SipXProxy:"OsTimerTask::insertTimer timer
> >to fire 31 microseconds in the past, queue length = 0"
> >....
> >
> >
> >- I have cofigured my system with --enable-cdr
> >
> >
> >Not sure what is still wrong in my setup.
> >
> Okay so it looks like CSEs can be written to the database. I guess the
> next set of things to look at are:
>
> - Change the log level for CDR (sipxcallresolver) to DEBUG and then
> check the log sipxcallresolver.log to see if it gives any indication of
> connections issues.
> - Log level for CDR can be changed by logging in as superadmin and
> navigating to System / Logging Levels, select "Show Advanced Settings".
>
> - From a command line, log into the SIPXCDR database and check to see if
> CDR records are being written.
>
> >psql -d SIPXCDR -U postgres
> > select count(*) from cdrs ; ===> counts the number of CDR
> records in the database table.
> > select * from cdrs ; ===> displays all of the records
> in the table.
>
It looks that in the sipxcallresolver.log keeps occurring the messages
below (even without active calls taking place). The log messages seems
to come from a ruby script cse_reader.rb. Of course there are no records
in cdrs table.
"2010-01-06T10:58:04.709621Z":DEBUG:Connecting CSE database.
"2010-01-06T10:58:04.718352Z":DEBUG:Read CSEs from ID: Time:
"2010-01-06T10:58:04.720255Z":ERR:Loss of connection to database -
retrying to connect after sleep
"2010-01-06T10:58:14.721612Z":DEBUG:Connecting CSE database.
"2010-01-06T10:58:14.730530Z":DEBUG:Read CSEs from ID: Time:
"2010-01-06T10:58:14.732499Z":ERR:Loss of connection to database -
retrying to connect after sleep
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
