OmniTouch Automated Message Delivery ... - alcatel …alcatel-lucent.de/enterprise/ipush/ipush88/TC1327en_OmniTouch_My... · Alcatel-Lucent OmniTouch My Teamwork 6.0 ... improvements

Alcatel-Lucent OmniTouch My Teamwork 6.0 and

OmniTouch Automated Message Delivery System Technical Release Notes R6.1.000.102.a (ACS 8.1.0b5225) Release R 6.1.000.102.a – ACS 8.1.0b5225 Revised Edition 03 – 26 July 2010 Summary Release 6.1 of Alcatel-Lucent OmniTouch MyTeamwork

Conferencing and Collaboration software

Technical Communication TC1327 – Ed 03

OmniTouch MyTeamwork, Technical Release Note R6.1.000.102.a Edition 03 – Page 2

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.

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


TABLE OF CONTENTS

1 - WHAT’S NEW ? 6

1.1 - GET TECHNICAL DOCUMENTATION AND LATEST SOFTWARE RELEASE 7 1.2 - LICENSING 9 1.3 - TRAINING AND CERTIFICATION 9 1.4 - TRY-AND-BUY 9 1.5 - HARDWARE CONFIGURATION – MINIMUM REQUIREMENT 9 1.6 - NEW FEATURES COMING WITH THE ACS 8.1 VERSION 10

1.6.1 - Language Support 10 1.6.2 - Embedded Operating System (documents conversion) 10 1.6.3 - Supported Desktop OS and Browsers 10 1.6.4 - New Video features 10

1.6.4.1 - Remote Audio Mixing with Radvision Video MCU 10 1.6.4.2 - Client Profiles 10 1.6.4.3 - Video for Anonymous Users 11 1.6.4.4 - Secondary Video MCU 11 1.6.4.5 - Real-time Audio/Video Client Statistics 12

1.6.5 - QOS Support 12 1.6.6 - Conference Recording Email Notification 13 1.6.7 - Offline IM Support 13 1.6.8 - Web Client Sign-In Notifications and Messaging 14

1.6.8.1 - End User License Agreement (EULA) 14 1.6.8.2 - System Notifications 14 1.6.8.3 - What’s New notification 14

1.6.9 - Conference Options 14 1.6.9.1 - Enable “Press 1 to Join” by Default 14 1.6.9.2 - Public Session 14 1.6.9.3 - RSS Stream Support 15

1.6.10 - Web Client Enhancements 15 1.6.10.1 - Download Recorded Audio / Web Presentation 15 1.6.10.2 - Disabled control notifications 15 1.6.10.3 - Set registered phone in conference / session window 15

1.6.11 - Directory Integration Enhancements 16 1.6.11.1 - Directory attribute to allow / disallow access to My Teamwork 16 1.6.11.2 - Auto-provision phone number 16

1.6.12 - AMDS 16 1.6.13 - Miscellaneous Administration Enhancements 17

1.6.13.1 - Disable Custom Access Codes 17 1.6.13.2 - Call Data Capture 17 1.6.13.3 - Enhanced CDR Query 17

1.7 - WHAT’S NEW IN THIS ACS 8.1 BUILD 5225 17 1.7.1 - Support for Radvision Scopia Elite 17 1.7.2 - Microsoft Office Communicator Federation for IM and Presence 18 1.7.3 - Outlook scheduling add-In 18 1.7.4 - Restricted Features in this build 5225 21

2 - THINGS YOU NEED TO KNOW 22 2.1 - HARDWARE AND SOFTWARE REQUIREMENTS 22 2.2 - SOFTWARE LOCKS OMNIPCX SIDE 22 2.3 - LICENSING AND DOCUMENT CONVERSION VIRTUAL MACHINE 22 2.4 - UPDATE FROM PRIOR ACS 6.X OR 7.X RELEASES TO ACS 8.1 23 2.5 - UPGRADE YOUR SERVER FROM ACS 7.1.4B4520 TO ACS 8.1.0B5225 23 2.6 - UPDATE FROM ANY PRIOR 8.X RELEASES TO ACS 8.1.0B5225 25 2.7 - LOAD YOUR NEW SERVER WITH ACS 8.1.0B5225 25 2.8 - RESOLVED ISSUES 26 2.9 - KNOWN ISSUES AND RESTRICTIONS 30

2.9.1 - General issues 30 2.9.2 - ActiveX conflict with build 5031 31 2.9.3 - Video configuration issues 32 2.9.4 - Missing x in front of phone number 32



2.9.5 - IE7, IE8 browsers 33 2.9.6 - Network disconnection 34 2.9.7 - Outlook issues 34 2.9.8 - Mobile client issues 34 2.9.9 - PSTN Audiocodes Card issues 34 2.9.10 - Additional steps for upgrading Audiocodes TP260 firmware 35 2.9.11 - LDAP issues 35 2.9.12 - Doc Conversion issues 35 2.9.13 - Application or Desktop Sharing 35 2.9.14 - RSS Feed issues 35 2.9.15 - Microsoft OCS federation issues 35

3 - APPENDIX A - VIDEO FEATURE 37 3.1 - VALID VIDEO CONFIGURATIONS 37 3.2 - MULTIPLE INTEGRATED VIDEO CLIENT (IVC) INSTALLATION ON SAME PC 38 3.3 - REGISTRATION OF INTEGRATED OR EXTERNAL VIDEO CLIENTS 38

3.3.1 - Use of Myteamwork Internal SIP Registrar (Kamailio) 40 3.3.2 - Use of OmniPCX Entreprise OXE as SIP Registrar 41 3.3.3 - Use of third party SIP Registrar 42

4 - APPENDIX B - BACKUP OPERATION 43 5 - APPENDIX C - RESTORE OPERATION 44



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 8460-ACS, 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 8460-ACS. 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.

History of the document Edition 01 - April 2010 - Creation of document for R 6.1.000.101.b – ACS 8.1.0b5031 Edition 02 – July 2010 - Update of document for R 6.1.000.102.a – ACS 8.1.0b5225 Edition 03 – July 2010 - added information for OXE SIP Video Registration of document

