2 Configuration

Overview

Introduction

Both the SMS and SLC require post-installation configuration before Short Message Charging Bundle can be used. This chapter explains the configuration required on each of the platforms.

Configuring the SLC

Introduction

The following configuration files must be set up for SMCB SLC platform:

Configuration File Description
eserv.config Main CCS configuration file, located in /IN/service_packages
acs.conf Main ACS configuration file, located in /IN/service_packages/ACS/etc
SLEE.cfg Main SLEE configuration file, located in /IN/service_packages/SLEE/etc

The eserv.config configuration file consists of two sections relevant to SMCB:

Section Type Description
CCS.smcbMacroNodes

A sub-section called smcbMacroNodes in the CCS section.

This contains all the SMCB specific configuration for CCS.

smcbMacroNodes

Parameters

Here are the parameters required in the CCS.smcbMacroNodes section of the eserv.config configuration file.

To configure SMCB, set up the parameters in the eserv.config configuration file: 

/IN/service_packages/eserv.config

To edit the configuration file, use a text editor such as vi.

AlwaysSendContinue

Syntax: AlwaysSendContinue = true|false
Description: Determines whether the SMCB/ACS sends a Continue or a Connect.
Type: Boolean
Optionality: Optional (default used if not set).
Allowed: true, false
Default: false
Notes:

When set to:

  • True, a Continue is sent regardless of whether the number from the incoming IDP is changed by the normalization process.
  • False, a Connect is sent if the number from the incoming IDP is changed by the normalization process, otherwise a Continue is sent.
Example: AlwaysSendContinue = true

CacheRefreshInterval

Syntax: CacheRefreshInterval = seconds
Description: Time to wait before checking the cache has up to date rating rules and types information.
Type: Integer
Optionality: Optional
Allowed: Seconds. Maximum is 43200 seconds (12 hours)
Default: 600
Notes: If this has expired, then the new configuration is re-read.
Example: CacheRefreshInterval = 600

CallingPartyNumberPrefix

Syntax: CallingPartyNumberPrefix = "prefix"
Description: String to prefix the calling number with for tariffed charging, so Short Messages can be billed differently to voice calls from the same location.
Type: String
Optionality: Optional
Allowed: Maximum 20 characters
Default: “E”
Notes: Can be set to “” (empty string) to disable prefix.
Example: CallingPartyNumberPrefix = "E"

CdrOrigCdNumExt

Syntax: CdrOrigCdNumExt = ext
Description: The original called party IDP number, extension number that is recorded in the CDR TN field.
Type: Integer
Optionality: Optional
Allowed:  
Default: 0
Notes:  
Example: CdrOrigCdNumExt = 0

CdrUsePendingTN

Syntax: CdrUsePendingTN = true|false
Description: Use pending TN rather than original called number in EDRs
Type: Boolean
Optionality: Optional (default used if not set).
Allowed: true, false
Default: false
Notes:  
Example: CdrUsePendingTN = false

DisableAutoReply

Syntax: DisableAutoReply = true|false
Description: Disable the auto-reply message.
Type: Boolean
Optionality: Optional
Allowed: true, false
Default: 0
Notes:  
Example: DisableAutoReply = false

HomeCountryCode

Syntax: HomeCountryCode = "code"
Description: String identifying the home country code for SMS-MO country code statistics.
Type: String
Optionality: Optional
Allowed: Maximum is10 characters
Default: “”
Notes:  
Example: HomeCountryCode = ""

OverrideInitialEventCdrType

Syntax: 
OverrideInitialEventCdrType =
true|false
Description: Override the EDR type for the initial event reservation
Type: Boolean
Optionality: Optional (default used if not set).
Allowed: true, false
Default: true
Notes:  
Example: OverrideInitialEventCdrType = true

OverrideInitialTariffCdrType

Syntax: 
OverrideInitialTariffCdrType =
true|false
Description: Override the EDR type for the initial tariff reservation
Type: Boolean
Optionality: Optional (default used if not set).
Allowed: true, false
Default: true
Notes:  
Example: OverrideInitialTariffCdrType = true

ReportSMSCFailures

Syntax: ReportSMSCFailures = true|false
Description: Report SMSC delivery failures to the system log file.
Type: Boolean
Optionality: Optional (default used if not set).
Allowed: true, false
Default: true
Notes:  
Example: ReportSMSCFailures = true

TimeToBill

Syntax: TimeToBill = seconds
Description: The time used for Tariffed calls.
Type: Integer
Optionality: Optional
Allowed: Maximum is 3600 seconds (1 hour).
Default: 60
Notes: This value should match the initial period in the CCS CLI-DN screen, so the cost of the Short Message equals the Initial Cost field.
Example: TimeToBill = 60

TimeZone

