ShoreTel

If you are running a ShoreTel System (at least in Germany or Switzerland) and you have some people forwarding calls to external phones like mobile phones and/or land lines. They may not see the incomming caller ID on their external device. They will only see your system default PRI caller ID. This is very bad if these guys miss the call, they cannot call back.

This behavior can be changed since 11.x with a registry hack and since 11.2 it has been integrated much better into the system, but it does not exists by default and leaves you in the rain; if you are not aware of this feature. Until today these settings are not documented in the public.

UPDATE 01/20/2012: We rolled back all below settings, after we have been migrated from Nokia to Siemens EWSD and are now using a Custom Trunk Group Dialing Rule with a value of ;3E only.

In previous 11.x builds this was done by appending a registry hack flip_rnie 0:

Sometimes you may have issues with the ShoreTel Communicator application and you need to find out what's going wrong behind the scenes. And there is a quick solution to extend the logging level. Please keep in mind the log files folder in %APPDATA%\ShoreWare Client\Logs may grow.

Enable debugging in Communicator is done with the following secret keys strokes:

1. Focus curser in Enter you name or number field, where you normally enter the numbers for dialing
2. Hold CTRL down and press F12
3. A window opens with several debugging options.
4. Enable what you need and close. Disable after you finished debugging.

The feature Make Number Private better known as CLIR in ShoreTel PBX is not working out of the box in Germany / Europe on ISDN and PRI lines. You can solve this by altering the Trunk Group Dialing Rules of your ShoreTel system.

Sometimes you may be in the situation that a ShoreTel phone may be unresponsible or does not connect to the headquater server. You may receive messages on phone display like "No service" or "Cannot connect to..." or the phone completly 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 powercycle 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:

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