TC1110en OmniTouch My Teamwork

Alcatel-Lucent OmniTouch My Teamwork 5.1 and

OmniTouch Automated Message Delivery System Technical Release Notes R5.1.000.586 (ACS 7.1.4b5084) Release R 5.1.000.586 – ACS 7.1.4b5084 Revised Edition 01 – November 2008

Edition 02 – April 2009 Edition 03 – July 2009 Edition 04 – June 2010

Summary Release 5.1 of Alcatel-Lucent OmniTouch MyTeamwork

Conferencing and Collaboration software

Technical Communication TC1110 - Ed 04

OmniTouch MyTeamwork, Technical Release Note R5.1.000.586 Edition 04 – Page 2 Technical Communication TC1110 Copyright © 2007-2008 by Alcatel-Lucent, All rights reserved

Disclaimer This documentation is provided for reference purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this documentation, this documentation is provided “as is” without any warranty whatsoever and to the maximum extent permitted. In the interest of continued product development, Alcatel-Lucent reserves the right to make improvements to this manual and the products it describes at any time without notice or obligation. Copyright Copyright ® 2007-2008 by Alcatel-Lucent. Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder. Distribution of the work or derivative of the work in any standard (paper) book form for commercial purposes is prohibited unless prior permission is obtained from the copyright holder. List of Trademarks Microsoft and Windows are registered trademarks of Microsoft Corporation in the United States and other countries. Pentium is a registered trademark of Intel Corporation. Linux is a registered trademark of Linus Torvalds. Red Hat is a registered trademark of Red Hat, Inc. in the United States and other countries. Lotus and Lotus Notes are registered trademarks of Lotus Development Corporation. Netscape is a registered trademark of Netscape Communications Corporation in the United States and other countries. Sun is a registered trademark of Sun Microsystems. Macintosh is a registered trademark of Apple Computer, Inc. Apache is a registered trademark of The Apache Software Foundation. Citrix is a registered trademark of Citrix Systems, Inc. FLEXlm is a registered trademark of Macrovision Corporation. Sybase is a registered trademark of SYBASE, Inc. All other trademarks and copyrights referred to are the property of their respective owners.


TABLE OF CONTENTS 1 WHAT’S NEW ? 6

1.1 WELCOME 6 1.1.1 Get technical documentation and latest software release 7 1.1.2 Licensing 8 1.1.3 Training and certification 8 1.1.4 Try-and-Buy 8

1.2 HARDWARE CONFIGURATION – MINIMUM REQUIREMENT 9 1.3 NEW FEATURES IN THIS VERSION 9 1.4 FEATURES FROM PREVIOUS VERSIONS 9

1.4.1 IBM Lotus Sametime 8.0 Support 9 1.4.2 Operating System Update 9 1.4.3 New GUI Icons 9 1.4.4 Support for OXE 9.0 9 1.4.5 40 ms outbound packet timing for g.729 codec 10 1.4.6 My Teamwork Mobile Client 10 1.4.7 My Instant Communicator 10 1.4.8 New Language Support: 10 1.4.9 Updated browser list 10 1.4.10 Updated PSTN Board/TDM Network Interface Firmware 10 1.4.11 Counted AMDS License 10 1.4.12 IBM Lotus Sametime 7.5.1 11 1.4.13 Organization Phone Number Management 11 1.4.14 Start / Stop Audio Recording via DTMF 11 1.4.15 ECS Phone Presence Caching 11 1.4.16 Video legs without requiring corresponding audio legs 12 1.4.17 IBM Lotus Notes Email invitations from browser 12 1.4.18 End User Phone List Management 12

1.4.18.1 MyTeamwork Client 12 1.4.18.2 System Admin 12 1.4.18.3 API Support 13

1.4.19 Suppress “User X has left the session” Messages 13 1.4.20 New Alcatel-Lucent Product Branding 13 1.4.21 OEM Partner Requested Enhancements 13 1.4.22 Miscellaneous API Enhancements 14

1.4.22.1 Parallel Audio Leg Creation e15427 14 1.4.22.2 No Phone GUI 14

1.4.23 Call-Back Confirmation 14 1.4.24 Change Nickname 15 1.4.25 Automatic Video Configuration 15 1.4.26 Searchable Help 16 1.4.27 “bypass=on” for Callback with OXE 16 1.4.28 Office 2007 support for Presentations 16 1.4.29 Deprecated Features 16 1.4.30 Document Conversion Backup 17 1.4.31 Partition size changes 17

1.5 FEATURES NOT SUPPORTED 17 1.5.1 Polycom MGC for multipoint video conference 17 1.5.2 My Teamwork running in a Virtual Machine 17

