ShoreTel Call Manager not connecting87
Pages:
1
|
LiquidLayer private msg quote post Address this user | |
| sergeant_kyle Junior Member Join Date: Jun 2009 Location: Twin Cities, MN Posts: 12 permalink I actually ran into this problem again when we were installing a new Terminal Server and we were able to see all the voicemails and call history and everything even though it said that 'Phone Disconnected - Line not in service' and when we did the 'CTRL + F12' the CSIS Status says it is healthy. The problem is not with the CSIS, it is with the TAPI connection back to the ShoreWare Director server. Here is how we resolved the problem: Check the ShoreTel Remote TAPI Service Provider: 1. Go to the control panel and open up the 'Phone and Modem Options' 2. Click on the 'Advanced' tab 3. Highlight the 'ShoreTel Remote TAPI Service Provider' from the list 4. Click the 'Configure' button to check the settings and if in the 'Provider Status' window it says anything about an error it needs to be deleted and recreated Remove the ShoreTel Remote TAPI Service Provider: 1. Go to the control panel and open up the 'Phone and Modem Options' 2. Click on the 'Advanced' tab 3. Highlight the 'ShoreTel Remote TAPI Service Provider' from the list 4. Click the 'Remove' button Add the ShoreTel Remote TAPI Service Provider: 1. Go to the control panel and open up the 'Phone and Modem Options' 2. Click on the 'Advanced' tab 3. Click the 'Add' button 4. Highlight the 'ShoreTel Remote TAPI Service Provider' from the list 5. Check the 'Application Server' checkbox 6. Enter <ip address of the Shoreware Director Server> in the 'Server:' field 7. Enter <ShoreTel> in the 'Login:' feild 8. Leave the rest blank and then click 'Apply' and 'OK' This was on a Windows Server 2003 R2 with Service Pack 2 set up as a Terminal Server but im sure that this would be the same fore the Windows XP. This should solve the problem that was described above. Best, __________________ Kyle E. Dille Communication Support Specialist Semper Fidelis Memorial Blood Centers, It’s About Life! Integrity - Respect - Synergy - Service - Excellence Source: ShoreTelForums.com (HC) HostCheetah.com  |
||
| Post 1 • IP flag post | ||
|
|
LiquidLayer private msg quote post Address this user | |
| HostCheetah If you have ever had a certain computer on your LAN suddenly stop talking to your ShoreTel phone, and you get a little phone with a red X on the call manager, it's irritating as heck to fix. At first we had to wipe the computer, and then found out that system restore also fixed this issue. Now, however, we learned how to go straight to the problem (the ShoreTel TAPI connector) and fix it in 5-10 minutes. Here's how: 1.) Exit the call manager. Make sure that CSISCMGR.exe has exited appropriately. 2.) Open Phone and Modems under the control panel and click on the Advanced Tab (you may have to enter an area code before you get the phone and modem dialog box) 3.) Open the Shoretel Remote TAPI Service Provider entry and disable the hardware. Save and close and go back in and enable it Fix? 4.) If not, delete/remove the Shoretel Remote Tapi entry. 5.) Uninstall the shoretel call manger in Add/Remove programs (Programs in Vista and Windows 7). 6.) Reinstall from http://[your shoretel server]/shorewaredirector/clientinstall. I don't typically reboot between uninstalling and reinstalling the client, but you can if you want. |
||
| Post 2 • IP flag post | ||
|
methylbromid private msg quote post Address this user | |
| If reinstalling does not fix (it did not for me), I modified the last set of instructions as follows: Because I had tried to uninstall/reinstall, I now had two instances of the Shoretel TAPI entry. I removed one and modified the properties of the other. For the one I was modifying, I manually input the server name, username, and password in the TAPI config. I restarted the Shoretel software and it worked perfectly. |
||
| Post 3 • IP flag post | ||
|
|
LiquidLayer private msg quote post Address this user | |
| Here is another user with a modified fix / this may work if the OP solution does not: Source URL: http://devdontech.wordpress.com/2013/02/05/shoretel-phone-disconnected/ Shoretel Phone disconnected I was looking for a solution to why my ShoreTel Communicator was showing Phone Disconnected, yet everything about the software worked fine. I found the below on https://community.hostcheetah.com/thread/87 and modified it a bit for my needs. We were able to see all the voicemails and call history and everything even though it said that ‘Phone Disconnected – Line not in service’ Here is how we resolved the problem: Check the ShoreTel Remote TAPI Service Provider: 1. Go to the control panel and open up the ‘Phone and Modem Options’ 2. Click on the ‘Advanced’ tab 3. Highlight the ‘ShoreTel Remote TAPI Service Provider’ from the list 4. Click the ‘Configure’ button to check the settings and if in the ‘Provider Status’ window it says anything about an error it needs to be deleted and recreated Remove the ShoreTel Remote TAPI Service Provider: 1. Go to the control panel and open up the ‘Phone and Modem Options’ 2. Click on the ‘Advanced’ tab 3. Highlight the ‘ShoreTel Remote TAPI Service Provider’ from the list 4. Click the ‘Remove’ button Add the ShoreTel Remote TAPI Service Provider: 1. Go to the control panel and open up the ‘Phone and Modem Options’ 2. Click on the ‘Advanced’ tab 3. Click the ‘Add’ button 4. Highlight the ‘ShoreTel Remote TAPI Service Provider’ from the list 5. Check the ‘Application Server’ checkbox 6. Enter <ip address of the Shoreware Director Server> in the ‘Server:’ field 7. Enter <ShoreTel Login ID> in the ‘Login:’ field 8. Leave the rest blank and then click ‘Apply’ and ‘OK’ This worked for me on a Windows 7 PC. Visit the source URL here to see if there are current updates to the above: Source URL: http://devdontech.wordpress.com/2013/02/05/shoretel-phone-disconnected/ |
||
| Post 4 • IP flag post | ||
|
|
LiquidLayer private msg quote post Address this user | |
| * Traceback on ShoreTelForums.com www.ShoretelForums.com Post by Keithmurphy: Upgrade to 13.x, they dropped TAPI and used CAS instead. I've found it to be 100 times more reliable for remote softphones. |
||
| Post 5 • IP flag post | ||
|
|
Austregisel private msg quote post Address this user | |
| Hello, First post here! LiquidLayer, I have a Server 2008R2 ENT Terminal Server and had an issue where no matter who logs onto the Server and try to use the Shoretel Communicator, it would not connect to their phones. The steps provided you worked, Thank you! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Remove the ShoreTel Remote TAPI Service Provider: 1. Go to the control panel and open up the ‘Phone and Modem Options’ 2. Click on the ‘Advanced’ tab 3. Highlight the ‘ShoreTel Remote TAPI Service Provider’ from the list 4. Click the ‘Remove’ button Add the ShoreTel Remote TAPI Service Provider: 1. Go to the control panel and open up the ‘Phone and Modem Options’ 2. Click on the ‘Advanced’ tab 3. Click the ‘Add’ button 4. Highlight the ‘ShoreTel Remote TAPI Service Provider’ from the list 5. Check the ‘Application Server’ checkbox 6. Enter <ip address of the Shoreware Director Server> in the ‘Server:’ field 7. Enter <ShoreTel Login ID> in the ‘Login:’ field 8. Leave the rest blank and then click ‘Apply’ and ‘OK’ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Austregisel~ Systems Administrator - DGSI |
||
| Post 6 • IP flag post | ||
Pages:
1
