SIP Server General Deployment. Genesys 7.6

PDF

Dokumen

Chapter

SIP Server General

Deployment

This chapter contains general information for the deployment, configuration, and installation of your SIP Server. You may have to complete additional configuration and installation steps specific to your SIP Server and devices.

You will find these steps in Part One of this document.

z z z z z z

This chapter contains the following sections:

Prerequisites, page 33

Network Considerations, page 37

Deployment Sequence, page 40

Wizard Deployment of SIP Server, page 41

Manual Deployment of SIP Server, page 44

Next Steps, page 50

Note:

You must read the Framework 7.6 Deployment Guide before proceeding with this SIP Server guide. That document contains information about the Genesys software you must deploy before deploying SIP Server.

Prerequisites

SIP Server has a number of prerequisites for deployment. Read through this section before deploying your SIP Server.

SIP Server—Deployment Guide 33

Chapter 2: SIP Server General Deployment Prerequisites

Software Requirements

Framework Components

You can only configure SIP Server after you have deployed the Configuration

Layer of Genesys Framework. This layer contains DB Server, Configuration

Server, Configuration Manager, and, at your option, Deployment Wizards. If you intend to monitor or control SIP Server through the Management Layer, you must also install and configure components of this Framework layer, such as Local Control Agent (LCA), Message Server, Solution Control Server

(SCS), and Solution Control Interface (SCI), before deploying SIP Server.

Refer to the Framework 7.6 Deployment Guide for information about, and deployment instructions for, these Framework components.

Media Layer and LCA

To monitor the status of components in the Media Layer through the

Management Layer, you must load an instance of LCA on every host running

Media Layer components. Without LCA, Management Layer cannot monitor the status of any of these components. If you do not use the Management

Layer, LCA is not required.

Supported Platforms

Refer to the Genesys Supported Operating Environment white paper for the list of operating systems and database systems supported in Genesys releases 7.x.

You can find this document on the Genesys Technical Support website at http://genesyslab.com/support/dl/retrieve/ default.asp?item=B6C52FB62DB42BB229B02755A3D92054&view=item

For UNIX-based (UNIX) operating systems, also review the list of patches

Genesys uses for software product builds, and upgrade your patch configuration if necessary. A description of patch configuration is linked to installation read_me.html

files for the Genesys applications that operate on

UNIX, and is available within the installation packages.

Hardware and Network Environment Requirements

Hosting

Genesys recommends that you or your IT specialist assign host computers to

Genesys software before you start Genesys installation. Remember the following restrictions:

•

Do not install all the Genesys server applications on the same host computer.

34 Framework 7.6

Chapter 2: SIP Server General Deployment Prerequisites

•

When installing a few server applications on the same host computer, prevent them (except for Configuration Server) from using the swap area.

Installation Privileges

During deployment, be sure to log in with an account that will permit you to perform administrative functions—that is, one that has root privileges.

Server Locations

Refer to the “Network Locations for Framework Components” chapter of the

Framework 7.6 Deployment Guide for recommendations on server locations.

Supported Platforms

Refer to the Genesys Supported Media Interfaces white paper for the list of supported switch and PABX versions. You can find this document on the

Genesys Technical Support website at http://genesyslab.com/support/dl/retrieve/ default.asp?item=A9CB309AF4DEB8127C5640A3C32445A7&view=item

Licensing Requirements

All Genesys software is licensed—that is, it is not shareware. Genesys products are protected through legal license conditions as part of your purchase contract. However, the level of technical license-control enforcement varies across different solutions and components.

Before you begin to install SIP Server, remember that, although you may not have had to use technical licenses for your software when you deployed the

Configuration and Management Layers in their basic configurations, this is not the case with the Media Layer.

SIP Server requires seat-related DN technical licenses to operate even in its most basic configuration. Without appropriate licenses, you cannot install and start SIP Server. If you have not already done so, Genesys recommends that you install License Manager and configure a license file at this point. For complete information on which products require what types of licenses, and on the installation procedure for License Manager, refer to the Genesys 7

