Cisco Mobility still calls Cell phone after being deleted

[CompuTron2013]

Hi Everyone,

I'm new to the forums.

We are still running Cisco Call Manager v6.0.1.2000-3. I had a user that allowed his cell phone to ring at the same time
as his desk phone. This way he could take calls after hours, etc.

In order to turn this off, we usually just go to the user's Remote Destination, and un-check the associated line(s).

When we uncheck the line, the calls still make it to the cell phone. We then tried a dummy # for the cell phone, but it still made it to his cell. The next step was to delete the Remote Destination AND the Remote Destination Profile. Deleting those items did not work either. We had absolutely no remote destination for the user, and the cell phone still rings. Right now, I have recreated both the Remote Destination AND the Remote Destination Profile. There are no dependencies for the Remote Destination, no call forwards, and no translation patterns.

Has anyone seen this before?

 

[whykap]

Have you checked to make sure the phone is not forwarded to the cell phone?
Other than that, and assuming that you have properly deleted his mobility profile you could be running into a db sync issue or a 6.0 bug or both.

 

[MitelInMyBlood]

What happens if the affected user places a call from his cell phone to one of the D-I-D extensions on the call manager? What CallerID is seen? Is it the full 7 (0r 10) digits of the cell number or do you instead see the internal extension of the calling user (as you would if Mobility was still active)??

If you still see the 4 digit user's extn displayed after all you've done to delete the RDP and extension association, then I'm with Whykap's suggestion that there is possible database corruption. As much as I'd rather have my gums scraped than open a TAC case, that may be your best option. With possible DB corruption, the one thing I would not do is reboot the call manager unless TAC tells you to.

Do you have RTMT running and are you familiar with how to check it for system alarms?
Do you know how to look at your CDR records & if so have you checked there to see what's happening with the call flow? Raw CDR is a little cryptic to look at, but I'm thinking that CDR would show the call boncing off a forwarded extn if that was the case.

If all else fails and your system is out of support, then as a last resort try completely deleting the user out of CUCM and then rebuild him from scratch.

Original MUG/NAMU Charter Member