for R 6.1.000.102.a – ACS 8.1.0b5225



1 - What’s New ? Welcome to Alcatel-Lucent OmniTouch 8460-ACS Release 6.1 of Alcatel-Lucent OmniTouch 8460-ACS is the latest version of the world's leading products for improving conference and Teamwork services across the enterprise.

OmniTouch 8460 - 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.



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

Then select in the pick list any of these options:

“OmniTouch 8460 Advanced Communication Server” “OmniTouch 8464 Meet-me Audio Conference Bridge” “OmniTouch 8660 My Teamwork Conferencing and Collaboration” “OmniTouch 8670 Automated Message Delivery System”

These names are all for the same server software providing different features activated by the license file.

Users Guides & Manuals are available at:

a) Same link as just above for Software

Support Technical Support Telephony User guides & Manuals

• Select Product

• Select menu Browse/Reference Book/User Guides

b) Our Offer link in BPWS Our Offer Products Choose the product in pick list


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

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


c) Online documentation from ICS in a MyIC configuration not in case of Stand-alone

Myteamwork ACS

Click on “help” then it will open your browser and connect to ICS URL:

d) Online help



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.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.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 :

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

1.5 - Hardware configuration – Minimum requirement To support ACS 8.1, the server used must support Red Hat Enterprise Server release 5 update 2 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 and on Red Hat Hardware specifications web site. The minimum processor requirement is a dual core 2,8 GHz or faster.




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


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.6 - New Features coming with the ACS 8.1 version

1.6.1 - Language Support

Added Arabic voice prompts

1.6.2 - Embedded Operating System (documents conversion) New ACS installations that use the Web Presentation feature will now require Microsoft Windows 7. The systems being upgraded, that contain earlier versions of Microsoft Windows, will continue to operate with that version.

1.6.3 - Supported Desktop OS and Browsers

Support added for Internet Explorer 8

Support added for Vista SP2 and Windows 7

1.6.4 - New Video features

1.6.4.1 - Remote Audio Mixing with Radvision Video MCU Video endpoints with audio on ISDN or H.323 are now supported, by routing audio through the external Radvision MCU. [Note that in the initial release of ACS 8.1, there are options exposed that allow the user to request audio on the Radvision MCU in other contexts – these are currently not supported. This restriction will be removed in a maintenance release]

1.6.4.2 - Client Profiles In prior releases, there was only one set of settings for the internal video client. In ACS 8.1 release, these settings can now be saved in up to three user created profiles, and also three “system” profiles (defined by the system administrator). Settings stored for each profile are:

• Audio/Video endpoint • Video Quality



• Registrar, Proxy, Realm, Username, Password • Auto answer options • Advanced options (logging, network protocol settings, and so on)

1.6.4.3 - Video for Anonymous Users In prior releases, the My Teamwork video feature was restricted to logged in My Teamwork users. In ACS 8.1 release, anonymous conference participants can pre-install the embedded HD video endpoint,and then participate in video conferences. Installation is performed using a link in the conference join page.

1.6.4.4 - Secondary Video MCU This feature allows an administrator to configure a secondary Radvision video MCU to be used in the event the primary fails. If the primary fails, and a secondary is configured, all subsequent video calls will be placed using the secondary, until it fails, at which point the system will fail back to the primary. Notable points:

It is assumed that the primary and secondary are configured with the same conference settings (e.g. conference code “86” has the same definition on both systems)

The secondary does not need to be the exact same model or have the same capacity as the primary.

When using a Radvision iView, it is possible to configure the primary to point to the iView, and the secondary to point to one of the MCU’s that sits behind the iView. This shields the users from a failure of the iView system, albeit at a potentially reduced capacity.

The secondary is used only for redundancy, not for increased capacity.



1.6.4.5 - Real-time Audio/Video Client Statistics When using the built-in HD video client, a user will be able to toggle on and off the display of real-time video statistics. Statistics include:

• Send / receive codec names for audio and video • Send / receive bitrates for audio and video • Send / receive video frames per second • Packet loss and jitter

1.6.5 - QOS Support In prior releases, ACS supported setting DSCP (DiffServ) bits for the audio RTP packets sent from ACS (Outbound IP Packets). In ACS 8.1, there are two new DSCP features:

In the VoIP settings page, the system administrator is able to set DSCP bits for SIP messages The built-in HD Video endpoint will now also set the DSCP / TOS bits for audio, video and SIP connections.

The ability to do this depends on the underlying operating system (Windows) allowing the setting the packet header TOS byte.

For Windows XP users, no client-side QoS management will be provided.

For Windows Vista and Windows 7 users, DSCP support is provided.

This is all managed through the Windows Group Policy facility. This is entirely outside and independent from the ACS system.



1.6.6 - Conference Recording Email Notification Starting with ACS 8.1, every time an audio conference is recorded, and the recording ends, a “recording details” email will be sent automatically to the owner of the conference. The email is the current standard “recording playback” message. Besides the basic convenience of the feature, having this now allows us to enable the audio recording feature for MACB users. Until now, MACB users could not record conferences because they had no access to the My Teamwork web client in order to play or download the recordings. MACB stand for Meet-Me Audio Conference Bridge (subjected to License) With this email notification, MACB users have access to the minimum required GUI needed to get to the audio recordings. Notable points:

Recordings will expire and be deleted on the schedule set by the system administrator.

Users can download audio (and combined web presentations) to make their own archive. For this release, MACB users cannot make use of the audio conference recording password feature.

1.6.7 - Offline IM Support ACS 8.1 introduces an “IM store and forward” capability. This feature allows messages to be delivered to a given user(s) even though they are not online when the message is sent. When using the My Teamwork client, if a user tries to send an IM to a user that is offline they will 1st be prompted to see if the message should be stored for future delivery. Later when the intended recipient signs in, a popup message will be displayed when there are messages pending delivery. The popup contains a list showing how many stored messages are waiting (and who they are from). The contents of the IM will not be automatically pushed to the client. The user can choose to view the messages, or to simply discard them.



