[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]


Configuring the SMSGateway Application for MSC Communication

The SMSGateway application manages all communication between Steel-Belted Radius Carrier and the MSC. The SMSGateway application also implements the MAP (Mobile Application Port) protocol and MAP messages that get sent through the Signalware protocol stack and out to the MSC (and back).

Configuration of the SMSGateway application requires the following activities:

Each of these activities is described in the following sections.

Configuring the SMSGateway Routing Location Information

This activity assigns the local routing options and identifies the point code of the MSC and the remote application using the MML commands shown in Table 44.

Table 44: MML Commands for Configuring the SMSGateway Routing Location Information
MML Command
Description

CREATE-CPC

Identify the concerned point code (CPC), which is the destination point code and the local application (authGateway).

CREATE-REMSSN

Identify the point code of the HLR and the remote application.

CREATE-GT

Create a global title translation for the remote HLR (if Global Title routing is used).


For more information about the syntax and usage of the MML commands, see Signalware MML Commands276.

Example

Line 1 (CREATE-CPC): SMSGateway is assigned a subsystem number (SSN) of 242 on the local host and the concerned point code on the MSC is identified as 3003.

Line 2 (CREATE-REMSSN): The subsystem number (application) on the remote host is identified as 241.

Line 3 (CREATE-GT): Global Title type translation will be used so that digits 987 will be sent to PC,SSN=3003,241. RI is not supplied in the CREATE-GT command and therefore defaults to DEF (do not modify) and uses the routing setting of the incoming message.

CREATE-CPC:PC=3003,SSN=242;
CREATE-REMSSN:PC=3003,SSN=241;
CREATE-GT:TT=0, NP=ISDN-TEL, NA=INT, DIG="987", PC=3003, SSN=241;


NOTE: MML commands are saved in MML files which can be loaded into Signalware. See Loading the MML Configuration Settings293.


Configuring the SMSGateway.conf File

The SMSGateway.conf file is the configuration file that specifies routing and options of the SMSGateway application.

Table 45: Local Routing Options for SMSGateway.conf 
Option
Description

lpc

Local Point Code (PC) (required).

lssn

Local Subsystem Number (SSN) (required).

oatype

Originating Address type:

0 — Unknown type

1 — International number

2 — National number

3 — Network-specific number

4 — Subscriber number

5 — Alphanumeric number

6 — Abbreviated number

oanp

Originating Address numbering plan:

0 — Unknown

1 — ISDN/telephone numbering plan (E.164/E.163)

3 — Data numbering plan (X.121)

4 — Telex numbering plan

8 — National numbering plan

9 — Private numbering plan

10 — ERMES numbering plan (ETSI DE/PS 3 01-3)

Refer to 3G TS 23.040 for more information on numbering plan values.

oadigits

Originating Address digits.


.

Table 46: Remote Routing Options for SMSGateway.conf Process 
Option
Description

rgti

Remote GTI value, usually 4 for C7 and 2 for A7.

rnai

Nature of Address Indicator. Indicates the scope of the address value, such as whether it is an international number (includes country code) or a national number (no country code).

