Last Change: 13.12.10
--------------------------------------------------------------------------------------------

During installation or operation of HiPath TAPI 170 V2.0 the following 
Windows problems can occur:


General
========

Info:       Operation of Tapi 170 via IP-Interface is not released for Hicom 150 E
            Office Rel. 2.2.

--------------------------------------------------------------------------------------------

Problem:    The application doesn't recognize the installed TAPI lines.
            The TSP product name was changed. In case of using a wrong product name
            and not the Global Unique ID for identification the lines are not recognized.

Solution:   Application should use the Extension ID to search for lines of the TSP.
 
            GUID:      lineNegotiateAPIVersion
                       APIVersion=x10004
                       extID.ID0=x3ab39627, .ID1=x9fa111d3, .ID2=xbd250050, .ID3=x46786eb, 

--------------------------------------------------------------------------------------------
09.02.09

Problem:  MULAP on HOOME doesn't go in Service

Solution: opposed to HiPath 3000 on HiPath OpenOffice ME you must not enter the station number of a MULAP member,
          but need to enter the number of the MULAP itself in the TSP lines configuration.

--------------------------------------------------------------------------------------------
18.11.08

Problem: CMDService.exe from HiPath TAPI 120/170 is wrongly detected as Spyware

Currently there exists a spyware program named CMDService.exe.
Due to improper signature programming some virus/spyware scanners do not detect only this malware file but also the file of the CSTA Message Dispatchers (CMD) with the same name as spyware.

In such cases prior to any action of the virus/spyware scanner it is required to check whether it is about the CSTA Message Dispatcher file or in fact the malware file.

The file of CSTA Message Dispatcher is named:
CMDService.exe

is by default located in directory
c:\Windows\system32\

and is related to the files:
CMDUI.cpl 
VulkanClient.mdb 

In case of any doubt the newest signature file for the virus/spyware scanner or additionally a different scanner has to be used.

--------------------------------------------------------------------------------------------


for Windows NT
==============

--------------------------------------------------------------------------------------------
Problem:    No available lines when RAS is activ

Solution:   (see also TAPI 2.1 readme)
If Remote Access Service (RAS) is installed on a telephony client 
that has RAS autodial enabled, TAPI applications will not have access 
to lines on the telephony server. The work around is to set the startup 
value for the telephony client's Remote Access Autodial Manager service 
to Manual. 
Please note that the same problem will occur anyway if an application
starts RAS automatically.

--------------------------------------------------------------------------------------------
Problem:    TCMSETUP for telephony server does not work

Solution:   (see also TAPI 2.1 readme)
In some configuration there can be a problem to setup the telephony
server via TCMSETUP. In this cases it will be necessary after TCMSETUP 
to correct the login to an vaild domain-administrator account for
the telephony service. Or the complete entries can be done using the
following steps:
manually with the control panel.

Control Panel\Services: Telephony Service
	Set to "Auto" startup and
        "Logon As:" to be the administrator you would 
           have specified on the command line for TCMSETUP /S ...

Create a new "Server" key under 
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Telephony" 
and ther assign the value "tsec.dll" to the new entry "MapperDLL" (String).

--------------------------------------------------------------------------------------------


For Windows 2000
================

--------------------------------------------------------------------------------------------
12.09.05
Problem:   No access to Windows 2000 Telephony Server via Remote TSP after installation 
of "Update Rollup 1 for Windows 2000 SP4" on the server:

This problem can be solved as follows:

  Windows XP Clients:
	Windows XP Clients has to be updated to SP2 (recommended).

  Windows 2000 Clients
	Installation of "Update Rollup 1 for Windows 2000 SP4" also on  
 	Windows 2000 Clients (recommended).

Alternatively the higher security settings on the server can be reduced, by setting the following registry key:
	[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Telephony\Server]
		"HighSecurity"=dword:00000000 
  You may edit the registry key manually or import the file W2000TAPIPatch.reg, which can be found at 
           MS\W2000_Hotfixes\w2000_serverpatch on this CD.

Separate installation of hotfixes KB824692 is not longer neccessarry.
The hotfixes of KB824692 has been removed from this CD.

--------------------------------------------------------------------------------------------


For Windows 2003
================

--------------------------------------------------------------------------------------------
20.02.04 (new 12.09.05)
Problem:   No access to Windows 2003 Telephony Server via Remote TSP:

In Windows 2003 Server higher security mechanism are activ by default. This causes that 
TAPI Clients cannot access their assigned lines. 

This problem can be solved as follows:

  Windows XP Clients:
	Windows XP Clients has to be updated to SP2 (recommended).

  Windows 2000 Clients
	Installation of "Update Rollup 1 for Windows 2000 SP4" on  
 	Windows 2000 Clients (recommended).

Alternatively the higher security settings on the server can be reduced, by setting the following registry key:
	[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Telephony\Server]
		"HighSecurity"=dword:00000000 
  You may edit the registry key manually or import the file W2003TAPIPatch.reg, which can be found at 
           MS\W2003_Hotfixes\w2003_serverpatch on this CD.

