InitialTASConfiguration

8/3/2019 InitialTASConfiguration

1/27

Initial TAS Configuration

-1-

Slide 1

Hello, and welcome to this Web lecture about Sametime

Unified Telephony. In this module, we will be showing how

to set up a trust between Sametime and a Telephony

Application Server, how to configure a connection between

the Telephony Application Server and the Telephony Control

Server using the Common Management Portal. And finally, we

will be looking at the backup and restore features within

the Common Management Portal.

Slide 2

Objectives and Agenda. Here are the objectives and the

agenda for this Web Lecture. After completing this module,

you should be able to:

-- explain why the Sametime server is configured to trust

-- describe how to set up a telephony policy on the Sametime

server

-- articulate how to review LDAP settings on the Sametime

server

-- explain how to configure a connection from a Telephony

Application Server to a Telephony Control Server using the

Common Management Portal -- or, CMP for short

-- describe the backup and restore features available in the

Common Management Portal.

For this agenda, we will cover:

-- setting up a trust between the Sametime and Telephony


2/27


-2-

Application Servers

-- set up a telephony policy on the Sametime server

-- review LDAP settings on the Sametime server

-- configuring a connection from Telephony Application

Server to Telephony Control Server using the Common

Management Portal -- or, CMP for short

-- backup and restore features within the Common Management

Portal -- or, CMP for short.

Slide 3

Setting up a trust between the Sametime and Telephony

Application Servers.

Slide 4

Okay, so now that the operations console is installed, our

next task is to configure the operations console. So again,

all the configuration steps are described in more detail in

the SUT failover step-by-step installation guide, and there

are several screenshots as well, so you would be able to

follow the configuration probably more clearly with that

document.

So the first thing to do is to invoke the Operations Console

Configuration Dialog. Whether it be on a Windows or Linux

machine, the command is the same: it's cfg direct. And from

Windows machine, for example, this will be located under

program files/ibm/tsamp/eez/bin.


3/27


-3-

So once you have the Operations Console Configuration Dialog

invoked, you will see that there are two tabs: there is the

Server Tab and a Security Tab on the Configuration Dialog.

So we are only interested in the Server Tab.

The only field to fill out is the Event Port Number. The

Event Port Number on the Server Tab specifies the port on

which the operations console listens for events from the

adaptor. Again, you should see the Installation

configuration Guide for detailed info on the Security Tab,

but it's outside the scope of this presentation.

So the next point is that in order to directly access the

operations console, the automation adaptor of the SAMP base

component must be configured. So the automation adaptor

establishes and manages communication between the automation

domains and the SAMP operations console.

So, to invoke the configuration window for the automation

adaptor, you need to log on to one of the nodes on which the

SAMP base component is running -- in other words, one of the

nodes in the cluster. You need to issue the command

cfg/samadaptor. Again, this is invoked from one of the

machines in the cluster. You can see the SAMP Installation

Configuration Guide for more complete explanation of all the

tabs and the fields of the Automation Adaptor Configuration


4/27


-4-

Dialog.

So the fourth step here is when the automation adaptor is

invoked, you're presented with a screen with four buttons.

These are configure, replicate, define and remove. Again,

there is a screenshot of this in the step-by-step document.

These four buttons allow you to configure the end-to-end

automation adaptor, to replicate the end-to-end automation

adaptor configuration files to other nodes. Thirdly, to

define the end-to-end automation adaptor automation policy

so that you can create the resources required to automate

the adaptor. And fourthly, you can remove the end-to-end

automation adaptor automation policy.

So firstly, we're going to concentrate on the configure page

of the automation adaptor. So the automation adaptor

consists of six tabs. Configuration steps are applied to

only three tabs: those tabs are the Adaptor tab, the Host

Using Adaptor tab and the Automation tab.

So I'll just describe a little bit more detail what is

involved in these three tabs. So on the Adaptor tab, you

can configure the adaptor host. This is the host name of

the node where the adaptor runs if the adaptor is not

automated. However, when you automate the adaptor, this

value is updated automatically with the value you specify in


5/27


-5-

the field, adaptor IP address on the Automation tab.

So the next tab I'm going to describe is the Host Using

Adaptor tab. You use this tab to determine which host the

