WELCOME [ Log In · Register ]        SITE [ Search · Page Index · Recent Changes ]    RSS

Wanpipe Solutions

Announcements

Sangoma Hardware
HW Installation Manuals
Tutorials

Wanpipe Drivers Download Linux | Windows

Product Spotlight (New)
    D100 Transcoding
    B800 Analog FXS/FXO
    Tapping 
    BRI: B700 / A500

Wanpipe for Asterisk
    Install
    Configure
    Operation
    Debugging
    Tutorials
    Appendix
    Trixbox 
    AsteriskNOW 
    OSLEC *NEW*
    Faxing
    FAQ

Wanpipe for FreeSwitch
    Install
    Configure
    Operation
    FreeTDM
    FAQ
    Appendix

Netborder VoIP Gateway
    Linux
    Windows
    Release Notes
    FAQ 
    Config Options 
    Routing Rules
     Guide  *NEW*
     Examples *NEW*

Netborder Call Analyzer
    Release Notes 
    FAQ *NEW*
    Asterisk Integration  
    Vicidial Integration *NEW* 
    Avaya Integration *NEW*

SMG-SS7
   Install/Upgrade
   Asterisk-SS7 Install
   FreeSwitch-SS7 Install
   Configure
   Operation
   Debugging
   FAQ

Mobile SS7

Wanpipe TDM API
    LibSangoma
    Install/Config
    FreeTDM

Wanpipe MTP2 API 

Wanpipe for Wan/API
   Install
   Configure
   RPMs
   Operation
   AFT Data API
   MPAPI-X25 API
   ADSL - S518
   ADSL2+ - S519
   Multi-Link PPP
   Appendix
   FAQ


Wanpipe for Yate
    Install
    Configure-Linux

Wanpipe for Callweaver
    Install
    Configure

Sangoma Aft-Prod

Wanpipe Case Studies

Troubleshooting

Tech Support

Glossary

 Wanpipe for Windows

Installation

 Operation

Google
sangoma wiki
sangoma.com

SMG-SS7 Demo Binaries

 

The SMG-SS7 Demo Binaries allow you to try SMG-SS7 in your labs without having to purchase a license. 
NOTE:  THERE IS LIMITED SUPPORT AVAILABLE WHEN USING THE DEMO BINARIES

 

The following wiki will guide you through installing SMG-SS7, configuring SMG-SS7, finally using SMG-SS7.  This walk through will guide you to setup 2 computers back-to-back both running SMG-SS7 and Sangoma A102/A104/A108 cards.

 

architecture-v2.jpg

  1. Installing Linux and Asterisk
  2. Downloading SMG-SS7
  3. Downloading the SMG-SS7 Demo Binaries
  4. Creating the Configuration Files
  5. Installing SMG-SS7 Stage 1
  6. Installing SMG-SS7 Stage 2
  7. Starting and debugging Layer 1 (Wanpipe)  and Layer 2/3 (ss7boxd)
  8. Starting and debugging Layer 4 (Sangoma_Isupd)  and SMG
  9. Starting and debugging Asterisk

-

Installing Linux and Asterisk

We recommend that you use the latest version of the CentOS distro with SMG-SS7 (and Asterisk).  CentOS is a distro built on stability but it still has decent support of newer computer hardware.  At the time of this writing the latest version of CentOS is 5.4.

NOTE: SMG-SS7 supports only 32-bit kernels.  We also recommend NOT to use PAE kernels.

 

SMG-SS7 works with any "stable" version of Asterisk.  You can find the latest version of Asterisk here:  http://www.asterisk.org/downloads

We recommend that you keep the Asterisk source files at /usr/src/ and create a symbolic link to the sources called /usr/src/asterisk.  Don't forget to run "make samples" to create a basic set of configuration files for Asterisk.

-

Downloading SMG-SS7

 

SMG-SS7 has a type version as well as a package version.  The type version indicates the major and minor revision of ss7boxd and sangoma_isupd.  i.e. 2.1, 2.2, 2.3, etc  The main method of versioning in SMG-SS7 is the major release version then the rev from the SVN. ie. smgss7-itu-2.5.124.tgz

Repeat Steps 1-3 on System 1 and System 2

  1. Download the following version of the SMG-SS7 package to /usr/src/
    Latest ---->  2.6 release:  ftp://ftp.sangoma.com/linux/smg/2.6/
  2. Un-archive the tar-ball
    # tar xfz smgss7-itu-<version>.tgz
  3. Change directory to the newly created directory
    # cd smgss7-itu-<version>
  4. All ss7box demo binaries are already located in
         smgss7-itu-<version> directory