Licensing Guide available on the Genesys Documentation Library DVD.

The sections that follow briefly describe the T-Server/SIP Server license types.

Note:

Starting with release 7.2, the licensing requirements for T-Server

(including SIP Server) have changed from previous releases. Please read this section carefully and refer to the Genesys 7 Licensing Guide for complete licensing information.

SIP Server—Deployment Guide 35

Chapter 2: SIP Server General Deployment Prerequisites

Licensing Basic Implementations

A stand-alone SIP Server serving a single site requires licenses to register all

DNs it monitors. DNs that agents use in day-to-day contact center operations, such as Extensions and ACD Positions, have to be registered using licenses that control agent seats.

Note:

Configure all seat DNs that agents use (Extensions and ACD Positions) in the Configuration Layer. This enables detailed call monitoring through Genesys reporting, and generally allows you to control access to individual DNs.

Licensing HA Implementations

SIP Servers operating with the hot standby

redundancy type require a special

CTI HA technical license, which allows for high-availability implementations, in addition to regular SIP Server licenses. Neither SIP Server in a redundant pair configured for hot standby

starts if this license is unavailable. Moreover, the primary and backup SIP Servers must use the same licenses to control the same pool of DNs. If your SIP Servers are configured with the hot standby redundancy type, order licenses for CTI HA support.

Licensing Multi-Site Implementations

SIP Servers performing multi-site operations require licenses that allow for such operations, in addition to regular SIP Server licenses. If some of your SIP

Servers are configured for multi-site routing while others are not, either order licenses for multi-site support for all SIP Servers or install an additional

License Manager to handle the SIP Servers involved in multi-site routing.

Note:

You do not need licenses for multi-site support if some SIP Server clients include the local location as the location

attribute value in their requests for routing within the same site.

Configuring License Files

You need a license to configure and install Media Layer components. Genesys recommends that, if you have not already done so, at this point you:

1. Install License Manager.

2. Configure license files.

36 Framework 7.6

Chapter 2: SIP Server General Deployment Network Considerations

Note:

If you use the

format when entering the name of the license server during installation, remember that some operating systems use

as a special character. In this case, the installation routine is unable to write license information for SIP Server to the

Configuration Layer or the run.sh

file. Therefore, when you use the

format, you must manually modify the command-line license parameter after installing SIP Server.

For information about which products require what types of licenses and for the installation procedure for License Manager, refer to the Genesys 7

Licensing Guide available on the Genesys Documentation Library DVD.

About Configuration Options

Configuring SIP Server is not a onetime operation. It is something you do at the time of installation and then in an ongoing way to ensure the continued optimal performance of your software. You must enter values for SIP Server configuration options on the relevant Wizard pages or on the

Options

tab of your SIP Server

Application

object in Configuration Manager. The instructions for configuring and installing SIP Server that you see here are only the most rudimentary parts of the process. You must refer extensively to the configuration options chapters located in Part One and Part Two of this book.

Pay particular attention to the configuration options specific to SIP Server.

Configuration options common to all T-Servers, independent of switch type,

are described in Chapter 12, “T-Server Common Configuration Options,” on page 343

. SIP Server-specific configuration options are described in Chapter 8,

“SIP Server Configuration Options,” on page 197 . SIP Server also supports

unified Genesys log options, as described in the Chapter 11, “Common

Configuration Options,” on page 321 .

Options that configure values for the TSCP (T-Server Common Part) software in your SIP Server are common to all T-Servers. Options based on the SIP custom features apply to your SIP Server only. Familiarize yourself with both types of options. You will want to adjust them to accommodate your production environment and the business rules that you want implemented there.

Network Considerations

This section is for system administrators, contact center operations heads, and developers who are planning to deploy Genesys SIP Server.

Deploying SIP Server is similar in many ways to deploying other components of the Genesys Framework, with the significant exception that the voice signal is carried over the data network. This has serious implications for network

