I have enabled extended functions, started the service and modified the softkey template and assigned it to ip phones. When I try to use QRT or Callback, i get a message on the phone saying "Service is not Active" and it fails. I have rebooted the callmanager and phones and can't make it work. Any ideas?
Yes. I have tried enabling @ the device pool level and the device level. The softkey shows up on the phone but it does not let me press it. It just says Service is not Active.
Do you have the Callback softkey configured in both the on-hook and ring-out states?
Also, do you have an AD integration? If so you might want to run the password utility to set/reset the CCMSysUser password on all servers in the cluster.
Have you checked DC Directory for a userprofile called CCMSysUser-profile and CCMSysUser-CCNProfile ?
I had the same problem after an upgrade from 3.2(2c) to 3.3(3). I will send you some screen-dumps if the DCD users are missing. This will also give you a problem with EM..
I have the same problem, neither Extension mobility nor the Callback feature seems to work, only difference is that I use active directory instead of DC directory. Do you have some info? Thanx in advance
i have one question, somebody knows how the softkey CallBack works, because it is so important for looking out why doesnt it wants work. OK?
With Callback setup and working, when you dial a DN that is on an active call you will see the softkey Endcall and Callback on the display. If you press the Callback softkey it will then say: Callback is activated on extension XXXXX. Once the far end goes idle your set will give an alerting tone and the display will a Dial softkey that will allow you to dial the original extension again.
Could you post or send me doco on how to check the particular profile. I am getting the same problem going from 3.1.4b to 3.3.3.
Configuring Call Back
Call Back FAQs
Once you have verified that it is configured properly you should also bounce the Tomcat service
I guess I better raise a TAC case because it seems like a lot of people is having the same problem. I find that the problem occurs when I do an upgrade but when I do a new install it is OK.
Did you get an answer and repair for this issue?
Take a look at this proceedure for those using the AD plugin to repair a password issue for those upgrading to 3.3 with the AD plugin:
Look in this link for "Enabling Cisco IP Services"
I was having the same issue with a new install of callmanager 3.3.2 service pack c integrated with AD but I following the instructions in the link that danbaum provided and that fixed it. Thanks for the help!!