as you can see, using a multicast address, and all the phones belongs to the same paging group.
The strange behaviour I get is that not all phones switch on the speaker when number 899 is dialed and it happens randomly, but if I press speaker button on a phone that doesn't play the message, after pressed, it play the message.
I think that multicast is configured correctly, and I don't think there are limits of ip phones while using multicast.
For the ones that are still looking for a workaround. This one worked for us:
CME phone does not enable speakerphone during paging after a hooklatch, Fixed CSCtw61625 Symptom: CME IP phones may fail to auto-enable the speakerphone during a page. Conditions: The issue occurs on IP phone firmware 9.2(1) and above. Workaround: Either of the following workarounds applies: a) Run firmware 9.1(1)SR1 or lower. or b) Hit any button on the IP phone after using the phone's handset or toggling the phone's hook latch. See 'Additional Details' for more information on this workaround. Additional Details: When the hook latch for the phone handset is toggled, the phone enters a bad state where speakerphone won't illuminate. Anytime after the hooklatch is used (i.e. the handset is picked up off the cradle), the user needs to hit any button on the IP phone (i.e. keypad digit, settings, NewCall softkey, etc.) to return the phone to a state where speakerphone auto-enables on page.
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...