denial event 1617: Dialing tmo/invalid digit D1=0x891e D2=0x426

[telcomwork]

Agents trying to login with ID and just return to dial tone. I'm trying as well and get the same thing. In list I can't see anything that changed to affect this. Avaya has done an indem a few days ago but this just started happening this AM. We have CM3.0

Any help is much appreciated!

 

[telcomwork]

Agent password was incorrect. Changed password and now back to working.

 

[HuppiFluppi]

Hi. We have the same problem here on a callmaster. The agent can't login.
If I trace it, I get the following line:

denial event 1617: Dialing tmo/invalid digit D1=0x83a5 D2=0x3a97

Password didn't change. If I test this login with the AVAYA IP Agent then I can login, normally.

 

[HuppiFluppi]

No answer? I can't find anything about this problem on the net. Who can help me?

 

[telcomwork]

Can you log in from a diifrent hard phone?

 

[HuppiFluppi]

yes. The login id can be used on other callmasters in the same project.

 

[telcomwork]

Did you do a steer and compare between the two phones maybe a COR issue?

 

[HuppiFluppi]

nothing changed. The callmaster just moved from one table to an other... The status screen for this extension tells me, that the callmaster is connected. It has the same COR like all the other callmaster in the same project...
Where can I find some documentation about error codes?

 

[lopes1211]

Probably didn't change the port when the phone moved. Programming, COR, etc, stays with the port, not the physical set.

-CL

 

[telcomwork]

I looked this error code up in the CM3.0 documentation CD and that's why I started ot look into the wrong digits dialed / password

 

[HuppiFluppi]

I moved the port. The station status says it is connected.