24-GSM Support PDF

GSM Support
NetPerformer System Reference
COPYRIGHTS AND DISCLAIMERS

Published Date: March 2011
Document # 1614
This publication contains information proprietary and confidential to Memotec Inc. Any reproduction,
disclosure or unauthorized use of this publication is expressly prohibited except as Memotec Inc. may
otherwise authorize in writing.
Memotec Inc. reserves the right to make changes without notice in product or component design as warranted
by evolution in user needs or progress in engineering or manufacturing technology. Changes which affect the
operation of the unit will be documented in the next revision of the manual.
We have made every effort to ensure the accuracy of the information presented in our documentation.
However, Memotec assumes no responsibility for the accuracy of the information published. Product
documentation is subject to change without notice. Changes, if any, will be incorporated in new editions of
these documents. Memotec may make improvements or changes in the products or programs described within
the documents at any time without notice. Mention of products or services not manufactured or sold by
Memotec is for informational purposes only and constitutes neither an endorsement nor a recommendation for
such products or services.
Memotec Inc. is a wholly owned subsidiary of Comtech EF Data Corp., and its parent company Comtech
Telecommunications Corp (NASDAQ: CMTL).
AccessView, CXTool, CX-U Series, CX-UA Series, AbisXpress, NetPerformer, AccessGate, ACTView, SDM8400, and the SDM-9000 series of products are either registered trademarks or trademarks of Memotec Inc.in
Canada, the United States of America, and in other countries.
Windows is a registered trademark of Microsoft Corporation in the United States and other countries.
Any other trademarks are the property of their respective companies.
Copyright 2011 Memotec Inc.
Memotec Inc.
7755 Henri Bourassa Blvd. West

Montreal, Quebec
Canada H4S 1P7
Tel.: (514) 738-4781
FAX: (514) 738-4436
www.memotec.com
Contents
Chapter 1: NetPerformer GSM Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1. 1
About the GSM Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1. 2
Network Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1. 3
1. 4
1. 5
1. 6
1. 7
1.2.1
GSM-only Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.2.2
Mixed GSM and Non-GSM Network . . . . . . . . . . . . . . . . . . . . . 1-3
NetPerformer Solution for GSM Networks. . . . . . . . . . . . . . . . . . . . . . . . . 1-4

1.3.1
GSM Interfaces Supported. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
1.3.2
GSM Traffic Types Supported . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Using NetPerformer on the GSM A/E Interface . . . . . . . . . . . . . . . . . . . . . 1-7

1.4.1
Advantages with NetPerformer . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
1.4.2
Characteristics of GSM A and E . . . . . . . . . . . . . . . . . . . . . . . . 1-8
1.4.3
NetPerformer Optimization of GSM A and E . . . . . . . . . . . . . . . 1-8
Using NetPerformer on the GSM Abis Interface . . . . . . . . . . . . . . . . . . . 1-10

1.5.1
Advantages with NetPerformer . . . . . . . . . . . . . . . . . . . . . . . . 1-10
1.5.2
Network Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
1.5.3
Characteristics of GSM Abis . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
1.5.4
NetPerformer Optimization of GSM Abis . . . . . . . . . . . . . . . . . 1-13
Using NetPerformer on the GSM Ater Interface . . . . . . . . . . . . . . . . . . . 1-16

1.6.1
Characteristics of GSM Ater. . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
1.6.2
NetPerformer Optimization of GSM Ater . . . . . . . . . . . . . . . . . 1-17
NetPerformer Platform for GSM Support. . . . . . . . . . . . . . . . . . . . . . . . . 1-18

1.7.1
Hardware and Base Software Requirements . . . . . . . . . . . . . . 1-18
1.7.2
GSM Abis/Ater Licensed Software Option . . . . . . . . . . . . . . . . 1-19
1.7.3
Satellite Network Application . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
1.7.4
GSM 2/2.5G and 3G Convergence . . . . . . . . . . . . . . . . . . . . . 1-20
1.7.5
TDMoIP Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
1.7.6
Configurable Software Features . . . . . . . . . . . . . . . . . . . . . . . 1-23
Chapter 2: Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

2. 1
Before You Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

2.1.1
2. 2
Is the GSM Abis/Ater Option Already Installed? . . . . . . . . . . . . 2-2
Configuration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

2.2.1
Configuring the NetPerformer for GSM Abis . . . . . . . . . . . . . . . 2-5
2.2.2
Configuring the NetPerformer for GSM Ater . . . . . . . . . . . . . . . 2-6
Memotec Inc.
2.2.3
2. 3
Configuring the NetPerformer for TDMoIP . . . . . . . . . . . . . . . . 2-7
Configuring the Digital Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

2.3.1
Configuring a T1 Physical Port (LINK). . . . . . . . . . . . . . . . . . . . 2-8
2.3.2
Configuring an E1 Physical Port (LINK). . . . . . . . . . . . . . . . . . 2-10
2. 4
Configuring the GSM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
2. 5
Configuring an SS7 Signaling Channel . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
2. 6
Configuring the GSM PVCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
2. 7
Configuring the GSM Traffic Channels (CHANNEL) . . . . . . . . . . . . . . . . 2-16

2.7.1
2. 8
Configuring the Timeslot Subchannels Manually (TSSUB) . . . 2-18
Extended Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Chapter 3: Advanced GSM Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3. 1
3. 2
3. 3
3. 4
Enhanced High-precision Clocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

3.1.1
Activating the Enhanced Clock . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.1.2
Activating the GPS Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
About the Prioritization of GSM Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

3.2.1
Uses and Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
3.2.2
How It Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Satellite Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

3.3.1
E1 Standard Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
3.3.2
E1 Bypass Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
3.3.3
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
PVC Link Redundancy in a TDMoIP Application. . . . . . . . . . . . . . . . . . . 3-11

3.4.1
Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Chapter 4: Monitoring and Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4. 1
About Monitoring and Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4. 2
Display GSM Channels (DCH) Command . . . . . . . . . . . . . . . . . . . . . . . . 4-4
4. 3
Display GSM TS Channel Allocation (DTSCH) Command . . . . . . . . . . . . 4-6
4. 4
Display DSP Allocation (DDSP) Command. . . . . . . . . . . . . . . . . . . . . . . . 4-9
4. 5
Display Jitter Level (DJL) Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
4. 6
Display GPS Status (DGPS) Command . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Memotec Inc.
4.6.1
Viewing the GPS Receiver and PLL Status. . . . . . . . . . . . . . . 4-12
4.6.2
GPS Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
4.6.3
PLL Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
4.6.4
Viewing the GPS Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
4.6.5
4. 7
Viewing the GPS Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Display Counters (DC) Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17

4.7.1
GSM Traffic Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
4.7.2
Transmit and Receive Traffic Counters . . . . . . . . . . . . . . . . . . 4-18
4. 8
Display Errors (DE) Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
4. 9
Display States (DS) Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
4. 10
Monitoring Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

4.10.1
Monitoring Activation of the Autodetection Function . . . . . . . . 4-21
4.10.2
Monitoring 3G Support Deactivation . . . . . . . . . . . . . . . . . . . . 4-24
4. 11
PCM Raw Data Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
4. 12
Error Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
Chapter 5: Concepts and Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

5. 1
About GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
5. 2
Mobile Cellular Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
5. 3
5. 4
5. 5
5. 6
5.2.1
Transmitter Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
5.2.2
Types of Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
5.2.3
Cells per Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
GSM Network Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

