Vector event 542 - can't connect idle agent

[wil19148]

Ran into vector event 542 - can't connect idle agent at one of my customers.

Avaya documentation defines this as "the call at the head of the queue could not be connected to the idle agent"

Does anyone know why this would happen, and how to troubleshoot and/or resolve?

Thanks!

 

[MadAccess]

I dont have an answer for you, but I'm having the same event occuring. The skills these calls are routing to should have plenty of agents staffed plus the queues are set to Unlimited queued calls.

Anybody have any ideas?

 

[jimbojimbo]

You didn't mention what you have as a system but here are a couple of items.

1. If you are using VoIP then do you have sufficient MEDPRO boards in Each Port Network or Media Gateway for the number of inbound trunks, and the codec you are using. Don't forget that the TN2302 provides 32 compressed channels.

2. There was a bug in 1.3 G3si and a patch. If the agent logs out and then back in and is then able to get calls this would be a signature of this problem.

James Middleton
ACSCI/ACSCD/MCSE
Xeta Technologies
jim.middleton@xeta.com