adaptor connects to and to specify the required information.

We're connecting to a base component operations console,

which runs in direct access mode, so basically you're

connecting to the operations console and you will be

inputting the host name or the IP address of the machine

where the operations console is running.

So the final tab I'm going to describe is the Automation

tab. This tab lets you configure the adaptor automation

policy. So this allows you to make the automation adaptor

highly available, meaning that if the node on which the

adaptor runs breaks down for any reason, the adaptor will be

restarted on another node in the domain.

Another thing that is specified on this tab is the name of

the automation adaptor. This is specified in the field

automated resources prefix. The default name that you'll

usually see is SAM adaptor. A think note here is that all

nodes where the adaptor can run must be accessible using the

same user ID and password.

So now you can click on save on the configuration dialog to

save your changes to the adaptor configuration files. Upon


6/27


-6-

completion, a configuration update status panel appears,

showing the list of configuration files that were updated.

Slide 5

Option A, to trust all servers. To trust all servers, which

is appropriate in a closed environment, please do the

following.

Open a standard text editor on your Sametime server, and

edit the Sametime.ini file. Please add the following line

to the debug section within this file:

vps_bypass_trusted_ips=1. Save and close the Sametime.ini

file, and restart your Sametime server for this parameter to

take effect.

Slide 6

Option B, to set up a list of restricted servers for a high

security environment. Determine the IP addresses of all

servers in your environment that will connect to the Lotus

Sametime server, beginning with the primary Telephony

Application Server and including any other Telephony

Application Servers or Lotus Sametime servers.

Please note a restriction: you must use actual IP addresses,

not server host names. On the primary Lotus Sametime

server, use a Lotus Notes client to open the stconfig.nsf

database. Open the By Form view, edit the community


7/27


-7-

connectivity document. In the community trusted IPS field,

enter all trusted IP addresses, separated by either a comma

or semicolon. Save the document, and restart the primary

Lotus Sametime server.

Slide 7

Set up a telephony policy on the Sametime server. To begin

with, launch a browser and enter the fully qualified domain

name for your Sametime server, together with a port value of

8088 and a database reference of stcenter.nsf. When this

page launches, log into the server as the administrator.

Next, go to the policies section and click on Sametime

default policy. Under community services, enable the

following item to allow outgoing calls from the client:

allow telephony for contact lists, instant messaging, and

instant meetings. This policy is disabled by default.

Slide 8

Set up a telephony policy on the Sametime server, continued.

Next, go to Policies and click Sametime Default Policy.

The following polices under instant messaging, control the

use of peer-to-peer voice and video chat. These features

are enabled by default, so there's no need to change

anything unless you want to disable them. And they are

listed for reference purposes only. The items are: allow

client-to-client voice calls, set UDP port for voice call,


8/27


-8-

allow client-to-client video call, set UDP port for video

call.

Slide 9

Set up a telephony policy on the Sametime server, continued.

Go to Policies and click Sametime Default Policy. Scroll

down to the Integrated Sametime Connect section, and make

sure you turn on Allow all Sametime Connect Features to be

used with Integrated Clients.

Slide 10

Review LDAP settings on the Sametime server. To review the

LDAP settings on the Sametime server, log on to your

Sametime server's Web-based administration applet using the

fully qualified domain name of your Sametime server together

with a port value of 8088, which is the configured HTTP

listing port for your Domino server.

The Lotus Sametime Administration Menu page should be

displayed next, as can be seen on the picture on this slide.

Under the LDAP directory section, we will be looking at

connectivity, basics, authentication and searching menu

items for reference purposes only.

Slide 11

Review LDAP settings on the Sametime server, continued.

LDAP Directory Connectivity tab. As can be seen in this


9/27


-9-

image, the host name for the LDAP server is displayed, the

search order, which is one, the default port, which is set

at 389 and also the LDAP secure port, which is set at 636.

Slide 12


LDAP Directory Basics tab. The following image contains

some sample settings for a basic LDAP configuration. These

are given for reference purposes only.

Slide 13


LDAP Directory Authentication tab. The following image

shows typical settings for an LDAP server. This is given

for reference purposes only.

Slide 14


LDAP Directory Searching tab. The following image contains