1 — Subscriber Number with no area code (example: 5551234

2 — unused

3 — National Significant Number with no country code (example: 2015551234)

4 — International Number including country code (example: 12015551234)

rnp

Remote Numbering Plan.

Acceptable values are:

1 — ISDN/Telephony

3 — DATA

4 — TELEX

5 — Maritime Mobile

6 — Land/Mobile

7 — ISDN/Mobile

10 — British Telecom special 1

11 — British Telecom special 2

14 — Private Network

rpc

Remote Point Code. Point Code of MSC.

rri

Remote Routing indicator - 0 for GT (Global Title), 1 for PC/SSN.

rssn

Subsystem Number of MSC.

rtt

Remote Translation Type. Generally in a live network TT will always be 0.


Example

DestAddress rnai 4 rnp 1 rgti 4 rtt 0 rri 0
LocalAddress lpc 3003 lssn 7 ldigits 1234 oatype 1 oanp 1 oadigits 7654321

Configuring the SMSGateway Startup Information

The CREATE-PROCESS and START-PROCESS MML commands start the smsGateway (by calling smsGatway.conf), using options that you specify.

Table 47 describes the MML commands needed to configure the start of smsGateway.

Table 47: MML Commands for Configuring the Start of SMSGateway 
MML Command
Description

CREATE-PROCESS

Identify the SMSGateway configuration file and the SMSGateway options.

START-PROCESS

Start the process.


For more information about the syntax and usage of the MML commands, see Signalware MML Commands276.

Table 48 lists the options that you can be use with the CREATE-PROCESS command for local address options. Table 49 lists the options that you can use with the CREATE-PROCESS command for remote address options.

Table 48: Routing Options for the SMSGateway Process Used with CREATE-PROCESS Command 
Option
Description

appctx

MAP protocol revision (2 or 3).

conf

Path and name of the SMSGateway configuration file. The default file is OMNI_HOME/conf/SMSGateway.conf.

debug

Sets a debug level. Use the following:

-debug 0xff

host

Local hostname.

invkretry

Number of invoke retry.

invktimeout

Duration of invoke timeout in seconds.

ldigits

MSISDN of the local node.

lgti

Local GTI value, usually 4 for C7 and 2 for A7.

lmsisdn

MSISDN of the local node. (Same as ldigits.)

lnai

Local Nature of Address Indicator. Indicates the scope of the address value, such as whether it is an international number (includes country code) or a national number (no country code).

1 — Subscriber Number with no area code (example: 5551234

2 — unused

3 — National Significant Number with no country code (example: 2015551234)

4 — International Number including country code (example: 12015551234)

lnp

Local Remote Numbering Plan.

Acceptable values are:

1 — ISDN/Telephony

3 — DATA

4 — TELEX

5 — Maritime Mobile

6 — Land/Mobile

7 — ISDN/Mobile

10 — British Telecom special 1

11 — British Telecom special 2

14 — Private Network

lnp

Local Numbering Plan

Acceptable values are:

1 — ISDN/Telephony

3 — DATA

4 — TELEX

5 — Maritime Mobile

6 — Land/Mobile

7 — ISDN/Mobile

10 — British Telecom special 1

11 — British Telecom special 2

14 — Private Network

lpc

Local Point Code (PC) (required).

lri

Routing indicator - 0 for GT (Global Title), 1 for PC/SSN.

lssn

Local Subsystem Number (SSN) (required).

ltt

Local Translation Type. Generally in a live network TT will always be 0.

max_requests

Maximum number of simultaneous MAP dialogs.

max_RoutingInfo

Maximum number of routing information cached.

name

Name of the process.

node

Node name.

port

Port number used by the SCTP association with the client.

prot

Variant used (C7, A7 or CH7).

routingInfoExp

Validity time for routing information.

smsc

Service center address.

tp_oa

Originating address information in SMS header.

The tp_oa field is made up of three fields: oatype, oanp, and oadigits. It is recommended to use these three fields as local routing options for SMSGateway.conf, rather than the tp_oa field.

For information about oatype, oanp, and oadigits, see Table 45.

trace

Enables debug tracing and displays the trace information on the console. (Consists of a trace of all MAP messages that are formatted and sent down the stack.)

Use the tracefile option to capture the trace information to a file.

tracefile

Captures the trace information to a file. The filename follows the -tracefile switch. Include the directory in the filename.


.

Table 49: Remote Routing Options for the SMSGateway Process used with CREATE-PROCESS Command 
Option
Description

rnai

Remote Nature of Address Indicator. Indicates the scope of the address value, such as whether it is an international number (includes country code) or a national number (no country code).

1 — Subscriber Number with no area code (example: 5551234

2 — unused

3 — National Significant Number with no country code (example: 2015551234)

4 — International Number including country code (example: 12015551234)

rnp

Remote Numbering Plan

Acceptable values are:

1 — ISDN/Telephony

3 — DATA

4 — TELEX

5 — Maritime Mobile

6 — Land/Mobile

7 — ISDN/Mobile

10 — British Telecom special 1

11 — British Telecom special 2

14 — Private Network

rgti

Remote GTI value, usually 4 for C7 and 2 for A7.

rtt

Remote Translation Type. Generally in a live network TT will always be 0.


Example—Creating and Starting the smsGateway Process

We recommend that the EXEC command use an absolute (full) pathname.

(Lines are wrapped.)

CREATE-PROCESS:NAME="SMS", CE="quark", 

EXEC="/opt/funk/radius/smsGateway -name SMS -port 2004 -host quark -node MGW -prot C7 -conf 
/opt/funk/radius/conf/smsGateway.conf -lri 1 -lpc 2730 -lssn 242 -rssn 241 -appctx 3";
START-PROCESS:NAME="SMS", CE="quark";

Configuring the smsulcmmg.conf File

The smsulcmmg.conf file establishes the connection between the SMSGateway application and Steel-Belted Radius Carrier.

The smsulcmmg.conf file consists of two lines, as shown in the example that follows. Modify the smsulcmmg.conf file shipped with SIM Server so that the LOCAL_HOST (Steel-Belted Radius Carrier) and REMOTE_HOST (Signalware system) values identify their DNS names and TCP port numbers. If you specify a DNS name for a local or remote host, you can enter the host's IP address in brackets as a backup.

Example

LOCAL_HOST quark:2005
REMOTE_HOST quark:2004 [172.25.97.230]

[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]