2 THINGS YOU NEED TO KNOW 18 1.6 HARDWARE AND SOFTWARE REQUIREMENTS 18 1.7 SOFTWARE LOCKS OMNIPCX SIDE 18 1.8 UPDATE FROM PRIOR RELEASES 19 1.9 OPERATING SYSTEM UPGRADE – OSU 20 1.10 MAJOR LIMITATIONS AND RESTRICTIONS 20 1.11 KNOWN ISSUES 21 1.12 RESOLVED ISSUES 22


About Release Notes This Release Notes provides installation and operating notes, and any known restrictions/limitations. Release Notes document contains the following chapters: What's New introduces you to OmniTouch My Teamwork, tells you about the new features and enhancements in this release, and points you to further information. Things You Need To Know points you to supported platforms, software environments and other information that you need to know before installing this release. Major limitations And Restrictions describes features limitations and restrictions associated with this release of OmniTouch My Teamwork. You can edit this document in the online version to suit the particular needs of your site. However, if you do edit the contents of this document, it must be strictly for the sole use of users within your organization. You cannot resell or otherwise distribute this documentation, modified or unmodified, to anyone outside your organization. Alcatel assumes no responsibility for the technical accuracy of any modifications made to this documentation. Related documents and filenames in Documentation CD-ROM :

• OmniTouch Advanced Communication Server 5.1 – ACS 7.1.4

• Administration guide 8AL90208USAB

File : 8AL90208USAC_ed01_ACSAdminGuide7_1_4.pdf

• Site Preparation guide 8AL90212USAA

File : 8AL90212USAB_ed01_MyTeamworkSitePrep.pdf

• Installation guide 8AL90213USAA

File : 8AL90213USAB_ed01_MyTeamworkInstallGuide.pdf

• Operator Console

File : Operator_Console.pdf

• Office Communicator Administration Guide

Is now included in Installation Guide.

• Sametime IBM

File : 8AL90229USAA_ed01_MyT_Sametime_UG.pdf

• Teamwork services on IP Touch

File : TC0960en-Ed02_Teamwork_Services_on_IP_Touch_Configuration_Guide.pdf

OmniTouch MyTeamwork, Technical Release Note R5.1.000.586 Edition 04 – Page 5

• OmniTouch Automated Message Delivery System – AMDS

• Administration guide 3BA19628USAC

File : 3BA19628USAD_ed01_AMDSAdminGuide.pdf

• Installation guide 8AL90209USAB

File : 8AL90209USAC_ed01_AMDSInstallGuide.pdf

• Site Preparation guide 8AL90210USAB

File : 8AL90210USAC_ed01_AMDSSitePrep.pdf

History of the document Edition 01 - November 2008 - Creation of document for R5.1.000.574 - ACS7.1.4b4033 Edition 02 - April 2009 - Modification of document for R 5.1.000.582 - ACS 7.1.4b4322 Edition 03 - July 2009 - Modification of document for R 5.1.000.583 - ACS 7.1.4b4520 Edition 04 - June 2010 - Modification of document for R 5.1.000.586 - ACS 7.1.4b5084

Technical Communication TC1110 Copyright © 2007-2008 by Alcatel-Lucent, All rights reserved


1 What’s New ?

1.1 Welcome Welcome to Alcatel-Lucent OmniTouch My Teamwork Release 5.1 Release 5.1 of Alcatel-Lucent OmniTouch My Teamwork is the latest version of the world's leading products for improving conference and Teamwork services across the enterprise.

OmniTouch My Teamwork enables knowledge sharing and collaboration through voice and data conferencing. Through a simple to use Web interface, employees can initiate conferences on the fly or scheduled on a regular basis including audio, data and application sharing. My Teamwork also provides presence information and instant messaging to facilitate effective real-time team communication. To get more information about the product (product descriptions, feature list), please consult the Sales & Marketing section on the Alcatel Business Partner Web Site (BPWS) at URL http://www.businesspartner.alcatel.com/ or see http://www.alcatel-lucent.com/choosemyteamwork .


http://www.businesspartner.alcatel.com/

http://www.alcatel-lucent.com/choosemyteamwork


1.1.1 Get technical documentation and latest software release

Software is available on the Business Partner Web Site at : http://www.businesspartner.alcatel-lucent.com/

• Support Technical Support Telephony Software Download Products Then select OmniTouch My Teamwork And select Release 5.1 Click on Display

You will find the DVD delivery ISO file and its associated MD5 file. You will also find the Upgrade file and its associated MD5 file.

Technical Communications and that Installation manuals are available on the Technical Knowledge Base at : • Support Technical Support Telephony Technical Knowledge Base • Then click on Technical communication and Go (it will open another tab or window)

• Select Product OmniTouch My Teamwork • Select Release 5.1 • Select menu The latest technical communications

Users Guides are also available on the Technical Knowledge Base at : Same link as just above except that you’ll select User guides & Manuals

• Select Product OmniTouch Unified Communication

• Select menu Browse/Reference Book/User Guides