Separate installation of hotfixes KB824692 is not longer neccessarry.
The hotfixes of KB824692 has been removed from this CD.

--------------------------------------------------------------------------------------------


For Windows XP/SP2 (and above)
==============================

--------------------------------------------------------------------------------------------
09.02.09
Problem:   The telephony client cannot communicate with the telephony server in Windows XP Service Pack 2 (and above):

This problem occurs because the remote telephony service provider
(TSP), such as the Remote TSP (Remotesp.tsp) component, uses a remote
procedure call (RPC) for communication between the telephony client and
the telephony server. By default, Windows Firewall in Windows XP SP2(and above)
blocks the RPC port.

This problem can be solved as follows:

Either disabling XP/SP2(and above) firewall completely on all clients or
TCP Port 251 needs to be enabled as a Windows-Firewall Exception for Remotesp, either manually via control panel (on all XP/SP2(and above) clients) or preferable via group policy on the domain-controller, e.g like this:
On a Windows Server 2003:
- Administrative Tools / Active Directory Users and Computers
- Properties <your DOMAIN>
- Tab "Group Policy"
- New: "Remotesp"
- Options "Remotesp": No Override
- Properties "Remotesp": Disable User Configuration settings
- Edit "Remotesp": Computer Configuration / Administrative Templates / Network / Network Connections / Windows Firewall / Domain Profile
- Setting "Windows Firewall: Define port exception": Enable, Show / Add... / Add Item / Enter the item to be added: 251:TCP:localsubnet:enabled:Remotesp
- Leave the dialogs, with OK confirmation if required
- Run gpupdate.exe to ensure the new GPO is ready for replication
On a Windows Server 2008:
- Administrative Tools / Group Policies
- Open tree <your DOMAIN>
- Right mouse button <your DOMAIN>: Create new Group Policy Object ...
- Name: "Remotesp", OK
- Right mouse button "Remotesp": Forced / No Override
- Right mouse button "Remotesp": Edit...
- Open tree "Computer Configuration / Administrative Templates / Network / Network Connections / Windows Firewall / Domain Profile"
- Properties of Setting "Windows-Firewall: Define Incoming Port Exception": Enable, Show... / Add... / Enter the item to be added: 251:TCP:localsubnet:enabled:Remotesp
- Leave the dialogs, with OK confirmation if required
- Run gpupdate.exe to ensure the new GPO is ready for replication
After enrollment of this group policy on reboot of all clients the issue is reliable solved because no client can accidently change the setting.
This GPO may be combined with the one from the next section (only the Setting "Windows Firewall: ..." and the name are different).

--------------------------------------------------------------------------------------------
09.02.09
Problem:   Delays (upto several minutes) in MS TAPI Client/Server environment via Remote TSP:

This problem is caused by the XP/SP2(and above) firewall being left enabled with its default settings.
Attention: if the firewall is enabled on only one XP/SP2(and above) client then all clients and the server are encountering these delays!!!

This problem can be solved as follows:

Either disabling XP/SP2(and above) firewall completely on all clients or
File and Printer Sharing needs to be enabled as a Windows-Firewall Exception, either manually via control panel (on all XP/SP2(and above) clients) or preferable via group policy on the domain-controller, e.g like this:
On a Windows Server 2003:
- Administrative Tools / Active Directory Users and Computers
- Properties <your DOMAIN>
- Tab "Group Policy"
- New: "File and Printer Sharing"
- Options "File and Printer Sharingt": No Override
- Properties "File and Printer Sharing": Disable User Configuration settings
- Edit "File and Printer Sharing": Computer Configuration / Administrative Templates / Network / Network Connections / Windows Firewall / Domain Profile
- Setting "Windows Firewall: Allow file and printer sharing exception": Enable, localsubnet
- Leave the dialogs, with OK confirmation if required
- Run gpupdate.exe to ensure the new GPO is ready for replication
On a Windows Server 2008:
- Administrative Tools / Group Policies
- Open tree <your DOMAIN>
- Right mouse button <your DOMAIN>: Create new Group Policy Object ...
- Name: "File and Printer Sharing", OK
- Right mouse button "File and Printer Sharing": Forced / No Override
- Right mouse button "File and Printer Sharing": Edit...
- Open tree "Computer Configuration / Administrative Templates / Network / Network Connections / Windows Firewall / Domain Profile"
- Properties of Setting "Windows-Firewall: Allow Incoming Exception for File and Printer Sharing": Enable, localsubnet
- Leave the dialogs, with OK confirmation if required
- Run gpupdate.exe to ensure the new GPO is ready for replication
After enrollment of this group policy on reboot of all clients the issue is reliable solved because no client can accidently change the setting.
This GPO may be combined with the one from the previous section (only the Setting "Windows Firewall: ..." and the name are different).

--------------------------------------------------------------------------------------------
08.12.05
Problem:   lineForward() with a non-empty destination address doesn't work via Remote TSP on the client:

on the client you get a locally generated LINEERR_INVALPARAM.

Currently there is no hotfix from MS available.

A workaround may be the usage of HT120 on the clients.

