DBPostgressAccessor::putHistory ERROR

Discussion in '3CX Phone System - General' started by Mori, Dec 8, 2007.

  1. Mori

    Mori New Member

    Joined:
    Mar 23, 2007
    Messages:
    223
    Likes Received:
    0
    Good morning.

    After upgrade to latest build published friday i got a strange line in log.
    When making outbound (with newest Client) call i get this:

    13:20:34.878 DBPostgressAccessor::putHistory ERROR: duplicate key violates unique constraint "history_pkey"
    13:20:34.808 Call::Terminate [CM503008]: Call(Cool: Call is terminated
    13:20:34.808 DBPostgressAccessor::putHistory ERROR: duplicate key violates unique constraint "history_pkey"
    13:20:34.798 DBPostgressAccessor::putHistory ERROR: duplicate key violates unique constraint "history_pkey"
    13:20:30.944 Line::printEndpointInfo [CM505003]: Provider:[Fortel 7600] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [CallWeaver] Transport: [sip:192.168.XXX.XXX:5060]
    13:20:30.944 CallCtrl::eek:nAnsweredCall [CM503002]: Call(Cool: Alerting sip:XXX425@sipgw1.briiz.no:5060
    13:20:30.373 MediaServerReporting::SetRemoteParty [MS210004] C:8.2:Offer provided. Connection(proxy mode): 62.16.XXX.XXX:16312(16313)
    13:20:30.283 DBPostgressAccessor::putHistory ERROR: duplicate key violates unique constraint "history_pkey"
    13:20:30.273 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(Cool: Calling: VoIPline:97600@[Dev:sip:XXXX425@sipgw1.briiz.no:5060]
    13:20:30.173 CallCtrl::eek:nSelectRouteReq Making route(s) to [sip:%239489XXXX@192.168.XXX.XXX:5060]
    13:20:30.173 MediaServerReporting::SetRemoteParty [MS210000] C:8.1:Offer received. RTP connection: 192.168.XXX.XXX:8000(8001)
    13:20:30.163 CallLeg::setRemoteSdp Remote SDP is set for legC:8.1
    13:20:30.163 Extension::printEndpointInfo [CM505001]: Ext.8000: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX VoIP Client;Rev: 1] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Phone v0.1] Transport: [sip:192.168.XXX.XXX:5060]
    13:20:30.163 DBPostgressAccessor::putHistory ERROR: duplicate key violates unique constraint "history_pkey"
    13:20:30.163
    13:20:30.153 CallCtrl::eek:nIncomingCall [CM503001]: Call(Cool: Incoming call from Ext.8000 to [sip:%239489XXXX@192.168.XXX.XXX:5060]

    Its this line i am confused with.

    DBPostgressAccessor::putHistory ERROR: duplicate key violates unique constraint "history_pkey"

    Never seen it in earlier versions or build and dont have a clue what it means.
    This occures in every call on any line, but the strange thing is that the calls works fine anyway.
     
  2. 5qg4

    5qg4 Active Member

    Joined:
    Jan 31, 2007
    Messages:
    643
    Likes Received:
    0
    I hit this before at V3. Just backup then restore the system file again.
    It should be solved this issue.

    This error only affect the CDR (call log). The call function should be works fine.
     
  3. Mori

    Mori New Member

    Joined:
    Mar 23, 2007
    Messages:
    223
    Likes Received:
    0
    That worked.
    Problem solved. :D

    Thnx.
     
  4. rnoguera

    Joined:
    Oct 25, 2007
    Messages:
    89
    Likes Received:
    0
    I got the same problem, for any call after upgrading to 3648.

    Doing the backup and restore worked.

    Even in this case it is a bug. In the meantime no call logs were made.
     

Share This Page