http://www.businesspartner.alcatel-lucent.com/

https://www.technical-knowledge-base.com/km



1.1.2 Licensing Licensing guides are available on the Business Partner Web site at: http://www.businesspartner.alcatel-lucent.com/

• Select Our Offer/eLicensing Offer/eLicensing Management

• Select the corresponding Licensing Guide: in the Related Documents section These guides explain you the mechanism of OmniTouch My Teamwork licenses, how to retrieve licenses files, and how to proceed when re-hosting licences

1.1.3 Training and certification OmniTouch My Teamwork application is a part of the Accredited Premium Business partners portfolio. In order to achieve accreditation on OmniTouch My Teamwork, Business Partners shall complete:

• Lab equipment: lab equipment can be bought according to general lab equipment conditions.

• Post-sales staffing and certification. This certification can be achieved through the training courses described on the BPWS (section Training and Certification).

1.1.4 Try-and-Buy A means for the customer to have an OmniTouch My Teamwork system, right on his premises. Conditions are as follows:

• Free licenses for 10 users, 4 audio and 4 data ports expiring after a period of 1 month. • Optional PBX gateway for non-OXE or pre-OXE 6.0.1 is to be acquired at standard

conditions with no refunding possibility. • Implementation is endorsed by the Alcatel-Lucent Business Partner or by Alcatel-Lucent

Professional Services.

To get a free trial license, click on the following link :






1.2 Hardware configuration – Minimum requirement To support ACS 7.0 or greater, the computer used must support Red Hat Enterprise Server release 4.0 update 6 and must adhere to minimum hardware specifications as appropriate to the number of users and ports purchased. Do not forget to account for growth due to increased demand. Please check minimum requirements in the Site preparation guide or in compliant platforms document. The minimum processor requirement is a dual core 2,8 GHz or faster. This can be checked before upgrade in WebAdmin/Monitoring/System Info, in the part “/proc/cpuinfo” you must have at least 2 processors (0 and 1) or more.

1.3 New features in this version No New features.

1.4 Features from previous versions

1.4.1 IBM Lotus Sametime 8.0 Support The Sametime install executable on the ACS 7.1.4 DVD now allows installation of the My Teamwork for Sametime plugin for Sametime 8.0, in addition to Sametime 7.5.1.

1.4.2 Operating System Update The ACS base operating system is updated to Red Hat Enterprise Linux version 4 Update 6

1.4.3 New GUI Icons All icons visible in the My Teamwork GUI have been updated to be more consistent with those used by the OTUC product.

1.4.4 Support for OXE 9.0 The SIP proxy interface can now use DNS to locate the main and standby OXE CPUs in a Spatially Redundant configuration. ACS now includes Session Timer Support (RFC4028)


1.4.5 40 ms outbound packet timing for g.729 codec The framing to be used for G729 outbound packet timing could be set to 40 ms (default is 20 ms).

In Web Admin, go to Configuration then VOIP Settings :

1.4.6 My Teamwork Mobile Client The Myteamwork Mobile Client Includes support fot Windows Mobile 6.1, new supported devices, and support for European languages.

1.4.7 My Instant Communicator Includes My Instant Communicator 1.7.000.002.

1.4.8 New Language Support: •

• • •

Cantonese (voice prompts only)

1.4.9 Updated browser list

The supported browsers page now list: Internet Explorer 7.0, Firefox 1.6 and later, Windows Vista (with restriction on internal video client).

1.4.10 Updated PSTN Board/TDM Network Interface Firmware

ACS 7.1 includes new firmware for the PSTN Board/TDM Network Interface Module (AudioCodes firmware version 4.6).

If you have this kind of board into your server, please contact the Support Centre and create an eSR to get the exact upgrade procedure that corresponds to your board serial number. New firmware will need to be installed onto your My Teamwork system.

1.4.11 Counted AMDS License

Starting with the release 7.1.0, AMDS licenses will include a user count. This license functions the same as the Mobile Client and MOC counted licenses. When an administrator enables AMDS for a user, the system will verify license availability. If no license is available, an appropriate error message will be displayed.



1.4.12 IBM Lotus Sametime 7.5.1 The ACS 7.1.3 release introduced audio conferencing support for IBM Lotus Sametime 7.5.1, allowing Sametime users to utilize the audio conferencing features of ACS form their existing Sametime environment. This support is implemented as a Sametime plug-in installed on an IBM Domino server. The installation of My Teamwork for IBM Lotus Sametime is described in the Installation Guide of Myteamwork 8AL90213USAB. The installation checklist of this feature is covered in chapter 3 of this document.

1.4.13 Organization Phone Number Management

The previous limit of three phone numbers per organization has been increased to 16, each with an optional display label. Email and Calendar invitations will (optionally) include any additional numbers and their corresponding label. Phone list management is accessed through the Organizations list.

