I went to run my queue_log parser so that I could send out a monthly report to one of my customers, and I noticed that every valid call complete action (COMPLETEAGENT, COMPLETECALLER) is followed by an ABANDON:
Here is a complete-caller: 1123325015|1123325011.2|mainq|NONE|ENTERQUEUE||00110102102 1123325020|1123325011.2|mainq|Agent/21|CONNECT|5 1123325030|1123325011.2|mainq|Agent/21|COMPLETECALLER|5|10 1123325030|1123325011.2|mainq|NONE|ABANDON|1|1|15 Here is a complete-agent: 1123325051|1123325047.7|mainq|NONE|ENTERQUEUE||00110102102 1123325055|1123325047.7|mainq|Agent/21|CONNECT|4 1123325061|1123325047.7|mainq|Agent/21|COMPLETEAGENT|4|6 1123325061|1123325047.7|mainq|NONE|ABANDON|1|1|10 Here is an actual abandon: 1123326180|1123326178.13|NONE|Agent/21|AGENTCALLBACKLOGIN|[EMAIL PROTECTED] 1123326196|1123326192.14|mainq|NONE|ENTERQUEUE||00110102102 1123326205|1123326192.14|mainq|NONE|ABANDON|1|1|9 I created mantis bug 4910: http://bugs.digium.com/view.php?id=4910 I guess I'll have to hack my parser up to ignore any data after the first complete type. Is anyone else seeing this? -Ryan _______________________________________________ Asterisk-Users mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