5.3.1
Mobile Station (MS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
5.3.2
Base Station Subsystem (BSS) . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
5.3.3
Network and Switching Subsystem (NSS) . . . . . . . . . . . . . . . . . 5-6
5.3.4
Operation and Support Subsystem (OSS) . . . . . . . . . . . . . . . . . 5-7
GSM Network Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

5.4.1
Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
5.4.2
Radio Resources (RR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
5.4.3
Mobility Management (MM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
5.4.4
Communication Management (CM) . . . . . . . . . . . . . . . . . . . . . . 5-8
5.4.5
Operation and Maintenance (O&M) . . . . . . . . . . . . . . . . . . . . . . 5-9
GSM Radio Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

5.5.1
Access Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
5.5.2
GSM Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
List of Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Chapter 6: SE/GSM Configuration Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

6. 1
Jitter buffer (ms). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Memotec Inc.
6. 2
Mode used when SIG detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
6. 3
Mode used when TCH detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
6. 4
Continuous AUTO detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
6. 5
Activate 3G support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
6. 6
Call management timeout (s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Chapter 7: SE/SLOT/#/CHANNEL Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . 7-1

7. 1
Channel Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
7. 2
Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
7. 3
Timeslot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
7. 4
Location on the GSM network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
7. 5
Vendor of the GSM units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
7. 6
TS subchannel mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
7. 7
Subchannel speed mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
7. 8
Idle code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
7. 9
Remote unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
7. 10
Remote port number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Chapter 8: SE/PVC/#/GSM Configuration Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

8. 1
GSM traffic type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
8. 2
Frame over IP, source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
8. 3
Frame over IP, destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
8. 4
Frame over IP, port number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
8. 5
Frame over IP, DSCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
8. 6
Use a forced route. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
8. 7
Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
8. 8
GSM maximum calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
8. 9
GSM VAD Deactivate threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
8. 10
GSM VAD Activate threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
8. 11
GSM VAD A (bps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
8. 12
GSM VAD B (bps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
8. 13
GSM VAD K (coefficient in percentage) . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
8. 14
GSM group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Memotec Inc.
8. 15
GSM maximum frame size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
8. 16
GSM pack delay (ms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
8. 17
PVCR PVC that manages this PVC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
Memotec Inc.
Memotec Inc.
1
NetPerformer GSM Solution
Memotec Inc.
1-1
GSM Solution
1.1
About the GSM Solution

The NetPerformer solution optimizes 2/2.5G GSM Abis/Ater traffic, and bundles and
transports GSM 3G UMTS traffic. It decodes GSM signaling information and voice
timeslots according to ETSI standards.
GSM 2/2.5G traffic is inherently bandwidth inefficient as it is based on a circuit-switched,
TDM-based system. It requires a dedicated network of leased lines, fiber, microwave links
and satellite links, which represent high recurrent costs. The system infrastructure is often
insufficient or nonexistent, and services are often deployed in remote areas as an
alternative to rural telephony. Satellite communication can be used in these cases, but is
very costly. These problems are resolved with the addition of the NetPerformer to the
GSM network.
For all NetPerformer products:
Support of GSM A and E is offered with the base software
Support of GSM Abis and Ater is offered as a licensed software option. When
this license is installed, the NetPerformer supports GSM Abis/Ater applications
over E1/T1, serial (WAN) and IP (LAN) connections.
NOTE:
1-2
For the SDM-9210, the GSM Abis/Ater licensed software option may be bundled with the base product software on certain OEM models.
Memotec Inc.
1.2
1.2.1
Network Compatibility
GSM-only Network
For GSM applications all NetPerformer units must be running the same phase of
GSM.
Backward compatibility is possible between V10.4.0 (R04 or later) and V10.3.5
GSM Abis/Ater support in V10.4.X is the only version that can run on the SDM9620
If an SDM-9620 is installed in the network, all participating NetPerformer
units must be upgraded to the same version of V10.4.X that is running on the
SDM-9620. Refer to the NetPerformer Version V10.4.X Release Bulletin
for upgrade procedures.
1.2.2
Mixed GSM and Non-GSM Network

A NetPerformer unit installed with the GSM licensed software option can communicate
with a unit that does not have the GSM license installed. This requires the following on all
participating units:
Installed with V10.4.0 R01 or later
Configured for PowerCell voice transport method (PVCR)
A PVCR connection must be configured between the unit running GSM and the
unit without GSM.
The non-GSM unit must be configured with the PowerCell version Global
parameter set to 2.
Memotec Inc.
1-3
GSM Solution
1.3
NetPerformer Solution for GSM Networks

The NetPerformer can be installed at various points of the GSM network to optimize
traffic and reduce the bandwidth load:
Reduces operational costs by lowering bandwidth requirements on all GSM network interfaces
Converts TDM data to Packet data
Compresses signaling and O&M data, and suppresses redundant data. On the
TCH stream:
- Redundant data is removed
- Silence and idles (flags) are not transmitted across the WAN
Provides load balancing, which allows for multiple links to be set up between
the same two units using serial or digital ports
Supports integration of packetized voice (besides GSM), LAN routing, ATM
traffic and legacy data
NOTE:
For WAN traffic, all participating NetPerformer units must be installed

with the GSM Abis/Ater Option, as the PVCR protocol used with GSM is
not compatible with the PVCR protocol used on the NetPerformer base
product.
Spoofs the SS7 protocol and optimizes the signaling channel by transmitting only
significant data end-to-end
Provides congestion control, prioritized flow control, packetization and call
blocking to maximize the bandwidth
Low end-to-end delay (maximum 20 to 30 ms)
Autodetection of voice/data or signaling traffic on timeslot subchannels
Supports IP multiplexing with GSM traffic
Can be used in a point-to-multipoint application
Optional high-precision clocking for synchronization and timing control of system clocks. See Enhanced High-precision Clocking on page 3-2 for details.
1-4
Memotec Inc.
The GSM network with NetPerformer is illustrated in Figure 1-1.
Figure 1-1: GSM Network with NetPerformer
1.3.1
GSM Interfaces Supported

A and E interfaces: PCM voice is optimized using standard available codecs
(G723, G726, G729, ACELP-CN). Available on all NetPerformer products.
Refer to Using NetPerformer on the GSM A/E Interface on page 1-7
Abis interface: Coded TRAU bandwidth is optimized using various techniques.
Available only on an SDM-9210, SDM-9220, SDM-9230, SDM-9606 or SDM9620 installed with the GSM Abis/Ater licensed software option. Refer to
Using NetPerformer on the GSM Abis Interface on page 1-10
Ater interface: Coded TRAU bandwidth is optimized, and SS7 messages are
processed with either FISU spoofing or MTP2 layer termination (configurable).
Available only on an SDM-9210, SDM-9220, SDM-9230, SDM-9606 or SDM9620 installed with the GSM Abis/Ater licensed software option. Refer to
Using NetPerformer on the GSM Ater Interface on page 1-16.
1.3.2
GSM Traffic Types Supported

Signaling: 16K, 32K and 64K, both concentrated and non-concentrated
Voice/fax:
- Enhanced Full Rate (EFR) at 12.2K
- Full Rate (FR) at 13.5K
- Half Rate (HR) at 4.75K to 12.2K
- Adaptive Multi Rate Full Rate (AMR-FR) at 4.75K to 12.2K
Memotec Inc.
1-5
GSM Solution
- Adaptive Multi Rate Half Rate (AMR-HR) at 4.75K to 7.4K

GSM Data:
- GPRS
- EDGE
- Extended Data
- FR data
- HR data
- Frame Relay-based Gb
Digital cross connect: 64 Kbps non-blocking, 8 Kbps subchanneling.
For a detailed list of traffic types supported, turn to For each timeslot subchannel, the
subchannel mode or type of traffic currently being carried by that timeslot subchannel is
displayed beneath the applicable Bitn columns: on page 4-7.
NOTE:
1-6
The GSM PVC parameter GSM traffic type should be set to TCH for all of
these traffic types. Refer to Configuring the GSM PVCs on page 2-14.
Memotec Inc.
1.4
Using NetPerformer on the GSM A/E Interface

This is a hub solution available on the NetPerformer base product (no license required).
The NetPerformer units transporting GSM A traffic between the BSC and MSC, or E
traffic between the MSC and PSTN, via digital E1/T1 links. For configuration details,
refer to Configuring the NetPerformer for GSM A or E on page 2-4.
Figure 1-2: The NetPerformer with GSM A Interface: between the BSC and MSC
Figure 1-3: The NetPerformer with GSM E Interface: between the MSC and PSTN
A and E traffic uses SS7 signaling, which is configured on one or more channels
of the E1/T1 link with the SS7 or SS7MTP2 protocol.
One or more voice channels are also required, using the G.711, ACELP-CN or
other voice protocol.
1.4.1
Advantages with NetPerformer

The NetPerformer transports the GSM A or E traffic point to point, and offers the
following advantages:
Multiple A/E interfaces can be concentrated over a single WAN connection
WAN flexibility: satellite links, Frame Relay, ATM, IP backbone, leased lines,
etc.
Choice of physical interfaces: serial, digital E1/T1, Ethernet
Redundant WAN links can be installed to improve overall network resilience
Voice and data are integrated. Any bandwidth that is not used for GSM traffic can
be used to carry data (IP or others), LAN and legacy data, or analog voice
High bandwidth savings through voice compression of 64K PCM audio paths
using a highly efficient voice codec (8:1 voice compression ratio, or as high as
20:1 when used with silence suppression)
Data is also compressed, to improve the efficiency of the link.
Memotec Inc.
1-7
GSM Solution
1.4.2
Characteristics of GSM A and E

2 Mbps E1 or 1.54 Mbps T1 circuit
Up to 30 voice channels per line
SS7 signaling
Voice channels are uncompressed:
- Circuit switched, TDM-based
- Bandwidth for inactive channels (unassigned timeslots) is wasted.
1.4.3
NetPerformer Optimization of GSM A and E

The NetPerformer provides several optimization features:
Signaling and O&M data are compressed, and transported transparently
SS7 traffic is handled in one of two ways:
- FISU spoofing (Protocol parameter set to SS7). Only significant data is
transmitted end to end, and idles and redundant data are handled locally
- MTP2 layer termination (Protocol parameter set to SS7MTP2). No FISU or
LSSU frames are transported to the remote side.
Basic ISUP support is also available for SS7 traffic, used for a DCME application
only (Protocol parameter set to SS7 ISUP-A or SS7MTP2 ISUP-A).
Voice optimization to conserve bandwidth:
- Compression of 64K PCM audio paths using highly efficient voice codec
(5.3K to 8K)
- Silence suppression further reduces bandwidth requirements
- Comfort Noise generation contributes to high voice quality
Works on multiple types of WAN interfaces;
- Not limited to digital E1/T1 interfaces
- Can integrate other types of traffic with the required traffic prioritization levels.
These features result in up to 90% bandwidth reduction on GSM A or E interfaces.
For example, a single A/E interface with 30 voice calls can be optimized to less than 256
Kbps.
Bandwidth Required (in Kbps)
Voice Channels
Uncompressed
576
8K Voice
40% Silence
8K Voice
96
61
Table 1-1: Bandwidth reduction on GSM A or E interface
1-8
Memotec Inc.
Bandwidth Required (in Kbps)

Voice Channels
Uncompressed
8K Voice
40% Silence
8K Voice
16
1088
181
112
24
1600
266
163
30
2048
330
202
Table 1-1: Bandwidth reduction on GSM A or E interface
Memotec Inc.
1-9
GSM Solution
1.5
Using NetPerformer on the GSM Abis Interface

This solution connects multiple remote BTS sites to the BSC on the hub side, with the
NetPerformer units connected to the BTS and BSC via digital E1/T1 links. Available only
on an SDM-9210, SDM-9220, SDM-9230, SDM-9606 or SDM-9620 installed with the
GSM Abis/Ater licensed software option. For configuration details refer to
Configuring the NetPerformer for GSM Abis on page 2-5.
Figure 1-4: The NetPerformer with GSM Abis Interface: between the BTS and BSC
One NetPerformer unit is set up at the remote location, connected to the BTS via
the digital E1/T1 link. The Location on the GSM network must be set to BTS
ABIS (refer to Configuring the GSM Traffic Channels (CHANNEL) on
page 2-16)
The other NetPerformer is on the hub side, connected to the TRAU in front of the
BSC. On this unit the Location on the GSM network must be set to BSC ABIS.
One or more channels are configured with the GSM protocol (refer to Configuring the GSM Traffic Channels (CHANNEL) on page 2-16). These channels
are divided into timeslot subchannels (or TSSUB), which are defined to support the type of traffic detected by the NetPerformer.
For example, some are defined as traffic channels (TCHD or TCHU) for transporting voice and data, and others as control channels (SIG) for signaling and O&M
functions. Refer to GSM Channels on page 5-11 for background information
on GSM channels.
1.5.1
Advantages with NetPerformer

Packet-based Abis transmission permits variable bandwidth for TDMA, which otherwise
has a fixed-time allocation. With the addition of the NetPerformer:
Signaling data is not a constant stream, and can be easily compressed
Audio can be carried at a variable rate
Idle traffic and silence are suppressed
Traffic is allocated dynamically to all available channels.
1-10
Memotec Inc.
1.5.2
Network Connectivity
The NetPerformer is connected to the BSC and BTS through its T1 or E1 interface cards
It communicates with the network management system through IP connectivity
The WAN connection can be a leased-line, wireless or shared packet network
PVCs can also be used in a GSM-only application, using Frame Relay over IP
(FRoIP).
Redundant WAN links can be installed to improve overall network resilience
The timeslot subchannels (TSSUB) defined on the NetPerformer CHANNEL
support the individual TRXs.
For GSM Abis, the timeslot subchannels can be defined automatically through
the NetPerformer Autodetection function. To enable this function, refer to For
an Abis application, set the GSM auto detect mode to: on page 2-8.
1.5.3
Characteristics of GSM Abis

The most common interface in GSM networks
Supports multiple radio channels per E1 or T1 line
Voice channels are compressed:
- Circuit switched, TDM-based, using 16-Kbps subchannels (8 for every pair of
64K timeslots). Maximum of 16 channels for Half Rate (HR)
- Bandwidth for inactive channels is wasted
Timeslot Allocation
Each radio channel supports a maximum of 8 subchannels using 2 64-Kbps
timeslots
GSM signaling can be transported in the radio channel or a separate timeslot, at
16, 32 or 64 Kbps
The E1 interface has 32 timeslots, and the T1 interface has 24
Each TDMA channel (tranceiver timeslot, or TRX) uses 2 timeslots
All TRXs must be defined in contiguous timeslots
A single 64-Kbps timeslot can be configured, or multiple subchannels of 8, 16, or
32 Kbps
The O&M channel can also be 8, 16, 32 or 64K
Signaling and O&M scenarios vary depending on the type of switch and the network topology. Possible scenarios include:
- 32K signaling with one 32K O&M channel
Memotec Inc.
1-11
GSM Solution
- 16K signaling with several 16K O&M channels

- 16K signaling with several 64K O&M channels
- 64K signaling with one 64K O&M channel.
An example of timeslot allocation is the following:
Format of Transceiver Timeslots (TRXs)

One TRX uses two 64K timeslots
Each of the two timeslots is divided into subchannels, as follows:
- At 16K (Full Rate):
- At 8K (Half Rate):
- At 16K/8K (Dual Rate):
1-12
Memotec Inc.
A particular subchannel can carry signaling or voice/data traffic

The associated signaling channel can be assigned to a separate timeslot and operate at a different rate.
1.5.4
NetPerformer Optimization of GSM Abis

Signaling traffic and OEM data are compressed:
- Processed as voice/data traffic by the DSP, and multiplexed with voice packets during transmission
- Fully supported in discrete 64K timeslots or subchannels at 8, 16 or 32K
- Idles are removed
- Bandwidth requirements are reduced.
Audio data is optimized:
- Packetized as transparent 64K PCM
- The GSM Abis TCH stream is analyzed, removing unused and redundant bits
using DSP processing power
- Supports voice/data integration
- NetPerformer recognizes when the TCH stream is carrying voice or data and
optimizes it accordingly. Less bandwidth is required on data channel timeslots
- Silence is not transmitted
- NetPerformer can be configured to allocate a channel only when a call is
established
- Spoofing and suppression of idle voice channels (grooming) so that unused
timeslots are not transmitted
Not limited to digital E1/T1 interfaces:
- Works on multiple types of WAN interfaces, including satellite, leased lines,
Frame Relay, ATM, IP
- Can integrate other types of traffic with the required prioritization levels.
These features result in up to 50% bandwidth reduction on a GSM Abis interface,
depending on the traffic pattern (type of vocoder, Full Rate or Half Rate, percentage and
type of data traffic, silence ratio, number of idle channels). Please contact Memotec Inc. or
your NetPerformer distributor for an evaluation of the potential bandwidth savings
specific to your installation.
Memotec Inc.
1-13
GSM Solution
PowerCell Encapsulation of Abis Traffic

The NetPerformers unique PowerCell technology permits convergence of Abis traffic
with other traffic types, and tunneling of Abis through any type of WAN network.
Abis signaling and optimized cells from different TCHs are multiplexed and
encapsulated as NetPerformer PowerCell frames
The NetPerformer at the receiving end demultiplexes the PowerCell traffic and
recreates the original Abis frames for each TCH.
Figure 1-5: PowerCell Tunneling of Abis Traffic over Various WAN Networks
The NetPerformer can transport PowerCell frames over any type of WAN network
The result is a homogeneous logical network using PowerCell.
Refer also to TDMoIP Application on page 1-22.
NOTE:
When integrating with WAN traffic, all participating NetPerformer units

must be installed with the GSM Abis/Ater Option, as the PVCR protocol
used with GSM is not compatible with the PVCR protocol used on the
NetPerformer base product.
Dual Rate Traffic Channels

A dual rate traffic channel (TCHD) initially operates at 16 Kbps. A volume threshold is
defined on the GSM switch, above which the speed is reduced to 8 Kbps. If the BTS/BSC
equipment switches from 16 Kbps to 8 Kbps, the NetPerformer processes the channel
1-14
Memotec Inc.
accordingly.
A TCHD channel can carry one 16-Kbps voice call or, when the traffic volume increases,
one or two 8-Kbps voice calls. This allows the provider to carry more voice calls without
having to increase the number of subchannels (or TRXs).
NOTE:
Less bandwidth optimization is possible at 8 Kbps, since there is less GSM

overhead that can be removed. Users may experience a change in voice quality on calls placed after the volume threshold has been reached.
Example:
A system with 10 TRXs can support 80 calls at 16 Kbps. The provider decides
that when the volume of calls reaches 80%, all subsequent calls should be placed
at 8 Kbps rather than 16 Kbps.
This means that the first 64 calls will be placed using 16 Kbps, and the 65th call
using 8 Kbps. All subsequent calls are placed at 8 Kbps until the maximum
number of voice calls is reached.
Using dual rate traffic channels (TCHD) this system can support 64 calls at 16
Kbps, plus 32 calls at 8 Kbps for a total of 96 calls.
Memotec Inc.
1-15
GSM Solution
1.6
Using NetPerformer on the GSM Ater Interface

This is a hub solution with the NetPerformer units connected to the BSC and the MSC via
digital E1/T1 links. Available only on an SDM-9210, SDM-9220, SDM-9230, SDM9606 or SDM-9620 installed with the GSM A-bis/ter licensed software option. For
configuration details, refer to Configuring the NetPerformer for GSM Ater on page 2-6.
Figure 1-6: The NetPerformer with GSM Ater Interface: between the BSC and MSC
One NetPerformer unit is connected to the BSC at the remote location. The Location on the GSM network must be set to BSC ATER (refer to Configuring the
GSM Traffic Channels (CHANNEL) on page 2-16)
The other NetPerformer is the hub, connected to the TRAU in front of the MSC.
On this unit the Location on the GSM network must be set to MSC ATER
Ater traffic uses SS7 signaling, which is configured on one or more channels of
the E1/T1 link using the SS7 or SS7MTP2 protocol
One or more channels are also configured with the GSM protocol (refer to Configuring the GSM Traffic Channels (CHANNEL) on page 2-16). Unlike the
Abis application, no signaling subchannels are required on these channels, which
are all configured as traffic channels (TCHD or TCHU) for transporting voice and
data. Refer to GSM Channels on page 5-11 for background information on
GSM channels.
1.6.1
Characteristics of GSM Ater

Typically 8 Full Rate voice channels for every two 64-Kbps timeslots
SS7 signaling in 64 Kbps timeslots (similar to the A interface)
Audio channels have the same compression options as Abis (TCH compression)
The TRAU is in the MSC rather than the BSC
Voice channels are compressed
- Maximum of 120 voice channels per digital line (at 16 Kbps)
- Circuit switched, TDM based
- Uses 16-Kbps subchannels for Full Rate support (8 per two 64K timeslots) or
8-Kbps subchannels for Half Rate support (16 per two 64K timeslots)
1-16
Memotec Inc.
- Bandwidth for inactive channels is wasted

Signaling is in SS7 format:
- FISU spoofing (Protocol parameter set to SS7) reduces bandwidth by not
sending redundant information. Significant signaling data is compressed.
- MTP2 layer termination (Protocol parameter set to SS7MTP2). No FISU or
LSSU frames are transported to the remote side.
1.6.2
NetPerformer Optimization of GSM Ater

Optimization of GSM Ater traffic is similar to that of Abis traffic. Refer to NetPerformer
Optimization of GSM Abis on page 1-13.
Memotec Inc.
1-17
GSM Solution
1.7
1.7.1
NetPerformer Platform for GSM Support

Hardware and Base Software Requirements
SDM-9210, SDM-9220, SDM-9230, SDM-9606 or SDM-9620
GSM A and E is supported on all NetPerformer products
For the SDM-9220 or SDM-9230, a sufficient number of E1 or T1 interface cards
to support the GSM subchannels (or TRXs)
A sufficient number of available DSP channels to process the TRXs and support
autodetection of GSM timeslots.
Under autodetection, when signaling traffic (SIG) is recognized, it is given high
priority automatically. Refer to Autodetection of Timeslot Subchannel Traffic
Types on page 1-27.
- As a rule of thumb, calculate the same number of DSP channels as the number
of timeslots carrying GSM traffic.
NOTE:
Higher GSM capacity is achieved when the unit is equipped with a high-density DSP (HD DSP), which has more channels than the low-density DSP
(DSP-160). For details about the DSPs, consult the Hardware Installation
Guide for your NetPerformer product.
- If you dont have enough DSP capacity, you can manually configure a timeslot to carry 64K signaling. In this case, you must configure it for high priority
as well. Refer to Configuring the Timeslot Subchannels Manually (TSSUB)
on page 2-18.
- As an example, if you have a full E1 for GSM traffic, you need 31 channels of
DSP capacity to provide autodetection on the full span. If a low-density DSP
with only 30 channels is installed in the unit, you can:
Set a maximum of 30 timeslots in autodetection mode
Configure the remaining timeslot as an HDLC channel with high
priority. This channel can carry 64K signaling only, not subchannels
or TRXs, which require a DSP for processing.
Support of channelized data:

- Bit-oriented or transparent transmission
- 64K or Nx64K (G.703/704)
- GSM subchanneling Nx8K, up to 64K
All standard WAN interfaces supported: leased/switched line, digital, Frame
Relay, ATM, satellite, IP backbone
Flexible packet and TDM architecture:
1-18
Memotec Inc.
- DS0 cross connect for digital to digital

- DS0 transparent or enhanced packetization.
1.7.2
GSM Abis/Ater Licensed Software Option

The GSM Abis/Ater licensed software option permits optimization of the Abis/Ater TCHs
in TDM timeslots. Refer also to NetPerformer Optimization of GSM Abis on page 1-13
for features of this option.
NOTE:
This software license is available for the SDM-9210, SDM-9220, SDM9230, SDM-9606 or SDM-9620.
Caution: The SDM-9210, SDM-9220, SDM-9230 and SDM-9606 are limited

to a single Ethernet port when the GSM A-bis/ter licensed software option is
installed. Only the first Ethernet port (ETH1) can be configured and used. The
second Ethernet port (ETH2) is not available, as its resources are allocated to ATM
functionality to support GSM 3G. If you require the second Ethernet port, you
must turn off 3G support. Refer to Configuring the GSM Parameters on page 212.
1.7.3
Satellite Network Application

The NetPerformer can transport optimized GSM Abis traffic over various types of satellite
networks such as SCPC, SCPC DAMA, A-TDMA, D-TDMA, IP-based and DVB-RCS.
Depending on the specific satellite technology, satellite bandwidth can be allocated
dynamically when TCHs are active. With the NetPerformers bandwidth optimization,
Memotec Inc.
1-19
GSM Solution
traffic to all remote units can share the same bandwidth.
Figure 1-7: Bandwidth Optimization in the Satellite Network
The NetPerformer units at the BTS sites optimize the GSM Abis traffic and transmits it via satellite to the NetPerformer unit at the BSC central site
The central site NetPerformer unit restores the original traffic stream and sends it
transparently to the BSC.
This application reduces satellite hardware required at the central site (modem,
RF amplifier, etc.)
NOTE:
1.7.4
A satellite application normally requires constant bandwidth for optimum

results. Refer to Constant Bandwidth Support on page 1-26. For information on satellite backup scenarios, turn to Satellite Backup on page 3-9.
GSM 2/2.5G and 3G Convergence

The NetPerformer supports convergence of 2/2.5G GSM Abis and 3G traffic on the SDM9230 and SDM-9606, using UMTS/ATM.
NOTE:
1-20
GSM 3G uses UMTS, which is an ATM-based traffic type. This application

takes advantage of the ATM capabilities of the SDM-9230. When the GSM
Abis/Ater license is activated, if the unit supports ATM then GSM 3G is
Memotec Inc.
also supported. ATM support is indicated at the NetPerformer console during

system start-up.
Simultaneous support of optimized and encapsulated traffic (GSM Abis) and

encapsulated-only transparent traffic (ATM AAL2 for voice, AAL5 for data)
Both applications can be converged on the same WAN link using PowerCell
technology
3G support is available by default when the GSM license is activated.
NOTE:
When 3G support is activated, only the first Ethernet port (ETH1) can be
configured and used. The second Ethernet port (ETH2) is not available,
as its resources are allocated to ATM functionality. If you require the second Ethernet port, you must turn off 3G support. Refer to Configuring
the GSM Parameters on page 2-12.
Figure 1-8: Converging GSM Abis and GSM 3G Traffic
In this application:
The NetPerformer is connected to both a 2/2.5G BTS generating GSM Abis traffic, and a 3G BTS generating UMTS/ATM traffic
Abis is compressed and uses variable amount of bandwidth
The NetPerformer transparently transports the UMTS cells from the 3G BTS to
the satellite modulator using an ATM-Multiplex PVC
- Only the active cells are transported, limiting the bandwidth required
- AAL2 and AAL5 data cells can be compressed by the NetPerformer
Memotec Inc.
1-21
GSM Solution
The UMTS cells are bundled and transmitted over the same PowerCell link as the
Abis traffic from the 2/2.5G BTS.
1.7.5
TDMoIP Application
GSM traffic can be sent using packet over IP delivery, or TDMoIP. This application is
implemented using a proprietary encapsulation technique over a UDP/IP protocol stack.
For an overview of configuration requirements, turn to Configuring the NetPerformer for
TDMoIP on page 2-7.
A GSM PVC carries the GSM traffic, which is routed over an IP connection
A PVCR PVC manages the connection between the two NetPerformer units
NOTE:
A GSM PVC must be configured on each NetPerformer unit that is participating in the application (see Configuring the GSM PVCs on page 2-14). Configuration of a PVCR PVC is discussed in the WAN/Frame Relay module of
this document series.
Figure 1-9: NetPerformer TDMoIP Application with Enhanced Clock
This application offers the advantages traffic transport via the Internet. Since PVCs are
used to carry voice and signaling traffic, it also provides traffic shaping, through:
Cell packetization (see Packetization on page 1-25)
Control of the frame size (see Constant Bandwidth Support on page 1-26)
Idle bandwidth optimization (see Idle Bandwidth Optimization on page 1-25)
Control of the frame timeouts, by means of the Timer in ms for FR Over IP
parameter in the Global profile
Control of the information rate, by means of the Committed Information rate
PVC parameter
Control of the combined information rate of all PVCs, by means of the Global
CIR for FR Over IP parameter in the Global profile.
1-22
Memotec Inc.
The total CIR of all PVCRoIP PVCs must be less than the Global CIR for FR
over IP.
IP precedence for GSM traffic is configured on GSM PVC using the differentiated
services codepoint (DSCP). By using DSCP, the NetPerformer can tell the satellite modem
to prioritize GSM traffic. The relative priority of GSM traffic can be adjusted to suit your
application.
NOTE:
In a TDMoIP application, the E1/T1 reference clocking source cannot be

taken from the serial or Ethernet interface. An enhanced clock is required to
support GSM A-bis traffic that is transported over a serial or packet network
(see Figure -1-9). For details, refer to Enhanced High-precision Clocking
on page 3-2.
Caution: Multihomed IP routing must not be used in a TDMoIP application.
To turn it off, enter the following at the NetPerformer console command line:
EP IP MULTIHOMEDTYPE DISABLED
1.7.6
Configurable Software Features

This section discusses the following configurable features for supporting GSM traffic:
Hub versus Remote Functionality on page 1-24 (see next section)
Network Jitter on page 1-24
Prioritization on page 1-24
Flow Control on page 1-25
Packetization on page 1-25
Idle Bandwidth Optimization on page 1-25
Constant Bandwidth Support on page 1-26
Call Blocking on page 1-27
Autodetection of Timeslot Subchannel Traffic Types on page 1-27
Load Balancing on page 1-29.
Further information and configuration procedures are provided elsewhere in this
document:
To fully configure the NetPerformer for GSM traffic support, refer to the chapter
Configuration on page 2-1
To activate an enhanced clock installed in the NetPerformer unit, turn to page 2
For details on configurable parameters, refer to:
- SE/GSM Configuration Parameters on page 6-1
Memotec Inc.
1-23
GSM Solution
- SE/SLOT/#/CHANNEL Configuration Parameters on page 7-1

- SE/PVC/#/GSM Configuration Parameters on page 8-1
All extended parameters are detailed in the Extended Parameters module of
the NetPerformer System Reference.
Hub versus Remote Functionality

The NetPerformer can be connected to various components of the GSM network. Its
functionality as a hub or remote unit is determined by the value of the GSM parameter
Location on the GSM network.
GSM interface
Network
side
GSM channel
connected to
Value of Location on the

GSM network
Abis
Remote
BTS
BTS ABIS
Abis
Hub
BSC
BSC ABIS
Ater
Remote
BSC
BSC ATER
Ater
Hub
TRAU (in front of MSC) MSC ATER
Table 1-2: NetPerformer Functionality in the GSM Network
Network Jitter
The NetPerformer is able to compensate for variations in network delay so that packets
can arrive at consistent intervals, thereby avoiding choppy voice quality. When the
NetPerformer receives optimized GSM traffic at the destination site, it buffers the traffic
for a configurable amount of time before transmitting it to the BSC (or GSM switch).
You can set the GSM parameter Jitter buffer (ms) from 4 to 160 ms, in increments of 4
(default 20 ms).
This wait time allows the NetPerformer to regenerate the voice stream smoothly
If a jitter overrun occurs, the NetPerformer discards the packets in the jitter
buffer, rebuilds packets as best as it can according to the previously processed
packet, and sends these packets
If a jitter underrun occurs, the NetPerformer rebuilds packets as best as it can
according to the previously processed packet, and sends them until the underrun
condition is corrected.
Prioritization
GSM traffic (including voice and signaling) is prioritized over WAN (PVCR) traffic by
default. This can be changed using the extended GSM parameter TRAFFICPRIO.
Each GSM input channel for signaling and voice can be assigned to a priority queue in the
NetPerformer. Voice traffic and signaling traffic, which are intolerant of delay, are placed
in the highest-priority queue (HIGH PRIORITY class), for the most expeditious delivery to
1-24
Memotec Inc.
the network.
If there is congestion on a GSM PVC, the host will send a message to the NetPerformer
DSP module to start discarding samples. During this time, signaling traffic is prioritized
over voice traffic.
Other traffic types, such as data, can be buffered into classes (queues) 1 to 8 for delivery
after the higher-priority traffic packets are sent. These traffic classes are prioritized
according to their assigned weight, with levels from 1 to 16.
Details on traffic prioritization and classes are provided in the Quality of Service (QoS)
module of this document series.
Flow Control
Flow control is executed using the following prioritization (from highest to lowest
priority):
Signaling data
Voice data (FR/EFR/HR/AMR)
Call identification in progress (40-400 ms at the beginning of transmission of a
new traffic type)
Known data (EFR DATA, O&M, Nokia GPRS)
Unknown data (GPRS and EDGE from other vendors).
When congestion occurs, the data (known and unknown) is the first to be discarded. If
greater congestion occurs, voice data and call identification may also be discarded, but
only if this does not affect the synchronization of the call (time alignment, protocol
change, etc.). The signaling is never discarded.
Two extended GSM parameters can be used to manage and override the flow control
settings:
FLOWCTLACCUMULATION: To define the number of packets that will be accumulated for flow control in a congestion situation.
VOICEONLY: To always discard the data (known and unknown) even if no congestion occurs.
Packetization
In a TDMoIP application (see TDMoIP Application on page 1-22) it is possible to
reduce the amount of bandwidth used by packing the frames to reduce the IP header
overhead. The GSM pack delay (ms) parameter controls the Packetization feature on each
GSM PVC in the application. This parameter determines how many milliseconds of
frames will be packed before transmitting to the remote side.
Idle Bandwidth Optimization

The NetPerformer includes the IDLE STOP mechanism, which permits using less
bandwidth when no calls are placed between the NetPerformer units on the BSC and BTS
Memotec Inc.
1-25
GSM Solution
sides.
When no call is detected between the two units, IDLE STOP is automatically
activated after a 2-second delay
When IDLE STOP is activated, only SIG packets are sent across the link via the
GSM PVC
If no signaling is present, nothing is sent over the GSM PVC. In this case, each
NetPerformer unit rebuilds the IDLE traffic at its end of the network, and remains
in sync with the other unit concerning the jitter level.
Constant Bandwidth Support

On the NetPerformer, constant bandwidth is achieved through dynamic Voice Activation
Detection (VAD) and the suspension of the Silence Suppression mechanism in low traffic
situations. When VAD is active, the NetPerformer generates constant-length IP frames for
carrying the TRAU traffic.
Below a given number of simultaneous calls, Silence Suppression has more disadvantages
than advantages, particularly when GSM traffic is transported over a satellite connection.
Bandwidth usage is highly variable when few calls are placed between the BTS and BSC.
This is not compatible with the requirements of a satellite application.
Dynamic VAD activation/deactivation is a configurable feature on the NetPerformer GSM
PVC, using the following parameters:
GSM VAD Activate threshold. The number of calls needed to activate VAD.
When this threshold is reached, the NetPerformer deactivates Silence Suppression and activates VAD to avoid unstable bandwidth usage.
GSM VAD Deactivate threshold. The number of calls needed to deactivate VAD.
When this threshold is reached, bandwidth usage is more constant. Here, the NetPerformer reactivates Silence Suppression and deactivates VAD.
NOTE:
For dynamic VAD activation/deactivation to work, the GSM VAD Activate

threshold must be higher than the GSM VAD Deactivate threshold. When
both of these thresholds are set to zero, Silence Suppression is always
active on the GSM PVC, and bandwidth usage may vary.
When VAD is active, the NetPerformer generates IP frames (which carry the TRAU
traffic) of a constant length, based on the bandwidth used, the number of DSPs available to
handle the traffic, and the desired VAD coefficient. The VAD levels can be fine-tuned to
ensure constant bandwidth, using the GSM VAD A (bps), GSM VAD B (bps), and GSM
VAD K (coefficient in percentage) parameters. Details for these parameters are provided in
the appendix SE/PVC/#/GSM Configuration Parameters on page 8-1.
NOTE:
1-26
When VAD is active on a GSM PVC and several calls are placed at the same
Memotec Inc.
time, the required CIR is allocated immediately. If several calls hang up at the
same time, the NetPerformer DSP deallocates the bandwidth only when the
CIR returns to 2000 ms or less. This allows the NetPerformer to send the last
frames queued for these calls, and ensures a more stable CIR when many calls
are deallocated and reallocated at the same time.
Call Blocking
The Call Blocking feature permits rejecting new calls when a maximum threshold is
reached.
The GSM maximum calls parameter on the GSM PVC determines the maximum
number of calls allowed before calls start to be rejected. When set to 0, no calls
are rejected. See GSM maximum calls on page 8-5 for details.
In an IGMP/Multicast application, a timer must also expire before Call Blocking
will be activated. This timer is configured using the GSM parameter Call management timeout (s). If no START or STOP message has been received for the
duration of this timeout, calls are rejected on the basis of the GSM maximum calls
parameter. When set to 0, the timer is deactivated.
Autodetection of Timeslot Subchannel Traffic Types

The NetPerformer can be configured to detect the kind of Abis traffic sent over each
timeslot, and automatically define the subchannels required to support this traffic. The
Autodetection function is activated by configuring the digital link to operate in either
MASTER or SLAVE mode, using the LINK parameter GSM auto detect mode (refer to
Configuring the Digital Link on page 2-8). You must also configure the NetPerformer to
support GSM Abis traffic (refer to Configuring the NetPerformer for GSM Abis on
page 2-5).
MASTER: Initializes autodetection on the DSPs, and detects what channels are
required based on traffic received over the link. When the MASTER link receives
the configuration from the DSPs, it sends a configuration message to the SLAVE
link on the remote unit. The MASTER is usually the link on the BSC side, but it
can be on the BTS side if required by the application.
SLAVE: No autodetection is performed on the link. Rather, the link waits for the
configuration message sent from the MASTER. The SLAVE is usually on the
BTS side, but can be on the BSC side if required by the application.
NOTE:
A link defined in MASTER mode must face a link defined in SLAVE

mode. Likewise, a SLAVE link must face a MASTER link.
Once the Abis timeslot subchannels are configured, they retain their settings until the
Autodetection function restarts. A restart occurs when:
Memotec Inc.
1-27
GSM Solution
The unit is powered up

The link goes down (loss of SYNC on the interface)
The link is activated (enabled through the LINK configuration).
Revising, Overriding and Disabling the Automatic Settings
Revising: The NetPerformer can be configured to restart the autodetection process whenever the traffic type changes on a timeslot subchannel. The GSM parameter Continuous AUTO detection controls this feature (see Continuous AUTO
detection on page 6-3).
Overriding: You can control which type of channel will be configured when SIG
or TCH traffic is detected at the DSPs, using the GSM parameters Mode used
when SIG detected (see Mode used when SIG detected on page 6-2) and Mode
used when TCH detected (see Mode used when TCH detected on page 6-2).
Disabling:
- When GSM auto detect mode on the digital link is set to DISABLE, you can
configure the timeslot subchannels manually. This can be useful for special
applications requiring fine-tuning of the type of traffic supported on individual subchannels. For details, refer to Configuring the Timeslot Subchannels
Manually (TSSUB) on page 2-18.
- GSM auto detect mode affects only those Abis timeslots that are configured
with the GSM protocol (using the Protocol parameter in the SE/SLOT/CHANNEL submenu). If you do not want Autodetection to operate on a particular
timeslot, set it to OFF or to another Protocol value.
1-28
Memotec Inc.
Load Balancing
As of version 10.4.0, the NetPerformer supports load balancing in a GSM application.
With load balancing, you can set up multiple links between the same two units, using
PVCR ports or PVCs.
To enable load balancing:
Configure the number of PVCR links required (see Configuring a T1 Physical
Port (LINK) on page 2-8)
Set the Speed (bps) of all links going to the same destination to the same value, or
as close to this as possible
Leave the Allow load balancing port parameter at its default value: YES.
NOTE:
Load balancing must be disabled for satellite backup. Set Allow load balancing to NO in this case. Refer to Satellite Backup on page 3-9 for details.
GSM Frame Header and the Deactivation of Load Balancing
The GSM frame header used in NetPerformer V10.4.0 is now compatible with the frame
header version used in NetPerformer V10.3.5. If the earlier frame header is detected on the
remote unit, the local unit (running V10.4.0) switches to that header version. By
implication, no new GSM features in V10.4.0 will be available on the connection,
including Load Balancing.
To view the GSM frame header version in use, execute the Display GSM Information
(DGSM) command. The Frame header version is displayed as 1 for V10.3.5 or earlier, or
2 for V10.4.0 R04 or later.
Memotec Inc.
1-29
GSM Solution
1-30
Memotec Inc.
2
Configuration
Important: The GSM Abis/Ater Option includes a Software Licensing Agreement,
which can be found in the product package.

You must agree to the terms and conditions of this agreement before loading the
software.
Each NetPerformer unit in the GSM Abis/Ater application requires a separate
software license.
The GSM Abis/Ater option can be loaded on an SDM-9210, SDM-9220, SDM9230, SDM-9606 or SDM-9620 only.
Refer also to Network Compatibility on page 1-3.
Memotec Inc.
2-1
GSM Solution
2.1
Before You Configure

The GSM Abis/Ater software must be activated on the NetPerformer unit before you
can configure and use any GSM A-bis/ter features. This requires entering the GSM
Abis/Ater Software License to the License Profile.
NOTE:
A specific License Profile is valid for a single NetPerformer unit only.
To prepare for GSM Abis/Ater configuration you must first:

Install the NetPerformer unit according to the instructions given in the Hardware Installation Guide for the particular product, which is available on the
NetPerformer Documentation CD (Order No. 161-0692-001, Part No. 5200081-001).
Install and activate the GSM Abis/Ater Option software license, following the
procedure provided in the Software Licensing chapter of the Software Installation and Licensing module of this document series.
NOTE:
Install the GSM Abis/Ater Option on a remote unit before bringing up a

connection with the NetPerformer at the central site.
At any time, you can reset the unit configuration to its factory defaults: enter FS
at the command prompt. The GSM Abis/Ater Option is reset along with all
other areas of the configuration, and all previously defined values are lost.
When you execute the FS command, the NetPerformer unit clears its License
Profile and resets all parameters to their default values. You must:
- Re-enter the GSM Abis/Ater Option software license, and
- Change all parameters involved in the application back to their required values. Refer to Configuration Procedure on page 2-4.
2.1.1
Is the GSM Abis/Ater Option Already Installed?

To determine whether a NetPerformer unit is already installed with the GSM Abis/Ater
licensed software option, execute any of the following commands, which include
information on any optional software that has already been installed on the unit:
Product License Status (PLS)
Display Parameters (DP)
Display Version (DV)
Display Alarms (DA).
2-2
Memotec Inc.
Configuration
The PLS command provides a prompt to delete any software licenses currently installed,
citing their license numbers.
PLS
command:
with GSM
Abis/Ater
option
installed
SDM-9230>PLS
PRODUCT LICENSE STATUS
LICENSE> Enter a new license key (NO/YES,def:NO) ? NO
LICENSE> Delete GSM license (AAAA-BBBB-CCCCCCCC-DDDD) (NO/
YES,def:NO) ? NO
For the DP, DV and DA commands, the message GSM license (AAAA-BBBBCCCCCCCC-DDDD) enabled on this unit indicates the software license number.
DP example:
with GSM
Abis/Ater
option
installed
DV example:
with GSM
Abis/Ater
option
installed
DA example:
with GSM
Abis/Ater
option
installed
Memotec Inc.
SDM-9230>DP
DISPLAY PARAMETERS
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/HUNT/IP/IPX/MAP/
PHONE/
PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/USER/VLAN,
def:REDUNDANCY) ? ALL
Wait for <ENTER> after each screen (NO/YES,def:YES) ? NO
SDM-9230 vX.X.X Memotec Inc. (c) 2007
Signaling Engine vX.X.X Memotec Inc. (c) 2007
DSP QCXXX.BIZ code version: X.X.X
Console connected on port CSL
GSM license (AAAA-BBBB-CCCCCCCC-DDDD) enabled on this unit
GLOBAL> Unit name................................SDM-9230
...
SDM-9230>DV
DISPLAY VERSION
Voice transport method: PowerCell
SDM-9230>DA
DISPLAY ALARMS
Voice transport method: PowerCell
Time> THU
2007/03/08 11:16:16
Alarm>
PVC 2 UP (BSC)
THU
2007/03/08 9:23:42
Alarm>
PVC 1 UP (BSC)
THU
2007/03/08 9:23:39
...
2-3
GSM Solution
2.2
Configuration Procedure
The NetPerformer is configured to support GSM traffic using the GSM, PVC, SLOT/LINK
(or SPAN/LINK, on products with built-in E1/T1 interfaces) and SLOT/CHANNEL (or
SPAN/CHANNEL) submenus of the SETUP (SE) console command.
In addition, there are parameters governing:
Activation of an optional enhanced high-precision clock and, for an SDM-9210
installed with a G.823 PDH compliant clocking module, activation of the GPS
port. Refer to Enhanced High-precision Clocking on page 3-2 for further
information and activation procedures.
For a TDMoIP application, the configuration of one or more PVCR PVCs that
manage the GSM PVCs. Refer to Configuring the NetPerformer for TDMoIP
on page 2-7. Redundant PVCR PVCs can be configured for higher network availability, as described in PVC Link Redundancy in a TDMoIP Application on
page 3-11.
Fine-tuning of GSM and GPS operations for special applications, using an
extended parameter set. Refer to the Extended Parameters module of this document series.
UnitID>
(main prompt)
Setup (SE)
GSM (GS)
BTS
ABIS
BSC BSC MSC

ABIS ATER ATER
PVC
SLOT (SL)
GSM
LINK (LI)
NONE
CHANNEL (CH)
GSM
Figure 2-1: Configuring the NetPerformer for GSM A or E
NOTE:
2-4
Support of GSM A or E traffic is available with the NetPerformer base software on all products.
Memotec Inc.
Configuration
GSM A or E traffic requires SS7 signaling and digital voice channels that support the
G.711, ACELP-CN or other voice codec. Refer to Using NetPerformer on the GSM A/E
Interface on page 1-7 for a description of this application.
To configure a NetPerformer unit for support of GSM A or E:
Define the physical port (LINK) on the T1 or E1 interface card using the SLOT/
LINK submenu of the SETUP command.
The Signaling mode parameter must be set to NONE. Refer to:
- Configuring a T1 Physical Port (LINK) on page 2-8
- Configuring an E1 Physical Port (LINK) on page 2-10
Define one or more channels to carry signaling information, using the SLOT/
CHANNEL submenu of the SETUP command
The Protocol parameter must be set to SS7 or SS7MTP2. Refer to Configuring an SS7 Signaling Channel on page 2-13
Define one or more channels to carry voice traffic, using the SLOT/CHANNEL
submenu of the SETUP command. The Protocol parameter can be set to G.711,
ACELP-CN or another voice protocol typical of other digital voice applications.
For configuration details, refer to the Digital Voice module of this document
series.
NOTE:
2.2.1
For a GSM A or E application the Location on the GSM network does not
need to be defined, the GSM auto detect mode LINK parameter has no
effect, and the GSM submenu of the SETUP command is not used.
Configuring the NetPerformer for GSM Abis
NOTE:
Support of GSM Abis is available only on an SDM-9210, SDM-9220,

SDM-9230, SDM-9606 or SDM-9620 installed with the GSM A-bis/ter
licensed software option. For the installation procedure, refer to the Software Installation and Licensing module of this document series.
GSM Abis traffic requires timeslot subchannels that are configured for voice/data traffic
(TCH) or signaling and O&M functions (SIG). The Location on the GSM network must
also be defined on the GSM channel. Refer to Using NetPerformer on the GSM Abis
Interface on page 1-10 for a description of this application.
To configure a NetPerformer unit for support of GSM Abis:
Memotec Inc.
2-5
GSM Solution

Configure the GSM parameters (SE/GSM), as described in Configuring the
GSM Parameters on page 2-12
Define the logical connections (channels) that carry GSM Abis traffic, using the
SLOT/CHANNEL submenu of the SETUP command. Refer to Configuring the
GSM Traffic Channels (CHANNEL) on page 2-16.
NOTE:
2.2.2
An SS7 signaling channel is not required in an Abis application. All signaling is carried by the timeslot subchannels that are configured for this purpose. If you are configuring the timeslot subchannels manually, refer to
Configuring the Timeslot Subchannels Manually (TSSUB) on page 2-18.
Configuring the NetPerformer for GSM Ater
NOTE:
Support of GSM Ater is available only on an SDM-9210, SDM-9220,

SDM-9230, SDM-9606 or SDM-9620 installed with the GSM A-bis/ter
licensed software option. For the installation procedure, refer to the Software Installation and Licensing module of this document series.
GSM Ater traffic requires SS7 signaling and timeslot subchannels that carry voice or data
only. The Location on the GSM network must also be defined on the GSM channel. Refer
to Using NetPerformer on the GSM Ater Interface on page 1-16 for a description of this
application.
To configure a NetPerformer unit for support of GSM Ater:
Configure the GSM parameters (SE/GSM), as described in Configuring the
GSM Parameters on page 2-12
Define one or more channels to carry signaling information, using the SLOT/
CHANNEL submenu of the SETUP command
The Protocol parameter must be set to SS7 or SS7MTP2. Refer to Configuring an SS7 Signaling Channel on page 2-13
2-6
Memotec Inc.
Configuration
Define the logical connections (channels) that carry GSM Ater traffic, using the
SLOT/CHANNEL submenu of the SETUP command. Refer to Configuring the
GSM Traffic Channels (CHANNEL) on page 2-16.
You must define the timeslot subchannels manually (TSSUB), with the TS
subchannel mode parameter set to TCHD or TCHU on all timeslot subchannels. Refer to Configuring the Timeslot Subchannels Manually (TSSUB) on
page 2-18.
2.2.3
Configuring the NetPerformer for TDMoIP

The TDMoIP application (packet over IP delivery) is described in TDMoIP Application
on page 1-22. The following are general requirements for NetPerformer support of
TDMoIP:
The GSM Abis/Ater licensed software option must be activated on both NetPerformer units (BTS and BSC sides)
IP connectivity is required on both NetPerformer units. Refer to the LAN Connection and IP Networks module of this document series
A PVCR PVC must be defined on both NetPerformer units to manage the connection between them. This PVC must be configured for PVCR over IP, that is,
with the Port parameter set to 0. Refer to the WAN/Frame Relay module of this
document series.
PVCR PVCs can be configured between a unit or blade running GSM and a unit
without the GSM software license. For a product that is not installed with the
GSM license, set the PowerCell version global parameter to V2. This selects the
latest PowerCell version, which provides an increased number of cell relay channels for GSM support.
One GSM PVC must be defined on each NetPerformer unit to transport the GSM
traffic. See Configuring the GSM PVCs on page 2-14.
Global parameters (SE/GLOBAL) that influence traffic shaping include:
- Global CIR for FR over IP
- Timer in ms for FR over IP
For details on the Global parameters, refer to the appendix SE/GLOBAL Configuration Parameters in the Quick Configuration module of this document
series.
Caution: Multihomed IP routing must not be used in a TDMoIP application.
To turn it off, enter the following at the NetPerformer console command line:
EP IP MULTIHOMEDTYPE DISABLED
Memotec Inc.
2-7
GSM Solution
2.3
Configuring the Digital Link

The SLOT/LINK submenu of the SETUP command includes all parameters that define the
physical port (LINK) on a T1 or E1 interface card.
NOTE:
2.3.1
The following procedures apply to all GSM interface types supported by the
NetPerformer: A, E, Abis and Ater. However, the parameters listed are
slightly different for a T1 versus an E1 interface card, and for a Dual Framer
interface card versus a legacy digital interface card.
Configuring a T1 Physical Port (LINK)

To define the physical port on a T1 interface card:
1.
Enter the menu sequence: SE SLOT
2.
Select the Slot number
3.
On a Dual Framer interface card only (E1/T1), select the Port number
4.
Enter LINK
5.
On a Dual Framer interface card only (E1/T1), define the Framer Type for this link.
Enter T1
6.
Set the Status to ENABLE to activate the physical link
NOTE:
If the physical link is disabled, all data channels associated with this port are
disabled as well. You can continue with channel configuration, and then
enable the link at a later time.
7.
Set Clock recovery to ENABLE if required for your application
8.
Select the Digital port clock source, either INTERNAL or the slot number of the
interface that provides the clock source
9.
Set the Signaling mode to NONE
10.
For an Abis application, set the GSM auto detect mode to:
MASTER: To initialize autodetection on the DSPs, and detect what channels are
required based on traffic received over the link.
When the MASTER link receives the configuration from the DSPs, it sends a
configuration message to the SLAVE link on the remote unit. The MASTER is
usually the link on the BSC side, but it can be on the BTS side if required by the
application.
2-8
Memotec Inc.
Configuration
SLAVE: No autodetection is performed on the link. Rather, the link waits for the
configuration message sent from the MASTER.
The SLAVE is usually on the BTS side, but can be on the BSC side if required by
the application.
A link defined in MASTER mode must face a link defined in SLAVE mode.
Likewise, a SLAVE link must face a MASTER link.
DISABLE: The Autodetection feature is turned off, and you must configure the
timeslot subchannels manually (refer to Configuring the Timeslot Subchannels
Manually (TSSUB) on page 2-18).
The NetPerformer can also be configured to restart the autodetection process
whenever the traffic type changes on a timeslot subchannel. The GSM parameter
Continuous AUTO detection controls this feature (refer to Configuring the GSM
Parameters on page 2-12).
GSM auto detect mode affects only those timeslots that are configured with
the GSM protocol (using the Protocol parameter in the SE/SLOT/CHANNEL
submenu). If you do not want Autodetection to operate on a particular timeslot in
an Abis application, set the timeslot to OFF or to another Protocol value. Autodetection does not apply to A, E or Ater traffic, and the GSM auto detect mode
parameter has no effect on these applications.
11.
Change the other digital link parameters from their default values, if desired.
For details on the other parameters listed for T1 link configuration, consult the
appendix SE/SLOT/#/LINK Configuration Parameters in the Digital Data
SE/SLOT/#/
LINK example:
on a T1
interface card
Memotec Inc.
SDM-9230-BSC>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/GSM/HUNT/IP/IPX/
MAP/
PHONE/PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/SS7/USER/
VLAN,
def:BRIDGE) ? SLOT
SLOT> Slot number (1/2/3,def:1) ? 1
Port number (1/2,def:1) ? 1
Item (LINK/CHANNEL,def:LINK) ? LINK
PORT 100> Framer Type (def:E1) ? T1
PORT 100> Status (def:DISABLE) ? ENABLE
PORT 100> Clock recovery (def:DISABLE) ?
GLOBAL > Digital port clock source (def:1) ?
PORT 100> Signaling mode (def:NONE) ?
PORT 100> Pcm encoding law (def:MU-LAW) ?
PORT 100> Hunt Group Sorting (def:RRA) ?
PORT 100> Idle code (def:7F) ?
PORT 100> Zero suppression mode (def:B8ZS) ?
PORT 100> Long Haul (def:NO) ?
PORT 100> Framing mode (def:ESF) ?
PORT 100> Line Build Out (def:0-133FT) ?
PORT 100> Custom Waveform (def:DISABLE) ?
PORT 100> Loopback (def:DISABLE) ?
PORT 100> PVCR Link management (def:DISABLE) ?
PORT 100> GSM auto detect mode (def:DISABLE) ? MASTER
2-9
GSM Solution
2.3.2
Configuring an E1 Physical Port (LINK)

To define the physical port on an E1 interface card:
1.
2.
3.
On a Dual Framer interface card only (E1/T1), select the Port number
4.
Enter LINK
5.
On a Dual Framer interface card only (E1/T1), define the Framer Type for this link.
Enter E1
6.
Set the Status to ENABLE to activate the physical link
NOTE:
If the physical link is disabled, all data channels associated with this port are
disabled as well. You can continue with channel configuration, and then
enable the link at a later time.
7.
Set Clock recovery to ENABLE if required for your application
8.
Select the Digital port clock source, either INTERNAL or the slot number of the
interface that provides the clock source
9.
Set the Signaling mode to NONE
10.
For an Abis application, set the GSM auto detect mode to MASTER, SLAVE or
DISABLE, as described for T1 link configuration on For an Abis application, set the
GSM auto detect mode to: on page 2-8
A link defined in MASTER mode must face a link defined in SLAVE mode.
Likewise, a SLAVE link must face a MASTER link.
11.
Change the other digital link parameters from their default values, if desired.
For details on the other parameters listed for E1 link configuration, consult the
appendix SE/SLOT/#/LINK Configuration Parameters in the Digital Data
2-10
Memotec Inc.
Configuration
SE/SLOT/#/
LINK example:
on an E1
interface card
(Dual Framer)
Memotec Inc.
SDM-9230-BTS>SE
SETUP
MAP/
VLAN,
def:BRIDGE) ? SLOT
Port number (1/2,def:1) ? 1
Item (LINK/CHANNEL,def:LINK) ?
PORT 300> Framer Type (def:E1) ?
PORT 300> Status (def:DISABLE) ? ENABLE
PORT 300> Clock recovery (def:DISABLE) ? ENABLE
GLOBAL > Digital port clock source (def:1) ?
PORT 300> Signaling mode (def:NONE) ?
PORT 300> Interface Mode (def:TE) ?
PORT 300> Pcm encoding law (def:A-LAW) ?
PORT 300> Hunt Group Sorting (def:RRA) ?
PORT 300> Idle code (def:7E) ?
PORT 300> Zero suppression mode (def:HDB3) ?
PORT 300> Long Haul (def:NO) ?
PORT 300> Impedance and Line Build Out (def:120 OHMS) ?
PORT 300> Custom Waveform (def:DISABLE) ?
PORT 300> CRC4 mode (def:ENABLE) ?
PORT 300> International bit (def:ENABLE) ?
PORT 300> Loopback (def:DISABLE) ?
PORT 300> PVCR Link management (def:DISABLE) ?
PORT 300> GSM auto detect mode (def:DISABLE) ? SLAVE
2-11
GSM Solution
2.4
Configuring the GSM Parameters

The GSM submenu of the SETUP command includes all parameters that affect GSM
operations on all digital channels that are configured for GSM Abis or Ater support on the
NetPerformer unit.
NOTE:
The GSM parameters appear only on a NetPerformer unit that has been
installed with the GSM Abis/Ater licensed software option. They are
applied globally to all GSM timeslot subchannels.
To configure the GSM parameters:

1.
At the NetPerformer command line prompt, enter the menu sequence: SE GSM
2.
Specify the desired Jitter buffer (ms) for your application
3.
Specify the Mode used when SIG detected and the Mode used when TCH detected on
the timeslot subchannels
4.
Disable Continuous AUTO detection, if desired (default ENABLE)
5.
Set Activate 3G support to NO to disable 3G support and enable the second Ethernet
port (default YES)
Any change to this parameter must be confirmed, and the unit must be reset with the
Reset Unit (RU) command. See Examples: on page 6-4 for examples.
6.
Enter the Call management timeout (s) for control of Call Blocking in an IGMP/
Multicast application.
The GSM maximum calls parameter on the GSM PVC also determines how Call
Blocking behaves. See GSM maximum calls on page 8-5.
SE/GSM
example
SDM-9230-BTS>SE
SETUP
MAP/
VLAN,
def:BRIDGE) ? GSM
GSM> Jitter buffer (ms) (4-160,inc:4,def:20) ?
GSM> Mode used when SIG detected (def:SIG) ?
GSM> Mode used when TCH detected (def:TCHD) ?
GSM> Continuous AUTO detection (def:ENABLE) ?
GSM> Activate 3G support (def:YES) ? NO
GSM> Call management timeout (s) (0-255,inc:5,def:0) ?
Details on all of these parameters are provided in the appendix SE/GSM Configuration
Parameters on page 6-1.
2-12
Memotec Inc.
Configuration
2.5
Configuring an SS7 Signaling Channel

An SS7 signaling channel is required on the NetPerformer to support GSM A, E or
Ater traffic. SS7 is available with the NetPerformer base product.
To define an SS7 signaling channel:
1.
2.
3.
Enter CHANNEL
4.
Select the Channel Number, or enter ALL to configure all channels at once
5.
Set the Protocol to either:

SS7: FISU spoofing. Only significant data is transmitted end to end, and idles
and redundant data are handled locally
SS7MTP2: MTP2 layer termination. No FISU or LSSU frames are transported to
the remote side.
The NetPerformer unit at the remote end also requires a CHANNEL set to the same
protocol.
6.
Select the Timeslot to be assigned to this channel.

Any timeslot can be used as the SS7 signaling channel.
7.
Change the Idle from its default value, if desired
8.
Define the destination for all traffic from this channel:

Remote unit
Remote port number
9.
SE/SLOT/#/
CHANNEL
example: for
SS7 signaling
channel
Memotec Inc.
Define the priority Class to which all traffic from this channel belongs
SDM-9230-MSC>SE
SETUP
MAP/
VLAN,
def:BRIDGE) ? SLOT
Item (LINK/CHANNEL,def:LINK) ? CHANNEL
SLOT> Channel Number (101-131/ALL,def:101) ? 131
PORT 131> Protocol (def:OFF) ? SS7
PORT 131> Timeslot (def:3) ? 16
PORT 131> Idle (def:FLAG) ?
PORT 131> Remote unit (def:) SDM-9230-BSC
PORT 131> Class (def:3) ?
PORT 131> Remote port number (1-65534,def:131) ?
2-13
GSM Solution
2.6
Configuring the GSM PVCs

A GSM PVC must be configured on each NetPerformer unit participating in a TDMoIP
application. Refer to TDMoIP Application on page 1-22 for a description of this
application.
Configuring and Activating the GSM PVCs

The GSM PVCs are configured using the PVC submenu of the SETUP (SE) command.
To configure a GSM PVC:
1.
Enter the menu sequence: SE PVC at the NetPerformer command line prompt
2.
Select the PVC number of the PVC you want to configure
3.
Set the Mode parameter to GSM
4.
Specify the GSM traffic type that will be carried by this PVC: TCH or NONE
TCH represents both voice/data traffic and signaling traffic in the TCH stream.
5.
Set the Port to 0
6.
Specify a unique DLCI address
7.
Set the Committed Information rate
8.
Set the Frame over IP characteristics:

Frame over IP, source: enter the IP address of the source unit
Frame over IP, destination: enter the IP address of the destination unit
Frame over IP, port number: from 1 to 65535
Frame over IP, DSCP: the relative priority from 0 to 63.
9.
Set Use a forced route to YES, if desired, and specify the Port to be used. Enter a
question mark ? for a full list of available ports
10.
Set the GSM maximum calls for Call Blocking. The default value, 0, means no calls
will be blocked.
Call Blocking can be used an IGMP/Multicast application. Refer to GSM
maximum calls on page 8-5 for configuration details.
11.
Configure the VAD parameters, if desired for your application (see Constant
Bandwidth Support on page 1-26):
GSM VAD Deactivate threshold
GSM VAD Activate threshold
GSM VAD A (bps)
GSM VAD B (bps)
GSM VAD K (coefficient in percentage)
2-14
Memotec Inc.
Configuration
NOTE:
SE/PVC/GSM
example
Leave these parameters at zero (0) if constant bandwidth is not required.
12.
The GSM group parameter is reserved for special applications. In most cases it should
be left at its default value, 0. If changed, the same value must be configured on both
the BTS-side and BSC-side units.
13.
Set the GSM maximum frame size (default 1504 octets) to define the largest IP frame
that can be sent.
14.
Set the GSM pack delay (ms) for control of packetization on this PVC
15.
For PVC link redundancy in a TDMoIP application, select the PVCR PVC that
manages this PVC.
SDM-9230-BSC>SE
SETUP
MAP/
VLAN,
def:BRIDGE) ? PVC
PVC number (1-300,def:1) ? 2
PVC 2> Mode (def:OFF) ? GSM
PVC 2> GSM traffic type (def:NONE) ? TCH
PVC 2> Port (def:1 ) ? 0
PVC 2> DLCI address (0-1022,def:0) ? 101
PVC 2> Committed Information rate (4000-100000000,def:10000000) ?
PVC 2> Frame over IP, source (def:000.000.000.000) ? 5.072.001.111
PVC 2> Frame over IP, destination (def:000.000.000.000) ?
5.072.001.110
PVC 2> Frame over IP, port number (1-65535,def:1024) ?
PVC 2> Frame over IP, DSCP (0-63,def:0) ?
PVC 2> Use a forced route (def:NO) ? YES
PVC 2> Port (def:NONE) ? WAN 1
PVC 2> GSM maximum calls (0: no call rejected) (0-10000,def:0) ?
PVC 2> GSM VAD Deactivate threshold (0-10000,def:0) ?
PVC 2> GSM VAD Activate threshold (0-10000,def:0) ?
PVC 2> GSM VAD A (bps) (0-15000000,def:0) ?
PVC 2> GSM VAD B (bps) (0-15000000,def:0) ?
PVC 2> GSM VAD K (coefficient in percentage) (0-100,def:0) ?
PVC 2> GSM group (0-65535,def:0) ?
PVC 2> GSM maximum frame size (1-1504,def:1504) ?
PVC 2> GSM pack delay (ms) (0-100,inc:4,def:0) ?
PVC 2> PVCR PVC that manages this PVC (def:NONE) ? FR-PVC 1
Details on these parameters can be found in the appendix SE/PVC/#/GSM Configuration

Parameters on page 8-1.
Memotec Inc.
2-15
GSM Solution
2.7
Configuring the GSM Traffic Channels (CHANNEL)

GSM channels are required on the NetPerformer to support GSM Abis or Ater
traffic. They can be configured only on a NetPerformer unit that has been installed
with the GSM Abis/Ater licensed software option.
The SLOT/CHANNEL submenu of the SETUP command includes all parameters that
define the logical connections for GSM Abis or Ater traffic, including the channels,
timeslots and timeslot subchannels (TSSUB).
In a GSM Abis or Ater application, each channel can contain only one timeslot, and each
timeslot is divided into a number of subchannels. For Abis the type of traffic supported on
the timeslot subchannels is determined in one of two ways, depending on the value of the
GSM auto detect mode parameter on the digital link (see For an Abis application, set
the GSM auto detect mode to: on page 2-8):
GSM auto detect mode set to MASTER or SLAVE: The NetPerformer automatically configures the timeslot subchannels using its Autodetection function. You
are not required to configure each subchannel independently.
GSM auto detect mode set to DISABLE: You must configure the timeslot subchannels manually. This is also the method used for an Ater configuration.
Refer to Configuring the Timeslot Subchannels Manually (TSSUB) on page 218.
NOTE:
The logical connections are defined in the exactly same way for GSM Abis
and GSM Ater traffic. However, if you are defining the timeslot subchannels manually, the TS subchannel mode of a GSM Ater logical connection
must be set to TCHD or TCHU for support of voice/data only, as all signaling
is handled by the SS7 signaling channel. Refer to Configuring an SS7 Signaling Channel on page 2-13.
To define the GSM Abis or Ater logical connections:

1.
2.
3.
Enter CHANNEL
4.
Select the Channel Number, or enter ALL to configure all channels at once
5.
Set the Protocol to GSM
NOTE:
The NetPerformer unit at the remote end also requires a CHANNEL set to the
GSM protocol.
If you do not want the NetPerformer to detect the traffic type automatically on
2-16
Memotec Inc.
Configuration
a specific timeslot, set the Protocol to OFF (the default value).
6.
Select the Timeslot to be assigned to this channel

Only one Timeslot can be selected. Thus for a GSM channel, the Number of
consecutive timeslots is a read-only parameter.
7.
Set the Location on the GSM network to:

BTS ABIS: To support Abis traffic at a remote site, where the channel is connected to the base transceiver station via the digital E1/T1 link
BSC ABIS: To support Abis traffic at the hub site, where the channel is connected to the base station controller via the digital link
BSC ATER: To support Ater traffic at a remote site, where the channel is connected to the base station controller via the digital link
MSC ATER: To support Ater traffic at the hub site, where the channel is connected to the TRAU in front of the MSC via the digital link.
8.
Specify the Vendor of the GSM units
9.
If the value of the GSM auto detect mode on the digital link has been set to DISABLE
(see For an Abis application, set the GSM auto detect mode to: on page 2-8), define
the timeslot subchannel (TSSUB) parameters:
TS subchannel mode: SIG, TCHU or TCHD
Subchannel speed mask
For a SIG timeslot subchannel, the Idle code
Refer to Configuring the Timeslot Subchannels Manually (TSSUB) on page 2-18.
10.
Define the destination for all traffic from this channel:

Remote unit
Remote port number
SE/SLOT/#/
CHANNEL
example, with
Autodetection
of timeslot
subchannels
Memotec Inc.
SDM-9230-BTS>SE
SETUP
MAP/
VLAN,
def:BRIDGE) ? SLOT
Port number (1/2,def:1) ?
PORT 101> Protocol (def:OFF) ? GSM
PORT 101> Timeslot (def:1) ?
PORT 101> Number of consecutive timeslots........1
PORT 101> Location on the GSM network (def:BTS ABIS) ?
2-17
GSM Solution
PORT 101> Vendor of the GSM units (def:ANY) ?

