Client Ring for 1 second

[mahmoud.helmy@cairoairpor]

Dear support
i have 10 agent available i use round robin strategy
some times call ring for 1 second and drop then ring again in same agent and calculated missed like below :
12/29/2019 6:23:23 PM - [CM503003]: Call(C:8222): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 192.168.1.57:49213

cdr.log
Call 348707,0000016F5277C31A_8222,00:00:24,2019/12/29 16:22:58,TerminatedBySrc,idelete the client noumber ,Ext.8001,10001,8001,8001,ReplacedDst,Ext.6001,6001,Chain: idelete the client noumber ;Ext.8001;Ext.6001;,2019/12/29 16:23:23,1014;

 

[eddv123]

More information required such as what are the endpoints involved in the (I assume based on the polling strategy-queue), where are they all located and are they logged in.

Also the version of 3CX you have and where is it located in regards to the endpoints.

A 4xx style request normally denotes a client side issue.

 

[mahmoud.helmy@cairoairpor]

@eddv123
all agent logged in and ''call come from ivr to queue to extension then agent"'
normal synario: ring time for agent on the queue 15 seconds after call reach 15 seconds the call calculated missed and transfer to next available agent
non normal synario :ring time for agent on the queue 15 seconds after call reach 1 or 2 second
calculated missed and call back to the same agent and he served the call and calculated not served
like this log

8001:this is ivr ex
6001 :queue ex
and call end in 6001 in log but that not what happen in real
what happen like above in non normal synario

Call 348707,0000016F5277C31A_8222,00:00:24,2019/12/29 16:22:58,TerminatedBySrc,idelete the client noumber ,Ext.8001,10001,8001,8001,ReplacedDst,Ext.6001,6001,Chain: idelete the client noumber ;Ext.8001;Ext.6001;,2019/12/29 16:23:23,1014


3cx version 16
3cx hosted local in same network with agent.

 

[eddv123]

I think the best approach in seeing what is going on here is to probably get the logs and output of the issue with the 3CX binary log viewer.

Trace the issue in Verbose mode and look at the files: https://www.3cx.com/docs/3cx-log-viewer/