Sut852 Install

7/28/2019 Sut852 Install

1/322

Sametime

Version 8.5.2 IFR1

Sametime Unified Telephony

Installation Guide

Second edition, December 2011


2/322


3/322

Sametime

Version 8.5.2 IFR1

Sametime Unified TelephonyInstallation Guide


4/322

NoteBefore using this information and the product it supports, read the information in "Notices."

Edition notice

This edition applies to version 8.5.2 of IBM Sametime Unified Telephony (program number 5724U79) and to allsubsequent releases and modifications until otherwise indicated in new editions.

Copyright IBM Corporation 2009, 2011.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.


5/322

Contents

Chapter 1. Overview . . . . . . . . . 1PDF library . . . . . . . . . . . . . . . 1

Solution overview . . . . . . . . . . . . 1Features and functions . . . . . . . . . . 2Supported interfaces, protocols, PBX devices, andgateways . . . . . . . . . . . . . . 5

Component overview . . . . . . . . . . . 7Telephony Application Server. . . . . . . . 8Media Server overview . . . . . . . . . . 9SIP Proxy and Registrar . . . . . . . . . 11Telephony Control Server . . . . . . . . . 12

Deployment scenarios . . . . . . . . . . . 13Minimal server deployment . . . . . . . . 13Multiple TAS server deployment with StandbyTAS . . . . . . . . . . . . . . . . 14Deployment with IP PBX environment . . . . 15

Deployment with non-IP PBX environment . . . 16Virtualized servers using VMware . . . . . . 16

Chapter 2. Planning . . . . . . . . . 19System requirements . . . . . . . . . . . 19Planning a virtualized deployment . . . . . . 19

Requirements for the virtualized TelephonyControl Server . . . . . . . . . . . . 21Requirements for the virtualized TelephonyApplication Server . . . . . . . . . . . 28

Planning server upgrades. . . . . . . . . . 28Resources for IBM Sametime Unified Telephonyusers . . . . . . . . . . . . . . . . 31

Chapter 3. Installing version 8.5.2 . . . 33Hardware installation . . . . . . . . . . . 33

Setting up hardware for a Telephony ControlServer . . . . . . . . . . . . . . . 33Setting up hardware for a Telephony ApplicationServer . . . . . . . . . . . . . . . 44Setting up hardware for a Storage Area Network 50

Software installation . . . . . . . . . . . 66Installing Telephony Control Server . . . . . 66Installing Telephony Application Servers . . . 85Installing a SIP Proxy and Registrar server . . 138Starting and stopping services. . . . . . . 139Verifying the installation . . . . . . . . 141

Chapter 4. Upgrading from 8.5.1 and8.5.1.1 . . . . . . . . . . . . . . 143Performing a file system backup . . . . . . . 143

Backing up the Telephony Control Server . . . 143Backing up a Telephony Application Server orMedia Server . . . . . . . . . . . . 144

Upgrading a Telephony Control Server cluster . . 145Downloading the Telephony Control Serverinstallation package for upgrading . . . . . 145Applying patch PS32E49 to the TelephonyControl Server cluster . . . . . . . . . 150

Disabling the HISPA Observer daemon. . . . 151Upgrading the Telephony Control Server cluster

to release 8.5.2 . . . . . . . . . . . . 152Installing a SIP Proxy and Registrar for anupgraded deployment . . . . . . . . . . 159Upgrading a Telephony Application Server . . . 160

Backing up the Telephony Application Serverconfiguration . . . . . . . . . . . . 160Removing out-dated Telephony ApplicationServer components . . . . . . . . . . 161Downloading the Telephony Application Serverinstallation package for upgrading . . . . . 161Preparing the Telephony Application Serverresponse file . . . . . . . . . . . . . 166Upgrading the framework . . . . . . . . 167Restoring the framework . . . . . . . . 167

Upgrading the Media Server . . . . . . . 168Replacing Telephony Application Servercomponents . . . . . . . . . . . . . 168Restoring the Telephony Application Serverconfiguration . . . . . . . . . . . . 169

Configuring security in an upgraded deployment 172Configuring TLS encryption in an upgradeddeployment . . . . . . . . . . . . . 172Configuring secure access to an LDAPrepository in an upgraded deployment . . . . 178Configuring the trusted IP list for the SIPProxy/Registrar server in an upgradeddeployment . . . . . . . . . . . . . 179Configuring authorization settings in an

upgraded deployment . . . . . . . . . 179Configuring TLS encryption for the PBX trunksin an upgraded deployment . . . . . . . 182

Restoring Telephony Application Server services 183Completing the upgrade by updating to IFR1 . . 184

Chapter 5. Configuring . . . . . . . 185Configuring the Telephony Control Server. . . . 185

Command-line interface tasks . . . . . . . 185CMP (Common Management Portal)configuration tasks . . . . . . . . . . 198

Configuring Telephony Application Servers . . . 223Initializing the persistent cache on a TelephonyApplication Server . . . . . . . . . . 223

Establishing trust between TelephonyApplication Servers and Sametime servers. . . 227

Configuring the dial plan . . . . . . . . . 229Example dial plan . . . . . . . . . . . 230Creating office codes . . . . . . . . . . 231Creating Home DNs . . . . . . . . . . 233Different numbering plans available . . . . . 236Configuring business groups . . . . . . . 238Creating numbering plans . . . . . . . . 241Creating default unified number feature profiles 243Creating a queue device . . . . . . . . . 243

Copyright IBM Corp. 2009, 2011 iii


6/322

Creating call routing components. . . . . . 251Adding subscribers for testing. . . . . . . . 268Conducting simple call tests . . . . . . . . 269Configuring conferencing . . . . . . . . . 270

Enabling conferencing on the Media Server . . 271Updating the dial plan . . . . . . . . . 275Configuring conferencing resources on TAS . . 285Testing conference features . . . . . . . . 291

Configuring advanced features . . . . . . . 295Localizing announcements . . . . . . . . 295Configuring CDR and call records . . . . . 305Setting up 911 . . . . . . . . . . . . 305

Communications Assistance for LawEnforcement Act . . . . . . . . . . . 306Setting up speed dial lists . . . . . . . . 307Setting up voice mail . . . . . . . . . . 307

Chapter 6. Deploying SametimeUnified Telephony to users . . . . . 309

Notices . . . . . . . . . . . . . . 311Trademarks . . . . . . . . . . . . . . 313

iv Sametime Unified Telephony: Installation Guide


7/322

Chapter 1. Overview

IBM Sametime Unified Telephony provides the integration of telephony acrossmultivendor Private Branch Exchange (PBX) systems resulting in a unified

end-user experience, including integrated softphones; phone and IM presenceawareness; call control and rules-based call management.

PDF library

You can find information for IBM Sametime Unified Telephony administrators inthe documents linked below.

Guide Description

Sametime Unified Telephony 8.5.2IFR1Release Notes

Any release notes for Sametime Unified Telephony8.5.2 and 8.5.2 IFR1 are included in the SametimeStandard release notes.

Sametime Unified Telephony 8.5.2Quick Start Guide

The Quick Start Guide provides an overview of theinstallation requirements and process for deployingSametime Unified Telephony; this IFR1 release usesthe 8.5.2 version of the guide.

Sametime Unified Telephony 8.5.2IFR1Preview Guide

The Preview Guide provides a quick overview of whatis new and changed in this release; the administratorcan customize the guide before distributing to users.

Sametime Unified Telephony 8.5.2Functional Specification

The Functional Specification includes a description ofSametime Unified Telephony software capabilities andbenefits, as well as a summary of user andadministrator features. The specification describessupported languages and product architecture,including detailed server specifications for the

Telephony Control Server, the Telephony ApplicationServer, and the Media Server. The functionalspecification also describes the storage area networkand IP network connections. The specification alsoincludes information on interoperability and testing.The functional specification was not updated for IFR1.

Sametime Unified Telephony 8.5.2IFR1 Installation Guide

The Installation Guide provides detailed informationon installing and configuring Sametime UnifiedTelephony 8.5.2 IFR1, including: hardware, operatingsystems, primary servers, and failover servers.

Solution overview

Enterprises need to deliver products and services faster to enhance customerservice and speed decision making. Companies are finding that a key to improvingproductivity and business responsiveness is delivering communication andcollaboration tools in a consistent and meaningful context. By integratingtelephony into the company's greater communications platform, decision makingand handling business processes are accelerated. The telephony integration allowsperson-to-person as well as multi-person interaction.

IBM SametimeUnified Telephony software offers the immediacy of instantmessaging with telephone capabilities on users' desktops, so that users can find,

