On Wed, Feb 16, 2011 at 3:02 PM, Matt White <[email protected]>wrote:
> The database is empty. CDR is turned on as far as sipxconfig reports. > > The proxy also looks fairly clean. I do not see anything and a grep for > all errors only reveals > > SipXProxy:"OsConnectionSocket::read[4] error or EOF on fd 14, errno = 0 > Success" > > But I've seen that sip registration messages to a sip trunk. > > Call resolver log does look like it connected to the DB: > > "2011-02-15T20:10:02.967980Z":DEBUG:cse_hosts: host name localhost, host > port: 5432 > > "2011-02-15T20:10:02.970452Z":DEBUG:Polling CSE DB every 10 seconds. > > "2011-02-15T20:10:02.979545Z":DEBUG:Purging CDRs older than Sat Aug 14 > 20:10:02 +0000 2010 > > "2011-02-15T20:10:02.988347Z":DEBUG:CSE Queue Size = 2500 CDR Queue Size = > 1000 > > "2011-02-15T20:10:02.988595Z":DEBUG:Connecting CSE database. #<struct > DatabaseUrl database="SIPXCDR", port=5432, host="localhost", > adapter="postgresql", username="postgres"> > > "2011-02-15T20:10:02.994888Z":DEBUG:Purging CSEs older than Tue Feb 08 > 20:10:02 +0000 2011 > > "2011-02-15T20:10:02.995076Z":DEBUG:State Thread priority = 2 > > "2011-02-15T20:10:02.997681Z":DEBUG:Read CSEs from ID: Time: > > "2011-02-15T20:10:03.005278Z":DEBUG:Going to sleep. Connection > localhost:5432 > > "2011-02-15T20:10:13.009165Z":DEBUG:Waking up. Connection localhost:5432 > problem is probably on the proxy side then. put proxy log level to DEBUG and run tail -f /var/log/sipxpbx/sipXproxy.log | grep CallStateEventWriter_DB and place a call you should get something. I do. "2011-01-22T20:19:07.483556Z":20340:CDR:DEBUG:finch.hubler.us: SipXProxyCseObserver-14:411B5940:SipXProxy:"CallStateEventWriter_DB::writeLog"
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
