Benoit Plessis wrote: >> This is a slightly different approach, but have you seen the state interface >> code that is in Asterisk 1.6? There is a backport of the code for 1.4 >> floating >> around somewhere, I think. It allows you to specify a different device for a >> queue member that app_queue will use to determine the state of an agent. So, >> you can still list a Local channel for dialing, but Asterisk will look at the >> state of SIP/myphone, for example, to know whether the agent is busy or not. >> > ok but since we are using IAX2 with ZoIPer for sendurl() handling this > won't help
I don't see why this wouldn't help. You just list the IAX2 peer as the device Asterisk uses to determine the state of the agent. >> Alternatively, if you would like to control the usability of an agent through >> the dialplan, then you could use the DEVICE_STATE() function to create a >> custom >> device state. Then, you could list your custom "device" as what app_queue >> should look at before attempting to call the agent > > This is more interesting :) > Is it from 1.6 too ? Yes, this is also from 1.6, but an unsupported backport of DEVICE_STATE(), exists, as well. http://www.asterisk.org/node/48325 http://www.asterisk.org/node/48360 -- Russell Bryant Senior Software Engineer Open Source Team Lead Digium, Inc. _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users