This topic presents the M3UA configuration file parameters. To satisfy entity dependency, configuration sections must be loaded to the M3UA task in the following order:
It is not required that these sections appear in this order in the text file, provided that the configuration program reads and downloads the sections in the correct order, as the provided m3uacfg sample file does.
The following table lists the configurable parameters in the M3UA general configuration section. The default values for all timers at the M3UA level are shown in milliseconds. A configuration value of zero for a timer disables that timer.
|
Parameter |
Default |
Description |
|
NODE_TYPE |
ASP |
Type of M3UA node. Only application server process (ASP) is currently supported. Use this parameter for both ASP and IPSP nodes. |
|
MAX_NSAP |
2 |
Maximum number of NSAPs supported simultaneously. |
|
MAX_NETWORK |
2 |
Maximum number of network contexts supported. There is one network context per variant and network indicator. |
|
MAX_ROUTE |
16 |
Maximum number of route entries supported, including local routes. |
|
MAX_DPC |
32 |
Maximum number of destination point codes (DPC) supported, including configured and dynamically learned DPCs. |
|
MAX_PS |
8 |
Maximum number of peer servers supported, including both local and remote peer servers. |
|
MAX_LPS |
4 |
Maximum number of local peer servers. |
|
MAX_PSP |
16 |
Maximum number of peer signaling processes supported. |
|
MAX_MSG |
128 |
Number of M3UA messages in transit supported. |
|
MAX_RNDRBN_LS |
4 |
Maximum number of peer servers that can use round-robin load sharing. |
|
MAX_SLS_LS |
4 |
Maximum number of peer servers that can use SLS-based (signaling link selector) load sharing. |
|
MAX_SLS |
128 |
Maximum number of SLS values that can be used by all peer servers. |
|
QUEUE_SIZE |
256 |
Outgoing congestion queue size per association. Messages above this limit are dropped. |
|
CONG_LEVEL1 |
64 |
Congestion level 1 in the queue; not valid in international networks. |
|
CONG_LEVEL2 |
128 |
Congestion level 2 in the queue; not valid in international networks. |
|
CONG_LEVEL3 |
196 |
Congestion level 3 in the queue; not valid in international networks. |
|
TMR_RESTART |
1000 |
Restart hold-off time. This parameter is only used in an SGP configuration. |
|
TMR_AS_PEND |
5000 |
Time for which a peer server can remain in an AS_PENDING state. |
|
TMR_ASP_UP1 |
2000 |
Initial time between ASPUP (ASP Up) retries. |
|
TMR_ASP_UP2 |
2000 |
Steady state time between ASPUP retries. |
|
NMB_ASP_UP1 |
3 |
Number of initial attempts at sending ASPUP messages at interval TMR_ASP_UP1 before sending them at interval TMR_ASP_UP2. |
|
TMR_ASPDN |
2000 |
Time between ASPDN (ASP Down) retries. |
|
TMR_ASPM |
2000 |
Time to wait before failing, after sending ASPAC (ASP Active) or ASPIA (ASP Inactive) messages. |
|
TMR_DAUD |
2000 |
Time between DAUD (Destination State Audit) messages. |
|
TMR_DRKM |
2000 |
Time between DRKM (Dynamic Routing Key Registration Message). |
|
NMB_DRKM |
3 |
Number of DRKM attempts before failing. |
|
TMR_SEQ_CNTRL |
1000 |
Delay used when diverting traffic to maintain sequencing. |
|
PC_FORMAT |
DFLT |
Point code format used for all point codes in the M3UA configuration files. DFLT = Point codes are interpreted and displayed as 24-bit 8.8.8 values. INTL = Point codes are interpreted and displayed as 14-bit 3.8.3 values. JNTT = Use for both Japan NTT and TTC networks. Point codes are interpreted and displayed as 16-bit mcode.scode.ucode values with the U-code in the most significant 7 bits, the S-code in the next 4 bits, and the M-code in the least significant 5 bits. |
|
TRACE_DATA |
FALSE |
Turns data tracing on or off. Data tracing is sent to the ss7trace utility. Refer to the TX Utilities Manual for information about ss7trace. Data tracing can also be turned on or off through the m3uamgr utility. Refer to the Dialogic® NaturalAccess™ SIGTRAN Stack Developer's Reference Manual for information about m3uamgr. |
|
DEBUG_LOG |
FALSE |
Turns debug logging on or off. Debug logging is sent to the txalarm utility. Refer to the TX Utilities Manual for information about txalarm. Debug logging can also be turned on or off through the m3uamgr utility. Refer to the Dialogic® NaturalAccess™ SIGTRAN Stack Developer's Reference Manual for information about m3uamgr. |
|
END |
N/A |
Marks the end of this general configuration definition. This parameter is required. |
The following table describes the M3UA network configuration parameters:
|
Parameter |
Default |
Description |
|
NETWORK_ID |
1 |
Network identifier. Valid range is 1 - 255. |
|
NETWORK_APPEAR |
1234 |
Network appearance code. Network appearance values are determined and configured by network operators on each side of an association. |
|
SSF |
NAT |
Subservice field. Valid values are: INTL = International NAT = National |
|
DPC_LENGTH |
24 |
DPC or OPC length. Valid values are: 14 = Length for ITU networks 16 = Length for Japanese networks 24 = Length for ANSI networks and other national variants |
|
SLS_LENGTH |
5 |
SLS length, in bits. Valid values are: 4 = SLS length 4 bits 5 = SLS length 5 bits 8 = SLS length 8 bits |
|
SERVICE_USER_VAR |
ANS |
Protocol variant of the M3UA service user, such as ISUP, SCCP, and TUP. Valid values are: ANSI = ANSI variant BICI = BICI ITU = CCITT variant China = China variant NTT = NTT Japan TTC = TTC Japan |
|
SERVICE_USER_VAR2 |
ANS |
Protocol variant for user of the M3UA service user, such as TCAP, which uses SCCP. Valid values are: ANSI = TCAP type ANSI ETSI = TCAP type ETSI ITU = TCAP type ITU |
|
END |
N/A |
Marks the end of this network configuration definition. This parameter is required. |
The following table describes the M3UA SCT SAP configuration parameters:
|
Parameter |
Default |
Description |
|
SCT_SAP_ID |
0 |
M3UA identifier for this SCT SAP. This value must be 0. |
|
SRC_PORT |
2095 |
Source port for the listening endpoint. |
|
SP_ID |
0 |
SCTP identifier for this SCT SAP. This value must be 0. |
|
END |
N/A |
Marks the end of this M3UA SCT SAP definition. This parameter is required. |
The following table describes the M3UA NSAP configuration parameters:
|
Parameter |
Default |
Description |
|
NSAP_ID |
0 for ISUP 1 for SCCP |
Identifier for this NSAP. |
|
NWK_ID |
1 |
Logical network identifier for this NSAP. |
|
SERVICE_TYPE |
ISUP |
Type of NSAP service user. Valid values are: ISUP = ISUP user SCCP = SCCP user TUP = TUP user BICC = BICC user |
|
END |
N/A |
Marks the end of this NSAP definition. This parameter is required. |
The following table describes the M3UA peer signaling process configuration parameters:
|
Parameter |
Default |
Description |
|
PSP_ID |
1 |
Peer service process (PSP) identifier. Valid values range from 1 to the result of (Max Number of PSP -1). |
|
PSP_TYPE |
IPSP |
Remote peer signaling process type. Valid values are: SGP = Signaling gateway process. IPSP = IP service process. |
|
IPSP_MODE |
DE |
Valid when PSP_TYPE = IPSP. Indicates whether the IPSP mode is single-ended or double-ended. Valid values are: DE = Double-ended mode SE = Single-ended mode |
|
DRKM_ALLOWED |
FALSE |
Indicates whether this peer signaling process can send and receive dynamic routing key management (DRKM) messages. Valid values are: TRUE = Peer signaling process can send and receive DRKM messages. FALSE = Peer signaling process cannot send or receive DRKM messages. |
|
USE_NWK_APP |
FALSE |
Determines whether the optional network appearance parameter is included when communicating with the remote peer. Valid values are: TRUE = Include the network appearance parameter. FALSE = Do not include the network appearance parameter. |
|
ASP_ID_MAND |
NONE |
Indicates whether an ASP identifier is required in sent and/or received ASPUP and ASPUP ACK (ASP Up Acknowledgement) messages. Valid values are: RX = Identifier is required in received ASPUP and ASPUP ACK messages. TX = Identifier is required in transmitted ASPUP and ASPUP ACK messages. BOTH = Identifier is required in transmitted and received ASPUP and ASPUP ACK messages. NONE= ASP ID not required in transmitted or received ASPUP and ASPUP ACK messages. |
|
NWK_ID |
1 |
Default network context identifier for incoming messages, if the messages do not include one. |
|
CFG_ALL_LPS |
FALSE |
Whether this PSP needs to be configured for all local peer servers: TRUE = Configure all local peer servers with this PSP. FALSE indicates = Do not configure all local peer servers with this PSP. |
|
Association parameters |
||
|
PRIME_DEST_ADDR |
192.168.1.2 |
Primary destination address of the remote peer used in outgoing association requests. |
|
DEST_PORT |
2905 |
Remote SCTP port. |
|
CLIENT_SIDE |
TRUE |
TRUE = Associations are automatically initiated from this PSP, if PSP_TYPE = IPSP. FALSE = Associations are not initiated from this PSP, if PSP_TYPE = IPSP. The other side is expected to initiate any associations. |
|
NMB_OUT_STREAMS |
2 |
Number of streams supported by this association. Valid range is 1 - 255. |
|
TOS |
0 |
Type of Service octet sent in all outgoing packets for this association. This can be changed later using the M3UA management API. For more information, refer to Dialogic® NaturalAccess™ SIGTRAN Stack Developer’s Reference Manual. |
|
END |
N/A |
Marks the end of this PSP configuration definition. This parameter is required. |
The following table describes the M3UA peer server configuration parameters:
|
Parameter |
Default |
Description |
|
PS_ID |
N/A |
Peer server identifier. |
|
NWK_ID |
1 |
Peer server network identifier. |
|
MODE |
ACTSTANDBY |
Peer server availability mode. Valid values are: ACTSTANDBY LOADSHARE BROADCAST (not supported) |
|
LOAD_SHARE_TYPE |
ROUND_ROBIN |
If MODE = LOADSHARE, the LOAD_SHARE_TYPE parameter selects the type of load sharing to use. Valid values are: ROUND_ROBIN SLS |
|
LOCAL |
FALSE |
Indicates whether the peer server is local or remote: TRUE = Local peer server FALSE = Remote peer server |
|
PSP |
1 |
Ordered list of PSP identifiers configured in the system that handle the routing key associated with this PS. Preference is given to earlier entries in the list when performing fail-over or fail-back procedures. Valid values are 1 to MAX_PSP. |
|
RTE_CTX |
0 |
Routing context. Allowed value is any unsigned 32-bit integer. |
|
END |
N/A |
Marks the end of this peer server definition. This parameter is required. |
The following table describes the M3UA routing configuration entry parameters:
|
Parameter |
Default |
Description |
|
DPC |
N/A |
Destination point code associated with this route. |
|
DPC_MASK |
0xFFFFFF |
Wildcard mask for the DPC. In most cases, set to all 1 bits to use the entire DPC for routing. |
|
OPC |
0 |
Origination point code (OPC) associated with this route, if any. |
|
OPC_MASK |
0 |
Wildcard mask for the OPC. In most cases, set to all 1 bits (0xFFFFFF) to use the entire OPC for routing, if OPC routing is required. Otherwise, set to 0 to indicate that OPC routing is not used. |
|
SIO |
0 |
Service information octet (SIO) associated with this route, if any. Valid values are ISUP, SCCP, BICC, TUP, or a numeric value between 0 and 0xF. Note: If SIO is not specified, the default is 0, which indicates that SIO is not used for routing. |
|
SIO_MASK |
0 |
Wildcard mask for the service information octet (SIO). If SIO is set, set SIO_MASK to 0xF to use the specified SIO value for routing. Set SIO_MASK to 0 if SIO routing is not used. |
|
RTE_TYPE |
PS |
Route type. Valid value is PS. |
|
NWK_ID |
1 |
Network identifier. Valid range is 1 - 255. |
|
NSAP_ID |
0 |
NSAP identifier configured in the system with which this route is associated. Used only for local (or up) routes. Do not specify for remote routes. |
|
RTE_PS_ID |
0 |
Identifier of the peer server associated with this route. |
|
END |
N/A |
Marks the end of this routing entry definition. This parameter is required. |