I think we are going to do it if we get big problems with those many
queues. From what I'm seeing, the biggest problems seem to be related to
agents, so maybe we can have a try at using straight terminals instead of
agents.
l.
On Fri, 05 Jan 2007 01:14:08 +0100, Leo Ann Boon [EMAIL
On 1/5/07, Lenz [EMAIL PROTECTED] wrote:
I think we are going to do it if we get big problems with those many
queues. From what I'm seeing, the biggest problems seem to be related to
agents, so maybe we can have a try at using straight terminals instead of
agents.
l.
Being somewhat familiar
Yes, unfortunately they want to run a queue for each client, who has
different agents located etc. This is a bit like a true Skill-based
routing using Asterisk standard mechanisms. Apart for the business
problems, I wondered if there are known problems with Asterisk running so
many
You are correct, this is more or less the scenario involved - the problem
is that people want to call a personalized line AND speak to the same
subset of agents preferably.
I have never seen such a setup myself - I have seen CCs with 30 or 40
queues, never 200 - so I was wondering if
On Thu, 04 Jan 2007 11:05:38 +0100
Lenz [EMAIL PROTECTED] wrote:
You are correct, this is more or less the scenario involved - the
problem is that people want to call a personalized line AND speak to
the same subset of agents preferably.
I have never seen such a setup myself - I have seen
Lenz wrote:
You are correct, this is more or less the scenario involved - the
problem is that people want to call a personalized line AND speak to
the same subset of agents preferably.
I have never seen such a setup myself - I have seen CCs with 30 or 40
queues, never 200 - so I was
Lenz wrote:
You are correct, this is more or less the scenario involved - the
problem is that people want to call a personalized line AND speak to
the same subset of agents preferably.
I have never seen such a setup myself - I have seen CCs with 30 or 40
queues, never 200 - so I was
HI Gavin,
wish we could do that! :) the problem is that they want to have
personalized agents too - so that each client has its own line AND his own
agents, so that they get back to speaking to the same people all of the
time. SO we need many different queues to accomodate all those
We are doing this here is RSA.
Please apologize but what does RSA stand for ?
___
--Bandwidth and Colocation provided by Easynews.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
One thing you might want to consider is what distribution strategy to use for
the queues. Note that Asterisk Queues use FIFO methodology to handle calls and
distribute them to the agents.
Say you have one queue and round robin strategy. When 5 calls come in and only
2 agents are available, the
Republic of South Africa
On 04/01/07, Olivier [EMAIL PROTECTED] wrote:
We are doing this here is RSA.
Please apologize but what does RSA stand for ?
___
--Bandwidth and Colocation provided by Easynews.com --
asterisk-users mailing list
To
lenz wrote:
HI Gavin,
wish we could do that! :) the problem is that they want to have
personalized agents too - so that each client has its own line AND his
own agents, so that they get back to speaking to the same people all
of the time. SO we need many different queues to accomodate all
Yeah, get a Business Process specialist to analyze the client's
environment and develop a better solution. 200 queues with only 100
agents sounds pretty ludicrous to me!
On Wed, 2007-01-03 at 14:22 -0600, lenz wrote:
Hello list,
one of our clients is going to be deploying a system with over
Not necessarily... The same agents could very well be providing support for
multiple companies. You wouldn't want an announcement from company A in
company B's queues.
Alex
On 1/3/07, Joe Dennick [EMAIL PROTECTED] wrote:
Yeah, get a Business Process specialist to analyze the client's
I stand corrected, but it still seems excessive.
On Wed, 2007-01-03 at 15:06 -0600, Alex Robar wrote:
Not necessarily... The same agents could very well be providing
support for multiple companies. You wouldn't want an announcement from
company A in company B's queues.
Alex
On 1/3/07,
lenz wrote:
Hello list,
one of our clients is going to be deploying a system with over 200
differently composed queues and 100 agents. We are going to do a full
test of the viability of this solution before deployment, but I was
wondering if anyone has experience of such a setup and if there
16 matches
Mail list logo