1.6.8 - Web Client Sign-In Notifications and Messaging

1.6.8.1 - End User License Agreement (EULA)

Starting with ACS 8.1, a user may be required to accept an EULA before successfully signing in to the My Teamwork web client. When required, the user will see a somewhat standard looking EULA dialog. The user will not be able to navigate to the My Teamwork web application until the agreement is accepted. The acceptance of the agreement will be permanently recorded in the users’ database profile. Over time, as new software versions are deployed, users may be required to re-accept a new EULA, which will also be independently recorded.

1.6.8.2 - System Notifications

Starting with ACS 8.1, a system administrator may post a text message to be displayed to each user the next time they sign-in to the My Teamwork web client. The user may optionally choose to dismiss the message. If not dismissed, the message will continue to be displayed each time the user signs in. The system administrator can turn off the display of the system notification.

1.6.8.3 - What’s New notification

This notification is an opportunity to point users to any thing special or noteworthy about a new software release.

For a minor system upgrade it may be used to highlight a new small feature or change in

behaviour.

For a major system update it may provide a complete overview of the new features for the release.

1.6.9 - Conference Options

1.6.9.1 - Enable “Press 1 to Join” by Default

Prior to ACS 8.1, this feature was not enabled by default.

Starting with ACS 8.1, all newly created conferences will have the “press 1 to join” feature enabled by default. This helps to prevent a number of problems that have caused difficulties for users joining conferences.

1.6.9.2 - Public Session

This new per-conference feature allows conference rooms to be marked as “public”, meaning the session does not automatically end once all participants have “left the room” and no content filtering is performed (currently participants only see messages while they are in the session). The IM stream can be used for asynchronous messaging between participants that come and go at various times. Unlike other types of conferences, users that join the session can see all



communications left by previous participants, and their messages will be seen by all future participants. And messages can be deposited into the session even though no other participants are there at that moment. When viewing one of these never-ending public sessions, a new GUI control will be visible in the IM session window. This control provides backwards and forwards navigation through the history of the session.

1.6.9.3 - RSS Stream Support

For conferences that have been marked as Public, there is also the option of making the session IM stream accessible through an RSS feed. These streams can be viewed by any standard RSS client (Outlook, for example).

For each message in the IM stream, the RSS feed will contain the from user id and display name, date and time the message was sent and the message body. If the message contains any URL’s they will be formatted to allow hyper-link navigation from the RSS reader.

Look at online help of MyTeamwork for description of the feature operation.

1.6.10 - Web Client Enhancements

1.6.10.1 - Download Recorded Audio / Web Presentation

In ACS 8.1, a user may download a combined audio / web presentation package which contains all files necessary to replay the recorded web presentation, with synchronized audio, from a desktop system or web server other than the original My Teamwork server.

The option to download the complete presentation is found on the standard “Recording Details”

page. When selected, a zip file is created and downloaded to the users local desktop. The zip file contains a complete tree with proper relative references for both the audio and html content from the web presentation.

1.6.10.2 - Disabled control notifications

Today there are various GUI controls that are intentionally disabled during certain conditions. But a user will often still try to use the control and wonder why the client is not doing what they expect. For this release some informational messaging will be added to provide better user feedback.

Examples of where the user feedback has been enhanced:

• Conference settings that are disabled while a conference is in progress • Disabled microphone and speaker controls

1.6.10.3 - Set registered phone in conference / session window

This feature allows a user to change their registered phone number from any session window. For normal signed in My Teamwork users this is just a convenience feature. But for anonymous session participants this is the only way they can change the number that should be used after



they’ve joined the session. When changing the number for a session window it will also change on the main console display. Note that this feature does not provide a unique per-conference phone number.

1.6.11 - Directory Integration Enhancements

1.6.11.1 - Directory attribute to allow / disallow access to My Teamwork

The prior auto-provision feature does not provide a mechanism for distinguishing between users that should or should not have access to My Teamwork. Starting with ACS 8.1, when using LDAP external authentication, a system administrator can pre-authorize a user or group of users for access to My Teamwork. The administrator can create a GROUP in their directory (Active Directory for example) and then add authorized users to that group.

1.6.11.2 - Auto-provision phone number

Previously, when auto-provisioning new users, the users email address is automatically extracted from LDAP or OTUC and stored in the new user profile. Starting with ACS 8.1 ACS will also extract phone number information. The phone number will be added to the users ACS phone list and stored as type “user”, meaning users can modify or delete these numbers. These auto-provisioned numbers will not be used to automatically setup presence monitoring.

This new feature works for both LDAP and OTUC external authentication modes.

LDAP – For LDAP we specifically extract the telephone Number and mobile elements.

OTUC – For OTUC we specifically extract the ‘phoneNumber’ field from the SOAP message

returned during the user authentication process.

1.6.12 - AMDS

Starting with ACS 8.1, a new delivery option is available for the AMDS broadcast feature. When scheduling a broadcast, the user may specify to unconditionally play the recording N times, or until the called number disconnects (hangs up). Certain other AMDS options cannot be combined in a broadcast that selects this feature. When selected, the following features will not be available:

Confirm receipt of a message: Called parties will be prompted to press a touchtone key after the recording has been played.

When the recording ends, prompt called parties to join a scheduled or

reservationless conference.



1.6.13 - Miscellaneous Administration Enhancements

1.6.13.1 - Disable Custom Access Codes

A system administrator may optionally choose to restrict access to the custom access codes feature. This prevents users from intentionally selecting easy to remember / guess access codes. Standard Organization / per-user User Settings rules apply.

1.6.13.2 - Call Data Capture

ACS previously had the feature which allows the capture of all RTP packets for all legs in a given call, but the capture was restricted to a single media server. For ACS 8.1 there are two enhancements to this feature:

• Start data capture by entering the DTMF sequence ##8197. This feature is only usable by a call Leader.

