01-18-2011 10:42 AM - edited 03-14-2019 07:13 AM
Remote site agents are getting the error "Cannot change agent state because the phone is out of service." But the phone is operational. No network changes have occured so this has me confused as these agents were working yesterday. Anyone ever experience this? Thanks in advance.
Solved! Go to Solution.
05-21-2012 08:59 AM
I was experiencing the same issue. Below are the steps that I followed to get it resolved.
Added One Button Login service on the phone
Moved IPCC Extension on button 1 of the phone
(During the course, I also removed/added MAC from the application user)
Hopefully that will help.
Thanks
SH
01-29-2011 03:43 AM
Hi John
This message is coming from Call Manager. A couple of things to try, 1) unassociate and reassociate the device to the RMCM application user in call manager; 2) stop and start all the CTI Manager processes in the CUCM cluster (do not restart). Then start the service one at a time (no particular order).
Thanks
Joe
05-21-2012 08:59 AM
I was experiencing the same issue. Below are the steps that I followed to get it resolved.
Added One Button Login service on the phone
Moved IPCC Extension on button 1 of the phone
(During the course, I also removed/added MAC from the application user)
Hopefully that will help.
Thanks
SH
05-21-2012 09:41 AM
Thanks for the reply and information.!!
08-07-2012 06:33 PM
The Start/Stop of CTI Manager in CUCM worked for me.
Thanks
09-18-2012 08:33 AM
I know this is an OLD post, but we recently had experienced the same issue where only one Agent was getting this error. So I thought I would share how we fixed the issue.
The Agent was able to login but could not "go ready".
When you tried to "Go Ready" this error message below poped-up:
"11:07:27 Resource's Device is Off.
--------------------------------------------
11:07:27 The agent extension is out of service.
Ready state change and call control operations cannot be performed."
The way we resolved this was to: Disassociate the Agent's Device from the main "Application User" --> the "rmuser", save the config, then re-associate the Agent's Device back to the "rmuser" and save the config...
I hope this helps someone, because I was searching all over for a resolution to this...
Thanks,
Matt
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide