Re: [sipx-users] SIPXCDR errors

2013-01-09 Thread Tony Graziano
Do you show any "ongoing calls" in CDR history (active calls)? Have you restarted ONLY CDR service yet? There were issues with this in 4.4 and these were fixed but this was before patch #16. I think you might be in store for an update. It would be helpful to know if these errors show on successful

Re: [sipx-users] SIPXCDR errors

2013-01-09 Thread Melcon Moraes
Hi, Elwin 2 - Not that easy way. All the ruby that does the job are placed in /usr/lib/ruby/gems/1.8/gems/sipxcallresolver-2.0.0/lib I believe you can edit any of the scripts and simply "sipxproc -r CallResover" to see your changes. Maybe the db/cdr_writer.rb can be of some help. In a quick and

Re: [sipx-users] SIPXCDR errors

2013-01-09 Thread Elwin Formsma
Hi Douglas, On this system 4.4 patch #16 Stunnel from SipXecs. Kind regards, Met vriendelijke groet, Elwin Formsma Telecats BV - Elwin Formsma | Telecats bv | KvK Enschede 06069106 | Tel: 053 488 99 44 | Fax: 053 488 99 10 | E-mail: e.form...@telecats.nl | Op 9 jan. 2013, om 12:14 heef

Re: [sipx-users] SIPXCDR errors

2013-01-09 Thread Michael Picher
sorry, my bad... saw the errors about the duplicate key in the database. On Wed, Jan 9, 2013 at 6:14 AM, Douglas Hubler wrote: > On Wed, Jan 9, 2013 at 6:09 AM, Michael Picher wrote: > > Elwin, > > > > Did you try to re-index the database? > > > > There's a trick to do this... in the search b

Re: [sipx-users] SIPXCDR errors

2013-01-09 Thread Douglas Hubler
On Wed, Jan 9, 2013 at 6:09 AM, Michael Picher wrote: > Elwin, > > Did you try to re-index the database? > > There's a trick to do this... in the search box in the upper right, just > enter some junk. On submit of the search a button will appear to re-index > the database. Mike, i don't think th

Re: [sipx-users] SIPXCDR errors

2013-01-09 Thread Michael Picher
Elwin, Did you try to re-index the database? There's a trick to do this... in the search box in the upper right, just enter some junk. On submit of the search a button will appear to re-index the database. Mike On Wed, Jan 9, 2013 at 4:21 AM, Elwin Formsma wrote: > Hi guys, > > Google doe

Re: [sipx-users] SIPXCDR errors

2013-01-09 Thread Elwin Formsma
Hi guys, Google does not give me much additional info about this problem. Also i dont really understand why this should be the problem of Postgres since the queries are initiated by the CDR service? Anyway, there are more errors. These: ERROR: duplicate key violates unique constraint "cdrs_ca

Re: [sipx-users] SIPXCDR errors

2013-01-08 Thread Tony Graziano
If it matters, this is a postgres complaint. I think you would do well to try to restart CDR and if that doesnt clear it up dig into the postgres forums. I would suggest if a lot fo your calling behavior consists of forwards then it is likely a duplicate call id might try to store and postgres woul

Re: [sipx-users] SIPXCDR errors

2013-01-08 Thread Douglas Hubler
y, sounds very familiar, sug. you google it On Tue, Jan 8, 2013 at 6:10 AM, Elwin Formsma wrote: > Hi, > > The following errors occur in the sipxcallresolver LOG. Sipxecs 4.4. Is this > a known issue? > > > "2013-01-08T11:05:01.033231Z":20:CDR:ERR:xxx.nl:main::cdr:", ERROR: > null valu

[sipx-users] SIPXCDR errors

2013-01-08 Thread Elwin Formsma
Hi, The following errors occur in the sipxcallresolver LOG. Sipxecs 4.4. Is this a known issue? "2013-01-08T11:05:01.033231Z":20:CDR:ERR:xxx.nl:main::cdr:", ERROR: null value in column \"from_tag\" violates not-null constraint" "2013-01-08T11:05:01.040001Z":21:CDR:ERR:xxx.nl:main: