Remote Feature Activation

Getting Started with Remote Feature

Activation (RFA)

03-300484
Issue 4.1
November 2007
 Contents

Chapter 1: Remote Feature Activation Overview . . . . . . . . . . . . . 7

RFA user requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
RFA Design configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
RFA Reliability and availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Registration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Registration for Avaya Associates . . . . . . . . . . . . . . . . . . . . . . . . 9
Registration for Avaya BusinessPartners . . . . . . . . . . . . . . . . . . . . 9
Group Authorization Identification (GAI) . . . . . . . . . . . . . . . . . . . 10
Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Feature Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Value types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Host IDs and serial numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
RFA Swap-Out functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Pre-installation and application readiness checklist . . . . . . . . . . . . . . . . 13
RFA help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 2: Important Product Information . . . . . . . . . . . . . . . . . 17

Advanced IP Phone Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Advanced IP Phone Features license file information . . . . . . . . . . . . . 19
Application Assurance Networking . . . . . . . . . . . . . . . . . . . . . . . . . 20
Application Assurance Networking license file information . . . . . . . . . . 21
Application Design Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
RFA licensed ADE components . . . . . . . . . . . . . . . . . . . . . . . . . 23
ADE license file information . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Application Enablement (AE) Services. . . . . . . . . . . . . . . . . . . . . . . . 25
Upgrading to AE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Upgrading CVLAN R9 to AE. . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Upgrading DEFINITY LAN Gateway to AE . . . . . . . . . . . . . . . . . . . . 26
CVLAN Server 9.0 for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
RFA licensed AE applications . . . . . . . . . . . . . . . . . . . . . . . . . . 27
AE license file information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Avaya IQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Host ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Avaya IQ licensing information . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Avaya Proactive Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Host ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Avaya Proactive Contact licensing information . . . . . . . . . . . . . . . . . 31
Branch Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Issue 4.1 November 2007 3

Contents

The serial number for the G250 or G350 Media Gateway . . . . . . . . . . . . 34

Post installation verification . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Activating the VPN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Branch Gateway license file information. . . . . . . . . . . . . . . . . . . . . 35
Communication Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Applications under the Communication Manager product family . . . . . . . 36
IP connect to Multi-Connect migration changes . . . . . . . . . . . . . . . . 36
Serial numbers for Communication Manager . . . . . . . . . . . . . . . . . . 37
Working with authentication files. . . . . . . . . . . . . . . . . . . . . . . . . 37
DEFINITY upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
DEFINITY migrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Communications Process Manager . . . . . . . . . . . . . . . . . . . . . . . . . 39
Host ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Communications Process Manager licensing information . . . . . . . . . . . 40
Customer Interaction Express . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
CIE licensing information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Directory Enablement Management . . . . . . . . . . . . . . . . . . . . . . . . . 44
Host ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Directory Enablement Management licensing information . . . . . . . . . . . 45
Enterprise Network Management Console. . . . . . . . . . . . . . . . . . . . . . 45
Host ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
NMC license file information . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Event Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Host ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Event Processor Licensing Information . . . . . . . . . . . . . . . . . . . . . 46
Integrated Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Integrated Management license file information . . . . . . . . . . . . . . . . 48
Interaction Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
E-mail license request and IC . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
IC license file information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Meeting Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Meeting Exchange license file information . . . . . . . . . . . . . . . . . . . 53
Modular Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Host ID information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Post installation verification . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Modular Messaging license information . . . . . . . . . . . . . . . . . . . . . 54
one-X Mobile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
one-X Mobile licensing information . . . . . . . . . . . . . . . . . . . . . . . 56
one-X Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

4 Getting Started with Remote Feature Activation (RFA)

 Contents

one-X Portal licensing information . . . . . . . . . . . . . . . . . . . . . . . . 56

