Cisco Phone Endpoint Management
Managing Cisco IP telephones often requires a visit to the handset, or at the very least, a request to the user of the handset to perform a sequence of key presses. This is because around 80% of the management of Cisco handsets is through the Call Manager web interface and 20% on the handset itself. It’s the 20% that can cost a great deal of money in terms of time, travel and communications. PhoneView addresses this overhead by providing a way to control multiple (’000s if you so choose) handsets remotely as opposed to clumsy single point single handset remote control tools that attempt to emulate real bulk control – but fail.
In fact PhoneView will remove the need to physically touch the phone, saving travel time and costs, making the management of the Cisco handsets a much easier, more cost effective, proposition.
How PhoneView will save you time and money
Both at the design stage and through actual usage, we’ve identified a number of scenarios that our customers use PhoneView for:
1. Phone background management
2. Extension mobility state management (when upgrading or changing clusters)
3. Phone firmware update management
4. Messaging to users
5. Bulk update of phone settings e.g. CTL/ITL files
6. Device inventory and reporting
7. Remote training and troubleshooting
One of our largest customers got caught out by the ITL situation and found themselves in the very difficult situation of having to delete 52,000 ITL files over a weekend. That is indeed a nightmare scenario for even if you have the ability and the money to get enough people to the right locations to do this task manually, you certainly don’t have enough time over a weekend to do it. Thankfully the customer had invested previously in PhoneView and he was able to delete the ITL files on 52,000 phones in under 4 hours! That’s right 4 hours and in fact they could have done it faster if they had driven the software harder with a faster multi core computer.