TSSUB 1011> TS subchannel mode (def:OFF) ? TCHD
TSSUB 1011> Subchannel speed mask (def:00) ? C0
TSSUB 1013> Subchannel speed mask (def:00) ? 30
TSSUB 1015> Subchannel speed mask (def:00) ? 0C
TSSUB 1017> TS subchannel mode (def:OFF) ? SIG
TSSUB 1017> Idle code (def:7E) ?
PORT 101> Remote unit (def:) ? SDM-9230-BSC
Details on all of these parameters are provided in the appendix SE/SLOT/#/CHANNEL

Configuration Parameters on page 7-1.
2.7.1
Configuring the Timeslot Subchannels Manually (TSSUB)

If you have disabled the Autodetection function on the digital link (GSM auto detect mode
set to DISABLE), all timeslot subchannels must be configured manually. This can be
useful for special applications requiring fine-tuning of the type of traffic supported on
individual subchannels.
The parameters for all timeslot subchannels (TSSUB) are presented during configuration
of the GSM Abis or Ater logical connections (see the preceding section).
To define the GSM Abis/Ater timeslot subchannels manually:
1.
Execute steps 1 to 7 described on Enter the menu sequence: SE SLOT on page 216
The TSSUB parameters are listed after the Vendor of the GSM units parameter. The
prefix for each parameter indicates which subchannel is being configured, in the
format TSSUB xxxy, where:
xxx is the Channel Number
y is the subchannel number.
NOTE:
2.
The NetPerformer will continue to prompt you for subchannel configuration