Copyright IBM Corp. 2009, 2011 1
http://public.dhe.ibm.com/software/dw/lotus/sametime/st852/rnST852.htmlhttp://public.dhe.ibm.com/software/dw/lotus/sametime/st852/rnST852.htmlhttp://public.dhe.ibm.com/software/dw/lotus/sametime/st852/rnST852.htmlhttp://public.dhe.ibm.com/software/dw/lotus/sametime/st852/CF2Y1ML_SUT852_QSG.pdfhttp://public.dhe.ibm.com/software/dw/lotus/sametime/st852/CF2Y1ML_SUT852_QSG.pdfhttp://public.dhe.ibm.com/software/dw/lotus/sametime/st852/sut852_func_spec.pdfhttp://public.dhe.ibm.com/software/dw/lotus/sametime/st852/sut852_func_spec.pdfhttp://public.dhe.ibm.com/software/dw/lotus/sametime/st852/sut852_instal.pdfhttp://public.dhe.ibm.com/software/dw/lotus/sametime/st852/sut852_instal.pdfhttp://public.dhe.ibm.com/software/dw/lotus/sametime/st852/sut852_instal.pdfhttp://public.dhe.ibm.com/software/dw/lotus/sametime/st852/sut852_instal.pdfhttp://public.dhe.ibm.com/software/dw/lotus/sametime/st852/sut852_instal.pdfhttp://public.dhe.ibm.com/software/dw/lotus/sametime/st852/sut852_func_spec.pdfhttp://public.dhe.ibm.com/software/dw/lotus/sametime/st852/sut852_func_spec.pdfhttp://public.dhe.ibm.com/software/dw/lotus/sametime/st852/CF2Y1ML_SUT852_QSG.pdfhttp://public.dhe.ibm.com/software/dw/lotus/sametime/st852/CF2Y1ML_SUT852_QSG.pdfhttp://public.dhe.ibm.com/software/dw/lotus/sametime/st852/rnST852.htmlhttp://public.dhe.ibm.com/software/dw/lotus/sametime/st852/rnST852.html


8/322

reach, and collaborate with one another more effectively. Telephony features withintegrated presence awareness, softphones, call control, and rules-based callmanagement can be used with a wide variety of telephone systems. Themiddleware layer of Unified Telephony software provides connectivity to multipletelephone systems both IP private branch exchange (PBX) and legacytime-division multiplexing (TDM) systems independent of the enterprise'stelephony infrastructure or migration to IP telephony.

Features and functionsThis section describes the benefits and features contained in IBM Sametime UnifiedTelephony.

Benefits

v Helps users access telephony functionality from within real-time collaborationsoftware. The front-end user capabilities in IBM Sametime Unified Telephonysoftware are designed to be intuitive and ease access to telephony functionalityfrom within the Sametime client.

v Provides users a simple, consistent user communications experience includingtelephony presence, incoming call management and call control, click to call andsoftphones. Within a single client, users have the same functions and userexperience independent of the phone system to which they are connected. Userscan see if colleagues are available and then reach them more reliably andeffectively without having to find different numbers for different locations.

v Fosters communication and collaboration within applications to help speedbusiness processes for users. Sametime and IBM Sametime Unified Telephonysoftware allow communication and collaboration in a meaningful context thataccommodates work-style preferences. Users can access and manage theircommunications from a Sametime or IBM Notes client; a Microsoft Outlook,Microsoft Exchange, or Microsoft Office application; or an enterprise application.

v Helps optimize the value from existing enterprise applications and telephonysystems - independent of the telephony infrastructure or migration to IP

telephony. The software integrates both IP PBX and legacy TDM systems.v Helps reduce calling costs with softphone, call management, and aggregated

presence awareness. Calls made through the softphone feature avoid PBXtelephone charges. Call management capabilities can direct calls to a user'spreferred device so that colleagues do not have to call various devices to findthe user. The aggregation of presence information - a user's availability forinstant messaging or a telephone call - helps colleagues avoid makingunnecessary calls or calls that cannot be accepted by a user. Theclick-to-conference feature can reduce cost of expensive audio-conferencingservices for improvised conferences

Features

v

Presence awareness - including telephony status. At a glance, users can seetelephone status (for example, on the phone, off the phone) along with onlinepresence status (for example, available, away, in a meeting, do not disturb),making it easy to know whether it is appropriate to initiate a real-timeconversation through instant messaging or a phone/conference call.

v Telephony and voice The front-end user capabilities in Sametime UnifiedTelephony software are designed to be intuitive and ease users' access totelephony functionality from within the Sametime client. The software combinesthe immediacy of instant messaging with telephone capabilities, right on users'

2 Sametime Unified Telephony: Installation Guide


9/322

desktops. Users can see if colleagues are available and then reach them morereliably and effectively without having to look up their numbers even if theyare on the move.

Softphone users can initiate and manage phone calls through their PCmicrophone and speakers using the Sametime Unified Telephony embeddedsoftphone.

Click to Call and Click to Conference Users can initiate a call or audioconference through a PBX telephone system by selecting one or multiplenames from the contact list. Users who are collaborating through an instantmessage can escalate from instant messaging to a call or audio conference byusing the click-to-call, click-to-conference capability.

Incoming call management With Sametime Unified Telephony software,users focus on the people they need to reach not where they are or whatdevice they are using. Users can have a single unified phone number thatallows calls to be routed automatically to their current location and the devicethey are currently using. Users can easily set rules and preferences to directtheir calls such as redirecting a call to a mobile phone. Because Sametimesoftware has presence and location awareness, Sametime Unified Telephonysoftware can automatically set the preferred contact device based on

availability and location status. Call control The software includes call control capabilities for participants

and moderators.

- Participant call controls

v Click to Call

v Click to Conference

v accept, reject, or redirect incoming call

v transfer/forward call

v raise/lower volume

v mute/unmute

v

move call to another devicev Call Merge

v hold/resume

v disconnect

- Moderator call controls

v mute one or all participants

v lock call

v invite others

v end call for everyone

A simple, consistent user communications experience on the desktop client.Sametime Unified Telephony software provides the same set of functionality

and user experiences to supported users, independent of the phone system towhich they are connected. And, it provides these capabilities from within asingle client. Other offerings provide a softphone that only works with a PBXfrom a specific vendor and that require a full migration to IP telephony beforedelivering a common set of unified communications collaboration capabilitiesto users.

v A platform for unified communications and collaboration

The back-end middleware layer of Sametime Unified Telephony softwaremasks the complexity of back-end integration by providing connectivity tomultiple telephone systems.

Chapter 1. Overview 3


10/322

The software connects through Session Initiation Protocol (SIP) toSIP-compliant PBXs from multiple vendors using SIP, and it connects tolegacy TDM phone systems through SIP gateways.

Technology and telecommunications managers can extend their existingtelephone systems rather than replacing them to provide the same set ofunified communications functionality to supported users regardless of thephone systems they access.

The middleware approach can help enterprises deliver the value of unifiedcommunications to virtually all users even if they have not yet completeda migration to VoIP telephony.

Sametime Unified Telephony software is designed for reliability andscalability from hundreds of users to hundreds of thousands.

The call control elements are designed to provide high availability, helping toassure that calls can be completed. Other elements of the system supportredundancy, clustering, and load balancing to help optimize performance andcontinue to provide service to users in the event of component failure. Theincluded IBM Tivoli System Automation for Multiplatforms (SAMP) softwareprovides advanced policy-based automation for applications and servicesacross heterogeneous environments to help provide high levels of availabilityand reduce the frequency and duration of service disruptions.

Sametime Unified Telephony software provides tools for configuring,monitoring, and managing your deployment. A browser-based configurationinterface aids the configuration of the telephony control, application andMedia servers, as well as the definition of business groups, number plans andfeature profiles. Administration consoles can be used to check server status; tomonitor call volume, user call activity and license usage; and to view and editSIP proxy properties.

Emergency calling

Due to implementation differences from the OpenScape source that IBM licenses

from Siemens AG, the IBM implementation of the emergency calling feature maynot work as described in the "Emergency calling" topic within the "Administering"section of this documentation.

In Sametime Unified Telephony, emergency calling works as follows:

When an emergency call is made from within the internal corporate network,Sametime Unified Telephony's built-in E911 (Enhanced 911) support provides thecapability to forward the call to the gateway served by the appropriate PSAP(Public Safety Answering Point) jurisdiction. By conveying location identifiersregistered in the PSAP's ALI (Automatic Location Identification) database, itenables the PSAP operator to retrieve information about the geographical locationof the caller's Unified number and place a response call to either the originator of

the emergency call or a designated on-site destination.

Note: This is not the geographic location of the caller's device. It is the registeredlocation of the unified number. A warning message appears to the caller whenplacing an emergency call informing the caller that their actual geographic locationwill not be known to the PSAP.

Sametime Unified Telephony's Emergency Calling service is applicable to mostEmergency regulatory requirements for enterprise systems. For example, thelocation identification number and callback numbers are provisionable numbers upto 25 digits in length.



11/322

The E911 application is embedded in Sametime Unified Telephony's genericsoftware and is referred to as Emergency Calling table. Since this application isembedded, there is no separate server and there is no additional cost forimplementing the E911 functionality. Performance is directly tied to the resiliencyof the system and the remote gateways in the enterprise network.

Sametime Unified Telephony can support the routing and correct user location

reporting for E911 calls made by its users when located on the corporate network.

