Summary: | ASTERISK-05827: unique signature do not match beetween queue_log and recorded calls | ||
Reporter: | nording (nording) | Labels: | |
Date Opened: | 2005-12-13 04:05:01.000-0600 | Date Closed: | 2011-06-07 14:10:47 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Channels/chan_agent |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | Unique signature do not match beetween queue_log and recorded calls, thus it is very hard to automaticaly find record file when looking queue_log and vice-versa. Maybe a wrong side of a bridged call is used when querying "->uniqueid" or something like this? ****** ADDITIONAL INFORMATION ****** examples of queue_log entries and manualy matched call-record files: normaly the difference is tiny - second number differs by caller wait time (3 sec here): 1134405700|1134405700.7965|q1|NONE|ENTERQUEUE||74957700644 1134405703|1134405700.7965|q1|Agent/2104|CONNECT|3 1134405793|1134405700.7965|q1|Agent/2104|COMPLETECALLER|3|90 agent-2104-1134405700-7968-in.wav more caller waits - more is difference (6 sec here): 1134022876|1134022876.19676|q1|NONE|ENTERQUEUE||70950000001 1134022882|1134022876.19676|q1|Agent/2114|CONNECT|6 1134022965|1134022876.19676|q1|Agent/2114|COMPLETECALLER|6|83 agent-2114-1134022876-19682-in.wav but when agent, who take a call is busy at the moment of call arrival to the queue, not only second number differs, but also do the first: 1134022937|1134022937.19684|q1|NONE|ENTERQUEUE||70950000001 1134022984|1134022937.19684|q1|Agent/2114|CONNECT|47 1134023009|1134022937.19684|q1|Agent/2114|COMPLETEAGENT|47|25 agent-2114-1134022977-19722-in.wav | ||
Comments: | By: Kevin P. Fleming (kpfleming) 2005-12-13 10:07:34.000-0600 The callid in the queue_log is the callid of the incoming call; the callid of the recorded file is the callid of the call placed to the agent. They will not match. You will need to find a way to generate your recorded files using the incoming call's callid, instead of the agent's callid. This is a configuration issue, not a bug. |