Contents
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.
- Configure SIP Feature Server applications
- Deploy a co-located/external Cassandra cluster
- Configure SIP Feature Server for a co-located/external Cassandra cluster
- Start and verify SIP Feature Server
- Configure voicemail
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 |