• When requesting a capture, capture the data on all ACS media servers that may be processing legs in the specific call. Today the capture is only performed on the system that the administrator is currently accessing when initiating the trace.

1.6.13.3 - Enhanced CDR Query

The current CDR query mechanism allows for specifying the owner User ID, but this is not accessible from the main (Reporting) CDR query page. Starting with ACS 8.1 the administrator may specify the User ID of a specific user when requesting CDR’s. The query will return any records for calls owned by the specified User ID including partial matches.

1.7 - What’s new in this ACS 8.1 build 5225

1.7.1 - Support for Radvision Scopia Elite In addition to the previously supported Radvision Scopia Classic, ACS 8.1.0 now supports the Radvision Scopia Elite Video MCU:

• Scopia Elite 5110



• Scopia Elite 5115 • Scopia Elite 5230

Note that unlike the Scopia Classic, use of the Elite requires the use of Radvision iView of the associated version. With iView, it is possible to use a mix of Scopia Elite and Scopia Classic MCUs. Validated versions are:

MCU Scopia Version : 5.7.1.2.15 with iView version : 5.7.0.0.3005 or 7.1.2.0.22 MVP Scopia Version : 5.7.1.0.9

MCU Sopia Elite : 7.1.2.6.2 with iView 7.1.2.0.22

1.7.2 - Microsoft Office Communicator Federation for IM and Presence ACS 8.1.0.5225 adds the ability to federate with a Microsoft OCS infrastructure. With this federation, the following capabilities are available:

• MyTeamwork users can add OCS users in their contact list, and vice versa • Either My Teamwork or OCS users can start IM sessions with mixes of MOC and Myteamwork users • Roles of Leader vs. Participant are preserved • My Teamwork and OCS users share presence

In order for My Teamwork users to have MOC users as contacts, they must have “MOC Conferencing” enabled in the “User Licenses” section of “User settings”. See section 2.9.15 for know issue with MOC federation.

1.7.3 - Outlook scheduling add-In The Outlook scheduling add-in does not automatically prompt the user to upgrade. The users should be told to uninstall their current client and re-install from the MyTeamwork Menu Tools Download Outlook AddIn. This will be the same procedure for all version upgrade. The following captures are done on a client PC having already the Outlook addin loaded with an older version. It was not necessary to uninstall it before running these steps. From the client GUI, you could ask for download of the Outlook addin:



Click on download link

You may save the msi package then run it or directly run it.



As MS-Outlook is currently running, you could not complete the installation and need to stop Outlook to get the process carry-on.

When the setup is ended correctly then you may start Outlook and if the credentials of addin are already entered then you see the icon for Myteamwork scheduling in the menu:



If you were never signed-in, you get the sign-in windows that can be modified via the options menu:

1.7.4 - Restricted Features in this build 5225 The following feature is restricted in this release of ACS 8.1:

Audio Conferencing for Microsoft Office Communicator Restrictions will be reduced or removed in future maintenance releases.



2 - Things You Need To Know

2.1 - 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 :

Support Technical Support Telephony Technical Communications

To access the latest technical communications, please click here.

You will access to the Documentation Website

2.2 - 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)

An “ad hoc” (instant) conference of 2 participants in MyTeamwork will require 2 ports for software lock 188 of OXE.

2.3 - Licensing and Document Conversion Virtual Machine The ACS 8.1 is a “maintenance release” of ACS 8.0 and therefore the license file remain the same. No need to ask for a new license file if yours is already done for ACS 8.0. (R6.0) When upgrading ACS releases 7.1.x (R5.x) systems to 8.x (R6.x), you can keep temporarily your ACS license but you’ll get a warning:


https://www.businesspartner.alcatel-lucent.com/bp/englishnavigation.nsf/content/_SSO-KnowledgeBase


ACS license is made up of a .lic file provided by Support Center. The file is secured and can not be read with text editor.

The license for VMWare Workstation 6.5 is embedded in the Myteamwork. Document conversion tool for presentations 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 and higher

The Microsoft licenses for Windows and Office are not provided with Myteamwork by Alcatel-Lucent and should be ordered separately. 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. This last ACS 8.1 is done to integrate the Microsoft Windows 7 Operating System.

2.4 - Update from prior ACS 6.x or 7.x releases to ACS 8.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.4b4520. (Next step is to apply the upgrade procedure from next chapter)

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.4b4520.(Next step is to apply the upgrade procedure from next chapter)

2.5 - Upgrade your server from ACS 7.1.4b4520 to ACS 8.1.0b5225 Boot on DVD 8.1.0b5225 and ask for “u” to upgrade the server. (If using a USB DVD you have to use options uu1 or uu2)



You must get:

- correct partitioning (done by ACS 7.1.4b4322 or higher) - have enough space in Root partition (at least 2,8 GB) - have done the upgrade to minimum version 7.1.4b4520

To be ready for loading the ACS 8.x, you must make an adapted disk partitioning:

If the partitioning is not correct or not enough space (at least 2,8 GB), the upgrade won’t be possible. To get those conditions you must follow the following procedure :

upgrade with tar.gz files up to 7.1.4b4520 (at least) do a manual Backup of all data that you want to keep (see Appendix B) do a manual Backup of your “document conversion” embedded Vmware (see

Appendix B) save your license file R5.x if waiting for new R6.0 license. Reload from scratch the server with ACS7.1.4b520 (DVD boot and option K)

(ACS 7.1.4b4520 is still available on BPWS for downloading) Configure your TCPIP settings and connect in Web Admin Load your license Restore your Data backup (from same 7.1.4b4520) … server will then restart Restore your “document conversion” backup … server will restart

Now your may upgrade the server by booting on DVD of 8.0.0b5225 and ask option “u”.



2.6 - Update from any prior 8.x releases to ACS 8.1.0b5225 It can be done easily by uploading the tar.gz file into the server (Configuration/Upgrade Software) then click on ‘INSTALL’.

