TDM: SS7

 

NetBorder SS7 VoIP Media Gateway can be configured to be used as a SS7 to VoIP media gateway as well as a media transcoding server. Please click on one of the links below in order to learn how to configure NSG:

• Overview
• Configuration Introduction
• TDM SS7 Configuration Page
• Port Identification
• Physical T1/E1 Configuration
• Link Configuration
• Linkset Configuration
• Route Configuration
• ISUP Interface Configuration
• Channel Map Configuration
• Port Completion and Other Options 

 To access TDM: SS7 endpoint configuration section

1. Select Netborder SS7 from side Menu 
2. Select Configuration -> TDM 

---

Configuration Introduction

SS7 is a signalling protocol, it is used to carry call control information such as call start, call progress, call hangup etc.  The SS7 call control information is used to control arbitrary number of voice channels that are carried using T1/E1 spans.

In a typical SS7 setup the telco will provide you with SS7 information that will be used to map T1/E1 physical spans and channels into SS7 call control information.  

The NSG TDM SS7 configuration page has been designed as bottom up SS7 configuration approach.

1. Identify T1/E1 spans on your system
   -- 
2. For each T1/E1 span on your system:
   - Determine which T1/E1 spans will carry SS7 Link channels
   - T1/E1 Span can either carry an SS7 Link in one of its channels or All T1/E1 channels
     can be used to carry voice. 
   -- 
3. Configure T1/E1 physical configuration parameters
   -- 
4. Identify if T1/E1 span carries SS7 link or is Voice Only
   -- 
5. If T1/E1 span has an SS7 link associate with it:
   - Create a new SS7 Link
   - Next step is to bind the new SS7 Link to an SS7 Linkset.
   - If an SS7 Link set does not exist, Create a new SS7 Link Set
   - Then bind the SS7 Link to an existing or new SS7 Link Set
   
   - Next step is to bind the SS7 Linkset into an SS7 Route.
   - If an SS7 Route does not exist, Create a new SS7 Route
   - Then bind the SS7 Linkset to an existing or new SS7 Route
   
   - Next step is to bind the SS7 Route into an SS7 ISUP Interface
   - If an SS7 ISUP Interface does not exist, Create a new SS7 ISUP Interface
   - Then bind the SS7 Route to an existing or new SS7 ISUP Interface
   
   
6. The Last step is to assign CIC values to each physical T1/E1 timeslot in the span.
   Whether the Span carries only voice or it contains the SS7 Link, each timeslot must be associated with a SS7 CIC value. This way when an incoming SS7 Call Start message arrives with an arbitrary CIC value.  The NSG system can open the appropriate physical voice channel associated with the CIC value. 
   
   
7. Once all T1/E1 spans are configured you need to Generate the configuration files.
   Note that this step does not start the NSG gateway.  It just writes the appropriate configuration files.
   
   
8. Proceed to the Control Panel to start the NSG SS7 to VoIP Gateway.

 

 TDM SS7 Configuration Page

To access TDM: SS7 endpoint configuration section

1. Select Netborder SS7 from side Menu 
2. Select Configuration -> TDM 

NSG initial TDM SS7 Configuration page:

The TDM Configuration page will display to the user every T1/E1 card detected by NSG.

Each card is logically separated into ports, which initially displays the firmware version and the Echo Cancellation security chip ID. If the echo cancellation security chip ID is 0, then the card installed does not have echo cancellation. If there is a alert image next to the firmware version, that means the firmware on the system is out of date, and must be updated in order to have the most up to date and efficient firmware running.

 

Port Identification

The first step is to physically identify the T1/E1 Span that you are working with.
Note that for all Sangoma TDM T1/E1 cards Port 1 is closest to the PCI slot. 

The identify button is used so that the port you are trying to configure is identified on the physical card. When you click on the button, you are then redirected to a new page which gives you instructions on how to identify the physical port. See images below:

At this point you should look at the back of your server and visually identify the physical port that is blinking. Once you identify the port you can click Stop Identify button to disable the port identification feature.

Physical T1/E1 Configuration

The next step is to configure the T1/E1 Span with physical T1/E1 configuration parameters.  
These parameters should be provided to you by your Telco.

This is the area that a user would enter the hardware level T1/E1 configuration. 
The Advanced options should only be used if you know what you are doing. 

At the top of the page, you have the option to choose whether this port will be configured for T1 or E1. Once chosen, you will be presented with options specific to the line type you have chosen.

There are also advanced options that can be made accessible by clicking on the "Show Advanced Options" link. Once clicked, the user will be presented with options as depicted below:

For more information on what each option does, please see insert link here

 

 

Link Configuration

The next step is determine if the T1/E1 span you are configuring will contain an SS7 Link.
If the Span does not contain the SS7 Link, its known as Voice only span.  

The question presented below will determine if the Span is carrying SS7 Link or is Voice Only.

If the user chooses to configure the port as a voice link, they will proceed directly to enter the channel map and the CiC mapping for that port. If the user chooses a signalling link, they will be prompted to create the SS7 Link.

The information required for the SS7 Link configuration must be provided by the Telco. It is important to note that the signalling channel and the SLC MUST be filled out in order to proceed to the next step. Also, if the SS7 links all belong to the same SS7 Linkset, then the SLC values MUST be unique. For more information on what each option does, please see INSERT LINK HERE.

If you are configuring a voice link, please click HERE to proceed to the Channel Map section.

 

Linkset Configuration
 