--------------------------------------------------------------------------------------------


For Windows Vista
==================

--------------------------------------------------------------------------------------------
09.02.09

Problem:   The telephony client cannot communicate with the telephony server in Windows Vista:

See the solution described under XP/SP2(and above).

--------------------------------------------------------------------------------------------
09.02.09
Problem:   Delays (upto several minutes) in MS TAPI Client/Server environment via Remote TSP:

See the solution described under XP/SP2(and above).

--------------------------------------------------------------------------------------------
23.11.07

Vista (apart from Home editions) is supported by HiPath TAPI 120/170 beginning with V2 R0.55.0.
Please note the following requirements / restrictions.

--------------------------------------------------------------------------------------------
23.11.07

DebugSpy doesn't work under Vista

The current version of DebugSpy doesn't capture OutputDebugString on Vista.

As a workaround you can use the latest version of DebugView (DbgView.exe) from MS / SysInternals:
http://www.microsoft.com/technet/sysinternals/Miscellaneous/DebugView.mspx
It is required to start it with "Run as administrator" and then to enable on its
menu / Capture / Capture Global Win32.

--------------------------------------------------------------------------------------------
19.02.08

HiPath TAPI 120 Setup cannot be re-configured under Vista

If you have only the TSP installed on a PC and want to re-configure this by adding the CMD via Setup, then this won't work.
Instead you first need to remove the TSP installation and then re-install the TSP along with the CMD.

--------------------------------------------------------------------------------------------


For Windows 7
==================

--------------------------------------------------------------------------------------------
09.02.09

Problem:   The telephony client cannot communicate with the telephony server in Windows 7:

See the solution described under XP/SP2(and above).

--------------------------------------------------------------------------------------------
09.02.09
Problem:   Delays (upto several minutes) in MS TAPI Client/Server environment via Remote TSP:

See the solution described under XP/SP2(and above).

--------------------------------------------------------------------------------------------
12.02.10

Windows 7 (apart from Home editions) is supported by HiPath TAPI 120/170 beginning with V2 R0.63.0.
Please note the following requirements / restrictions.

--------------------------------------------------------------------------------------------
23.11.07

DebugSpy doesn't work under Windows 7

The current version of DebugSpy doesn't capture OutputDebugString on Windows 7.

As a workaround you can use the latest version of DebugView (DbgView.exe) from MS / SysInternals:
http://www.microsoft.com/technet/sysinternals/Miscellaneous/DebugView.mspx
It is required to start it with "Run as administrator" and then to enable on its
menu / Capture / Capture Global Win32.

--------------------------------------------------------------------------------------------
19.02.08

HiPath TAPI 120 Setup cannot be re-configured under Windows 7

If you have only the TSP installed on a PC and want to re-configure this by adding the CMD via Setup, then this won't work.
Instead you first need to remove the TSP installation and then re-install the TSP along with the CMD.

--------------------------------------------------------------------------------------------
27.10.10

CMD and Firewall - Windows 7:
Windows-Firewall is usually activated on Windows 7 PC's. TAPI 120 clients will therefore not be able to access CMD after
CMD installation and configuration.
 The Windows Firewall can be configured for CMD as described below:
- "Control Panel\All Control Panel Items\Windows Firewall\Allowed Programs:"
- Button: <Change settings> and then <Allow another program...>
- select the CMD Service Modul: "C:\Windows\System32\CMDService.exe" with  <Browse...> button and <Add> the program to list

--------------------------------------------------------------------------------------------


For Windows Server 2008
========================

--------------------------------------------------------------------------------------------
26.01.09

To get the telephony server/service to work with a domain-admin/admin account on a Windows Server 2008,
it is required to assign two additional user rights to the corresponding user account manually:

On a Domain Controller:
- Run gpme.msc (former dcpol.msc)
- Select tab "All"
- Select "Default Domain Controllers Policy", click OK
- Open tree: "Computer Configuration/Policies/Windows Settings/Security Settings/Local Policies/User Rights Assignment"
- Double click policy "Replace a process level token" and add corresponding user
- Double click policy "Generate security audits" and add corresponding user

On a Server, that isn't a Domain Controller:
- Run secpol.msc
- Open tree: "Security Settings/Local Policies/User Rights Assignment"
- Double click policy "Replace a process level token" and add corresponding user
- Double click policy "Generate security audits" and add corresponding user

--------------------------------------------------------------------------------------------

For 64 bit Windows (CMD only)
=============================

--------------------------------------------------------------------------------------------
13.12.09

Problem:    1. TAPI 170 cannot be installed on 64 Bit Windows,
               if there is already MS-Office 32 Bit installed.
	    2. After installation of TAPI 170 on a 64-Bit Windows it is not possible
               to install MS-office in 32 Bit Version.

Solution:   Both products are based on usage of "Microsoft Access database engine". 
            Microsoft does not support installation of 32-Bit and 64-Bit variant of "Microsoft Access database engine" in parallel. 
            On a 64-Bit TAPI 170 machine only MS-Office 64-Bit Version can be installed. 