SIP Server—Deployment Guide 37

Chapter 2: SIP Server General Deployment Network Considerations planning and server sizing. The primary purpose of this section is to highlight the major planning and resource concerns you face in rolling out SIP Server, and to explain how it overlaps with the underlying data network. However, this section is not intended to be an exhaustive guide to network planning. Refer to the Framework 7.6 Deployment Guide for further help with Framework rollout.

The performance of SIP Server is directly linked to that of the underlying data network. It is essential that you perform a proper network audit to ensure that the data network has been properly sized and tuned for real-time (voice) packet transport. This section discusses the factors that affect overall performance of an IP-based configuration, and provides some general rules to follow when deploying SIP Server.

Voice Quality

The following factors have a direct impact on voice quality:

•

Network latency—Overall network delay.

In a system in which packets are emitted at 20-millisecond (msec) intervals, some packets actually arrive at intervals ranging from 0 to 32 msec. To minimize network latency and ensure acceptable voice quality, you need to tune the network to prioritize real-time voice packets. There are various available schemes for prioritizing voice packets, depending on the IP router vendor.

•

Packet loss—Voice packets that are dropped for various reasons (physical media error, timeout due to network congestion, and so on).

Packet loss is a function result of several factors, including network bandwidth. As a general rule, the maximum sustained packet loss must not exceed 5 percent. Zero (0) percent packet loss is easily achievable on localarea networks (LANs) that use full-duplex Ethernet connections and this must be your goal for reliable high-quality voice operations.

•

Packet jitter—Variation in voice packet arrival times.

You can minimize packet jitter by using a jitter buffer at the endpoint device. As a general rule, you must set the buffer size to the maximum anticipated deviation from the typical interpacket emission time.

Other factors that influence voice quality include:

•

Packet misordering—Packets arrive in the wrong order (similar to packet loss).

•

Type of codec used—Codecs that do not compress the audio signal produce better voice quality but use greater bandwidth.

•

Silence suppression—Silence suppression can save bandwidth, but it can also impact voice quality.

38 Framework 7.6

Chapter 2: SIP Server General Deployment Network Considerations

Bandwidth Requirements

Determining the bandwidth requirements for the underlying data network is another critical step in achieving proper performance and voice quality.

Bandwidth requirements for a video connection are, of course, much higher.

Genesys recommends that you verify network performance and voice quality by conducting performance tests and measurements in a lab environment prior to production rollout.

For an IP/Ethernet network, two factors that affect bandwidth requirements are:

•

Codec used.

•

Protocol headers.

Genesys has found that a full-duplex voice conversation using the G.723.1 codec requires approximately 20 Kbps (kilobits per second). When estimating actual network bandwidth needs, you must also consider such factors as network efficiency and utilization.

Note:

Genesys recommends that LANs not have a throughput higher than 30 percent of the theoretical maximum (10 Mbps/100 Mbps/1 Gbps).

Exceeding the 30-percent level often leads to packet loss, because the

IP switches and routers are overloaded.

Remote Agent Configuration

SIP Server’s remote agent capabilities range from a single remote agent, to a group of remote agents in a branch office environment. The distributed nature of branch office and remote agent architectures adds to the complexity of network sizing and tuning.

Note:

Remote agent deployment behind media gateways on circuit-switching networks (such as PSTN) is not fully supported in the current release of

SIP Server. If inbound calls are answered by, or transferred to, such remote agents, the

Annex tab >

Tserver

section of the corresponding

object in Configuration Manager must have the refer-enabled

option set to false.

This value limits call-transfer functionality to

Consult

Transfer

only. In addition, your media gateway must be configured as a DN of type

Trunk,

with the refer-enabled

option set to

false

Bandwidth and Network Tuning

Just as for local network deployment of a VOIP-based system, you must, if at all possible, allot proper bandwidth for voice communication and tune the underlying network for real-time media. Remote agents using a dial-up connection require greater bandwidth (at least 33 Kbps, with 56 Kbps

SIP Server—Deployment Guide 39

Chapter 2: SIP Server General Deployment Deployment Sequence recommended) because of the extra network overhead. This assumes use of the

G.723.1 codec, although some dial-up connections may accommodate G.729. A

Digital Subscriber Line (DSL) connection is a better alternative than a dial-up connection. The choice of remote access method is important—avoid sending voice communication over an unmanaged data network, such as the public

Internet, where voice quality cannot be guaranteed.

For a branch office environment, network bandwidth requirements depend on the number of agents. Again, wide-area network (WAN) connectivity to the corporate LAN must be tuned for real-time voice communications. You need to ensure that service-level agreements from your virtual private network

(VPN) provider give details of such requirements. End-to-end network latency must not exceed 250 msec.

Firewalls

This release of SIP Server provides no explicit support for Network Address

Translation (NAT). Genesys recommends using virtual private networks (such as PPTP) and ensuring that all agents are on the same network, without NAT translators between the agents and SIP Server.

Deployment Sequence

Genesys recommends deploying SIP Server by using the SIP Server

Configuration Wizard. However, if for some reason you must manually deploy

SIP Server, you will also find instructions for doing that in this chapter.

The recommended sequence to follow before deploying SIP Server is described below. Steps 1 through 3 apply for both Wizard-based and manual deployment. For Wizard deployment, Steps 4 and 5 take place within the

Wizard deployment process itself.

Wizard or Manual

Deployment

Manual

Deployment

1. Deploy Configuration Layer objects and ensure Configuration Manager is running (see the Framework 7.6 Deployment Guide).

2. Deploy Network objects (such as Host objects).

3. Deploy the Management Layer (see the Framework 7.6 Deployment

Guide).

When manually deploying SIP Server, you must continue with the next two steps. If you are deploying SIP Server with the Configuration Wizard, the next two steps take place within the Wizard deployment process itself, where you can create and configure all the necessary objects for SIP Server deployment.

4. Configure Telephony objects (see “Manual Configuration of Telephony

Objects” on page 44 ):

Switching Offices

Switches

40 Framework 7.6

Chapter 2: SIP Server General Deployment Wizard Deployment of SIP Server

Verifying Starting

Parameters

Agent Logins

DNs

5. Deploy the Media Layer:

SIP Server (beginning with “Manual Configuration of SIP Server” on page 46 ).

If, during the installation procedure for any of the Genesys applications, the script warns you that Configuration Server is unavailable and that the configuration cannot be updated, continue with the installation. Following the installation, you must complete the information on the

Start Info

tab to ensure that SIP Server will run.

When installation is complete, verify the information on the

Start Info

tab to

ensure that SIP Server will run. See “Verifying the manual installation of SIP

Server” on page 49

Wizard Deployment of SIP Server

Configuration wizards facilitate component deployment. SIP Server configuration and installation involves many steps, and Genesys strongly recommends that you set up SIP Server using the Wizard rather than manually.

The SIP Server Configuration Wizard guides you through a series of steps and options to customize your deployment of SIP Server.

Wizard Configuration of SIP Server

The first step to take for a Wizard-based configuration is to install and launch

Genesys Wizard Manager. (Refer to the Framework 7.6 Deployment Guide for instructions.) When you first launch Genesys Wizard Manager, it suggests that you set up the Management Layer and then the Framework. The Framework setup begins with configuring and creating the objects related to SIP Server, starting with the

Switch

and

Switching Office

objects, and the SIP Server’s

Application

object itself.

Note:

With the wizard, you create your SIP Server

Application

object in the course of creating your

Switch

object.

During creation of the

Switch

object, you also have an opportunity to run the

Log Wizard to set up SIP Server logging. Then, you can specify values for the most important SIP Server options. Finally, you can create contact center objects related to SIP Server, such as

DN s,

Agent Login s, and some others.

SIP Server—Deployment Guide 41