information as long as the timeslot can handle another subchannel (a least one
bit of the 64-Kbps timeslot is still available). A maximum of 8 subchannels
are available per timeslot, e.g. TSSUB 1011 to TSSUB 1018.
Select the TS subchannel mode required for your application:

SIG: Signaling channel, which may also contain operation and maintenance
(O&M) information. Used in a GSM Abis application only
2-18
Memotec Inc.
Configuration
TCHU: Uncompressed traffic channel using GSM Abis or Ater. Carries voice or
data, but the frames are never compressed. This can be useful for transmitting
GPRS traffic in a satellite application.
TCHD: Dual rate traffic channel for voice or data using GSM Abis or Ater. In this
mode, the subchannel is configured at 16 Kbps, and can process a single traffic
stream at 16 Kbps or two traffic streams at 8 Kbps each. See Dual Rate Traffic
Channels on page 1-14.
3.
Set the Subchannel speed mask to a hexadecimal value. The speed mask determines
which burst of the TDMA frame is handled by this timeslot subchannel (see Time
Division Multiple Access (TDMA) on page 5-10).
All bits set to 1 must be contiguous, and no Subchannel speed mask value can
overlap the mask configured for another timeslot subchannel. The NetPerformer
provides a warning if an improper value is entered. Refer to Subchannel speed
mask on page 7-5 for details on this parameter.
SE/SLOT/#/
CHANNEL
example: for
GSM Abis,
with manual
configuration
of timeslot
subchannels
4.
For a SIG timeslot subchannel, change the Idle code from its default value, if desired.
5.
Configure the remaining CHANNEL parameters (step 10 in Define the destination

for all traffic from this channel: on page 2-17).
SDM-9230-BTS>SE
SETUP
MAP/
VLAN,
def:BRIDGE) ? SLOT
PORT 116> Protocol (def:OFF) ? GSM
PORT 116> Timeslot (def:16) ?
PORT 116> Number of consecutive timeslots........1
PORT 116> Location on the GSM network (def:BTS ABIS) ?
TSSUB 1161> Subchannel speed mask (def:00) ? C0
TSSUB 1163> Subchannel speed mask (def:00) ? 0C
TSSUB 1164> TS subchannel mode (def:OFF) ? SIG
TSSUB 1164> Idle code (def:7E) ?
PORT 116> Remote unit (def:) ? SDM-9230-BSC
Details on the TSSUB parameters are provided in the appendix SE/SLOT/#/CHANNEL

Configuration Parameters on page 7-1.
Memotec Inc.
2-19
GSM Solution
2.8
Extended Parameters
Several extended parameters are available to fine-tune the NetPerformer for special GSM
applications. These parameters are available from the NetPerformer console only
under 4 subtypes of the Extended Parameters (EP) command:
GSM: For fine-tuning GSM operations on the unit: BYPASSUDP, DSPCOMP,
ETHTXOPT, FLOWCTLACCUMULATION, FROIPTXOPT, IDLEMARK,
IDLESTOP, INTFSTATEVALIDATION, NBRXBUFFER, SIGBYPASSCR,
TRAFFICPRIO, VOICEONLY
PORT: For fine-tuning a PVCR port or channel that carries GSM traffic:
GSMTXQTHRESHOLD, TXQDATALEVEL, TXQLOWLEVEL,
TXQVOICELEVEL
PVC: For fine-tuning a PVCR PVC and its related GSM PVC in a TDMoIP GSM
application: TXONFRCHECKTIMER, TXQDATALEVEL, TXQLOWLEVEL,
TXQVOICELEVEL
GPS: For fine-tuning GPS operations and statistics: PLLENABLE, STATUSSOURCE
Information on these parameters is available in the Extended Parameters module of the
NetPerformer System Reference (Doc. No. 620-0216-021). For fast access, click on
the parameter name in the document index.
2-20
Memotec Inc.
3
Advanced GSM Applications
This chapter includes a discussion of:

Enhanced High-precision Clocking on page 3-2 (see next section)
Satellite Backup on page 3-9.
PVC Link Redundancy in a TDMoIP Application on page 3-11.
Memotec Inc.
3-1
GSM Solution
3.1
Enhanced High-precision Clocking

High-precision clocking for synchronization and timing control is available as an
enhancement option on the SDM-9210, SDM-9220 and SDM-9230. Contact Memotec
Inc. or your NetPerformer distributor for ordering information. Options include:
Temperature Compensated Crystal Oscillator (TCXO)
Stratum 3 clock (TCXO-S3)
G.823 PDH compliant GPS clocking module (for units installed with a GPS
receiver only)
A TCXO clock is included with the GPS clocking module, in case the GPS signal
is lost.
Enhanced clocking can be used for GSM applications that require TDMoIP (packet over
IP delivery). In particular, it supports GSM A-bis traffic that is transported over a serial or
packet network. In this application, the E1/T1 reference clocking source cannot be taken
from the serial or Ethernet interface. Thus, without the NetPerformer enhanced clock, the
clocks on the BTS and BSC will start drifting from each other.
The NetPerformer on the BTS side must supply the clock to the BTS, and therefore requires a precise clock source
Precise clocking is not required for the NetPerformer on the BSC side, since it is
able to retrieve the clock from the network.
A TDMoIP application with enhanced clocking is further discussed on NetPerformer
TDMoIP Application with Enhanced Clock on page 1-22.
3.1.1
Activating the Enhanced Clock

All units installed with an enhanced high-precision clock are factory set to operate
with the standard clock. If you want a unit to operate with the enhanced clock you must
activate it from the NetPerformer console. In addition, you must identify which
NetPerformer unit will provide the clock to the others.
To activate the enhanced clock:
1.
Set the Digital port clock source parameter on the link to INTERNAL, using the
SLOT/LINK submenu of the SETUP (SE) command. This setting will be applied
to all active links on the unit.
Refer to the Digital Data module of the NetPerformer System Reference for
details on this parameter.
2.
Select the oscillator source. By default, the standard clock is activated on all units.
You must change the oscillator source to activate an enhanced clock.
When the Digital port clock source is INTERNAL, the list of choices for the oscillator source corresponds to the clock module(s) that are installed on the unit.
- To view the available clocking options, enter the following at the NetPerformer command line prompt:
3-2
Memotec Inc.
EP GLOBAL OSCILLATORSOURCE ?
- To activate the TCXO clock, enter:

EP GLOBAL OSCILLATORSOURCE TCXO
- To activate the Stratum 3 clock, enter:

EP GLOBAL OSCILLATORSOURCE STRATUM-3
- To activate the GPS clocking module with TCXO clock, enter:

EP GLOBAL OSCILLATORSOURCE GPSTCXO
You must also activate the GPS port, as described in the next section.
- If you have already activated an enhanced clock, and want to use the standard
clock instead, enter:
EP GLOBAL OSCILLATORSOURCE STD_OSC
The STD_OSC setting is the default value.
3.1.2
Activating the GPS Port

A GPS port with a BNC connector is available on the SDM-9210 unit for connection of a
GPS antenna. Signals from a GPS satellite can be received by the GPS clocking module
via this port only if the port is activated.
To activate the GPS port:
1.
2.
Enter 3 as the Slot number
3.
Enter 301 as the Channel Number
4.
Set the Protocol to GPS.
NOTE:
SE/SLOT/#/
PORT 301
example
Memotec Inc.
If you leave the Protocol at its default value, OFF, the NetPerformer Phase
Locked Loop (PLL) system is operative, but the GPS STATUS column of the
Display GPS Status (DGPS) command will not be displayed at the console,
and it will be difficult to determine whether the GPS function has successfully
determined its position. Refer to Display GPS Status (DGPS) Command on
page 4-12 for details on how to monitor GPS using the DGPS command.
SDM-9230-BTS>SE
SETUP
Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/GPS/HUNT/IP/IPX/
MAP/
VLAN,
def:BRIDGE) ? SLOT
SLOT> Slot number (1/3,def:1) ? 3
3-3
GSM Solution
SLOT> Channel Number (301-301/ALL,def:301) ?

PORT 301> Protocol (def:OFF) ? GPS
Port 301 behaves like any other WAN connection with respect to statistics and traffic
capture commands:
Display States (DS) command:
SDM-9230-BTS>DS
DISPLAY STATES
Item (GLOBAL/PORT/REDUNDANCY/SLOT,def:GLOBAL) ? SLOT
SLOT> Slot number (3,def:3) ? 3
SLOT> Channel Number (301,def:301) ? 301
PORT 301> Protocol...............................GPS
PORT 301> Interface..............................DTE-RS232
PORT 301> Speed used (bps).......................38400
PORT 301> TxC speed (bps)........................N.A.
PORT 301> RxC speed (bps)........................N.A.
PORT 301> Modem signals..........................STDRCPORT 301> State..................................DATA
Modem signals:
d(S)r
d(T)r
(D)cd
(R)ts
(C)ts
r(I)
(-)off
Display Errors (DE) command:

SDM-9230-BTS>DE
DISPLAY ERRORS
Item (BOOTP/CHANNEL/DICT/GROUP/NAT/PORT/Q922/REDUNDANCY/SLOT/
TIMEP,
def:BOOTP) ? SLOT
PORT 301> Number of bad frames...................0
-----PORT 301> Number of underruns....................0
PORT 301> Number of retries......................0
PORT 301> Number of restarts.....................2
PORT 301> Number of frames discarded (overrun)...0
PORT 301> Number of octets discarded (bad).......0
PORT 301> Number of octets discarded (overrun)...0
Bad flags: U:Bad LENGTH
A:Abort
Q:Overflow
F:Flush
S:Overrun
B:Bad CRC
Display Counters (DC) command:

SDM-9230-BTS>DC
DISPLAY COUNTERS
Last counter reset : WED
2007/03/07 10:38:52
Item (BOOTP/CHANNEL/CONFIG/DNS/GROUP/IP/NAT/PORT/Q922/Q933/QOS/
REDUNDANCY/
SLOT/SNMP/TIMEP,def:BOOTP) ? SLOT
Counters (MEAN/PEAK,def:MEAN) ?
3-4
Memotec Inc.

PORT 301> Transmitter rate.......................0
% (M)
PORT 301> Receiver rate..........................0
% (M)
PORT 301> Number of frames transmitted...........0
PORT 301> Number of frames received..............0
PORT 301> Number of octets transmitted...........868
PORT 301> Number of octets received..............150636
Setup Capture (SC) command:

SDM-9230-BTS>SC
SETUP CAPTURE
Capture ITEM (DSP/PORT/PU/PVC/SE/SLOT/SVC,def:DSP) ? SLOT
Capture another item, please confirm (NO/YES,def:NO) ?
Capture direction (def:BOTH) ?
Capture mode (def:CONTINUE) ?
Capture ending (def:MANUAL) ?
Capture activation (def:BACKGROUND) ?
Start Capture (def:YES) ?
The capture is activated in background
View Capture (VC) command:

SDM-9230-BTS> VC
VIEW CAPTURE
Capture is running, stop capture? (NO/YES,def:NO) ? YES
Include WAN 301 (NO/YES,def:YES) ?
Decode control field (NO/YES,def:YES) ?
Display block headers (NO/YES,def:YES) ?
Capture Direction (RX/TX/BOTH,def:BOTH) ?
Display ASCII? (NO/YES,def:NO) ? YES
Include Unrequested Blocks? (NO/YES,def:YES) ?
Decode With Starting Block Number (1-47,def:1) ?
Wait for <ENTER> after each screen (NO/YES,def:YES) ?
SDM-9210 v10.X.X Memotec Inc. (c) 2007
Code base v10.X.X Memotec Inc. (c) 2007
BOOTSTRAP vX.X.X Memotec Inc. (c) 2007
BOOT vX.X.X Memotec Inc. (c) 2007
Hardware Info> Processor version (PVR): 0x8082
Hardware Info> Processor revision (PVR): 0x2013
Hardware Info> Processor mask number (IMMR): 0x0A01
Hardware Info> CPM RISC microcode revision: 0x0070
Hardware Info> Main board Id: 5
Hardware Info> Main FPGA version id: 3.4.0 option id: 2
Hardware Info> PBUS module: Precision clock (type=1)
Unit name: 9230>
Capture started> WED
Capture ended>
WED
Memotec Inc.
2007/03/07 10:58:36
2007/03/07 10:58:40
3-5
GSM Solution
TIME(SEC)DIR
0.000
RX WAN
INDEX
TYPE
WAN 301 COMPLETE
LNG DATA
48 BLOCK = 1
24475047 4C4C2C34 3532352E 37303937

38302C4E 2C303733 32372E34 39343938
392C572C 30303139 32392E37 34342C56
0.012
RX WAN
WAN 301 COMPLETE
48
BLOCK = 2
2C4E2A35 300D0A24 4750524D 432C3030

31393239 2E373434 2C562C34 3532352E
37303937 38302C4E 2C303733 32372E34
0.025
RX WAN
WAN 301 COMPLETE
48
$GPGLL,4525.7097
80,N,07327.49498
9,W,001929.744,V
,N*50..$GPRMC,00
1929.744,V,4525.
709780,N,07327.4
BLOCK = 3
39343938 392C572C 302E3030 302C302E

30302C30 3630312D 32302C2C 2C4E2A37
460D0A24 47504747 412C3030 31393239
94989,W,0.000,0.
00,0601-20,,,N*7
F..$GPGGA,001929
...
3-6
Memotec Inc.
3.2
About the Prioritization of GSM Traffic

This application takes advantage of PowerCell tunneling over the WAN (see PowerCell
Tunneling of Abis Traffic over Various WAN Networks on page 1-14), and permits the
prioritization of GSM traffic with respect to other traffic types using IP precedence
settings in a TDMoIP application.
NOTE:
This application requires a GSM PVC and a PVCRoIP PVC, as described in

Configuring the NetPerformer for TDMoIP on page 2-7.
PVC #1
Mode: PVCRoIP
Traffic type: PVCR
Precedence: 3
Satellite
PVC #2
Mode: GSM
Traffic type: TCH & SIG
Precedence: 5
TDMA
PO
WE R F A U L T
DAT A
L ARM
A
M
Satellite
Modem
Satellite dish
Satellite dish
RAL A
A T A D T L U A F R E WO
Satellite
Modem
SDM-9230
SDM-9230
SIG
SIG
TCH
TCH
BSC
Figure 3-1: IP Precedence for GSM Traffic
3.2.1
Uses and Benefits

GSM traffic prioritization guarantees that high-priority traffic, i.e. signaling traffic, will be
handled first by the satellite modems. This is particularly useful when the satellite
modems control QOS levels.
The satellite modem does the traffic shaping
A PowerCell connection can be configured on the NetPerformer to match the
required QOS levels, e.g. to prioritize SIG frames
When the GSM license is active, Cell Packetization can be configured on the
WAN port to permit longer frames
Memotec Inc.
3-7
GSM Solution
As a result, the NetPerformer is better able to provide sufficient bandwidth for all
traffic types.
3.2.2
How It Works
This application is based on PVCR over IP (see PowerCell Encapsulation of Abis
Traffic on page 1-14) using a port configuration that integrates PVCs designed to carry
GSM traffic.
The NetPerformer on the BSC side receives signaling traffic (SIG), voice (TCH)
and WAN traffic from the NetPerformer on the BSC side.
The value of the Frame over IP, precedence parameter on the PVCRoIP PVC
specifies the class of service.
The specific priority level of each class will vary depending on the IP service
provided (private or public). However, 0 (zero) is commonly associated with the
lowest priority level, and 7 the highest priority level.
By default, PVCR traffic is automatically assigned higher priority than GSM traffic when it is sent over the network. To give GSM traffic higher priority, set the
Frame over IP, precedence parameter on the PVCRoIP PVC to a relatively low
value, e.g. 3.
3-8
Memotec Inc.
3.3
Satellite Backup
The NetPerformer is able to back up a terrestrial E1 link with a satellite E1 link. One
application of this is to back up a GSM dedicated link over E1 with a satellite link that also
uses an E1 interface. Satellite backup can be configured on the NetPerformer when the E1
links are configured for Standard or Bypass operation.
NOTE:
3.3.1
Bypass operation is available on the SDM-9210 only, and requires a specially

designed E1/T1 interface. Hardware strapping is also required on the interface
(jumper pins installed on jumpers J8 and J9). For details, refer to the SDM9210 Hardware Installation Guide.
E1 Standard Mode
Figure 3-2: Satellite Backup in E1 Standard Mode
The backup link is activated automatically if the terrestrial link fails

The BTS and BSC must be configured for satellite operation
The NetPerformer is always optimizing A.bis traffic in this scenario.
Memotec Inc.
3-9
GSM Solution
3.3.2
E1 Bypass Mode
Figure 3-3: Satellite Backup in E1 Bypass Mode
During normal operation the SDM-9210 on the BTS side has all E1 links set to
Bypass mode (the Interface operating mode parameter set to MANUAL
BYPASS).
If the terrestrial link fails, backup is activated via satellite upon manual intervention by the operator (jumper settings on the E1/T1 Bypass interface)
The BTS/BSC configuration needs to be changed for satellite operation.
3.3.3
Configuration
Two parameters have been added to the configuration of a PVCR port and PVCR PVC to
permit satellite backup:
Allow load balancing. Indicates whether this PVCR port or PVC performs load
balancing. Set to NO to disable load balancing. By default load balancing is enabled (YES).
When Allow load balancing is set to NO, a second parameter is available: Link
rank in the group. This parameter indicates the relative ranking of this link (or
PVCR connection). The primary link must take the value 1. The first secondary
link must take the value 2. The other secondary links must take values from 3 to
10.
Both of these parameters are available for all serial WAN ports, WAN ports on the digital
interfaces, Frame Relay PVCs in PVCR mode, ATM PVCs in ATMPVCR mode and ATM
SVCs in ATMPVCR mode.
3-10
Memotec Inc.
3.4
PVC Link Redundancy in a TDMoIP Application

On the NetPerformer, a backup PVCR PVC can be configured to carry traffic from
another PVCR PVC that goes down. When applied to a TDMoIP application, this can
provide higher availability for GSM traffic, since an alternate ISP can be used if the
Internet path goes down.
The NetPerformer units on both the BTS and BSC sides of the network are configured with GSM channels, 2 GSM PVCs and 2 PVCRoIP PVCs.
Each GSM PVC transports the GSM traffic from one NetPerformer unit to the
other via one of the IP networks. The bulk of the traffic load is handled by these
PVCs.
The PVCR PVCs manage the GSM PVCs. Both PVCR PVCs go to the same destination, but through different IP networks. The traffic on these PVCs is primarily
Hello packets, which ascertain the current status of the WAN connection.
Only one PVCR PVC carries traffic at a time. Load balancing must be disabled
between the two PVCR PVCs by setting the Allow load balancing parameter to
NO.
One PVCR PVC is configured as the primary link, by setting the Link rank in the
group parameter to 1. The PVCR PVC that provides the backup link is configured with Link rank in the group set to 2.
If the primary link goes down, traffic is routed over the backup link. When the
primary link comes back up, the traffic is routed back to it.
Each GSM PVC is bound to a PVCR PVC using the parameter PVCR PVC that
manages this PVC. In this way, the GSM PVC follows the state (up or down) of
its managing PVCR PVC.
3.4.1
Configuration Example
Figure 3-4: PVC Link Redundancy for High Internet Availability
In this example, PVCs 1 and 2 use the Internet connection supplied by ISP #1. PVCs 3 and
4 use the Internet connection supplied by ISP #2. PVC 1 is configured as the primary link,
and PVC 3 as the backup link. If ISP #1 goes down, traffic is switched to IPS #2.
Memotec Inc.
3-11
GSM Solution
PVCR PVC 1
BSC>DP
DISPLAY PARAMETERS
Item (BRIDGE/CLASS/CUSTOM/GLOBAL/GSM/IP/IPX/PORT/PVC/REDUNDANCY/
SLOT/
SNMP/SS7/USER/ALL,def:PVC) ? PVC
PVC 1> Mode......................................PVCR
PVC 1> Port......................................0
PVC 1> DLCI address..............................1
PVC 1> Committed Information rate................2048000
PVC 1> Remote unit name..........................
PVC 1> Type......................................DEDICATED
PVC 1> Timeout (ms)..............................1000
PVC 1> Number of retransmission retries..........100
PVC 1> Compression...............................YES
PVC 1> IP address................................000.000.000.000
PVC 1> Subnet mask (number of bits)..............8
{255.000.000.000}
PVC 1> NAT enable................................NO
PVC 1> TCP acceleration..........................NO
PVC 1> BRG connection............................NO
PVC 1> Filter....................................ALL
PVC 1> Maximum number of voice channels..........10000
PVC 1> Maximum Voice Channels If High Priority Data 10000
PVC 1> Frame over IP, source.....................005.051.005.002
PVC 1> Frame over IP, destination................005.051.004.001
PVC 1> Frame over IP, port number................1024
PVC 1> Frame over IP, DSCP.......................0
PVC 1> Use a forced route........................NO
PVC 1> Use this port as default gateway..........NO
PVC 1> Redundant link............................NO
PVC 1> GSM group.................................0
PVC 1> Allow load balancing......................NO
PVC 1> Link rank in the group....................1
GSM PVC 2
BSC>DP
DISPLAY PARAMETERS
SLOT/
PVC 2> Mode......................................GSM
PVC 2> GSM traffic type..........................TCH
PVC 2> Port......................................0
PVC 2> DLCI address..............................2
3-12
Memotec Inc.
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
PVC
2>
2>
2>
2>
2>
2>
2>
2>
2>
2>
2>
Use a forced route........................NO

GSM maximum calls (0: no call rejected)...0
GSM VAD Deactivate threshold..............0
GSM VAD Activate threshold................0
GSM VAD A (bps)...........................0
GSM VAD B (bps)...........................0
GSM VAD K (coefficient in percentage).....0
GSM group.................................0
GSM maximum frame size....................1504
GSM pack delay (ms).......................0
PVCR PVC that manages this PVC............FR-PVC 1
PVCR PVC 3
BSC>DP
DISPLAY PARAMETERS
SLOT/
PVC 3> Mode......................................PVCR
PVC 3> Port......................................0
PVC 3> DLCI address..............................3
PVC 3> Remote unit name..........................
PVC 3> Type......................................DEDICATED
PVC 3> Timeout (ms)..............................1000
PVC 3> Number of retransmission retries..........100
PVC 3> Compression...............................YES
PVC 3> IP address................................000.000.000.000
PVC 3> Subnet mask (number of bits)..............8
{255.000.000.000}
PVC 3> NAT enable................................NO
PVC 3> TCP acceleration..........................NO
PVC 3> BRG connection............................NO
PVC 3> Filter....................................ALL
PVC 3> Maximum number of voice channels..........10000
PVC 3> Maximum Voice Channels If High Priority Data 10000
PVC 3> Use this port as default gateway..........NO
PVC 3> Redundant link............................NO
PVC 3> GSM group.................................0
PVC 3> Allow load balancing......................NO
PVC 3> Link rank in the group....................2
GSM PVC 4
BSCAF.BSC>DP
Memotec Inc.
3-13
GSM Solution
DISPLAY PARAMETERS
SLOT/
PVC 4> Mode......................................GSM
PVC 4> GSM traffic type..........................NONE
PVC 4> Port......................................0
PVC 4> DLCI address..............................4
PVC 4> GSM maximum calls (0: no call rejected)...0
PVC 4> GSM VAD Deactivate threshold..............0
PVC 4> GSM VAD Activate threshold................0
PVC 4> GSM VAD A (bps)...........................0
PVC 4> GSM VAD B (bps)...........................0
PVC 4> GSM VAD K (coefficient in percentage).....0
PVC 4> GSM group.................................0
PVC 4> GSM maximum frame size....................1504
PVC 4> GSM pack delay (ms).......................0
PVC 4> PVCR PVC that manages this PVC............FR-PVC 3
3-14
Memotec Inc.
4
Monitoring and Statistics
Memotec Inc.
4-1
GSM Solution
4.1
About Monitoring and Statistics

Several commands are available from the console to view the status of GSM connections
on the NetPerformer:
The Display GSM Channels (DCH) command provides a real-time analysis of the
status and errors for each timeslot subchannel (see next section)
The Display GSM TS Channel Allocation (DTSCH) command shows what type
of GSM Abis traffic is being carried by each timeslot subchannel (see Display
GSM TS Channel Allocation (DTSCH) Command on page 4-6)
The Display DSP Allocation (DDSP) command indicates how the DSP channels
are allocated to the timeslots (see Display DSP Allocation (DDSP) Command
on page 4-9)
The Display Jitter Level (DJL) command displays the amount of jitter that is
occurring on each timeslot subchannel, compared to the configured jitter level
(see Display Jitter Level (DJL) Command on page 4-10)
The Display GPS Status (DGPS) command shows the current status of GPS functions and Phase Locked Loop (PLL) activities (Display GPS Status (DGPS)
Command on page 4-12)
Use the GSM option of the Display Counters (DC) command to view the GSM
traffic types and number of calls supported, or the SLOT option for the transmit
and receive traffic counters (see Display Counters (DC) Command on page 417)
The SLOT option of the Display Errors (DE) command shows the values of the
error counters for the digital channels and timeslot subchannels (see Display
Errors (DE) Command on page 4-19)
Current status information can be viewed using the SLOT option of the Display
States (DS) command (see Display States (DS) Command on page 4-20)
Perform a traffic capture using the Setup Capture (SC) and Start Capture (STC)
command, and display the result with the View Capture (VC) command. The display includes decoding of the various communication protocols on all ports, as
well as call setup on the TCH. PCM raw data capture is also available (see PCM
Raw Data Capture on page 4-30).
4-2
Memotec Inc.
Debugging tools such as the ELOG command are also available for the use of
NetPerformer Technical Support personnel (see Error Log on page 4-32).
UnitID>
(main prompt)
DisplayGSM
Channels(DCH)
Real-time
status&
errors
Display DSP
Allocation (DDSP)
DisplayGSM TS
ChannelAllocation
(DTSCH)
Real-time timeslot
activity
Channel
allocation
Display
Counters
(DC)
DisplayGPS
Status(DGPS)
DisplayErrors
(DE)
DisplayStates
(DS)
GPS & PLL