Linkset configuration on Netborder SS7 VoIP Media Gateway is a profile based configuration. It is setup so that multiple SS7 Signalling links can use the same SS7 Linkset Profile. The term used when attaching links to linksets in NSG is BIND. You always have to bind a link to a linkset in order to proceed.

If no SS7 linkset profile has been created, the user is directed to the SS7 linkset profile creation page.

The linkset creation page asks for the following information from the user:

• Adjacent Point Code
• Minimum active signalling links that will be used with this linkset. Mainly used for redundancy.

See the screenshot below for more details:

Once the user has filled out the profile options, and there are no errors, they will be taken to the next step of the configuration. Also note that if this is the first link and linkset, the link will be automatically bound to the linkset.

When a linkset profile has been created on the system, and the user returns to the SS7 linkset configuration, they will be presented with the list below. It contains all the SS7 linkset profiles that have been created. The user has an option to bind a link to a different linkset, edit the linkset, create a linkset, or remove the linkset if no links are bound to it.

***NOTE: A linkset CAN ONLY BE deleted when there are no signalling links using it***

 

Route Configuration

Like the linkset configuration profiles, the SS7 route configuration is also configured as profiles. It is setup so that multiple SS7 linkset profiles can be used with 1 SS7 route.

If there are no SS7 Routes configured on the system, the user is prompted to create a route profile.

The SS7 route requires 3 fields to be filled out by the user:

• Destination Point Code
• Whether there is an STP switch along the SS7 route
• Which linksets get attached to this route

See the screenshot below for more details:

A linkset MUST be attached to a route in order to proceed.

Once the route profile is filled out and there are no errors, the user will be taken to the next step of the configuration.

When a route profile already exists on the system, and the user returns to the route configuration, they will be presented with the list below which is similar to the linkset configuration.

The user has the ability to add a new route, edit an existing route, or to delete a route when it is not in use.

Unlike linkset profiles, the user does not need to bind or attach linksets from here. If a new linkset needs to be attached to a route, the user must edit the route, then add the new linkset to that route. The user will only need to edit a route if a new linkset is created on the system. If no new linksets are created, the user will proceed directly to the channel map and CiC map configuration.

***NOTE: A ROUTE CAN ONLY BE DELETED FROM THE SYSTEM IF THERE ARE NO ISUP INTERFACES USING THAT ROUTE***

 

ISUP Interface Configuration

Like the linkset configuration and route configuration profiles, the ISUP Interface configuration is also configured as profiles. It is setup so that 1 SS7 route can be attached to 1 ISUP Interface.

If there are no SS7 ISUP Interfaces configured on the system, the user is prompted to create a ISUP profile.

The SS7 ISUP Interface requires 3 fields to be filled out by the user:

• Self Point Code of the system
• SSF or NI value for the ISUP Interface
• Which Route the ISUP Interface will use

See the screenshot below for more details:

A route MUST be attached to an ISUP Interface in order to proceed.

Once the ISUP Interface profile is filled out and there are no errors, the user will be taken to the next step of the configuration.

When a ISUP Interface profile already exists on the system, and the user returns to the ISUP Interface configuration, they will be presented with the list below which is similar to the linkset configuration.

The user has the ability to add a new ISUP Interface, edit an existing ISUP Interface, or to delete an ISUP Interface when it is not in use.

Unlike linkset profiles, the user does not need to bind or attach linksets from here. If a new linkset needs to be attached to a route, the user must edit the route, then add the new linkset to that route. The user will only need to edit a route if a new linkset is created on the system. If no new linksets are created, the user will proceed directly to the channel map and CiC map configuration.

***NOTE: AN ISUP INTERFACE CAN ONLY BE DELETED FROM THE SYSTEM A PORTS CHANNEL CONFIGURATION DOESN'T SPECIFY TO USE THAT ISUP INTERFACE***

 

Channel Map Configuration

The SS7 Channel Map and the CiC mapping is done within the channel map configuration section. This section asks for the following information from the user:

• ISUP Interface that is being used with this port
• Starting CiC base for the port
• Control type which will be used in the case of call collisions
• Channel Map
• Span group number

See the screenshot below for more details:

The channel map and CiC values are automatically extrapolated by prior information entered, however, the channel map does not take into account for any gaps and always assumes there is a CiC assigned to each channel on the line. Any modifications to both the CiC value and the channel map should be done here.

For information on how to create a channel map, please see INSERT LINK HERE.

The following advanced options are also available:

• Minimum incoming digits for overlap dialing
• Calling NADI value
• Called NADI Value
• Optional backwards indicators - In-band information

See the screenshot below for more details:

Once all the information has been entered for the channel map section and there are no errors, the user is returned to the TDM Configuration screen.

 

Port Completion and Other Options 

If the configuration was successful and without conflicts, the user will be presented with a similar layout for the port they were working on like below:

Note that there is now a check-mark next to the "Clear" button which is only there when a port is completed

Some other options available to the user if required:

• Generate Configuration
• Clear Configuration
• Reset Configuration
• Restore Configuration

In order to generate the configuration of completed ports, the user must click the generate configuration button found at the bottom of the TDM Configuration page. If the gateway is running, the user will not be able to generate new configuration until the gateway has been fully stopped.

Within the header of each port, there exists a "Clear" button which clears out that particular ports configuration. A user should only be clearing a port when they need to reconfigure the whole port or when that port is no longer going to be used in the SS7 Configuration.

The "Reset Config" button works like the "Clear" button, but clears all ports of their configurations and allows the user to start fresh. If there is already configuration generated, then the user can restore the old configuration using the "Restore Config" button just in case the "Reset Config" button was pressed in error.