Chapter 2: SIP Server General Deployment Wizard Deployment of SIP Server

Note:

During configuration of a

Switch

object, the Wizard prompts you to copy a SIP Server installation package to an assigned computer. After that package is copied to the destination directory on the SIP Server host, complete the last steps of the SIP Server configuration. Then, install SIP Server on its host.

After you complete the Framework configuration, the Genesys Wizard

Manager screen no longer prompts you to set up the Framework. Instead, it suggests that you set up your solutions or add various contact center objects to the Framework configuration, including the

Switch, DNs

and

Places, Agent

Logins, Agent Groups, Place Groups

, and, in a multi-tenant environment, a

Tenant

. In each case, click the link for the object you wish to create. Again, you create a new SIP Server

Application

object in the course of creating a new

Switch

object.

Wizard Installation of SIP Server

After creating and configuring your SIP Server and its related components with the wizard, you can proceed to SIP Server installation. That installation process closely mimics that of previously installed components.

Note:

Certain Wizard-related procedures are not described in this document.

Refer to the Framework 7.6 Deployment Guide for general instructions.

Warning!

Genesys does not recommend installation of its components via a

Microsoft Remote Desktop connection. The installation should be performed locally.

Procedure:

Installing SIP Server on UNIX using the wizard

Start of procedure

1. In the directory to which the SIP Server installation package was copied during Wizard configuration, locate a shell script called install.sh.

2. Run this script from the command prompt by typing sh

and the file name.

For example: sh install.sh.

3. When prompted, confirm the host name of the computer on which SIP

Server is to be installed.

4. When prompted, confirm the application name of the SIP Server that is to be installed.

42 Framework 7.6

Chapter 2: SIP Server General Deployment Wizard Deployment of SIP Server

5. Specify the destination directory into which SIP Server is to be installed, with the full path to it.

6. If asked which version of the product to install, the 32-bit or the 64-bit, choose the one appropriate to your environment.

7. Specify the license information that SIP Server is to use.

8. As soon as the installation process is finished, a message appears announcing that installation was successful. The process places SIP Server in the directory with the name specified during the installation.

End of procedure

Next Steps

•

To test your configuration and installation, go to Chapter 4, “Starting and

Stopping SIP Server,” on page 69

, and try it out.

•

To configure and install redundant SIP Servers, see Chapter 3, “High-

Availability Deployment,” on page 51

•

To install T-Servers for a multi-site environment, proceed to Chapter 10,

“Multi-Site Support,” on page 267 .

Procedure:

Installing SIP Server on Windows using the wizard

Start of procedure

1. Open the directory to which the SIP Server installation package was copied during Wizard configuration.

2. Locate and double-click

Setup.exe

to start the installation. The

Welcome screen launches.

3. When prompted, specify the connection parameters to the Configuration

Server associated with this SIP Server.

4. Identify the SIP Server

Application

object in the Configuration Layer to be used by this SIP Server.

5. Specify the license information that SIP Server is to use.

6. Specify the destination directory into which SIP Server is to be installed.

7. Click

Install

to begin the installation.

8. Click

Finish

to complete the installation.

By default, SIP Server is installed as a Genesys service (Windows

Services

) with

Automatic

startup type.

End of procedure

SIP Server—Deployment Guide 43

Chapter 2: SIP Server General Deployment Manual Deployment of SIP Server

Next Steps

•

To test your configuration and installation, go to Chapter 4, “Starting and

Stopping SIP Server,” on page 69

, and try it out.

•

To configure and install redundant SIP Servers, see Chapter 3, “High-

Availability Deployment,” on page 51

•

To install SIP Servers for a multi-site environment, proceed to Chapter 10,

“Multi-Site Support,” on page 267 .

Manual Deployment of SIP Server

Deploying SIP Server manually requires that you configure a number of different objects in the Configuration Layer prior to setting up your SIP Server objects and then installing SIP Server. This section describes the manual deployment process.

Manual Configuration of Telephony Objects

