Sometimes you may be in the situation that a ShoreTel phone may be unresponsive or does not connect to the headquarter server. You may receive messages on phone display like No service or Cannot connect to... or the phone completely hangs (and power off/on does not solve your issue) or similar issues. This could happen because of reboot failures or firmware loading issues if you may have unplugged the phone while it have booted up and such issues or if there are firmware bugs. Often it helps to power-cycle the phone again, but if this does not help you can reset the device. We have seen this in rare situations, but here is a way how to solve this issue.

Follow this step-by-step instruction and the phone is starting from scratch:

Sometimes you may need to develop custom tracking code for Google Analytics. If you sit in front of your development machine and the development or testing site you are using is localhost you will run into the problem that you don't see a tracking event firing to Google.

So you may ask you how to test the code without going into production? There are several options...

This article describes how you can setup a proxy server on an existing Microsoft IIS Server in your company to tunnel the ShoreTel Communicator for iPhone App calls to your internal ShoreTel server. ShoreTel was so kind to document this with Apache, but not with IIS. If you do not like to run Apache as an extra instance in your company only for the ShoreTel App you can follow this document and save your time as this solution is really easy to implement.

Installation