Re: Changing ring types not possible: "Ringer is Busy !" message
We just ran into the same problem. We have 3.2(2a) on one cluster and 3.2(2c) on another. Both clusters had the same problem. The bad phone load is P00303020204. Cisco sent us P00303020205, but it caused other problems, such as long delays with retrieving ringer files (+10 secs) and down-grading back to 204 was causing a bunch of TFTP errors and was taking 15 minutes to reboot. Cisco sent us P00303020100 and it has corrected the "Ringer is Busy" problem and so far is working good with 3.2. I think the 100 load is from 3.2(1).
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...