Location Identification

When an emergency number is dialled by a device/client, the E911 service looksup an ELIN (Enhanced Location Identification Number) associated with thesubscriber's location and the correct route to the PSAP. The ELIN has previously

been registered with the PSAP with additional information. The location can bederived from the subscriber's DN.

Source Location-based Translation and Routing

The routing of calls in Sametime Unified Telephony is generally fixed by thesubscriber's assigned PNP (Private Numbering Plan). Regardless of the subscriber'sphysical location - within an office/branch, from a hotel connection or even fromhome - whenever there is IP connectivity to Sametime Unified Telephony, thesubscriber can authenticate against the system and is bound to the same PNP.Unless exceptions are enforced by other processes or external applications, diallednumbers are always translated in the same way and the resulting calls are routedto the same destinations.

Supported interfaces, protocols, PBX devices, and gatewaysIBM Sametime Unified Telephony supports a variety of interfaces, protocols, PBXdevices, and gateways.

The complete list of supported interfaces and PBXes is included in the SametimeUnified Telephony system requirements. The list below includes a representativesample:

Protocols

v Proprietary protocol

Virtual Places (VP) - A proprietary protocol used in Sametime forcommunication between clients and server applications and the Sametimeserver.

v Standard protocols:

Hypertext Transfer Protocol (HTTP) - A communications protocol for thetransfer of information about the Internet.

Session Initiation Protocol (SIP) - A signaling protocol used for setting up andtearing down multimedia communication sessions.

Media Gateway Control Protocol (MGCP) - A signaling and call controlprotocol used within a distributed Voice over IP system.

Simple Object Access Protocol (SOAP) - A simple XML-based protocol to letapplications exchange information over HTTP.

Computer-Supported Telecommunications Applications (CSTA) - Anabstraction layer for telecommunications applications.

SIMPLE

http://www-01.ibm.com/support/docview.wss?uid=swg27019317http://www-01.ibm.com/support/docview.wss?uid=swg27019317http://www-01.ibm.com/support/docview.wss?uid=swg27019317http://www-01.ibm.com/support/docview.wss?uid=swg27019317


12/322

T.120

XMPP

H.323

PBX devices

v IP PBX Voice over a data network and interacts with the normal public

switched telephone network (PSTN)v Telephony Gateway Telecommunications network node that can interface with

another network that uses different protocols, as follows:

PSTN Network of the world's public circuit-switched telephone networks.

TDM PBX Time-Division Multiplexing used for circuit mode communicationwith a fixed number of channels and constant bandwidth per channel.

Gateways

v Siemens Gateway

SIP gateways for Non-IP PBX sites

Gateway RG8702 - two E1/T1 ports - 60 or 46 IP channels

Gateway RG8708 - eight E1/T1 ports - 240 or 184 IP channels Gateway RG8716 - 16 x E1/T1 ports - 480 or 368 IP channels

Software RG7800

v Dialogic Gateway

DMG2030DTI - one E1/T1 port - 30 IP channels

DMG2060DTI - two E1/T1 ports - 60 IP channels

DMG2120DTI - four E1/T1 ports - 120 IP channels

Virtualization

For a virtualized deployment, use VMware ESXi 4.0 virtualizaed platform. Be sure

to read about the virtualization requirements in Planning a virtualizeddeployment on page 19.

What to do next

Next, review the Sametime Unified Telephony components.



13/322

Component overview

This section describes the components that make up the IBM Sametime UnifiedTelephony product including servers, clients, and external telephony equipment.

The following graphic shows the various components and how they work together.

The major components are discussed in separate topics:

v Telephony Application Server

v The Media Server

v Telephony Control Server

Sametime Standard Server

IBM Sametime Standard server lets a community of users to collaborate inreal-time activities such as online meetings, presence, chat, and VoIP over andintranet or the Internet.

Sametime Connect Client

The Sametime Connect client is the end-user client for letting community userscollaborate in real-time activities: presence, chat, and VoIP over an intranet or theInternet.

External Telephony Equipment

v IP PBX The business telephone system that delivers voice over a data networkand interacts with the normal public switched telephone networks (PSTN).

v PSTN The network of the world's public circuit switched telephone networks.



14/322

v Telephony Gateway A telecommunications network node that can interfacewith another network that uses different protocols.

Telephony Application ServerThe Telephony Application Server provides telephony services to the IBMSametime Unified Telephony users through the Sametime Connect client. The

Telephony Application Server interfaces with the Sametime Community server,enterprise directory, and Telephony Control Servers.

Telephony Application Server

The Telephony Application Server executes the workflow for handling the calls ofthe users. Users must be provisioned to a specific Telephony Application Server

before they can use Sametime Unified Telephony. The Telephony ApplicationServer is notified when a user logs on to the Sametime Connect and a channelopens to the user and notifies the user that the telephony service is available.

There can be up to 128 Telephony Application Servers on each Sametime UnifiedTelephony deployment.

Each Telephony Application Server monitors up to 15,000 users. User affinity isestablished when a person logs on to the Sametime server with a SametimeUnified Telephony client. Once the Sametime server notifies the TelephonyApplication Server of the event, the Telephony Application Server opens a channelto the Sametime Connect client that enables the Sametime Unified Telephonyfeatures.

Users can provision as many preferred devices and phone numbers for themselvesas they like. The Telephony Application Server can ring any of these devices basedon rich presence and user rules that allow the user to determine what device theywant to ring according to any combination of time, location, and presence status.Telephony Application Servers are deployed with at least one warm standby server

to provide redundancy for server failure. One warm standby server can be used toprovide redundancy for one or all eight Telephony Application Servers. If higherredundancy is required, the number of warm standby servers can be increased tomatch the number of Telephony Application Servers.

Components

SIP Proxy/RegistrarStarting with version 8.5.2, the Telephony Application Server no longerprovides the SIP Proxy/Registrar. Instead, the Sametime Unified Telephonydeployment uses the SIP Proxy and Registrar server provided by theMedia Manager in a Sametime Standard deployment; this provides aconsolidated SIP Proxy and Registrar for all Sametime services. If your

Sametime Standard deployment does not include the Media Manager, youcan deploy its SIP Proxy and Registrar component separately for use withSametime Unified Telephony (see the topic Installing a Sametime MediaManager in the Sametime wiki).

Presence AdapterThis component publishes telephony presence to the Sametime community.

Communications AdapterThis component starts and manages two-party and conference calls. Thecommunication adapter keeps the Sametime Connect client informed of theIP address of the SIP registrar.

http://www-10.lotus.com/ldd/stwiki.nsf/dx/Installing_a_Sametime_Media_Manager_on_Linux_or_Windows_st852http://www-10.lotus.com/ldd/stwiki.nsf/dx/Installing_a_Sametime_Media_Manager_on_Linux_or_Windows_st852http://www-10.lotus.com/ldd/stwiki.nsf/dx/Installing_a_Sametime_Media_Manager_on_Linux_or_Windows_st852http://www-10.lotus.com/ldd/stwiki.nsf/dx/Installing_a_Sametime_Media_Manager_on_Linux_or_Windows_st852


15/322

Media ServerThis component provides tones and announcements for teleconferencemessages.

AdministrationThis component displays the status of the main components and providesreal-time monitoring of user sessions and registered devices.

REST APIThe Representational State Transfer Convention (REST) is the standard for

building web services. The REST interface allows for Click-To-Call andconference integration with third-party applications.

Functions

Telephony Application Server performs the following functions:

v Runs all application logic that manages the workflow associated with routingincoming calls so that they are always routed to the preferred device.

v Initiates all call-related events to the client. If the Sametime Connect client isonline, the Telephony Application Server initiates a popup window that lets the

user answer an incoming call with the current preferred device or deflect the callto another device.

v Provides personal call history records of all calls that user makes and receives.

v Handles all call and flow control for audio conferences.

v Manages all user and configuration data.

v Some data is provisioned into the system as part of the initial configuration,while other data is managed by the user.

v Together with Media Server component provides limited audio conferencingcapability. Primary use case is for small ad-hoc meetings. This capacity isconfigurable.

v Provides ability to provision remote administrative features.

Media Server overviewThe IBM Sametime Unified Telephony Media Server is an application thatntegrates into the Telephone Control Server fFramework. The Media Server can beinstalled on a Telephony Application Server (onboard) or on its own hardware (off

board). Dedicated hardware improves Media Server performance.

The Media Server hosts and executes the following services:

v Provides announcement services for the Telephony Control Server in differentlanguages.

v Supports the following audio-codecs, and can transcode between different codes:

G.711 A-Law (Europe and the rest of the world)

G.711 -Law (North American and Japan)

G.729 AB

Every Media Server node can handle up to a certain number of media channels. Amedia channel is an active call with an active RTP-based media steam.

Attention: For the most recent and detailed information on the Media Servercapabilities, refer to the Sametime Unified Telephony Functional Specification.



16/322

Media Server Scalability

