Vu-Display AGENT NOT MEASURED

[SchuylerJ]

Hey folks,

Have a bit of an odd one. We are using Vu-Disp here to show the agent what AUX state they are in. For the most part it works fine, however I periodically am getting "AGENT NOT MEASURED". I can't see any difference between the agents and have no idea why it works for some but not for others. Attached is the VU template I am using.

I saw another post on this but that guy didn't get an answer so trying my luck.

Thanks!

 

[BIS]

Make sure the hunt group is measured internally.

 

[AvayaTier3]

agents when using EAS are programmed with skills - skill is hunt-group, hunt-group needs measured = internal or both
agents when not using EAS are stations that are programmed as members of hunt-groups.
list usage extension xxxx (will show xxxx and all hunt-groups station is a member of)
all hunt-groups with xxxx as a member needs measured = internal or both

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[SchuylerJ]

Thanks guys but all skills are measured both internally and externally (Had to be for CMS). I saw this product release from Avaya dated in 2000 that detailed the problem I am having:

"In a configuration for non-EAS BCMS login IDs, if an agent administered in multiple splits who is not logged into the first administered split presses the Vu-Stats(Vi-Display) button, the message says Agent Not Measured. Other agents logged into the same hunt groups get accurate data using the same button.

Contact your technical support organization. Request and apply latest approved combo patch that includes patch 12430. Related document: PSN000923"

The issue is that it's only some agents that are getting this display (they are in the same skill sets that the others are, they were duped agents). It's really strange. This PSN was really old and we're on the newest release of CM so I doubt this is the issue. But same behavior.

Any thoughts?