A different prompt set may be configured for each phone number allowing a single Organization to offer multiple prompt sets.

For systems upgraded from previous releases, the exiting Prompt Set setting will be preserved and re-labeled Default Prompt Set. This setting will be used for IVR functions for users in this Organization when placing outbound calls.

Each configured phone number for an Organization may optionally be marked as toll-free. This is required for integration with third party systems such as Microsoft Office Communicator or IBM Lotus Sametime. In those applications, it is expected that a toll free phone number can be distinguished from other numbers. This setting provides a language-neutral toll-free indicator which can be reliably associated with the toll-free field in the third party system.

The MyTeamwork mobile client will be updated to handle the larger list of possible phone numbers.

1.4.14 Start / Stop Audio Recording via DTMF

Starting with this release, the owner of a conference, or another user who joins a conference with a leader code, may start and stop audio recording for a conference that is in progress using the phone number pad (DTMF)

•

•

•

When a conference leader presses the double ## sequence, a new option ?4? will be available. When no recording is in progress, the user can start the recording and when a recording is in progress, the user can stop the recording. This option will not be available if the system does not have a recording license.

1.4.15 ECS Phone Presence Caching

When ACS is configured to receive phone presence via the ECS interface, ACS receives real-time presence updates containing dynamic and static presence details. Starting with this release the ACS presence server will cache the static presence updates. This allows subsequent subscriptions to the ACS presence server to receive this information along with the standard basic presence states (online, offline, busy, etc).


1.4.16 Video legs without requiring corresponding audio legs Previously, the ACS API did not allow the creation of a video leg without first creating a corresponding audio leg. For 7.1, the ACS API will support the creation of video legs without the corresponding audio leg. The MyTeamwork user interface will not provide any GUI for creating this type of video call.

1.4.17 IBM Lotus Notes Email invitations from browser Currently, Lotus Notes does not properly support the HTML mailto: HREF scheme. This has meant that prior to this release, MyTeamwork conference invitations have not contained sufficiently complete details for joining the conference.

Starting with ACS 7.1.0, a user may now select IBM Lotus Notes for all email invitations. A check is made by MyTeamwork to verify that a supported version of Notes is installed. If not found an appropriate error message is displayed. The result will be that Lotus Notes email invitations contain the same info as is currently made available in Microsoft Outlook and other email clients. This feature will work with Notes 6.5 and 7.0. A new user preference is made available to both the end-user and system administrator. Standard organization default processing for user settings and preferences is used.

1.4.18 End User Phone List Management

1.4.18.1 MyTeamwork Client Starting with this release, the MyTeamwork end user web client provides improved management of the end users phone number list. This includes the following:

•

• • •

•

• • • •

•

The phone number list is no longer stored in a machine-specific persistent browser cookie. Phone numbers are now stored in the ACS database. Phone numbers may optionally have a text label. The label can be any string. The user can add, delete and modify phone numbers and their optional text label. Certain phone numbers may be marked with an ?admin? attribute. These numbers will be visible to the end user, and can be selected as the registered phone, but cannot be modified by the end-user. Any number from the phone list may be selected as the current MyTeamwork registered phone number.

1.4.18.2 System Admin The system administration interface is enhanced to allow full management of the user phone list. The User Settings continues to allow specification of the users registered phone. It also provides the link to the page that allows complete management of the user’s phone list. From this page the administrator can specify a number of options:

Create any number of phone number / label pairs Delete numbers from the list Select one number to be the current MyTeamwork registered phone number Specify the type of the phone number. Numbers with the ?User? type may be completely managed by the end-user. Numbers with the ?Admin? type may only be modified by a system or organization administrator. Specify that a number should be ?Presence Monitored?. This option is only available if the system has an ?ECS? license. Further, only ?Admin? type numbers are eligible for


presence monitoring. For this release only one number may be marked for presence monitoring.

The bulk provisioning interface is updated to support phone list management including all parameters specified above.

1.4.18.3 API Support

• • •

The VCS API is updated to support server based phone list management. The ICS API is updated to support server based phone list management. The SIP SERVICE XML interface is updated to support server based phone list management

1.4.19 Suppress “User X has left the session” Messages The MyTeamwork client has a feature where all participants in a session are notified as participants leave the session. When a conference has a large number of participants, the number of “left the session” messages can become excessive to the point of getting in the way of the normal session communications. For this release a new per-conference setting will allow a conference to be scheduled such that these messages will not be shown to session leaders or participants. A run-time accessible toggle will also be provided to allow this feature to be enabled and disabled for any session while it is in progress. Note that use of the run-time toggle will not alter the persistent setting associated with the scheduled conference. This toggle will be added to the People Panel dropdown on the session window.