The following table shows media server scalability according to the server profile.It displays required hardware, RAM, and the maximum rate of calls per hour atthe busiest time of the day.

Table 1. Media Server Scalability by server profile

ServerProfile CPU RAM (GB)

Max. G.711Channel

Max. G.729Channel BHCA rate

Small server Dual-Coresystem, forexample, IntelXeon 3060 or5030 (>= 2.33GHz)

4 150 50 3,000

MidrangeServer

Quad-coresystem, forexample, IntelXeon 5345(>= 2.33

GHz)

4 300 100 6,000

High-EndServer

IBM 3550, 2 xIntel 5450(Quad core 3GHz)

8 500 160 10,000

Each Telephony Application Server is provided with a single-accompanying MediaServer to handle the media server needs of that Telephony Application Server.

When scaling up to multiple Telephony Application Servers with theircorresponding Media Server, the Telephony Control Server must be configured touse the Media Server used for the tones and announcements of the users

configured on a specific TAS.

The following graphic shows a typical Sametime Unified Telephony environmentthat can support up to 100,000 users. This support requires the use of sevenTelephony Application Servers, each supporting up to 15,000 users and at thecenter is a Duplex Telephony Control Server system.

Note: One TAS server is used as a failover server in this diagram but it is notactive until required.

The Sametime server supports 30,000 - 50,000 users depending on the operationalprofile. The Sametime cluster support can be scaled as needed.

A Telephony Application Server can be connected to one Sametime server or acluster community.



17/322

Media Server Conferences:

Media Servers support ad-hoc conferencing. Users can initiate conference calls andthe conference bridge in the Media Server dials out to participants. Once thead-hoc conference has been started by the user, the conference bridge in the MediaServer can accept inward dialing into the conference bridge. The Media Serverconferences feature has its own set of specifications:

v There is no fixed limit to the number of simultaneous ad-hoc conferences. Thelimit is based on the maximum number of total conference participants allowed.

v The Media Server transcodes between different codecs if needed.

v The number of conference participants in a single conference can be configured.The default number of users is 6.

vAn onboard Media Server can handle 400 concurrent conference legs. For

example, there can be 100 conferences with 4 people each, or 80 conferenceswith five people each, and so on.

Media Server: Offboard

A Sametime Unified Telephony cluster supports up to eight external or offboardMedia Servers. The ratio of TAS to Media Servers is always one-to-one. There is alimit of eight Telephony Application Servers to one Telephony Control Server.

Note: You can configure the Telephony Control Server itself to use a separateMedia Server for tones and announcements. However, this Media Server cannot beused for conferences.

For failover purposes, the TAS and Media Server must be on the same subnet.

An off-board Media Server can handle up to:

1. 500 simultaneous conference call legs with G.711 codec

2. 160 simultaneous conference call legs with G. 729 codec

SIP Proxy and RegistrarIBM Sametime Unified Telephony uses the SIP Proxy and Registrar provided bySametime Standard, rather than a dedicated SIP server of its own.



18/322

The SIP (Session Initiation Protocol) protocol is used for creating, modifying, andterminating sessions with one or more Sametime Unified Telephony users. SIP useselements called proxy servers to help route requests to the user's computer, toauthenticate between applications, and to authorize users. SIP also provides aregistrar function that lets users send information on their current locations to theproxy server.

Prior to version 8.5.2, Sametime Unified Telephony provided its own SIP Proxyand Registrar functionality, hosted on the Telephony Application Server. Startingwith version 8.5.2, Sametime Standard and Sametime Unified Telephony share aconsolidated SIP Proxy and Registrar, which simplifies SIP-based communications

between products. The SIP Proxy and Registrar is deployed in Sametime Standardas a component of the Media Manager. If your Sametime Standard deploymentdoes not include the Media Manager, you can deploy its SIP Proxy and Registrarcomponent separately for use with Sametime Unified Telephony (see the topicInstalling a Sametime Media Manager in the Sametime wiki).

Telephony Control ServerIn an IBM Sametime Unified Telephony deployment, the Telephony Control Server

is responsible for receiving incoming requests. The Telephony Control Server alsoprovides the unified number service and handles all incoming call routing for theunified number. The Telephony Control Server container is a back-to-back useragent (B2BUA) with a PBX abstraction layer that allows it to work with TelephonyApplication Server.

Specifications

The Telephony Control Server handles VoIP connections. This server is part of aduplex configuration that serves as a failover system. The Telephony ControlServer is always deployed in a duplex configuration with RAID hard disk drivesto provide high availability.

The Telephony Control Server provides the unified number facility that informs theTelephony Application Server about receiving a call from the unified number of auser. It also uses that number for any calls the user makes through SametimeConnect client. The unified number is the single telephone number for routing callsto the telephony devices of the user.

The Telephony Control Server uses the CSTA (Computer SupportedTelecommunications Application) to communicate with the Telephony ApplicationServer, where call-related events are triggered and handled. When a call comes into Telephony Control Server and is a unified number, Telephony Control Servernotifies the Telephony Application Server through CSTA. The Telephony ControlServer also expects the Telephony Application Server to return the number wherethe call is routed. All this communication happens through CSTA.

The Telephony Control Server has the following functional components:

v SIP B2BUA The SIP back-to-back user agent (B2BUA) is the user agent to bothend points of a SIP call. B2BUA handles all SIP signaling between the end point,from call initiation to call termination.

v CSTA The abstraction layer of Sametime Unified Telephony allows interactionson a telephone and a computer to be integrated.

v Virtualized deployment: one or two physical servers (depending on the type ofdeployment), each running VMware ESXi 4.0.

http://www-10.lotus.com/ldd/stwiki.nsf/dx/Installing_a_Sametime_Media_Manager_on_Linux_or_Windows_st852http://www-10.lotus.com/ldd/stwiki.nsf/dx/Installing_a_Sametime_Media_Manager_on_Linux_or_Windows_st852


19/322

For more information, see Planning a virtualized deployment.

v Hardware: IBM System x3550 M2 or x3550 M3. These are the only supportedsystems for a physically installed Telephony Control Server in this release.

The Sametime Unified Telephony Connect software cannot be installed to anyother server.

This part number comes with a predefined set of adapters and a

configuration, including two 146 GB SCSI hard disks configured into RAIDand with two redundant power supplies.

Use of this specified part number ensures that all the correct components areshipped with the server and that the configuration matches what has beentested by IBM software development and performance test teams.

v Operating System: SUSE Linux Enterprise Server version 10 SP3 64 bit isincluded in the Sametime Unified Telephony software bundle.

v Software: The Telephony Control Server is packaged in the Telephony Connectcomponent of Sametime Unified Telephony.

v Telephony Control Servers have eight Gigabit Ethernet ports and require twosets of physical Ethernet switches with three Virtual LANs (Billing, Managementand Signaling). They also require two direct server-to-server interconnect cables

to assure high availability.v Two Telephony Control Servers must be on the same layer two subnet with the

following requirements:

The network links used for interconnects must have low latency and lowerror rates.

The interconnects must not be used on any network that might experiencenetwork outages of 5 seconds or more.

v Telephony Control Server can handle up to 100,000 users. Telephony ControlServer can handle up to 15,000 SIP trunks.

v Telephony Control Server acts as SIP B2BUA between PBXs (IP PBXs and Non IPPBXs through SIP gateways).

v

Telephony Control Server can connect to the PSTN through SIP gateways. TheTelephony Control Server is connected to IP PBXs, non-IP PBXs, and gatewaysthrough SIP trunks.

v Telephony Control Server can support up to 128 active Telephony ApplicationServers with up to 15,000 users each. The total number of users cannot exceed100,000 users.

What to do next

Proceed to review typical Sametime Unified Telephony deployment scenarios.

Deployment scenarios

The following sections describe the supported deployment scenarios for theSametime Unified Telephony system.

The supported deployment scenarios are as follows:

Minimal server deploymentThis section describes the minimal IBM Sametime Unified Telephony deployment.IT consists of two Telephony Application Servers for failover, a single MediaServer, and a standard duplex Telephony Control Server cluster.



20/322

The Sametime clients are connected to a Domino Sametime server, a TelephonyApplication Server configured for failover, and a Media Server which can behosted on the Telephony Application Server or on a separate server.

The Telephony Application Server is connected to the Telephony Control Serverwhich in turn is connected to the normal array of PBX equipment: desk phones,time-division multiplexing phones, and VoIP phones made up of IP and cell

phones that are connected to the IP-PBX system.

This minimal deployment is sufficient for up to 15,000 users.

Multiple TAS server deployment with Standby TASThis section describes a multiple Telephony Application Server IBM SametimeUnified Telephony deployment with a standby TAS. This failover solution employsa standby Telephony Application Server that comes online when another TAS fails.The failover solution is implemented using IBM Tivoli System Automation forMultiplatforms (SAMP).



21/322

The basis for this system is the storing of all the individual TAS applicationconfiguration details on separate partitions on a storage area network (SAN).When a particular Telephony Application Server fails, the standby TelephonyApplication Server is pointed to a location on the SAN from which it loads therequired configuration settings and applications.