DisplayJitter
Level(DJL)
GSM
Jitter buffer
GSM traffic
types
SLOT
SLOT
Traffic
Error counters
counters
(tx & rx)
SLOT
Currentstatus
Figure 4-1: GSM Display Commands in the CLI Tree
Two practical procedures for monitoring GSM operations are also provided in this
chapter:
Monitoring Activation of the Autodetection Function on page 4-21
Monitoring 3G Support Deactivation on page 4-24.
Memotec Inc.
4-3
GSM Solution
4.2
Display GSM Channels (DCH) Command

This command allows you to view the activity and total number of errors for each timeslot
subchannel.
To execute the DCH command:
1.
At the NetPerformer command line prompt, enter: DCH
2.
Select the Speed (bps) that the statistics will be sent to the console.
- The default speed is 115200 bps. Select this speed by pressing the carriage
return.
- Enter a different speed after the Speed (bps) prompt. Valid values are 1200,
2400, 4800, 9600, 14400, 19200, 28800, 38400, 57600 and 115200 bps.
- Once the speed is set, this question is not asked again during the same console
session.
3.
To scroll through the statistics for all timeslot subchannels:

- UP and DOWN arrow keys: to view lower or higher numbered timeslot
subchannels, respectively
- HOME: to view the first timeslot subchannels
- END: to view the last timeslot subchannels.
4.
The DCH command is available only on a NetPerformer unit that has been
installed with the GSM Abis/Ater licensed software option. It is not listed on
other units.
DCH example
SDM-9230-BTS>DCH
DISPLAY GSM CHANNELS
Speed (bps) (def:115200) ? 9600
-------------------------------------------------------------------------------| CH# TS ST ERR RX TX | CH# TS ST ERR RX TX | CH# TS ST ERR RX TX
|
-------------------------------------------------------------------------------| 1011 1 DA
0 41% 19% | 1013 1 DA
0 41% 19% | 1015 1 DA
0 41% 19% |
| 1017 1 DA
0 41% 19% | 1021 2 DA
0 41% 19% | 1023 2 DA
0 41% 19% |
| 1025 2 DA
0 41% 19% | 1027 2 DA
0 41% 19% | 1031 3 DA
0 41% 19% |
| 1033 3 DA
0 41% 19% | 1035 3 DA
0 41% 19% | 1037 3 DA
0 41% 19% |
| 1041 4 DA
0 41% 19% | 1043 4 DA
0 41% 19% | 1045 4 DA
0 41% 19% |
| 1047 4 DA
0 41% 19% | 1051 5 DA
0 41% 19% | 1053 5 DA
0 41% 19% |
| 1055 5 DA
0 41% 19% | 1057 5 DA
0 41% 19% | 1061 6 DA
0 41% 19% |
| 1063 6 DA
0 41% 19% | 1065 6 DA
0 41% 19% | 1067 6 DA
0 41% 19% |
| 1071 7 DA
0 41% 19% | 1073 7 DA
0 41% 19% | 1075 7 DA
0 41% 19% |
| 1077 7 DA
0 41% 19% | 1081 8 DA
0 41% 19% | 1083 8 DA
0 41% 19% |
| 1085 8 DA
0 41% 19% | 1087 8 DA
0 41% 19% | 1091 9 DA
0 41% 19% |
| 1093 9 DA
0 41% 19% | 1095 9 DA
0 41% 19% | 1097 9 DA
0 41% 19% |
| 1101 10 DA
0 41% 19% | 1103 10 DA
0 41% 19% | 1105 10 DA
0 41% 19% |
| 1107 10 DA
0 41% 19% | 1111 11 DA
0 41% 19% | 1113 11 DA
0 41% 19% |
| 1115 11 DA
0 41% 19% | 1117 11 DA
0 41% 19% | 1121 12 DA
0 41% 19% |
| 1123 12 DA
0 41% 19% | 1125 12 DA
0 41% 19% | 1127 12 DA
0 41% 19% |
| 1131 13 DA
0 41% 19% | 1133 13 DA
0 41% 19% | 1135 13 DA
0 41% 19% |
| 1137 13 DA
0 41% 19% | 1141 14 DA
0 41% 19% | 1143 14 DA
0 41% 19% |
| 1145 14 DA
0 41% 19% | 1147 14 DA
0 41% 19% | 1151 15 DA
0 41% 19% |
| 1153 15 DA
0 41% 19% | 1155 15 DA
0 41% 19% | 1157 15 DA
0 41% 19% |
-------------------------------------------------------------------------------Use HOME, END, UP and DOWN arrow keys to scroll. Press any other key to exit.
4-4
Memotec Inc.
NOTE:
The format (horizontal alignment) of this display has been changed slightly to
accommodate 4-digit port numbers and 5-digit TSSUB numbers on SDM9620 spans numbered 10 and higher.
The columns in the DCH display provide the following information:

CH#: Timeslot subchannel number
TS: Timeslot number
This number is also indicated by the second and third digits of the timeslot
subchannel number.
ST: Current state of this timeslot subchannel, which may be:
- ID: Idle
- DA: Data
- PA: Pause
- CA: Call
- OF: Off
- ST: Standby
ERR: Total number of errors that have occurred on this timeslot subchannel. For
details on these errors, execute the SLOT option of the Display Errors (DE) command (see Display Errors (DE) Command on page 4-19)
RX: The percentage of the bandwidth used for traffic received on this timeslot
subchannel
TX: The percentage of the bandwidth used for traffic transmitted from this timeslot subchannel.
Memotec Inc.
4-5
GSM Solution
4.3
Display GSM TS Channel Allocation (DTSCH) Command

This command displays the current timeslot configuration for the digital interface, and
shows what type of GSM Abis traffic is being carried by each timeslot subchannel. The
display is continuously updated in real time.
The DTSCH command also shows the number of active calls on the digital interface that is
currently displayed (Current slot), and for all digital interfaces on the unit (All slots).
To execute the DTSCH command:
1.
At the NetPerformer command line prompt, enter: DTSCH
2.
Select the GSM traffic direction, either INCOMING or OUTGOING
3.
Select the Speed (bps) that the statistics will be sent to the console.
The default speed is 115200 bps. Select this speed by pressing the carriage return.
Enter a different speed after the Speed (bps) prompt. Valid values are 1200, 2400,
4800, 9600, 14400, 19200, 28800, 38400, 57600 and 115200 bps.
Once the speed is set, this question is not asked again during the same console
session.
4.
To scroll through the statistics for all timeslot subchannels:

UP and DOWN arrow keys: to view lower or higher numbered timeslot subchannels, respectively
LEFT and RIGHT arrow keys: to view the timeslot subchannels of another port
HOME: to view the first timeslot subchannels of the current port
END: to view the last timeslot subchannels of the current port.
5.
A fast access method is also available, where you press a single key to bring up the
display of a specific span. This method uses a pseudo-hexadecimal correspondence
between span numbers and key numbers:
Spans 1 to 9: Press 1 to 9
Spans 10 to 15: Press A to F
Span 16: Press 0
At the bottom of the screen the message Other keys : press K is displayed. Press
the K key for an on-screen explanation of single keystroke access to span statistics.
NOTE:
4-6
The DTSCH command is available only on a NetPerformer unit that has

been installed with the GSM Abis/Ater licensed software option. It is not
listed on other units.
Memotec Inc.
DTSCH
example
SDM-9230-BTS>DTSCH
DISPLAY GSM TS CHANNEL ALLOCATION
GSM traffic direction (INCOMING/OUTGOING,def:INCOMING) ?
Speed (bps) (def:115200) ?
--------------------------------- SLOT 1-1 : E1 ----------------------INCOMING-|
| Number of active calls:
Current slot=48
All slots=48
|
| # TS| Bit7
Bit6
Bit5
Bit4
Bit3
Bit2
Bit1
Bit0 |
-------------------------------------------------------------------------------|101 1|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|
|102 2|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|
|103 3|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|
|104 4|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|
|105 5|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|
|106 6|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|
|107 7|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|
|108 8|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|
|109 9|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|
|110 10|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|
|111 11|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|
|112 12|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|
|113 13|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|
|114 14|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|
|115 15|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|
|116 16|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|
|117 17|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|
|118 18|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|<----AMR_670---->|
-------------------------------------------------------------------------------Use HOME, END, UP and DOWN arrow keys to scroll.
Use LEFT and RIGHT arrow keys to change slot. Press any other key to exit.
NOTE:
The first line of the display indicates the slot-port number, the type of digital interface and
whether the traffic is INCOMING or OUTGOING.
The columns in the DTSCH display provide the following information:
#: The channel number
TS: The timeslot number
Bitn: The location of the timeslot subchannels, represented according to bit
structure from MSB (Bit7) to LSB (Bit0)
For each timeslot subchannel, the subchannel mode or type of traffic currently
being carried by that timeslot subchannel is displayed beneath the applicable
Bitn columns:
- AMR_475: Adaptive Multi Rate (AMR) at 16 Kbps, using 4.75 Kbps mode
- AMR_515: AMR at 16 Kbps, using 5.15 Kbps mode
Memotec Inc.
4-7
GSM Solution
- AMR1020: AMR at 16 Kbps, using 10.2 Kbps mode

- AMR_SID: AMR at 16 Kbps, using Silence Descriptor (SID)
- AMR_SIDU: AMR at 16 Kbps, using Silence Descriptor Update (SIDU)
- AMRSID: AMR at 8 Kbps, using SID
- AMRSIDU: AMR at 8 Kbps, using SIDU
- BLOCKED: Call blocking in effect on this timeslot subchannel
- DATA_RA8: Full or Half Rate Data 8K
- DATA_RA16: Full or Half Rate Data 16K
- DOWN: The timeslot subchannel is down between the two NetPerformer units
- EDATA: Extended Data
- EDATA_SYNC: Extended Data - Synchronous
- EFR: Enhanced Full Rate
- FR: Full Rate
- GPRS_SYNC: GPRS at 16 Kbps, using Sync indicator
- HDLC: HDLC channel
- HR: Half Rate
- HR_O&M: Half Rate Operation and Maintenance
- HR_S: Half Rate for Siemens
- IDLESP: Idle speech frame
- IDLETR: Idle TRAU frame
- O&M: Operation and maintenance information processed by the DSP
- PASSTH: PASSTHRU channel
- SIG: Signaling processed by the DSP
- SS7: SS7 channel
- UNCOMP: Uncompressed TRAU frame
- UNKNOWN: Unknown frame type; the host application did not recognize the
frame received from the DSP.
4-8
Memotec Inc.
4.4
Display DSP Allocation (DDSP) Command

This command displays the DSP channel allocation according to channel profile.
To execute the DDSP command:
At the NetPerformer command line prompt, enter: DDSP.
DDSP example
SDM-9230-BTS>DDSP
DISPLAY DSP ALLOCATION
DSP
CH1
CH2
CH3
CH10
1
101
102
103
2
107
108
109
3
113
114
115
4
119
120
121
5
125
126
127
6
131
151
152
7
156
157
158
8
162
163
164
9
168
169
170
10
174
175
176
11
180
181
12
13
14
15
16
17
18
19
20
21
22
<ENTER>
23
24
NOTE:
Memotec Inc.
CH4
104
110
116
122
128
153
159
165
171
177
CH5
105
111
117
123
129
154
160
166
172
178
CH6
CH7
CH8
CH9
106
112
118
124
130
155
161
167
173
179
4-9
GSM Solution
4.5
Display Jitter Level (DJL) Command

This command allows you to view the current jitter level on each timeslot subchannel, and
compare it with the configured jitter level.
To execute the DJL command:
At the NetPerformer command line prompt, enter: DJL.
NOTE:
The DJL command is available only on a NetPerformer unit that has

been installed with the GSM Abis/Ater licensed software option. It is not
listed on other units.
DJL example
BSC>DJL
DISPLAY GSM JITTER LEVEL
-------------------------------------------------------------------------------| CH# TS ST JITTER LEVEL | CH# TS ST JITTER LEVEL | CH# TS ST JITTER LEVEL |
-------------------------------------------------------------------------------| 1011 1 DA
8 packets | 1013 1 DA
8 packets |
| 1017 1 DA
8 packets |
| 1025 2 DA
8 packets |
| 1033 3 DA
8 packets |
| 1041 4 DA
8 packets |
| 1047 4 DA
8 packets |
| 1055 5 DA
8 packets |
| 1063 6 DA
8 packets |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
------Configured Jitter Level: 8 ---------------------------------------------Use HOME, END, UP and DOWN arrow keys to scroll. Press any other key to exit.
The columns in the DJL display provide the following information:

CH#: Timeslot subchannel number
TS: Timeslot number
This number is also indicated by the second and third digits of the timeslot
subchannel number.
ST: Current state of this timeslot subchannel, which may be:
- ID: Idle
- DA: Data
- PA: Pause
- CA: Call
4-10
Memotec Inc.
- OF: Off
- ST: Standby
JITTER LEVEL: The amount of jitter on the timeslot subchannel, in packets.
Each packet is equivalent to 4ms of data.
For comparison purposes, the Configured Jitter Level is provided at the bottom of
the screen. In the above example the value is 8 packets, which indicates that the
Jitter buffer (ms) parameter is configured to 32 ms.
Memotec Inc.
4-11
GSM Solution
4.6
Display GPS Status (DGPS) Command

This command provides information about the current status of the GPS receiver installed
in the NetPerformer unit, and related Phase Locked Loop (PLL) activities. The DGPS
command has three submenus:
STATUS (see next section)
LOG (see Viewing the GPS Log on page 4-14)
VERSION (see Viewing the GPS Version on page 4-16).
NOTE:
4.6.1
The DGPS command is available only on a NetPerformer unit that has

been installed with the GPS G.823 PDH compliant clocking module. It is
not listed on other units.
Viewing the GPS Receiver and PLL Status

To view the status of the GPS receiver and PLL activities:
1.
At the NetPerformer command line prompt, enter: DGPS
2.
At the GPS prompt, enter STATUS.
The display is divided into two columns, labelled GPS STATUS (see next section) and
PLL STATUS (see PLL Status on page 4-14).
DGPS/STATUS
example
4-12
9230>DGPS
DISPLAY GPS STATUS
GPS (def:STATUS) ? STATUS
-------------------------------------------------------------------------------| GPS STATUS
PLL STATUS
|
-------------------------------------------------------------------------------| UTC Time:
000347.664
State:
HOLDOVER
|
| UTC Date:
0601-20
Nb Samples: 239
|
| Latitude:
4525.709780 N
PHn:
2.427380
|
| Longitude:
07327.494989 W
XLP:
0.000000
|
| Sats used in pos: 2
YLP:
0.000000
|
| Fix status:
No fix (NF)
YPI:
0.000000
|
| Time Accuracy:
99999
DAC:
36448
|
| Receiver Dynamics: 1
Status:
0201001D
|
| Sat: 30
signal: 29
Fault:
NO
|
| Sat: 31
signal: 30
|
| Sat:
0
signal: 0
|
| Sat:
0
signal: 0
|
| Sat:
0
signal: 0
|
| Sat:
0
signal: 0
|
| Sat:
0
signal: 0
|
| Sat:
0
signal: 0
|
| Sat:
0
signal: 0
|
| Sat:
0
signal: 0
|
| Sat:
0
signal: 0
|
| Sat:
0
signal: 0
|
-------------------------------------------------------------------------------Press ESC or any other key to exit.
Memotec Inc.
4.6.2
GPS Status
The GPS STATUS column indicates:
UTC Time: The current time, in Coordinated Universal Time (UTC)
UTC Date: The current date, UTC
Latitude: The current latitude of the GPS receiver
Longitude: The current longitude of the GPS receiver
Sats used in pos: The number of satellites providing global positioning information to the GPS receiver
Fix status: The status of the current fix, or position established by the GPS
receiver, which is shown in two fields:
- GPS status: Either No Fix or GPS Fix
- GPS fix solution (in brackets):
(NF): No fix
(G2): Standalone 2D solution
(G3): Standalone 3D solution.
Time accuracy: The estimated time accuracy of the GPS solution. The lower the
value, the better the clock accuracy.
Typically, after GPS startup, this value decreases gradually (indicating the clock
accuracy is improving) and eventually stabilizes once the satellite survey period
is complete (indicated by a Receiver dynamics value of 0).
Receiver dynamics: Indicates the dynamic of the GPS Receiver, which may be:
- 0: Fixed base station
- 1: Stationary, but unknown position
Typically, after GPS startup, the Receiver dynamics is at 1. Once the satellite
survey period is complete (about 20 minutes), it changes to 0.
Sat: A unique number assigned to each satellite that is currently sending a signal
to the GPS receiver. Up to 12 satellites can be supported at one time.
signal: The signal-to-noise ratio for each satellite detected. The higher the value,
the more dependable the signal. A value lower than 18 is considered inadequate
for precise clocking.
NOTE:
Memotec Inc.
The GPS STATUS column is not displayed if the GPS port is not activated.
Refer to Activating the GPS Port on page 3-3.
4-13
GSM Solution
4.6.3
PLL Status
NOTE:
The PLL STATUS column is not displayed if the extended GPS parameter
PLLENABLE is set to NO.
The PLL STATUS column indicates:

State: The current state of the Phase Locked Loop function, which may be:
- INIT: Initializing
- TRACKING: Clocking is following the GPS signal
- HOLDOVER: The GPS signal has been lost or is no longer dependable.
Clocking is now being based on the frequency of the last dependable GPS signal detected.
- OFF: The PLL function is disabled. The entire PLL STATUS column is hidden when PLL is disabled.
Nb samples: The number of samples received. This counter increases once
every second.
PHn: The raw phase comparator sample value, an internal parameter of the PLL
used for testing purposes. Deviations in this value are important for tracking and
synchronization.
XLP: The input to a Low Pass filter, representing the phase comparator sample
value derived from PHn. The PLL tries to maintain XLP at 0.
YLP: The output from a Low Pass filter. Its value should fluctuate around 0 with
minimal deviations.
YPI: The output of an integrator, used to determine the operating point of a Digital-to-Analog Converter (DAC), which controls the oscillator of the PLL.
DAC: The actual value being used to control the DAC (from 0 to 65535). This
value should be fairly stable, although slight variations are normal. The typical
operating point is around 38000 when using a TCXO clock.
Steady DAC values of 0 or 65535 may indicate a potential problem, but could
occur temporarily during GPS startup.
Status: Displays very low-level PLL status flags.
Fault: Displays a real-time indication of PLL fault detection, in particular, the
detection of excessive phase comparator slippage.
4.6.4
Viewing the GPS Log

To view the GPS log:
1.
4-14
Memotec Inc.
2.
At the GPS prompt, enter LOG
3.
Select the GPS Entry:

- FAST: (default value) To show the latest sample in the log only. This is a single snapshot of the PLL Status information (see PLL Status on page 4-14).
- LOG: To show several samples in the log. Specify the range using the First
record to display and Last record to display parameters.
DGPS/LOG
example:
showing the
latest sample
only
9230>DGPS
DISPLAY GPS STATUS
GPS (def:STATUS) ? LOG
GPS Entry (def:FAST) ?
--------------------------------------------------------------|
nb_samples |
PHn
|
XLP
|
YLP
|
|
YPI
|
DAC
|
STAT
|
FAULT
|
|---------------+---------------+---------------+---------------|
|
330 |
1.248 |
0.000 |
0.000 |
|
0.000 |
36448 |
0201001D |
NO |
---------------------------------------------------------------
DGPS/LOG
example:
showing
several
samples
9230>DGPS
DISPLAY GPS STATUS
GPS (def:STATUS) ? LOG
GPS Entry (def:FAST) ? LOG
First record to display (0-147483647,def:0) ?
Last record to display (0-147483647,def:0) ? 16
--------------------------------------------------------------|
nb_samples |
PHn
|
XLP
|
YLP
|
|
YPI
|
DAC
|
STAT
|
FAULT
|
|---------------+---------------+---------------+---------------|
|
0 |
2.738 |
0.000 |
0.000 |
|
0.000 |
36448 |
0201001D |
NO |
|
1 |
2.614 |
0.000 |
0.000 |
|
0.000 |
36448 |
0201001D |
NO |
|
2 |
2.427 |
0.000 |
0.000 |
|
0.000 |
36448 |
0201001D |
NO |
|
3 |
2.148 |
0.000 |
0.000 |
|
0.000 |
36448 |
0201001D |
NO |
|
4 |
1.869 |
0.000 |
0.000 |
|
0.000 |
36448 |
0201001D |
NO |
|
5 |
1.621 |
0.000 |
0.000 |
|
0.000 |
36448 |
0201001D |
NO |
|
6 |
1.341 |
0.000 |
0.000 |
|
0.000 |
36448 |
0201001D |
NO |
|
7 |
2.955 |
0.000 |
0.000 |
|
0.000 |
36448 |
0201001D |
NO |
|
8 |
2.583 |
0.000 |
0.000 |
|
0.000 |
36448 |
0201001D |
NO |
---------------------------------------------------------------
Memotec Inc.
4-15
GSM Solution
4.6.5
Viewing the GPS Version

To view the version of the GPS chip:
DGPS/
VERSION
example
1.
2.
At the GPS prompt, enter VERSION.
9230>DGPS
DISPLAY GPS STATUS
GPS (def:STATUS) ? VERSION
GPS version: CW25-TIM 1.79-00.02.00bM
4-16
Memotec Inc.
4.7
4.7.1
Display Counters (DC) Command

GSM Traffic Counters
The GSM traffic counters display information concerning the number of successful and
blocked calls, and the number of frames transmitted for each type of GSM traffic
supported. These counters are displayed with the GSM option of the DC command.
To view the GSM traffic counters:
1.
At the NetPerformer command line prompt, enter the menu sequence: DC SLOT
2.
Enter the Slot number
3.
Enter the Port number or ALL to display all ports in this slot
4.
Enter the Channel Number or ALL to display all channels of this port
5.
Set Display counters set to zero to:

- YES: to display all GSM traffic statistics, even those with a zero value
- NO: to display only those statistics which have a non-zero value.
6.
DC/GSM
example
Select the Traffic direction, either INCOMING or OUTGOING.
SDM-9230-BSC>DC
DISPLAY COUNTERS
Last counter reset : THU
2007/03/08 17:59:33
Item (BOOTP/CHANNEL/CONFIG/DNS/GROUP/GSM/IP/NAT/PORT/PVC/Q922/
Q933/QOS/
REDUNDANCY/SLOT/SNMP/TIMEP,def:BOOTP) ? GSM
GSM> Slot number (1,def:1) ? 1
GSM> Port number (1/2/ALL,def:ALL) ? 1
GSM> Channel Number (101/102/103/104/105/106/ALL,def:ALL) ? 101
GSM> Display counters set to zero (Default value:NO, Current
value:NO) ?
GSM> Traffic direction (INCOMING/OUTGOING,def:INCOMING) ?
GSM> Total number of active calls................24
GSM> Total number of blocked calls...............0
TSSUB
TSSUB
TSSUB
TSSUB
1011>
1011>
1011>
1011>
Uncompressed TRAU frames.............33

Compressed EFR good voice frames.....596656
Compressed EFR good CN frames........103001
TOTAL................................699690
(0%)
(85%)
(15%)
(100%)
TSSUB
TSSUB
TSSUB
TSSUB
1013>
1013>
1013>
1013>

TOTAL................................699690
(0%)
(85%)
(15%)
(100%)
TSSUB 1015> Uncompressed TRAU frames.............33

TSSUB 1015> Compressed EFR good voice frames.....596656
TSSUB 1015> Compressed EFR good CN frames........103001
Memotec Inc.
(0%)
(85%)
(15%)
4-17
GSM Solution
TSSUB 1015> TOTAL................................699690
(100%)
TSSUB
TSSUB
TSSUB
TSSUB
(0%)
(85%)
(15%)
(100%)
NOTE:
4.7.2
1017>
1017>
1017>
1017>

TOTAL................................699959
Transmit and Receive Traffic Counters

The transmit and receive traffic counters for the timeslot subchannels are similar to those
for digital data channels. These counters are displayed with the SLOT option of the DC
command.
To view the transmit and receive traffic counters:
DC/SLOT
example
4-18
1.
At the NetPerformer command line prompt, enter the menu sequence: DC SLOT
2.
3.
Enter the Port number or ALL to display all ports in this slot
4.
Enter the Channel Number or ALL to display all channels of this port
SDM-9230-BSC>DC
DISPLAY COUNTERS
Item (BOOTP/CHANNEL/CONFIG/DNS/GROUP/GSM/IP/NAT/PORT/PVC/Q922/
Q933/QOS/
REDUNDANCY/SLOT/SNMP/TIMEP,def:BOOTP) ? SLOT
Counters (MEAN/PEAK,def:MEAN) ?
SLOT> Port number (1/2/ALL,def:1) ?
SLOT> Channel Number (101/102/103/104/105/106/107/108/109/110/111/
112/113/114/115/116/117/118/119/120/121/122/123/124/125/126/127/
128/129/130/131/ALL,def:ALL) ? 101
TSSUB 1011> Transmitter rate.....................0
% (M)
TSSUB 1011> Receiver rate........................0
% (M)
TSSUB 1011> Remote packet transmission rate......100 % (M)
TSSUB 1011> Number of frames transmitted.........37000147
TSSUB 1011> Number of frames received............37987404
TSSUB 1011> Number of octets transmitted.........19489400
TSSUB 1011> Number of octets received............17520912
...
Memotec Inc.
4.8
Display Errors (DE) Command