2.7 - Load your new server with ACS 8.1.0b5225 This type of installation is also called “Scratch Installation” or “Fresh Installation”. Using this procedure will cause all data deletion (Configuration, database, user presentations and attachments, …) Boot on DVD 8.1.0b5225 and ask for option “S” to load the server (with Single partition). Then your server disk will be formatted and loaded with new version. You need to configure the TCPlP setting, access in Web Admin, Load the license file, manage all parameters of you server and provision all users. Keep in mind : a restore of a previous backup (from older version even 8.1) could not be done as the versions are not compatible.



2.8 - Resolved Issues The following resolved issues were reported by BPs via SR # and identified in R&D with Bug #.

SR # Bug # Summary

1-103664961 25725 SPA/ES translation set has English in it

1-104577801 24950 Not all organization phones are presented in Conference created via Outlook

1-105054285 1-105938745 25181 Problem when SIP/RTP traffic on a different port than eth0

1-105325661 24912 INVITE from MUXER to THS does not contain Domain value in X- domain

1-105389293 1-106545391 1-106783530

25364 https port probes often result in fd and buffer leaks / No more HTTP service and SIP / Serious slow-down of http access.

1-105742254 22434 Edit poll does not always delete responses on owner's copy

1-105742317 25299 Duplicate Operator Queue entry in Organization settings

1-106144501 25676 If a doc conversion takes too long, it stays "preparing" forever

1-106234451 25419 IMS environment: MGC needs P-asserted-ID header to be in E164 format

1-106370351 MYIC show a red phone in taskbar icon and the current phone is greyed and could not be selected.

1-106475701 24814 Cancel link in audio calls doesn't work

1-106818453 25699 Pb to send invitation mytw when account in french and more than 8 phone numbers in the list

1-107373696 24863 Admin page Reporting for schedule conferences do not shows the recurrence conference details

1-107440153 25635 Conference recording using IVR failed for non-DEFAULT domain users

1-107700131 22879 Corrections in email sent for Admin-provisioned conference / Wrong DTMF Instructions

1-107850273 25401 Outlook scheduling with LDAP authentication shows blank page

1-108573811 25911 French accent issue on Video statistics

1-109472165 26055

AppShare activeX install problems encountered when users switch between 8.1.0.5031 and 8.1.0.5025 servers.



1-97288241 Could not send detail of the recorded conference when using Lotus Notes mail client LN 6.5

1-98539513 Lotus Notes is closed then client want to send new memo via Myteamwork - Bad icon for INBOX and Workspace

The following resolved issues were reported by R&D Quality Assurance (Validation) or discovered by Alcatel-Lucent engineering but were not reported by BPs. You may look into this list to get confirmation that an issue that was not reported to Technical Support is now fixed in this last build of ACS 8.1.

Bug # Summary

21306 'Cancel' link is active if phone answered before window open

23159 Calendar Presence publishes an expired recurring meeting

23368 The join page takes a long time to load

24242 Pause my video icon under video panel should pause my video and not the video of selected person

24432 Conversation History tab listing shows server time not local time

24432 Conversation History tab listing shows server time not local time

24443 When choosing external video device, the option "Use my video phone" can't be chosen

24488 users see the wrong appointment in my presence

24544 RHE5.2 Smart Array Controller for HP DL380G6 produces errors. To install ACS 8.1 on these servers, please contact Customer Support.

24547 NaN:NaN:NaN instead of time next to controls while playing presentation

24749 ‘Cal.Presence:Date’ format in the Calendar Presence has a mix of formats

24809 Private message window doesn't appear when video or appshare tab is viewed

24830 Update "Name" field in Prompt_set table for Czech & Korean

24830 Update "Name" field in Prompt_set table for Czech & Korean

24848 User cannot make external video calls if you double-click on the video icon next to scheduled conferences.



24855 Localization page is in English instead of Russian/French

24855 Localization:page in in English instead of Russian/French

25012 "The access code for this call is invalid" if conference owner requires alert about web conf joining

25037 User Options: Cz and Ru has incorrect text in Invitaion tab of Options page

25132 Want proxy user without registration

25158 user gets 'offline message delivery options' while sending the private message.

25158 User gets 'offline message delivery options' while sending the private message.

25168 conference shows up in user's view blocked contact list

25168 Conference shows up in user's view blocked contact list.

25169 Unexpected error message: That user is not currently in your call

25188 Outlook appointment with recurrences doesn't appear in the tooltip after creating.

25216 LDAP: After switching authentication config from Internal to LDAP, user who had been enabled with “Require password change...” is unable to log in.

25240 External registered video or audio clients may fail to connect if user part of Sip URI has any upper case

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

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

25285 alpha: history is corrupted if users of French alpha were involved

25305 Unable to send IMs after primary in stack comes back up

25305 Unable to send IMs after primary in stack comes back up

25330 Long term Appshare load limited to 150+ legs

25347 DTMF keypad doesn't open to press 1 for confirm callback when audio on VMCU

25348 No audio panel when use my telephone and for video calls, use my computer's speaker and microphone option is checked



25383 Set h323 phone as external video device and joining a scheduled conference doesn't work

25401 Outlook addin shows blank details page (with LDAP auth)

25451 Localization: Video Statistic window is corrupted

25459 When user fails back to primary , user's presence is not moved over

25478 Unexplained long delay for presentation paging (while doing video)

25486 Joining a scheduled conference by URL, audio/video profiles should be hidden

25523 report alarm in case any server in the stack cannot reach 1 of the servers in stack

25539 Outlook addin shows only submit and cancel buttons on details page (with stack configuration)

25541 Download new cal presence ActiveX, browser (or explorer) hangs

25552 Outlook Scheduling add-in doesn't support multiple DNS IP addresses

25563 Video icon for video speed dials doesn't change after video is dropped and added back

25581 anonymous users inherit the preferences of the conference owner

25598 audio to video escalation in scheduled conf fails with video sp/dials

25618 Anonymous user's video icon appears grey for the owner.

