Sample authGateway Command and File

sampleCreateProcess.mml

authGateway.conf (Gateway Routing Configuration File)

Each line of this configuration file describes:

The parameters used to form the destination SCTP address.
The decimal value of the bearer service (bs) and/or teleservices (ts) indicating an authorization.
A string associated with each bs or ts value. If no bs and no ts are specified, no authorization is performed by the authGateway.

For each request, the first digits of the IMSI are compared with odigits. The first line of the configuration file that matches is selected for the current request. If the routing indicator (rri) specifies that the routing is done on GT, the leading digits are replaced with the new digits (ndigits) to perform the numbering plan translation. If a parameter is not present on the line, it is not present in the destination SCTP address. If this is incompatible with the routing indicator, an error message is issued when the MAP authentication Gateway is started.

After modifying this configuration file, the authGateway has to be restarted. Modification of the ndigits value may require the creation of a new GT rule (CREATE-GT command).

Table 46: Parameters Used in Create and Start Commands

Parameter	Description
rri	Routing indicator - 0 for GT (Global Title), 1 for PC/SSN (Point Code/Subsystem Number).
rgti	Local Global Title Indicator value. 4 for C7; 2 for A7. (Usually 4.)
rssn	Subsystem Number of HLR.
rtt	(GT only) Translation Type (usually 0).
rnp	(GT only) Numbering Plan. 1=E.164=ISDN-TEL, 7=E.214=ISDN-MOB.
rnai	Nature of address indicator. (4=INT)
bs	`bs` `dec`:`string` If the specified bearer service exists in HLR SIM-profile, then `string` is returned for further processing (see ProfileMap in `simauth`.aut).
ts	`ts` `dec`:`string` If the specified teleservice exists in HLR SIM-profile, then `string` is returned for further processing (see ProfileMap in simauth.aut).