Configuring SIP Feature Server

[In progress]

This section explains how to install and configure the SIP Feature Server instances for SIP Cluster.

Planning and pre-installation

Before installing and configuring SIP Feature Server, you must plan your environment and install required hardware and software. In your planning, you must:

Meet hardware and software prerequisites such as operating system, hardware, and Genesys and third-party components.
Review the current known issues and recommendations.

Feature Server configuration options

See Configuration options for information about the SIP Feature Server configuration options.

Deploying SIP Feature Server

Complete these steps to install and configure the SIP Feature Server instances for SIP Cluster.

Important

It is recommended to use External Cassandra cluster in the SIP Cluster environment.

Configure voicemail

To configure voicemail in Cluster mode:

In Genesys Administrator, navigate to the rm section of the Options tab of the Resource Manager (RM) application, and set the option value of the sip-header-for-dnis option to request-uri.
Create a resource group of type Media control platform to make the Media Control Platform (MCP) instances in the cluster available for RM instances.
Create a resource group of type gateway between SIP Server and each RM instance in the cluster.
Under the SIP Cluster Switch, create a DN of type Voice over IP Service with the same name as the configured Direct Inward Dialing (DID). Create one DN for each data center. The voicemail DNs will be used for configuring voicemail.
- In the Options > TServer section, configure the following options:
Name Value Example

contact ::msml

geo-location <A string identifying the data center to which this DN belongs> geo-location=sfo

service-type voicemail
Under the Voice Platform tab, create one IVR profile for each Feature Server instance in the cluster:
- service-type,value voicexml
- initial-page-url, value [http: https:]//FQDN1 or FS1 IP address:port/fs
  FQDN1 is the FQDN you created while configuring Feature Server applications, if your environment includes more than two Feature Server instances per SIP switch.
- alternatevoicexml,value [http: https:]//FS(n+1) IP address:port/fs
  FS(n+1) IP address is the IP address of the "extra" Feature Server instance that is not included in FQDN1.
For each IVR profile created above, configure a unique DID.
Map IVR profiles to VOIP Service DNs by specifying the following parameter in the Annex tab of the tenant:
- gvp.dn-groups, value <DNs in the group>
  where <DNs in the group> are configured DNs under a Switch with which the voicemail SIP Server Application is associated.
- gvp.dn-group-assignments, value <DBID of the Voicemail IVR Profile>
To configure external voicemail deposit, configure a URS strategy that considers the DN/Agent dial-plan settings for business calls that land at a route point. In TRouteCall to SIP Server, the strategy must respond to the value full with UseDialPlan.

Configure a URS strategy to retrieve an individual or group voicemail. This strategy must respond with TRouteCall to the P-Alcatel-CSBU header.

For example, on this routing point the strategy should generate the following TRouteCall:

  message RequestRouteCall
  AttributeThisDN     '1519'
  AttributeConnID     010a02020db9f03c
  AttributeOtherDN    'gcti::voicemail'
  AttributeLocation   ''
  AttributeExtensions [152] 00 04 00 00..
  'SIP_HEADERS'       'P-Alcatel-CSBU'
  'P-Alcatel-CSBU'   'call_condition=localdirect;categparty=internal;
                      rd=unconditional'
  AttributeDNIS       '1519'
  AttributeRouteType  1 (RouteTypeDefault)

Configure Message Waiting Indicator (MWI)

To configure Feature Server to issue a Message Waiting Indicator (MWI):

In your SIP proxy application, select Options > sipproxy > feature-server-address. Configure the Feature Server IP address with port 5160.
To use a different SIP port from the default SIP port on the SIP Feature Server, create a sip section on the SIP Feature Server and add a localport option to assign the SIP port.

Notes:

The SIP MWI is supported only for individual mailboxes.
For group mailboxes, only the T-Library MWI is supported.
Feature Server does not accept subscriptions for device numbers (except where the mailbox number matches the device number).
To support SIP MWI notification, the SIP endpoints must be configured to subscribe to the voice mailbox number directly.
The subscription should be sent to SIP Proxy—for example, mailbox number@SIP Proxy IP.

Configuring dial-plan in Feature Server

See Dial plan for information about creating partitions and calling profiles, and editing dial plan settings.
Configuring dial-plan DNs
Calling profiles and its associations
Minimum dial-plan configuration

Configuring dial-plan DNs

[In progress]

The SIP Cluster Switch might contain one or more dial-plan DNs. A typical SIP Cluster deployment will have one dial-plan DN configured for each data center.

Under the SIP Cluster Switch, create a DN of type Voice over IP Service named, for example, dial-plan-sfo.
In the Options > TServer section, configure the following mandatory options:

Name	Value	Notes	Example
url	A URL of a local SIP Feature Server	Set this option to the URL for the local SIP Feature Server in this data center. If there is more than one SIP Feature Server in the data center, create as many url options as needed to accommodate all of their addresses in one DN. The first option must always be named url. All consecutive options must be named url-<n>, depending on the number of deployed Feature Server instances (see url-1 below).	url=`http://sfo-001.example.com:8800/`
url-1	A URL of the second SIP Feature Server	Set this option to the URL for the second SIP Feature Server in this data center. All consecutive options must be named url-<n>, depending on the number of deployed Feature Server instances.	url-1=`http://sfo-002.example.com:8800/`
geo-location		A string identifying the data center to which this DN belongs.	geo-location=`sfo`
service-type	feature-server

Calling profiles and its associations

Calling profile can be assigned to the following contact center objects:

Switch—Generic rules applicable for all calls in the cluster deployment.
User—Specific set of rules that need to be configured for a set of users.
Extension—Specific set of rules that need to be configured for set a of extensions.
Trunk—Customized dial-plan for a particular trunk because external calling profile is used for all inbound calls.
Softswitch—Customized dial-plan for a particular softswitch. For example, 10-digit numbers must be converted into E.164 to match PSTN carrier requirement.
Trunk Group—Calling profile used for predictive calls.
Route Point—Calling profile will be used only for predictive calls, it don't affect call routing.

Minimum dial-plan configuration

The following minimum dial-plan rules must be created for any cluster deployment.

Name	Description	Rule
Basic	Used for digit translation.	`=>${DIGITS}`
Voicemail	Used for voicemail access number to `gcti::voicemail` translation.	`5555=>gcti::voicemail`

Contents