History: ss7boost User ManualSource of version: 28 (current)!Overview
__Contents__{maketoc} !Installation --- #Copy ss7boost_<version> to /usr/local/ss7box #Copy/create /etc/ss7box/ss7boost.conf from template file #Copy/create /etc/ss7box/tgN_isup_timer.conf where N is 0..n and each N is a trunk group identifier from template file ((SMG Installation)) does this automatically. !Configuration --- All configuration files are found in /etc/ss7box. !!((ss7boost.conf)) !!((tgN_isup_timers.conf)) !Operations --- *All commands are executed from /usr/local/ss7box unless otherwise noted. !!Starting ~pp~# ./ss7boost_<version> {-v}~/pp~ *ss7boost is started automatically using the re-sync.sh script described in the Operations section of the SMG User Manual. *Manually starting ss7boost is most often used by development and support staff. *-v option enables verbose logging for the Verbose Group defined in ((ss7boost.conf)). !!Stopping ~pp~# ./ss7boost_<version> --term~/pp~ !!Checking Revision Currently the revision is part of the ss7boost executable file name. This practice will be curtailed in the future to make it easier to maintain control scripts. ~pp~[root@b2 smg]# ss7box/ss7boost_i_0.2.43.38diag --ver Xyganda Technology, Inc. ss7boost Revision 0.2.43.38diag~/pp~ !!Circuit Blocking/Unblocking Circuit blocking prevents use of a particular span and channel, while unblocking allows use of it. This is a necessary tool for managing use of trunks and circuits for transmission maintenance, troubleshooting, and software upgrading. In this discussion, the terms trunk, span, wanpipe, and E1/T1 are used interchangeably as demonstrated in the previous sentence. Also, circuit and span/chan are equivalent terms. There are two kinds of blocking: hardware and maintenance. When a wanpipe is enabled, the span and channels assigned to the E1/T1 are either blocked or unblocked according to Initial Block parameter for each trunk in the [[TRUNK] section of ((ss7boost.conf)). When a wanpipe is stopped, or if it fails, Using the commands described below the user can change the blocked/unblocked state of a circuit. !!Command Line Interface The CLI is used to control ss7boost operation while it is running as a daemon. The CLI is composed of the ((ss7boost_cli)) program and ss7boost. ss7box_cli provides the human interface and sends and receives packetized information to ss7boost to execute the commands specified on the human interface. !Conformance --- The 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: *C - comply *NC - does not comply, no plans to comply at this time *(n) - see note n in Notes section !!Q784 Compatibility/Validation Tests !!!Circuit Supervision and Signaling Supervision 1.1, Non allocated circuit, C 1.2.1, RSC received on an idle circuit, C 1.2.2, RSC sent on idle circuit, C 1.2.3, RSC received on a locally blocked circuit, (10) 1.2.4, RSC received on a remotely blocked circuit, (10) 1.2.5, Circuit group reset received, (11) 1.2.6, Circuit group reset sent, (11) 1.2.7, Circuit group reset received on remotely blocked circuits, (10) 1.3.1.1, CGB and CGU received, (10) 1.3.1.2, CGB and CGU sent, (10) 1.3.2.1, BLO received, C 1.3.2.2, BLO sent, C 1.3.2.3, Blocking from both ends; removal of blocking from one end, (10) 1.3.2.4, IAM received on remotely blocked circuit, (10) 1.4.1, CCR received successful, (12) 1.4.2, CCR sent successful , (12) 1.4.3, CCR received unsuccessful, (12) 1.4.4, CCR sent unsuccessful, (12) 1.4.5, CCR received successful, verify timer T27, (12) 1.5.1, Receipt of unexpected messages, C 1.5.2, Receipt of unexpected messages during call setup, C 1.5.3, Receipt of unexpected messages during a call, C 1.5.4, Confusion procedures, (13) !!!NORMAL CALL SETUP :-ORDINARY SPEECH CALLS 2.1, Bothway circuit selection, 2.1.1, IAM sent by controlling SP, C 2.1.2, IAM sent by non-controlling SP, C 2.2, Called address sending, 2.2.1, ))En-Block(( operation, C 2.2.2, Overlap operation, C 2.3, Successful operation, 2.3.1, Ordinary call; various indicators in ACM, C 2.3.2, Ordinary call; various indicators in CPG or ANM, C 2.3.3, Ordinary call; various indicators in CON, C 2.3.4, Call switched via satellite (only from VSAT), (15) 2.3.5, Echo control procedure for call setup, (16) 2.3.6, Blocking and unblocking during a call (initiated), (10) 2.3.7, Blocking and unblocking during a call (received), (10) !!!NORMAL CALL RELEASE 3.1, Calling party clears before ACM, C 3.2, Calling party clears before ANM, C 3.3, Calling party clears after ANM, C 3.4, Called party clears after ANM, C 3.5, Suspend initiated by network, (17) 3.6, Suspend and resume initiated by calling party, (17) 3.7, Suspend initiated by called party, (17) 3.8, Collision of REL messages, C !!!UNSUCCESSFUL CALL SETUP 4.1, Validate a set of knows causes for release, C !!!ABNORMAL SITUATIONS DURING A CALL 5.1, Inability to release in response to a release after ANM, 5.2, Timers, 5.2.1, T7; waiting for an ANM, C 5.2.2, T9; waiting for a ACM or CON, (18) 5.2.3, T1 and T5; failure to receive a RLC, C 5.2.4, T6; waiting for a RES (Network) message, (17) 5.2.5, T8; waiting for COT message if applicable, (12) 5.2.6, T12 and T13; failure to receive a BLA, (10) 5.2.7, T14 and T15; failure to receive a UBA, (10) 5.2.8, T16 and T17; failure to receive a RLC, C 5.2.9, T18 and T19; failure to receive a CGBA, (10) 5.2.10, T20 and T21; failure to receive a CGUA, (10) 5.2.11, T22 and T23; failure to receive a GRA, (11) Not-in-Q784, T33 INR/INF procedure, (19) 5.3, Reset of circuits during a call, 5.3.1, Reset of circuits during a call - of an outgoing circuit, C 5.3.2, Reset of circuits during a call - of an incoming circuit, C !!!SPECIAL CALL SETUP 6.1.1, Continuity check required, (12) 6.1.2, COT applied on previous circuit, C 6.1.3, Calling party clears during a COT, (12) 6.1.4, Delay of through connect, (12) 6.1.5, COT unsuccessful, (12) 6.2, Automatic repeat attempt, 6.2.1, Dual seizure for non-controlling SP, C 6.2.2, Blocking of a circuit, (10) 6.2.3, Circuit reset, (20) 6.2.4, Continuity check failure, (12) 6.2.5, Reception of unreasonable signalling information, (21) 6.3, Dual seizure, 6.3.1, Dual seizure for controlling SP, C 6.4, Semi-automatic operations, 6.4.1, FOT sent following a call to a subscriber, (22) 6.4.2, FOT received following a call to a subscriber, (22) 6.4.3, FOT sent following a call via codes 11 and 12, (22) 6.4.4, FOT received following a call via codes 11 and 12, (22) !!!BEARER SERVICES 7.1, 64 kbit/s unrestricted, 7.1.1, Successful call setup, (23) 7.1.2, Unsuccessful call setup, (23) 7.1.3, Dual seizure, (23) 7.2, 3.1 kHz audio, 7.2.1, Successful call setup, C !!!Notes 10. circuit and circuit group blocking/unblocking is under development; ready date is expected in March 2007 11. Circuit group reset is not completely functional; will address after blocking in complete; response is given but actions are not taken; expected ready date in Feb 2007 12. continuity testing not fully supported; not sure how valuable it is for a small platform; have not had much demand for it; COT on previous support exists as noted 13. confusion not implemented; has not been a problem so far 14. number not used 15. VSAT not supported 16. echo control not dynamically supported; either all on or all off per facility; control in Sangoma driver 17. suspend/resume operation partially supported; not hard to implement; feature on hold for several months for lack of criticality 18. T9 not implemented; needs to be done; not hard; could be done in Jan-Mar timeframe 19. INF/INR not implemented; lack of interest 20. auto repeat call on reset not supported; found requirement while working on blocking; will fix during block implementation; expected ready in Jan-Feb 21. more testing needed 22. FOT not supported; lack of interest 23. 64 kb/s not tested; support possible - probably without trouble |
Login |