1.4.20 New Alcatel-Lucent Product Branding Starting with ACS 7.1, the legacy Alcatel logo and colors will be replaced with the new Alcatel-Lucent “infinity” scheme. Also, for the first time ACS and MyTeamwork will include support for a “favicon” icon. For browsers that support this feature, the new Alcatel-Lucent logo will appear in the favorites or bookmark list.

1.4.21 OEM Partner Requested Enhancements For ACS 7.1, there are several enhancements specifically to support our OEM partner base. The list includes:

a) OEM specific SNMP MIB description. MIB to be delivered via OEM partner CD b) OEM-signed ActiveX controls. Unsigned ActiveX cab files will be delivered to OEM, signed,

and then returned to Alcatel-Lucent for inclusion in the master OEM partner CD. c) Via the OEM partner CD, configure the system admin interface such that the User Settings

�Billing Extension field is not displayed. d) Allow up to 17 MGCP Conference Port IP Address Range settings. This is intended to

increase the number of supported MGCP ports to 204 from the current maximum of 96. e) Allow a MyTeamwork session (conference) to be started without any phone related GUI.

Any subsequent session participants would also not see any phone GUI. f) Allow online help to be branded with OEM-specific product name.


g) Set default MGCP RTP Send and Receive ports to 5004 in the OEM partner CD. h) Provide documentation on all ActiveX cab files such that a customer could pre-deploy the

various components to end-user desktops via a system such as Microsoft SMS. Optionally, provide an MSI installer application that installs all Alcatel-Lucent ActiveX controls in one step.

1.4.22 Miscellaneous API Enhancements

1.4.22.1 Parallel Audio Leg Creation e15427 The VCS API will be updated to support inviting multiple audio legs to a call, in parallel, and without any prompt being played to each leg when/if it answers. The conference to which these legs are being added will only be aware (in the conference audio) of the attempt to add the new leg(s) if the leg is successfully added to the conference.

1.4.22.2 No Phone GUI The VCS API is being extended to allow creation of conferences that will not show any telephony related GUI. The VCS API service vcs_conf_schedule has a new parameter, no_audio=true|false. When specified as true, the following GUI will not be available in MyTeamwork:

• • • •

•

• • •

All methods of dial-out (call buttons, phone icons, etc). Call-control (hold, mute, drop). Video control will still be available. Recording, and playing existing recordings into the call. Locking the call.

A conference that has this setting will contain the following in its <options> XML: <no_audio>true</no_audio>

1.4.23 Call-Back Confirmation

This feature is included to address the increasing number of times that voice mailboxes and other inappropriate legs are joined into conferences because of problems with callbacks. When this per-conference option is selected, any time somebody joins the conference by having the system call them back, they are asked to confirm the callback with a DTMF key press. With this feature, a user would not be able to accidentally add a voice mailbox, for example, because the leg is not added to the conference until a live person presses a key.

Callback Confirmation is a user-selectable setting that applies to scheduled and reservationless conferences. The checkbox, which is enabled by default, is called "Confirm callbacks with a keypress", and it is located on the Conference Features tab of the conference details form.

When the setting is checked, confirmations happen in the following situations: double-click a phone icon on the schedule tab click to join page double-click on your own phone icon once inside a web conference.

When the user answers the phone, he or she should hear

"Welcome to the A-L conference center. To join, press 1. To decline, press 2”.

The Callback Confirmation feature will not apply when the phone number being called is of the form “sip:xxxx”. Many SIP devices do not have dial-pads and therefore would not be able to join the conference. Note that if the phone being called happens to be a SIP phone, but is called using a


conventional phone number (e.g. +1-781-895-3600) then the Callback Confirmation feature will be used.

Callback Confirmation is not automatically enabled for conferences created prior to this release. To use this feature for those conferences, end-users should view the Conference Features, check the new option and re-save the conference (press OK).

1.4.24 Change Nickname Starting with the release 7.1, a session leader (call owner or person who joined the conference with a leader access code) can change the nickname (display name) for any session participant(s) that joined the call either by direct inward dial (dial-in) or who were out-dialed by specifying a phone number. The nickname cannot be changed for calls placed to Contacts or Speed-Dials. The feature is accessed through the right-mouse menu after selecting a call participant in the People panel.

1.4.25 Automatic Video Configuration

Deploying and managing video endpoints today is complex and potentially a very error prone process. For many video configurations to be successful, the customer must provide a SIP registrar, a session border controller (SBC), and they must configure those systems to be synchronized with the user configuration of the ACS server. This synchronized management is unavoidable for complex configurations where video users can be on different networks, there are NAT (Network Address Translation) devices or other network boundaries or obstacles to traverse.

A new “automatic video configuration” option is available for environments where the network topology has no internal borders. Automatic Video Configuration can be used when all users are on the same network, meaning that all video endpoints can bi-directionally route SIP and RTP IP traffic directly between users’ desktops. Automatic Video Configuration is also usable when a video MCU is part of the deployment as long as all desktops and the video MCU are on the same network (again, no NAT or other obstacles between the end point and video MCU elements).