typical settings for a standard LDAP server. These settings


Slide 15


LDAP Directory Group Contents tab. The following image

contains typical settings for a standard LDAP server. These



10/27


-10-

Slide 16

Verify the LDAP e-mail attribute is set to mail. The mail

attribute is important in the Sametime Unified Telephony

application as it is used internally to link the user's

e-mail address with provisioned users on the Telephony

Application Server. You can verify that the LDAP e-mail

attribute is set to mail, by either a) checking that the

Domino Notes.ini file contains the following parameter in

the Notes section: st_LDAP_email_attribute=mail.

Slide 17

Verify the LDAP e-mail attribute is set to mail, continued.

Option B: launch a Notes client that is connected to your

Domino server. Log in, and open the stconfig.nsf database.

Click the LDAP servers option on the lefthand panel.

Next, on the righthand panel, under the Network Address

Section, double click the Domino Sametime Server you are

currently using. The LDAP server settings will be

displayed.

Scroll down to the People section, and make sure that the

following lines contain the parameter mail. The attribute

of the person entry that defines the internal ID of a

Sametime user should be set to mail. Also the attribute of

the person entry that defines the person's e-mail address


11/27


-11-

should be set to mail.

Slide 18

Configuring a connection from Telephony Application Server

to Telephony Control Server, using the Common Management

Portal, or CPM for short.

Slide 19

Telephony Control Server background. The Telephony Control

Server -- or, TCS for short -- is a SIP Telephony Interface

server that provides the unified number facility that

informs the Telephony Application Server, or TAS for short,

about the receipt of a call for the unified number of a user

and also uses that unified number for any calls made by the

user, using the Sametime Connect client.

The Telephony Control Server converts the Computer Supported

Telecommunications Application -- or, CSTA -- commands from

the Telephony Application Server to the appropriate SIP

signaling on the soft switches, and/or SIP gateways to the

time division multiplexing-based private branch exchange, or

PBX for short.

The standard duplex Telephony Control Server is deployed via

a reference image on to two IBM System x3650 T servers.

This reference image contains default system configuration

data, for example OS parameters, UNIX accounts, nodes.cfg


12/27


-12-

file, et cetera, and a default database containing up to 10

SIP-to-SIP test subscribers, registered on one node.

A Telephony Control Server duplex server system supports up

to 100,000 subscribers, and a fully-equipped Sametime

Unified Telephony system will consist of one Telephony

Control Server running in duplex mode and seven Telephony

Application Servers, with one additional failover server,

which will be not active.

Slide 20

Telephony Control Server connections. Each Telephony

Application Server establishes a CSTA connection for call

control and also establishes a SOAP connection for

administrative purposes toward the Telephony Control Server

system.

The Telephony Control Server uses the media server for tones

and announcements and communicates with SIP soft switches

and SIP gateways via the SIP interface. The media server

also uses the SIP interface in case conferences are set up

by Telephony Application Server.

The Telephony Control Server Assistant, located under

Telephony Application Server communicates to the Telephony

Control Server via SOAP, as can be seen in the diagram on

this slide.


13/27


-13-

Slide 21

Configure a switch connection for your Telephony Application

Server. The Telephony Control Server Assistant does not

auto discover the Telephony Control Server, so a new switch

has to be configured to allow this to take place. To begin,

start your Telephony Application Server and log in to the

Common Management Portal, using an Internet Explorer

browser.

Next, click the Telephony Control Server tab. You should

see a section called List Switches. Click the Add button at

the bottom of the screen and the Configure Switch Addresses

dialog box is displayed, as can be seen on the image on this

slide.

Slide 22


Server, continued. From within the Configure Switch Address

dialog box, do the following: fill in the name field first.

Next, click the Cluster checkbox. Type the cluster IP

alias -- this is the IP address of your NMC assistant, VIP,

which is the cluster IP, which you would have configured in

the offline wizard utility, used to configure the node.cfg

file used during the Telephony Control Server installation.

Next, set the account field to SRX. Leave the


14/27


-14-

Synchronization Will Start field set to As Scheduled by

System. Please review the default settings in the picture

given on this slide.

Slide 23


Server, continued. In the Node 1 section, add the IP