The time IT takes for the Telephony Application Server system to restore itself isdirectly proportional to the user base that it needs to reload.

Deployment with IP PBX environmentSametime Unified Telephony software supports connectivity to multiple, mixedPBX environments. Sametime Unified Telephony software is designed to supportconnections to SIP-compliant PBX, using the following SIP RFCs: 3261, 3264, 4566,and to PBXs supporting Primary Rate Interface (PRI) and Basic Rate Interface (BRI)using gateways.

All calls routed to the desk telephones must be intercepted by the Sametime

Unified Telephony system. Based on Sametime Unified Telephony Subscriber rules,the call is then routed. There is a gateway between the PBX and the telephones.

Calls made to the PBX system are now routed through the Sametime UnifiedTelephony system and then routed to the desk top. The customer can choose tokeep the current telephone numbers or get a new set of numbers for the SametimeUnified Telephony installation. Most customers elect to keep their current numbersto avoid disruption in their communications environment. The telephone numbersare converted into Sametime Unified Telephony format, which can include aspecial prefix. The call gets directed to the preferred client device.



22/322

v Calls routed from the PBX to the desk telephones no longer reach the desktelephones directly, but instead are routed to Sametime Unified Telephony.

v Calls from Sametime Unified Telephony destined for desk telephones are routedto the telephones directly.

v Calls from Sametime Unified Telephony to anywhere else are routed to the PBX(and then to the PSTN if needed).

v

Calls from desk telephones can be routed directly back to the PBX which routeto Sametime Unified Telephony if needed.

Deployment with non-IP PBX environmentSametime Unified Telephony deployment on a non-IP PBX is the simplestSametime Unified Telephony installation. It requires that calls are intercepted

between the PBX and the desk phone.

Calls placed on the phones are routed through the non-IP PBX to other phones orto the Public Switched Telephone Network (PSTN).

All calls out to the desk-phones must be intercepted and the calls redirected to the

Sametime Unified Telephony system. Sametime Unified Telephony then decides,based on subscriber rules, where the call is routed. There are several options.

v If the non-IP PBX has a SIP interface, it could act like a gateway between the IPand the Time Division Multiplexing (TDM) world, as the integration point.

v If there is no SIP interface available on the PBX, the use of a SIP Gateway ispossible. The proposed gateway must be compatible with the existing TDMtraffic and there can be no known interoperability issues between the gatewayand the non-IP PBX.

What to do next

Now that you have reviewed the product components and typical deploymentscenarios, you are ready to plan your Sametime Unified Telephony deployment.

Virtualized servers using VMwareUse the VMware ESXi 4.0 virtualized platform to deploy IBM Sametime UnifiedTelephony using virtual machines.



23/322

A virtualized deployment is very similar to a physical deployment except for a fewadditional constraints. The most critical part, from a virtualized point of view, isthe cross-over connection. Network latency on this connection can lead tointermittent failures (where one node believes the other has failed and may go intorecovery mode). For this reason, the inter-cluster connection between nodes isusually on its own dedicated subnet. However a Virtual Host that is near to itsphysical limits may intermittently be overtaxed, resulting in virtual network

performance impacts. This needs to be considered when sizing the virtual host. Soyou have two options: deploy both Telephony Control Server nodes on a singlephysical host where there is a high degree of certainty that resources will not beoverutilized, or deploy each Telephony Control Server node on a separate physicalhost, where both physical hosts and the network in-between can guarantee nolatency. Regardless of whether the system is virtual or physical, you have the samenetwork options with regards to Signalling, Management and Billing networks.

Attention: For best results, the minimum virtualized deployment should providefor failover by including two physical hosts, with a Telephony Control Server nodeand a Telephony Application Server hosted on each (for example,tcs_node1/tas_node1 on the first server, and tcs_node2/tas_node2 on the secondserver).

You can deploy the Telephony Control Server nodes in one of the followingconfigurations:

Co-located on 1 physical server

v 3 subnets reserved for Admin, Billing, Signaling

v Cross-over connected via virtual switch

Co-located on 2 physical servers

v 3 subnets + one Private:

3 subnets reserved for Admin, Billing, Signaling, plus 1 Private for Cross-over

Cross-over cable connection between the nodesv 4 subnets

4 subnets reserved for Admin, Billing, Signaling, and Cross-over

Cross-over connectivity occurs through a layer 2 switch

Geo-separated on 2 physical servers

4 subnets per node, for a total of 8 subnets:

v 4 subnets reserved for Admin, Billing, Signaling, and Cross-over for node 1

v 4 subnets reserved for Admin, Billing, Signaling, and Cross-over for node 2



24/322



25/322

Chapter 2. Planning

Review this section before installing an IBM Sametime Unified Telephonydeployment.

System requirements

When planning your IBM Sametime Unified Telephony deployment, be sure toreview the system requirements to ensure you have all necessary hardware andsoftware.

General system requirements for this release are maintained as an IBM Tech Notecalled Detailed System Requirements IBM Sametime Unified Telephony 8.5.2Interim Feature Release 1.

Virtualization requirements

For a virtualized deployment using the VMware VMWare ESXi 4.0 virtualizedplatform, it is important to ensure that all components meet the minimumrequirements described in Planning a virtualized deployment.

Note: For detailed software and hardware recommendations, see the VMwareCompatibility Guides. Information on virtual machine overhead characteristics isavailable in the VMware Resource Management Guide for each version ofVMware; resource guides are available at the VMware documentation page.

What to do next

Your next step depends on whether you are upgrading an existing deployment or

installing a new deployment:1. Update from 8.5.2 to Interim Feature Release 1: proceed to

2. Upgrade from 8.5.1 or 8.5.1.1: proceed to Planning server upgrades.

3. New installation: proceed to Installing.

Planning a virtualized deployment

Rather than deploying with specialized hardware, you can create a virtualizeddeployment of IBM Sametime Unified Telephony by first installing the VMwareESX/ESXi virtualized platform on any supported hardware, and then deployingSametime Unified Telephony servers on top of it.

Before you begin

Install the VMWare ESXi 4.0 virtualized platform onto each server that will host avirtualized Sametime Unified Telephony server. For detailed software andhardware recommendations, see the VMware Compatibility Guides. Information onvirtual machine overhead characteristics is available in the VMware ResourceManagement Guide for each version of VMware; resource guides are available atthe VMware documentation page.

http://www.ibm.com/support/docview.wss?rs=477&uid=swg27023284http://www.ibm.com/support/docview.wss?rs=477&uid=swg27023284http://www.vmware.com/resources/guides.htmlhttp://www.vmware.com/resources/guides.htmlhttp://www.vmware.com/support/pubs/http://www.vmware.com/resources/guides.htmlhttp://www.vmware.com/support/pubs/http://www.vmware.com/support/pubs/http://www.vmware.com/resources/guides.htmlhttp://www.vmware.com/support/pubs/http://www.vmware.com/resources/guides.htmlhttp://www.vmware.com/resources/guides.htmlhttp://www.ibm.com/support/docview.wss?rs=477&uid=swg27023284http://www.ibm.com/support/docview.wss?rs=477&uid=swg27023284


26/322

About this task

A virtual machine is a self-contained operating system that behaves as if it is aseparate computer. A virtual environment is hardware independent, relying on thevirtualization platform to mimic the necessary hardware. Sametime UnifiedTelephony supports the use of the VMware VMWare ESXi 4.0 virtualized platformfor a standard duplex (co-located and geographically separated) configuration. All

hardware used should be on the VMware compatibility list for VMWare ESXi 4.0.

Note: Because a virtualized deployment is hardware independent, IBM cannotpredict which hardware your deployment will use; the examples provided in thisguide describe the installation and set-up for a IBM x3550 M2 server.

The virtual machine specifications are essentially the same as the physicalmachines with regards to CPU, memory and hard disks; the one difference, whichis very important, is that on a virtual system, hyperthreading on the CPU's must

be disabled.

The virtualized Sametime Unified Telephony deployment has the following specificcharacteristics:

v Supports Sametime Unified Telephony images in a Storage Area referred to as adatastore.

v Is hardware independent.

v Has no maintenance controller interfaces (RSA, IMM, iRMC, VMK).

v Does not support hardware alarming.

v Currently supports and requires a fixed number of 4 (virtual) Ethernet ports.

v Supports 2-node clustering in co-location and network geographical separation.

v Can be deployed as co-located on 1 host (both nodes on same physical host) oron 2 hosts, or as a geo-separated system on 2 hosts.

v Can use internal or SAN storage.

v

Is compatible with VMware ESXi 4; all hardware used should be on the VMwarecompatibility list for ESXi 4.0.

v Requires a virtual machine disk size of at least 140 GB.

The virtualized deployment is subject to the following limitations:

v Hyperthreading must be disabled on the CPUs.

v When installing from an ISO image file, you must allocate at least 5 GB of diskspace in a nodes datastore for the placement of the Virtualization Image DVDISO and Node Configuration files.