25622 Unable to send attachments > 64Kb across remote sites

25640 viewer in fullscreen, leader stops appshare, viewer's IE crashes

25641 PPT with animation, viewers do not see animation

25648 Statistics page lists Packet loss as a fraction instead of a percent.

25662 Cal.Presence: user not seen in meeting after deleting an instance of a recurring meeting

25687 Video web UI issues when lifesize or any speed dial is called and escalated from audio to video

25709 User set for automatic config has no way to accept a video call

25742 In a stack, appshare legs sometimes go to the wrong server



25765 Video with no auto accept can't answer the video call

25812 UDA presence : Telephony presence no more working on UDA Web and IPtouch

25813 Install guide should specify 32-bit version of Windows 7 for Doc Conversion

25819 On Doc Conversion Page Windows 7 32-bit must be specified

25862 On history page user name is appended with text "user:"

25879 Correct email format for Admin-scheduled confs (4 languages)

25882 User goes to IVR trying to invite second user to a video conference

25905 User selects himself and another user and speed dial can 't join video conference

25918 Reregister expires defaults to 300 instead of 0 under advanced video settings

25920 ActiveX:each time user is logged in - he gets installation of ActiveX

25932 Calendar presence doesn't work for weekly meetings occurring on Friday

25965 Special characters in RSS conference subject create RSS errors

25999 26027

In web admin “Restart Servers” page, TPdriver and TNS should always be restarted together.

26064 If server or domain name is longer than 40 characters, users are logged out immediately after login, even though they still see what appears to be an active contact list window.

crms00213568 24788 Mobile MyTeamwork application doesn't work with ICS & reverse proxy

crms00221326 25213 Windows "Security Information" pop up when computer disconnected from networks

2.9 - Known issues and restrictions

2.9.1 - General issues

ACS requires that all references to ACS servers will be by FQDN rather than IP addresses. This applies to user GUI, admin web, and internal configuration.

When using Windows Vista or Windows 7 and sharing the desktop, operations that require

administrative rights (causing the admin rights verification popup to appear) will cause the desktop share session to abort.



ACS requires that all references to ACS servers will be by FQDN rather than IP addresses.

This applies to user GUI, admin web, and internal configuration.

On the conference join page accessed through the email invitation, in a multi-site server configuration (stack or remote site), the option “If you have a My Teamwork account, click here" will not appear

Presentation sharing fails on some password protected PDF documents.

If an admin initially sets a users "Audio Auto Answer" setting in their profile, and then the

user changes the setting, then the admin cannot override it.

RHE5.2 Smart Array Controller for HP DL380G6 produces errors. To install ACS 8.1 on these servers, please contact Customer Support.

All servers in a stack or federation (remote sites) must be running the same version of ACS.

There is no support for “rolling upgrade” or mixed-version operation. When using “Play” button to listen to recordings (either recorded conferences or AMDS recordings), Windows Media Player displays a security error message and refuses to play the recording. This occurs on servers that do not have a valid certificate from a trusted source. WORKAROUND – for servers without trusted certificates, users should add the server name to their trusted sites in IE.

2.9.2 - ActiveX conflict with build 5031 After loading an higher build than 5031, we discovered that there was a conflict between the latest ActiveX files and the one from build 5031.In fact, when you already have the latest ActiveX files loaded into your PC client, you will get pop up windows to ask you to download the one from 5031 but you won’t be able to download it as shown in the following screen Capture:



The solution could be to download the MSI component and then install the all ActiveX from 5031 or even better to get all your servers loaded with this latest build 5225.

2.9.3 - Video configuration issues

In the web admin, under Configuration --> Video Settings, the checkbox "Enable Peer to Peer Video RTP" has been removed. The setting is now permanently enabled.

Anonymous video users do not have access to “automatic” profile, so system defined profiles

are required for anonymous users.

When the MCU is changed under Configuration -> Video Settings page, we don't get any message saying that the service list will be updated in 30 sec.

If a user starts a video call, he should wait until after the call to self is fully established before

initiating other legs. That is, wait until the video image is visible before starting another leg.

When configuring a stack that will use video, all servers on the stack need to have identical video settings (both application servers and media servers). For stacks with greater than four servers total, iView is required, since a Radvision Scopia will only support four simultaneous API connections.

By default the iView suite has a maximum setting of 4 hours for the amount of time a

conference can be extended. If this does not suit your needs, it may be extended using the Radvision Configuration Tool. Access the following url: http://<host-name-addr-of- iview>:port/icm-config. You'll be prompted to use the default admin login/password. Navigate to the "Scheduling Settings" page, and modify the "Maximum Length of Meeting Extension" to the desired setting.

Video speeddials are case sensitive in the user part of the SIP address. The case of the SIP address configured at the video end point must be the same as the SIP address in the video speeddial.

After editing the video speeddial, the case is changed to lower case. Work around is to delete and recreate the video speeddial.

2.9.4 - Missing x in front of phone number When using the “UC Authentication” you will get some cases where the x is missing in front of the number and then not displayed in the contact list but also not used for dialling (via the DAS rules).

when you configured the “autoprovisioning” with UC authentication in your Domain authentication. The UC/ICS does send the phone number as defined in the user and the x is not added by Myteamwork (phone formatting rules).

Starting your MyIC, the “current phone” will be added in the Myteamwork user phone numbers but still without the x in front (done by ewchost process of MyIC).

The consequences for the users are:

• The phone list will contains some numbers with x in front (coming from basic management of Myteamwork) and some others without x (coming from UC provisioning or MyIC).



• A phone call to a contact or callback to join a conference will use this phone number without x and using the default DAS rules of Myteamwork the call could not be established.

The DAS rules have to be adapted as follow :

Usually, the “x” is added in front of phone number according to Phone Formatting Rules:

There were anomaly reports entered by BPs for this issue but not taken into account by R&D: 1-96538405 & 1-94582951.

2.9.5 - IE7, IE8 browsers

