Global Call SS7 Technology User's Guide for Windows: 6.1.1. Intel® NetStructure™ SS7 Board Systems

6.1.1. Intel® NetStructure™ SS7 Board Systems

Verify an Intel® NetStructure™ SS7 board system configuration as follows:

Depending on the type of Intel® NetStructure™ SS7 board being used, add debug flags to the system.txt file as follows:

For Intel® NetStructure™ SS7 ISA (PCCS6) board systems: Add debugging flags to SSD and S7_MGT modules and make sure S7_LOG is launched:
            FORK_PROCESS   .\SSD.EXE -d 
            FORK_PROCESS   .\SSD_POLL.EXE 
            FORK_PROCESS   .\TIM_NT.EXE 
            FORK_PROCESS   .\TICK_NT.EXE 
            FORK_PROCESS   .\S7_MGT.EXE -d 
            FORK_PROCESS   .\S7_LOG.EXE -m0xef  
For Intel® NetStructure™ SS7 CompactPCI and PCI board systems: Add debugging flags to SSD and S7_MGT modules and make sure S7_LOG is launched:
            FORK_PROCESS   .\SSD.EXE -d 
            FORK_PROCESS   .\TIM_NT.EXE 
            FORK_PROCESS   .\TICK_NT.EXE 
            FORK_PROCESS   .\S7_MGT.EXE -d 
            FORK_PROCESS   .\S7_LOG.EXE -m0xef  
Start GCTLOAD and watch out for any error message (for example, "Timeout waiting for..."). A first part of the boot sequence should show messages similar to the following (important steps are in bold):
     (61)gctload: Initialisation complete 
     
     S7_log : mod ID=0xef, options=0xaf0d 
     S7MGT >> M-t7f0f-i0000-fcf-dcf-s00-p(8)00ff000000000000 
     S7MGT << M-t7f0f-i0000-fcf-dcf-s00-p(8)00ff000000000000 
     S7MGT >> M-t7680-i0000-fcf-d20-s00-p(24)200000cf70637337332e646331000000000
     0000000000010 
     ssd : 16 boards 
     S7MGT << M-t3680-i0000-fcf-dcf-s00-p(24)200000cf70637337332e646331000000000
     0000000000010 
     S7MGT >> M-t7681-i0000-fcf-d20-s00-p(24)0001000000006973757037362e646332000
     0000000000000 
     ssd[0] : pccs6 
     ssd[0] : reset requested 
     S7MGT << M-t3681-i0000-fcf-dcf-s00-p(24)0001000000006973757037362e646332000
     0000000000000 
     ssd[0] : code download requested 
     ssd[0] : code download started(isup76.dc2) 
     ssd[0] : code download complete 
     ssd[0] : run requested 
     ssd[0] : running  
If a "Timer expiry" message is displayed after the "ssd[0] : reset requested" line above, it is likely that the I/O settings are incorrect. Try different I/O port and/or SRAM address settings. These settings can be changed using the PCCSXCFG tool as described in the SS7 Programmer's Manual for PCCS6. Remember that the I/O port value must also be changed accordingly on the SW1 switch on the board.

If a "Reset failed" message is displayed on the console, check that the PCCS device is started. Open the "Devices" part of the Windows NT Control Panel and check the status of the PCCS device. The PCCS device is started when you run the PCCSXCFG toll. However, the PCCS device is set to manual mode and is consequently not restarted when you reboot your system. It is recommended to change the startup mode to Automatic.

For Intel® NetStructure™ CompactPCI and PCI boards, there should be an Intel® NetStructure™ SS7 device. In Windows 2000, right click on My Computer, then choose Manage to open the Computer Managerment dialog. Select Device Manager, then choose Show hidden devices from the View menu. Under Non-Plug and Play Drivers, there should be an Intel® NetStructure™ SS7 device and you can check if it has started or not.

Note: If an Intel® NetStructure™ SS7 device does not appear in the Non-Plug and Play Drivers list, type net start Septel at the command line.

At this point, the last thing you should see on the console is "S7_MGT Boot Complete" and a final S7_MGT message:
     S7MGT << M-t3311-i0001-fcf-dcf-s00-p(16)00010171000100060000000000000000 
     S7MGT >> M-t7312-i0000-fcf-d22-s00-p(32)00000002000000000000002000000000000
     00000000000000000000000000000 
     S7MGT << M-t3312-i0000-fcf-dcf-s00-p(32)00000002000000000000002000000000000
     00000000000000000000000000000 
     S7MGT >> M-t7700-i0000-fcf-d23-s00-p(40)0475234d4d22004d0001000a00020040011
     085000000000000000000000000000000000000000000 
     S7MGT << M-t3700-i0000-fcf-dcf-s00-p(40)0475234d4d22004d0001000a00020040011
     085000000000000000000000000000000000000000000 
     S7MGT >> M-t7701-i0000-fcf-d23-s00-p(30)0000000100000002000100017fff7fff001e
     000000000000000000000000 
     S7MGT << M-t3701-i0000-fcf-dcf-s00-p(30)0000000100000002000100017fff7fff001e
     000000000000000000000000 
     S7MGT >> M-t7701-i0001-fcf-d23-s00-p(30)0000000100000002002100217fff7fff001e 
     000000000000000000000000 
     S7MGT << M-t3701-i0001-fcf-dcf-s00-p(30)0000000100000002002100217fff7fff001e
     000000000000000000000000  
             **************************** 
             *   S7_MGT Boot complete   * 
             ****************************  
     S7MGT << M-t3f0f-i0000-fcf-dcf-s00-p(8)00ff000000000000  
Check that all messages on this last screen have a status of 0, indicating success. The status is indicated as -sXX in each message, where XX is an hexadecimal number.Does this mean that the successful status is -s00? This is confusing.
If, instead of the "S7_MGT Boot complete" message, you receive an "S7_MGT: Timeout occurred" message, check that the firmware you have specified in your config.txt file corresponds to the license button installed on the board.
Activate the MTP link(s) using the MTPSL tool (assuming linkset id 0 and link 0):
     MTPSL ACT 0 0  
If the MTP link is configured properly and activated at the adjacent point code and your system is properly clocked (this might require that Intel® Dialogic boards be downloaded if the Intel® NetStructure™ SS7 ISA (PCCS6) board is taking its clock from the SCbus), you should see messages similar to the ones below. The important thing to check for is the presence of "Destination available".
     S7L:I00 MTP Event : linkset_id/link_ref=0000 Changeback 
     S7L:I00 MTP Event : linkset_id=00 Link set recovered 
     S7L:I00 MTP Event : linkset_id=00 Adjacent SP accessible 
     S7L:I00 MTP Event : point code=00000002 
      Destination available  
If no other message appears on the console after a couple of minutesFred thinks the phrase "for a couple more minutes" is inappropriately informal as well as being vague., you can reasonably assume that your configuration is correct.
 

Click here to contact Telecom Support Resources