Details on timeslot subchannel errors are displayed with the SLOT option of the DE
command.
To view the timeslot subchannel errors:
DE/SLOT
example
1.
At the NetPerformer command line prompt, enter the menu sequence: DE SLOT
2.
3.
Enter the Channel Number or ALL to display all channels on this slot.
SDM-9230-BSC>DE
DISPLAY ERRORS
Item (BOOTP/CHANNEL/DICT/GROUP/NAT/PORT/PVC/Q922/REDUNDANCY/SLOT/
TIMEP,
def:BOOTP) ? SLOT
SLOT> Channel Number (100/101/102/103/104/105/106/ALL,def:ALL) ?
101
TSSUB 1011> Number of bad subchannels............0
TSSUB 1011> Number of unavailable subchannels....0
TSSUB 1011> Number of decode buffer empty errors.0
TSSUB 1011> Number of min frame length errors....0
TSSUB 1011> Number of jitter overflows...........0
TSSUB 1011> Number of jitter underflows..........0
TSSUB 1011> Number of jitter zero length errors..0
TSSUB 1011> Number of jitter_long length errors..0
TSSUB 1011> Number of bad frame type errors......0
TSSUB 1011> No. of bad DSP packet length errors..0
TSSUB 1011> Number of missing frame errors.......0
TSSUB 1011> Number of samples discarded..........0
TSSUB 1011> Number of unexpected seq. numbers....0
TSSUB
TSSUB
TSSUB
TSSUB
TSSUB
TSSUB
TSSUB
TSSUB
TSSUB
TSSUB
TSSUB
TSSUB
TSSUB
...
1013>
1013>
1013>
1013>
1013>
1013>
1013>
1013>
1013>
1013>
1013>
1013>
1013>
Number
Number
Number
Number
Number
Number
Number
Number
Number
No. of
Number
Number
Number
of bad subchannels............0
of unavailable subchannels....0
of decode buffer empty errors.0
of min frame length errors....0
of jitter overflows...........0
of jitter underflows..........0
of jitter zero length errors..0
of jitter_long length errors..0
of bad frame type errors......0
bad DSP packet length errors..0
of missing frame errors.......0
of samples discarded..........0
of unexpected seq. numbers....0
Bad flags: U:Bad LENGTH

A:Abort
Memotec Inc.
Q:Overflow
F:Flush
S:Overrun
B:Bad CRC
4-19
GSM Solution
4.9
Display States (DS) Command

The status information for timeslot subchannels is similar to that for digital data channels,
and includes the Protocol, Speed used in bps, the Modem signals used, and the current
State of the connection. These status indicators are displayed with the SLOT option of the
DS command.
To execute the DS command:
At the NetPerformer command line prompt, enter the menu sequence: DS
SLOT.
DS/SLOT
example
4-20
SDM-9230-BTS>DS
DISPLAY STATES
Item (GLOBAL/PORT/PVC/REDUNDANCY/SLOT,def:GLOBAL) ? SLOT
SLOT> Slot number (1/2/ALL,def:1) ?
111/112/113/114/115/116/117/118/119/ALL,def:ALL) ?
PORT 100> State..................................IN SYNC
PORT 100> Interface..............................E1-TE
TSSUB
TSSUB
TSSUB
TSSUB
1011>
1011>
1011>
1011>
Protocol.............................TCHD
Speed used (bps).....................16000
Modem signals........................STDRCState................................DATA
TSSUB
TSSUB
TSSUB
TSSUB
1012>
1012>
1012>
1012>
Protocol.............................SIG
Speed used (bps).....................16000
Modem signals........................STDRCState................................DATA
Memotec Inc.
4.10 Monitoring Procedures

4.10.1
Monitoring Activation of the Autodetection Function

The NetPerformer Autodetection function for an Abis application is described on
Autodetection of Timeslot Subchannel Traffic Types on page 1-27. Its configuration is
addressed on For an Abis application, set the GSM auto detect mode to: on page 2-8. In
the following example:
The digital link on the BTS side is set to SLAVE mode for the GSM auto detect
mode parameter
The digital link on the BSC side is set to MASTER mode
Autodetection is activated on the first 6 timeslots (Protocol parameter set to
GSM)
The other timeslots are set to OFF.
To verify successful activation of the Autodetection function:
1.
Execute the DTSCH command on the unit on the BSC side.

With Autodetection, all timeslot subchannels are configured in TCHD mode by
default during startup. If the NetPerformer subsequently detects signaling on a
particular timeslot subchannel, it changes the mode to SIG.
BSC>DTSCH
------------------------------ SLOT 1-1 : E1 ---------------------------------|
Current slot=0
All slots=0
|
| # TS| Bit7
Bit6
Bit5
Bit4
Bit3
Bit2
Bit1
Bit0 |
-------------------------------------------------------------------------------|101 1|<-----IDLETR---->|<-----IDLETR---->|<-----IDLETR---->|<-----IDLETR---->|
|102 2|<---------------------------------SIG--------------------------------->|
|103 3|<-----IDLETR---->|<-----IDLETR---->|<-----IDLETR---->|<-----IDLETR---->|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Memotec Inc.
4-21
GSM Solution
2.
Execute the DPORT command on the BSC side to view the timeslot subchannel
configuration.
BSC>DPORT
DISPLAY PORT STATES
-------------------------------------------------------------------------------|PORT# PROTOCOL
INTERFACE SPEED
MODEM
STATE DELAY
|
|
(BPS)
SIGNALS
|
-------------------------------------------------------------------------------|
1 PVCR
DTE-V35
2048k
STDRCDATA 4ms
|
| 1011 TCHD
E1-NT
16000
STDRCDATA
|
| 1013 TCHD
E1-NT
16000
STDRCDATA
|
| 1015 TCHD
E1-NT
16000
STDRCDATA
|
| 1017 TCHD
E1-NT
16000
STDRCDATA
|
| 1021 TCHD
E1-NT
16000
STDRCDATA
|
| 1023 TCHD
E1-NT
16000
STDRCDATA
|
| 1025 TCHD
E1-NT
16000
STDRCDATA
|
| 1027 TCHD
E1-NT
16000
STDRCDATA
|
| 1031 TCHD
E1-NT
16000
STDRCDATA
|
| 1033 TCHD
E1-NT
16000
STDRCDATA
|
| 1035 TCHD
E1-NT
16000
STDRCDATA
|
| 1037 TCHD
E1-NT
16000
STDRCDATA
|
| 1041 TCHD
E1-NT
16000
STDRCDATA
|
| 1043 TCHD
E1-NT
16000
STDRCDATA
|
| 1045 TCHD
E1-NT
16000
STDRCDATA
|
| 1047 TCHD
E1-NT
16000
STDRCDATA
|
|
|
| Modem signals: d(S)r d(T)r (D)cd (R)ts (C)ts r(I) (-)off
|
NOTE:
4-22
When the MASTER link receives the timeslot subchannel configuration from
the DSPs it configures its own timeslot subchannels, and sends a configuration message to the SLAVE link for the timeslot subchannels on the remote
unit. The timeslot subchannels are thus configured identically on both sides of
the connection. They retain these settings until the Autodetection process is
restarted (refer to Autodetection of Timeslot Subchannel Traffic Types on
page 1-27 for restart conditions).
Memotec Inc.
3.
Execute the DTSCH command on the BTS side to confirm successful implementation
of the configuration message from the BSC side.
BTS>DTSCH
------------------------------ SLOT 1-1 : E1 ---------------------------------|
Current slot=0
All slots=0
|
| # TS| Bit7
Bit6
Bit5
Bit4
Bit3
Bit2
Bit1
Bit0 |
-------------------------------------------------------------------------------|101 1|<-----IDLETR---->|<-----IDLETR---->|<-----IDLETR---->|<-----IDLETR---->|
|102 2|<---------------------------------SIG--------------------------------->|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4.
Execute the DPORT command on the BTS side to confirm that its timeslot
subchannel configuration is identical to that on the BSC side.
BTS>DPORT
DISPLAY PORT STATES
-------------------------------------------------------------------------------|PORT# PROTOCOL
INTERFACE SPEED
MODEM
STATE DELAY
|
|
(BPS)
SIGNALS
|
-------------------------------------------------------------------------------|
1 PVCR
DTE-V35
2048k
STDRCDATA 4ms
|
| 1011 TCHD
E1-NT
16000
STDRCDATA
|
| 1013 TCHD
E1-NT
16000
STDRCDATA
|
| 1015 TCHD
E1-NT
16000
STDRCDATA
|
| 1017 TCHD
E1-NT
16000
STDRCDATA
|
| 1021 TCHD
E1-NT
16000
STDRCDATA
|
| 1023 TCHD
E1-NT
16000
STDRCDATA
|
| 1025 TCHD
E1-NT
16000
STDRCDATA
|
| 1027 TCHD
E1-NT
16000
STDRCDATA
|
| 1031 TCHD
E1-NT
16000
STDRCDATA
|
| 1033 TCHD
E1-NT
16000
STDRCDATA
|
| 1035 TCHD
E1-NT
16000
STDRCDATA
|
| 1037 TCHD
E1-NT
16000
STDRCDATA
|
| 1041 TCHD
E1-NT
16000
STDRCDATA
|
| 1043 TCHD
E1-NT
16000
STDRCDATA
|
| 1045 TCHD
E1-NT
16000
STDRCDATA
|
| 1047 TCHD
E1-NT
16000
STDRCDATA
|
|
|
|
Memotec Inc.
4-23
GSM Solution
4.10.2
Monitoring 3G Support Deactivation

NetPerformer 3G support is described on GSM 2/2.5G and 3G Convergence on page 120. Its configuration is addressed on Set Activate 3G support to NO to disable 3G
support and enable the second Ethernet port (default YES) on page 2-12. In the following
example, 3G support is activated on both units (on the BTS and BSC sides). It is
deactivated on the unit on the BSC side, which is accessed using the NetPerformer console
Relay (RE) command from the BTS unit console.
To monitor the effects of deactivating 3G Support:
1.
Execute the RE command to access the remote unit on the BSC side.
BTS>RE
RELAY
Unit name (def:) ? BSC
Press ENTER three times to connect
Press CTRL/Z three times to exit
+SDM-9230 vX.X.X Memotec Inc. (c) 2007
+Signaling Engine vX.X.X Memotec Inc. (c) 2007
+DSP QCxxx.BIZ code version: X.X.X
+Console connected through link relay
+Voice transport method: PowerCell
+GSM license (AAAA-BBBB-CCCCCCCC-DDDD) enabled on this unit
+Display commands, type HE
+BSC>
2.
When 3G support is active on a unit, the second Ethernet port is deactivated. To

confirm this, execute the SE command, select the PORT submenu, and enter ETH2.
+BSC>SE
+SETUP
+Item (BRIDGE/CALLER ID/CLASS/CUSTOM/FILTER/GLOBAL/GSM/HUNT/IP/
IPX/MAP/
+PHONE/PORT/PU/PPPOE/PPPUSER/PVC/REDUNDANCY/SCHEDULE/SLOT/SS7/
USER/VLAN,
+def:BRIDGE) ? PORT
+Port number (ETH1/ETH2/CSL/1,def:ETH1) ? ETH2
+PORT ETH 2> Protocol.............................OFF
4-24
Memotec Inc.
3.
Execute the DPORT command to view the current port and channel configuration for
the unit on the BSC side.
In this example, an ATM channel has been configured on timeslot 151.
+BSC>DPORT
+DISPLAY PORT STATES
-------------------------------------------------------------------------------|PORT# PROTOCOL
INTERFACE SPEED
MODEM
STATE DELAY
|
|
(BPS)
SIGNALS
|
-------------------------------------------------------------------------------|
1 PVCR
DTE-V35
6144k
STDRCDATA 4ms
|
| 151 ATM
E1-TE
64000
ST-RCDOWN
|
| 1011 TCHD
E1-NT
16000
STDRCDATA
|
| 1013 TCHD
E1-NT
16000
STDRCDATA
|
| 1015 TCHD
E1-NT
16000
STDRCDATA
|
| 1017 TCHD
E1-NT
16000
STDRCDATA
|
| 1021 SIG
E1-NT
64000
STDRCDATA
|
| 1031 SIG
E1-NT
64000
STDRCDATA
|
| 1041 SIG
E1-NT
64000
STDRCDATA
|
| 1051 SIG
E1-NT
64000
STDRCDATA
|
| 1061 SIG
E1-NT
64000
STDRCDATA
|
| 1071 SIG
E1-NT
64000
STDRCDATA
|
| 1081 SIG
E1-NT
64000
STDRCDATA
|
| 1091 SIG
E1-NT
64000
STDRCDATA
|
| 1101 SIG
E1-NT
64000
STDRCDATA
|
| 1111 SIG
E1-NT
64000
STDRCDATA
|
| 1121 SIG
E1-NT
64000
STDRCDATA
|
|
|
|
4.
Execute the DPVC command to view the current PVC configuration.

+BSC>DPVC
+DISPLAY PVC STATES
+PVC TYPE (ATM/FR,def:FR) ?
-----------------------------------FR PVC--------------------------------------|PVC MODE
INFO.
SPEED
PORT
DLCI DESTINATION
STATE &
|
|
SIGNALS
(BPS)
NAME
DELAY(MS) |
-------------------------------------------------------------------------------| 1 PVCR
off line
56000
WAN
1 0
CALL
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Information signals: NETwork/USER (N)ew (A)ctive (C)ir (F)ecn (B)ecn (-)off |
5.
Memotec Inc.
Execute the SE command and select the PVC submenu to define an ATMPVCR PVC
on the unit on the BSC side.
4-25
GSM Solution
This is not required for the application, but to show how disabling 3G support affects
the configuration of ATM PVCs.
+BSC>SE
+SETUP
IPX/MAP/
USER/VLAN,
+def:BRIDGE) ? PVC
+PVC number (1-300,def:1) ? 1
+PVC 1> Mode (def:PVCR) ? ?
+CHOICE: OFF
ATMPVCR
ATM-MULTIPLEX ATMPPP
BROADCAST
+
FRF.8
MULTIPLEX
PVCR
RFC1483
RFC1490
+
TRANSP
GSM
+
+PVC 1> Mode (Default value:PVCR, Current value:PVCR) ? ATMPVCR
+PVC 1> VPI address (0-63,def:0) ?
+PVC 1> VCI address (0-1023,def:32) ?
+PVC 1> Service category (def:UBR) ?
...
6.
Execute the SP command to save the configuration.

This step is not required if you execute the RU command.
+BSC>SP
+SAVE PROFILE
+Save Configuration, please confirm (NO/YES,def:NO) ? YES
7.
Execute the SE command and select the GSM submenu to deactivate 3G support.
+BSC>SE
+SETUP
IPX/MAP/
USER/VLAN,
+def:BRIDGE) ? GSM
+GSM> TCH channel management......................PERMANENT
+GSM> Jitter buffer (ms) (4-160,inc:4,def:20) ?
+GSM> Mode used when SIG detected (def:SIG) ?
+GSM> Mode used when TCH detected (def:TCHD) ?
+GSM> Continuous AUTO detection (def:ENABLE) ?
+GSM> Activate 3G support (def:YES) ? NO
+WARNING: This will deactivate all ATM functions and activate the
second
+Ethernet port on this unit.
+Please confirm (NO/YES,def:NO) ? YES
+NOTE: To apply this change, execute the Reset Unit (RU) command.
4-26
Memotec Inc.
8.
Execute the RU command to apply the change to the Activate 3G support parameter.
When the unit restarts, it will no longer support 3G.
+BSC>RU
+RESET UNIT
+Reset unit, please confirm (NO/YES,def:NO) ? YES
+Unit restarted !
+
+Display commands, type HE
9.
Execute the DA command to confirm a successful unit reset.

+BSC>DA
+DISPLAY ALARMS
+Time> TUE
2007/03/06 14:48:00
+Alarm>
LINK 100 IN SYNC
TUE
2007/03/06
14:47:58
+Alarm>
LINK 1 UP (BTS)
TUE
2007/03/06
14:47:57
+Alarm>
SOFT START (RST)
TUE
2007/03/06
14:47:47
+Alarm>
RESET BY USER
TUE
2007/03/06
14:47:20
+Alarm>
LINK 100 IN SYNC
TUE
2007/03/06
13:53:37
+Alarm>
LINK 1 UP (BTS)
TUE
2007/03/06
13:53:35
+Alarm>
LINK 1 DOWN (BTS)
TUE
2007/03/06
13:53:22
+<ENTER> <Esc>
10.
Execute the DJ command to see that all ATM functions have been disabled on this
unit (the last line in this example).
+BSC>DJ
+DISPLAY JOURNAL LOG
+Display full log (NO/YES,def:NO) ?
+
+Time> TUE
2007/03/06 14:48:10
+
+2007/03/06 14:48:01 [tssub 1301] SpeedMask CHANGED FROM: 0x0 TO:
Memotec Inc.
4-27
GSM Solution
0xff
+2007/03/06
+2007/03/06
0xff
+2007/03/06
+2007/03/06
0xff
...
...
+2007/03/06
0xc0
+2007/03/06
+2007/03/06
+2007/03/06
+2007/03/06
...
11.
14:48:01
14:48:01
[tssub 1301] Mode CHANGED FROM: OFF TO SIG

[tssub 1291] SpeedMask CHANGED FROM: 0x0 TO:
14:48:01
14:48:01
[tssub 1291] Mode CHANGED FROM: OFF TO SIG

14:48:00
14:48:00
14:47:59
14:47:52
14:47:52
[tssub 1011] Mode CHANGED FROM: OFF TO TCHD

***********gsm_start_auto_detect_process
***********gsm_start_auto_detect_process
[atmpvc 1] ATM protocol (10) not supported
Execute the SE command and select the PORT submenu. The second Ethernet port is
now available for configuration and LAN/IP connectivity.
+BSC>SE
+SETUP
IPX/MAP/
USER/VLAN,
+def:BRIDGE) ? PORT
+Port number (ETH1/ETH2/CSL/1,def:ETH1) ? ETH2
+PORT ETH 2> Protocol (def:ETH AUTO) ? ?
+CHOICE: OFF
ETH AUTO ETH 802.3 ETH V2
+
+PORT ETH 2> Protocol
+
(Default value:ETH AUTO, Current value:ETH AUTO) ?
...
12.
Execute the SE command and select the PVC submenu to see that the ATMPVCR
PVC has been turned off (Mode changed to OFF), and that ATM PVCs are no longer
offered as possible values for the PVC Mode parameter.
+BSC>SE
+SETUP
IPX/MAP/
USER/VLAN,
+def:BRIDGE) ? PVC
+PVC number (1-300,def:1) ?
+PVC 1> Mode (def:OFF) ? ?
+CHOICE: OFF
BROADCAST MULTIPLEX PVCR
RFC1490
TRANSP
GSM
+
+PVC 1> Mode (Default value:PVCR, Current value:OFF) ?
4-28
Memotec Inc.
13.
Execute the SE command and select the SLOT/CHANNEL submenu to see that the
ATM channel has been turned off (Protocol changed to OFF), and that the value ATM
is no longer available for the Protocol parameter.
+BSC>SE
+SETUP
IPX/MAP/
USER/VLAN,
+def:BRIDGE) ? SLOT
+SLOT> Slot number (1,def:1) ? 1
+Port number (1/2,def:1) ? 2
+Item (LINK/CHANNEL,def:LINK) ? C
+SLOT> Channel Number (151-181/ALL,def:151) ?
+PORT 151> Protocol (def:OFF) ? ?
+CHOICE: OFF
BSC
COP
FR-NET
FR-USER
+
HDLC
HDLCOFR
P-SDLC
PASSTHRU
PASSTHRUOFR
+
PPP
PVCR
R-ASYNC
RSP
S-SDLC
+
T-ASYNC
X25
14.
Execute the DPORT command to see that the ATM channel (timeslot 151) is no
longer listed.
+BSC>DPORT
+DISPLAY PORT STATES
-------------------------------------------------------------------------------|PORT# PROTOCOL
INTERFACE SPEED
MODEM
STATE DELAY
|
|
(BPS)
SIGNALS
|
-------------------------------------------------------------------------------|
1 PVCR
DTE-V35
6144k
STDRCDATA 9ms
|
| 1011 TCHD
E1-NT
16000
STDRCDATA
|
| 1013 TCHD
E1-NT
16000
STDRCDATA
|
| 1015 TCHD
E1-NT
16000
STDRCDATA
|
| 1017 TCHD
E1-NT
16000
STDRCDATA
|
| 1021 SIG
E1-NT
64000
STDRCDATA
|
| 1031 SIG
E1-NT
64000
STDRCDATA
|
| 1041 SIG
E1-NT
64000
STDRCDATA
|
| 1051 SIG
E1-NT
64000
STDRCDATA
|
| 1061 SIG
E1-NT
64000
STDRCDATA
|
| 1071 SIG
E1-NT
64000
STDRCDATA
|
| 1081 SIG
E1-NT
64000
STDRCDATA
|
| 1091 SIG
E1-NT
64000
STDRCDATA
|
| 1101 SIG
E1-NT
64000
STDRCDATA
|
| 1111 SIG
E1-NT
64000
STDRCDATA
|
| 1121 SIG
E1-NT
64000
STDRCDATA
|
| 1131 SIG
E1-NT
64000
STDRCDATA
|
|
|
|
Memotec Inc.
4-29
GSM Solution
4.11 PCM Raw Data Capture

PCM raw data can be captured on a specific timeslot or channel of a DSP, as an option of
the Setup Capture (SC) command. The capture can be executed one channel at a time, or
for all channels of a specific DSP.
Multiple captures of different channels cannot be executed at once. Also, the capture of a
specific timeslot subchannel (TSSUB) is not available.
To capture PCM raw data:
1.
At the NetPerformer command line prompt, enter the menu sequence: SC DSP
2.
Enter the Capture DSP number
3.
Enter the Channel Number
4.
Enter YES at the Capture PCM raw data prompt
5.
Specify the other capture parameters, as required.
Examples
On a unit with the following DSP allocation:

BTS>DDSP
DISPLAY DSP ALLOCATION
DSP CH1 CH2 CH3 CH4 CH5 CH6 CH7 CH8 CH9 CH10
1 101 102 103 104 105 106
2 107 108 109 110 111 112
3
Enter the following to capture the PCM raw data on a single channel, in this case, channel
102:
BTS>SC
SETUP CAPTURE
Capture ITEM (DSP/PORT/PU/PVC/SE/SLOT/SPECIAL/SVC,def:DSP) ?
Capture DSP number (1/2/3/ALL,def:ALL) ? 1
112/113/114/115/116/117/118/119/120/121/122/123/124/125/126/127/
128/129/130/131/151/ALL,def:ALL) ? 102
Capture DSP Pings (NO/YES,def:NO) ?
Capture DSP Data (NO/YES,def:YES) ?
Capture DSP non-data (NO/YES,def:YES) ?
Capture PCM raw data (NO/YES,def:NO) ? YES
Capture activation (def:FOREGROUND) ?
Enter the following to capture the PCM raw data of all channels on DSP 2 (channels 107
to 112):
4-30
Memotec Inc.
BTS>SC
SETUP CAPTURE
Capture ITEM (DSP/PORT/PU/PVC/SE/SLOT/SPECIAL/SVC,def:DSP) ?
Capture DSP number (1/2/3/ALL,def:1) ? 2
112/113/114/115/116/117/118/119/120/121/122/123/124/125/126/127/
128/129/130/131/151/ALL,def:102) ? ALL
Capture DSP Pings (NO/YES,def:NO) ?
Capture DSP Data (NO/YES,def:YES) ?
Capture DSP non-data (NO/YES,def:YES) ?
Capture PCM raw data (NO/YES,def:NO) ? YES
Capture activation (def:FOREGROUND) ?
Using the View Capture (VC) command, the PCM raw data is identified by 0x1040 and
0x1041 packets (DSP COMMAND), where 0x1040 indicates data received on the PCM
and 0x1041 indicates data sent to the PCM.
Memotec Inc.
4-31
GSM Solution
4.12 Error Log

To activate the collection of special error counters in an Error Log, activate the
ELOGCOUNTERS extended global parameter:
EP GLOBAL ELOGCOUNTERS YES
The Error Log and ELOG command are intended for the use of NetPerformer Technical
Support personnel only. This section provides information about recent improvements to
these debugging tools.
For improved troubleshooting of GSM applications, the size of the ELOG has
been increased from 512 to 5120 entries
GSM autodetection switching is now indicated in the ELOG
New error counters have been added to the ELOG:
- PVC Sorter Timeout: 0x900
- UDP invalid checksum: 0x901
- Jitter Underflow: 0x902
- Jitter Overflow: 0x903
- Missing frame errors: 0x904
- Unexpected seq. numbers: 0x905
Example
An example of the ELOG entry for jitter overflows is:

2007/08/31-16:40:58 DSP 2:5 CHANNEL 106/5 ERROR 0x903
4-32
Memotec Inc.
5
Concepts and Terminology
Memotec Inc.
5-1
GSM Solution
5.1
About GSM
The Global System for Mobile communications (GSM) provides a worldwide standard
for digital cellular communications systems. Designed to be compatible with ISDN
services, GSM describes the functionality and interface for all system components, and
proposes system design standards which guarantee proper interworking between those
components.
The GSM standard includes directives concerning:
Bandwidth efficiency
Roaming across international borders
Quality of Service (QoS)
Cost efficiency
Compatibility, scalability and adaptability to new communications services.
In recent years, the GSM system has expanded from its European base to acceptance in
over 80 countries around the world. It can be used with either E1 or T1 digital networks,
depending on the location and network architecture.
5.2
Mobile Cellular Systems