Operator Set PC (OSPC). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
OSPC licensing information . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Security Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Security Gateway models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Security Gateway license file information . . . . . . . . . . . . . . . . . . . . 60
SIP Enablement Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
SIP Enablement Services module type. . . . . . . . . . . . . . . . . . . . . . 61
Post installation verification . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
SIP Enablement Services license file information . . . . . . . . . . . . . . . . 61
Softclients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Softclients Host ID information . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Softclients license file information . . . . . . . . . . . . . . . . . . . . . . . . 62
Unified Communication Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
UCC Host ID information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
UCC license file information . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Voice Self Service (VSS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
VSS Host ID information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
VSS license file information. . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Issue 4.1 November 2007 5

Contents

6 Getting Started with Remote Feature Activation (RFA)

Chapter 1: Remote Feature Activation Overview

Remote Feature Activation (RFA) is a web-based application that is used to create and deliver
license files for Avaya products. The license files are created using information from the
customer and the SAP order.The SAP ordering information can be entered directly into SAP or
Avaya and Avaya BusinessPartners can use the Order Messaging/OA Price Tool.

RFA user requirements

To meet the requirements to access RFA you must:
l Be one of the following:
- An Avaya associate or designee with a valid Avaya HRID number. This requirement also
includes the Variable Workforce associates.
- An approved BusinessPartner with a valid BusinessPartner number.
- An approved Avaya contractor. This individual typically works for Avaya without a valid
HRID number.
l Have a computer equipped with:
- Internet Explorer 5.0 or later
- 128 bit encryption
- Internet access to the RFA web site
- The supported monitor resolution of 800 X 600

Issue 4.1 November 2007 7

Remote Feature Activation Overview

l Be registered and authenticated for each of the Avaya products in which you wish to
create or modify a license file:
- To be registered means you have been given a SSO (Single Sign On) login and are
identified in the RFA database.
- To be authenticated means that your coach or your Avaya Group Authorization
Identification (GAI) manager has approved your access to RFA. For information on what
a GAI is see Group Authorization Identification (GAI) on page 10.

RFA Design configuration

RFA does not provide design configurations. Avaya configurations must continue to be
engineered using the existing tools and processes. The RFA process begins with an approved
and accurate SAP order. A correct SAP order is key to the successful creation of the license file.

RFA Reliability and availability

RFA has been designed for high reliability and high availability. RFA is normally available 24
hours a day, seven days a week. However, please be aware that there are factors that exist that
will limit RFA availability for up to twelve hours at a time. These factors include maintenance,
interactions with other systems that are not available, etc. The times for scheduled RFA outages
are posted on the RFA Information page at http://rfa.avaya.com. Please check the RFA
Information page regularly for the most current information.
Note:
Note: It is highly recommended that you create a license file as soon as you have all
the needed information. Do not wait until the day of installation to obtain the
license file.

Registration information
This section explains how to register for RFA for Avaya Associates and BusinessPartners.

8 Getting Started with Remote Feature Activation (RFA)

 Registration information

Registration for Avaya Associates

To log on to RFA you must have a valid Single Sign On (SS0) login and password. The SSO
system provides access security for many Avaya applications, including RFA. You do not have
to register for a SSO login if you are an Avaya associate.

! Important:
Important: Check your personal information in RFA for accuracy. Make sure your POST
information is correct.
Complete the following steps to register in RFA for a product family:
1. Access the RFA web site at http://rfa.avaya.com. This link takes you to the SSO login site.
2. After you enter your SSO login and password the RFA Information page appears.
3. Click Register to Use RFA for a product family.
4. Select the product family from the drop-down menu:
- Select the job function that most closely resembles the job function that you perform. You
can find a detailed description for each job function on the RFA Information page under
the RFA Job Function Descriptions link.
- Complete the required information and click Submit.
- Your coach automatically receives an e-mail that must be approved before you can
become an RFA user.

Registration for Avaya BusinessPartners

To log onto RFA you must have a valid Single Sign On (SS0) login and password. The SSO
system provides access security for many Avaya applications, including RFA.
Make sure that your business card information is correct. The business card information is the
same as your SSO information. Ensure that your e-mail address is accurate. You can update
this information from the SSO login screen.
Complete the following steps to register for a product family:
1. Access the RFA web site at http://rfa.avaya.com. This link takes you to the SSO login site. If
you already have a SSO login, enter your login and password. If you do not have a SSO
login, click New User and complete the required information.
After you enter your SSO login and SSO password the system displays the RFA Information
page.
2. Click Register to Use RFA for a product family and select the product family from the
menu:

Issue 4.1 November 2007 9

Remote Feature Activation Overview

3. Select one of the following user types:

- Tier 1 BusinessPartner if you purchase directly from Avaya.
- Tier 2 BusinessPartner if you purchase from a Tier 1 BusinessPartner.
- Contractor if you are a contractor working for Avaya and do not have an Avaya HRID
number.
4. Enter a Group Authorization Identification (GAI) number. Click Show GAI Name to verify
that you entered the correct GAI. For more information on GAI, see Group Authorization
Identification (GAI) on page 10.
5. Enter the e-mail address that your company provided to Avaya to receive the RFA
generated e-mail. RFA uses this e-mail address to e-mail your request to access RFA to
your company. Avaya must receive a reply to the e-mail before you can become an
authenticated RFA user.

Group Authorization Identification (GAI)

A GAI is a unique number assigned to each BusinessPartner in RFA. This number is included
on the system record of each license. A BusinessPartner must have their GAI on a system
record in order to access it. The GAI for a Tier II BusinessPartner is available from the Tier I
BusinessPartner. During the creation of a system record, the Tier I BusinessPartner must
include the Tier II BusinessPartner’s GAI. Should a BusinessPartner require access to a system
record that does not contain their GAI, they can complete a form called Transfer System
Record to a Different BP located on the RFA Information page.

Training
The detailed instructions on how to use RFA for each product family can be found in the Avaya
Remote Feature Activation (RFA) User Guide located at http://support.avaya.com. You should
read the RFA User Guide shortly before an upcoming installation to ensure you can apply the
knowledge that you obtained.

10 Getting Started with Remote Feature Activation (RFA)

 Feature Keywords

Feature Keywords
RFA creates a license file based on the material codes that appear in the SAP order. RFA maps
between the SAP material codes and the features and capacities in the license file. While the
license file does not contain the material codes themselves, it does contain the features and the
capacities that will be activated for the system. The features and capacities are represented by
Feature Keywords. Feature Keywords are English text that uniquely identify which features and
capacities to activate. A list of Feature Keywords for each RFA supported product, except
Communication Manager, can be found in Chapter 2: Important Product Information on
page 17. For a complete listing of the Communication Manager Keywords see the RFA
Information page at http://rfa.avaya.com.

Value types
Each feature, feature capacity, or customer entitlement, falls into one of the following types.
l Type I: The Type I Features table contains the software features that are entitlements and
the features that are purchased by the customer. Type I features have an on and off, or a
yes and no setting.
l Type II: The Type II Features table contains features that have a value or capacity. For
some Feature Keywords, the Setting column can be used to set the value for the Feature
Keyword.
l Type III: The Type III Features Table contains registration features that have a product ID,
a release, and a capacity setting.

Host IDs and serial numbers

RFA uses either the Host ID or the serial number to identify the Avaya product. Each Host ID or
serial number must be unique within its product group and therefore can only be used once. You
may use the same Host ID or serial number for multiple RFA licenses if the licenses are created
for different products.

Issue 4.1 November 2007 11

Remote Feature Activation Overview

For products using WebLM as their licensing server, the Host ID of the WebLM server is used in
RFA. For information on how to obtain the Host ID of your server, see Table 1.

Table 1: Host ID information table

Operating Command Description

System

Windows ipconfig/all A 12 digit hexadecimal physical

address is shown. Remove the
hyphens before entering the
address in RFA.
AIX /usr/bin/uname -m An eight digit hexadecimal Host ID
is returned.
Linux /sbin/ifconfig -a | grep HWaddr A 12 digit hexadecimal HWaddr is
returned. Remove the colons
before enter the address in RFA
Solaris ifconfig -a An eight digit hexadecimal Host ID
is returned.

Note:
Note: If WebLM is already installed on the server, you can display the primary Host ID
of your server after you log into WebLM by clicking Server Properties.

RFA Swap-Out functionality

The RFA Swap-Out functionality is used when a licensed server needs to be replaced. The
Swap-Out functionality creates a new RFA system record that contains the new Host ID or the
serial number.
All RFA supported products use the Swap-Out functionality. For Communication Manager and
Branch Gateways an authenticated user can perform the swap-out. For all other RFA supported
products, the RFA Swap-Out functionality can only be performed by a Tier III Avaya Global
Services associate. Use the following information to contact an Avaya support center:
l Avaya technician call 1-800-248-1234
l Avaya BusinessPartner call 877-295-0099
l For international please refer to the following URL to locate your international support
center: http://support.avaya.com/japple/css/
japple?PAGE=OpenPage&temp.template.name=Support_Countries

12 Getting Started with Remote Feature Activation (RFA)

 Pre-installation and application readiness checklist

Pre-installation and application readiness checklist

Table 2 contains information that you need to obtain before accessing RFA to create or update a
license file.

Table 2: Readiness checklist

Item Completed

SAP order number

Host ID or serial number
RFA Transaction number or activity
Email address of person receiving license file (if applicable)
SID (if this is an addition or an upgrade)
Complete Tier I, Tier II, and end-user customer information

Issue 4.1 November 2007 13

Remote Feature Activation Overview

RFA help
There may be times when you need help with RFA or with a RFA license file. The organization
that you call for help depends on the type of problem you are experiencing. Table 3 shows
examples of the types of problems for which each Helpdesk provides support.

Table 3: Who to call for support

Organization What they support

The IT Helpdesk l The RFA application, such as:

- SSO logins and passwords
- RFA navigational support such as
screens, error messages, and so on.
- Mistakes made in the RFA system record
such as using the wrong SAP order
number or the wrong serialized hardware
component in the system record.
l Problems with the SAP order number or
creation of the transaction record.
l Downloading the FET or LIT
l Problems with system records such as
creating, locating, and accessing a system
record.
The Avaya Services Helpdesk The license file or the authentication file(s) such
as:
l Getting the license file in to the Avaya
product including reading the error
messages and providing solutions
l FET and/or LIT interactions with DEFINITY
l License-Error mode and No-License Mode
l The inability to connect to DEFINITY using
Connect2

! Important:
Important: If you are having trouble with the RFA application, or creating a license file or an
authentication file, call the IT Helpdesk. If you need help installing a license or an
authentication file, or if you are having trouble with a license or an authentication
file that is already installed, call the Avaya Services Helpdesk.

14 Getting Started with Remote Feature Activation (RFA)

 RFA help

Table 4 shows the Helpdesk group to contact and the Helpdesk’s contact information for RFA
application support.

Table 4: IT Helpdesk information

Groups Contact

l United States and Canada l For urgent matters call 866-282-2948 or

Avaya associates (303)354-8999.
l Members of one of the l For less urgent matters with an expected 48
Variable Workforce Groups hour (or more) response time send an e-mail
l Avaya Contractors message to [email protected].
l Avaya BusinessParters
l All international callers l No language support: 866-282-9248 or
(303)345-8999
l Language support: Contact your regional
support center. Support center contact
information see http://support.avaya.com/
japple/css/
japple?PAGE=avaya.css.OpenPage&temp.te
mplate.name=Escalations_Global

Issue 4.1 November 2007 15

Remote Feature Activation Overview

16 Getting Started with Remote Feature Activation (RFA)

Chapter 2: Important Product Information

This chapter explains how the following product families work with RFA:
l Advanced IP Phone Features on page 18
l Application Assurance Networking on page 20
l Application Design Environment on page 23
l Application Enablement (AE) Services on page 25
l Avaya IQ on page 29 (formally CCR)
l Avaya Proactive Contact on page 31
l Branch Gateways on page 33
l Communication Manager on page 35
l Communications Process Manager on page 39
l Customer Interaction Express on page 40
l Directory Enablement Management on page 44
l Enterprise Network Management Console on page 45
l Event Processor on page 46
l Integrated Management on page 47
l Interaction Center on page 49
l Meeting Exchange on page 52
l Modular Messaging on page 53
l one-X Mobile on page 55
l one-X Portal on page 56
l Operator Set PC (OSPC) on page 57
l Security Gateway on page 58
l SIP Enablement Services on page 60
l Softclients on page 62
l Unified Communication Center on page 63
l Voice Self Service (VSS) on page 65

Issue 4.1 November 2007 17

Important Product Information

Advanced IP Phone Features

Advanced IP Phone Features is a release of firmware for the Avaya 4600 series IP phone that is
comprised of the Avaya IP Phone application and a VPN client. The Avaya 4600 phone uses
the VPN client to establish a secure IPSec tunnel for all traffic including signalling, media and
application. The use of the phone is controlled by the number of concurrent user licenses that
are managed by a WebLM application residing on a WebLM server. After the VPN tunnel is
established, the phone must obtain a license from the WebLM server. Once the phone obtains a
license it is allowed to register with Communication Manager.
Advanced IP Phone Features uses WebLM as a licensing server. The Host ID of the WebLM
server is used in RFA as a unique identifier. For information on how to identify the Host ID of
your server, see Host IDs and serial numbers on page 11.

18 Getting Started with Remote Feature Activation (RFA)

 Advanced IP Phone Features

Advanced IP Phone Features license file information

Table 5 shows information that you will need to know to create a license file for Advanced IP
Phone Features.

Table 5: Advanced IP Phone Features license Information table

New Installs

Swap-Outs
Additions

RFA Feature Keyword Description RFA Feature Keywords Value

Type

X X X REGISTRATION is used for concurrent REGISTRATION 3

use of IP endpoint registration features
within the server. This feature is a type
3 feature and will have a quantity
associated with it. If the feature setting
is MAX than the setting for this feature
is at its allowed maximum.
FEAT_ENTERPRISE activates the FEAT_ENTERPRISE 1
enterprise licensing on the WebLM
server. This feature is a type 1 feature
with a on or off setting. When this
feature is set to ’ON’, the WebLM
server acts as the master WebLM
server. A master WebLM server is
used for administration of local WebLM
servers and can be used to generate
allocation license files for enterprise
licensing.

Issue 4.1 November 2007 19

Important Product Information

Application Assurance Networking

Application Assurance Networking is a Linux-based application that runs on specific
configurations of IBM eServer xSeries 306 and 336 platforms. Application Assurance
Networking performs the following functions:
l Identifies the applications running on the network.
l Monitors the quality of service (QoS) provided by the network to each application session
over a specific network path.
l Determines an alternate network path providing a greater QoS.
l In real-time, reroutes application sessions to better performing paths, without the
applications or the users being aware of the reroute.
Currently there is only one application under the Application Assurance Networking product
family that is licensed by RFA.
Application Assurance Networking uses WebLM as a licensing server. The Host ID of the
WebLM server is used in RFA as a unique identifier. For information on how to identify the Host
ID of your server, see Host IDs and serial numbers on page 11.

20 Getting Started with Remote Feature Activation (RFA)

 Application Assurance Networking

Application Assurance Networking license file information

Table 6 shows information that you will need to know to create a license file for Application
Assurance Networking.

Table 6: Application Assurance Networking license file information table

Support Updates
New Installs

Swap-Outs
Upgrades
Additions

RFA Feature Keyword RFA Feature Keywords Value

Description Type

X X X X X Reporting Only mode enabled, VALUE_AAN_CNA 2

web application model

Web application reporting only VALUE_AAN_CNA_TIER 2

tier
Route Assert mode enabled VALUE_AAN_APC 2

Route Assert tier VALUE_AAN_APC_TIER 2

VoIP application model VALUE_AAN_VOIP 2
configurable

VoIP tier VALUE_AAN_VOIP_TIER 2

1 of 2

Issue 4.1 November 2007 21

Important Product Information

Table 6: Application Assurance Networking license file information table (continued)

Support Updates
New Installs

Swap-Outs
Additions

Upgrades
RFA Feature Keyword RFA Feature Keywords Value
Description Type

Enterprise application model VALUE_AAN_ENT 2

configurable

Enterprise tier VALUE_AAN_ENT_TIER 2

Real-time multimedia app VALUE_AAN_MMED 2
model configurable

Multimedia tier VALUE_AAN_MMED_TIER 2

Streaming audio and video VALUE_AANSTRM 2
app model configurable

Streaming audio and video tier VALUE_AANSTRM_TIER 2

Load table entries enabled VALUE_AAN_WCO 2

Load table entries tier VALUE_AAN_WCO_TIER 2

2 of 2

22 Getting Started with Remote Feature Activation (RFA)

 Application Design Environment

Application Design Environment

Application Design Environment (ADE) is the product family name within RFA. Dialog Designer
(DD) is the only application under the ADE product family that requires an RFA license.
There are two major components of DD:
l A development environment that runs on a PC.
l A run-time component that runs on a web container on a web server.
The run-time component is the only component of DD that is licensed in RFA.

! Important:
Important: When the Dialog Designer CTI Connector is used through the Application
Enablement Services JTAPI/TSAPI interface, the appropriate number of
Application Enablement VALUE_TSAPI_USERS must be set. This setting may
cause a change in the Application Enablement product family license. The
correct number of VALUE_TSAPI_USERS that you enable is based on the
number of supported VRU channels that use CTI simultaneously.

RFA licensed ADE components

Table 7 shows a list of what is being licensed by RFA for ADE.

Table 7: ADE licensed components

Product family Application name in What is being licensed?

application description RFA

ADE Dialog Designer l The Dialog Designer

standalone package
l The Computer Telephony
Integration (CTI) library
enablement
l The Computer Telephony
Integration (CTI) library
universal enablement
l The IC library enablement
l The IC library universal
enablement

Issue 4.1 November 2007 23

Important Product Information

ADE license file information

ADE uses WebLM as a licensing server. The Host ID of the WebLM server is used in RFA as a
unique identifier. For information on how to identify the Host ID of your server, see Host IDs and
serial numbers on page 11.
Table 8 shows that you will need to know to create a license file for ADE.

Table 8: Application Design Environment license file information table

Support Update
New Installs

Value Type
Swap-Out
Additions

Upgrade

RFA Feature Keyword RFA Feature Keywords

Description

X X X X X DD standalone package: VALUE_DD_UNIVERSAL 2

Allows customers without
an Avaya IR or VP
platform to run Dialog
Designer applications.
CTI library enablement: VALUE_DD_CTI_LIBRARY 2
Allows Avaya IR/VP
customers who have
purchased the CTI
connector to interface
with the CTI server
through Dialog Designer
applications.
CTI library universal VALUE_DD_CTI_LIBRARY_ 2
enablement: Allows UNIVERSAL
customers who don’t have
an IR/VP platform, but do
have an Avaya CTI
system to use the CTI
connector in Dialog
Designer to interface with
their CTI system(s).
1 of 2

24 Getting Started with Remote Feature Activation (RFA)

 Application Enablement (AE) Services

Table 8: Application Design Environment license file information table (continued)

Support Update
New Installs

Value Type
Swap-Out
Additions

Upgrade
RFA Feature Keyword RFA Feature Keywords
Description

IC library enablement: VALUE_DD_IC_LIBRARY 2

Allows Avaya IR/VP
customers who have
purchased the IC
connector to interface
with their IC system
through Dialog Designer
applications.
IC library universal VALUE_DD_IC_LIBRARY_ 2
enablement: Allows UNIVERSAL
customers who don’t have
an IR/VP system, but who
have an Avaya IC system,
to use the IC connector in
Dialog Designer to
interface with their IC
system(s).
2 of 2

Application Enablement (AE) Services

! Important:
Important: CVLAN is called Application Enablement (CTI) in RFA. Application Enablement
(CTI) is the new name in RFA for the products formerly known as Computer
Telephony Integration (CTI).

Issue 4.1 November 2007 25

Important Product Information

Upgrading to AE
You can upgrade to AE from a:
l Non-RFA windows platform (Avaya CT)
l CVLAN R9
l DEFINITY LAN Gateway (DLG):
- Upgrades from DLG co-resident on Communication Manager to AE are supported.
- Upgrades from a MAPD board to DLG are not supported.
An Upgrade to AE is considered a new install. You must invoke the new install functionality in
RFA to perform the upgrade.

Upgrading CVLAN R9 to AE
Use the following process to upgrade CVLAN R9 to AE:
1. Obtain the existing System Identification Number (SID) of the CVLAN R9 to be upgraded to
AE.
2. Call the help desk.
3. The help desk:
- Checks the SID to verify that the RFA record is assigned to a CVLAN R9.
- Executes the AE Conversion script that converts the CVLAN R9 system record to an AE
system record.

Upgrading DEFINITY LAN Gateway to AE

DEFINITY LAN Gateway (DLG) can be installed on a MAPD board or co-resident on the same
server as Communication Manager. When DLG is co-resident with Communication Manager, an
upgrade to AE is considered a new install in RFA. There is no upgrade path to AE for a DLG on
a MAPD board.
Note:
Note: Communication Manager Release 3.0 does not support co-resident DLG.

26 Getting Started with Remote Feature Activation (RFA)

 Application Enablement (AE) Services

CVLAN Server 9.0 for Linux

CVLAN is an Application Programming Interface (API) that allows applications to communicate
with Avaya Communication Manager. The communication path between the CVLAN server and
the Communication Manager server is made up of one or more ASAI links.
The CVLAN operating environment includes the following:
l CVLAN client
l CVLAN server running Linux 9.0
l Communication Manager server
CVLAN Client: The CVLAN client software runs on a workstation or a server and provides
access to the Communication Manager server by way of the CVLAN server. You can obtain the
CVLAN client software from the Avaya web site. You do not need an RFA license file for the
CVLAN client software. Refer to Avaya CVLAN Server for 9.0 Linux Installation and Basic
Administration Guide for information on the downloading the CVLAN client software.
CVLAN server: The CVLAN server software runs on a Linux based PC and manages ASAI
traffic between the Communication Manager server and the CVLAN client. The CVLAN server
requires an RFA license file.

RFA licensed AE applications

Table 9 shows what is being licensed for the applications that are in the AE product family.

Table 9: AE applications license information

Product family Application name in What is being licensed

application description RFA

MVAP Server Application Number of connections

Enablement
Connections
CallVisor LAN CVLAN l Application
l Number of connections
l Proprietary links
DEFINITY LAN Gateway DLG Application
Telephony Services API TSAPI l Application
l Number of users
l Number of advanced users

Issue 4.1 November 2007 27

Important Product Information

AE license file information

AE uses WebLM as a licensing server. The Host ID of the WebLM server is used in RFA as a
unique identifier. For information on how to identify the Host ID of your server, see Host IDs and
serial numbers on page 11.
Table 10 shows information that you will need to know to create a license file for AE.

Table 10: AE license file information table

New Installs/Migrations

Value Type
Swap-Out
Additions

RFA Feature Keyword RFA Feature Keywords for AE

Descriptions

X X X Application Enablement VALUE_AEC_VERSION 2

Connections Version
Application Enablement VALUE_AEC_CONNECTIONS 2
Connections
CVLAN VALUE_CVLAN 2
CVLAN Version VALUE_CVLAN_VERSION 2
CVLAN Proprietary Links VALUE_PROPRIETARY_LINKS 2
CVLAN Switch Connections VALUE_SWITCH_CONNECTIONS 2
DLG VALUE_DLG 2
TSAPI Version VALUE_TSAPI_VERSION 2
TSAPI Simultaneous Users VALUE_TSAPI_USERS 2
TSAPI Simultaneous VALUE_TSAPI_ADVANCED_USERS 2
Advanced Users

28 Getting Started with Remote Feature Activation (RFA)

 Avaya IQ

Avaya IQ
! Important:
Important: Avaya IQ is formally CCR. Avaya IQ does not display in the list of product families
in RFA. Select CCR from the product family list to create or modify a license file
for Avaya IQ.
Avaya IQ provides the existing features of the Communication Management System (CMS)
while adding the following capabilities:
l Web based reporting
l Platform Choice
l Extensible Database
l Blending of Proactive Contact and CMS
l Greater capacity
An RFA license file is needed for Avaya IQ when you perform one of the following actions:
l New installations
l Additions
l Swap-out: A swap-out is performed when the hardware that was used for the Host ID in
the RFA license file needs to be changed out for maintenance purposes. A swap-out
allows the user to enter a new Host ID and obtain a replacement license file.
l Support Updates
l Upgrades
l Migrations

Host ID
Avaya IQ uses WebLM as a licensing server. The Host ID of the WebLM server is used in RFA
license file as a unique identifier. For more information on how to identify the Host ID of the
WebLM server, see Host IDs and serial numbers on page 11.

Issue 4.1 November 2007 29

Important Product Information

Avaya IQ licensing information

Table 11 shows information that you will need to know to create a license file for Avaya IQ.

Table 11: Avaya IQ licensing information

Keyword Description Keyword Value

Type

Number of concurrent agents VALUE_CCR_AGENTS 2

Number of concurrent report VALUE_CCR_REPORT_USERS 2
users
Historical Data Export FEAT_CCR_HIST_DATAEXPORT 1
Realtime Data Export package A FEAT_CCR_REAL_DATAEXPORT_A 1
Realtime Data Export package B FEAT_CCR_REAL_DATAEXPORT_B 1
Realtime Data Export package C FEAT_CCR_REAL_DATAEXPORT_C 1
Number of Communication VALUE_CCR_CM_EVENTINPUTS 2
Manager data resources
Number of Proactive Contact VALUE_CCR_PC_EVENTINPUTS 2
data sources
Enable Enterprise Licensing FEAT_ENTERPRISE 1
Note:
Note: This feature activates
enterprise licensing on the
WebLM server. If this feature
is set to on, the WebLM
server acts as a master and
allows the administration of
local WebLM servers.

30 Getting Started with Remote Feature Activation (RFA)

 Avaya Proactive Contact

Avaya Proactive Contact

Avaya Proactive Contact is a software and hardware product that provides a high performance
predictive dialing functionality for calls centers for both inbound calls and outbound with
blending.
An RFA license file is needed for Avaya Proactive Contact when you perform one of the
following actions:
l New installations
l Additions
l Swap-out: A swap-out is performed when the hardware that was used for the Host ID in
the RFA license file needs to be changed out for maintenance purposes. A swap-out
allows the user to enter a new Host ID and obtain a replacement license file.
l Support Updates
l Upgrades

Host ID
Avaya Proactive Contact uses WebLM as a licensing server. The Host ID of the WebLM server
is used in RFA license file as a unique identifier. For more information on how to identify the
Host ID of the WebLM server, see Host IDs and serial numbers on page 11.

Avaya Proactive Contact licensing information

Table 12 shows information that you will need to know to create a license file for Avaya
Proactive Contact.

Table 12: Avaya Proactive Contact licensing information

Keyword Description Keyword Value

Type

Number of agents VALUE_APC_TOTAL_AGENTS 2

Number of agents with predictive VALUE_APC_PREDICTIVE_AGENTS 2
dialing
1 of 2

Issue 4.1 November 2007 31

Important Product Information

Table 12: Avaya Proactive Contact licensing information (continued)

Keyword Description Keyword Value

Type

Number of Supervisor VALUE_APC_SUPERVISORS 2

Workstations
Number of Telephone Lines VALUE_APC_PHONELINES 2
Number of CTI agents VALUE_APC_TOTALCTIAGENTS 2
Number of CTI agents with VALUE_APC_PREDICTIVECTIAGENTS 2
predictive dialing
2 of 2

32 Getting Started with Remote Feature Activation (RFA)

 Branch Gateways

Branch Gateways
The G250 and the G350 media gateways are the only RFA supported gateways in the Branch
Gateways product family. License file requirements for the G250 and the G350 media gateway
vary depending on the configuration.
Use the information in Table 13 to determine when an RFA license file is needed.

Table 13: Branch Gateways information table

G250/G350 Configuration RFA license required?

A Standalone G250 or a G350 without Virtual Private No.

Networking (VPN).
A standalone G250 or a G350 with VPN. Yes. You need one RFA license
file to activate VPN.
A standalone G250 or G350 with an S8300 Media Yes. You need one RFA license
Server. file for Communication Manager.
A standalone G250 or G350 is with an S8300 Media Yes. You need two RFA license
Server and VPN. files:
l One for Communication
Manger
l One to activate the VPN
feature
The G250 or G350 is remotely controlled by a server. No.
The G250 or G350 does not have VPN.
The G250 or the G350 is remotely controlled by a server. Yes. You need one RFA license
The G250 or the G350 has an S8300 Media Server file for the LSP.
acting as an LSP.
The G250 or the G350 is remotely controlled by a server. Yes. You need two RFA license
The G250 or the G350 has an S8300 Media Server files:
acting as an LSP and has VPN. l 1 for the LSP
l 1 for the VPN

Issue 4.1 November 2007 33

Important Product Information

The serial number for the G250 or G350 Media Gateway

Each Branch Gateway has a license file that contains a unique serial number. The same serial
number cannot be used more than once within the Branch Gateways product family. When the
G250 or the G350 has VPN and a S8300 Media Server, you need two license files. In this case,
the serial number of the G250 or the G350 can be used for both license files because each
license file is created in a different product group. In this example, the G250 or the G350 with
VPN is licensed in the Branch Gateway product family while the S8300 Media Server is licensed
in the Communication Manager product family.
To identify the G250 or the G350 serial number type, show sys from the command line
interface.

Post installation verification

If you attempt to load a license file with a serial number that does not match the serial number of
the new G250 or the G350 media gateway:
l The license file fails to install
l A SNMP notification is sent
l A message is written in the Syslog

Activating the VPN

After you load the license file, you must perform a reset on the G250 or the G350 media
gateway to activate VPN. A feature setting of 1 indicates that VPN is turned on. A feature setting
of 0 (zero) indicates VPN is turned off.

34 Getting Started with Remote Feature Activation (RFA)

 Communication Manager

Branch Gateway license file information

Table 14 shows information that you will need to know to create a license file.

Table 14: Branch Gateway license file information table

New Installs/Migrations

Swap-Out
Additions

RFA Feature Keyword RFA Feature Keywords Value

Descriptions Type

X X X Virtual Private Networking VALUE_VPN 2

Platform VALUE_PLATFORM 2

Communication Manager
A separate license file is required for each of the following Avaya servers:
l DEFINITY Server R, SI, and CSI (starting with release 10)
l DEFINITY ONE or IP600 (starting with release 10)
l Media servers:
- S8100
- S8300
- S8500
- S8700 series servers
l WAN Spare Processor (WSP)
l Survivable Remote Processor (SRP)
l Local Survivable Processor (LSP)
l Enterprise Survivable Server (ESS)
Note:
Note: An Avaya system that is equipped with a duplicated processor only requires one
license file. This license file contains the serial number for both processors.

Issue 4.1 November 2007 35

Important Product Information

Communication Manager requires a license file when you are performing one of the following:
l An installation or a migration
l An addition
l A support update
l An upgrade
l A server or processor swap-out
A list of Feature Keywords and Feature Keyword descriptions can be found in the DEFINITY/
MultiVantage/Avaya Communication Manager and Audix Feature Keywords document at
http://rfa.avaya.com.

Applications under the Communication Manager product family

There are several applications that may appear in an SAP order when creating a license file for
Communication Manager. Currently the applications are:
l Communication Manager
l Call Center
l Audix
Applications appear in the following RFA tabs:
l SAP Order tab: Applications are listed in the Detailed Feature Information.
l Assign Order Items tab
l Module/App Details tab
l Features tab
To view the applications in the Module/App Details and the Features tab, use the drop-down
menu to select the application. A screen appears with the information for that application.

IP connect to Multi-Connect migration changes

RFA 10.3 contains the following enhancements for systems migrating from IP connect to
Multi-Connect and upgrading to Communication 4.0 or later:
l A migration from IP connect to Multi-Connect does not involve a hardware change,
therefore a new serial number is not needed and will not be allowed in RFA.
l The Platform Type changes in the module record.

36 Getting Started with Remote Feature Activation (RFA)

 Communication Manager

Note:
Note: The migration from IP to Multi-Connect and the upgrade to Communication
Manager Release 4.0 or later, must be on the same material code.

Serial numbers for Communication Manager

You can find the serial number for Communication Manager in one of the following ways:
l Hardware: All Communication Manager servers and IPSI boards have the serial number
printed on a label found in the front or the back of the hardware.
l Firmware: Serial numbers can also be identified through the firmware of the server or IPSI
board.
l RFA (DEFINITY only): RFA provides a method to retrieve serial numbers on Avaya
DEFINITY servers.
For more information on how to find the serial number for a Communication Manager server,
see The Remote Feature Activation (RFA) User Guide at http://support.avaya.com.

Working with authentication files

In addition to the license file, Avaya servers that use an open operating system require an
authentication file. The authentication file contains non-default passwords and Access Security
Gateway (ASG) keys for the Avaya services logins. When you create an RFA system record for
an Avaya system Release 11 and later, RFA automatically creates an authentication file.
Note:
Note: The Avaya DEFINITY servers do not run on an open operating system and
therefore do not require an authentication file.
Note:
Note: For the S8100 Media Server Release 10 or earlier, the Automatic Registration
Tool (ART) is used to generate the authentication file. ART is available to Avaya
associates or the regional registration teams.

Issue 4.1 November 2007 37

Important Product Information

! CAUTION:
CAUTION: If you are going to request a new authentication file, you must be logged in to the
server before you request the new ASG key. If you are not logged in to server you
will be locked out and will not have access to the server.

DEFINITY upgrades
DEFINITY upgrades may consist of one of the following:
l An upgrade:
- From a DEFINITY Release 4 to a DEFINITY Release 9
- From a DEFINITY release to a Communication Manager release
l A DEFINITY server that is upgrading within the same platform. Platforms for DEFINITY
include the CSI, the SI, the R, the DEFINITY ONE, and the IP600.
Note:
Note: The Feature Extraction Tool (FET) must be used to extract features from a
DEFINITY server that is upgrading to Release 10 or later. For more information
on FET, see The Remote Feature Activation (RFA) User Guide at
http://support.avaya.com.

DEFINITY migrations
A DEFINITY migration may consist of one of the following:
l DEFINITY ONE to S8700 IP Connect
l DEFINITY ONE to DEFINITY CSI
l DEFINITY ONE to DEFINITY SI
l DEFINITY G3i, s, or vs, to DEFINITY CSI
l DEFINITY G3i, si, or vs, to DEFINITY SI
l DEFINITY G3d, G3i, or G3si, to DEFINITY R
l DEFINITY G3s, G3i, or G3si, to S8700 Multi-Connect
l DEFINITY R to S8700 Multi-Connect
l Any system that is currently at pre Version 4 upgrading to a Communication Manager
release
l Upgrades from pre Release 4 to a Release 10

38 Getting Started with Remote Feature Activation (RFA)

 Communications Process Manager

Note:
Note: DEFINITY migrations cannot use FET to extract existing features. Instead the
GES configurator provides tracking or migration codes that carry forward optional
features and capacities previously purchased to the new system record and
license file. When the account team requests a DEFINITY migration in the GES
configurator, they manually identify and input the existing features. The
configurator produces an output containing both existing features and new
capabilities on a single SAP order.

Communications Process Manager

Communications Process Manager is available in Phase A and Phase B. The following
information provides a high-level description of Phase A and Phase B:
l Phase A provides a generalized click-to-call service for one or more parties using Avaya’s
Crystal 1.5 conference bridge.
l Phase B includes reference services that provide the following services:
- Advisory Service
- Notify and Response Service
- Fire and Call
- Exception Conference Service
- Notify with Task Lists Service
The above feature set requires Crystal R1.5 Conference Bridge and Avaya’s Voice Portal
R3.1.
An RFA license file is needed for Communications Process Manager when you perform one of
the following actions:
l New installations
l Additions
l Swap-out: A swap-out is performed when the hardware that was used for the Host ID in
the RFA license file needs to be changed out for maintenance purposes. A swap-out
allows the user to enter a new Host ID and obtain a replacement license file.
l Support Updates
l Upgrades

Issue 4.1 November 2007 39

Important Product Information

Host ID
Communications Process Manager uses WebLM as a licensing server. The Host ID of the
WebLM server is used in RFA license file as a unique identifier. For more information on how to
identify the Host ID of the WebLM server, see Host IDs and serial numbers on page 11.

Communications Process Manager licensing information

Table 15 shows information that you will need to know to create a license file for
Communications Process Manager.

Table 15: Communications Process Manager licensing information

Keyword Description Keyword Value

Type

Communications Platform VALUE_CPM_COMMUNICATIONS_PLATFORM 2

Communications Users VALUE_CPM_COMMUNICATIONS_USERS 2
Advisory Service FEAT_CPM_ADVISORY_SERVICE 1
Notify and Response FEAT_CPM_NOTIFY_RESPONSE_SERVICE 1
Service
Find and Call Service FEAT_CPM_FIND_CALL_SERVICE 1
Notify with Task List Service FEAT_CPM_NOTIFY_TASKLIST_SERVICE 1
Notify and Conference FEAT_CPM_NOTIFY_CONFERENCE_SERVICE 1
Service
Crisis Management Service FEAT_CPM_CRISIS_MANAGEMENT_SERVICE 1

Customer Interaction Express

Customer Interaction Express (CIE) is a Contact Center application residing on a Microsoft
based application server. CIE delivers a suite of Contact Center functionality including the
following features:
l Soft ACD

40 Getting Started with Remote Feature Activation (RFA)

 Customer Interaction Express

l E-Mail Routing
l Graphical Vectors
l Skill Based Routing
l IVR
l Soft Dialer
l Real-time and historical Contact Center reporting

Tip:
Tip: Customers may migrate from Business Contact Center (BCC) to CIE. Migrating
from BCC to CIE requires an RFA license file. The New Install procedure in RFA
is used to generate the license file for the migration.

! Important:
Important: Currently, orders for CIE that are placed in the Tenovis SAP (Atlas) box are not
visible to RFA. Orders placed in Tenovis SAP require a manual RFA process to
generate a license file. To kick off the manual process, the SAP order information
should be provided to the KSPA group who handles most of the Tenovis license
requests.

CIE licensing information

CIE uses WebLM as a licensing server. The Host ID of the WebLM server is used in RFA as a
unique identifier. For information on how to identify the Host ID of your server, see Host IDs and
serial numbers on page 11.
Table 16 shows information that you need to know to create a license file for CIE.
.
Table 16: CIE license information table
New Installs

Value Type
Swap-Out
Additions
Upgrades

RFA Keyword Description RFA Keywords

X X X X Number of concurrent inbound VALUE_CIE_CC_USER_VOICE 2

voice user
1 of 4

Issue 4.1 November 2007 41

Important Product Information

Table 16: CIE license information table (continued)

New Installs

Value Type
Swap-Out
Additions
Upgrades
RFA Keyword Description RFA Keywords

Number of concurrent outbound VALUE_CIE_CC_PREVIEW_USR 2

preview user
Number of concurrent outbound VALUE_CIE_CC_AUTODIALER_ 2
autodialer user USER
Number of concurrent outbound VALUE_CIE_CC_PROGRESSIVE 2
progressive dialer user _USER
Number of concurrent e-mail user VALUE_CIE_CC_USER_ 2
NONVOICE
2 of 4

42 Getting Started with Remote Feature Activation (RFA)

 Customer Interaction Express

Table 16: CIE license information table (continued)

New Installs

Value Type
Swap-Out
Additions
Upgrades
RFA Keyword Description RFA Keywords

Number of concurrent user with VALUE_CIE_CC_MONTELUSER 2

extended voice features
Number of concurrent team leaders VALUE_CIE_CC_TEAMLEADER 2
Number of concurrent supervisors VALUE_CIE_CC_SUPERVISOR 2
Number of concurrent service VALUE_CIE_CC_SERVUSER 2
users
Number of concurrent user with VALUE_CIE_CC_BLCCON 2
integration interface
Number of concurrent TRS user VALUE_CIE_CC-TRS 2
Number of CIE ports VALUE_CIE_IVR_PORT 2
Number of CIE IVR systems VALUE_CIE_IVR_CON 2
Number of CIE TTS ports VALUE_IVR_TTSPORT 2
Number of CIE ASR ports VALUE_CIE_IVR_ARSPORT 2
Number of CIE TTS language ports VALUE_CIE_IVR_TTSLANG 2
Enablement of Texttemplates for VALUE_CIE_CC_TEXTMODULES 2
users
Number of CLIP entries in DB VALUE _CIE_CC_CLIP 2
Number of ACM Switches VALUE_CIE_CC_PX_ACM 2
connected
Number of I55 Switches connected VALUE_CIE_CC_PX_I55 2
Number of nonvoice media phone VALUE_CIE_CC_MEDIA_LINE 2
lines
Enablement of SMTP Connector FEAT_CIE_CC_SVC_SMTP 1
for Mail
Enablement of Faxrouting FEAT_CIE_CC_SVC_FAX 1
Enablement of SMS Routing FEAT_CIE_CC_SVC_SMS 1
3 of 4

Issue 4.1 November 2007 43

Important Product Information

Table 16: CIE license information table (continued)

New Installs

Value Type
Swap-Out
Additions
Upgrades
RFA Keyword Description RFA Keywords

Enablement of Skills Based FEAT_CIE_CC_SBR 1

Routing
Enablement of Extended CallFlow FEAT_CIE_CC_EXTUI 1
Editor
Enablement of CGI Scripts of FEAT_CIE_CC_CGI 1
Dialer
Enablement of SPOP Server FEAT_CIE_CC_SPOP 1
4 of 4

Directory Enablement Management

An RFA license file is needed for Directory Enablement Management when you perform one of
the following actions:
l New installation
l Additions
l Upgrades
l Swap-out: A swap-out is performed when the hardware that was used for the Host ID in
the RFA license file needs to be changed out for maintenance purposes. A swap-out
allows the user to enter a new Host ID and obtain a replacement license file.
l Support upgrades

Host ID
Directory Enablement Management uses WebLM as a licensing server. The Host ID of the
WebLM server is used in RFA license file as a unique identifier. For more information on how to
identify the Host ID of the WebLM server, see Host IDs and serial numbers on page 11.

44 Getting Started with Remote Feature Activation (RFA)

 Enterprise Network Management Console

Directory Enablement Management licensing information

Table 17 shows information that you need to know to create a license file for Directory
Enablement Management.

Table 17: Directory Enablement Management license information table

Keyword Keyword description Value type

VALUE_DEM_DSM Concurrent directory connections 2

Enterprise Network Management Console

An RFA license file is needed for Enterprise Network Management Console (NMC) when you
perform one of the following actions:
l New installation
l Swap-out: A swap-out is performed when the hardware that was used for the Host ID in
the RFA license file needs to be changed out for maintenance purposes. A swap-out
allows the user to enter a new Host ID and obtain a replacement license file.
l Upgrades

Host ID
NMC uses WebLM as a licensing server. The Host ID of the WebLM server is used in RFA
license file as a unique identifier. For more information on how to identify the Host ID of the
WebLM server, see Host IDs and serial numbers on page 11.

Issue 4.1 November 2007 45

Important Product Information

NMC license file information

Table 18 shows information that you need to know to create a license file for NMC.

Table 18: NMC license information table

Keyword Keyword description Value type

FEAT_NMC Enterprise Network Management Console 1

Event Processor
An RFA license file is needed for Event Processor when you perform one of the following
actions:
l New installation
l Additions
l Upgrades
l Swap-out: A swap-out is performed when the hardware that was used for the Host ID in
the RFA license file needs to be changed out for maintenance purposes. A swap-out
allows the user to enter a new Host ID and obtain a replacement license file.
l Support upgrades

Host ID
A Host ID is used to license Event Processor. The Host ID of the server on which Event
Processor is installed will be used. Event Processor uses a WebLM license but does not use a
WebLM server.

Event Processor Licensing Information

Table 19 shows information that you need to know to create a license file for Event Processor.

46 Getting Started with Remote Feature Activation (RFA)

 Integrated Management

Table 19: Event Processor licensing Information table

Host ID used

RFA Keyword Description RFA Keywords Value

Type

X Event Processor Distributed Processing FEAT_EP_DIST_ 1

feature PROCESSING
Event Processor Input Data Source VALUE_EP_INPUT_ 2
The number of input data sources licensed. DATA_SRC
Event Processor Output Data Stream VALUE_EP_OUTPUT_DATA_ 2
The number of output data sources STRM
licensed.

Integrated Management
RFA supports the following application within the Integrated Management product family:
l VoIP Monitoring Manager (VMM): An RFA license file is required for VoIP Monitoring
Manager 3.0 or later. VMM versions earlier than 3.0 do not require an RFA license file.
Refer to Table 20 for information on applications licensed by RFA for Integrated Management.

Table 20: Integrated Management applications

1RFAApplication Name for Integrated What is being licensed
Management

Integrated Management Monitoring l Application (3.0 or later)

Solutions l Number of endpoints:
- Up to 2000
- Additional 2000
l Gateways:
- Up to 40
- Additional 40
1 The RFA Application Name is the name that represents Integrated Management within RFA.

Issue 4.1 November 2007 47

Important Product Information

On new installations of Integrated Management, an SAP order is used to enable the minimum
quantities for both endpoints and gateway capacity. The RFA New Install capability is used to
create a system record and generate a license file.
For additional endpoint and gateway capacity, a SAP order is required. Endpoints and gateways
are bundled together in quantities of 2,000 endpoints and 40 gateways. The RFA Additions
capability is used to add the new capacity and generate a new license file.

Integrated Management license file information

Table 21 shows information that you need to know to create a license file for Integrated
Management.

Table 21: Integrated Management license file information table

New Installs/Migrations

Support Update

Swap-Out
Additions

Upgrade

Host ID RFA Feature RFA Feature Value

Host ID

information Keyword Keywords Type

Description

X For Integrated X X X X X VoIP Monitoring VALUE_VMM_ 2

Management, Manager (VMM) VERSION
a Host ID is Version
the Media
Access Maximum Number
Control VALUE_VMM_ 2
of Endpoints
Address ENDPOINT
(MAC) of the
first ethernet Maximum Number
of Gateways VALUE_VMM_ 2
port (eth0) on GATEWAY
the WebLM
server

Note:
Note: The number of gateways and the number of endpoints are calculated separately.
Additional quantities must be purchased if a customer exceeds either the
maximum purchased endpoints or managed gateways.

48 Getting Started with Remote Feature Activation (RFA)

 Interaction Center

Interaction Center
RFA is used to obtain a license file for Interaction Center (IC) when:
l IC is purchased with Release 6.1.3 or later.
Note:
Note: When IC is purchased with Release 6.1.3 or later, the Interaction Center
Operational Analyst (IC/OA) Price Tool version 3.4 or later is required.
l IC is used in a production environment. If IC is being used for demonstration or evaluating
purposes, an RFA license is not needed.
l A single WebLM (one Host ID) environment is being used.
l A permanent license is needed.
l A change in the Host ID is needed. In this case the RFA Swap-Out functionality is used to
create a new license file containing the new Host ID.
Note:
Note: If your Avaya IC system includes multiple sites, or a redundant multi-server
solution, you need a series of segmented licenses. Each segmented license is
specific to a WebLM application in your Avaya IC system. In these situations,
RFA is not used to generate a license file. When RFA is not used to license IC,
the E-mail License Request process at [email protected] is used.

E-mail license request and IC

Use the existing E-mail License Request process when:
l IC is being used in a non-production environment. In this case IC uses a development and
test license.
l IC was purchased with release 6.0.X through 6.1.2, or you are upgrading IC from a earlier
release.
l Multiple WebLM applications are used requiring multiple segmented licenses.
l The customer is evaluating IC.
l IC contains a temporary license.
Note:
Note: An Operational Analyst (OA) license can be requested by the E-mail License
Request process.

Issue 4.1 November 2007 49

Important Product Information

IC license file information

Table 22 shows information that you need to know to create a license file for IC.

Table 22: Interaction Center license file information table

New Installs/Migrations

Support Update

Swap-Out
Additions

Upgrade
Host ID RFA Feature RFA Feature Value
Host ID

information Keyword Keywords Type

Description

X The Host ID X X X X X Max num users VALUE_ 2

is the Media concurrently TOTALAGENTS
Access logged into IC
Control
Address Max num users for
(MAC) of VALUE_ 2
inbound voice
the first channel media INBOUNDVOICE
ethernet AGENTS
port (eth0)
on the
server.
Max num users for VALUE_ 2
email media EMAILAGENTS
channel
VALUE_WEB 2
Max num users for AGENTS
web media
channel
1 of 3

50 Getting Started with Remote Feature Activation (RFA)

 Interaction Center

Table 22: Interaction Center license file information table (continued)

New Installs/Migrations

Support Update

Swap-Out
Additions

Upgrade
Host ID RFA Feature RFA Feature Value
Host ID

information Keyword Keywords Type

Description

PeopleSoft FEAT_ 1
connector enabled PEOPLESOFT
SERVER
Sibel 7 Connector
enabled FEAT_SIBLE7GW 1

Sibel 2000
Connector
enabled FEAT_ 1
SIBLE2000GW
Max num of VALUE_ 2
content analysis CONTENT
servers ANALYSISVRS
Business FEAT_BUSINESS 1
Advocate feature
enabled ADVOCATE

Max num VALUE_SOFT 2

Softdialer agents DIALERSVRS

Max num VALUE_SOFT 2

Softdialer servers DIALERSVRS
2 of 3

Issue 4.1 November 2007 51

Important Product Information

Table 22: Interaction Center license file information table (continued)

New Installs/Migrations

Support Update

Swap-Out
Additions

Upgrade
Host ID RFA Feature RFA Feature Value
Host ID

information Keyword Keywords Type

Description

Outbound feature FEAT_SOFT 1

of import list DIALERIMPORT
enabled LIST

Outbound feature FEAT_SOFT 1

of predictive
dialing enabled DIALER
PREDICTIVE
Max num Avaya VALUE_TS 2
switch servers DEFINITYSVRS

Max num Aspect VALUE_TS 2

switch servers ASPECTSVRS
Max num Nortel VALUE_TS 2
Meridian switch
servers MERIDIAN

Max num Nortel VALUE_TS 2

Symposium switch SYMPOSIUM
servers SVRS

3 of 3

Meeting Exchange
Meeting Exchange Groupware Edition is shipped pre-configured to the customer. The assembly
and test team is responsible to obtain the license file from RFA and load the license on to the
Meeting Exchange server.
A unique Host ID is required to license each instance of Meeting Exchange. For help in finding
the Host ID on your Meeting Exchange server, see the Avaya Remote Feature Activation (RFA)
User Guide located at http://support.avaya.com.

52 Getting Started with Remote Feature Activation (RFA)

 Modular Messaging

RFA supports the following application within the Meeting Exchange product family:
l Groupware Edition

Meeting Exchange license file information

Table 23 shows information that you need to know to create a license file for Meeting Exchange.

Table 23: Meeting Exchange license file information table

New Installs/Migrations

Support Update

Swap-Out
Additions

Upgrade

Host ID RFA Feature RFA Feature Value

Host ID

information Keyword Keywords Type

Description

X For Meeting X X X X X Number of Meeting VALUE_MXGE_ 2

Exchange, the Exchange G711_CODEX
Host ID is the Groupware Edition
Media Access G.711 CODEX
Control supported.
Address
(MAC) of the Number of Meeting
first ethernet Exchange VALUE_MXGE_ 2
port (eth0) on Groupware Edition PORTS
the Meeting ports.
Exchange
server.

Modular Messaging
An RFA license is required for the following Modular Messaging features:
l Seats: The number of voice mail-enabled mailboxes that are being licensed.
l Text-to-Speech/engine type/language: The number and type of concurrent sessions of
test-to-speech conversion that is being licensed.
l Platform: Messaging platform that is being licensed. Different versions of Modular
Messaging work with Avaya, Microsoft, and IBM/Lotus messaging stores.

Issue 4.1 November 2007 53

Important Product Information

Host ID information
For Modular Messaging the Host ID is the voice mail domain identifier. The Host ID may be
alpha/numeric and can be up to 50 characters in length. The format for a Modular Messaging
Host ID is:
<8 hex char>-<4 hex char>-<4 hex char>-<4hex char>-<12 hex char>
Note:
Note: Modular Messaging does not distinguish between upper and lower case letters.
Note:
Note: For information on how to find the Host ID for Modular Messaging, see The
Remote Feature Activation (RFA) User Guide at http://support.avaya.com.

Post installation verification

If the Host ID in the RFA license file does not match the Host ID in the Modular Messaging
system, the License import Wizard in VMSC fails. The system displays a message that states
that the license is not valid. The Windows event log on MAS, through which the import was
requested, also contains an error event that says "The license does not refer to this system.
Please obtain a new license."

Modular Messaging license information

Table 24 shows information that you need to know to create a license file for Modular
Messaging.

54 Getting Started with Remote Feature Activation (RFA)

 one-X Mobile

Table 24: Modular Messaging license file information table

New Installs/Migrations

Support Update

Swap-Out
Additions

Upgrade
Host ID RFA Feature RFA Feature Value
Host ID

information Keyword Keywords Type

Description

X Modular X X x X X Platform VALUE_PLATFORM 2

Messaging
Host IDs are Modular VALUE_MM_SEATS 2
known as Messaging
voice mail Mailboxes
domain
identifier
outside of Text to speech, VALUE_TTS_ 2
RFA. ScanSoft
RealSpeak, Any REALSPEAK_ANY
Language

Text to speech,
Fonix, DECtalk VALUE_TTS_ 2
US English DECTALK_EN_US

Text to speech,
Scansoft VALUE_TTS_ 2
TTS-3000 TTS3000_INT
International

one-X Mobile
one-X Mobile is a software application supporting multiple client types in a client/server
environment. one-X Mobile communicates through AES to Communication Manager.
An RFA license file is needed for the following actions:
l New installs
l Upgrades and updates
l Additions
l Swap-Outs

Issue 4.1 November 2007 55

Important Product Information

one-X Mobile licensing information

Table 25 shows information that you need to know to create a license file for one-X Mobile.

Table 25: one-X Mobile license file information table

Host ID used

RFA Feature Keyword Descriptions RFA Feature Keywords Value

Type

X Maximum number of one-X Mobile VALUE_ONEXM_USERS 2

administered users.

one-X Portal
One-X Portal provides a web access point to Avaya servers such as:
l IP telephony
l Modular Messaging
l Mobility (EC 500)
l Meeting Exchange conferencing
One-X Portal is easy to install, can be managed centrally, and works without a VPN client
installation on the PC desktop. One-X Portal users are able to support remote workers by way
of remote call control of an Avaya Communication Manager station or a VoIP connection.

one-X Portal licensing information

Table 26 shows information that you need to know to create a license file for one-X Portal.

56 Getting Started with Remote Feature Activation (RFA)

 Operator Set PC (OSPC)

.
Table 26: one-X Portal license file information table
Host ID used
New Installs

Swap-Out
Additions
Upgrades

RFA Feature RFA Feature Keywords Value

Keyword Type
Descriptions

X X X X X Maximum number of VALUE_ONEXPORTAL_USERS 2

one-X Portal
configured users
Maximum number of VALUE_ONEXPORTAL_HA_USERS 2
one-X Portal high
availability configured
users.1
1 This feature is reserved for future use.

Operator Set PC (OSPC)

OSPC is a PC based attendant console for Communication Manger that runs on XP, Server
2003, and the Vista operating system. OSPC provides a high integration into customer’s
workflow with two different modes: road warrior and telecommuter.
An RFA license file is needed for the following actions:
l New installs
l Upgrades and updates
l Additions
l Swap-Outs

Issue 4.1 November 2007 57

Important Product Information

OSPC licensing information

Table 27 shows information that you will need to know to create a license file for OSPC.

Table 27: OSPC licensing information

Keyword Description Keyword Value

Type

OSPC client licenses VALUE_OSPC_CLIENT 2

OSPC connection to FEAT_OSPC_EXTERNAL_DB 1
external data bases
OSPC absence info from FEAT_OSPC_CAL_ABSENCE_OUTLOOK_NOT 1
calendar (outlook) ES
OSPC absence info from FEAT_OSPC_ABSENCE_ASSIST_EXCHANGE 1
absence assist (Exchange)
OSPC absence info from FEAT_OSPC_ABSENCE_WEB_TOOL 1
web tool
OSPC Network wide busy FEAT_OSPC_NBA_GENERAL 1
lamp
OSPC Network wide busy VALUE_OSPC_NBA_STATIONS 1
lamp number of stations
OSPC use of PUM users FEAT_OSPC_PUM_USERS 1

Security Gateway
Avaya ships the Security Gateway product family with a default license file. An Avaya Security
Gateway does not require an RFA license file unless additional capabilities are added.
Additional capabilities include increasing the number of site-to-site connections and remote
users.
Since the Security Gateway unit is shipped with a default license file the Security Gateway does
not have a corresponding system record in RFA. When you add additional capabilities for the
first time, use the New Install option in the RFA Application Main Menu. After the system record
is created in RFA, use the RFA Additions functionality to create any future license files.

58 Getting Started with Remote Feature Activation (RFA)

 Security Gateway

When you create a license file, the RFA system record reflects only the additional capabilities
contained in the SAP order. RFA does not reflect the default settings. You can use the RFA
Features screen to view the additional capacities. The Security Gateway combines both the
capabilities of the default settings and the capabilities in the license file. Table 28 shows an
example of a Security Gateway with increased capabilities.

Table 28: Security Gateway example

Scenario Site-to-Site Remote

Connections Users

The default settings of the Security Gateway 25 50

The additional capabilities from the SAP order 10 30
RFA system record reflects this total 10 30
Security Gateway provides this total capability 35 80

Security Gateway models

Avaya requires a RFA license file on the following Security Gateway Solutions models:
l SG5 Security Gateway
l SG5X Security Gateway
l SG200 Security Gateway
l SG203 Security Gateway
l SG208 Security Gateway
Note:
Note: An RFA license is not required for Security Gateway unless you are adding
additional site-to-site connections or remote users that are above the default
entitlements.

Issue 4.1 November 2007 59

Important Product Information

Security Gateway license file information

Table 29 shows information that you need to know to create a license file for Security Gateway.

Table 29: Security Gateway license file information

New Installs/Migrations
Serial Number

Swap-Out
Additions

RFA Feature Keyword RFA Feature Keywords Value

Description Type

X X X X Site-to-site Remote Users VALUE_SITETOSITE 2

Number of Remote Users VALUE_REMOTEUSERS 2

SIP Enablement Services

SIP Enablement Services integrates with Communication Manager to extend a set of
SIP-based software services and SIP registration for:
l All current endpoints
l SIP endpoints
l Third-party applications
Most often, the SIP Enablement Services application requires SIP Trunking activated on the
host Communication Manager server. Avaya Communication Manager, Release 2.0 and later,
integrates with SIP Enablement Services as a telephony feature server to SIP-based endpoints.
The SIP Enablement Services solution typically requires two RFA license files: One for the
Communication Manager host server, to activate SIP trunking, and one for the SIP Enablement
Services server.

60 Getting Started with Remote Feature Activation (RFA)

 SIP Enablement Services

SIP Enablement Services module type

There is a single module type for SIP Enablement Services. The module type for SIP
Enablement Services is SES_Main.

Post installation verification

If the Host ID of the server and the Host ID within the license file do not match, the SIP
Enablement Services server enters in to a license-error mode. The SIP Enablement Services
server can run in a license-error mode for up to 10 days. Service is not affected while the server
is in the license-error mode. If the problem that created the license-error mode is not corrected
after the 10 days, the SIP Enablement Services server ceases to operate.

SIP Enablement Services license file information

Table 30 shows information that you need to know to create a license file for SIP Enablement
Services.

Table 30: SIP Enablement Services license file information

New Installs/Migrations

Support Update

Swap-Out
Additions

Upgrade

Host ID RFA Feature RFA Feature Value

Host ID

information Keyword Keywords Type

Description

X For SIP X X X X X Number of Edge VALUE_EDGE_ 2

Enablement Proxy seats PROXY
Services, a
Host ID is the Number of Basic
Media VALUE_BASIC_ 2
Proxy seats PROXY
Access
Control
Address Number of Client VALUE_CLIENTS 2
(MAC) of the seats
first ethernet
port (eth0) on
the server.

Issue 4.1 November 2007 61

Important Product Information

Softclients
The Softclients product family contains one RFA licensed application that is named SIP
Softphone.
Over a SIP, the Avaya SIP Softphone is a PC-based endpoint enabling users to:
l Initiate and receive calls
l Send and receive instant messages
There are three supported SIP softphone configurations:
l Avaya SIP Infrastructure (Converged Communications Server): When the Avaya SIP
Softphone operates in a CCS environment, the SIP Softphone communicates using TLS
with Avaya CCS 2.x and later. The SIP Softphone implements features as per IETF RFC
3261, IETF drafts for message-waiting indication, and a subset of the SIPPING 19 features
(where applicable). For more information on CCS see SIP Enablement Services on
page 60.
l Non-Avaya SIP Proxy, registrar, and endpoints: When the Avaya SIP Softphone operates
in a non-Avaya SIP Proxy environment, it communicates using TCP and UDP with other
vendor’s SIP proxies, registrar, and endpoints. The SIP Softphone implements the
SIPPING 19 (where applicable).
l No SIP Infrastructure (Peer-to-Peer): When the Avaya SIP Softphone is installed in an
environment where no proxies are used, SIP Softphone provides basic telephony and IM
functionality when communicating directly with another Avaya SIP Softphone.

Softclients Host ID information

The Host ID that is used for Softclients is the MAC address of the first Network Interface Card
(NIC) on the WebLM server. The Host ID may consist of:
l Numbers and letters
l Up to 50 characters in length
l Upper and lower case letters
l Some special characters

Softclients license file information

A license for SIP Softphone contains the maximum number of SIP Softphones that can be
running at one time. Once the maximum number is obtained, a user attempting to start a new
session receives an error message that directs them to contact their support organization.

62 Getting Started with Remote Feature Activation (RFA)

 Unified Communication Center

There is a single module type for Softclients. The name for the module type is SIPSP_Main.
Table 31 shows information that you need to know to create a license file for Softclients.

Table 31: Softclients license file information table

New Installs/Migrations

Swap-Out
Additions

RFA Keyword Description RFA Keywords Value

Host ID

Type

X X X X IP Endpoint Registration REGISTRATION 3

Unified Communication Center

Unified Communication Center (UCC) consists of a suite of applications. Each application uses
the UCC License Server to obtain a license that allows the UCC application to run. The UCC
applications are:
l Avaya Web Messaging Application (WMA)
l Avaya Web Collaboration Application (WCA)
l Avaya Advanced Speech Access (ASA)
A UCC License Server software is a product called Avaya License Manager. The RFA license
file is installed on the UCC License Server. If the customer purchases the Web Messaging
Application (WMA) or the Web Collaboration Application (WCA), then the UCC License Server
is the UCC Base Server. If the customer purchases only the Advanced Speech Access (ASA)
application, then the UCC License Server is the ASA Server (UCC Speech Server).
The UCC license file contains feature settings for the following:
l For the Web Messaging and Web Collaboration applications:
- Number of seats: The number of people who can use each UCC application at the same
time.
- Expiration date

Issue 4.1 November 2007 63

Important Product Information

l For the Advanced Speech Access application:

- Number of seats
- Expiration date
- Number of Automatic Speech Recognition ports
- Number of Text-to-Speech sessions

UCC Host ID information

For UCC the Host ID is the MAC address of the first Network Interface card in the UCC license
server. If the customer purchases the:
l Web Messaging Application (WMA) or the Web Collaboration Application (WCA), the Host
ID is the MAC address of the first Network Interface Card (NIC) in the UCC Base Server.
l Advanced Speech Access (ASA) application only, the Host ID is the MAC address of the
first NIC in the ASA Server. The ASA server is also referred to as the UCC Speech Server.

64 Getting Started with Remote Feature Activation (RFA)

 Voice Self Service (VSS)

UCC license file information

Table 32 show information that you need to know to create a UCC license file.

Table 32: UCC license file information table

New Installs/Migrations

Swap-Out
Additions
Upgrade

RFA Keyword Description RFA Keywords Value

Type

X X X X Number of Adv. speech resource VALUE_ASR_PORTS 2

ports

Number of Text to Speech ports VALUE_TTSPORTS 2

Number of seats VALUE_SEATS 2

Number of switch connections VALUE_SWITCH_ 2

CONNECTIONS

Text to speech, ScanSoft RealSpeak, VALUE_TTS_REALSPEAK 2

any language _ANY

Maximum ports VALUE_PORT 2

Node locking FEAT_NODELOCK 1

Voice Self Service (VSS)

The Voice Self Service (VSS) product family contains two applications that require an RFA
license file:
l Interactive Response
l Voice Portal

Issue 4.1 November 2007 65

Important Product Information

VSS Host ID information

VSS uses the MAC address of the first Network Interface Card (NIC) on the WebLM server for
licensing. The Host ID can contain:
l Numbers or letters
l Up to 50 characters in length
l Upper and lower case letters
l Some special characters

VSS license file information

Table 33 shows information that you need to know to create a license file for VSS.

Table 33: VSS license file information table

Support Update
Host ID used
New Installs

Swap-Out
Upgrades
Additions

RFA Keyword Description RFA Keywords Value

Type

X X X X X X This Feature Keyword FEAT_ENTERPRISE 1

enables the Enterprise
Licensing feature on the
WebLM server
1 of 2

66 Getting Started with Remote Feature Activation (RFA)

 Voice Self Service (VSS)

Table 33: VSS license file information table (continued)

Support Update
Host ID used
New Installs

Swap-Out
Additions

Upgrades RFA Keyword Description RFA Keywords Value

Type

Number of IR ports VALUE_IR_PORTS 2

Number of ASR ports VALUE_IR_ASR_ 2
PORTS
Number of Test to Speech VALUE_IR_TTS_ 2
ports PORTS
Number of servers with VALUE_IR_SNMP 2
SNMP enabled
Maximum number of VALUE_VP_PORTS 2
concurrent telephony ports
Maximum number of ASR VALUE_VP_ASR_ 2
connections CONNECTIONS

2 of 2

Issue 4.1 November 2007 67

Important Product Information

68 Getting Started with Remote Feature Activation (RFA)

Glossary

F
Feature Keywords See Feature Keywords on page 11. RFA uses Feature Keywords to identify
features
FSO Field Service Organization

G
GAI See Group Authorization Identification (GAI) on page 10.

L
License File Encrypted file that activates features and capacities

P
POST Avaya’s internal directory web resource.
Product family Identifies the Avaya product line such as Avaya Communication Manager and
Branch Gateways.

R
RFA Remote Feature Activation. See Chapter 1: Remote Feature Activation
Overview on page 7.
RFA IBM Helpdesk Navigational, escalation and SSO password support for the RFA application.
RTU Right-to-use

S
SAP Avaya’s ordering system for products and services.
Serial numbers A serial number of the Avaya hardware is used to create a valid license file. The
hardware serial number and the serial number within the license file must
match.
Swap-Out RFA functionality used to create a new license file for maintenance.
SSO Single Sign-On is the Avaya corporate mechanism requiring a single login to
allow users access to certain web sites.
System Record An RFA record for each licensed Avaya product.

Issue 4.1 November 2007 69

Tier I BusinessPartner

T
Tier I A BusinessPartner that has a direct purchasing relationship with Avaya
BusinessPartner (Distributor).
Tier II A BusinessPartner that purchases from a Tier I BusinessPartner (Dealer).
BusinessPartner
Transaction Record Temporary state when an RFA System Record is being created or updated.
This converts to a permanent System Record upon completion.
Type 2 features A feature that has a value.

70 Getting Started with Remote Feature Activation (RFA)

 Index

Index

A D
Advanced IP Phone Features . . . . . . . . . . . . 18 DEFINITY
license file information . . . . . . . . . . . . . 19 Migrations . . . . . . . . . . . . . . . . . . . 38
AE . . . . . . . . . . . . . . . . . . . . . . . . 25 Upgrades . . . . . . . . . . . . . . . . . . . . 38
Applications . . . . . . . . . . . . . . . . . . 27 Design Configuration . . . . . . . . . . . . . . . . .8
CVLAN Server 9.0 for Linux . . . . . . . . . . . 27 Directory Enablement Management . . . . . . . . . 44
CVLAN Client . . . . . . . . . . . . . . . . 27
CVLAN server . . . . . . . . . . . . . . . . 27
License file information . . . . . . . . . . . . . 28 E
Upgrading CVLAN R9 to AE . . . . . . . . . . . 26 Enterprise Network Management Console . . . . . . 45
Upgrading DLG to AE . . . . . . . . . . . . . . 26 Event Processor . . . . . . . . . . . . . . . . . . 46
Upgrading to . . . . . . . . . . . . . . . . . . 26
Application Assurance Networking . . . . . . . . . 20
License file information . . . . . . . . . . . . . 21 F
Application Design Environment
Feature Keywords . . . . . . . . . . . . . . . . . 11
Components . . . . . . . . . . . . . . . . . . 23
License file information . . . . . . . . . . . . . 24
Application Design Environment (ADE) . . . . . . . 23
Application Enablement Services . . . . . . . . . . 25
G
Application readiness checklist . . . . . . . . . . . 13 G250 and G350
Applications Activating Virtual Private Networking . . . . . . . 34
Audix . . . . . . . . . . . . . . . . . . . . . 36 Activating VPN . . . . . . . . . . . . . . . . . 34
Call Center . . . . . . . . . . . . . . . . . . . 36 Post installation verification . . . . . . . . . . . 34
Applications under the Communication Manager product Remotely controlled by a server . . . . . . . . . 33
family . . . . . . . . . . . . . . . . . . . . . . 36 Remotely controlled by a server with an LSP . . . 33
Audix . . . . . . . . . . . . . . . . . . . . . . . 36 Remotely controlled by a server with an LSP and VPN33
Authenticated . . . . . . . . . . . . . . . . . . . . 8 With an S3800 and VPN . . . . . . . . . . . . . 33
Authentication file . . . . . . . . . . . . . . . . . 37 With an S8300 . . . . . . . . . . . . . . . . . 33
Authentication files . . . . . . . . . . . . . . . . . 38 G250 and G350 serial number. . . . . . . . . . . . 34
Availability . . . . . . . . . . . . . . . . . . . . . . 8 G250 Media Gateway . . . . . . . . . . . . . . . . 33
Avaya IQ . . . . . . . . . . . . . . . . . . . . . 29 Configurations . . . . . . . . . . . . . . . . . 33
Avaya support center. . . . . . . . . . . . . . . . 12 G350 Media Gateway . . . . . . . . . . . . . . . . 33
Configurations . . . . . . . . . . . . . . . . . 33
Standalone G350 with VPN . . . . . . . . . . . 33
B Standalone G350 without VPN . . . . . . . . . . 33
Branch Gateways . . . . . . . . . . . . . . . . . 33 GAI . . . . . . . . . . . . . . . . . . . . . . . . 10
License file information . . . . . . . . . . . . . 35 Group Authorization Identification . . . . . . . . . . 10

C H
Call Center . . . . . . . . . . . . . . . . . . . . 36 Help for RFA . . . . . . . . . . . . . . . . . . . . 14
Communication Manager . . . . . . . . . . . . . . 35 Help information . . . . . . . . . . . . . . . . . . 12
Authentication file . . . . . . . . . . . . . . . . 37 Host ID
Communications Process Manager . . . . . . . . . 39 Host ID information table . . . . . . . . . . . . . 12
licensing information . . . . . . . . . . . . . . 40 Host IDs . . . . . . . . . . . . . . . . . . . . . . 11
Computer requirements . . . . . . . . . . . . . . . 7 HRID . . . . . . . . . . . . . . . . . . . . . . . .7
Customer Interaction Express . . . . . . . . . . . 40
Licensing information . . . . . . . . . . . . . . 41

Issue 4.1 November 2007 71

Index

Security Gateway . . . . . . . . . . . . . . . . . . 58
Security Gateways
I License file information . . . . . . . . . . . . . 60
Important product Information . . . . . . . . . . . . 17 Models . . . . . . . . . . . . . . . . . . . . . 59
Integrated Management (Avaya IM) . . . . . . . . . 47 Serial numbers . . . . . . . . . . . . . . . . . . . 11
License file information . . . . . . . . . . . . . 48 Communication Manager . . . . . . . . . . . . 37
Interaction Center . . . . . . . . . . . . . . . . . 49 Firmware . . . . . . . . . . . . . . . . . . 37
Email license request . . . . . . . . . . . . . . 49 Hardware . . . . . . . . . . . . . . . . . . 37
License file information . . . . . . . . . . . . . 50 SIP Enablement Services . . . . . . . . . . . . . . 60
License file information . . . . . . . . . . . . . 61
Post installation verification . . . . . . . . . . . 61
M Softclients . . . . . . . . . . . . . . . . . . . . . 62
Material Codes . . . . . . . . . . . . . . . . . . .11 CCS . . . . . . . . . . . . . . . . . . . . . . 62
Meeting Exchange . . . . . . . . . . . . . . . . . 52 Host ID information . . . . . . . . . . . . . . . 62
License file information . . . . . . . . . . . . . 53 License file information . . . . . . . . . . . . . 62
Migrations . . . . . . . . . . . . . . . . . . . . . 38 Peer-to-Peer . . . . . . . . . . . . . . . . . . 62
Modular Messaging . . . . . . . . . . . . . . . . 53 SIP Softphone . . . . . . . . . . . . . . . . . 62
Host IDs . . . . . . . . . . . . . . . . . . . . 54 Swap-Out . . . . . . . . . . . . . . . . . . . . . 12
License file information . . . . . . . . . . . . . 54
Post installation verification . . . . . . . . . . . 54
T
Training . . . . . . . . . . . . . . . . . . . . . . 10
N
NMC . . . . . . . . . . . . . . . . . . . . . . . 45
U
Unified Communication Center . . . . . . . . . . . 63
O Host ID . . . . . . . . . . . . . . . . . . . . . 64
one-X Mobile . . . . . . . . . . . . . . . . . . . 55 License file information . . . . . . . . . . . . . 65
one-X Portal . . . . . . . . . . . . . . . . . . . . 56 Upgrades . . . . . . . . . . . . . . . . . . . . . 38
licensing information . . . . . . . . . . . . . . 56 User requirements . . . . . . . . . . . . . . . . . .7
Operator Set PC (OSPC) . . . . . . . . . . . . . . 57
OSPC licensing information. . . . . . . . . . . . . 58
V
Value Types . . . . . . . . . . . . . . . . . . . . 11
P Virtual Private Networking . . . . . . . . . . . . . . 34
Pre-installation check list . . . . . . . . . . . . . . 13 Voice Self Service . . . . . . . . . . . . . . . . . 65
License file information . . . . . . . . . . . . . 66

R
Registered . . . . . . . . . . . . . . . . . . . . . 8
Registration for Avaya Associates . . . . . . . . . . . 9
Registration for Avaya BusinessPartners . . . . . . . 9
Reliability . . . . . . . . . . . . . . . . . . . . . . 8
RFA
Access . . . . . . . . . . . . . . . . . . . . . . 7
Overview . . . . . . . . . . . . . . . . . . . . . 7

S
S8300 Media Server
Acting as an LSP . . . . . . . . . . . . . . . . 33
Acting as an LSP with VPN . . . . . . . . . . . 33
Standalone G250 and G350 with an S8300 . . . . 33
Standalone G250 or G350 with an S8300 and a VPN33

72 Getting Started with Remote Feature Activation (RFA)