This section describes how to manually configure SIP Server telephony objects if you are using Configuration Manager.

Recommendations

Genesys recommends registering (configuring) only those entities you plan to use in the current configuration. The more data there is in the Configuration

Database, the longer it takes for the CTI setup to start, and the longer it will take to process configuration data. Remember that adding configuration objects to the Genesys Configuration Database does not cause any interruption in contact center operation.

Depending on how much work is required to manually configure all applications and objects, consider registering more

Person

objects first, with a set of privileges that lets them perform configuration tasks.

Switching Offices

Your telephony network may contain many switching offices, but you should only configure those that are involved with customer interactions.

Using Configuration Manager, be sure to register a

Switching Office object of type

SIP Switch

that accommodates your

Switch

object under

Environment.

Until you have done this, you cannot register a

Switch

object under

Resources

(single-tenant environment) or a

Tenant

(multi-tenant environment).

Note:

The value for the switching office name must not have spaces in it.

44 Framework 7.6

Chapter 2: SIP Server General Deployment Manual Deployment of SIP Server

Switches

1. Configure a

Switch

object for each switch on your telephony network.

Assign each

Switch

object to the appropriate SIP Server

Application object.

2. If implementing the multi-site configuration, specify access codes for all switches on the network so that the call-processing applications can route and transfer calls between switches.

Two types of access codes exist in a Genesys configuration:

Default access codes that specify how to reach this switch from any other switch in the Genesys environment.

Switch-to-switch access codes that specify how to reach a particular switch from any other switch. Use this type when either a nondefault dial number or routing type is required between any two locations.

When a switch-to-switch access code is configured, its value has a higher priority than that of a default access code.

See Chapter 10, “Multi-Site Support,” on page 267 , for step-by-step

instructions.

Note:

When the numbering plan uses unique directory number (DN) assignment across sites and multi-site routing is not used, you do not have to configure access codes.

DNs and Agent Logins

For each SIP Server for which you are configuring DNs, you must configure all DNs that agents and their supervisors use in day-to-day contact center operation—so-called seat-related DNs—such as Extensions and ACD

Positions. Otherwise, SIP Server does not register such DNs.

1. To configure telephony objects within each switch, consult the switch documentation. For configuration information specific to your SIP devices,

see Chapter 5, “SIP Devices Support,” on page 77

2. Check the numbering plan for different types of DNs, to see if you can save time by registering Ranges of DNs. Usually, DNs of the same type have consecutive numbers, which will make an otherwise tedious configuration task easy.

Agent Login

objects almost always have consecutive numbers, which means you can register them through the

Range of Agent Logins feature as well.

3. If you plan to use Virtual Queues and Virtual Routing Points in the contact center operation, Genesys recommends registering them after you have outlined the call-processing algorithms and identified your reporting needs.

SIP Server—Deployment Guide 45

Chapter 2: SIP Server General Deployment Manual Deployment of SIP Server

Note:

Remember that CTI applications, not the switch, generate telephony events for DNs of these types.

Multi-Site Operations

See the section, “Configuring Multi-Site Support” on page 307 , for

information on setting up DNs for multi-site operations.

Manual Configuration of SIP Server

Note:

Use the Framework 7.6 Deployment Guide to prepare accurate configuration information. You may also want to consult Configuration

Manager Help, which contains detailed information about configuring objects.

Recommendations

Genesys recommends using an Application Template when you are configuring your SIP Server application. The Application Template for SIP

Server contains the most important configuration options set to the values recommended for the majority of environments. When modifying configuration options for your SIP Server application later in the process, you can change the values inherited from the template rather than create all the options by yourself.

Procedure:

Configuring SIP Server manually

Start of procedure

1. Follow the standard procedure for configuring all

Application

objects to begin configuring your SIP Server

Application

object. Refer to the

Framework 7.6 Deployment Guide for instructions.

2. In a multi-tenant environment, specify the

Tenant

to which this SIP Server belongs on the

