Callback and Call Records BUG

Discussion in '3CX Phone System - General' started by michalpro, Mar 26, 2014.

Thread Status:
Not open for further replies.
  1. michalpro

    Joined:
    Jan 18, 2014
    Messages:
    5
    Likes Received:
    0
    Discovered a strange bug in the system.
    Ver 12 does not recognise that the callback call was actually picked up by an agent- see the log below.

    * Call reports show callback failed.
    * Call reports do not show this call on records at all - you can't listen to it
    * Windows phone shows this call on the recent calls and you can listen to it.

    On the server log it looks like the call was "hanging" in the queue for more than 3 minutes and the customer hang up. Well, the call was for 1 minute in the queue and 2 minutes on the phone with an advisor.

    Here is the log, does not show anything that the call was picked up. Result - almost all calls from callbacks are like this- always FAILED.
    Can anyone advise? We bought this system and as a telecom retailer we wanted to be a reseller but now we're not so sure, every day discovering something strange in the 3CX system.

    26-Mar-2014 16:13:37.474 Leg L:962.1[Line:10024<<NUMBER] is terminated: Cause: BYE from PBX
    26-Mar-2014 16:13:37.474 [CM503008]: Call(C:962): Call is terminated
    26-Mar-2014 16:13:37.472 Leg L:962.3[Queue] is terminated: Cause: BYE from 127.0.0.1:5488
    26-Mar-2014 16:10:16.117 Leg L:962.2[Ivr] is terminated: Cause: BYE from 127.0.0.1:40600
    26-Mar-2014 16:10:15.917 [CM503007]: Call(C:962): Queue:8005 has joined, contact <sip:8005@127.0.0.1:5488>
    26-Mar-2014 16:10:15.913 L:962.3[Queue] has joined to L:962.1[Line:10024<<NUMBER]
    26-Mar-2014 16:10:15.761 [CM503025]: Call(C:962): Calling T:Queue:8005@[Dev:sip:8005@127.0.0.1:5488;rinstance=ca0804c4a58d64dd] for L:962.1[Line:10024<<NUMBER]
    26-Mar-2014 16:10:15.709 [CM503027]: Call(C:962): From: Line:10024<<NUMBER ("to CS:" <sip:NUMBER@192.168.0.80:5060>) to T:Queue:8005@[Dev:sip:8005@127.0.0.1:5488;rinstance=ca0804c4a58d64dd]
    26-Mar-2014 16:10:15.709 [CM503004]: Call(C:962): Route 1: from L:962.1[Line:10024<<NUMBER] to T:Queue:8005@[Dev:sip:8005@127.0.0.1:5488;rinstance=ca0804c4a58d64dd]
    26-Mar-2014 16:09:39.935 [CM503007]: Call(C:962): Ivr:8001 has joined, contact <sip:8001@127.0.0.1:40600>
    26-Mar-2014 16:09:39.934 [CM503007]: Call(C:962): Line:10024<<NUMBER has joined, contact <sip:mad:sip.aql.com:5060>
    26-Mar-2014 16:09:39.931 L:962.2[Ivr] has joined to L:962.1[Line:10024<<NUMBER]
    26-Mar-2014 16:09:39.781 [CM503025]: Call(C:962): Calling T:Ivr:8001@[Dev:sip:8001@127.0.0.1:40600;rinstance=1987ae23f72c2277] for L:962.1[Line:10024<<NUMBER]
    26-Mar-2014 16:09:39.737 [CM503027]: Call(C:962): From: Line:10024<<NUMBER ("to CS:" <sip:NUMBER@192.168.0.80:5060>) to T:Ivr:8001@[Dev:sip:8001@127.0.0.1:40600;rinstance=1987ae23f72c2277]
    26-Mar-2014 16:09:39.737 [CM503004]: Call(C:962): Route 1: from L:962.1[Line:10024<<NUMBER] to T:Ivr:8001@[Dev:sip:8001@127.0.0.1:40600;rinstance=1987ae23f72c2277]
    26-Mar-2014 16:09:39.735 [CM503001]: Call(C:962): Incoming call from Line:10024<<NUMBER to <sip:8001@192.168.0.80:5060>
     
  2. kbrv

    Joined:
    May 15, 2013
    Messages:
    22
    Likes Received:
    1
    I am having the same issue with our phone system.
    About 60-80% of our callback failure messages are for calls where either a successful callback was made earlier or where the operator is actually on the callback at the time the notification gets emailed through.
    V11 used to have the same problem but there was way fewer of them. V12 has made the problem worse.
     
Thread Status:
Not open for further replies.