Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Denial event 1389: Agent login max/error D1=0x1eb D2=0x1bf 2

Status
Not open for further replies.

kb9udr

Technical User
Dec 21, 2009
5
US
Hello,

I have asked this before, without replies, so I figured I would try again.

denial event 1389: Agent login max/error D1=0x1eb D2=0x1bf

I have a station that suddenly cannot login to their assigned hunt group. They are a member of the hunt group. I tried removing the station from the hunt group, deleting the station, re-adding the station, then adding it back into the hunt group. nothing seems to work, and I cannot find anything about this error on the forums. I have 2 other stations setup the same as this one, and they can log into the hunt group just fine.

Please help.
 
I found 2 descriptions of the denial event:

For a CM2.2 and earlier:
Maximum number of simultaneous logins
exceeded, or this agent failed the login digits
check (for example, this agent is using someone
else’s login-id).

For a CM3.0 and later:
Non-EAS ACD split agent. Login processing failed

 
How do I know which CM version I have?

Sorry, I am a bit of a noob when it comes to call processing other than simple stations.
 
#define DNY_MIS_LOGIN (C_DNY_BASE+389) /* acd_compl.c (1389)
* Non-EAS ACD split agent
* mis_ap login processing failed
*/


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

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting
 
With AvayaTier3's post, I was able to use "non-eas acd split agent" and searched that on Google. That pointed me to a long thread that contained this:

This means two things.
You are not using EAS (Expert Agent Selection) with skills and agents

You are using ACD hunt-groups which must me logged into one at a time and
your hunt-groups are measured internally, and the system is programmed to NOT ALLOW users to login without a programmed bcms-vustats loginID

This system restriction is programmed on system-parameters features form
BCMS/VuStats LoginIDs? y
and
Validate BCMS/VuStats Login IDs? y

loginIDs are added with the following command. Making changes on this form associates a LoginID with a name for BCMS reporting.
"Command: change bcms-vustats loginIDs"

From there I was able to notice that my extension was not in the loginids list, and added it back in.

Works now!

Figured I would let you all know.
 
Yes.

Was that you? The signature looks familiar...
 
That was my post

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

bsh

36 years Bell, AT&T, Lucent, Avaya
Tier 3 for 26 years and counting
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top