When Automatic Video Configuration is selected for a given user, the system will ignore any video end point address or registrar / proxy configuration that may currently be configured. When the user logs into My Teamwork, the system makes note of the IP address of the end user desktop. When a request is made to start video with that user, the SIP dialog is established directly to that IP address, bypassing any registrar or proxy. This applies to both peer to peer and calls involving a video MCU.

When a user is signed in to My Teamwork from more than one location, and automatic video configuration is selected, video calls will be directed to the most recently created My Teamwork session.

Automatic Video Configuration not available when the user is configured for use with an external video client or device.

As part of the implementation for this feature, the Video Conferencing panel in the Tools, Options dialog has been modified to improve usability.


1.4.26 Searchable Help For this release, the online help facility is being enhanced to allow interactive search. Help will be searchable for all language translations.

1.4.27 “bypass=on” for Callback with OXE

When an ACS system is connected to an Alcatel-Lucent OXE PBX via SIP, it is possible to control when calls should forward to voice mail, and when they should not. For example, when someone uses the My Teamwork click-to-join feature, where the system out-dials the user to join a conference, it is desirable to prevent that call from forwarding to voice mail. For this case it is assumed that the user wants to actually join the call and never wants the callback to go to voicemail.

Alternatively, when user A calls user B, user A may in fact want that the call to user B to go to voice mail if user B does not answer or they have forwarded their phone to voicemail. This behavior is controlled by setting the “bypass” parameter in the P-Alcatel-CSBU header in the SIP INVITE sent to OXE. In previous ACS releases the bypass parameter was set to “off” for all calls. With ACS 7.1, the following simple rules are used to determine the bypass setting:

•

•

•

Audio legs created by a call-back (URL or click-to-join in MyTW) to “yourself” will specify “bypass=on” Audio legs created by a call to another user will specify “bypass=off”

Note that the P-Alcatel-CSBU header is only included for calls where the call owner has a “Billing Extension” (aka QMCDU) configured in their user settings. This feature does not apply for any other ACS configuration, including when ACS is connected to an OXE, but TDM is used instead of SIP.

1.4.28 Office 2007 support for Presentations

Prior ACS releases used Microsoft Office 2003 (ACS 7.0.0) or Office 2000 (ACS 6.1.0 and earlier) to perform document conversions for presentations.

Starting with ACS 7.1.0, new installations will use Office 2007. Prior ACS servers that are currently installed with Office 2003 or Office 2000 are still supported.

1.4.29 Deprecated Features

In this release, we are announcing the deprecation of the following features. These features remain supported in the current release, but will be removed in the next major release.

Admin web setting Restrict Users to Organization will be removed.


1.4.30 Document Conversion Backup In the Web Admin, in Configuration / Manual Server Backup, a new option has been added to the list of available backup choices, Backup Document Conversion (only). If this option is selected, then only the contents of the document conversion subsystem are backed up. This operation should be done only after the document conversion system is first installed, or after an installation update or upgrade. During normal server operation, the document conversion system does not change, so there is no need for more frequent backups. Document conversion system backups are never included in automatic (nightly) backups.

1.4.31 Partition size changes On a scratch install, new partition sizes are:

Boot 100 MByte Root 24 GByte /var 16 GByte /swap 1 GByte /slides remaining free space on drive

This change applies only to scratch installs. No change is made on an update. It will avoid to get root partition too small to be able to upgrade the software with tar.gz file (as the upgrade file is untar and unzip in the Root partition).

1.5 Features not supported

1.5.1 Polycom MGC for multipoint video conference Video feature with Polycom MGC MCU is not supported (either in Converged video solution or stand-alone configuration). The Polycom MCU could still appears in the Video Settings of your Web Admin but should not be used anymore.

1.5.2 My Teamwork running in a Virtual Machine Running the My Teamwork ACS/AMDS server into a Virtual Machine into VMWARE for instance is not supported. This kind of configuration has not been validated at all and we could not guarantee the quality of service.


2 Things You Need To Know

1.6 Hardware and software requirements Please refer to the Feature List document that can be found on the Technical Knowledge Base. To get access to the document please browse: Reference Book – Feature List – More Documentation . Concerning server HW platforms supported, please refer to the Technical Communication UC Compliant platforms document, that can be found on the Business Partner Web Site at :

• Home/Support/Technical Support Telephony/Technical Communications/ OmniTouch Unified Communication

1.7 Software locks OmniPCX side For users distributed in a PBX network, following software lock is necessary in OmniPCX Enterprise side. These locks are provided automatically when ordering My Teamwork by the “Sip Bypass” commercial option. Name Lock reference Value SIP gateway 185 1 SIP Networking 188 (n port)


1.8 Update from prior releases

