Can you describe exactly what you lose by using the dynamic queue member
alternative? We tried to ensure that no functionality was lost in this
transition, so if there is something that was missed please let us know
what it is and we'll try to take care of it.
Now, i'm finally trying to
On a side note, does anyone have the URL to the AEL example so I can
write out an extensions.conf version for the wiki?
- --
Kind Regards,
Matt Riddell
Director
It's called queues-with-callback-members.txt in the /docs directory in
the source tree.
- Brad
But as mentioned in the same email, the feature set just isn't the same
and it's a /lot/ more difficult to implement.
I'll be extremely disappointed if it /does/ get removed from Asterisk
without a suitable /easy/ and /equivalent/ function being made readily
available.
Matt Riddell wrote:
On Mon, Sep 17, 2007 at 05:31:30AM -0400, Watkins, Bradley wrote:
On a side note, does anyone have the URL to the AEL example so I can
write out an extensions.conf version for the wiki?
It's called queues-with-callback-members.txt in the /docs directory in
the source tree.
Well, this is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kevin P. Fleming wrote:
Paul Hales wrote:
I stand corrected - when I keyed AddQueueMember onto our in-house
production server (1.2.23) I did not see that option. But on my test
environment on my laptop (1.4.10) it's there looking back at me.
On 9/13/07, Kevin P. Fleming [EMAIL PROTECTED] wrote:
It shouldn't be that hard to translate the AEL example into traditional
dialplan language; in fact, Asterisk does that itself when you load the
AEL into memory, so if you load it yourself and then do a 'dialplan
show' you'll see the
James FitzGibbon wrote:
On 9/13/07, *Kevin P. Fleming* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
It shouldn't be that hard to translate the AEL example into
traditional
dialplan language; in fact, Asterisk does that itself when you
load the
AEL into memory,
On Wed, 2007-09-12 at 21:45 -0700, Kevin P. Fleming wrote:
Paul Hales wrote:
I have written stuff using the addqueuemember, but you lose agent level
functionality and reporting. :(
Can you describe exactly what you lose by using the dynamic queue member
alternative? We tried to ensure
Paul Hales wrote:
It means that you end up reporting on SIP extensions, rather than agents
which doesn't work so well for call centres where people change desks or
have different staff using phones between shifts.
This has already been discussed multiple times on this list, and has not
been
Kevin P. Fleming wrote:
Paul Hales wrote:
It means that you end up reporting on SIP extensions, rather than agents
which doesn't work so well for call centres where people change desks or
have different staff using phones between shifts.
This has already been discussed multiple
Anthony Francis wrote:
So the most helpful thing would be a solid example of how to exactly
duplicate the agent callback login behavior in a real-time friendly
manner. The part I am missing is how we are to do authentication.
Please define what you mean by Realtime friendly. Do you mean the
Kevin P. Fleming wrote:
Anthony Francis wrote:
So the most helpful thing would be a solid example of how to exactly
duplicate the agent callback login behavior in a real-time friendly
manner. The part I am missing is how we are to do authentication.
Please define what you mean
Anthony Francis wrote:
Right I am just saying that I can't use AEL in the DB.
My dialplan is in the DB, not the agents.
It shouldn't be that hard to translate the AEL example into traditional
dialplan language; in fact, Asterisk does that itself when you load the
AEL into memory, so if you
Kevin P. Fleming wrote:
Anthony Francis wrote:
Right I am just saying that I can't use AEL in the DB.
My dialplan is in the DB, not the agents.
It shouldn't be that hard to translate the AEL example into traditional
dialplan language; in fact, Asterisk does that itself when you
On Thu, 2007-09-13 at 12:01 -0700, Kevin P. Fleming wrote:
Paul Hales wrote:
It means that you end up reporting on SIP extensions, rather than agents
which doesn't work so well for call centres where people change desks or
have different staff using phones between shifts.
This has
Paul Hales wrote:
I stand corrected - when I keyed AddQueueMember onto our in-house
production server (1.2.23) I did not see that option. But on my test
environment on my laptop (1.4.10) it's there looking back at me.
That is correct, we added it in 1.4 specifically because it was
necessary
Awhile back I had heard some talk, in this list I believe that Agent
callback login was going to be deprecated in 1.4, I see it is still
there. Does anyone know what is happening with this?
--
Thank you and have a wonderful day,
Anthony Francis
Rockynet VOIP
(303) 444-7052 opt 2
[EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Anthony Francis wrote:
Awhile back I had heard some talk, in this list I believe that Agent
callback login was going to be deprecated in 1.4, I see it is still
there. Does anyone know what is happening with this?
It has been deprecated and use
I tried to use it back in 1.4.6 or so and it is horribly broken, I ended up
rewriting the functionality with dynamic queue members in the dial plan. I
really liked the call back agent feature set. I found it to be far superior
to dynamic queue member alternative.
-Ryan
On 9/12/07, Anthony
It's a great feature, and one hopes it will return one day.
PaulH
On Wed, 2007-09-12 at 19:01 -0700, Ryan Stark wrote:
I tried to use it back in 1.4.6 or so and it is horribly broken, I
ended up rewriting the functionality with dynamic queue members in the
dial plan. I really liked the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Hales wrote:
It's a great feature, and one hopes it will return one day.
PaulH
On Wed, 2007-09-12 at 19:01 -0700, Ryan Stark wrote:
I tried to use it back in 1.4.6 or so and it is horribly broken, I
ended up rewriting the functionality
Matt Riddell wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Hales wrote:
It's a great feature, and one hopes it will return one day.
PaulH
On Wed, 2007-09-12 at 19:01 -0700, Ryan Stark wrote:
I tried to use it back in 1.4.6 or so and it is horribly broken, I
On Thu, 2007-09-13 at 15:23 +1200, Matt Riddell wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Hales wrote:
It's a great feature, and one hopes it will return one day.
PaulH
On Wed, 2007-09-12 at 19:01 -0700, Ryan Stark wrote:
I tried to use it back in 1.4.6 or so
Paul Hales wrote:
I have written stuff using the addqueuemember, but you lose agent level
functionality and reporting. :(
Can you describe exactly what you lose by using the dynamic queue member
alternative? We tried to ensure that no functionality was lost in this
transition, so if there is
24 matches
Mail list logo
