> http://track.sipfoundry.org/browse/XCF-3484
> Can someone help me triage this one: it looks like calls set up by sipXconfig click-to-call UI behave differently from calls that are directly > > dialled with regard to overflow queues. I don't think the failure has anything to do with the difference between calling from click-to-call UI vs from TUI. It might be just a conincidence. I just did a quick test on my system with not exactly the same load though (14888), whcih I got inconsistent behavor. Sometimes, I got calls being forwarded to overflow entry at the same time as ringing signed-in agents, even though it should not be an overflow situation. Then after I restart ACD, it was never be able to transfer calls to overflow entry. ( Note: there was no difference if I called from TUI or click-to-call), from the sipxacd.log I saw error: "transferOverflowCall - ACDCall(1) needs to be answered first", and I saw the similar error in the reported case. The other problem I was seeing is that even though the "Call routing scheme" was configured as "Ring All", but it was routed as Circular mode, until I restart ACD. So, to me, from the surface, it does not appear to be related to click-to-call, rather than an ACD call routing issue. Cheers, Huijun _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
