Additional SMS Service Configuration

Use the configuration properties in create_config.info to configure additional CAMEL Application Part (CAP) 3 and CAP4 SMS charging services.

SMS Charging Service Configuration Parameters describes the configuration parameters in create_config.info for configuring additional SMS services and shows example values for each parameter.
Table 1. SMS Charging Service Configuration Parameters
Parameter Description Example Value
Number of Additional SMS Services The number of SMS services required in addition to the default SMS services. Enter a value of 1 or more to configure additional SMS services.

create_config.info question: How many additional SMS services do you wish to create?

1
SMS Service Name The unique name of the SMS service that you want to add. The default value is "SMS Additional 1".

create_config.info question: Camel Gateway:SMS Additional 1:What is the name identifier of the SMS service?

my_sms_service
Enable SMS Charging Sets whether SMS details are sent to MATRIXX Engine to enable charging for SMS messages that use this service.

create_config.info question: Camel Gateway:SMS my_sms_service:Do you wish to charge short messages to this service?

y
SMS Service ID The ID to use for Multi Service Credit Control (MSCC) information sent to MATRIXX Engine. The specified value populates the following MSCC charging configuration fields in My MATRIXX:
  • ServiceId
  • ServiceTypeObjectId

The default value for the SMS Service ID is 4.

create_config.info question: Camel Gateway:SMS my_sms_service:What charging Service ID should be used for this SMS service?

4
Charging Type Sets whether the SMS service is for immediate charging or unit reservation. Valid values are:
  • 1 — Immediate charging, where MATRIXX Engine attempts to charge for the SMS as a one off event without establishing a charging session.
  • 2 — Unit reservation, where MATRIXX Engine reserves the cost of the SMS message and then commits it later only if the SMS is successfully submitted.

create_config.info question: Camel Gateway:SMS my_sms_service:What SMS charging type is required for this SMS service?

2
Subscriber Source A comma-separated list of sources (from the IDPSMS) used to search, in list order, and to determine which subscriber to associate with the SMS (for example, for charging purposes). Valid values are:
  • imsi
  • calling
  • destination

create_config.info question: Camel Gateway:SMS my_sms_service:What subscriber sources are required for this SMS service?

imsi
TCAP End Type Sets the service behavior at the end of an open TCAP transaction when there are no outstanding messages to send. The default CAMEL behavior is prearranged end. For switches that do not use this, you can configure to end the transaction by canceling (TCAP Abort) or by sending an empty TCAP End. Valid values are:
  • 1 — Prearranged End
  • 2 — TCAP Abort
  • 3 — Empty TCAP End

create_config.info question: Camel Gateway:SMS my_sms_service:What TCAP transaction prearranged-end behavior is required for this SMS service?

2
Enable Relay SCCP Answer y to enable CCF to relay incoming TCAP messages for subscribers who cannot be found in the MATRIXX subscriber database to the specified relay SCCP address.If you answer n, the additional questions are not asked.

create_config.info question: Camel Gateway:SMS my_sms_service:Do you wish to enable relay sccp for the service?

n
SMS Emergency Numbers The comma-separated list of emergency numbers for the service. SMS messages to emergency numbers are continued without charge. The default value is 911.

create_config.info question: Camel Gateway:SMS my_sms_service:Enter the list of numbers to be treated as emergency numbers in this service?

 911
Rule Set Name The name of the rule set to use for number normalization or denormalization. To use the default rule set, enter default.

create_config.info question: Camel Gateway:SMS my_sms_service:What rule set should be used for number (de)normalization for this SMS service?

default