___________________________________________________ Telesnap Release 2009 - Readme File Client/Server Version 6.0.27008.2 (C) Copyright 1995 - 2010 Telesnap GmbH All rights reserved. ___________________________________________________ Content ======= 1. Changes compared to version 2009 service pack 1 2. In Release 2009 service pack 2 fixed bugs and problems 3. Changes compared to version 2009 service pack 0 4. In Release 2009 service pack 1 fixed bugs and problems 5. Changes compared to version 2007 6. Known Problems and Restrictions 7. Updating earlier versions to Release 2009 1. Changes compared to version 2009 service pack 1 ================================================== General: - Notifications for administrators via SMTP or event viewer (via Service Manager) - Show profiles in the user configuration also when they are assigned via a group / container - Show only configuration profiles for available licenses - Warning after saving an user without server / PBX profile - Enhanced database profile overview - Deletion of multiple selected users - Enhanced address book profile - „Mark all“ in container configuration - Enhanced configuration of multiple selected users („Products“) - Check for special characters in the hostname at installation - Warning if different link numbers are used after a link was copied Snapware: - Support for Windows 7 - LDAP redundancy for caller identification - Optimzed configuration for fixed entries in the favorites list - Button for preconfigured OTD search - Chat from OTD search - Option to add a phone from the OTD search to the team bar - Button to activate/deactivate fixed call forwarding - Integration of the Exchange hotkey into the hotkey profile - Deletion of user parameters in the configuration overview - Enhanced Lotus Notes / Outlook integration in Citrix environment - Button to change Snapware status - Status with closed team bar available - Controlling PM profiles via Calendar Server - New symbols in Snapware journal - Hide numbers in Snapware journal using wildcard character - Configurable target for a rejected second call Voice Option: - Automatic activation of primary Voice Option Server (if available) - Settings of the statistic can be stored - Different statistics for Telesnap Attendant and Telesnap ACD can be stored (incl. waiting queues configuration) - Statistics can be sent by SMTP automatically Telesnap Attendant: - Support for Windows 7 - Support for Aastra 5000 (via XCAPI) - Automatic call distribution - Conference handling - Phonetic Search - Phone notice with editable subject - Integration of a Web-Panel in the Gui (-> e.g. integration of communale.cc) - Integration of the ASC voice recording like it is in the PM Operator - Connection to Microsoft OCS and Lotus SameTime via Calendar Server - Configuration of attribute display names in directory profile - Configuration of queue display names in PBX profile - New profile Attendant Special Settings Telesnap ACD: - Setting Telesnap ACD agent states via WebAdmin (Pause, NBZ) Telesnap Calendar Server: - Default values for private entries can be configured in the WebAdmin - Default values for all public entries can be configured in the WebAdmin - Cache reset after an access failure (mail box doesn‘t exist any longer etc.) - New connection to Microsoft Exchange via WebServices (Exchange 2007 and 2010) Telesnap UMS: - New connection to mail system via Calendar Server - Deactivation of MWI after mail read/deleted in mail system (only with Calendar Server connection) - WebAdmin user import with user mailbox, optional mail address and Telesnap UMS user - Configuration of Telesnap MTA with Telesnap UMS Setup - Enhanced caching of attachments for multiple-address faxes 2. In Release 2009 service pack 2 fixed bugs and problems ========================================================= General: - If the not redundant DB is running on a separat server and this server is more than 250 seconds unavailable, the DALService will stop unexpectedly - Snapware Server crash after socket connetion problems with a client - Exceptions after sending chat messages - Memory usage of Snapware Server and PM Server increases (memory leaks) - initialization of cascaded links doesn't work in an environment using block configuration - Connection problems of server modules (PM Server, ...) to the Snapware Server in an environment using block configuration - If the Snapware Server ist installed on Windows Server 2008 / Windows Server 2008 R2 the licenses can become invalid after a Server reboot. - WAIT_TIMEOUT in the server trace - DAL Service cannot read the right registry settings on 2003 Server - Linestate problem on Alcatel 4400 / OXE PBX - Problem with the MS Tapi API Version - A problem with a reconnect can occur because the xRefID's are not invalidated, this can cause problems on a monitor restart - User search: Error with the device search - Different E.164 problems - Connection lost between the Snapware Server, PM Server or any other Telesnap Server to the DAL Service because of an missing IsAlive result - SideBySide error in Webadmin on Windows 2008 server / mfc8 dll's - Windows 2008 Server: Pipeline mode now changed to "Classic" by the setup Snapware: - Second register request of a client was aborted (reconnect scenarios) - Problems with extention mobility / shared line - Pause status after Telesnap ACD failover - Hang up calls at Avaya AES - Connected party is unknown after transfer on Alcatel 4400/OXE PBXe - Windows 7 / TAPI bridge (32bit) security issue - SwTAPIMakeCall is now hidden during a makecall request - Improves performance for outlook OTD search - Attention Feature dialog crash - Set forward for Aastra 5000 Voice Option: - JTAPI linestate in a mandator environment with more than 1 JTAPI link - Wrong fallback informations after a screened Transfer - A call which is transfered to a busy device will not be transfered to the configured transfer Target - After activating the Automatic Update for the waiting fields within the Voice Option monitoring and then changing the server, the next update will go back to the previous selected server Telesnap Attendant: - The configuration of the mandator devices is not working properly, only the last mandator device is handled - Display of the originally called number on a fallback is not working properly - Display of the number using the function "wait while busy" is not working properly - Linestate via NeMeX protocol was wrong in a transferred call scenario - Blind transfer to an external number is not working properly (line prefix added twice) - The information value can only be deleted with entering a blank - "Last attendant" message doesn't appear when using the OnDuty/OffDuty button - Client is not switching automatically to the backup server when shutting down the primary Snapware Server - Backup Server informations are missing after a disconnect of the client or with an inactive primary server - A/B panel and queue list are not resetted after a disconnect - Switchback to primary server is not working properly - Client still active in task manager with an inactive primary DAL service - Search failed when following chars are included: "/", "-", "*" and no search for telno was intended - Exception was thrown when AutoSearch is off and was kept in off state while closing the options dialog with Ok or Apply PM Operator: - A wrong memo document is opened sporadically when creating a telephone notice in Lotus Notes. Recipient's address and subject are not set. - If the Operator makes a consultation call -> transfered to voicemail -> hang up the call -> send email then the number of the voicemail instead of the caller is put in the subject. - Using E.164 Prefix from PBX Profil for external/internal recognition - Selecting a private calendar entry during scrolling the calendar entries changes the focus to the date field. - No device status after multiple searches within a very short period of time - Wrong "LastOperator" message when using same queues but different fallback nd park queues - Problem (crash) on an additional server reconnect Telesnap UMS: - MWI is not switched off with no unread voicemails by a VoiceAccess - Problems with attachment shell conversion and x64 support - Voicemail is not recognized in Notes 8 - With one announcement the PGM menu was never entered - Attachments not included in error reports - Integration of several hotfixes in the service pack - Several other problems are fixed 3. Changes compared to version 2009 service pack 0 ================================================== General: - Service Manager for Telesnap services - Current active DAL Service and Database shown in Webadmin - Rename Server in Webadmin - Logged in users shown in user administration - Additional user right for PM monitoring - E.164 support for internal devices - Automated hot fix distribution for Clients - Caching for TAPI line list - Support for Aastra 800 - Support for Windows 2008 Server (32bit and 64bit) for 64bit: - XML Service is not supported - for TAPI interfaces you need a 64 bit TSP - PM Admin capabilities (PM profiles, Voicemail) configurable per user - PM profile directory integration (via LDAP) Snapware: - Improved hotkey profile (hotkeys for OTD search, hang up, alternate call, call transfer,…) - Shared line support for JTAPI - Node prefixes between PBX links configurable in WebAdmin - Activate Snapware client trace via configuration profile - HTTP service for make call requests - Redial button with flyover in teambar - Central configuration for all confirmation dialogs - Show current used Snapware Server in settings dialog - Snapware status available on other servers Voice Option: - License overview for ACD and Attendant licenses in WebAdmin - Improved PM Monitoring (Status of attendants, callingNumber informations for waiting fields) - Search capabilities for workgroups and waiting queues in WebAdmin - W2W (waiting field to workgroup) mapping via WebAdmin - Special targets for holidays Telesnap Attendant: - Attendant Statistics in the WebAdmin - Automatic Reconnect / Failover - Hold call - Chat with Snapware clients (inbound / outbound) - Wait while busy - Direct drop to voicemail - Write access to LDAP information attribute - Sound notification - XML Push / Phone notification - Callback - Last attendant handling - Auto Answer (only calls retrieved from queue) - Dynamic fallback - Fallback on busy - Context menus in search list and BLF - All status informations in search list, BLF and detail view (PAM) - Additional informations via flyover (RUL target, PM Profile, …) - Improved user handling (inactive CallControl buttons, focusing, ...) PM Operator: - Display of called number after a transfer on failed Telesnap ACD: - Statistics now available in Webadmin - Set agent state via context menu in teambar - Improved queue counters for free agents - Permanent agent handling for workgroups Telesnap VoiceMail: - Voicemail synchronisation for Lotus Notes and GroupWise Telesnap UMS: - Support for Aastra 5000 (via SIP and XCAPI) - Support for OpenCom 1000 - 64bit fax driver support - Enhanced voice access menu LDAP: - Current status of import visible in WebAdmin - Manual import/export via WebAdmin 4. In Release 2009 service pack 1 fixed bugs and problems ========================================================= General: - Problems on a link shutdown with more than one JTAPI link - Clients with a corrupt socket connection can't be removed by a new client or by WebAdmin - Problems with extension mobility and removed lines (monitor objects with refId -1 causes problems), server crash after some time - Problems with StartMonitors of specific devices - now StartMonitor of devices with specific prefixes can be rejected - Restoring user data from a DB backup fails - SnapshotDevice / BackInService recursive loop - Problems with active PM Server display in WebAdmin in redundancy mode Voice Option: - Long workgroup numbers (>10) can now be handled correctly - Initialization of voice devices with more than one PM Media Server is not working correctly if one of the PM Media Servers is not running on startup of the PM Server - Server gets inactive in a redundancy environment if the connection to the primary DAL service is lost - PM Media Server crashes (C++ Runtime Exception or without any response), especially in environments with separate PM Media Server - Deleting Holidays/Servicetimes in the webadmin has no effect within the workgroup handling Snapware: - Problems with the CMG PBX socket to synchronize CMG activities with PM profiles - Problems with extention mobility and shared line - Problems OTD Search with umlauts in connection with Lotus Notes - Outofservice events for cascaded Snapware Server link - Notes Telephony Library always returns TS_READY - Problems with PDU file size - Calendar Server: Exchange mailbox couldn't be found in Multiserver Exchange Environment - Calendar Server DAL reconnect Telesnap Attendant: - Problems with line state via NeMex socket PM Operator: - Reconnect for additional servers - Assignment of PM Operator clients to the waiting queues isn't resetted after client socket connection problems - Registered PM Operator Clients can't be seen in the PM Monitoring view in the WebAdmin - PM Operator statistics does not show answered PM Operator calls Telesnap ACD: - ACD Agent state display in PM Monitoring for internal calls Telesnap VoiceMail: - Voicemails are also sent via SMTP if no mail address is configured for the corresponding user Telesnap UMS: - Shrinking of LineManager logs - Priority handling of send requests - Callback number handling for Alcael OXE with SIP / H.323 - Integration of several hotfixes in the service pack - Several other problems are fixed 5. Changes compared to version 2007 =================================== - Calendar integration in the Snapware - OCS integration in the Snapware - New product: Telesnap OCS Gateway - Support for Aastra 5000 - Support for Aastra OpenCom and Ascotel with OIP Server - JTAPI support for Cisco Unified Callmanager - New product: Telesnap Attendant - OTD search via different databases in Snapware - OTD search with line state in Snapware - Enhanced Telesnap ACD counters in the teambar - LDAP web administration - Calendar Server web administration - PM Monitoring in the web administration 6. 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 a PM Operator's or 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). The function MWI in Telesnap UMS is currently not available for the PBX Aastra 5000. 7. Updating earlier versions to Release 2009 ============================================ If you have version 5.0 or 2007 already installed, you can use the update program to update to Release 2009. Versions prior to version 5.0 can not be updated to the current version directly. Last update: March 9, 2010 (ss/ab)