Once boards are loaded and successfully communicating, normal data traffic can begin.
If links are not established and/or data traffic is not successful, there may be a problem with the redundant MTP or SIGTRAN configuration.
Check the MTP link status to determine if the links are up. Use the mtpmgr application to determine the link status. MTP configuration provides a sample MTP configuration for each board having a single link to a third node at point code 2.2.2. Performing a status link * command for Node 1 for this configuration produces the following results:
Num Name MTP3 State MTP2 Hi State Low State
0 T1 ACTIVE ENABLED IN_SERVICE
1 R ACTIVE REMOTE
Performing the same command for Node 2 produces the following results:
Num Name MTP3 State MTP2 Hi State Low State
0 R ACTIVE REMOTE
1 T1 ACTIVE ENABLED IN_SERVICE
If the links are expected to be enabled and active, but are not in this state, check the MTP configuration.
Ensure that the proper MTP configuration file is called from the proper ss7load script listed in the HMI configuration file. Also verify that links are configured with valid port types on the board they are physically terminated on and are configured as remote (R) on the mate board. For more information, refer to MTP configuration over TDM.
If the port type appears to be configured correctly but the links do not come into service, other problems may exist. Refer to the Dialogic® NaturalAccess™ Signaling Software Configuration Manual for information on troubleshooting MTP configurations.
In a SIGTRAN configuration, check the SIGTRAN association status to determine if associations were established and M3UA management messages were exchanged correctly. To check the SIGTRAN association status, use the status psp 1 command, and check the values for State and ASP State in the output. For example:
m3uamgr[1]>status psp 1
=====================PSP 1 Association Status===================
AssocId = 0 State = ACTIVE ASP State = ACTV Inhibit = NO
=================Active PSs (4)=================
PsId = 3
PsId = 4
PsId = 1
PsId = 2
=================Registered PSs (0)==============
None
=====================Current PSP 1 Confuration=================
pspType = IPSP ipspMode = DBL END dynRegAllow = YES
loadShareMode = RNDRBN nwkAppIncl = NO rxTxAspId = NO
selfAspId = 0 nwkId = 1 PriDestAddr = 10.51.1.185
DestPort = 2905 locOutStrms = 2
The following table describes the association states:
|
Association state |
Description |
|
ACTIVE |
An association is established. |
|
DOWN |
No association is established. If M3UA is configured as an ASP or IPSP client, there is probably a configuration or connectivity problem. For information, refer to Checking the SIGTRAN configuration. |
The following table describes the ASP states:
|
ASP state |
Description |
|
ACTV |
ASPAC messages were exchanged, and traffic can flow. |
|
DOWN |
No M3UA ASP messages were exchanged. This should only occur if the association State is also DOWN. |
|
INACTV |
ASPUP messages were exchanged, but not ASPAC messages. This can occur if an upper layer has not yet bound to M3UA, or if this is the backup node. The ASPAC messages will be sent as soon as an upper layer binds to M3UA or the node becomes the primary node, or both. |
Ensure that the proper M3UA and SCTP configuration files are called from the proper ss7load script listed in the HMI configuration file. Also verify that the primary destination address specified for each PSP is correct. For more information, refer to M3UA and SCTP configuration over IP (SIGTRAN).
If the configurations seem correct, verify that you have connectivity from each board to the remote nodes. Use the cpcon utility to send pings from each board to the destination addresses.
If the configuration and connectivity seem OK, other problems may exist. Refer to the Dialogic® NaturalAccess™ Signaling Software Configuration Manual for more information about troubleshooting SIGTRAN configurations.
Once both boards of the redundant set are loaded and communicating and links are established, ISUP tests can take place using:
Applications
orig and term demonstration programs (refer to the Dialogic® NaturalAccess™ ISUP Layer Developer's Reference Manual)
Once both boards are loaded and communicating and the links are established, TCAP tests can take place using:
Applications
find800 demonstration program (refer to the Dialogic® NaturalAccess™ TCAP Layer Developer's Reference Manual)
Once both boards of the redundant set are loaded and communicating and links are established, TUP tests can take place using:
Applications
tuporig and tupterm demonstration programs (refer to the Dialogic® NaturalAccess™ TUP Layer Developer's Reference Manual)
Once both boards are loaded and communicating and the links are established, SCCP tests can take place using:
Applications
sccpdemo demonstration program (refer to the Dialogic® NaturalAccess™ SCCP Layer Developer's Reference Manual).