If all agents are busy, caller can access agent login

Can't seem to duplicate this one.. Leave it open and see if you can get more info.

--Rob

Asterisk Log during event

According to our customer service people, when the guy called at 8:40am there was nothing going on. None of the guys were on the phone. The customer told our people that he get the greeting and then was send directly to the agent login.

Attched log file

zip version of log file

I'd like to know what sort of ring strategy they have/had setup in the queue. My theory of what is going on is that someone logged into the queue at some point (not on the day in question) and put in 1000* as the agent number by accident. The ring strategy is setup such that for what ever reason, that other logged on agents are called before that 'agent' is called. However, in the trace in question, the previous agent had logged off the queue. So if this 'agent' was left, it is now the one that the queue answered.

If it happens again, before doing anything to reset asterisk or anything, you can do a show queue 1000 And if it shows something like the following you have found your culprit. Btw - I could easily see how an agent could accidently do this, dial into the queue by typing 1000*, then when it asks them to login, they blindly type 1000* again (it's early, not enough coffee yet, etc.). The question is, why isn't it being hit more often - which may have to do with the ring strategy or something.

1000         has 0 calls (max unlimited) in 'roundrobin' strategy (0s holdtime), W:0, C:1, A:3, SL:0.0% within 0s
   Members: 
      Local/1000*@from-internal/n (dynamic) (Unknown) has taken no calls yet
      Local/183@from-internal/n (dynamic) (Unknown) has taken no calls yet
   No Callers

closing bug (so you see it pop up). Check those out, reopen if you think it is something else.