I second that. We have about 40 instances of 1.6 installations all managed by Asterisk-GUI 2.0 and we never regretted it! Imho it is the only slim solution for CF-based low-performance appliances.

The only thing we actually missed was a feature like in freepbx "if user does not answer, goto ..." in case a user does not have voicemail. i know there is still a workaround with ringgroups, so not such a big deal in the end.

keep up the good work!
S.

On 04.08.2010 21:03, Greg Nutt wrote:
Let me add my voice to that concern.  Perhaps anyone else monitoring can do so also so we can show how much appreciation the work on the asterisk-gui there is.

Greg

On 08/04/10 2:19 PM, Ron Byer wrote:
Could I possibly interest you in incorporating this change ?
We finished it this morning.

Thanks a bunch for opening the path to 1.6

I'm a little concerned by "for those that still use it".  I think there is a real place for ast-gui in the CF-card based appliance market.

Regards,

Ron


We are already making a modest change to the asterisk-gui in the main
Queues panel to support a Overall Queue timeout facility (as defined for
the Queue() function)  to enable a max time for call to sit on the queue
before timing out and returning to the dial plan, potentially to be put
on a different queue, or to be sent to VM, etc.  This was a bare minimum
requirement to make the queues/agents as defined by the asterisk-gui
functional, IMO.


Ryan Brindley wrote:
Greetings,
To perform Agent call processing in 1.6 you'll have to move from AgentCallBackLogin to [Add|Remove]QueueMember() functions and extra dialplan fun. Fortunately, I've been instructed to make a new release of the GUI that works on all versions of Asterisk for those that still use it. So literally within days (if not today), there will be a patch resolving your issue!

--                 
Ryan Brindley                 
Digium, Inc. | Software Developer                 
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA                 
main: +1 256-428-6000   fax: +1 256-864-0464                 
Check us out at: http://digium.com & http://asterisk.org


Greetings list,

I was wondering if anyone out there is using asterisk 1.6 with the
asterisk-gui, and, if so, what is the status of the Agent Login
functionality, given
that the AgentCallBackLogin (ACBL) function was deprecated in 1.4, and
{I believe} removed completely in 1.6.

If that's true, then I would expect that the ACBL function is broken ?
(as defined on panel Queues/Agent Login Settings/Second extension)

I am running on 1.4 presently, and don't have any immediate plans to go
to 1.6, but I'm also not interested in painting myself into a corner. I
have seen some "replacement" functionality that performs a similar, but
not identical, function as ACBL, but would require changes in the
asterisk-gui in terms of the code that is generated.

We are already making a modest change to the asterisk-gui in the main
Queues panel to support a Overall Queue timeout facility (as defined for
the Queue() function)  to enable a max time for call to sit on the queue
before timing out and returning to the dial plan, potentially to be put
on a different queue, or to be sent to VM, etc.  This was a bare minimum
requirement to make the queues/agents as defined by the asterisk-gui
functional, IMO.

Any info on Asterisk-gui, Asterisk 1.6, and Agent processing would be
appreciate,

TIA

Ron




--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-gui mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-gui




-- 
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-gui mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-gui

Reply via email to