Syntax: TimeZone = "zone"
Description: The time zone sent in the event reservation request to the VWS. For example, GMT, MST, or GMT+01:00.
Type: String
Optionality: Optional (default used if not set)
Allowed: zone must be typed in a form recognized by the operating system. You can find a list of recognized time zones in the Time Zones appendix of Advanced Control Services Technical Guide.
Default: "GMT"
Notes:  
Example: TimeZone = "GMT"

Example

After installation of the packages are complete, place the following entries into /IN/service_packages/eserv.config. An example is provided in the smcbMacroNodes section in /IN/service_packages/SMCB/etc/examples/eserv.config.smcb_example: 

CCS = {smcbMacroNodes = {CallingPartyNumberPrefix =
"E"TimeToBill = 60CacheRefreshInterval = 600HomeCountryCode =
"44"DisableAutoReply = falseAlwaysSendContinue =
falseReportSMSCFailures = trueCdrOrigCdNumExt =
0OverrideInitialTariffCdrType = trueOverrideInitialEventCdrType =
trueCdrUsePendingTN = falseTimeZone = "PST"}}#

acs.conf

Parameters

To configure SMCB in ACS, set up the parameters in the acs.conf configuration file:

/IN/service_packages/ACS/etc/acs.conf

To edit the configuration file, use a text editor such as vi.

Note: The acs.conf parameters must begin with an initial space otherwise they will not be read by ACS.

This table describes the parameters required in the acsChassis section of the acs.conf configuration file.

Parameter Description

ServiceEntry(SERVICE_

HANDLE, WHO_CHARGE,

WHERE_FROM, WHERE_TO,

WHO_CONNECT,

SERVICE_LIBRARY)

Although ACS has specific terms for the fields in a Service Entry, the use of them in SMCB is described here.

This shows how the desired behavior can be achieved.

Example

An example configuration for three SMCB services are shown below.

Note: The parameters of the ServiceEntry field should NOT be space separated.

Parameter Description
MacroNodePluginFile libSMCBMacroNodes.so Library with SMCB Feature Node.
ServiceEntry(CCS_ SM_MO 
, nN,
cC, dD, E, ccsServiceLibrary.so)
 Defines the ACS Chassis fields to use for a Mobile Originating Service.
ServiceEntry(CCS_ SM_MT 
, dD,
cC*, dD, E, ccsServiceLibrary.so)

Defines the ACS Chassis fields to use for a Mobile Terminating Service.

* Note: for “SM_MT” handles the ASP_NAME will be prepended to the WHERE_FROM field.

ServiceEntry(

CCS_REVERSE_ SM_MT 
, cC, dD*, dD,
E, ccsServiceLibrary.so)

Defines the ACS Chassis fields to use for a Mobile Terminating Service where there is a separate sender than the ASP to charge.

* Note: for “SM_MT” handles the ASP_NAME will be prepended to the WHERE_FROM field.

SLEE.cfg

Parameters

The following parameters are required in the SLEE.cfg configuration file. 

  • APPLICATION=slee_acs slee_acs.sh
/IN/service_packages/ACS/bin 1 1 1000
  • SERVICE= SM_MO 
    1 slee_acs
CCS_SM_MO
  • SERVICE= SM_MT 
    1 slee_acs
CCS_SM_MT
  • SERVICEKEY=INTEGER 5 SM_MO
  • SERVICEKEY=INTEGER 6 SM_MT

The values in bold are the Service Handles that SMCB will compare to decide whether to run the Short Message Originating Call Plan or the Short Message Terminating Call Plan.

Note: The third field in SERVICEKEY must match the first field in SERVICE.

Configuring the SMSC

Configuration requirements

The SMCB SLC platform requires SMSC to be installed and configured for Auto-Reply Text Message support.

The smcbScp installation configures the short message template for the Unknown language only.

The default SMSC installation creates a SLEE notification interface using the notificationIF name. CCS requires that the interface be named Notification; this requires a change to the SLEE.cfg file.

The SMSC notification interface requires a .from file to be created in the /IN/service_packages/SLEE/msgs directory, this file contains the text that will become the Calling Party Address for the short message sent to the SMSC.

Nokia 47 Extension Configuration

Configuration requirements

To configure an extension the following changes are required to the acs.conf file.

Firstly, the service entry line requires the use of the extension number in place of the called/calling number. This is indicated by the use of a 0 instead of cC or dD.

Example: 

ServiceEntry
(EXT_CCS_SM_MT,0,0,dD,dD,ccsSvcLibrary.so)

Secondly, an extension definition is required, to specify the type of extension to be used. It has the following format:

  • Extension number (the number specified in the service entry)
  • Extension type (IDP tag as specified in the trigger application)
  • Extension number format (fixed at ‘inapaddressstring’)
  • Number description (fixed at ‘extension,nature,plan,digits’)

Example: 

extensionNumber 0 47 inapaddressstring
extension,nature,plan,digits

Configuring the SMS

Introduction

The SMCB service provides Service Management System screens to allow configuration of billing rates and rules. This defines the charging mechanism and cost for sending a Short Message.

Refer to the chapter - SMCB Service for details.