Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: TimPNRHA on October 09, 2012, 02:12:18 PM
-
Good Afternoon Everyone,
Just recently I have had a user report that they cannot log in via Hot Desking. When logging in they receive Feature Failed. They previously were working and still everyone in the cluster and on that particular controller is still working. I have removed the user and re-added her back and still have the same feature. I show that she is not logged in and still ran the Bust Reset command on her extension. List below are the log messages for her.
Log Type Maintenance
Log Number 1740
Severity Info
Date 2012/Oct/09
Time 12:08:11
Source MOBILITY
Description Hot Desk : Login of 52590 at 413 initiated
Module Main
File Name and Line Number Maintenance;0
Log Type Maintenance
Log Number 1741
Severity Info
Date 2012/Oct/09
Time 12:08:11
Source MOBILITY
Description Hot Desk : redirect or update failed for 413
Module Main
File Name and Line Number Maintenance;0
Log Type Maintenance
Log Number 1742
Severity Info
Date 2012/Oct/09
Time 12:08:11
Source MOBILITY
Description Hot Desk : Login failed at 413 - Redirect or update issue
Module Main
File Name and Line Number Maintenance;0
Log Type Software
Log Number 1743
Severity Warning
Date 2012/Oct/09
Time 12:08:11
Source ViPER
Description LoginManager::sHandleCookieUpdateResult() -> Cookie update/delete fails for DN=413 when op = REGISTER_COMPLETED
Module Main
File Name and Line Number LoginManager.cpp;2156
CEID Info:
NAME: LCP221
PBX #/CIED: 221
CIED Digits: 2221
Feature DN: 0221
-
Is the hotdesk user trying to login on a phone that is on a different controller than where their hotdesk user is programmed? If so I think your CEID digits may cause a problem. I seem to remember having a remote feature problem with a digit being dropped because the extension length was shorter than the ID. It has been a while so it is a little foggy.
But first is hotdesking enabled on the set they are trying to login on?
-
Yes the user is local to the controller. I have a couple of phones in the surrounding offices that are have hotdesking enabled included hers. I logged into her office with my hotdesking info no problem, tried her got the error message. Came back to my office tried her same error, then logged into my phone without any issues.
By extension number being to short you mean the hotdesking phone extension being 413 possible should 4413? the users extension is 5 digits (52590)?
Thank you for your help
-
Does anyone else have any suggestions?
-
Have you try to reset the password?
-
Sorry for the delay.. yes we have change the password
-
Do you not have conflicts in your feature access codes, where functions are dialed and conflict with internal numbers?
Just a far away thought but who knows.
-
if hers is 52590 and it doesn't work and your does what is your extension number? Is it in the 525xx range. I assume you both have the same COS? If not change hers to yours. Anything else different for this user?
-
Hello,
I'm wondering if there was a resolution to this? I'm having the same issue with one of my sets. I run vMCD and all of my phones are programmed off this one controller. The particular extension that gives me the same error produces this when trying to hot desk in with that extension on multiple phones. I've reset the pin and deleted the ext. multiple times and have built is using multigroup and none multigroup. COS is the same as all of my other sets. I've tried coping working hot desk extensions. All with no luck. My log shows me the following 3 logs associated with my issue.
LoginManager::sHandleLogin() -> on dn(1234),mdn(1234) entry is marked as RegDN, reject the login, send mobilityResp (13) msg
Hot Desk : redirect or update failed for *1190
Hot Desk : Login failed at *1190 - Redirect or update issue
thanks,
-
Try the command :
Gdm check...
Gdm repair...
-
Thanks.
Try the command :
Gdm check...
Gdm repair...
I tried that just now and no luck. I get the same error
-
Whenever I come across this issue of feature failed on hotdesk login, a reboot of the problem phone clears it up.