A mobile cellular system is based on a cellular division of a geographic operating area, or
operator.
A cell corresponds to the area covered by a single transmitter or a set of transmitters
The size of a cell is determined by the power of its transmitters
Several groups of cells, or clusters, comprise the covering area of an operator
All available radio channels in the frequency band are distributed over each cluster, and this distribution is repeated from one cluster to the next.
5.2.1
Transmitter Frequencies
Mobile cellular systems require low-power transmitters to allow the available frequencies
to be reused in an efficient way.
Reuse of frequencies increases the number of users that can access the cellular
system at one time
Frequencies used in one cell are reused in another, which must be far enough
away to avoid interference
If a transmitter is too powerful, its frequencies cannot be reused beyond the range
of that transmitter
Neighboring cells cannot use the same radio channels
5-2
Memotec Inc.
Some channels must also be reserved for carrying signaling and administrative
information.
5.2.2
Types of Cells
Several types of cells are available to the mobile cellular system:
Macrocell: A large cell that is ideal for areas with low population density.
Microcell: A small cell for highly populated areas. With smaller cells more channels become available more quickly, providing greater overall capacity.
Since microcells are spaced closely together, their transmitters must maintain a
lower level of power than those used in macrocells, to avoid interference between
neighboring cells.
Umbrella cell: A cell that includes several microcells, used to reduce the number
of handovers when the travelling speed of the mobile user is high.
When a mobile connection is handed off to an umbrella cell it can stay longer in
the same cell, since the power level of the umbrella cell is greater than that of the
microcell.
Selective cell: A cell that does not have a 360-degree range of transmission, for
more efficient use of frequencies in places where full coverage is not required.
For example, a selective cell with a 140-degree range may be sufficient near the
entrance to a tunnel.
5.2.3
Cells per Cluster

As mentioned earlier, cells are grouped into clusters. The number of cells in each cluster
must be calculated to allow the same cluster structure to be repeated continuously across
the entire covering area of an operator. There is a trade-off here between system capacity
and frequency interference:
The lower the number of cells per cluster, the higher the number of channels per
cell and the greater its capacity
The greater the capacity of a cell, the more likely interference will occur between
neighboring clusters.
Therefore, clusters must not be designed to be too small. Usually a cluster contains 4, 7, 12
or 21 cells, depending on system capacity requirements.
Memotec Inc.
5-3
GSM Solution
5.3
GSM Network Architecture

The GSM network is composed of:
Mobile Station (MS)
Base Station Subsystem (BSS)
Network and Switching Subsystem (NSS)
Operation and Support Subsystem (OSS).
These high-level network elements are in turn composed of the basic network elements
illustrated in Figure 5-5-1, and others described in the following sections. For an
impression of the GSM network with NetPerformer.
Figure 5-1: GSM Network Components
5-4
Memotec Inc.
5.3.1
Mobile Station (MS)

The Mobile Station consists of the mobile terminal and the Subscriber Identity Module
(SIM).
Terminal
Different types of terminals with varying output power are available:
Terminal type
Typical installation
Max. output power
Fixed
Vehicles
20W
GSM portable
Vehicles
8W
Handheld
No fixed installation
0.8W
Table 5-1: Terminal types
Subscriber Identity Module (SIM)

The SIM is a smart card that identifies the terminal and allows the user to access all
subscribed services.
A terminal cannot function if a SIM is not installed
The SIM can be moved from one terminal to another
Protected by a four-digit Personal Identification Number (PIN)
Includes parameters that identify the user to the GSM system, e.g. the International Mobile Subscriber Identity (IMSI).
5.3.2
Base Station Subsystem (BSS)

The BSS connects the MS to the Network and Switching Subsystem (NSS). It handles
transmission and reception of mobile cellular traffic, and includes:
Base Transceiver Station (BTS), also called the base station
Base Station Controller (BSC).
Base Transceiver Station (BTS)

The BTS includes all transceivers and antennas that are used in a single cell of the
network.
Usually placed in the center of the cell
Its transmitting power defines the size of the cell
May have between 1 and 16 transceivers, depending on the density of users in the
cell.
Memotec Inc.
5-5
GSM Solution
Base Station Controller (BSC)

The BSC controls a group of BTSs. It manages radio resources, handovers, frequency
hopping, exchange functions and radio frequency power levels. The Transcoder Rate
Adapter Unit (TRAU), which compresses the voice channels, is located in front of the
BSC.
NOTE:
5.3.3
To reduce bandwidth requirements, the NetPerformer can be installed

between the BSC and the BTS. Refer to Using NetPerformer on the GSM
Abis Interface on page 1-10.
Network and Switching Subsystem (NSS)

The NSS manages the following:
Communications between mobile users within the GSM network
Connections to outside networks, such as ISDN and PSTN
Subscriber information and mobility.
The NSS includes several sub-components, described below.
Mobile Switching Center (MSC)

The MSC performs switching functions in the GSM network, and provides
interconnection to other networks. It is the central component of the NSS.
To reduce bandwidth requirements, the NetPerformer can be installed between the
MSC and the BSC, or between the MSC and the PSTN. Refer to Using NetPerformer
on the GSM A/E Interface on page 1-7 and Using NetPerformer on the GSM Ater
Interface on page 1-16.
Gateway Mobile Switching Center (GMSC)

The GMSC provides the interface between the mobile cellular network and the PSTN, and
routes calls from the fixed network to a GSM user. The GMSC is able to determine which
HLR corresponds to a particular number, and can access routing information from the
subscribers current VLR via that HLR.
Home Location Register (HLR)

The HLR is a database of subscribers that belong to the MSC, including their current
location and the services to which they have access.
The subscriber location corresponds to the SS7 address of the Visitor Location Register
(VLR) associated with the terminal.
5-6
Memotec Inc.
Visitor Location Register (VLR)

The VLR contains information from a subscriber's HLR for providing the subscribed
services to visiting users. When a subscriber enters the covering area of a new MSC, the
VLR that is associated with this MSC will request information from the HLR about the
new subscriber. This ensures that the desired services can be provided without having to
re-establish communication parameters.
The VLR is always implemented together with an MSC and as such, the MSC area is itself
under the control of the VLR.
Authentication Center (AuC)

The AuC is a register that provides the information needed for encryption purposes and for
authentication of the user's identity.
Equipment Identity Register (EIR)

The EIR is a register of all valid terminals, identified by their International Mobile
Equipment Identity (IMEI). The EIR can block calls from a stolen or unauthorized
terminal, and from a terminal that does not respect the maximum permitted output power.
GSM Interworking Unit (GIWU)

The GIWU provides an interface to various external networks for transmission of both
voice and data.
5.3.4
Operation and Support Subsystem (OSS)

The OSS controls and monitors the GSM system, and is connected to the various
components of the NSS and the BSC. When required, it controls the traffic load of the
BSS.
Some system maintenance tasks can be transferred to the BTS to reduce costs.
Memotec Inc.
5-7
GSM Solution
5.4
GSM Network Functions

GSM handles the following network functions:
Transmission
Radio Resources (RR)
Mobility Management (MM)
Communication Management (CM)
Operation and Maintenance (O&M, also referred to as OA&M).
5.4.1
Transmission
The transmission function deals with the transmission of both user information and
signaling information. Some components of the GSM network are directly involved with
transmission, such as the MS, BTS and BSC. Other components require transmission of
signaling information only, such as the HLR, VLR and EIR registers.
5.4.2
Radio Resources (RR)

The RR function establishes, sustains and tears down the channels that are required
between an MS and the MSC. The components that are directly involved with RR are the
MS and the BSC. Control of handovers by the MSC is also involved.
The RR also manages the frequency spectrum and monitors how the network reacts to
changing radio environment conditions. This includes control of power levels, frequency
hopping, and the continuity of transmission and reception.
5.4.3
Mobility Management (MM)

The MM function deals with procedures that concern user mobility, including location
management, authentication and security (encryption, equipment identity and user
confidentiality).
5.4.4
Communication Management (CM)

The CM function is responsible for managing:
Call control (CC): call routing, establishment, maintenance and tear-down
Supplementary Services (SS): the supplementary services to which the subscriber has access
Short Message Services (SMS): available through contact with a Short Message
Service Center.
5-8
Memotec Inc.
5.4.5
Operation and Maintenance (O&M)

The O&M function allows the operator to configure and monitor the system. The OSS is
directly involved with O&M. The BSS and NSS also participate, in that they are a source
of system information and include certain test functions. BSC monitoring of the BTSs is
also subsumed under O&M.
Memotec Inc.
5-9
GSM Solution
5.5
GSM Radio Interface

The GSM radio interface carries traffic between the MS and the rest of the GSM network,
which comprises equipment of many different types, models and manufacturers. It is
crucial to transmission efficiency, system capacity, prevention of interference and the
reuse of radio frequencies.
The GSM radio interface has been allocated two frequency bands of 25 MHz each:
Uplink transmissions: Frequency band from 890 to 915 MHz, for transmissions
from the MS to the BTS
Downlink transmissions: Frequency band from 935 to 960 MHz, for transmissions from the BTS to the MS.
These frequency bands are limited in some countries due to legacy analog systems and military communications systems that encroach upon the permitted
GSM frequency range.
5.5.1
Access Schemes
GSM uses a multiple access scheme that includes:
Frequency Division Multiple Access (FDMA)
Time Division Multiple Access (TDMA), which operates from within FDMA
Frequency hopping.
Frequency Division Multiple Access (FDMA)

Under FDMA:
Each user is provided with a particular frequency
More frequencies must be made available as the user base grows
The number of users is limited by this constraint.
Time Division Multiple Access (TDMA)

Several users can share the same frequency
The frequency band of 25 MHz is divided into 124 carrier frequencies of 200
KHz each, with an initial carrier frequency provided as a buffer between GSM
and other services operating at lower frequencies
Each carrier frequency is divided into TDMA frames, which are composed of 8
bursts each
Each user is provided with a particular burst.
Slow Frequency Hopping

Slow frequency hopping changes the frequency with every TDMA frame. Frequency
5-10
Memotec Inc.
hopping reduces the effects of interference between channels, and helps preserve overall
voice quality.
Various frequency hopping algorithms have been constructed. Notification of the selected
algorithm is sent from the BTS to the MS via the Broadcast Control Channels (explained
in the next section). All MSs support frequency hopping, although some types of BTSs
may not.
5.5.2
GSM Channels
Under GSM, a channel is based on the recurrence of one burst in every TDMA frame.
Each channel is defined according to the position of the burst within the frame as well as
the frequency of the frame. Two types of channels are used:
Traffic channels (TCH): for transporting voice and data
Control channels: for network management and channel maintenance.
Traffic Channels (TCH)

Traffic channels use a 26-multiframe structure, and may be:
Full-rate channel (TCH/F):
- Uses 24 TDMA frames for traffic, one frame for the Slow Associated Control
Channel (SACCH), and one idle frame for monitoring purposes
- Downlink and uplink channels are separated by 3 bursts, so the MS does not
need to transmit and receive simultaneously
- Fixed length of 320 bits (40 bytes)
- 16 Kbps rate (20 ms per frame)
Half-rate channel (TCH/H): Uses a different internal structure that doubles the
system capacity:
- Fixed length of 160 bits (20 bytes)
- 8 Kbps rate (20 ms per frame)
NOTE:
Although frame length is fixed, not all bits are used, as there are periods of
inactivity.
Control Channels
Control channels include:
Broadcast channels (BCH): Used by the BTS to provide the MS with synchronization information. There are three types of BCHs:
- Broadcast Control Channel (BCCH): Provides the MS with information
concerning identification and access to the network
Memotec Inc.
5-11
GSM Solution
- Synchronization Channel (SCH): Provides the MS with the training

sequence required to demodulate information from the BTS
- Frequency-Correction Channel (FCCH): Provides the MS with a frequency reference for synchronization with the network.
Common Control Channels (CCCH): Used to establish calls from the MS or
the network. There are three types of CCCHs:
- Paging Channel (PCH): Notifies the MS of an incoming call
- Random Access Channel (RACH): Used by the MS to request access to the
network
- Access Grant Channel (AGCH): Used by the BTS to acknowledge a RACH
from the MS, and tell it which channel it should use.
Dedicated Control Channels (DCCH): Used for exchanging messages between
MSs, or between an MS and the network. There are two types of DCCHs:
- Standalone Dedicated Control Channel (SDCCH): Exchanges signaling
information on the downlink and uplink
- Slow Associated Control Channel (SACCH): Used for channel maintenance and control.
Associated Control Channels: Take over all or part of a traffic channel for
transmission of urgent signaling information, when required.
5-12
Memotec Inc.
5.6
List of Acronyms
AGCH
Access Grant Channel
AuC
Authentication Center
BCCH
Broadcast Control Channel
BCH
Broadcast Channel
BSC
Base Station Controller
BSS
Base Station Subsystem
BTS
Base Transceiver Station
CC
CCCH
CM
DCCH
EIR
FACCH
Call Control
Common Control Channel
Communication Management
Dedicated Control Channel
Equipment Identity Register
Fast Associated Control Channel
FCCH
Frequency-Correction Channel
FDMA
Frequency Division Multiple Access
GIWU
GSM Interworking Unit
GPRS
General Packet Radio Service
GSM
GMSC
HLR
Global System for Mobile communications

Gateway Mobile Switching Center
Home Location Register
IMEI
International Mobile Equipment Identity
IMSI
International Mobile Subscriber Identity
MM
Mobility Management
MS
Mobile Station
Memotec Inc.
5-13
GSM Solution
MSC
Mobile Switching Center
NSS
Network and Switching Subsystem
O&M
OSS
Operation and Support Subsystem
PCH
Paging Channel
RACH
RNC
RR
SACCH
SCH
SDCCH
Random Access Channel

Radio Network Controller
Radio Resources management
Slow Associated Control Channel
Synchronization Channel
Standalone Dedicated Control Channel
SIM
Subscriber Identity Module
SMS
Short Message Services
SS
Supplementary Services
TCH
5-14
Operation and Maintenance
Traffic Channel
TCHD
Traffic Channel: Dual rate
TCH/F
Traffic Channel: Full rate
TCH/H
Traffic Channel: Half rate
TCHU
Traffic Channel: Uncompressed
TDMA
Time Division Multiple Access
TRAU
Transcoder Rate Adapter Unit
TRX
Transceiver Timeslot
VLR
Visitor Location Register
Memotec Inc.
6
SE/GSM Configuration Parameters
Memotec Inc.
6-1
GSM Solution
6.1
Jitter buffer (ms)

Console
Jitter buffer (ms)
SNMP
gsmJitterBuffer
Text-based Config
[gsm] JitterBuffer
The amount of jitter delay, in milliseconds, that the NetPerformer uses to compensate for a
variation in network delay, which can produce variable arrival time of packets on a voice/
fax connection.
If packets arrive at inconsistent intervals, voice quality may be choppy. When the Jitter
buffer parameter is set to higher values, the end-to-end delay increases, but voice quality
remains smooth. Lower values decrease end-to-end delay, but may produce choppy voice
quality.
To view the current jitter level occurring on each timeslot subchannel, execute the Display
Jitter Level (DJL) command (see Display Jitter Level (DJL) Command on page 4-10).
6.2
Values:
4 - 160, in increments of 4
Default:
20
Mode used when SIG detected

Console
Mode used when SIG

detected
SNMP
gsmModeDetectSig
Text-based Config
[gsm] ModeDetectSig
Selects the GSM traffic mode to be used when the NetPerformer Autodetection function
detects signaling information in the GSM Abis traffic (a SIG channel):
TCHU: Uncompressed traffic channel. Carries voice or data, but the frames are
never optimized. This can be useful for transmitting GPRS traffic in a satellite
application.
SIG: Signaling channel
OFF: The channel is not used.
6.3
Values:
OFF, SIG, TCHU
Default:
SIG
Mode used when TCH detected

Console
Mode used when TCH

detected
6-2
SNMP
gsmModeDetectTch
Text-based Config
[gsm] ModeDetectTch
Memotec Inc.
Selects the GSM traffic mode to be used when the NetPerformer Autodetection function
detects voice or data in the GSM Abis traffic (a TCH channel):
application.
TCHD: Dual rate traffic channel for voice or data. In this mode, the subchannel is
configured at 16 Kbps, and can process a single traffic stream at 16 Kbps or two
traffic streams at 8 Kbps each. See Dual Rate Traffic Channels on page 1-14
for an example.
SIG: Signaling channel (used in a GSM Abis application only)
OFF: The channel is not used.
6.4
Values:
OFF, SIG, TCHU, TCHD
Default:
TCHD
Continuous AUTO detection

Console
SNMP
Continuous AUTO detec- gsmContinuousAutotion

Detect
Text-based Config
[gsm] ContinuousAutoDetect
Determines whether the NetPerformer will restart the autodetection process on an Abis
timeslot subchannel when its traffic type changes.
ENABLE: The unit will revise the settings that have been detected and configured on a timeslot subchannel when its traffic type changes.
DISABLE: The initial settings that have been detected and configured on all
timeslot subchannels will remain unchanged until the Autodetection function
restarts. A restart occurs when:
- The unit is powered up
- The link goes down (loss of SYNC on the interface)
- The link is activated (enabled through the LINK configuration).
Example:
Continuous AUTO detection is set to ENABLE

A TCH channel is detected and configured on a timeslot subchannel through the
Autodetection process
The traffic received on this timeslot subchannel switches to signaling information
The DSP advises the host of the mismatched traffic
The detection process is restarted on this timeslot subchannel
Memotec Inc.
6-3
GSM Solution
The timeslot subchannel is reconfigured as a SIG channel.
6.5
Values:
ENABLE, DISABLE
Default:
ENABLE
Activate 3G support
Console
Activate 3G support
SNMP
gsm3GEnable
Text-based Config
[gsm] 3GEnable
Determines whether the unit will support a 3G application, which requires ATM
functionality.
When ATM is activated, the second Ethernet port on the unit is not available.
YES: The unit supports 3G. All ATM functions are activated and the second
Ethernet port on this unit is deactivated. This is the default setting when the
GSM license is activated.
NO: The unit does not support 3G. All ATM functions are deactivated. The second Ethernet port on this unit is available for LAN/IP connectivity.
You must confirm a change in value for this parameter. Enter YES at the console prompt.
It also requires that you reset the unit. Execute the Reset Unit (RU) command.
Examples:
Deactivation of 3G support and ATM functions:

...
GSM> Activate 3G support (def:YES) ? NO
WARNING: This will deactivate all ATM functions and activate the
second
Ethernet port on this unit.
Please confirm (NO/YES,def:NO) ? YES
NOTE: To apply this change, execute the Reset Unit (RU) command.
Reactivation of 3G support and ATM functions:

GSM> Activate 3G support (def:NO) ? YES
WARNING: This will activate all ATM functions and deactivate the
second
Ethernet port on this unit.
Please confirm (NO/YES,def:NO) ? YES
NOTE: To apply this change, execute the Reset Unit (RU) command.
To monitor the deactivation and reactivation of 3G support, follow the procedures

provided on Monitoring 3G Support Deactivation on page 4-24.
6-4
Memotec Inc.
6.6
Values:
NO, YES
Default:
YES
Call management timeout (s)

Console
SNMP
Call management timeout gsmCallMgmtTimeout

(s)
Text-based Config
[gsm] CallMgmtTimeout
Determines the duration, in seconds, before Call Blocking is activated. If no START or

STOP message has been received for this duration, calls are rejected on the basis of the
GSM maximum calls parameter defined on the GSM PVC (see GSM maximum calls on
page 8-5).
The default value, 0, means that the timer is deactivated, and no START or STOP
commands are cancelled or reevaluated. Other values are in 5-second increments. The
value 5 is not recommended if the delay between the START/STOP messages is also 5
seconds.
Memotec Inc.
Values:
Default:
6-5
GSM Solution
6-6
Memotec Inc.
7
SE/SLOT/#/CHANNEL Configuration
Parameters
NOTE:
Memotec Inc.
Configuration parameters for an SS7 channel, used in a GSM A, E or Ater