Browser requirements for Windows XP with IE8, Vista with IE7 or IE8, and Windows 7 with IE8, If connected to a server that does not have a valid certificate form a trusted source:

1. The ACS server must be added to the browser’s trusted sites. Otherwise problems will result using callURLs, application sharing, in installation of activeX components and internal video client operation. When adding the server to the trusted site list, be sure to add only the server name, without a http:// or https:// prefix, and make sure the box “Require server verification …” is not checked. Also be certain that the “Enable protected mode …” checkbox is OFF for trusted sites. 2. In some cases with IE8, security popups may still appear when new windows are opened, In this case, the server’s certificate should be added to the browser’s trusted root certificates:

a. Log into My Teamwork on the server b. Open File --> Properties --> Certificates --> install Certificate c. Select "Place all certificates in the following store". In the associated browse window, select "Trusted Root Certification Authority" and click OK, Next, Finish, Yes, OK.



d. Close all browser windows and re-login.

2.9.6 - Network disconnection

When a user’s PC is disconnected from the network, the ACS server will not declare the user “offline” for as long as 15 minutes. During this time, other users may start new sessions with, send IMs to, the disconnected user with no indication of a problem.

In a stack, if a client PC loses it network connection, or if the primary or secondary server loses

its eth0 connection (and thus disconnects a group of users), then other users who are still connected will not notice a status change for the disconnected users for up to 15 minutes.

2.9.7 - Outlook issues

Non-default Outlook Calendar folders are not supported in the MyTeamwork Conference Scheduling Addin. If you create, copy, or move appointments with MyTeamwork conferences included to a non-default calendar, the conference will not be modified when changes are made to its appointment.

My Teamwork Conference Scheduling add-in for Outlook 2003 requires Windows XP SP2 or

greater and Outlook SP3 or later.

ACS does not support exceptions to recurring conferences. As a result, when using Outlook 2003 or 2007, if an attempt is made to modify one occurrence of a recurring meeting with an ACS conference, a popup window will appear telling the user they must either modify the series or delete and reschedule the occurrence.

2.9.8 - Mobile client issues

In some Smartphones, the My T Mobile application is unable to recognize the phone own number from the SIM. In this case, if it is desired to set the mobile device as the registered phone, the user will have to enter it in the "change Phone Number" option.

Sending an IM to off-line contacts is not supported in the Windows Mobile Client. The sender

will receive the message that the message could not be delivered to the off-line contact. The behavior of the mobile client has not changed compared to previous MyTeamwork releases.

2.9.9 - PSTN Audiocodes Card issues

After a scratch installation, the Audiocodes PSTN board sometimes losses its IP address (PSTN trunks are all down). Workaround could be applied by Customer Support.

Web Admin/Configuration/Trunk Settings shows “initializing phone circuits”

Workaround: Restart telephony services Web Admin/Configuraiton/Advanced Settings/Restart servers, select TNS, THS, TPDRIVER and click Restart Selected Servers Then verify the Trunk Settings are displayed.



2.9.10 - Additional steps for upgrading Audiocodes TP260 firmware If a server is equipped with an Audiocodes TP260 with firmware version lower than 5.2, then the following steps must be executed after the ACS 8.1.0 is installed: • After system reboots (following ACS 8.1.0 installation), on a PC connected to the same network as the server, enter “servername/cgi-bin/ac_ftrkey_upgrade.cgi” into a web browser. o Screen will display “AudioCodes Feature Key Upgrade Log” o If an AudioCodes board is detected, the serial number will display, the Feature Key will be upgraded, if necessary, and the firmware upgrade will be burned to the card. o On the successful finish of the burn process – look for “Current firmware image file is now: F5.20.035.001 … Burning firmware upgrade finished”. o The TP driver will restart, and the system will be ready to use. • This procedure should NOT be used when upgrading between 8.x.x releases. It is only required when upgrading from ACS 7.1.x to ACS 8.x, or when scratch installing ACS 8.1 on a server with an older Audiocodes TP260 (firmware pre-5.2).

2.9.11 - LDAP issues

Users from nested groups in LDAP are unable to log in to My Teamwork.

When using the “Require Group Membership” option, if the LDAP group name contains “#” symbol, verification of group membership will fail.

2.9.12 - Doc Conversion issues

Doc Conversion installation is automatic only for US English. All other languages must use alternate semi-automated install as documented in the MyTeamwork Install Guide.

2.9.13 - Application or Desktop Sharing

When using Windows Vista or Windows 7 and sharing the desktop, operations that require administrative rights (causing the admin rights verification popup to appear) will cause the desktop share session to abort.

2.9.14 - RSS Feed issues

IE6 does not support RSS

The Internet Explorer RSS reader does not display the latest messages if there are many messages (> 1000).

2.9.15 - Microsoft OCS federation issues

After ACS server reboot, presence of My Teamwork users in MOC contact list will become unknown and will stay in this state until timeout or MOC client restart.



If message from My Teamwork user does not reach an intended OCS user for any reason, the

My Teamwork user is not ware of the failure.

Multiple OCS domains not supported.

Federation will only work across multiple stacks (meaning multiple primary application servers such as in remote sites) if all the stacks see the same OCS forest.

If FGW is restarted, it will have no knowledge of new users and existing subscriptions.

Workaround: If FGW is restarted, THS also to be restarted. MOC will periodically attempt to resubscribe to unreachable contacts, so it will correct itself eventually. The length of the period depends on how long it has been since the last successful connection. For active subscriptions, MOC will resubscribe sometime before the subscription expires, which can be up to 60 minutes in the default settings.

Mobile client users do not see proper status for OCS contacts.

OCS CWA is not supported in ACS 8.1.

Application sharing is not supported between MOC and MyTeamwork users, but there is no

warning that it does work. Additionally, My Teamwork features for Polling, Document Presentat6ion, and File Attachment will not work with MOC contacts.



3 - Appendix A - Video Feature

3.1 - Valid Video configurations

The video P2P or Multi-Point controlled by MyTeamwork do require correct licensing of the ACS:

