ss7box User ManualOverviewContents
InstallationThe first step for all installations is to complete the ss7box Installation Questionnaire. Installing ss7box requires:
You should determine if you are installing ss7box as part of Sangoma Signal Media Gateway (SMG), SCP, STP, or some combination. If SMG functionality is needed then install with the standard SMG installation procedure; otherwise follow the instructions below. ALERT: Only works with 32 bit Linux kernels. GCC Rev 3.x compilers are recommended.
ConfigurationAll configuration files are found in /etc/ss7box. ss7box Wanpipe Configuration Filess7box.confOperationReading ss7box Output to /var/log/messagesAll messages have a text explanation and optional parameters that follow in a colon-separated format. Each message describes its own parameters.
Starting ss7box
Stopping ss7boxYou should stop ss7box only to change configuration or revisions of ss7box or xmtp2km. These events do not occur frequently. Stopping ss7box drops all SS7 links. Adjacent point codes will generate lots of alarms when SS7 links are down. In this case, the node technicians at the adjacent point codes will most likely put the offending links into a manually disabled state. You will need to coordinate manual enabling of the SS7 link to get it back in service. Once your links are up, leave them up unless you need to reconfigure or upgrade ss7box/xmtp2km. Any outages should be planned with the adjacent node operators and durations minimized.
Are The Links Up?Refer to SS7 Link Status.Finding the SS7 Links In a E1/T1This procedure samples the raw bitstream flow of the the entire E1/T1 as presented by the Sangoma Bitstream API which is channels 1-31 for E1 and 1-24 for T1. The wanpipeX.conf file is modified, so be sure to save existing wanpipeX.conf files if appropriate.
Checking Level 1While ss7box is running you can do the following:
Checking Level 2This is a brand new tool that runs the bitstreams through and HDLC decoder so the LSSU and FISU patterns can be seen. Here's how to install and use it. It will be included in new Sangoma driver releases.
Output: telco->ss7box, FISUs INCOMING Len=80 TimeStamp=59136 Mar 06 00:04:17 831279 [1/100s] Raw (HEX) FF FF 00 FF FF Raw (HEX) FF FF 00 FF FF Raw (HEX) FF FF 00 FF FF Raw (HEX) FF FF 00 FF FF Raw (HEX) FF FF 00 FF FF Raw (HEX) FF FF 00 FF FF Raw (HEX) FF FF 00 FF FF Raw (HEX) FF FF 00 FF FF Raw (HEX) FF FF 00 FF FF ss7box->telco, FISUs OUTGOING Len=80 TimeStamp=59143 Mar 06 00:04:17 837884 [1/100s] Raw (HEX) FF 83 00 9B A6 Raw (HEX) FF 83 00 9B A6 Raw (HEX) FF 83 00 9B A6 Command Line InterfaceMore to come....ConformanceThe compliance information is given in comma separated variable format so that it can be easily entered into a spreadsheet. The first value from the left is the test identifier, the second value is the test title, and the third value is:
Q.781LINK STATE CONTROL-EXPECTED SIGNAL UNITS/ORDERS1.1, Initialisation (Power-up), C1.2, Timer T2, C 1.3, Timer T3, C 1.4, Timer T1 and T4 (Normal), C 1.5, Normal alignment - correct procedure (FISU), C 1.6, Normal alignment - correct procedure (MSU), C 1.19, Set emergency while in "not aligned state", C 1.25, Deactivation during initial alignment, C 1.26, Deactivation during aligned state, C 1.29, Deactivation during link in service, C 1.32, Deactivation during proving period, C TRANSMISSION FAILURES3.1, Link aligned ready (Break Tx path), C3.3, Link aligned not ready (Break Tx path), C 3.5, Link in service (Break Tx path), C 3.7, Link in Processor outage (Break Tx path), C TRANSMISSION AND RECEPTION CONTROL (BASIC)8.1, MSU transmission and reception, CTRANSMISSION AND RECEPTION CONTROL (PCR)9.1, MSU transmission and reception, NCQ782 COMPATIBILITY/VALIDATION TESTSSIGNALLING LINK MANAGEMENT1.1, First signalling link activation (Configuration A), C1.2, Signalling linkset deactivation (Configuration A), (1) 1.3, Signalling linkset activation (Configuration A), (1) SIGNALLING MESSAGE HANDLING2.4, Load sharing within a linkset, C2.4.1, All links available (Configuration A), C 2.4.2, With one link unavailable (Configuration A), C 2.5, Load sharing between linksets, 2.5.1, Between two linksets (Configuration B), 2.7, Message transfer function (Configuration C), CHANGEOVER3.1, Changeover initiated at one side of a linkset (COO <-> COA) (Configuration A), (4)3.2, Changeover initiated at both ends at the same time (COO <-> COO) (Configuration A), (4) 3.16, Changeover to another linkset with the adjacent SP accessible (Configuration B), (2) 3.17, Changeover to another linkset with the adjacent SP inaccessible (Configuration B), (2) 3.20, Changeover as compatibility test (Configuration A), C CHANGEBACK4.1, Changeback within a linkset (Configuration A), C4.4, No acknowledgement to first CBD (Configuration A), C 4.8, Changeback from another linkset (Configuration B), C 4.11, Time controlled diversion procedure (Configuration B), C 5., Forced rerouting (Configuration B), (2) 6., Controlled rerouting (Configuration B), (2) MANAGEMENT INHIBITING7.1, Inhibition of a link, (5)7.1.1, Available link (Configuration A), (5) 7.1.2, Unavailable, (5) 7.2, Inhibition not permitted, (5) 7.2.1, Local reject on an available link, (5) 7.2.2, Local reject on an unavailable link, (5) 7.6, Manual uninhibition of a link, (5) 7.6.1, With changeback, (5) 7.6.2, Without changeback, (5) 7.8, Not possible uninhibiting, (5) 7.17, Management inhibiting test, (5) 7.17.1, Normal procedure, (5) SIGNALLING ROUTE MANAGEMENT9.1, Sending of a TFP on an alternative route,9.1.1, Failure of normal linkset (Configuration D), n/a 9.1.2, On reception of a TFP (Configuration D), n/a 9.2, Broadcast TFPs, 9.2.1, On one linkset failure (Configuration D), n/a 9.2.2, On multiple failures (Configuration D), n/a 9.4, Sending of a TFA on an alternative route, 9.4.1, Recovery of normal linkset (Configuration D), n/a 9.4.2, On reception of a TFA (Configuration D), n/a 9.5, Broadcast of TFAs, 9.5.1, On one linkset recovery (Configuration D), n/a 9.5.2, Various reasons (Configuration D), n/a SIGNALLING POINT RESTART10.1, Recovery of a linkset (SP has not the STP function),10.1.1, With use of point restart procedure (Configuration B), (6) 10.2, Recovery of a linkset (SP has the STP function), 10.2.1, With use of point restart procedure, n/a 10.5, Restart of an SP having no STP function (Configuration B), (6) 10.6, Restart of an SP having STP function (Configuration D), n/a SIGNALLING LINK TEST12.1, After activation of a link (Configuration A), C12.6, Additional SLTM/SLTA (Configuration A), C NOTESC means comply.1. command line interface link stop/start supported; CLI linkset stop/start not supported yet 2. worked in past; needs testing in lab; used only as F-link access device in last two years; if not working, fix date will be provided 3. n/a; not testing STP function 4. only emergency changeover supported; normal changeover will be supported in the future; date not known at this time; link failures are infrequent; traffic volume on signal link not above 1%; not essential for small systems 5. link inhibiting not supported; its absence has caused no inconvenience in any SMG installation so far; If a link is not to be used, then the telco or the ss7box side can simply stop the link; Inhibiting stops a link from being used but keeps the link aligned; Inhibiting has complicated rules for automatic uninhibiting in distress situations; the link inhibit procedure offers little value in operations, it is a complex implementation, and link stopping is a reasonable and simple alternative; comments to the contrary are welcome 6. MTP restart not supported; systems have low link count signal low traffic; opposite end of linksets have restart procedure and throttle linkset operation during restart Created by: admin last modification: Monday 09 of July, 2007 [15:43:13 UTC] by mike |
Login |