From a quick glance, it appears that this is not a trivial change.
the ackcall is handled by the agent channel, and the agent channel doesn't tell queue that the channel has been aswered until the # key is pressed. Once queue understands that the channel is answered it plays the announcement.
To make what you want work, both applications would need additional coding to have app_agent be able to notify app_queue that the end device has answered but wants an announcement message before accepting the caller, and also supply information to app_queue that the end user accepts or rejects the call after hearing the annoucement.
You may want to submit a feature request at http://bugs.digium.com/ asking for this feature.
-Chris
> >CVS-HEAD-10/30/04 > >When using the queue announce= in conjunction with a callback agent it >appears the # key must be pressed before the optional announcement is >heard by the agent (as far as I can tell), this seems to make sense for >always logged in agents, but is in the reverse order of what one might >expect for callback agents. > >I realize the # is an acknowledgement that not only was the call >answered, but there is a real live body on the answering end. Perhaps >the announcement could loop until timeout or ackcall? > >Is there a method available to play the announcement before the ackcall ># key is pressed? What about to loop it until timeout? >
_______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
