Hi, I have several queues configured at my call center for different support levels. Today, something weird happened: - A client called queue 1 and was answered by an agent - The agent transferred the call to an user (not a queue), by dialing the atxtransfer (1) key defined in features.conf - The user transferred the client to another Queue, by using the second channel and the XFer key of her EyeBeam softphone) - The client entered this second queue and was answered correctly by an analyst from this second queue. But, when I ran "show queue secondqueue" or "show agents", even though the analyst is busy, she appear as available and the call is not registered in queue_log or anywhere else. She also can receive other calls from this queue, since she is not considered busy by the Queue application. Has anybody already realized this issue? Is this a bug or a misuse? Thank you!!! Dov -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060405/5251ad05/attachment.htm
On 04/05/06 21:37 Dov Bigio said the following:> - The agent transferred the call to an user (not a queue), by dialing > the atxtransfer (1) key defined in features.confon a related note, we notice that if we've set atxfer = *1 in features.conf and blindxfer=#1, then attended transfers dont work. somehow, the Queue app captures the '*' and hangs up the call. is this the behaviour others have observed ? obviously, since we've used *2 for auto monitor, that doesnt work as well. -- Regards, /\_/\ "All dogs go to heaven." dinesh@alphaque.com (0 0) http://www.alphaque.com/ +==========================----oOO--(_)--OOo----==========================+ | for a in past present future; do | | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=========================================================================+
In article <4433EB1D.9010407@alphaque.com>, dinesh@alphaque.com says...> on a related note, we notice that if we've set atxfer = *1 in features.conf > and blindxfer=#1, then attended transfers dont work. somehow, the Queue app > captures the '*' and hangs up the call. is this the behaviour others have > observed ? obviously, since we've used *2 for auto monitor, that doesnt > work as well.Yes, this is well known (problem?). I have "solved" it by editing features.conf file. -- Tomislav Parcina tparcina#lama.hr
In article <op.s7k68zmo3wzjep@pc-lenz.xcept.it.local>, lenz-ml@loway.it says...> On Thu, 06 Apr 2006 13:17:29 +0200, Tomislav Par??ina <tparcina@lama.hr> > wrote: > How did you modify it? and will the ATXFR be perceived as a discharge from > the queue system as a blind transfer using #?features.conf blindxfer => #1 ; Blind transfer atxfer => #2 ; Attended transfer automon => #9 ; One Touch Record disconnect => #0 ; Disconnect -- Tomislav Parcina tparcina#lama.hr