ICS Prerequisites and Data Collect Guide Release R6.x Revised Edition 01 March, 2011 Summary ICS Prerequisites and Data Collect Guide Edition 1
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-2010 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 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. All other trademarks and copyrights referred to are the property of their respective owners. Author This document is written under Technical Support responsibility. In order to improve customer satisfaction, any positive feedbacks, remarks or requests on this Technical Communication are welcome by email: release-notes-ics@alcatel-lucent.com setting subject email to TC1446. Edition 1 Page 2
TABLE OF CONTENTS 1. List of the people involved in the project...5 2. ICS Data Collection and requirement...6 2.1. HARDWARE REQUIREMENT...6 2.2. DOCUMENTATION......6 2.3. SOFTWARE REQUIREMENT...7 2.4. LICENSES...7 2.5. NETWORK...8 2.5.1. Mail servers, DNS, AD...8 2.5.2. ICS servers...9 2.5.3. ACS Teamwork server...11 2.5.4. OFS Fax server...13 2.5.5. OXE server...13 2.6. OXE REQUIREMENT...14 2.7. INTEGRATION WITH OTHER SERVER OR APPLICATION...15 2.7.1. Microsoft solution prerequisite...15 2.7.2. IBM solution prerequisite...16 2.8. WHAT KIND OF AUTHENTICA TION DO I USE...16 2.9. SECURITY AND CERTIFICATE...16 2.10. MESSAGING SERVICES...17 2.11. IMAP 4......17 2.12. CORPORATE DIRECTORY...18 2.13. MY TEAMWO RK...18 2.14. FAX SERVER...19 2.15. HIGH AVAILABILITY...19 2.16. WHERE DO I DEPLOY THE SOLUTION...19 2.17. END USER APPLICATIONS AND TERMINALS...20 2.18. WHO IS IN CHARGE OF THE MAINTENANCE AND ADMINISTRATION OF THE SOLUTION?...21 Edition 1 Page 3
Aim of this document: The aim of the document is to provide to ACSE technical expert a checklist of the different needs before installing an ICS 6.X solution. It can be use as guide in order to prepare the installation process of Instant Communication Suite 6.x and above It covers the Data Collection for ICS and the list of the necessary point that must be clarified and check before installing the solution in the customer site. History of the document Edition 1 March, 2011 Creation Edition 1 Page 4
1. List of the people involved in the project Before preparing the installation on the customer site, it is necessary to prepare a list of the people involved in the project Customer Presales Sales Exchange Administrator Lotus administrator System Administrator Telephony Administrator Security Administrator Project Manager Alcatel-Lucent professional services Alcatel-Lucent Technical support Name Phone E-mail Edition 1 Page 5
2. ICS Data Collection and requirement Before preparing the installation on the customer site, it is necessary to define clearly what are the customer s needs, and the solution sold in order to prepare the configuration. 2.1. Hardware Requirement For up to date information please download the latest Feature List on the Alcatel-Lucent Business Partner Web Site. You will find the on dedicated page (HW & SW requirements) all software requirements. To check that your platform is a Red Hat Enterprise Linux 5uX certified platform, use the Red Hat Hardware Catalogue (a database containing certified and compatible hardware for Red Hat products) at following URL: https://hardware.redhat.com Requirement Hardware for ICS Raid 1 + Raid 0 installation (recommended) 2.2. Documentation Document for ICS release Release Note Feature List ICS Expert Documentation MyTeamwork Expert Documentation Fax Server Expert Documentation If MyTeamwork installation planned If Fax server installation planned Edition 1 Page 6
2.3. Software Requirement Software for ICS release (check release note and documentation CD) Boot CD Red Hat enterprise ICS software DVD TTS See Feature List for TTS available language 2.4. Licenses Deployment files (from ACTIS) ICS Licenses OXE licenses MyTeamwork licenses Fax Server licenses If MyTeamwork installation planned. If Fax server installation planned. For ICS and Fax Server, it is necessary to request a licenses file to welcome center, the license file is linked to the Mac address of the server. For My teamwork, it is necessary to install the My Teamwork server before asking the license. Edition 1 Page 7
2.5. Network When installing an ICS solution some network information must be checked like, IP address, DNS and FQDN naming rules, security, bonding Recommendation: Use easy naming rules for ICS hostnames so connection to the different ICS services will be easier to remember for users. 2.5.1. Mail servers, DNS, AD Device Hostname IP address DNS 1 DNS 2 NTP 1 NTP 2 Active directory LDAP Exchange Server(s) Domino Server(s) Edition 1 Page 8
2.5.2. ICS servers 2.5.2.1 Mono server topology Physical Addresses IP address FQDN Netmask Default Router AS primary physical bond0 AS primary physical Virtual Addresses IP address FQDN Netmask Default Router AS Primary virtual Edition 1 Page 9
2.5.2.2 Multi servers topology Physical Addresses IP address FQDN Netmask Default Router AS primary physical bond0 AS primary physical Middleware physical bond0 Middleware physical HA Server physical bond0 HA Server physical Virtual Addresses IP address FQDN Netmask Default Router AS Primary virtual Middleware virtual Edition 1 Page 10
2.5.3. ACS Teamwork server 2.5.3.1 Mono server topology Physical Addresses IP address FQDN Netmask Default Router Primary MyTeamwork eth0 Virtual Addresses IP address FQDN Netmask Default Router Primary MyTeamwork Domain cluster Address 2.5.3.2 Multi servers topology Physical Addresses IP address FQDN Netmask Default Router Primary MyTeamwork eth0 Primary MyTeamwork eth1 backplane stack link Primary MyTeamwork Edition 1 Page 11
Secondary MyTeamwork eth0 Secondary MyTeamwork eth1 backplane stack link Secondary MyTeamwork Virtual Addresses IP address FQDN Netmask Default Router Primary MyTeamwork Domain cluster Address Secondary MyTeamwork Domain cluster Address Edition 1 Page 12
2.5.4. OFS Fax server Physical Addresses IP address FQDN Netmask Default Router Primary Server Fax Virtual Addresses IP address FQDN Netmask Default Router Fax virtual Server 2.5.5. OXE server Device Hostname OXE Main Cpua Cpub OXE secondary Cpua Cpub If using OXE spatial redundancy, it is necessary to use an external delegation on an external DNS server. Edition 1 Page 13
2.6. OXE Requirement Define the number of PBX on the client network and what kinds of PBX are used. To see OXE compatibility please refer to the Release Note of ICS Release/version of the PBX front-end PBX redundancy Other PBX: Same Subnet Spatial (dual Subnet) How many: Release version: Compatibility with ICS OXE and Applications cross compatibility information may be found on the Technical Knowledge Base. Select menu browse / Reference Book / Cross Compatibility / More Information to get access to the document Characteristics OmniPCX Enterprise Applications/Terminals Cross Compatibility. It is of course highly recommended to use the latest patch in a given OXE release. For distributed users in a PBX network, software locks are necessary on OmniPCX side, see Licenses Guide in expert documentation on chapter OmniTouch 8410ICWS Requirements Recommended OXE version and release Last OXE version installed (Recommended) Licenses Check release note for license information Software locks G711 G729 Thales boxes 4635 (Integrated Messaging) Version : 4545 FTP account Login: Passwd: For more information about OXE, please refer to the OXE Expert Documentation Edition 1 Page 14
2.7. Integration with other server or application In this part define on which existing server or application ICS solution will be integrated. Servers Integration with ICS MS exchange server For unified messaging Domino For unified messaging Applications Integration with ICS Outlook Outlook extensions, My Teamwork add-in MOC MOC integration with MyIC Lotus Lotus extensions Lotus Sametimes Sametimes Integrations If an integration with a third party solutions is planned, verify the compatibility and needs please refer to the Feature List of ICS 2.7.1. Microsoft solution prerequisite Requirements Installation on exchange with plug-in Installation without plug-in Check exchange version Check Outlook version Check OS version for client Check CDO version (collaboration data object) It is necessary to add an users on exchange server It is necessary to add an users on exchange server For MOC installation see last edition of TC1368 available on BPWS For Exchange installation see last edition of TC1344 available on BPWS Edition 1 Page 15
2.7.2. IBM solution prerequisite Requirements Version of domino server Authorize SMTP without Authentification OS of Domino server Clustering not supported 2.8. What kind of authentication do I use Define if an authentication is already used and what kind of authentication will be used with ICS. Type of Authentication ICS internal LDAP n secured (LDAP) Secured (LDAPS) Certificate to connect to Corporate LDAPS LDAP version Radius NTLM Supported NTLM V1 only. Verify the compatibility and needs for authentication describe in Feature List. If using NTLM authentication please check the Windows server domain version. If using 2008R2 a modification on the registry is necessary, please refer to TC1344 (Unified Messaging relying on Exchange 2007/2010 Web Services) 2.9. Security and certificate Requirements Certificate for ICS server trusted by user s computer/browser authorities Client Certificate for ICS if using LDAPS Flow control Which certificate must be installed? Which communication and port use for ICS. For flow control information, please refer to the Excel document in the ICS Expert Documentation Edition 1 Page 16
2.10. Messaging services Define the customer messaging services Type of voice mail Unified Messaging Local storage Integrated messaging Number of users : 4645 or 4635 for Integrated Messaging Exchange/Domino/IMAP server for UM Local storage For Local storage, external Backup has to be planned depending on voice message volume. Unified Messaging may also impact email user s mailbox size and quota. Rules to calculate size of voice messages Wav files of 1 minutes = 500kB For 10 minutes 5MB Requirements Define voice mail boxes space for users Space available on email-server LS partitioning External Storage External Backup Check if the backup space is available Check local storage partitioning Prepare your external backup 2.11. IMAP 4 Requirements Licenses Number of session on the server (some messaging client use several session for one user) If more than 1000 sessions a dedicated server for imap4 is mandatory Edition 1 Page 17
2.12. Corporate Directory Requirements Directory LDAP LDAPS Authentication LDAP LDAPS Certificate Authorities Use to connect to the corporate LDAPS Credential Login: Password: Directory: LDAP (not secured) or LDAPS (not secured) can be managed on ICS to give ICS users access to Corporate Directory from My IC whatever interfaces. Authentication: as external LDAP(S) server used for ICS user authentication, credentials can be managed on ICS to get connected to LDAP(S) server. 2.13. My Teamwork Define if the customer needs a solution with MyTeamwork Audio conferencing Application sharing Teamwork services for mobiles users Teamwork services for IPtouch Video GUI language(s) TUI (vocal access) language(s): Number of teamwork users Number of ports: Number of ports: Number of users: Number of users: See My Teamwork Feature List See My Teamwork Feature List For more information about MyTeamwork, please refer to the My Teamwork Expert Documentation Edition 1 Page 18
2.14. Fax Server Define if the customer needs a solution with Fax Server Fax server Number of ports High availability For more information about Fax server, please refer to the Fax Server Expert Documentation 2.15. High Availability Define if the customer needs an ICS solution which includes High Availability. High availability for ICS Two ICS license files requested : one for AS Primary and one High availability for fax server My Teamwork stacking For high availability installation it is necessary to apply a PCS. for HA server Two ICS license files requested : one for AS Primary and one for HA server 2.16. Where do I deploy the solution Define with the customer, where the ICS server will be installed. Server emplacement available Power supply available Network connection available Backup power protection system recommended Dual Gigabit links recommended (bonding) Edition 1 Page 19
2.17. End User Applications and Terminals Define the applications and terminals applications used by end users. Terminals and Numbers of Services applications users and profile IpTouch Telephony One Number Messaging 4980 MyIC for PC MyIC SIP MyIC for Iphone MyIC for Windows phone MyIC for Blackberry MyIC for Nokia MyIC for Android Web Softphone TUI Outlook Connectors Lotus Connectors MOC integrations Sametime Integrations Telephony One Number Messaging Teamwork Telephony One Number Messaging Teamwork Telephony One Number Messaging Telephony One Number Messaging Voice IT Voice on page Telephony One Number Messaging Telephony One Number Messaging Edition 1 Page 20
For MyIC deployment please check the requirements. Requirements.NET 2.0 SP2 on PC PC in 64 bits OS Headset Deployment solution For Mobility installation see last edition of: TC 1217 (Configuration guideline of MIC client for Nokia) Dot-net SP2 mandatory for MyIC installation VoIP on PC with 64 bits OS not supported Check the white list on the BPWS Check if a deployment solution is available for My IC PC,, Outlook extensions as Administrative rights on user s computer needed. TC1218 (Technical release notes of OmniPCX Enterprise & Instant Communications suite mobility solution with mobile MIC clients for BB, Nokia NCC, android and Windows Mobile) TC1247 (Configuration guideline of MIC client on WM) TC1287 (Configuration guideline of MIC mobile for BB) TC1323 (Configuration guideline of MIC client for iphone) TG0056 (Mobility troubleshooting guide) 2.18. Who is in charge of the maintenance and administration of the solution? Define who will maintain the solution, customer, BP Who is in charge of the maintenance Customer BP Alcatel-Lucent Professional services - END OF DOCUMENT - Edition 1 Page 21