You do need to watch out for the new phone models 89xx & 99xx etc., the URI's are quite different for opening the Setting Page for example. you should refer to the Internal URI Section: If you then goto the Cisco Unified IP Phone Services Application Development Notes for the relevant release, for example UCM 8.5 is: In order to make sure you are following the right information for each UCM version the main page to start from is: I just need to account for our different models and a few uris I had not found yet.
#UNIFIED FX PHONEVIEW DOWNLOAD CODE#
I had some of the uris and some working code already so I know it works in our environment. If you then copy the Macro to notepad you will have a list of all the Internal URI's you need in the right sequence ) If you haven't done so already you should download the free version of PhoneView ( ) and create the relevant macro, it's very quick and easy, there is a demo video here: Another trick is sending **# in a single CiscoIPPhoneExecute object to make sure the buttons are pressed in a timely manor. You also need about a 5 second gap/pause after sending **# as the phone can take a bit of time to unlock and won't be ready for the next key-press. Obviously they are normally locked by default, but if you have a sequence you can send a couple of times that will perform the same steps from the same starting point you should be covered. The main sticking point is usually the unlock of the phone, if you are scripting and you can't see the phone screens, you can't tell if any are locked/un-locked.
Previous message: 'remote controlling phones.'remote controlling phones Stephen Welsh stephen.welsh at
0 kommentar(er)
