Documentos de Académico
Documentos de Profesional
Documentos de Cultura
December, 2006
This document contains information proprietary to Gilat Satellite Networks Ltd. and may not be
reproduced in whole or in part without the express written consent of Gilat Satellite Networks Ltd. The
disclosure by Gilat Satellite Networks Ltd. of information contained herein does not constitute any
license or authorization to use or disclose the information, ideas or concepts presented. The contents of
this document are subject to change without prior notice.
SS7 Signaling over Satellite
Contents
1. Scope..............................................................................................................................1
1.1 Requirements ..........................................................................................................1
1.2 Limitations ...............................................................................................................1
2. Introduction....................................................................................................................3
3. Configuration .................................................................................................................6
3.1 VMUX-110 Common Configuration ..........................................................................6
3.2 Remote Side VMUX-110 Configuration ....................................................................7
3.2.1 Physical Connections ....................................................................................7
3.2.2 Parameter Configuration ...............................................................................8
3.3 Hub Side VMUX-110 Configuration........................................................................10
3.3.1 Parameter Configuration .............................................................................11
3.3.2 SS7 Keep-alive Suppression Rate Configuration.........................................13
3.3.3 Packetizing Interval Configuration ...............................................................14
3.4 Remote Side Gateway VSAT Configuration ...........................................................15
3.4.1 Physical Connections ..................................................................................15
3.4.2 Drop and Insert Parameter Configuration ....................................................18
3.4.3 Gateway/VSAT Parameter Configuration ....................................................20
3.4.4 Validating and Committing the Gateway/VSAT ............................................22
Figures
Tables
1. Scope
Additional Configuration
1.1 Requirements
A VMUX-110 device is required at both ends of the satellite link. For other
adaptors configuration may vary
The SS7 link requires approximately 21k over the satellite link
1.2 Limitations
This feature cannot work with GA access scheme configured on the Inbound
band
If other IP applications use the same network, QoS must be provided for
VMUX-110 signaling.
If signaling and voice are carried over a single E1 port Drop and Insert must be
used. For more information on Drop and Insert see Section: 3.4.2 Drop and Insert
Parameter Configuration.
CAUTION
Drop and insert of data is not supported on Gateways for timeslot 16. As
a result no voice or signaling data may be carried over timeslot 16.
2. Introduction
SS7 signaling in The SkyEdge network was traditionally not sent to the hub over the
satellite link but was sent outside the network to a SP and then routed to the hub.
Some customers either could not, or did not want to route the signaling out of the
SkyEdge network.
The SS7 Signaling over Satellite feature was developed to permit the transport of a
remote SS7 signaling point (SP) to another SS7 SP located at the hub over the
satellite link.
An SS7 device (in this document VMUX-110) performs the following functions:
Carrying IP traffic over the satellite link while providing QoS for other
applications as needed
Providing bandwidth efficiency by removing FISU and LSSU messages (as much
as possible)
NOTE
The SS7 link uses 64KBps plus the size of the headers used for
encapsulation. Removal of FISU and LSSU MSUs reduces the Bandwidth
size considerably compared to the original 64K. The reason for this is that
the 64K link is designed to support signaling for many E1s (formally 128,
with a standard safety factor of 64), while the Satellite Network typically
handles signaling traffic related to a single voice E1.
Typically, SS7 Signaling over Satellite carries the voice over the SkyEdge network
using the SkyEdge telephony application and an SIU. The signaling is carried from a
remote SP and is either connected directly to the hub-side SIU, or to the SIU through
an STP (that has access from the hub location). Directly connecting the links to an
SIU limits capacity to 22 remote sites. Using an STP removes this limit, but not
always is STP connectivity available or cost effective.
SS7 signaling link with no voice - This requires any SkyEdge terminal (IP, PRO
or Gateway). This situation rarely happens since, in most cases, voice is carried
over the SkyEdge network. However, there are cases where this configuration is
applicable (if SMS offload is needed). In this case no SIU is needed.
SS7 signaling with voice carried over the same satellite terminal - In this
case, a Gateway is required to carry the voice as well as the encapsulated SS7
signaling. In this case, SIU is usually present at the hub.
SS7 signaling with more than a single voice E1 - This configuration requires
additional IDUs. This configuration is currently not supported.
Figure 2 shows how SS7 signaling travels over the satellite link:
3. Configuration
This section details the configuration of at least one pair of adaptors, one adaptor
sitting at the hub site and the other at the remote site. The configuration consists of
procedures for both physical connections as well as configuring parameters on the
console and the NMS.
Time slot configuration for a pair of VMUX-110 devices is the same for both
devices. For procedures specific to each device see sections 3.2 Remote Side
VMUX-110 Configuration and 3.3 Hub Side VMUX-110 Configuration.
NOTE
The data typed into the screen is highlighted in gray.
Configuration
1. Quick Setup >
2. System >
3. Physical Ports >
4. Bundles >
5. Applications >
>2
Please select item <1 to 5>
@ - DB Update; # - DB Undo
ESC-prev.menu; !-main menu; &-exit 2 Mngr/s
2. Type 4 to enter the Bundles submenu.
Configuration>Bundles
1. Display []
2. Configure >
3. Time Slots >
>3
3. Type 3 to enter the Time Slots submenu.
Configuration>Bundles>Time Slots
1. Display []
2. Configure >
>2
Configuration>Bundles>Time Slots>Configure
1. Update from Time Slot[1 - 31] ... (1)
2. To Time Slot[1 - 31] ... (1)
3. Type > (Voice)
4. Bundle[1 - 12] ... (1)
5. Destination Port ID[1 - 4] ... (1)
6. Destination Time Slot ID[1 - 31] ... (1)
7. Update Time Slots
>
5. Set the timeslot that SS7 signaling is carried on, by typing 1, 2 and 6 (Update
from Time Slot (1), To Time Slot (2) and Destination Time Slot (6)).
1. Connect one end of a straight LAN cable to the Ethernet port marked NET and
the other to the VSAT Gateway LAN port.
2. Connect one end of the E1 cable to the E1 port marked CHANNEL, and the other
end of to the RJ45 E1 jack on the Gateway VSAT.
3. For direct terminal connection connect one end of a serial cable to the DB-9 port
and the other end to the terminal application.
This section details parameter needed to configure the remote VMUX-110 to work
with SS7 signaling over Satellite. For information on the use and configuration of
VMUX-110, consult the VMUX-110 user manual.
1. Connect to the VMUX-110 console using a serial cable and terminal emulation
application.
Result: A console window opens with the User Name and Password prompts
displayed.
USER NAME:
PASSWORD:
ESC - clear; & - exit 2 Mngr/s
----------------------------------------------------------------------
3. At the login prompt enter your user name and password.
NOTE
The first time you connect to the console use the default User name (su)
and password (1234). To change passwords consult the VMUX-110
Users Guide.
Main Menu
1. Inventory []
2. Configuration >
3. Monitoring >
4. Diagnostics >
5. File Utilities >
>2
4. Type 2 to enter the Configuration menu.
Configuration
1. Quick Setup >
2. System >
3. Physical Ports >
4. Bundles >
5. Applications >
>1
Please select item <1 to 5>
@ - DB Update; # - DB Undo
ESC-prev.menu; !-main menu; &-exit 2 Mngr/s
5. Type 1 to enter the Quick Setup submenu.
Configuration>Quick Setup
1. Host IP Address ... (172.24.4.110)
2. Host Subnet Mask ... (255.255.0.0)
3. Default Gateway ... (172.24.4.1)
4. Destination IP ... (0.0.0.0)
5. Destination Bundle [1 - 30] ... (1)
6. Signaling Mode > (CCS)
7. Save
>
6. Type 1 to enter the VMUX-110 IP address in the Host IP Address field.
7. Type 2 to enter the VMUX-110 IP subnet mask in the Subnet Mask field.
8. Type 3 to enter the VMUX-110 Default Gateway address using the VSATs IP
address, in the Default Gateway field.
Configuration>Quick Setup
NOTE: Changes will be applied only after DB Update !
1. Host IP Address ... (172.24.4.110)
2. Host Subnet Mask ... (255.255.0.0)
3. Default Gateway ... (172.24.4.1)
4. Destination IP ... (0.0.0.0)
5. Destination Bundle[1 - 30] ... (1)free antivirus
6. Signaling Mode > (CCS)
7. Save
>7
Result: a note is displayed stating that the changes do not take effect until
the database is updated.
1. Connect one end of the RJ45 LAN cable to the port on the back of the VMUX-
110 marked Net, and the other end to any port from 1-22 on the Satellite Extender
Switch.
2. Connect one end of a RJ45 E1 cross cable to the port on the back of the VMUX-
110 marked E1 Channel, and the other end to a free SIU E1 port or to an STP.
3. For direct terminal connection connect one end of a serial cable to the DB-9 port
and the other end to a terminal application.
NOTE
A LAN port is already used to connect the SIU to the Media Gateway-SIU
Switch, and the other is used to connect the SIU to another SIU.
If the E1 port of the VMUX-110 is connected to an STP use a regular
RJ45 E1 cable.
1. Connect to the VMUX-110 console using a serial cable and terminal emulation
application.
Result: A term window opens with the User Name and Password displayed.
USER NAME:
PASSWORD:
ESC - clear; & - exit 2 Mngr/s
----------------------------------------------------------------------
3. At the login prompts enter your user name and password.
NOTE
If this is your first time opening the console use the default user name
(su) and password (1234)
Main Menu
1. Inventory []
2. Configuration >
3. Monitoring >
4. Diagnostics >
5. File Utilities >
>2
4. Type 2 to enter the Configuration menu.
Configuration
1. Quick Setup >
2. System >
3. Physical Ports >
4. Bundles >
5. Applications >
>1
Please select item <1 to 5>
@ - DB Update; # - DB Undo
ESC-prev.menu; !-main menu; &-exit 2 Mngr/s
5. Type 1 to enter the Quick Setup submenu.
Configuration>Quick Setup
1. Host IP Address ... (172.24.4.110)
2. Host Subnet Mask ... (255.255.0.0)
3. Default Gateway ... (172.24.4.1)
4. Destination IP ... (0.0.0.0)
5. Destination Bundle [1 - 30] ... (1)
6. Signaling Mode > (CCS)
7. Save
>
6. Type 1 to enter the VMUX-110 IP address in the Host IP Address field.
NOTE
The IP addresses use the following range 172.24.4.110 -131.
7. Type 2 to enter the VMUX-110 IP Subnet Mask in the subnet mask field
according to the value configured in the DPS.
NOTE
The IP subnet mask and the Default Gateway should be the address
configured in the DPS or the Hub Edge Router.
8. Type 3 to enter the VMUX-110 Default Gateway address (using the IP address
of the DPS), in the Default Gateway field.
9. Type 4 to enter the Destination IP address (The address of the Remote VMUX-
110 located on the Gateway VSAT side).
Configuration
1. Quick Setup >
2. System >
3. Physical Ports >
4. Bundles >
5. Applications >
>2
Please select item <1 to 5>
@ - DB Update; # - DB Undo
ESC-prev.menu; !-main menu; &-exit 2 Mngr/s
1. Type 2 to enter the System submenu.
Configuration>System
1. Management >
2. Date & Time >
3. Factory Default >
4. Alarm Operations >
5. Signaling >
6. Main Link > (Ethernet)
7. Router (Disable)
8. Reset Unit
>5
2. Type 5 to enter the Signaling submenu.
Configuration>System>Signaling
1. Signaling Profiles >
2. SS7 Keep-Alive Suppression Rate > (90%)
>2
1. From the main terminal screen type 2 to enter the Configuration menu.
Configuration
1. Quick Setup >
2. System >
3. Physical Ports >
4. Bundles >
5. Applications >
>4
Please select item <1 to 5>
@ - DB Update; # - DB Undo
ESC-prev.menu; !-main menu; &-exit 2 Mngr/s
2. Type 4 to Enter the Bundles submenu.
Configuration>Bundles
1. Display []
2. Configure >
3. Time Slots >
>2
3. Type 2 to enter the Configure submenu.
Configuration>Bundles>Configure
1. Add Bundle[1 - 12] ... (0)
2. Delete Bundle[1 - 12] ... (0)
3. Edit Bundle >
>3
Configuration>Bundles>Configure>Edit Bundle
1. Bundle Number[1 - 12] ... (1)
2. Connect > (Yes)
3. Function > (TDMoIP)
4. Routing Parameters >
5. Max Bytes In Multiplexed Frame[100 - 1461] ... (500)
6. Packetizing Interval (msec)[10 - 254] ... (30)
7. Packet Redundancy[1 - 4] ... (1)
8. Connectivity Parameters >
9. Voice Parameters >
10. Transparent Jitter Size (N x 10mSec)[2 - 10] ... (2)
11. Bundle Name ... ()
>
5. Type 6 and configure a Packetizing Interval of 125 msec if the super slot is
120 msec and 185 msec if the super slot is 180 msec.
NOTE
Make sure the remote and hub units have the same value configured.
1. Connect one end of the E1 cable to the Gateway’s/VSAT’s E1 port(s) and the
other end to the VMUX-110 Channel port.
The Gateway VSAT E1 port connects to the VMUX-110 using either one RJ45 jack
or two BNC type jacks. For more information on VMUX-110 cable connections see
Section 3.2.1 Physical Connections.
1. Voice and signaling are carried over 2 separate E1s: One for voice and the other
for signaling only. In this case, the voice E1 is connected directly to the Gateway
E1 port. Signaling is connected to the VMUX-110 E1 port (and the VMUX110 is
connected by LAN cable to the Gateway's Ethernet port). The cabling connection
scheme depends on the E1 connector available at the switch side:
RJ45: Connect voice cable directly to GW E1, connect signaling cable directly
into VMUX-110. If required, have a crossed E1 cable ready.
BNC: Connect a Balun to the signaling E1 and connect the RJ45 side to the
VMUX-110. The voice E1 may be connected directly to the Gateway E1 BNC
connectors.
2. Voice and signaling are carried over the same E1. In this case, drop and insert is
required and a special cabling configuration applies, according to the connectors
used at the switch:
RJ45
BNC
If both the Gateway and VMUX-110 are connected to the switch with a single E1
interface and signaling is transmitted using a timeslot other than 16, it is necessary to
instruct the Gateway to loop back the applicable timeslot.
6. Double click the mode cell and select Not Assigned from the drop-down list.
7. Validate and commit the Gateway. For more information see Section 3.4.4 Result:
The Validate Confirmation dialog box is displayed.
4. From the ADA Operation Scheme drop-down list, select Legacy DA, and click
Save.
5. Click OK.
2. Enter the number of fixed PDA slots based on the table above.
NOTE
The required Band Width for the signaling link is about 21 Kbps. A typical
G723 network requires 4 voice timeslots to carry signaling and the
minimal internal SE signaling requirements. A dual rate network (where
DA is configured to have double the Voice DA rate) requires only 2
timeslots. For such a case a full E1 channel is supported (30 voice
timeslots which is 32 timeslots minus 2 DA slots).
Once Fixed PDA Slots are configured validate the configuration according to the
following section.
2. Click OK.
3. Click Save, to save and commit the changes in the Gateway Template
Configuration window.
4. Click OK.
5. Click Commit .
6. Click Yes.
NOTE
A reset command is issued to all Gateways linked to the specified Data
Template. When several Gateway configuration changes must be made,
first make all changes and only then commit and reset the Gateway. This
reduces the times the VSAT must be reset.
4. Additional Configuration
4.1 VMUX-110
Local terminal
Telnet
Web browser
NOTE
For more information on managing a VMUX-110, and polling telemetries
from VMUX-110 devices see the VMUX-110 User Manual.
New application software releases are distributed as *.img files. These files are
downloaded to the Vmux-110 using the XMODEM protocol or client TFTP
application. This is done from the File System menu of the boot software (before
booting the device). Alternatively, you can download a new software release using
TFTP protocol, while the Vmux-110 management software is already running.
The VMUX-110 software is stored in flash memory in, the boot and file system. The
boot sector holds a boot program that calls up the rest of the program from the file
system.
The file system can hold two compressed copies of the Vmux-110 application
software. One copy of the software is referred to as active partition
(usually partition 1), the other – as backup partition (usually partition 0). The active
partition is decompressed and loaded into the Vmux-110 RAM upon power-up. The
backup file is used whenever the active file is missing or corrupted.
NOTE
To be able to upload TFTP server software needs to be installed on a PC
and configured to upload the software file.
Result: the console opens with the User Name and Password prompts
displayed.
File Utilities
1. Show Partition Information >
2. Set Active Partition > (Partition 1)
3. TFTP Transfer >
>3
4. Type 3 to enter the TFTP Transfer submenu.
5. Type 1, (TFTP File Name), and enter the file name to be downloaded. (for
example: config.dat)
6. Type 2, (TFTP File), and enter the IP address of the computer where the file to be
downloaded is located.
1. Follow the steps above substituting the step below for step 7 above.
3. Click View.
7. Validate and Save changes. For more information see Section 3.4.4 Validating
and Committing the Gateway/VSAT.
CAUTION
Browsing the remote VMUX-110 is not recommended because of
bandwidth limitations.
3. Press Enter.
NOTE
It is possible to configure prioritization for the source and destination IP
addresses but is this is not recommended.
1. Open a web browser and type the IP address of Net Enforcer application in the
Address Bar.
4. Click New.
6. In the Contents of: field, name the host. For example: VMUX-110.
9. Click Add.
Result: The Host Catalog Editor closes and the Policy Editor window is
displayed.
14. In the Content of field name the application. For example: SS7 Signaling.
16. Go to Ports→Destination.
21. In the Policy Editor click the plus (+) sign to open Platinum-750.
Result: A New Virtual Channel is inserted and the cursor is placed in the
first cell.
27. In the Dir column make sure a double headed arrow is displayed.
34. In the Contents of: field, name the application. For example: vmuxqos.
35. Select Each Direction defined Separately from the Virtual Channel based
QoS drop-down list.
36. In the Inbound tab, select 10, (the highest priority) from the Priority per
Virtual Channel drop-down list.
37. In the Outbound tab, select 10. (the highest priority) Priority per Virtual
Channel drop-down list.
40. In the Policy Editor (the main window) select the row for the virtual channel
created above (named SS7).
41. Copy the row using either the Right Click menu or the Ctrl C keyboard shortcut.
42. Scroll down to the Gold section and put the cursor in the first cell of a row.
43. Paste the virtual channel using either the Edit menu or the Ctrl V keyboard
shortcut.
44. Paste the virtual channel under the Silver and Fall Back Pipe sections as well.