The ACD only jumps into action, when the group is called, not when the agent is called directly. In the later case it will just not that the agent is busy and not distribute other calls to the group to it. Tjapko ITS Consult@ncy wrote: > Hi Jan, this worked! (A message under linux showed me that already) > Now please tell me if I am thinking correctly. > > 1. I put 4 h323 aliasses in a group. An alias represent an endpoint > connected to the gk. > > 2. each endpoint has an alias and a e164 number assigned like: > alias .. e164 > one = 801 > two = 802 > three = 803 > four = 804 > > now I make my alias group in acd like > > one = group > two = group > three = group > four = group > > Now I call from 801 to 802 but I take 802 off the hook and put > distribution_algorithm=LONGEST_IDLE. > > According to what I want it should jump to 803 or 804.......:-) But as > you already might suspect ....it doesn't. > > I tried also this > 801 = group > 802 = group > 803 = group > 804 = group > > But same result. > > Jan, where is my thinking error? > > I have put all access to the status port, configured the > gatekeeper.ini with virtual queue etc, gk routed is on etc all > according the readme file and the acd tool seems to be running > correctly now. > > Tjapko. -- Jan Willamowius, jan@xxxxxxxxxxxxxx, http://www.willamowius.de/ ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________________ List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
