SMS Services Configuration

Use configuration in create_config.py to define Call Control Framework (CCF) configuration for standard SMS mobile originating (MO) and SMS mobile terminating (MT) services.

Unless additional SMS service patterns have been defined with more specific selection rules:

The SMS default service pattern is used for all SMS MO transactions that start with InitialDPSMS where the called SCCP sub-system number is 146.
The SMS MT service pattern is used for all SMS MT transactions that start with InitialDPSMS where the called SCCP sub-system number is 146, and the eventTypeSMS parameter is set to 11 (smsDeliveryRequested).

Note: For SMS MO services, both CAP3 and CAP4 are supported. For SMS MT services, only CAP4 is supported.

SMS MO and MT Service Configuration

SMS Charging Services Configuration Parameters describes the create_config.py parameters for the standard SMS MO and SMS MT services, and shows the default value for each parameter.

Table 1. SMS Charging Services Configuration Parameters
Parameter	Description	Default Value
SMS MT Service ID	The ID to use for Multi Service Credit Control (MSCC) information sent to MATRIXX Engine for the standard SMS MT service. The specified value populates the following MSCC charging configuration fields in My MATRIXX: ServiceId ServiceTypeObjectId create_config.info question: `What charging Service ID should be used for the SMS MT service?`	4
SMS MT Charging Type	Sets the charging method for the standard SMS MT service to immediate charging or unit reservation. The default value of "immediate" is used if no value is entered. Valid values are: 1 — Sets the value to `immediate` in create_config.info, where MATRIXX Engine attempts to charge for the SMS as a one off event without establishing a charging session. If it fails, CCF sends a TCAP END (ReleaseSMS) message to instruct the SMSC, or MSC, not to deliver the SMS. 2 — Sets the value to `unit_reservation` in create_config.info, where MATRIXX Engine reserves the cost of the SMS message and then commits it later only if the SMS is successfully submitted, as indicated by the EventReportSMS received from the SMSC, or MSC. create_config.info question: `What SMS charging type is required for the default SMS service?`	1
Enable Relay SCCP (SMS MT service)	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. For more information about configuring the relay SCCP address, see the discussion about TCAP handover and relay configuration. create_config.info question: `Do you wish to enable relay sccp for the service?`	n
SMS Emergency Numbers (SMS MT service)	The comma-separated list of emergency numbers for the standard MT service. SMS messages to emergency numbers are continued without charge. create_config.info question: `Enter the list of numbers to be treated as emergency numbers in this service?`	911
SMS MO Service ID	The ID to use for Multi Service Credit Control (MSCC) information sent to MATRIXX Engine for the standard SMS MO service. The specified value populates the following MSCC charging configuration fields in My MATRIXX: ServiceId ServiceTypeObjectId create_config.info question: `What charging Service ID should be used for the default SMS service?`	4
SMS MO Charging Type	Sets the charging method for the standard SMS MO service to immediate charging or unit reservation. The default value of `immediate` is used if no value is entered. Valid values are: 1 — Sets the value to `immediate` in create_config.info, where MATRIXX Engine attempts to charge for the SMS as a one off event without establishing a charging session. If it fails, CCF sends a TCAP END (ReleaseSMS) message to instruct the SMSC, or MSC, not to deliver the SMS. 2 — Sets the value to `unit_reservation` in create_config.info, where MATRIXX Engine reserves the cost of the SMS message and then commits it later only if the SMS is successfully submitted, as indicated by the EventReportSMS received from the SMSC, or MSC. create_config.info question: `What SMS charging type is required for the default SMS service?`	1
Enable Relay SCCP (SMS MO service)	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. For more information about configuring the relay SCCP address, see the discussion about TCAP handover and relay configuration. create_config.info question: `Do you wish to enable relay sccp for the service?`	n
SMS Emergency Numbers (SMS MO service)	The comma-separated list of emergency numbers for the standard MO service. SMS messages to emergency numbers are continued without charge. create_config.info question: `Enter the list of numbers to be treated as emergency numbers in this service?`	911

SMS Service Configuration

The following example create_config.info section shows SMS service configuration:

Camel Gateway:SMS sms_mt:What charging Service ID should be used for the SMS MT service?4
Camel Gateway:SMS sms_mt:What SMS charging type is required for the SMS MT service?1
Do you wish to enable relay sccp for the service?
Enter the list of numbers to be treated as emergency numbers in this service?911
Camel Gateway:SMS default_sms:What charging Service ID should be used for the default SMS service?4
Camel Gateway:SMS default_sms:What SMS charging type is required for the default SMS service?1
Do you wish to enable relay sccp for the service?
Camel Gateway:SMS default_sms:Enter the list of numbers to be treated as emergency numbers in this service?911