Downloading the SMG-SS7 Demo Binaries

 

  1. All ss7box demo binaries are already part of the smgss7 release

    ss7boxd-m3ua-itu-demo-spc0  -  demo binary for self point code 0
    ss7boxd-m3ua-itu-demo-spc1  -  demo binary for self point code 1
    ss7boxd-m3ua-itu-demo-spc2  -  demo binary for self point code 2
    ss7boxd-m3ua-itu-demo-spc3  -  demo binary for self point code 3
    ---
  2. On System 1 copy the ss7boxd demo binary over top of the existing ss7boxd binary
    # cp ss7boxd-m3ua-itu-demo-spc0 ss7boxd
    ---
  3. On System 2 copy the ss7boxd demo binary over top of the existing ss7boxd binary
    # cp ss7boxd-m3ua-itu-demo-spc1 ss7boxd

-

Creating the Configuration Files

The configuration files for SMG-SS7 are created using a 2-step process.  First, you fill in important information into an easy to read Google Docs Spreadsheet.  The spreadsheet is then exported as a CSV file to the target machine where it is the input to a script that creates the final configuration files used by the various components of SMG-SS7.

For this walk-through the spreadsheet has already been filled out for the target configuration...but you need to update the PCI SLOT and PCI BUS value to match location of your A10X card

NOTE: YOU WILL NEED A GOOGLE DOCS ACCOUNT TO SAVE YOUR CONFIGURATION FOR FUTURE USE BUT NOT VIEW AND USE ONE TIME

  1. The Google Docs Spreadsheet for System 1 can be found here:
    2.6 release - smgss7 cfg file - smgcfg-template-v08
  2. Create a Personal copy of the spreadsheet
    Click File, Create A Copy, and name it accordingly.
  3. Update the PCI Slot and PCI Bus value using information from "lspci"
    • Run the lspci command to find your A10X card
      # lspci -n | grep 1923
      04:00.0 0280: 1923:0040
    • The PCI BUS value is the value in the first column (convert this value to decimal from HEX and fill it in the google doc)
      04 -> hex to decimal = 4
    • THe PCI SLOT value is the value in the second column (convert this value to decimal from HEX and fill it in the google doc)
      00 -> hex to decimal = 0
    • Set the Self Point Code to 0
                 SPC -> 0
           autcode -> 000000000000000000000000
       
  4. Export the spreadsheet as a CSV file and copy the file to /usr/src/smginstall-2009-10-07-ITU directory
    • Click "File"->"Export"->"CSV Sheet Only", this will open a new browser window showing the CSV version of the spreadsheet
    • Start a new SSH connection to the SMG-SS7 server
    • Change directory to your smginstall directory
    • Start a new file called config-ss7.csv using "vi"
    • Copy and paste the text from the browser window to the config-ss7.csv file
    • Save and exit the file
  5. Parse the CSV file using smgcfg06.py script to create the final configuration files.
    # ./smgcfg08.py -f config-ss7.csv

 

  1. The Google Docs Spreadsheet for System 2 can be found here:
    http://spreadsheets.google.com/ccc?key=0AnjUnrfHBSc0dFJEc0s3SmtpNE1yWkNUVjEwV1daV2c&hl=en
  2. Create a Personal copy of the spreadsheet
    Click File, Create A Copy, and name it accordingly.
  3. Update the PCI Slot and PCI Bus value using information from "lspci"
    • Run the lspci command to find your A10X card
      # lspci -n | grep 1923
      04:00.0 0280: 1923:0040
    • The PCI BUS value is the value in the first column (convert this value to decimal from HEX and fill it in the google doc)
      04 -> hex to decimal = 4
    • THe PCI SLOT value is the value in the second column (convert this value to decimal from HEX and fill it in the google doc)
      00 -> hex to decimal = 0
    • Set the Self Point Code to 1
                 SPC -> 1
           autcode -> 000000000000000000000000
       
  4. Export the spreadsheet as a CSV file and copy the file to /usr/src/smgss7-itu-<version> directory
    • Click "File"->"Export"->"CSV Sheet Only", this will open a new browser window showing the CSV version of the spreadsheet
    • Start a new SSH connection to the SMG-SS7 server
    • Change directory to your smginstall directory
    • Start a new file called config-ss7.csv using "vi"
    • Copy and paste the text from the browser window to the config-ss7.csv file
    • Save and exit the file
  5. Parse the CSV file using smgcfg06.py script to create the final configuration files.
    # ./smgcfg08.py -f config-ss7.csv

-

Installing SMG-SS7 Stage 1

Stage 1 installs the Sangoma driver, creates various folders, and copies the configuration files from the install directory to their finally location. Perform this on System 1 and System 2

  1. Start the installation
    # ./smginstall install
  2. The installer will try to stop Asterisk, existing SMG-SS7, and any existing Wanpipes and ask the user to confirm success
  3. The installer will then install the Sangoma driver.  The first step to this is to confirm that you have all the correct compile tools, stop the install if you are missing any
  4. Choose install option #4 when asked otherwise choose Y or the default option for any questions asked by the driver
  5. Do not install the start up scripts, this should be done manually once proper operation as been confirmed
  6. Install the sample extensions.conf contexts
  7. Once the install is finished you will be returned to the Linux command prompt

 -

 Installing SMG-SS7 Stage 2

