___________________________________________________ Telesnap Release 2011 - Readme File Client/Server Version 7.0 Build 15011 SP0 (C) Copyright 1995 - 2011 Telesnap GmbH All rights reserved. ___________________________________________________ Content ======= 1. Changes compared to version 2009 2. Known Problems and Restrictions 3. Updating earlier versions to Release 2011 1. Changes compared to version 2009 =================================== General: - Provisioning Interface for Snapware Server and Presence Server - Update service with configurable times for planned updates - Presence Server with linestate connections - Notification service for Microsft Exchange for the Presence Server - New TR/87 Interface for the Snapware Server Telesnap Attendant: - Journal Panel - Different colours and sound notifications for the waiting queues - Caller identififcation via BLF Panel - Linestate directly from Presence Server - Save/Restore/Copy layout - Advanced configuration of automatic search - Configuration of attributes for the Details Panel - Send message via - Direct URL's for the Web Panel Snapware: - Snapware status with logged off client - Share caller identification and share calendar information separated - Dynamic teambar via OTD company/department search - Dynamic teambar via telephone groups - Caller identification via WebService 2. Known Problems and Restrictions ================================== The different server components use TCP/IP to communicate with Clients. By default, ports in the range between 5005 to 5080 are used. These settings can be changed when conflicting with other server products. If a Cisco IP Communicator is used on a Snapware server problems can occur in connection with the web administration. With user's name with over 40 characters it comes to problems with the agent's logon to Telesnap ACD. The function callPark of the Cisco Unified CallManager is not supported by the Snapware Client, the PM Operator client and the Telesnap Attendant client. Usage of Extension Mobility on Telesnap Attendant's phone on the Cisco Unified Callmanager is not supported. With the accessibility of three or more Snapware servers to a database or planned database replication the application of a full version of MS SQL Server is required (in the extent of supply not contained), with one or two servers the operation with the provided MS SQL Express is possible. Usage of the same user/device combination for different mandators in a hosted solution environment is not supported. User/device has to be unique in a hosted solution environment. On the server for the Presence Management Media Server there are no active loopback adapters as Network adapter allowed. Be careful with more than one network adapter: PM services query the address of the own system (localhost) for the start of the CTI ports and are registering the CTI ports to the UCCM with this address for the termination of the RTP streams. It must be ensured that this IP address will be kept at any time, also on changing a network adapter during runtime. When using a Cisco Unified Callmanager link and an Innovaphone link on the same Snapware Server, there can occur problems with monitor starts via TAPI. When using the silent installation mode and Lotus Notes integration for the Snapware Client there is a known InstallShield Bug in the produced ISS file for the silent install. In the 'SelectDir' dialogs the result has to be entered manually (Result=1). If the installation of Snapware TAPI Bridge failed on a 64Bit system, please execute the following steps: Step 1: - Open a command line as administrator - Navigate to the windows home directory (for example C:\windows\system32) - Run the command 'FSUTIL RESOURCE SETAUTORESET TRUE C:\' - Reboot the computer Step 2: Run vcredist_x64.exe (can be found under Tools/TAPI on the product CD) as administrator Step 3: Run TSPInstall.exe (can be found under Tools/TAPI on the product CD) as administrator from the command line with command 'TSPInstall add' Step 4: Check the telephony control panel, Snapware TAPI Bridge should be available in the list of TAPI Service Providers (TSPs) Update of Calendar/Presence Server: When a keystore was created due to invalid SSL certificates then please make a backup of this keystore file. To checkif a keystore file was generated you can have a look in the file by searching for an activated parameter like 3. Updating earlier versions to Release 2011 ============================================ If you have version 2007 or 2009 already installed, you can use the update program to update to Release 2011. Versions prior to version 2007 can not be updated to the current version directly. Last update: December 08, 2011 (ss/ab)