History: Past BlogsSource of version: 1 (current)-=2006-11-25 ss7boost 0.2.57 Released (preliminary)=-
__Features__ ((ss7boost_cli)) is being introduced. __Changes__ Python CLI scripts no longer work with this release of ss7boost. __Fixes__ User configurable SIO priority and network indicator are always set correctly now. __Availability__ Expected on 2006-11-27. -=2006-11-13 Three Releases=- __sangoma_mgd 1.5 Released__ __Features__ New RX/TX Gain options in /etc/sangoma_mgd.conf~pp~ rxgain=>0 txgain=>0~/pp~ These options can be used to adjust rx tx gain. These options are identical tozaptel options in zapata.conf. __Changes__ None. __Fixes__ Bug fix in START_NACK_ACK handling. __Availability__ ftp.sangoma.com/linux/smg/sangoma_mgd.trunk.smg15.woo14.tgz --- __chan_woomera 1.4 Released__ __Features__ Added the woomera panic option to gracefully stop all calls.~pp~CLI> woomera panic 10~/pp~ This command will completely gracefully stop all calls and it will disable woomera. After this point one can gracefully unload woomera module.~pp~ CLI> unload chan_woomera.so~/pp~ __Changes__ None. __ Fixes__ None. __Availability__ ftp.sangoma.com/linux/smg/sangoma_mgd.trunk.smg15.woo14.tgz --- __ss7boost 0.2.48 Released__ __Features__ User configurable MTP3 SIO priority and network indicator fields for ISUP messages. These values are managed on a per trunk group basis. Visit the ((ss7boost.conf)) page in the [[TRUNK_GROUPS] section for details on how to modify an existing ss7boost configuration. __Changes__ Call setup id diagnostics are disabled. __Fixes__ None. __Availability__ ftp.sangoma.com/linux/smg/ss7boost -=2006-11-07 SMG 2006-11-07 Released=- * WANPIPE Release: beta13-p1-2.3.4 * Woomera version v1.3a : SMG Version v1.3d * Xyganda Technology, Inc. ss7boost Revision 0.2.45.csupid_diag * xmtp2km Rev. 0.2.41 * use with ss7box Rev 0.3.55 and higher * fixes /smg/re-sync.sh script # Use ((SMG Installation)) procedure. __Use the archive option if you are upgrading.__The download command is~pp~wget -c ftp://ftp.sangoma.com/linux/smg/smginstall-2006-11-07.tgz~/pp~ # Modify the [[CDR] section in your /etc/((ss7boost.conf)). Add the "Automatic CDR Logging at Startup" variable and select the desired value. #Modify MTU value in all voice carrying wanpipe configurations. **Applies only to A10X Shark version Sangoma WAN interface cards. **Read the ((TDM API Interrupt Rate Control)) procedure. #Restart ss7box (see ((ss7box User Manual))) #Restart SMG (see ((SMG User Manual))) #Restart cdr_logger ((User Manual RCDREL)) #Check revisions and verify SMG inbound and outbound calls -=2006-11-1 Maintenance Releases for sangoma_md and ss7boost =- * sangoma_mgd (Rev 1.xxxx) **fixes problem on some instances of call handling thread failing to launch * ss7boost (Rev 0.2.45.csupid_diag) **fixes glibc double free on ISUP timer 5 expiry Installation: #Ensure that SMG Release 2006-10-25a is installed #stop ss7boost and sangoma_mgd #cd /usr/local/ss7box #download ss7boost update~pp~wget -c ftp://ftp.sangoma.com/linux/smg/ss7boost_0.2.45.csupid_diag~/pp~ #mv ss7boost ss7boost.old #mv ss7boost_0.2.45.csupid_diag ss7boost #chmod 744 ss7boost #verify ss7boost revision~pp~[mike01@lt as]$ ./ss7boost --ver Xyganda Technology, Inc. ss7boost Revision 0.2.45.csupid_diag~/pp~ #cd /usr/src/Sangoma/wanpipe/ssmg #mv sangoma_mgd.trunk sangoma_mgd.trunk.old #download the sangoma_mgd update file~pp~wget -c ftp://ftp.sangoma.com/linux/smg/sangoma_mgd.trunk.1.3d.tgz~/pp~ #untar the sangoma_mgd update file #cd sangoma_mgd.trunk #edit re-sync.sh and verify the ss7boost and ss7box macros #edit /etc/sangoma_mgd.conf; ensure that debug_level = 1 is set #verify SS7 links are up #start Asterisk and SMG with "re-sync.sh all" -=2006-10-27 SMG 2006-10-25a Released=- * sangoma_mgd and chan_woomera ** Bug fix concerning management of call setup id resource. ** Asterisk CLI command __woomera panic__ stops calls in chan_woomera and prevents further use. This command is useful for stop/upgrade/starting SMG while Asterisk continues to run. * ss7boost 0.2.43.40diag ** Configurable auto start of CDR Logger ** Bug fix concerning management of call setup id resource. * Sangoma driver **TDM API improvements - variable interrupt rate **Setup script has new SMG related options that simplify installation # Use ((SMG Installation)) procedure. __Use the archive option if you are upgrading.__The download command is~pp~wget -c ftp://ftp.sangoma.com/linux/smg/smginstall-2006-10-25a.tgz~/pp~ # Modify the [[CDR] section in your /etc/((ss7boost.conf)). Add the "Automatic CDR Logging at Startup" variable and select the desired value.~pp~[CDR] # Automatic CDR Logging at Startup (y/n) y # Local (app server) # address port 127.0.0.92 55001 # Remote (CDR Collector) # address port 127.0.0.93 55001~/pp~ #Modify MTU value in all voice carrying wanpipe configurations. **Applies only to A10X Shark version Sangoma WAN interface cards. **Read the ((TDM API Interrupt Rate Control)) procedure. #Restart ss7box (see ((ss7box User Manual))) #Restart SMG (see ((SMG User Manual))) #Restart cdr_logger ((User Manual RCDREL)) #Check revisions and verify SMG inbound and outbound calls **sangoma_mgd and chan_woomera~pp~ss7box-lhr*CLI> woomera version Woomera version v1.3a : SMG Version v1.3b~/pp~ **ss7boost~pp~ss7box-lhr ss7box # ./ss7boost --ver Xyganda Technology, Inc. ss7boost Revision 0.2.43.40.csupid_diag~/pp~ -=2006-09-25 ss7boost ITU 0.2.43.33 Released=- *prtisup command sends output to /usr/local/ss7box instead of console *CDR Logger output has a CLI on/off control *bug fixed; fatal exception occurred on reuse of outbound call setup resource; resource in_use indicator was not cleared after a circuit reset -=2006-09-07 Remote CDR Event Logging Ready For Field Trial=- This RCDREL tool is easy to describe. The concept is simple. Create an event message and send it to a logging program. The details of the implementation have been more difficult to handle. The number of test cases has been fairly large too. The ISUP/Woomera unit tester has yet again proven its value by letting us create complicated signaling patterns that were captured with the RCDREL. One of the most difficult things was to make sure the content was useful. After the system became functional initially, we found that content was confusing and wrong in some cases. We had to go through each call case again and ensure that the event log told the correct history of the call. A valuable technical advance that came from this effort was the development of the "dual seizure" injector in the ISUP/Woomera unit tester. We are able to inject dual seizures in a controlled, step-by-step fashion, to both the CIC controller and CIC non-controller so that we can analyse the procedural response of ss7boost and the reports generated to the RCDREL. The RCDREL is undergoing long duration high capacity testing now that unit testing is winding down. We have a initial field test site identified and will be starting tests there next week. We see the RCDREL as a key tool for the next phase of SMG development where support for clustering will be developed. With clustering, many SMG boxes and many E1/T1 facilities will operate as a single switching entity. RCDREL will give developers and operators accurate and detailed reports on the high volumes of calls that will be handled by the large systems. -=2006-08-09 Lots to Report=- The ss7box blog has moved to the wiki because the [http://ss7box.blogspot.com/|ss7box blogger.com website] is not universally reachable or otherwise problematic. The ss7box Wiki is growing. A lot of new information is being added every week. You can count on this trend continuing. The need for system documention is growing and the wiki tool makes it easy to deliver. It's a good way to clear out our heads to make room for new thoughts. Sangoma Signal Media Gateway (SMG) has completed a 10 day high capacity test successfully. The SMG platform under test has a single CPU and 5-E1 ports configured. The 5-E1s were configured into a single trunk group. The call load kept voice channel utilization at close to 100% with short duration calls. This is a key accomplishment that assures an increasing presence of the SMG product a place in the world's communication network. We are busy thinking up new and more challenging stress tests to prepare SMG for the assuming more load and capturing more opportunities. ss7boost now has a Command Line Interface capability. There are three new commands documented in the ((ss7boost User Manual)): #verbose on/off: turns verbose logging on and off while ss7boost is running #testcall: sets a trigger for an outbound call to use a specific span/chan for a call that meets the trigger criteria #prtisup on/off: turns ISUP decode printing on and off while ss7boost is running There is a new feature in ss7boost called the ((ss7boost Overview|Structured Trunk Group Value)) that allows the Asterisk dialplan to control the Calling Party Address header fields in the outbound IAM. The need to let the Asterisk operator control the Nature of Address Indicator (NADI) is especially keen. We have been improving the automatic installation of SMG. After many hours of experimentation on a wide variety of systems all with different operating environments we can report significant progress in this area. While SMG may never be as simple to install as a consumer game on a PC, the ((SMG Installation)) tool greatly simplfies the process and reduces operator errors. We are in the process of converting handling of signaling anomolies from fatal exception to circuit reset. This is a natural step on the path to product maturity. The fatal exception method has been exceptionally useful in the past to eliminate problems within ss7boost. We are now encountering situations in the field that are beyond our control, so the usefullness of the fatal exception is waning. The development of the CDR event logger is under test. This system sends small packets of information to another system that converts the entry to a comma-separated-variable formated string, and writes that string to a flat file. The flat files rotated periodically. The time stamps are based on the gettimeofday system function so that the time granularity is very small. By off-loading the CDR event logging to a separate system, the call-processing in SMG is not degraded while maintaining a high level of reporting detail. The event reporting system will scale up to large systems without impacting the performance of the call-processing systems. We will be designing new features for controlled isolation of SMG nodes. This is part of our larger effort to support clusters of media gateways that share a single point code. A good deal of the controlled isolation feature support will be within ((ss7box M3UA)). Other portions will reside in ss7boost and will be activated when upstream resources like Asterisk or sangoma_mgd are unavailable. We will be expanding support for reception of SUSpend/RESume ISUP signals. We will implement typical T6 handling as well as optional conversion of SUSpend to RELease. ss7mon has been getting better lately. It is running in two new places in North Carolina. It now handles probing 24 T1 channels (using 2 T1 ports) or 31 E1 channels (using 2 E1 ports). The next technology advancement for ss7mon is to port in the kernel module MTP2 so that ss7mon is not susceptible to the mood swings of the Linux scheduler process. This means that users will be able to run a wide spectrum of user space programs on the ss7mon platform without negatively impacting the performance of ss7mon. |
Login |