address of your Telephony Control Server to the address of

switch field. Next, set the SRX password field to default

SRX1SRX password.

Next, click the Test Connection button. If it reports back

successful, then continue on to Node 2 for a duplex system,

and configure this panel and click the corresponding Test

Connection button.

If this test is successful as well, click Save at the bottom

of the dialog box. After a short delay, the connection

should be established and the public key for remote access

to the switch will have been transferred.

Slide 24

Check synchronization. It is important at this stage to

verify that the Telephony Application Server has

synchronized up with the Telephony Control Server. To

verify that this has happened, go to the Users and Resources

tab and click on the Resources section. Next, click on the


15/27


-15-

Office Codes section.

On the righthand side, you should see listed all the

available office codes that currently reside on your

Telephony Control Server. If you have configured office

codes on your Telephony Control Server and they are not

appearing at this stage, you will have to manually

synchronize the system.

To do this, select your Telephony Control Server tab. Next,

click on General. Next, click on Telephony Control Server

Settings. And then, Directory Number Uniqueness. Within

this dialog box, click on the Synchronize button. When this

operation has finished, click the Save button to finish the

synchronization task.

Slide 25

Configure CSTA connection from Telephony Applications Server

to the Telephony Control Server. From the Common Management

Portal, select the Operation and Maintenance tab, and then

click on Configuration and Monitoring.

Click your Telephony Control Server Configuration option,

and then your Telephony Control Server Connection option.

Click the Add button to launch your Telephony Control Server

connection dialog box. Please review the image on this

slide for more information.


16/27


-16-

Slide 26

Configure CSTA connection from Telephony Application Server

to the Telephony Control Server, continued. In the CSTA

Access Configuration Panel, enter your CSTA IP address and

set the port to 1040, which is the default port for CSTA.

Repeat this in the alternative field for your backup CSTA

connection.

Click the Save button to establish the connection. You

should be returned to the Telephony Control Server switch

connections panel, and your new switch should be visible.

Please refer to the image on this slide for more

information.

Slide 27

Verifying CSTA connection. To verify your CSTA connection,

launch a terminal session on your Telephony Application

Server Linux box. Enter in the following command on your

Telephony Application Server to verify that a connection has

been created from your Telephony Application Server to your

Telephony Control Server, and that the port in use is 1040.

The command to use is: netstat-an|grep1040. You should see

the following output on your screen, which will consist of

the TCP reference, the IP address that has been listened on,

the port and an established status.


17/27


-17-

Slide 28

Backup and Restore features within the Common Management

Portal.

Slide 29

Backup and Restore using the Common Management Portal. The

Common Management Portal offers the option to backup and

restore system configurations and system data. There are

two locations within the Common Management Portal to carry

out these tasks.

The first, relating to the Telephony Application Server, can

be located by clicking on the Operation & Maintenance menu

item. Next, click on Recovery. Next, click on Backup and

Restore or Import and Export.

The second location is for the Telephony Control Server, and

can be found on the Telephony Control Server tab, next click

on Maintenance, and next choose Import or Export. The

backups of the systems data and configurations are stored in

archives. Each archive can contain one or more backup sets.

The data and configurations are backed up in these backup

sets either automatically or manually.

The archive can be created locally on the server computer,

on another computer on the network, or on a computer which


18/27


-18-

has remote access to your system. And the main items that

can be found in the archive menu are as follows. You can

display archives, you can add to an archive, you can edit an

archive, you can clear an archive, you can test an archive,

or you can do display and clear an archive's backup set.

Slide 30

Creating a new archive, using the Common Management Portal

Telephony Application Server configuration. To create a new

archive, choose the domain you wish to work with, then

choose the Operation & Maintenance tab.

Next, choose the Recovery option, then on the left hand

panel, choose General. Click on Archives, and then click

the Add button to create a new archive. The picture

displayed on this slide shows a newly-created default

archive.

Slide 31

Backup sets. System configurations and system data can be

backed up in a backup set. Each archive can contain one or

more backup sets. If the number of backup sets saved

exceeds the value set for the archive, the oldest backup

sets are cleared. You can display all the backup sets

present in the system; or, alternatively, you can also have

all the backup sets for an archive displayed.