General

tab of the

Properties

dialog box.

3. On the

Connections

tab, add all Genesys applications to which SIP Server must connect.

Note:

For multi-site deployments, you should also specify SIP Server connections on the

Connections tab for any SIP Servers that may transfer calls directly to each other.

46 Framework 7.6

Chapter 2: SIP Server General Deployment Manual Deployment of SIP Server

4. On the

Options

tab, specify values for configuration options as appropriate for your environment.

Note:

For SIP Server option descriptions, see Chapter 8, “SIP Server

Configuration Options,” on page 197 . The configuration options

common to all T-Servers are described in the Chapter 12,

“T-Server Common Configuration Options,” on page 343

chapter.

SIP Server also uses common Genesys log options, described in

the Chapter 11, “Common Configuration Options,” on page 321

5. In a multi-site environment, you must complete additional SIP Server

configuration steps to support multi-site operations; see Chapter 10,

“Multi-Site Support,” on page 267 .

End of procedure

Next Steps

•

See “Manual Installation of SIP Server” on page 47 .

Manual Installation of SIP Server

The following directories on the Genesys 7.6 SIP Server product CD contain

SIP Server installation packages:

•

SIP_Server/<component>/<platform>

for UNIX installations, where

is SIP Server or DMX, and

is your operating system.

•

SIP_Server\<component>\windows

for Windows installations, where

is SIP Server or DMX.

Procedure:

Installing SIP Server on UNIX manually

Note:

During installation on UNIX, all files are copied into the directory you specify. No additional directories are created within this directory.

Therefore, do not install different products into the same directory.

Start of procedure

1. In the directory to which the SIP Server installation package was copied, locate a shell script called install.sh.

2. Run this script from the command prompt by typing sh

and the file name.

For example: sh install.sh.

SIP Server—Deployment Guide 47

Chapter 2: SIP Server General Deployment Manual Deployment of SIP Server

3. When prompted, confirm the host name of the computer on which SIP

Server is to be installed.

4. When prompted, specify the host and port of Configuration Server.

5. When prompted, enter the user name and password to access Configuration

Server.

6. When prompted, select the SIP Server application you configured in

“Configuring SIP Server manually” on page 46

from the list of applications.

7. Specify the destination directory into which SIP Server is to be installed, with the full path to it.

8. If asked which version of the product to install, the 32-bit or the 64-bit, choose the one appropriate to your environment.

9. Specify the license information that SIP Server is to use: either the full path to, and the name of, the license file, or the license server parameters.

10. As soon as the installation process is finished, a message appears announcing that installation was successful. The process places SIP Server in the directory with the name specified during the installation.

End of procedure

Next Steps

•

To verify manual installation, go to “Verifying the manual installation of

SIP Server” on page 49

•

To test your configuration and installation, go to Chapter 4, “Starting and

Stopping SIP Server,” on page 69

, and try it out.

•

To configure and install redundant SIP Servers, see Chapter 3, “High-

Availability Deployment,” on page 51

•

To install SIP Servers for a multi-site environment, proceed to Chapter 10,

“Multi-Site Support,” on page 267 .

Procedure:

Installing SIP Server on Windows manually

Start of procedure

1. In the directory to which the SIP Server installation package was copied, locate and double-click

Setup.exe

to start the installation.

2. When prompted, specify the connection parameters to the Configuration

Server associated with this SIP Server.

48 Framework 7.6

Chapter 2: SIP Server General Deployment Manual Deployment of SIP Server

3. When prompted, select the SIP Server

Application

object you configured

in “Configuring SIP Server manually” on page 46 from the list of

applications.

4. Specify the license information that SIP Server is to use: either the full path to, and the name of, the license file, or the license server parameters.

5. Specify the destination directory into which SIP Server is to be installed.

6. Click

Install

to begin the installation.

7. Click

Finish

to complete the installation.

By default, SIP Server is installed as a Genesys service (Windows

Services

) with

Automatic

startup type.