Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Requires NSG 4.1.2 or greater, found at ftp://ftp.sangoma.com/nsg/4.1/Patches/4.1.2/

Info

IMPORTANT: These steps are in addition to the steps outlined on http://wiki.sangoma.com/NSG-Configuration

  1. When configuring an SS7 Link:

    1. Set MTP2 "Link Type" to ETSI (default ITU92)

    2. Set MTP3 "Switch Type" to ETSI v3 (default ITU00)

    3. **note** SLC numbering starts at 1, not 0. (ie you have two links to the same APC, you will need to assign them an SLC of 1 and 2 respectively (default 0 and 1))

  2. When configuring the SS7 Linkset:

    1. Ensure that "Minimum Active Signalling Links" is equal to the number of signalling links connecting to the same APC

  3. When setting the SS7 Channel Configuration for each span:

    1. Click on "Show Advanced Options"

    2. Set ITX/TXA Auto Reply to Enable (default Disable)

    3. Ensure CPG on Progress to Disable (default Disable)

    4. Set CPG on Progress Media to Disable (default Enable)

...

      <action application="export" data="acm_bi_iup=0" />

Asterisk Configuration

At this point all configuration changes on NSG have been made, and we need to modify our Asterisk dialplan to notify NSG when to natively bridge two channels to enable the redirection of calls.  This is needed to enable "redirection" and "portability" functionality.

...

This will ensure that NSG properly forwards all messages on a call that has been redirected back out to the PSTN.

Info

**

...

Note** This is not the full configuration.  You will need to create your dialplan to trigger "redirected" numbers which also modifies the Redirection X-Headers, and also set conditions for "ported" numbers which does not add those headers.  These lines are there only to enable the bridging of SS7 messages from one "side" of a redirected call to another.  For more information on the available SIP X-Headers, please visit http://wiki.sangoma.com/NSG-advanced-parameters-new