19/27


-19-

The list of backup units offered depends on the installed

applications, but generally you can expect the following

backup units to be available by default and these are listed

on the slides. Some of the more important ones are: Audit

Log files, Container Configuration files, Telephony Control

Server Backup, Licensed Management, lib-snmpdbaccess, which

relates to the SNMP traps sent during live operations and

stored in default management database. And also svc-

alarmhandler. Again, there's a bigger list available on the

slide itself.

Slide 32

Schedules. Schedules determine the times at which the

automatic backup jobs will be started. To set up a

schedule, select the domain you want from the Domain

Selection list.

On the main menu, choose Operation and Maintenance. Next,

click on the Recovery tab. On the left hand panel, choose

Backup and Restore. Next, click on Schedules. A list of

the available schedules appears on the right hand panel.

Options available are to add, edit or delete a schedule.

Slide 33

Job status. This option shows you information about the

last job performed. Such jobs can involve backup, restore,

or an import or export of data. You can also cancel


20/27


-20-

incomplete jobs at this stage. To avail of this option,

click on Operation & Maintenance from the main menu.

Next, click on the Recovery tab. Next, on the left hand

panel, click on the General option; and finally, click on

the Latest Job Status item for your chosen domain. The

picture displayed on this slide shows information about the

last performed job on a typical system.

Slide 34

Manual Backup of a Backup Set. It is also possible to save

the file system or a database manually. To do this, you

would select the domain you want from the domain selection

list.

Next, click Recovery under the Operation and Maintenance tab

in the main menu. Next, click on Backup. You should see

the Create Backup Set window. A backup set can only be

stored in one archive. To do this, either click Select, to

select an existing archive, or click Add to create a new

archive. If required, enter a comment for your backup set.

Next, click Continue. Select the backup units to be saved.

If you wish to make further changes to the archive, click

the Back button. If you wish to cancel the backup, click on

Cancel. Click the Start Backup button. A backup set with

the items that you have selected is stored in the archives


21/27


-21-

that you have specified. The progress of the backup

operation is also displayed.

Slide 35

Restoring a Backup Set. If you wish to manually restore a

file system, or a database from a saved backup set, please

do the following: select the domain you want from the Domain

Selection list. Next, choose the Recovery Item under the

Operation and Maintenance menu item.

Next, choose Restore. The Restore window should open.

Please note, a backup set can only be stored in one archive.

To perform the operation, either click on the button,

to select an existing archive, or click the Add button to

restore the name of an archive.

Once the archive is specified, click Continue. Select a

backup set from the list and click Continue. If you wish to

make further changes to the archive, click the Back button.

The backup units of the backup set are displayed. Select

the backup units that you wish to restore. If you wish to

cancel the Restore, click on the Cancel button. Finally,

click Start Restore to begin the operation. The progress of

the restoration is displayed on screen.

Slide 36

Telephony Control Server, specific import and export options


22/27


-22-

within the Common Management Portal. To navigate to the

Telephony Control Server, specific import and export

options, click on the Telephony Control Server main tab.

Then select the Maintenance option. You will see the Import

and Export options displayed on the left hand panel. Please

see the graphic on the slide for more information.

Slide 37

Telephony Control Server, specific import option. The

Import tab consists of two options. Option A, Telephony

Control Server Data. This option, which allows you to

import Telephony Control Server commands into a Telephony

Control Server system. Option B, Telephony Control Server

Assistant. This option allows the administrator to import

files containing the Assistant data.

Assistant data consists of items such as gateway URLs, URLs

to external applications, business group related defaults,

subscriber templates used for user management,

customer-specific remarks for the Telephony Control Server

entities, and endpoint templates.

These will be stored in three file types: type one being SQL

files, which represent each schema in the Assistant's

database. Type two, CTR files, which contain information

about each table's structures in every schema. Type three,

DAT files, containing the actual table data. It can also be


23/27


-23-

used as a base for database offline generation or to

configure an empty newly installed Assistant.

Slide 38

Import Option. Telephony Control Server Data. If you

choose this option, the following dialog box will be

displayed. You can import two file types on this dialog

box. The first import file contains the Telephony Control

Server Commands. The second file concerns the Deployment

