Why do you need to use agentlogin()
We use queues like this; agent logs in;
Inbound calls come into the queue and we play some information to the caller then the caller hears music on hold and the logged in agents phones ring and agents can make calls if needed or we can restrict with normal dial plan functionality.
the problem ist still when:
Agent is logged in -> he can receive inbound calls on the queues he is on.
Agent cant push any button to take himself from the queue when he is logged in. the only thing he can do is to hungup -> which takes him out of any queues he is in and place outbound call, then relog int a queue.
As AgentLogin() he can only remove himself from queue with hangup or press the * button to deny a call when its configured in queues.
The idea of Agent Pause and Unpause is nice, but how to get this work?
Yes I can see what you are saying as I did a test setup with Agentlogin()
my query was why is it necessary to use Agentlogin() we don’t want our Agent sitting around listing to musiconhold waiting for calls we get the doing some work while waiting for calls.
@ bwilks, how are you getting the agents into the queues.
Thats the idea 
, the agents shall not sit around and hear music.
[quote=“bwilks”]Yes I can see what you are saying as I did a test setup with Agentlogin()
my query was why is it necessary to use Agentlogin() we don’t want our Agent sitting around listing to musiconhold waiting for calls we get the doing some work while waiting for calls.[/quote]
Because our agents are strictly agents, and we have other people to do other work. When you have more than 200 agents, this is a necessity that agents do nothing but attend to calls.
Yes I can see you point busy call centre.
Yes, which is why this makes no sensey.
Mhamilton,
The only thing I can think of that may work in your case (Strictly using AgentLogin) is if you are using something like a newer Polycom hardphone with the microbrowser. Create a page that when chosen will pause the agent via a manager command, then the agent can put the “Live” line that is in the queue on hold without fearing getting calls. Then when they are done with the secondary call, click the unpause button in the microbrowser which will then make them available again for calls. Or maybe integrate the function into the agent’s screen pop utility if you have one.
I have not tested it but it may be an option for you.
[quote=“davevg”]Mhamilton,
The only thing I can think of that may work in your case (Strictly using AgentLogin) is if you are using something like a newer Polycom hardphone with the microbrowser. Create a page that when chosen will pause the agent via a manager command, then the agent can put the “Live” line that is in the queue on hold without fearing getting calls. Then when they are done with the secondary call, click the unpause button in the microbrowser which will then make them available again for calls. Or maybe integrate the function into the agent’s screen pop utility if you have one.
I have not tested it but it may be an option for you.[/quote]
Sounds like a good idea, except we’re using softphones. (eyeBeam)