The use of a Video MCU (currently agreed MCU are from RADVISION) is controlled by PCS (Premium Customer Support) and mean that installation of the configuration involving a Radvision MCU has to be done with help of Alcatel-Lucent Professional Services. The BP has to fill-up a PCS request and send it to the contact mentioned at end of the document.

BPWS --> Support --> Technical Support IP Telephony --> PCS Documents

Then look for Alcatel-Lucent OmniTouch Unified Communication in the pick list.

OmniTouch 8660 My Teamwork Multipoint Video Conferencing using RADVISION SCOPIA

To maximize deployment success and return on investment, OT 8660 My Teamwork multiparty video conferencing using the RADVISON SCOPIA video MCU requires PCS.

If an external Radvision MCU is used for video, the required software versions to be loaded are:

MCU Scopia Version : 5.7.1.2.15 with iView version : 5.7.0.0.3005 or 7.1.2.0.22 MVP Scopia Version : 5.7.1.0.9

MCU Sopia Elite : 7.1.2.6.2 with iView 7.1.2.0.22



3.2 - Multiple Integrated Video Client (IVC) installation on same PC

Starting with ACS 8.0.0.4758, it was possible for multiple versions of the Internal Video Client to reside simultaneously in same Windows PC.

This will allow users to have logins on different ACS servers that may be running different ACS versions (and different IVC versions), but not have to re-install the IVC software on each login to a different server.

Note however, that even though the user’s PC may have multiple IVC versions installed, user of the software will be restricted to the first MyTeamwork client that is logged in.

The installation of the video client is done with extract of the files in the Internet Explorer temp directory and it is recommended to not clear the files from Internet Explorer.

3.3 - Registration of Integrated or External Video Clients If you want to be able to do Point to Point (P2P) or Multi-Point video conferencing using MyTeamwork, you have to register all your Video Endpoints (Integrated IE Video Client or External Video Clients) to the same SIP Registrar. All video client should be known by a common PROXY/REGISTRAR equipment to be correctly switched together. There are various type of SIP registrar/proxy as you’ll see in the following descriptions. Configuration example in Integrated Video Client: The “Automatic Video Configuration” is to be used only on a flat network and could not be used over VPN connection. In this mode, there is no SIP Register sent by the video client to the registrar and this can not be used by external video client. In ACS8.1, you may block the Automatic configuration profile for all users of an organization:

Provisioning --> Organizations --> Default User Settings



The “automatic configuration” for video mode will automatically register the video endpoints on the Myteamwork server using port 5080

When the video client is not installed, it will propose you to download it and install it as follow:



3.3.1 - Use of Myteamwork Internal SIP Registrar (Kamailio) This configuration (Embedded SIP Registrar) is available for simple stand-alone Myteamwork topology for local use with small number of video endpoint and without Video MCU. We recommend to use other configurations in a more complex topology (Stacking, Remote site) with various video endpoint (IVC or External), with Internet access associated to SBC and large amount of video endpoint generating heavy SIP Video calls. It also shows a limitation with the use of UDP port 5080. With regular configuration, you will have issue while making a videoconference with someone else. The Myteamwork will send a SIP Invite to “default outbound proxy” with both payloads voice & video. As the outbound proxy OXE do not know the SIP Video endpoint (registered in MyTeamwork), the video RTP connection won’t be established. A problem report was entered and sent to R&D then answered with a configuration to be done in SIP Proxies:

To be taken into account, it needs to make a THS service (SIP Server) restart:

Configuration --> Advanced settings --> Restart servers If this configuration does not work in your case, please us the following work-around: Do not use the Outbound proxy configuration but use a DAS rule. (This will cause trouble if you were using the Spatial Redundancy with OXE 9.0)



3.3.2 - Use of OmniPCX Entreprise OXE as SIP Registrar The IVC configuration could be done as below:

The registration in the OXE could be checked using the command “sipregister” when connected as mtcl on OXE:



Using the OXE to make video with external MCU Radvision or P2P with long URI will cause a change of Transport mode from UDP to TCP (doing a Wireshark capture on Client PC will show it) then the IVC won’t be able to continue the video call. This is standard operation of OXE according to RFC saying that if message is too long in UDP then equipment should change for TCP transport mode. There is a way to change it in OXE via MGR but OXE version should be R9.1 – I1.605.16 minimum. Go to MGR then SIP and PROXY :

True is default value and you need to change it to FALSE.

Then to take it into account in the SIP Motor of OXE do : dhs3_init –R SIPMOTOR

3.3.3 - Use of third party SIP Registrar You may also use other SIP server equipments to perform the same registration. Then you need to enter FQDN or IP Address of this equipment in your video client to make it register and to be used by Myteamwork SIP server for the call invitations. Equipments could be OpenSER/KAMAILIO running on a LINUX distribution or Video MCU (RADVISION, POLYCOM, …); any equipment able to make SIP REGISTRAR/PROXY (SIP proxy server, call router, and User Agent Registration Server).

Take care with ASTERISK (or equivalent Free PBX) as this equipment is more a Back to Back Proxy than Regular Proxy and is not transparent for Payload processing (it will block the Video SIP Invite as it could not handle the H263/H264 video payload).



4 - Appendix B - Backup operation The backup operation is mandatory if you want to upgrade the system to 8.0 and keep all existing information of your server.(You may not have use before the Automatic or Manual Backup) If you are not familiar with this operation, please find hereafter an example of configuration using unsecured FTP with FILEZILLA server. 2 modes are possible:

• SCP transfer (based on port 22) and require a SSH server – using encryption security and certificate.

• FTP transfer (based on port 21) and require a FTP server – clear information on network.

Configure the Filezilla FTP server (can be downloaded from : http://filezilla-project.org/ )


http://filezilla-project.org/


Now you may set the backup of your data or of the document conversion.

5 - Appendix C - Restore operation Upload all files of your backup (Browse the backup directory) then when all files are uploaded and checked (MD5) you may ask for “Restore”.

End of document