application, are addressed in the Digital Data module of this document
series. The parameters listed below are for the logical channels of a GSM
Abis or Ater application.
7-1
GSM Solution
7.1
Channel Number
Console
Channel Number
SNMP
ifwanEntry, ifwanIndex
Text-based Config
[ifwan #]
Determines which logical channel of the T1 or E1 physical interface will be used to carry
GSM Abis traffic. All timeslot subchannels of this logical channel can be defined for
transmission of voice/data, signaling information or operation and maintenance
information.
Enter the three-digit channel number, or enter ALL to configure all channels on this digital
interface at once.
Values:
T1 interface card: x01-x24, ALL

E1 interface card: x01 - x31, ALL
where: x is the slot number
Default:
7.2
the lowest numbered unconfigured channel on this digital

interface
Protocol
Console
Protocol
SNMP
ifwanProtocol
Text-based Config
[ifwan #] Protocol
Determines the protocol to be used on this logical channel. The Protocol must be set to
GSM for an Abis application. Another logical channel on the remote NetPerformer unit
must also be set to GSM.
7.3
Values:
OFF, ACELP-CN, D&I, FR-NET, FR-USER, G723, G726 16K,

G726 24K, G726 32K, G726 40K, G729, G729A, GSM,
HDLC, MELP, PASSTHRU, PASSTHRUOFR, PCM64K, PPP,
PVCR, SS7, SS7MTP2, SS7MTP2 ISUP-A, SS7 ISUP-A,
TRANSPARENT
Default:
OFF
Timeslot
Console
Timeslot
SNMP
ifwanTimeslot
Text-based Config
[ifwan #] Timeslot
Determines which timeslot will be assigned to this channel.
7-2
Memotec Inc.
SE/SLOT/#/CHANNEL Configuration Parameters
NOTE:
Values:
Only one Timeslot can be selected per channel. For a GSM channel, the Number of consecutive timeslots is a read-only parameter.
T1 interface card: 1 - 24
E1 interface card: 1- 31
Default:
7.4
the lowest numbered unconfigured timeslot on this digital

interface
Location on the GSM network

Console
SNMP
Location on the GSM net- ifwanGsmLocation

work
Text-based Config
[ifwan #] GsmLocation
Determines whether the NetPerformer unit is on the hub or remote side of the GSM
network, and whether this channel supports GSM Abis or Ater traffic. Set this parameter
to:
BTS ABIS: To support Abis traffic at a remote site, where the channel is connected to the base transceiver station via the digital E1/T1 link
BSC ABIS: To support Abis traffic at the hub site, where the channel is connected to the base station controller via the digital link
BSC ATER: To support Ater traffic at a remote site, where the channel is connected to the base station controller via the digital link
MSC ATER: To support Ater traffic at the hub site, where the channel is connected to the TRAU in front of the MSC via the digital link.
7.5
Values:
BTS ABIS, BSC ABIS, BSC ATER, MSC ATER
Default:
BTS ABIS
Vendor of the GSM units

Console
Vendor of the GSM units
SNMP
ifwanGsmVendorId
Text-based Config
[ifwan #] GsmVendorId
Specifies the vendor of the GSM units that the NetPerformer communicates with in this
application. The NetPerformer can fine-tune its operations automatically based on the
value of this parameter.
Memotec Inc.
7-3
GSM Solution
NOTE:
If your GSM vendor is not listed, select the value ANY.
Values:
ANY, ALCATEL, ERICSSON, HUAWEI, MOTOROLA, NORTEL, NOKIA, SIEMENS, ZTE
Default:
ANY
The parameters for all timeslot subchannels (TSSUB) are presented next. The prefix
for each parameter indicates which subchannel is being configured, in the format TSSUB
xxxy, where:
xxx is the Channel Number
y is the subchannel number.
For example, TSSUB 1011 represents channel (or timeslot) 101 and
subchannel 1.
NOTE:
7.6
The NetPerformer will continue to prompt you for subchannel configuration

information as long as the timeslot can handle another subchannel (a least one
bit of the 64-Kbps timeslot is still available). A maximum of 8 subchannels
are available per timeslot, e.g. TSSUB 1011 to TSSUB 1018. For each
parameter, a different SNMP variable corresponds to each subchannel
configured.
TS subchannel mode
Console
TS subchannel mode
SNMP
ifwanTssubMode1
ifwanTssubMode2
ifwanTssubMode3
ifwanTssubMode4
ifwanTssubMode5
ifwanTssubMode6
ifwanTssubMode7
ifwanTssubMode8
Text-based Config
[tssub #] Mode
Determines what kind of GSM Abis traffic this timeslot subchannel will carry:
application
7-4
Memotec Inc.
TCHD: Dual rate traffic channel for voice or data. In this mode, the subchannel is
configured at 16 Kbps, and can process a single traffic stream at 16 Kbps or two
traffic streams at 8 Kbps each. See Dual Rate Traffic Channels on page 1-14
for an example
SIG: Signaling channel
OFF: The timeslot subchannel is not used.
NOTE:
7.7
The TS subchannel mode parameter is not displayed when Autodetection is in

effect (digital link GSM auto detect mode set to MASTER or SLAVE in an
Abis application).
Values:
OFF, SIG, TCHU, TCHD
Default:
OFF

Console
SNMP
ifwanTssubSpeedMask1
Text-based Config
[tssub #] SpeedMask
Determines which burst(s) of the TDMA frame are handled by this timeslot subchannel
(refer to Time Division Multiple Access (TDMA) on page 5-10).
Set the Subchannel speed mask to a hexadecimal value representing the bit allocation for
this timeslot subchannel (00 to FF).
All bits set to 1 must be contiguous
No Subchannel speed mask value can overlap the mask configured for another
timeslot subchannel
Subchannels of a single timeslot can be configured at different speeds, e.g. 4 8Kbps subchannels with 2 16-Kbps subchannels
The timeslot does not have to be fully configured. Enter 00 for an idle timeslot
subchannel.
Examples:
Memotec Inc.
7-5
GSM Solution
Divide the timeslot into 8 8-Kbps subchannels by entering Subchannel speed

masks 01, 02, 04, 08, 10, 20, 40 and 80 for the 8 timeslot subchannels that are
presented at the console for configuration
masks C0, 30, 0C and 03 for the 4 timeslot subchannels that are presented at the
console
masks FC, 7E and 3F for the 3 timeslot subchannels that are presented at the console
masks F0 and 0F for the 2 timeslot subchannels that are presented at the console
Divide the timeslot into a single 64-Kbps subchannel by entering a Subchannel
speed mask value of FF. In this case only 1 timeslot subchannel is presented at the
console for configuration.
The NetPerformer issues a warning at the console if an improper Subchannel speed mask
value is entered. Typical problems are:
One or more bits of the Subchannel speed mask are already used by another
timeslot subchannel:
WARNING!: Invalid subchannel speed mask: bits conflict TS=0b00111111
mask=0b00001100
Invalid Subchannel speed mask value:

WARNING!: Invalid subchannel speed mask 0b11111110: valid speed
(8K(1bit),16K(2bits),32K(4bits),48K(6bits) or 64K(8bits))
The Subchannel speed mask value has non-contiguous bits set to 1:

WARNING!: Invalid subchannel speed mask 0b10000001: not contiguous bits
NOTE:
7-6
The Subchannel speed mask parameter is not displayed when Autodetection is

in effect (digital link GSM auto detect mode set to MASTER or SLAVE in an
Abis application).
Values:
00 - FF
Default:
00
Memotec Inc.
7.8
Idle code
Console
Idle code
SNMP
ifwanTssubIdleCode1
ifwanTssubIdleCode2
ifwanTssubIdleCode3
ifwanTssubIdleCode4
ifwanTssubIdleCode5
ifwanTssubIdleCode6
ifwanTssubIdleCode7
ifwanTssubIdleCode8
Text-based Config
[tssub #] IdleCode
For SIG TS subchannel mode only
Determines the Idle code that the NetPerformer will send automatically during periods
when no traffic is sent across the timeslot subchannel. Enter a hexadecimal value from 00
to FF.
NOTE:
7.9
The Idle code parameter is not displayed when Autodetection is in effect (digital link GSM auto detect mode set to MASTER or SLAVE in an Abis application).
Values:
00 - FF
Default:
7E
Remote unit
Console
Remote unit
SNMP
ifwanRemoteUnit
Text-based Config
[ifwan #] RemoteUnit
The remote NetPerformer to which traffic from this channel will be directed. This
parameter must be defined for PowerCell transport to work. Enter the Unit name of the
remote unit.
NOTE:
Memotec Inc.
The Unit name is defined on the remote unit using the SETUP/GLOBAL submenu. Refer to the chapter Global Functions in the Quick Configuration
7-7
GSM Solution
Values:
Maximum 16-character string, determined by remote NetPerformer setup: A-Z, 0-9, . (period), , (comma (space), (hyphen)
Default:
none
7.10 Remote port number

Console
Remote port number
SNMP
ifwanRemotePort
Text-based Config
[ifwan #] RemotePort
The remote channel to which traffic from the local channel is sent.
NOTE:
7-8
The remote channel must be set to the GSM protocol.
Values:
1 - 65534
Default:
the local channel number
Memotec Inc.
8
SE/PVC/#/GSM Configuration Parameters
NOTE:
Memotec Inc.
The following parameters are common to other PVC modes, and are detailed
in the appendix SE/PVC Configuration Parameters of the WAN/Frame
Relay module of this document series: Mode, Port, DLCI address, Committed
Information rate. Also note that the Port parameter must be set to 0 for configuration of PVCR over IP parameters (for a TDMoIP application).
8-1
GSM Solution
8.1
GSM traffic type

Console
GSM traffic type
SNMP
pvcGsmTrafficType
Text-based Config
[frpvc#] GsmTrafficType
Defines whether GSM traffic will be carried over this PVC. Select TCH for both TCHD
(voice/fax/data) and signaling traffic. Select NONE to prevent traffic from passing over
this PVC.
8.2
Values:
NONE, TCH
Default:
NONE
Frame over IP, source

Console
Frame over IP, source
SNMP
pvcIpSrcAddress
Text-based Config
[frpvc#] IpSrcAddress
IP address of the source of traffic over this PVC. If left at its default value,
000.000.000.000, the NetPerformer uses the IP address of the port that sends the frames
over the IP network.
NOTE:
8.3
This parameter appears only if the PVC Port parameter is set to 0 (indicating
Frame over IP support).
Values:
000.000.000.000 - 255.255.255.255
Default:
000.000.000.000
Frame over IP, destination

Console
Frame over IP, destination
SNMP
pvcIpDestAddress
Text-based Config
[frpvc#] IpDestAddress
IP address of the remote unit that receives traffic from this PVC. The default value,
000.000.000.000, leaves the destination undefined; no traffic can be transported over the
Internet.
NOTE:
8-2
Memotec Inc.
8.4
Values:
000.000.000.000 - 255.255.255.255
Default:
000.000.000.000
Frame over IP, port number

Console
SNMP
Frame over IP, port num- pvcIpPort

ber
Text-based Config
[frpvc#] IpPort
IP address of the source UDP port that transmits the frames over IP. This parameter can be
used to allow transmission across a firewall.
NOTE:
8.5
Values:
1-65535
Default:
1024
Frame over IP, DSCP

Console
Frame over IP, DSCP
SNMP
pvcIpDscp
Text-based Config
[frpvc#] IpDscp
Specifies which differentiated services codepoint (DSCP) bit settings should be applied to
traffic on the individual GSM PVC, which determines the relative priority of the traffic on
this PVC with respect to other traffic.
6 bits are used to define 64 classes of traffic (0 to 63)
The value of the Frame over IP, DSCP parameter is mapped to NetPerformer
classes of service, from 0 to 7
The default value is 0. This setting is typically used when no QoS is implemented
in the backbone network
The specific priority level of each class will vary depending on the IP service
provided (private or public). However, 0 (zero) is commonly associated with the
lowest priority level, and 63 the highest priority level.
Memotec Inc.
8-3
GSM Solution
NOTE:
8.6
Values:
0-63
Default:
Use a forced route

Console
Use a forced route
SNMP
pvcForcedRouteActive
Text-based Config
[frpvc#] ForcedRouteActive
Determines whether all traffic from this PVC will be sent through a specific serial (WAN)
or LAN port, digital channel or PVC connection. Set this parameter to YES to activate the
forced route.
NOTE:
Values:
YES, NO
Default:
NO
If you set Use a forced route to YES, the following parameter is also presented at the
NetPerformer console to define the forced route:
8.7
Port
Console
Port
SNMP
pvcForcedRoutePort
Text-based Config
[frpvc#] ForcedRoutePort
Defines which port, channel or PVC connection will be used to carry all traffic from this
PVC. Enter a question mark, ?, at the parameter prompt to view a list of possible values.
8-4
Values:
NONE, automatically generated list of ports and PVCs
Default:
NONE
Memotec Inc.
8.8
GSM maximum calls

Console
GSM maximum calls
SNMP
pvcGsmMaxCalls
Text-based Config
[frpvc#] GsmMaxCalls
Determines the maximum number of calls allowed before calls start to be rejected, using
the Call Blocking feature. The default value, 0, means no calls are rejected.
Call Blocking can be used in an IGMP/Multicast application or other TDMoIP solution:
If IGMP/Multicast is used, you must:
- Configure the Call management timer (s) GSM parameter (see Call management timeout (s) on page 6-5). When the timer expires, the value of the GSM
maximum calls parameter is used for Call Blocking.
- Activate IGMP on the BSC-side unit that registers to the multicast group.
Configure the following Ethernet LAN parameters using the SE/PORT command:
IP Address 1: Configure a unique IP address
IGMP enable: Set to YES
IGMP version: Set to 2
IGMP send report: Set to YES
IP multicast active: Set to YES
IP GSM group management: Set to the IP address of the
multicast group to which the BSC will register.
UDP port (GSM group mgmt): Change the default value, 6000 to
another port number, if required for your application.
NOTE:
The UDP port (GSM group mgmt) parameter appears only if IP GSM group
management is set to a non-zero value.
In applications where IGMP/Multicast is not activated, the NetPerformer

blocks calls based on the GSM maximum calls parameter alone. The Call management timer (s) GSM parameter does not need to be configured in this case.
Memotec Inc.
Values:
0 - 10000
Default:
8-5
GSM Solution
8.9
GSM VAD Deactivate threshold

Console
GSM VAD Deactivate

threshold
NOTE:
SNMP
pvcGsmVadDeactivateThreshold
Text-based Config
[frpvc#] GsmVadDeactivate-Threshold
NetPerformer support of dynamic Voice Activation Detection, or VAD, is discussed in the section Constant Bandwidth Support on page 1-26.
The GSM VAD Deactivate threshold determines the number of calls at which VAD will be
deactivated. When VAD is deactivated, the NetPerformer activates Silence Suppression
and stops generating constant-length IP frames for carrying the TRAU traffic. Set this
parameter to the number of calls at which bandwidth usage in your network reaches an
acceptable level of stability.
Tip: Try setting the GSM VAD Deactivate threshold to 5 and then fine-tune for your
network application. For dynamic VAD activation/deactivation to work, the GSM VAD
Deactivate threshold must be lower than the GSM VAD Activate threshold.
Values:
0 - 10000
Default:
8.10 GSM VAD Activate threshold

Console
GSM VAD Activate

threshold
SNMP
pvcGsmVadActivateThreshold
Text-based Config
[frpvc#] GsmVadActivateThreshold
The GSM VAD Activate threshold determines the number of calls at which VAD will be
activated. When VAD is active, the NetPerformer suspends Silence Suppression and
generates constant-length IP frames for carrying the TRAU traffic. This allows for stable
bandwidth levels when few calls are placed between the BTS and BSC units.
Tip: The GSM VAD Activate threshold must be higher than the GSM VAD Deactivate
threshold. Try setting it to 100 and then fine-tune for your network application.
NOTE:
8-6
If you leave both the GSM VAD Deactivate threshold and the GSM VAD
Activate threshold at their default value of zero (0), Silence Suppression is
always active on the GSM PVC.
Memotec Inc.
Values:
0 - 10000
Default:
8.11 GSM VAD A (bps)

Console
GSM VAD A (bps)
SNMP
pvcGsmVadA
Text-based Config
[frpvc#] GsmVadA
Defines the mean bandwidth used by the signaling channel in your application. This
parameter is used to fine-tune the VAD levels, to ensure that the NetPerformer generates
IP frames of a constant length.
Tip: As a starting point, try setting the GSM VAD A (bps) parameter to 100000.
Values:
0 - 15000000
Default:
8.12 GSM VAD B (bps)

Console
GSM VAD B (bps)
SNMP
pvcGsmVadB
Text-based Config
[frpvc#] GsmVadB
Defines the mean bandwidth used by a call (TCH).

A value of 15000 or 16000 is usually sufficient, depending on the performance desired for
the constant bandwidth function. A GSM VAD B set to 16000 ensures that the unit will
never discard packets carried by this PVC, whereas a value of 15000 could occasionally
cause packets to be discarded.
Memotec Inc.
Values:
0 - 15000000
Default:
8-7
GSM Solution
8.13 GSM VAD K (coefficient in percentage)

Console
GSM VAD K (coefficient

in percentage)
SNMP
pvcGsmVadK
Text-based Config
[frpvc#] GsmVadK
Defines the statistical gain that must be generated through VAD to reach the desired
compression ratio under a high volume of calls. The higher the value of this parameter, the
longer the IP frames will be and the higher the CIR, thereby ensuring stable bandwidth
levels.
The value of GSM VAD K depends on the value of GSM VAD B. As a general rule of
thumb, if GSM VAD B is 16000, start with a value of 60 for GSM VAD K. If GSM VAD B is
15000, GSM VAD K should be around 70. Then increase or decrease GSM VAD K
depending on the voice quality desired:
If GSM VAD K is decreased, the NetPerformer will generate smaller frames and
permit more calls, but the quality of those calls will be lower. For example, with a
GSM VAD B value of 16000, a GSM VAD K at 50% would be very aggressive,
and at 80% would permit perfect voice quality. The ideal value would be somewhere between these two.
Even with a GSM VAD K of 60% there is a risk of congestion if a high volume of
voice traffic occurs on currently connected calls. In this case, the voice quality
for these users will be affected.
To see whether congestion is occurring on one or more timeslot subchannels,
look at the error counter Number of samples discarded, listed with the SLOT
option of the Display Errors (DE) command (see Display Errors (DE) Command on page 4-19). This counter increases when congestion occurs.
- If the Number of samples discarded seems too high (1 sample = 1 hit for
voice), raise the GSM VAD K value by 5.
- If no samples have been discarded, try lowering the GSM VAD K value by 5,
and observe the counter again.
NOTE:
8-8
The fact that samples are being discarded is not in itself problematical, since it
permits accommodating more calls. A higher number of calls may be more
important in your network than maintaining voice quality.
Values:
0 - 100
Default:
Memotec Inc.
8.14 GSM group

Console
GSM group
SNMP
pvcGsmGroup
Text-based Config
[frpvc#] GsmGroup
Defines the GSM group number associated with this PVC. This number may be used to
identify the ID service in special applications. Otherwise, it should be left at its default
value, 0.
NOTE:
The value of GSM group must be the same on both the BSC-side and BTSside units.
Values:
0 - 65535
Default:
8.15 GSM maximum frame size

Console
GSM maximum frame

size
SNMP
Text-based Config
pvcGsmMaximumFrame- [frpvc#] GsmMaximumSize

FrameSize
Determines the largest datagram, in bytes, that can be sent or received on the interface in
one IP frame. Datagrams larger than the GSM maximum frame size are divided into
fragments before transmission, then reassembled at the remote end.
Values:
1 - 1504
Default:
1504
8.16 GSM pack delay (ms)

Console
GSM pack delay (ms)
SNMP
pvcGsmPackDelay
Text-based Config
[frpvc#] GsmPackDelay
Controls the Packetization feature on this PVC. It is possible to reduce the amount of
bandwidth used by packing the frames to reduce the IP header overhead. This parameter
determines how many milliseconds of frames will be packed before transmitting to the
remote side.
Memotec Inc.
Values:
Default:
8-9
GSM Solution
8.17 PVCR PVC that manages this PVC

Console
SNMP
PVCR PVC that manages pvcManagingPvcrPvc

this PVC
Text-based Config
[frpvc#] ManagingPvcrPvc
Determines which PVCR PVC will manage this GSM PVC if it is used in a redundant
PVC link application. The GSM PVC follows the state (up or down) of its managing
PVCR PVC. Select the name and number of a PVC that has been configured for PVCRoIP
operations (the Port parameter set to 0).
For full details on this application, turn to PVC Link Redundancy in a TDMoIP
Application on page 3-11.
8-10
Values:
NONE, FR-PVC 1, FR-PVC 2 to FR-PVC 300
Default:
NONE
Memotec Inc.
Index
Numerics
3G traffic support 1-20
A
A and E interface 1-7
characteristics of 1-8
configuration 2-4
NetPerformer solution 1-8
A-bis interface 1-10
configuration 2-5
configuration, of CHANNEL 2-16
configuration, of TSSUB 2-18
network connectivity 1-11
PowerCell encapsulation 1-14
Access schemes 5-10
FDMA 5-10
slow frequency hopping 5-10
TDMA 5-10
Acronyms 5-13
Activate 3G support 6-4
Advanced applications 3-1
Applications
A and E 1-7
advanced 3-1
GSM 2/2.5 and 3G convergence 1-20
GSM A/E interface 1-7
GSM A-bis interface 1-10
GSM A-ter interface 1-16
PowerCell tunneling 1-14
satellite network 1-19
A-ter interface 1-16
configuration 2-6
configuration, of CHANNEL 2-16
configuration, of TSSUB 2-18
ATM application 1-20
AuC 5-7
Authentication Center 5-7
Autodetection 1-27
disabling 1-28
Availability, on NetPerformer products 1-3, 2-1
B
Backup
GSM Solution
satellite 3-9
Base Station Controller 5-6
Base Station Subsystem 5-5
Base Transceiver Station 5-5
BSC 5-6
BSS 5-5
BTS 5-5
C
Call blocking 1-27, 8-5
Call management timeout (s) 6-5
Capture, PCM raw data 4-30
Cell packetization 1-25
Cells per cluster 5-3
Cells, types of 5-3
Channel Number 7-2
Channels 5-11
configuring 2-16
control 5-11
SS7 2-13
TCH 5-11
Clocking, high-precision 3-2
activation 3-2
CM 5-8
Communication Management 5-8
Compatibility, for mixed network 1-3
Configuration 2-1
A-bis interface 2-5
A-ter interface 2-6
channel, for GSM A-bis/ter 2-16
channel, for SS7 2-13
digital link 2-8
GSM parameters 2-12
preparing for 2-2
timeslot subchannel, manually 2-18
Constant bandwidth 1-26
Continuous AUTO detection 6-3
Control channels 5-11
Counters, displaying 4-17
D
DC command 4-17
DCH command 4-4
DDSP command 4-9
DE command 4-19
DGPS command 4-12
Digital link, configuring 2-8

Display commands 4-1
DJL command 4-10
DS command 4-20
DSCP 8-3
DTSCH command 4-6
E
E1 card 2-10
E1/T1 connections
statistics 4-2
EIR 5-7
Enhanced clock 3-2
activation 3-2
Equipment Identity Register 5-7
Errors, displaying 4-4, 4-19
Extended parameters 2-20
F
Factory Setup command 2-2
FDMA 5-10
Flow control 1-25
Format
timeslots on A-bis interface 1-11
transceiver timeslots on A-bis interface 1-12
Frame over IP parameters 2-14
Frame over IP, destination 8-2
Frame over IP, DSCP 8-3
Frame over IP, port number 8-3
Frame over IP, source 8-2
Frequency Division Multiple Access 5-10
FS command 2-2
Functions, of GSM network 5-8
G
Gateway Mobile Switching Center 5-6
GIWU 5-7
GMSC 5-6
GPS port activation 3-3
GPS status 4-12
GSM group 8-9
GSM interfaces 1-5
GSM Interworking Unit 5-7
GSM maximum calls 8-5
GSM maximum frame size 8-9
GSM network 5-8
architecture 5-4
compatibility 1-3
concepts 5-1
radio interface 5-10
terminology 5-13
GSM pack delay (ms) 8-9
GSM parameters 2-12

GSM PVC 2-14
parameters 8-1
GSM traffic type 2-14, 8-2
GSM traffic, supported by NetPerformer 1-5
GSM VAD A (bps) 8-7
GSM VAD Activate threshold 8-6
GSM VAD B (bps) 8-7
GSM VAD Deactivate threshold 8-6
GSM VAD K (coefficient in percentage) 8-8
H
Hardware 1-18
High-precision clocking 3-2
activation 3-2
HLR 5-6
Home Location Register 5-6
Hub functionality 1-24
I
Idle bandwidth optimization 1-25
Idle code 7-7
IDLE STOP 1-25
Installation status 2-2
Interface
A and E 1-7
A-bis 1-10
A-ter 1-16
GSM, supported by NetPerformer 1-5
radio 5-10
WAN 1-18
J
Jitter buffer 1-24
Jitter buffer (ms) 6-2
Jitter, displaying 4-10
L
License 1-19, 2-1
See also Software license
Link parameters 2-10
Load balancing 1-29
Location on the GSM network 7-3
Logical connections 2-13, 2-16
M
MM 5-8
Mobile cellular systems 5-2
Mobile Station 5-5
Mobile Switching Center 5-6
Mobility Management 5-8
Mode used when SIG detected 6-2
Memotec Inc.
Mode used when TCH detected 6-2

Monitoring 4-1
MS 5-5
MSC 5-6
N
A-bis interface 1-10
A-ter interface 1-16
features, configurable 1-23
GSM 2/2.5 and 3G convergence 1-20
interface types 1-5
monitoring 4-1
platform 1-18
satellite application 1-19
traffic types 1-5
Network and Switching Subsystem 5-6
Network architecture 5-4
Network compatibility 1-3
Network jitter 1-24
NSS 5-6
O
O&M 5-9
Operation and Maintenance 5-9
Operation and Support Subsystem 5-7
Optimization
GSM bandwidth 1-4
idle bandwidth 1-25
OSS 5-7
P
Packetization 1-25
Parameter list
Activate 3G support 6-4
Call management timeout (s) 6-5
Channel Number 7-2
Continuous AUTO detection 6-3
Frame over IP 2-14
Frame over IP, destination 8-2, 8-3, 8-4, 8-5, 89, 8-10
Frame over IP, source 8-2
GSM traffic type 2-14
GSM VAD A (bps) 8-7
GSM VAD Activate threshold 8-6
GSM VAD B (bps) 8-7
GSM VAD Deactivate threshold 8-6
GSM VAD K (coefficient in percentage) 8-8
Idle code 7-7
Jitter buffer (ms) 6-2
Location on the GSM network 7-3
Mode used when SIG detected 6-2
GSM Solution
Mode used when TCH detected 6-2

Protocol 7-2
Remote port number 7-8
Remote unit 7-7
Subchannel speed mask 7-5
Timeslot 7-2
TS subchannel mode 7-4
Use a forced route 2-14
Vendor of the GSM units 7-3
Parameters
channel, for A-bis/ter 2-16
channel, for SS7 2-13
E1 link 2-10
extended 2-20
GSM 2-12
T1 link 2-8
timeslot subchannel 2-18
PCM raw data capture 4-30
Port, for forced route 8-4
PowerCell encapsulation 1-14
Prioritization 1-24
Product license 2-1
See also Software license
Protocol 7-2
PVC link redundancy 3-11
PVC, for GSM 2-14
PVC, GSM 8-1
PVCR PVC that manages this PVC 8-10
R
Radio interface 5-10
Radio Resources 5-8
Remote functionality 1-24
Remote port number 7-8
Remote unit 7-7
RR 5-8
S
Satellite application 1-19
constant bandwidth 1-26
Satellite backup 3-9
Silence suppression deactivation 1-26
SIM 5-5
Software 1-18
Software license 2-1
agreement 2-1
Solution, for GSM bandwidth 1-4
SS7 2-13
Statistics 4-1
Status, displaying 4-4, 4-6, 4-20
GPS 4-12
Subchannel speed mask 7-5
Subscriber Identity Module 5-5
T
T1 card
Link parameters 2-8
TCH 5-11
TDMA 5-10
TDMoIP Application 1-22
TDMoIP application
configuration 2-7
enhanced clocking 3-2
GSM PVCs 2-14
packetization 1-25
Port parameter 8-1
PVC link redundancy 3-11
Terminal 5-5
Time Division Multiple Access 5-10
Timeslot 7-2
Timeslot allocation
autodetection 1-27
displaying 4-9
manual configuration 2-18
on A-bis interface 1-11
Traffic capture 4-30
Traffic channel 5-11
Traffic prioritization 1-24
Transceiver timeslots, on A-bis interface 1-12
Transmission 5-8
Transmitter frequencies 5-2
TRX 1-12
TS subchannel mode 7-4
Tunneling, using PowerCell 1-14
U
Use a forced route 2-14, 8-4
V
VAD 1-26
Vendor of the GSM units 7-3
Visitor Location Register 5-7
VLR 5-7
Memotec Inc.
GSM Solution
REACH FURTHER. OFFER MORE.

Contact Memotec:
tel.: +1-514-738-4781
e-mail: MemotecSupport@memotec.com
7755 Henri Bourassa Blvd. West
Montreal, Quebec | Canada H4S 1P7
www.memotec.com

24-GSM Support PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

24-GSM Support PDF

Uploaded by

Copyright:

Available Formats

GSM Support

NetPerformer System Reference

COPYRIGHTS AND DISCLAIMERS

7755 Henri Bourassa Blvd. West

About the GSM Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Network Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

GSM-only Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Mixed GSM and Non-GSM Network . . . . . . . . . . . . . . . . . . . . . 1-3

NetPerformer Solution for GSM Networks. . . . . . . . . . . . . . . . . . . . . . . . . 1-4

GSM Interfaces Supported. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

GSM Traffic Types Supported . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Using NetPerformer on the GSM A/E Interface . . . . . . . . . . . . . . . . . . . . . 1-7

Advantages with NetPerformer . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Characteristics of GSM A and E . . . . . . . . . . . . . . . . . . . . . . . . 1-8

NetPerformer Optimization of GSM A and E . . . . . . . . . . . . . . . 1-8

Using NetPerformer on the GSM Abis Interface . . . . . . . . . . . . . . . . . . . 1-10

Advantages with NetPerformer . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Network Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Characteristics of GSM Abis . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

NetPerformer Optimization of GSM Abis . . . . . . . . . . . . . . . . . 1-13

Using NetPerformer on the GSM Ater Interface . . . . . . . . . . . . . . . . . . . 1-16

Characteristics of GSM Ater. . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

NetPerformer Optimization of GSM Ater . . . . . . . . . . . . . . . . . 1-17

NetPerformer Platform for GSM Support. . . . . . . . . . . . . . . . . . . . . . . . . 1-18

Hardware and Base Software Requirements . . . . . . . . . . . . . . 1-18

GSM Abis/Ater Licensed Software Option . . . . . . . . . . . . . . . . 1-19

Satellite Network Application . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19

GSM 2/2.5G and 3G Convergence . . . . . . . . . . . . . . . . . . . . . 1-20

TDMoIP Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22

Configurable Software Features . . . . . . . . . . . . . . . . . . . . . . . 1-23

Chapter 2: Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Before You Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Is the GSM Abis/Ater Option Already Installed? . . . . . . . . . . . . 2-2

Configuration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Configuring the NetPerformer for GSM Abis . . . . . . . . . . . . . . . 2-5

Configuring the NetPerformer for GSM Ater . . . . . . . . . . . . . . . 2-6

Configuring the NetPerformer for TDMoIP . . . . . . . . . . . . . . . . 2-7

Configuring the Digital Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Configuring a T1 Physical Port (LINK). . . . . . . . . . . . . . . . . . . . 2-8

Configuring an E1 Physical Port (LINK). . . . . . . . . . . . . . . . . . 2-10

Configuring the GSM Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

Configuring an SS7 Signaling Channel . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

Configuring the GSM PVCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

Configuring the GSM Traffic Channels (CHANNEL) . . . . . . . . . . . . . . . . 2-16

Configuring the Timeslot Subchannels Manually (TSSUB) . . . 2-18

Extended Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

Chapter 3: Advanced GSM Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Enhanced High-precision Clocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Activating the Enhanced Clock . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Activating the GPS Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

About the Prioritization of GSM Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Uses and Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

How It Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Satellite Backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

E1 Standard Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

E1 Bypass Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

PVC Link Redundancy in a TDMoIP Application. . . . . . . . . . . . . . . . . . . 3-11

Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Chapter 4: Monitoring and Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

About Monitoring and Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Display GSM Channels (DCH) Command . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Display GSM TS Channel Allocation (DTSCH) Command . . . . . . . . . . . . 4-6