v Because the virtual machine is hardware independent, it is assumed that thephysical server and the virtualized platform are installed, supervised, andmaintained by the customer. This documentation does not describe how to

deploy the physical server or the VMware virtualized platform.v The virtual Sametime Unified Telephony server assumes it has one disk and 4

Ethernet ports.

v Disk location (local or network), disk redundancy (RAID), hardware redundancy,and network redundancy (bonding driver) are outside the scope the virtualSametime Unified Telephony servers control, and must be installed by thecustomer.

Important: Although the VMware platform supports a wider range of hardwarethan the standard Sametime Unified Telephony servers, you must still ensure that



27/322

your servers meeting the minimum requirements described here. Failure to meetthese requirements may result in diminished performance, or even anon-functioning product.

Procedure

Complete these steps to ensure you are preparing the virtualization environment

correctly:1. Review the virtualization requirements described in this subsection.

2. Verify that your physical server hardware is supported by VMware.

3. Decide whether you will deploy a SAN (Storage Area Network) drive or usethe local hard disk of the physical server.

4. If you will connect a SAN, verify that it is supported by VMware.

5. Make sure you have a working Microsoft Windows or Linux system availablefor building the node.cfg files and placing them on the virtual floppy disksfor installing the Telephony Control Server application.

6. If network redundancy is required, configure the VMware host with NICteaming and determine the network port to VMNIC mapping.

7. Decide which type of installation configuration you will be conducting:co-located or geo-separated.

8. For a co-located configuration, decide whether the guest servers will berunning on 1 physical host server or 2 physical host servers.

9. Determine network cabling based on the configuration decisions you made inthe previous steps.

10. Create the guest virtual machines according to the specifications in theVMware release notes.

11. Install the Telephony Control Server image on each of virtual machines.

Requirements for the virtualized Telephony Control Server

A virtualized Telephony Control Server is hardware independent; however, thephysical server that you use must meet a specific set of minimum requirements toensure the product functions properly.

Before installing the virtualized Telephony Control Server, make sure the physicalserver meets these minimum requirements:

Physical server requirements for hosting a virtual machineEach physical server that will host one or more virtual machines must meet a setof requirements to ensure performance. The figures stated are minimumrequirements and vary with the number of users supported by the deployment,assuming a typical Enterprise Feature set with no Continuous tracing/Distributedregistration/Nodes on Separate servers/Active-Standby mode.

Overhead requirements

Each physical server must satisfy the following overhead requirements; note thatsome values cannot be predicted here because they depend on the configuration ofthe physical server.

Chapter 2. Planning 21


28/322

Table 2. Virtualization overhead requirements. Requirements apply to each physical server.

Hardware Description Size

Hard disk VMware system diskoverhead

17 GB

Hard disk Overhead for swap space forall unreserved VM memory

Unknown (GB)

This value cannot be strictlydefined because the physicalserver may host other VMsthat do not reserve all theirmemory.

Hard disk Overhead for snapshots if used

Unknown (GB)

This value cannot be strictlydefined because it dependson whether the customerplans to utilize snapshots.

RAM VMware system overhead 2.5 GB

CPU VMware system overhead Unknown (MHz)

See the VSphere ResourceManagement Guide

General requirements

Each physical server must satisfy the following general requirements to ensure thevirtual machine it hosts has the appropriate resources.

Table 3. General requirements for a physical server. Requirements apply to each physical

server.

Requirement 0 - 1.000 users1001 - 5.000users

5001 - 10.000users

More than10,000 users

Server affected Each physicalserver (eachnode)

Each physicalserver (eachnode)



Guest operatingsystem

SLES 10 SP3 SLES 10 SP3 SLES 10 SP3 SLES 10 SP3

Real-timeapplicationNote: Resourcesmust be reservedfor real-timeapplications toguarantee

availability.

Y Y Y Y

Number ofvNICs

4 4 4 4

NetworkBandwidth(Kbps)

319 1598 3194 16000

Use manualMAC

Yes Yes Yes Yes



29/322

Note: Keep in mind that:

v A fixed MAC address is required for license binding. Using a fixed (manual)MAC address ensures that the MAC address is not altered by any VMwarefunction.

v Network usage may vary based on call usage and feature mix.

v Total bandwidth KB/s requirement formula = cps*46, where cps (calls per

second) formula = # of users*5/3600*5 (5 calls per user per hour with a loadingfactor of 5 for features).

v It is recommended that you deploy nodes on separate physical servers toprovide hardware redundancy. If the nodes are located on the same physicalserver, the X-channel traffic will not use the physical network.

v X-channel bandwidth KB/s requirement formula = cps*35, where cps iscalculated as above.

Disk requirements

Each physical server must satisfy the following configuration requirements toensure the virtual machine it hosts has the appropriate resources.

Table 4. Disk requirements for a physical server. Requirements apply to each physicalserver.

Requirement 0 - 1,000 users1001 - 5,000users

5001 - 10,000users


Disk space forvirtual machine

140 GB 140 GB 140 GB 140 GB

IOPS -Input/outputoperations persecond (StorageI/O)Note: From

VMwareResourceManagementGuide: Beforeusing StorageI/O Control ondata stores thatare backed byarrays withautomatedstorage tieringcapabilities,check theVMware

Storage/SANCompatibilityGuide to verifywhether yourautomated tieredstorage array hasbeen certified tobe compatiblewith Storage I/OControl.

Shares = N +unlimited IOPS(defaults)






30/322

Table 4. Disk requirements for a physical server (continued). Requirements apply to each

physical server.

Requirement 0 - 1,000 users1001 - 5,000users

5001 - 10,000users


Disk throughput(Kbps)

23 113 225 1129

Virtual diskmode

Independentpersistent




Virtual diskformat typeNote: Usingthickeager-zeroedvirtual diskreduces delaysthe first timethat a block iswritten to thedisk and ensuresthat all space isallocated andinitialized atcreation time. FTrequires thindisk to beconverted tothickeager-zeroed.

Thicklazy-zeroed

Thicklazy-zeroed

Thicklazy-zeroed

Thicklazy-zeroed

Additional harddisk spaceneeded (on theserver/SAN) tohold things like

images,patchsets, massprovisioningfiles, restore cd,and so on.

10 GB 10 GB 10 GB 10 GB


v Additional disk space may be required for storing log and trace files (in the/software directory).

v Disk usage may vary based on call usage and feature mix.

v Hard disk KB/s formula = cps*3.25, where cps (calls per second) formula = # of

users*5/3600*5 (5 calls per user per hour with a loading factor of 5 for features).

CPU requirements




31/322

Table 5. CPU requirements for a physical server. Requirements apply to each physical

server.


5001 - 10.000users


vCPUs 2 2 4 8

vCPU Shares

(H=High,N=Normal)

H H H H

vCPUReservation(MHz)

5000 5000 10000 20000

vCPU Limit(MHz)

5000 5000 10000 20000