Stage 2 checks your system logger and setups the SMG-SS7 log files, compiles and installs SMG and Chan_woomera.  Perform this on System 1 and System 2

  1. In Stage 1 the installer created /smg and copied the SMG and Chan_woomera sources file there.  Change directory to /smg
  2. Start the installer passing in the arguments for SS7 and the location of the Asterisk source files
    # ./install -ss7 -pbxdir <asterisk source location>

-

Starting and debugging Layer 1 (Wanpipe)  and Layer 2/3 (ss7boxd)

SS7boxd is the software daemon that handles the signaling links.  At start-up it parse the configuration file /etc/ss7box/ss7box.conf, loads the XMTP2 kernel module, starts any ports that have signaling links and finally configures XMTP2 to use the ports.

ss7boxd is started by running it using "/usr/local/ss7box/ss7boxd".

The output of a manual start looks like:

[root@konrad-ss7-1 ~]# /usr/local/ss7box/ss7boxd
Xygnada Technology, Inc. ss7box daemon, Version: 2.5.1-4
Protcol: ITU        Application: M3UA
  PID TTY          TIME CMD
[root@localhost ss7box]#
Shutting down wanpipe1 interface: w1g2
Shutting down wanpipe1 interface: w1g16
Shutting down device: wanpipe1

Devices Still Running:
 wanpipe2


Shutting down wanpipe2 interface: w2g1
Shutting down wanpipe2 interface: w2g16
Shutting down device: wanpipe2
No devices running, Unloading Modules


Starting WAN Router...
Loading WAN drivers: wanpipe done.
Starting up device: wanpipe1
--> Waiting for ec device /dev/wanec....
--> Loading ec image OCT6116-256S.ima...
Configuring interfaces: w1g2 w1g16
done.


Starting up device: wanpipe2
Configuring interfaces: w2g1 w2g16
done.

Hit any key to return to the linux command prompt.

To confirm that ss7boxd is connected start from the bottom of the stack:

  1. MTP1 -> status of the T1/E1 lines
    • check "wanrouter status" to confirm that all loaded Wanpipes are "connected"..."connecting"/"disconnected" means there are line alarms active
    • check "wanpipemon -i wXg1 -c Ta", where X is the port/Wanpipe number.  Check that the signal strength is good as well as the status of any line alarms (framer and LIU)
  2. MTP2 -> status of XMTP2
    • XMTP2 reports periodically into the system logs when there is a problem.  Run "tail -f /var/log/messages" and look for logging from XMTP2
    • check "wanpipemon -i wXgY -mtp2_all -rx -c trh", where X is the port/Wanpipe number and Y is the time slot that carries the MTP2 link.  Confirm that you are see data incoming and that the incoming data is FISU...LSSUs mean that MTP2 link is not connected
  3. MTP3 -> status of ss7boxd
    • ss7boxd reports it's status into the system logs every 20 seconds for each MTP2 configured:
      Jan 21 10:38:24 konrad-ss7-1 ss7boxd[2818]: R:link util:ls 0:link 0:msu oc 32:tot oc 160480:util 0
    • "ls" = Link set
    • "link" = Link
    • "msu oc" = number of MSUs sent/received in the last second
    • "tot oc" = number of LSSU/FISU/MSU sent/received in the last second
    • "util" = status of layer 1 for this link
    • if "util 0" then ss7boxd sees layer 1 as connected, "util -1" means ss7boxd sees layer 1 as down
    • if "msu oc" > 0 then MTP2 is connected as MSUs are only transmitted or received when layer 2 is up

-

Starting and debugging Layer 4 (Sangoma_Isupd)  and SMG

In SMG-SS7 version 2.3 and earlier the ISUP daemon is called ss7boost.  Since then, the name of the ISUP daemon has been changed to sangoma_isupd.  This is a name change only...the functionality of the daemon has not changed.  The ISUP daemon controls the Voice CICs and controls all calls on the SS7 side. 

When the ISUP daemon starts it will attempt to reset all the CICs...this can take several minutes depending on the number of CICs to reset

The ISUP daemon is started along with SMG using "smg_ctrl start"

Sangoma_isupd logs on info to the system logs so you can monitor by running "tail -f /var/log/messages".  When it is running properly you will see no messages from it.

You can check the state of the CICs by running "/usr/local/ss7box/cr.sh all"

-

Starting and debugging Asterisk

To start the Asterisk daemon run "asterisk"

To connect to the Asterisk CLI run "asterisk -r"

To determine if Chan_woomera has loaded correctly run "woomera default version".  This command will return the verions of Chan_woomera that is running as well as the version of SMG that is running (the version is obtained by communicating with the Woomera Server in SMG so if there is a version number Chan_woomera is communicating with the Woomera server)

-

Latest ---->  2.6 release:  ftp://ftp.sangoma.com/linux/smg/2.6/