1. Update from any prior 6.x.x releases (updated first to 6.1.0b2982 at least) must be done by booting first on the DVD of the ACS 7.1.3b3855 (option “u” for regular dvd drive or for USB dvd drive options uu1 or uu2). Then you may apply the tarball update (tar.gz) of ACS 7.1.4b5084.

When upgrading 6.1 systems to 7.1, a new license is required for ACS and for VMWARE 5, ask to Support Center via a Service Request.

2. Update from any prior 7.x.x releases must first pass by the ACS 7.1.3b3855 (tar.gz file). Then you may apply the tarball update (tar.gz) of ACS 7.1.4b5084.

When upgrading 7.0 systems to 7.1, you can keep your ACS and VMWARE licenses.

ACS license is made up of a .lic file provided by Support Centre (which is encrypted). VMWARE 5.x license is a text file also provided by Support Centre that can be view and should have the following information : … LicenseVersion = "5.0" …

Upgrades from ACS 6.1 or ACS 7.0 to ACS7.1 continue to use their existing environments, database is translated and all users, conferences and contacts information are kept.

Document conversion tool for presentations of office documents (ppt, doc, xls) is based on MICROSOFT Operating system and Office running into a virtual machine from VMWARE. Microsoft Windows2000 and Office 2000 for ACS 6.1 and priors.

Microsoft Windows XP Pro and Office 2003 for ACS 7.0.

Microsoft Windows XP Pro and Office 2007 for ACS 7.1.

The Microsoft licenses for Windows and Office are not provided with Myteamwork by Alcatel-Lucent and should be ordered separately to Microsoft.

If you upgraded your server from 6.x to 7.1, you still have the old Virtual Machine with Windows 2000 and Office 2000 and you could not load documents from Office 2003 and 2007.

If your server was “scratch” installed (cleaning existing disk partitions) then you must install the Windows XP and Office 2007 to get the “Presentation” feature available for users.



1.9 Operating System Upgrade – OSU A message in the Admin Web page will ask you to upgrade the OS, this will upgrade the OS from Red Hat Linux 4.3 to 4.6. You need to reboot the server on the DVD and ask for option “OSU”.

There will be no data lost but it is still recommended to have a backup of your datas.

The server processor must be at least a dual core processor in order to use the multi-processor mode defined in this new Red Hat 4 Update 6.

1.10 Major Limitations and restrictions

Issues in this section are likely to remain through the life of ACS 7.1.x

18229

Sametime 7.5.1 only: Disconnecting the called party before they answer doesn't disconnect the call:

1. From the Sametime client call the party from the main window 2. In the meeting window, the called party status displayed as "Waiting for the response". While waiting for response, right click on status and try to disconnect the call. Note that call is made even though user tries to end the call.

18542 Sametime: Max length of conference for ACS and Sametime must agree:

In ACS, the default length for a conference is 26 weeks. Sametime’s behavior can be set to match this with the “STScheduleLimitDays” setting in the Notes.ini configuration file.

18584 Sametime cannot reserve ports

If Sametime users schedule meetings, and want to specifically reserve a number of ports, they must use the ACS user interface to modify the meeting.

18612 Sametime only supports ACS default domain

18634 Sametime requires IRP ECS license

19532

Thomson 2030 SIP phones require special configuration This is a defect in the Thomson SIP stack. In a normal ACS configuration, the Thomson 2030 returns error 400 to a SIP invite. Workaround : On the ACS VoIP options page, use payload type 97. This may be resolved in the future if Thomson updates their firmware.

18576

Sametime only users are not able to join the ad-hoc conference If a user who is provisioned ONLY on Sametime (not an ACS user) starts an ad-hoc call with another user who is provisioned in both Sametime and ACS, then the Sametime-only user will never be called. WORKAROUND – for 7.1.3, all Sametime users should also be provisioned in ACS.

18586 Sametime: If user’s “Idle Session Timeout” token has expired and they try to create a meeting, they see a "Meeting not created" message. However, Sametime actually has created the meeting, but ACS has not.

18069 For video conferencing, all servers in a stack must have common video settings. Note that for Scopia MCUs without iView, this means stack size is limited to 4 nodes. Using iView removes this restriction.

http://edialbugs.usa.alcatel.com/show_bug.cgi?id=18229









1.11 Known Issues Issues in this section are expected to have fixes or workarounds in some future release.

18835 The appshare viewer does not work with Mac OS/X 10.4. OS/X 10.5 is OK.

18470

Sametime (7.5.1 only – functions properly in Sametime 8.0): When scheduling a repeating meeting in Sametime, there are actually two (identical) conferences scheduled on ACS. Only one of these two ACS conferences is associated with the Sametime meeting, the other is useless.

18528

Sametime (7.5.1 only – functions properly in Sametime 8.0): Error Scheduling a Sametime meeting with restricted users:

There are two separate issues, both relating to Sametime 7.5.1: 1) When the user tries to schedule a conference with restricted participants, Sametime schedules the meeting but then immediately deletes it. 2) If user has JRE >= 6.0, they may encounter a client hang when scheduling a meeting with restricted participants. To fix this hang, contact customer support and reference this issue number.

18571 Sametime never calls processStartConference, if scheduled conf starts "now"

Schedule a repeating meeting where the first instance of the meeting starts less than ten minutes from now. Sametime shows that the meeting is taking place, but when users try to attend, a dialog box is displayed saying some conference parameters are not set.

18613 Sametime does not enforce ACS "callers are not allowed to un-mute themselves"

19187 Sametime 8 - adhoc conference - join call button grayed out

If anyone leaves an adhoc conference, then attempts to rejoin, if the call fails for any reason, the join button is grayed out, and so the user cannot attempt to re-join.

19188 Sametime 8 - adhoc conference - Unable to mute individual participant

After everyone in an adhoc conference call leaves, the leader and a participant rejoin the call. The leader selects to mute that participant. In this case, the participant is not muted.

19190 Sametime 8 – adhoc conference – multiple failure messages

In an adhoc conference, if any call related error occurs, then the person who initiated the event will see N failure dialogues where N is the number of people in the conference.

19191 Sametime 8 - adhoc conference - Unable to invite user into call

If leader leaves an adhoc conference, and then rejoins, that leader will find the "add person" option is missing from the invite option.

19285 My Teamwork help topics not updated to show the new GUI icons

19357 When “Participants are not allowed to see each other” is set in conference options (“webinar mode”), if a participant starts an application sharing session, then the appshare session, and that participants name, is displayed to all other participants.

19377 Sametime 8 - Participant meeting window displays wrong status

In an ad-hoc call, if some users hang up, and then some smaller number of them re-join, then all users in the conference will see call status "Waiting for response". This message will persist until everyone who left re-joins.

19419 Sametime 8 - desktop client error

In ad-hoc calls, if there is any failure in placing the call, the user will see an error message describing the problem, and also call status "Waiting for response". At this point, from this client, no further calls can be placed to the same user in that conference.

19573 Sametime 8 - "Stop Recording Conference Audio" Menu Item is not enabled

The leader is in a conference that is being recorded. The leader closes the meeting window, then attends the same meeting. The option to "Stop Recording Conference" in the Actions menu is disabled. To stop the recording, the leader must click "Record Conference Audio".






19828 When AppShare leader is using Windows Vista, and stops the appshare, the appshare exe still runs in the background, and viewers see a still image of the last updated leaders frame. Exiting IE will clear the problem.

18721 Mobile client: Smart Minimize on HTC/Mobile 6.0 shuts down application

19258, 19995 Mobile cient: Various problems when ACS server runs in OTUC authentication mode.

19506

Mobile client: Conference owner on PC joins with incorrect privilege if mobile client joins first 1) Web user "user1" creates scheduled conference 'test', but does not join. 2) Mobile user "user2" joins conf web only, either leader or participant code. Result: Web user "user1" sees the conference window opening, but only has participant Privileges.

19576 Mobile client: Conference created while user is logged onto web and mobile are not visible in mobile until after sign-off then sign-on again.

1.12 Resolved Issues

18508 Incorrect invitation text for no-dialout allowed user

20964 Password is not encrypted in upglog for OTUC authentication

22729 Edited meeting repeat info in Sametime is incorrect on ACS

22760 Some users during webinar do not see app sharing across a stack

23060 Stack/timing case can't activate wait for leader call

23136 Invite Contact of Recurring Meeting - Outlook 2007 Displays Wrong Time

23150 THS crash in stack situation

23165 Delete Admin then select Cancel still causes deletion

23437 All Conference Participants hear prompt when remote leg is added.

23439 No MOH for participant connecting via remote site

23479 Unable to start a recording leg when conference is on remote site

23522 crms00193953 MyIC: conf. email invitation isn't created if interface language is RUS

23749 Muxer restarts on stack with 100’s of appshares

24053 ACS SIP REGISTER Registration to Alternate Proxy fails "403 Forbidden"

24709 IVR process grows 6.4MB/hour with call load of 288 legs

24785 MyIC adhoc conference Lotus Notes email Invitations, Create an email fails

25255 Request user CDRs with project code -> window closes itself

End of document

http://bugs-ed.inse.lucent.com/show_bug.cgi?id=18508












https://aww.crms.bsf.alcatel.fr/cqweb/main?schema=Repository&contextid=crms&shortcut=tru&command=GetEntity&entityDefName=CR&entityId=crms00193953






TC1110en OmniTouch My Teamwork

Documents

technical

oem partner

automatic

document conversion

audio legs

ibm lotus

acs presence

callback confirmation