and Licensing Server or DLS, for short.

The DLS server is a Telephony Control Server, central

inventory data management application for administering IP

devices, both SIP and HFA types. A DLS server is used for

the following: inventory management, configuration

management, software deployment, plug-and-play options and

user mobility. The latest version of DLS is version 2.

When you have entered the file names that you want, you just

click on the Import button at the bottom of the dialog box

to begin the operation.

Slide 39

Import Option. Telephony Control Server Assistant Data. If

you choose this option, the following dialog box will be

displayed: Import Assistant data allows a pre-prepared file

to be imported into the designated Telephony Control Server.


24/27


-24-

Select what type of data should be imported. If Telephony

Control Server specific data are selected, the user must

specify the Telephony Control Server system whose data is to

be used. When you have chosen your file type, click on the

Import button at the bottom of the dialog box to begin the

operation.

Slide 40

Telephony Control Server, Specific Export Option. The

Export tab consists of five options. They are:

Administration Data, Numbering Plan, ENUM Data, which is

Electronic or E164 Number Mapping, Full Configuration Data,

or Assistant Data.

Slide 41

Export Option. Telephony Control Server, Administration

Data. The Telephony Control Server administration data

option allows the user to export administration specific

data to a command file.

The data that can be exported consists of the following

items: office codes, directory numbers, routing areas,

destinations, endpoints, class of service, routes, media

gateway, media gateway circuits, intercept, treatment, SIP

reasons, alias, carrier destination, origin destination,

ENUM operators, ENUM servers, calling locations. To begin


25/27


-25-

this operation, you just click on the Export button at the

bottom of the screen.

Slide 42

Export Option. Telephony Control Server, Numbering Plan.

If you choose this option, the following dialog box will be

displayed: the Telephony Control Server numbering plan

allows the creation of a file that contains all the

necessary command statements, which allow the re-creation of

the original exported numbering plan.

In this dialog box, first select a business group to get a

list of the associated numbering plans. Then select one or

more of these numbering plans and hit the OK button to

export them.

Slide 43

Export Option. Telephony Control Server, ENUM. ENUM is a

protocol developed by the Internet Engineering Task Force --

or, IETF for short -- that provides the routing information

for calls and services from a single telephone number to a

variety of numbers and IP addresses for multiple devices.

When you choose this option, the following dialog box will

be displayed: click on the Export button to begin this

operation. The default file name, which will be generated

from this action, is EnumDataDxportFile.txt.


26/27


-26-

Slide 44

Export Option. All Telephony Control Server Configuration

Data. If you choose this option, the following dialog box

will be displayed: this option exports the full Telephony

Control Server configuration details to a command file.

There are two checkboxes on this dialog box. The first is:

Export file will be used for offline database re-generation,

and the second checkbox is for Export file using the old

Telephony Control Server format. The preferable way of the

exported data to be imported back to the database correctly

is by pressing the Export button without using the

checkboxes.

The type of data to be exported consists of the following:

business group, subscribers, endpoint, endpoint profile,

feature profile, numbering plan, office code, directory

number, routing area, class of service, calling location,

destination, authorization codes, route, alias, time

destinations, day schedule, period schedule, weekly

schedule, media gateway, media gateway circuits, origin

destination, origin route, carrier destination, carrier

route, CAC groups, MLHG, display number modifications, RTP

parameters. Click on the Export button to begin this

operation.


27/27


Slide 45

Export Option. All Telephony Control Server Assistant Data.

If you choose this option, the following dialog box will be

displayed: this feature allows the export of a file

containing the Assistant relevant data listed below as well

as the schema definition files for a successful recreation

of that data.

This consists of the following: CheSe Group Identification,

that is members and their secondary lines, URL of the DLS

server, gateway URLs, URLs to external applications,

business group related defaults, subscriber templates used

for user management, customer specific remarks for the main

Telephony Control Server entities, i.e., business groups,

subscribers, feature profiles, et cetera, and finally,

endpoint templates.

In the dialog box, select what type of data should be

exported. If Telephony Control Server specific data are

selected, the user must specify the Telephony Control Server

system whose data is to be used. When ready, click on the

Export button to begin the operation.

Documents

InitialTASConfiguration