Where 8 CPUs are required, a virtual host with only 4 CPUs can create a virtualmachine emulating 8 CPUs; however. this can lead to CPU contention where themachines might not look overtaxed, but will perform badly due to the contention.For example, a Telehpony Application Server with an onboard Media Serverrequires 8 cores (2 quad-core CPU's). If the underlying physical host machinedoesn't have at least this number of cores available, it will lead to CPU contention.

Memory requirements


Table 6. Memory requirements for a physical server. Requirements apply to each physical

server.


5001 - 10.000users


VM Memory(GB)

4 4 8 8

VM MemoryShares (H=High,N=Normal)

N N N N

VM MemoryReservation (GB)

4 4 8 8

VM MemoryLimit (GB)

4 4 8 8

Supported features


Table 7. Supported features for a physical server. Requirements apply to each physical

server.

Feature 0 - 1.000 users1001 - 5.000users

5001 - 10.000users


VMware manualMAC used

Y Y Y Y



32/322

Table 7. Supported features for a physical server (continued). Requirements apply to each

physical server.

Feature 0 - 1.000 users1001 - 5.000users

5001 - 10.000users


VMwareVMotionsupported

Planned forfuture upgrade




VMware HighAvailabilitysupported





VMware FaultTolerancesupported

N N N N

VMwareDistributedResourceScheduler (DRS)supported

Required forvMotion

Required forvMotion

Required forvMotion

Required forvMotion

VMware DataRecoverysupported

N (planned forvApp)

N (planned forvApp)

N (planned forvApp)

N (planned forvApp)

VMXNET3virtual networkadaptersupportedNote: Ifsupported pleasereferenceproduct specificinstallation/configurationdocumentation

section forVMXNET3

N (planned forvApp)

N (planned forvApp)

N (planned forvApp)

N (planned forvApp)

Virtual machine hard disk requirementsThe amount of disk space required for each virtual machine is dependent on avariety of factors, including space for snapshots, installation images, and VMwareitself. Use this information to determine the minimum required disk space for thephysical server hosting each virtual machine.

This information here is in addition to the general hard disk requirementsdescribed in Physical server requirements for hosting a virtual machine on page21 and Other requirements for hosting a virtual machine on page 28.

The virtualized IBM Sametime Unified Telephony requires that the virtual machinepresent a single SCSI disk on target (0:0). The virtual machine disk size should be140 GB; however, VMware itself requires an additional 40 GB so the host serverdisk drive should be at least 180 GB for a single Sametime Unified Telephonyvirtual machine on a dedicated physical server (140 GB + 40 GB).

If you configure a co-located virtual machine on a single physical server, another140 GB of disk space is required for the additional virtual machine, for a total of320 GB (140 GB + 140 GB + 40 GB).



33/322

Calculations for the physical HD sizing including allowances for VMware and ISOimages are based on the following:

v New Image + Old Image during upgrade: 10GB

v Restore CD: 100 MB

v Allowed for VMware machine overhead: 3 GB (140 GB VM disk size)

v Allowed for VMware system disk overhead: 17 GB

Note: The calculations for the physical hard disk sizing does not include spacethat would be needed for snapshots, or for swap space for needed by other virtualmachines that do not reserve their memory.

The virtual SCSI controller must be type LSI Logic parallel. The physical disks canbe on-board the host or connected by SAN. Any level of RAID can be used. Diskreservation parameters should be left at their default settings.

Virtual machine network requirementsThe virtualized IBM Sametime Unified Telephony deployment requires that 4subnets be presented to it as labels during virtual machine creation. Each of theselabels needs to be in a different subnet as presented to Sametime Unified

Telephony; these subnets are used in building the node.cfg file for installing theTelephony Control Server.

You can configure the subnets based on the type of configuration you areinstalling, described in Virtualized servers using VMware on page 16. In eachcase these 4 subnets are required (each subnet would be assigned to specificnetwork interface card):

v Admin subnet (assigned to NIC1)

Used for administration and maintenance information.

v Signaling subnet (assigned to NIC2)

Used for SIP/CSTA/MGCP signaling.

v

Cross Connect (assigned to NIC3)Used for call state synchronization:

When virtual machines are co-located on the same host, this is avirtual-switch-only connection.

When virtual machines are co-located on separate hosts, this is a directgigabit-quality ethernet cable cross connect.

When virtual machines are a geo-separated system, this can be either an L2bridged connection or an L3 routed connection.

v Billing subnet (assigned to NIC4)

Used for sending CDRs to the billing server.

Attention: The connection of the labels to the real network is dependent on thecustomers network configuration. This can be a flat or segmented network andcan also use the VMware VLAN capability. VMware network interface redundancycan also be used if required. The exception to this is the cross-connect link, whichdue to the heavy traffic carried and the L2 nature of co-located or L2 bridgedgeo-separated connections should be a dedicated link.

The subnets must be created as type E1000 in the virtual machine.



34/322

Other requirements for hosting a virtual machineOther than the parameters used for configuration, most of the virtual machineparameters should be left at their default settings. There are several exceptions,discussed in here.

The following virtual machine parameters should be set as explained to ensurebest performance of the virtualized deployment:

v Hyperthreading should be turned on, if it is available.

v Important: The CDROM must be on virtual device node IDE(0:0) this is notthe default setting, so be sure to update it.

v For ease of installation, the CDROM should be set to connect on power-on.

v For ease of installation, the "force BIOS flag on next reboot" flag should be set inthe boot options.

Requirements for the virtualized Telephony Application ServerA virtualized Telephony Application Server is hardware independent; however, thephysical server that you use must meet a specific set of minimum requirements toensure the product functions properly.

For the Telephony Application Server, virtualization is supported only for standardduplex deployments. Before installing the virtualized Telephony ApplicationServer, make sure the physical server meets these minimum requirements:

Table 8. Requirements for a physical server. Requirements apply to each physical server.

Requirement 0 - 500 users 501 - 1,000 users

Hard disk size (GB) 140 GB 140 GB

Number of cores 4 8

CPU Share High High

Frequency (MHz) 10640 21280

Memory Share Normal NormalRAM (GB) 10 10


v If you store multiple virtual machines on the same physical server, each virtualmachine requires 10 GB RAM; also, you should reserve an additional 2 GB morethan the total. For example, if your physical server hosts two virtual machines, itrequires 10 GB + 10 GB + 2 GB = 22 GB of RAM.

v In a production environment, it is strongly recommended that the requiredamount of RAM be physically available on the server and reserved for the node.

v It is strongly recommended that you reserve the required number of CPU

resources. The CPU frequency to reserve can be calculated by multiplying thecores required for a node by the processor frequency required for the VMwareconfiguration. Example: If the specification for a Standard Duplex (small) noderequires 8 cores in a 2.66 GHz CPU, you need to reserve 21280 MHz (82660MHz).

Planning server upgrades

Before upgrading IBM Sametime Unified Telephony, you should review the overallupgrade process.



35/322

Important: You can upgrade directly to version 8.5.2 from versions 8.5.1 and8.5.1.1 only; if you still use version 8.0CF1 you must upgrade it to at least version8.5.1 before proceeding to upgrade to version 8.5.2.

Upgrading a Sametime Unified Telephony deployment involves upgrading allTelephony Control Servers, Telephony Application Servers, Media Servers, and theSIP Proxy and Registrar. Each server must be upgraded separately.

Note: The system will not be available to users during the upgrade process so youshould perform the upgrade during a period of low demand.

Whats new in this release?

Sametime Unified Telephony 8.5.2 includes the following new features:

v Click-2-Call number in IBM Lotus Notes and Sametime

v Active Speaker Notification

v Enhanced call merge support

v Initiate SUT calls from Android devices

v

Rest APIs (to support mobile web page for getting/adding/setting devices)v New Hardware support (3550M3)

Attention: Sametime Unified Telephony 8.5.2 is an extension to features inSametime Standard 8.5.2 and is dependent on components in that product. Do notattempt to upgrade Sametime Unified Telephony until Sametime Standard has

been successfully upgraded to release 8.5.2.

An important change in this release is the move to a consolidated SIP Proxy andRegistrar server. In previous releases, each Telephony Application Server installedwith its own SIP Proxy and Registrar. Starting with release 8.5.2, all TelephonyApplication Servers will share the same SIP Proxy and Registrar. If the SametimeStandard deployment already includes a SIP Proxy and Registrar, then the

Telephony Application Servers will use that server, too. If the Sametime Standarddeployment does not provide the SIP Proxy and Registrar, you can install it whileupgrading to Sametime Unified Telephony 8.5.2.

Note: In a Sametime Standard deployment, the SIP Proxy and Registrar isdeployed as part of the Sametime Media Manager; it can be deployed on the samecomputer as the Media Manager, on its own computer, or as a cluster. TheTelephony Application Servers can use the SIP Proxy and Registrar regardless ofhow it has been deployed.

What gets upgraded?

The following tables indicate the version of various components before, and after,upgrading from different releases of Sametime Unified Telephony.

Upgrading from version 8.5.1

Table 9. Component versions before and after upgrading from version 8.5.1

Component Upgrade from version To version

Telephony Control Server V3.1_PS32E46 V5_R0.17.4_03



36/322

Table 9. Component versions before and after upgrading from version 8.5.1 (continued)


Framework TAS10-R11.0.11Note: You will upgrade toTAS10-R11.0.14 as an initialstep in the upgrade process.

TAS11-R2.0.0

Presence Adapter 8.5.1 8.5.2Communication Adapter 8.5.1 8.5.2

User Provisioning 8.5.1 8.5.2

WebSphere ApplicationServer

7.0.0.7 7.0.0.15

SIP Proxy and Registrar 8.5.1 8.5.2

Administration Console 8.5.1 8.5.2

Upgrading from version 8.5.1.1

Table 10. Component versions before and after upgrading from version 8.5.1.1


Telephony Control Server V3.1_PS32E48 V5_R0.17.4_03

Framework TAS10-R11.0.13Note: You will upgrade toTAS10-R11.0.14 as an initialstep in the upgrade process.

TAS11-R2.0.0

Presence Adapter 8.5.1.1 8.5.2

Communication Adapter 8.5.1.1 8.5.2

User Provisioning 8.5.1.1 8.5.2

WebSphere ApplicationServer

7.0.0.7 7.0.0.15

SIP Proxy and Registrar 8.5.1.1 8.5.2

Administration Console 8.5.1.1 8.5.2

What is the upgrade process?

You will perform the upgrade in three phases:

1. Perform a full system backup of all Telephony Control Servers and TelephonyApplication Servers.

2. Install and upgrade components.

3. Complete the system configuration.

Instructions for performing the system upgrade appear in the Chapter 4,Upgrading from 8.5.1 and 8.5.1.1, on page 143 section.

What to do next

After planning your upgrade, you are ready to upgrade Sametime UnifiedTelephony.



37/322

Resources for IBM Sametime Unified Telephony users

You can help your IBM Sametime Unified Telephony users get started quickly andeasily using the informational and learning resources in the Sametime wiki.

For starters, the Administrators: Previewing IBM Sametime Unified Telephony foryour users provides your users with a preview of the new features coming to their

desktops. This ready-to-distribute PDF file gives a quick overview of what is newand changed in this release. The Lotus Symphony file includes the sameinformation as the PDF file, with instructions on how to customize the file withinformation specific to your site and how to create your own PDF. Note: Be sure toread the customization instructions in blue text.

The Learning Center page links you to all of the informational and educationalmaterial you'll need, including Getting started pages and the Media Gallery. Theseresources include links to Flash demonstrations, videos, reference cards, Webseminars, product tours, and other materials for learning Sametime.

Finally, you can provide your users with desktop access to Web seminars, referencecards, and other learning materials by giving them the Sametime Learning Widget.You can find this widget in the Sametime Learning Widget page.

http://www.lotus.com/ldd/stwiki.nsf/dx/Administrators_Previewing_IBM_Sametime_Unified_Telephony_8.5.2_for_your_users_http://www.lotus.com/ldd/stwiki.nsf/dx/Administrators_Previewing_IBM_Sametime_Unified_Telephony_8.5.2_for_your_users_http://www-10.lotus.com/ldd/stwiki.nsf/xpViewCategories.xsp?lookupName=Learning%20Centerhttp://www-10.lotus.com/ldd/stwiki.nsf/xpViewCategories.xsp?lookupName=Getting%20Startedhttp://www-10.lotus.com/ldd/stwiki.nsf/xpViewCategories.xsp?lookupName=Media%20Gallery&SessionID=CEL4U6FN3Lhttp://www.lotus.com/ldd/stwiki.nsf/dx/Download_the_Sametime_8.5.2_Learning_Widgethttp://www.lotus.com/ldd/stwiki.nsf/dx/Download_the_Sametime_8.5.2_Learning_Widgethttp://www-10.lotus.com/ldd/stwiki.nsf/xpViewCategories.xsp?lookupName=Media%20Gallery&SessionID=CEL4U6FN3Lhttp://www-10.lotus.com/ldd/stwiki.nsf/xpViewCategories.xsp?lookupName=Getting%20Startedhttp://www-10.lotus.com/ldd/stwiki.nsf/xpViewCategories.xsp?lookupName=Learning%20Centerhttp://www.lotus.com/ldd/stwiki.nsf/dx/Administrators_Previewing_IBM_Sametime_Unified_Telephony_8.5.2_for_your_users_http://www.lotus.com/ldd/stwiki.nsf/dx/Administrators_Previewing_IBM_Sametime_Unified_Telephony_8.5.2_for_your_users_


38/322



39/322

Chapter 3. Installing version 8.5.2

Install hardware and software for IBM Sametime Unified Telephony 8.5.2.

About this task

You must install the complete 8.5.2 deployment before updating to Interim FeatureRelease 1. If you have already deployed version 8.5.2, skip this section and proceeddirectly to Updating to 8.5.2 IFR1.

Hardware installation

Hardware technical information relating to the Telephony Control Server and theTelephony Application Server.

Setting up hardware for a Telephony Control Server

The steps for setting up hardware for a Telephony Control Server depend onwhether you install a physical server or a virtual machine.

Setting up hardware for a virtual Telephony Control ServerConfigure the physical server that will host a virtual Telephony Control Server.

About this task

The virtualized deployment is hardware independent, so specific instructions forconfiguring the physical server cannot be provided; however, the use of VMwarerequires that the server meet a particular set of requirements. For details about therequired configuration of a physical server that will host a VMware ESXi 4.0virtual machine, see the topics in the Requirements for the virtualized Telephony

Control Server on page 21 section.

Setting up hardware for a physical Telephony Control ServerSet up the hardware needed for a Telephony Control Server in an IBM SametimeUnified Telephony deployment.

The Telephony Control Server runs on an IBM xSeries 3550 M2 or 3550 M3, usingSuSE Enterprise Linux Server version 10 SP3. Install Telephony Control Server inpairs to provide backup and failover services; each server can be cabled in aswitchover/failover style or directly to the network. For technical specifications,see the Sametime Unified Telephony system requirements.

TCS hardware installation checklist:

This section lists all the hardware requirements for the TCS.

Hardware checklist

The Telephony Control Server hardware checklist:

v Inventory and inspect the hardware.

v Locate the IBM xSeries server printed documentation and digital media.

v Perform a power on test.

http://./upgrade/upgr_ifr1_intro.htmlhttp://www-01.ibm.com/support/docview.wss?uid=swg27018591http://www-01.ibm.com/support/docview.wss?uid=swg27018591http://./upgrade/upgr_ifr1_intro.html


40/322

v Attach the slides to the rack and place the servers onto the slides.

v Connect all cables.

v Modify the SCSI RAID configuration

v Modify the server BIOS settings.

v Update firmware.

v Power-Supply AC or DC (Hot swappable)

The basic system sometimes come with the memory and additional NIC cards.These cards are packaged separately and need to be inserted into the server. Thedual port and Quad port Gigabyte Ethernet cards must be placed in specific PCIslots.

Telephony Control Server cabling:

This section describes the Telephony Control Server cabling for simplex and duplexsystems in an IBM Sametime Unified Telephony deployment.

You will need the following items:

v

2 x Power-Supply AC or DC (Hot swappable)v Remote Management with Intel BMC

v 2U rack-optimized 20" deep chassis

IBM Sametime Unified Telephony 8.5.2 uses the IBM x3550 M3 server (the M2 isno longer sold). For details on the M3 server, see the IBM System x3550 M3specifications.

There are at least eight cables used in connecting a single x3550 M3 server. Sixcables are connected to the network and two cables serve as crossover cables to beconnected to the second x3550 M3 server.

Configuring BIOS Settings:

When installing the Telephony Control Server hardware for an IBM SametimeUnified Telephony deployment, you must configure the BIOS settings.

Procedure

1. Turn on the server.

It make take a few minutes for the server to start up and display the IBMSystem x screen.

2. When the IBM System x screen appears, press the F1 key to run the Setupprogram.

http://www-03.ibm.com/systems/x/hardware/rack/x3550m3/specs.htmlhttp://www-03.ibm.com/systems/x/hardware/rack/x3550m3/specs.htmlhttp://www-03.ibm.com/systems/x/hardware/rack/x3550m3/specs.htmlhttp://www-03.ibm.com/systems/x/hardware/rack/x3550m3/specs.html


41/322

3. On the System Configuration and Boot Management screen, select Date andTime.

Tip: Refer to the banner at the bottom of the Setup screens for information onhow to navigate the Setup program and manipulate the data on the variousscreens. Some of the Setup screens display screen specific help in the rightcolumn of the screen.

4. On the Date and Time screen:

a. Ensure that the date and time settings are correct; change them asnecessary.

Chapter 3. Installing version 8.5.2 35


42/322

b. Press the Esc key to return to the System Configuration and BootManagement screen.

5. Back on the System Configuration and Boot Management screen, selectSystem Information.

6. On the System Information screen, select Product Data.

7. On the Product Data screen:

a. Verify that the version levels of the Host Firmware, IntegratedManagement Module, and Diagnostics are at least at the levels listed in thefollowing screen:



43/322

If any of the versions are not up to the level listed, consult the IBM SystemX documentation for information concerning the update of drivers andfirmware.

b. Press the Esc key to return to the System Configuration and BootManagement screen.

8. Back on the System Configuration and Boot Management screen, select BootManager.

9. On the Boot Manager screen:

Chapter 3. Installing version 8.5.2 37


44/322

a. Select Change Boot Order.

b. On the Change Boot Order screen, change the order to match the ordershowing in the following screen:

c. Press the Enter key to save your changes.

d. Press the Esc key to exit the Setup screens until you have backed up to theSystem Configuration and Boot Management screen.

10. Do one of the following:

v If you will proceed to set up the RAID unit as described in the next task,leave the System Configuration and Boot Management screen open.



45/322

v Otherwise, press the Esc key to exit the Setup program.

Configuring the RAID unit setup:

When installing the Telephony Control Server hardware for an IBM SametimeUnified Telephony deployment, you must configure the SCSI RAID and create adisk mirror.

Before you begin

You must have set up the BIOS on the server before you can configure the SCIRAID.

About this task

A new server is accompanied by an IBM ServerGuide software. It contains all thenecessary drivers for the server type and model. You can boot the server using theCD and it takes you through setting up the date and time, and the RAIDcontroller. It also primes the server with the correct hard disk drivers (SCSI) for therequired operating system.

You can download the software from the IBM Support site.

If you do not have the IBM ServerGuide software available, you can set up theSCSI RAID unit and create a disk mirror as follows:

Procedure

1. If you are not currently in the Setup program, reboot the server (either cyclethe power or press the Ctrl-Alt-Del keys simultaneously) and press F1 at IBMSystem x screen.

2. On the System Configuration and Boot M

Date post:	03-Apr-2018
Category:	Documents
Upload:	k4lonk
View:	228 times
Download:	0 times

Sut852 Install

Documents