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_call_id_unique"
ERROR:  duplicate key violates unique constraint "cdrs_call_id_unique"

My first guess would be that it can be a result of loops in the dialplan. But 
then again there might be more situations that this can occur.
We would really like to resolve these situations since the end result is that 
the callresolver cant handle it and seems to crash. A few questions about this 
one:

1. The Unique contraint is now on the collumn 'call_id'. Why isnt the 
constraint on the combination of collums 'id' and 'call_id'? Wouldn't this 
resolve the errors?
2. Is there an easy way to log the Queries generating the errors? That way it 
would be easier to debug the problem situations.

Thanks in advance,


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: 
[email protected]<mailto:[email protected]> |

Op 8 jan. 2013, om 18:51 heeft Tony Graziano 
<[email protected]<mailto:[email protected]>> het 
volgende geschreven:

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 would complain. Looking more directly at
postgres will probably pinpoint this.

On Tue, Jan 8, 2013 at 11:27 AM, Douglas Hubler 
<[email protected]<mailto:[email protected]>> wrote:
y, sounds very familiar, sug. you google it

On Tue, Jan 8, 2013 at 6:10 AM, Elwin Formsma 
<[email protected]<mailto:[email protected]>> 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:00000000:cdr:", ERROR:  
null value in column \"from_tag\" violates not-null constraint"
"2013-01-08T11:05:01.040001Z":21:CDR:ERR:xxx.nl:main:00000000:cdr:", ERROR:  
null value in column \"from_tag\" violates not-null constraint"
"2013-01-08T11:05:01.139580Z":22:CDR:ERR:xxx.nl:main:00000000:cdr:", ERROR:  
null value in column \"from_tag\" violates not-null constraint"
"2013-01-08T11:05:21.199918Z":23:CDR:ERR:xxx.nl:main:00000000:cdr:", ERROR:  
null value in column \"from_tag\" violates not-null constraint"
"2013-01-08T11:05:31.100696Z":24:CDR:ERR:xxx.nl:main:00000000:cdr:", ERROR:  
null value in column \"from_tag\" violates not-null constraint"
"2013-01-08T11:05:51.331098Z":25:CDR:ERR:xxx.nl:main:00000000:cdr:", ERROR:  
null value in column \"from_tag\" violates not-null constraint"
"2013-01-08T11:06:31.349482Z":26:CDR:ERR:xxx.nl:main:00000000:cdr:", ERROR:  
null value in column \"from_tag\" violates not-null constraint"
"2013-01-08T11:06:31.367072Z":27:CDR:ERR:xxx.nl:main:00000000:cdr:", ERROR:  
null value in column \"from_tag\" violates not-null constraint"
"2013-01-08T11:06:41.400521Z":28:CDR:ERR:xxx.nl:main:00000000:cdr:", ERROR:  
null value in column \"from_tag\" violates not-null constraint"
"2013-01-08T11:06:51.405508Z":29:CDR:ERR:xxx.nl:main:00000000:cdr:", ERROR:  
null value in column \"from_tag\" violates not-null constraint"
"2013-01-08T11:06:51.419459Z":30:CDR:ERR:xxx.nl:main:00000000:cdr:", ERROR:  
null value in column \"from_tag\" violates not-null constraint"
"2013-01-08T11:06:51.425822Z":31:CDR:ERR:xxx.nl:main:00000000:cdr:", ERROR:  
null value in column \"from_tag\" violates not-null constraint"


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: 
[email protected]<mailto:[email protected]> |

_______________________________________________
sipx-users mailing list
[email protected]<mailto:[email protected]>
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
[email protected]<mailto:[email protected]>
List Archive: http://list.sipfoundry.org/archive/sipx-users/



--
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: 
[email protected]<mailto:[email protected]>
Fax: 434.465.6833
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~

Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab 2013!

--
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: [email protected]

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to