NetPerformer User Guide

NetPerformer ® 

User Guide 

Revision B1

Copyright 

Trademarks 

© Copyright 2002-2004 Verso Technologies, Inc. All rights reserved. 

No part of this publication, including text, examples, diagrams, or icons, may be 

reproduced, transmitted, or translated in any form or by any means, electronic, 

mechanical, manual, optical or otherwise, for any purpose, without prior written 

permission of Verso Technologies, Inc. 

Information in this publication is subject to change without notice. Verso Technologies, 

Inc. may have patents or pending patents applications, trademarks, copyrights, or other 

intellectual property rights covering subject matter in this publication. The furnishing of 

this document does not give you license to these patents, trademarks, copyrights, or 

other intellectual property. 

NetPerformer, PowerCell, SkyPerformer, ACTview, Clarent OpenAccess, Clarent 

Command Center, Clarent ThroughPacket, Clarent BHG, Clarent C4CM and C5CM are 

trademarks or registered trademarks of Verso Technologies, Inc. All other trademarks, 

registered trademarks and service marks are the property of their respective owners. 

October, 2002 

Document Part Number 620-0120-001 

Revision B1 

Verso Technologies, Inc. 

400 Galleria Parkway, Suite 300 

Atlanta, GA 30339 

USA 

Telephone: +1 (678) 589-3500 NetPerformer Technical Support: 

Fax: +1 (678) 589-3750 Telephone (direct): +1 (450) 619-2279 

Email: Info@NetPerformer.ca Email: Support@NetPerformer.ca 

Web: http://www.Verso.com 

http://www.NetPerformer.com

Contents 

Preface 

Chapter 1: Product Overview 

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 

Document Organization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 

Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 

NetPerformer Document Set . . . . . . . . . . . . . . . . . . . . . . . . . 16 

Other NetPerformer Documents. . . . . . . . . . . . . . . . . . . . . . . 17 

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 

Enter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 

Enter a Menu Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 

Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 

Parameter Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 

Instructions to the Reader . . . . . . . . . . . . . . . . . . . . . . . . . . 19 

Changes to Console Operations . . . . . . . . . . . . . . . . . . . . . . . . . 19 

Request for Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 

Technical Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 

Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 

NetPerformer Software Features . . . . . . . . . . . . . . . . . . . . . . . . 25 

Scalability and Flexibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 

Convergence of Multiple Traffic Types . . . . . . . . . . . . . . . . . . 26 

Multi-service Feature Set . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 

Traffic Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 

Application Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 

NetPerformer PowerCell-based Scenario . . . . . . . . . . . . . . . . . 31 

NetPerformer SIP VoIP Scenario . . . . . . . . . . . . . . . . . . . . . . 32 

Standard NetPerformer Characteristics . . . . . . . . . . . . . . . . . . . . 33 

PowerCell Technology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 

Data Handling Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . 34 

Analog and Digital Voice Support . . . . . . . . . . . . . . . . . . . . . . 35 

VLAN Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 

Traditional LANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 

Virtual LANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 

NetPerformer VLAN Capabilities . . . . . . . . . . . . . . . . . . . . 37 

Mapping VLAN IDs to Destinations. . . . . . . . . . . . . . . . . . . 38 

Using VLAN to Prioritize Traffic . . . . . . . . . . . . . . . . . . . . . 38 

NetPerformer SIP VoIP Characteristics . . . . . . . . . . . . . . . . . . . . 39 

Session Initiation Protocol (SIP) . . . . . . . . . . . . . . . . . . . . . . 39 

ATM Option Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 

ATM Switching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 

ATM Support on the NetPerformer . . . . . . . . . . . . . . . . . . . . . 41 

NetPerformer User Guide 3

Contents Doc. No. 620-0120-001 

Chapter 2: Getting Started 

Chapter 3: Configuration 

SkyPerformer Option Characteristics . . . . . . . . . . . . . . . . . . . . . . 44 

SkyPerformer Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 

Frame Relay Switching over Satellite. . . . . . . . . . . . . . . . . . . . 47 

Setting Up a SIP VoIP Network . . . . . . . . . . . . . . . . . . . . . . . . . . 49 

Configuring the NetPerformer from the Console . . . . . . . . . . . . . . 50 

Connecting the Console Terminal . . . . . . . . . . . . . . . . . . . . . . 50 

NetPerformer with Factory Configuration . . . . . . . . . . . . . . . 50 

NetPerformer with IP Address . . . . . . . . . . . . . . . . . . . . . . 50 

DHCP Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 

Direct Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 

Dialup Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 

Accessing a Remote NetPerformer Console . . . . . . . . . . . . . . . 54 

Relay (RE) Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 

TELNET Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 

Console Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 

Changing Parameter Values . . . . . . . . . . . . . . . . . . . . . . . . 56 

Arrow Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 

NetPerformer Console Operations . . . . . . . . . . . . . . . . . . . . . . 57 

Help (HE) Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 

Reset Unit (RU) Command. . . . . . . . . . . . . . . . . . . . . . . . . 59 

Quit Console (QU) Command . . . . . . . . . . . . . . . . . . . . . . . 59 

Configuration Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 

Setup (SE) Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 

SE Command Submenus . . . . . . . . . . . . . . . . . . . . . . . . . . 60 

Factory Setup (FS) Command . . . . . . . . . . . . . . . . . . . . . . 62 

Configuring the NetPerformer with SNMP . . . . . . . . . . . . . . . . . . . 64 

SNMP Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 

Accessing the SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 

NetPerformer MIB Categories . . . . . . . . . . . . . . . . . . . . . . . . . 66 

Defining User Access Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 

Defining the Global Characteristics . . . . . . . . . . . . . . . . . . . . . . . 71 

Standard NetPerformer and NetPerformer SIP VoIP Option . . . . 72 

Global Rackmount Chassis Parameters . . . . . . . . . . . . . . . . 74 

ATM Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 

Defining Bridge Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . 76 

Defining IP Routing Characteristics . . . . . . . . . . . . . . . . . . . . . . . 76 

Enable IP Router and Set Up Global IP Properties . . . . . . . . . . . 77 

IP Static Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 

Dynamic IP Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 

BOOTP/DHCP Relay Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 

TIMEP Real-time Clock. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 

SNMP Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 

TELNET Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 

FTP Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 

DNS Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 

Defining IPX Routing Characteristics . . . . . . . . . . . . . . . . . . . . . . 83 

4 Verso Technologies

Revision B1 (October, 2002) 

Enable IPX Router and Set Up Global IPX Properties . . . . . . . . 83 

IPX Filter Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 

Configuring a LAN Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 

Setting up a Virtual LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 

Defining SIP Characteristics on the NetPerformer SIP VoIP 

Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 

Enable SIP and Set Up Global Properties. . . . . . . . . . . . . . . . . 88 

SIP Timer Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 

SIP Retries Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 

Configuring a WAN Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 

Dedicated WAN Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 

Backup Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 

Calling Side of the Backup Link . . . . . . . . . . . . . . . . . . . . . 93 

Answering Side of the Backup Link . . . . . . . . . . . . . . . . . . 94 

Bandwidth on Demand Link. . . . . . . . . . . . . . . . . . . . . . . . . . 95 

Calling Side of the BOD Link . . . . . . . . . . . . . . . . . . . . . . . 95 

Answering Side of the BOD Link . . . . . . . . . . . . . . . . . . . . 95 

Defining the Phones for Backup and BOD Links . . . . . . . . . . . . 96 

Modem Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 

ISDN Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 

Wait-User Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 

Inactive Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 

Satellite Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 

MODULATOR Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 

DEMODULATOR Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 

EXPANSION Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 

AGGREGATE Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 

Defining the Frame Relay Connections . . . . . . . . . . . . . . . . . . . . 101 

FR-USER Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 

FR-NET Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 

PVCR PVC Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 

RFC1490 PVC Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 

Multiplex PVC Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 

Broadcast PVC Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 110 

Transparent PVC Parameters. . . . . . . . . . . . . . . . . . . . . . . . . 111 

ATMPVCR PVC Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 111 

AAL1 PVC Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 

FRF.8 PVC Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 

RFC1483 PVC Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 

ATMPPP PVC Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 

SP-Multiplex PVC Parameters . . . . . . . . . . . . . . . . . . . . . . . . 118 

Configuring an OSPF Connection . . . . . . . . . . . . . . . . . . . . . . . . 119 

OSPF Global Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 

Enable OSPF Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 

Area Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 

Range Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 

Virtual Link Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 

Allocating DSPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 

Configuring a T1, E1 or ISDN-BRI Connection . . . . . . . . . . . . . . . 125 

T1 Physical Port Parameters (LINK) . . . . . . . . . . . . . . . . . . . . 125 

CCS Signaling Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 



E1 Physical Port Parameters (LINK). . . . . . . . . . . . . . . . . . . . 128 

CCS Signaling Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 

ISDN-BRI S/T Physical Port Parameters (LINK). . . . . . . . . . . . 130 

Non-Japanese CCS Signaling Modes . . . . . . . . . . . . . . . . . 132 

Digital Voice/Data Channel Parameters (CHANNEL). . . . . . . . . 133 

Data Channel Parameters . . . . . . . . . . . . . . . . . . . . . . . . 134 

Voice Channel Parameters . . . . . . . . . . . . . . . . . . . . . . . . 141 

ISDN Caller ID Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . 149 

Configuring an Analog Voice Connection. . . . . . . . . . . . . . . . . . . 150 

Analog Physical Port Parameters (LINK). . . . . . . . . . . . . . . . . 150 

Analog Voice Channel Parameters (CHANNEL) . . . . . . . . . . . . 150 

FXS Channels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 

FXO Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 

E&M Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 

Configuring the Voice Mapping Table . . . . . . . . . . . . . . . . . . . . . 155 

Setting up a Voice Mapping Table on the Standard 

NetPerformer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 

Adding a MAP Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 

Modifying a MAP Entry . . . . . . . . . . . . . . . . . . . . . . . . . . 156 

Deleting a MAP Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 

Setting up a Voice Mapping Table on the NetPerformer 

SIP VoIP Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 

Adding a MAP Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 

Ingress and Egress Dial Rule Definitions . . . . . . . . . . . . . . 159 

Modifying a MAP Entry . . . . . . . . . . . . . . . . . . . . . . . . . . 161 

Deleting a MAP Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 

Configuring Hunt Forwarding on the Standard NetPerformer. . . . . 162 

Defining Custom Signaling Characteristics . . . . . . . . . . . . . . . . . 163 

Customizing the Line Signaling . . . . . . . . . . . . . . . . . . . . . . . 163 

Idle Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 

Seizure Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 

Pulse Dial Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 

Wink Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 

Clear Back Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 167 

Clear Forward Parameters . . . . . . . . . . . . . . . . . . . . . . . . 167 

Answered Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 

Ring Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 

Customizing the Ring Cadence . . . . . . . . . . . . . . . . . . . . . . . 169 

Examples of Custom Ring Definitions . . . . . . . . . . . . . . . . 170 

Customizing the Error Cause Code . . . . . . . . . . . . . . . . . . . . 171 

Defining NAT Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . 172 

Network Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 

Configuration Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 

Enabling NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 

IP NAT Rule Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 

Method of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 

IP NAT Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 

IP NAT Timeout Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 177 

IP NAT Service Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 178 

Method of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 

Defining Transparent User Port Characteristics . . . . . . . . . . . . . . 179 



HDLC Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 

DDCMP Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 

T-ASYNC Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 

R-ASYNC Port Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . 183 

BSC Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 

COP Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 

PASSTHRU Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 185 

PPP Port Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 

X25 Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 

Defining SNA Device Characteristics . . . . . . . . . . . . . . . . . . . . . . 189 

SNA/SDLC Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . 190 

PU Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 

Common Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 

Parameters for SDLC Side . . . . . . . . . . . . . . . . . . . . . . . . 193 

Parameters for LLC Side. . . . . . . . . . . . . . . . . . . . . . . . . . 194 

Parameters for DLSW Side . . . . . . . . . . . . . . . . . . . . . . . . 195 

Parameters for Links Side. . . . . . . . . . . . . . . . . . . . . . . . . 196 

Parameters for BAN Side . . . . . . . . . . . . . . . . . . . . . . . . . 196 

Parameters for BNN Side . . . . . . . . . . . . . . . . . . . . . . . . . 197 

Traffic Priority and Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . 197 

Class Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 

Default Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 

Schedule Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 

Filter Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 

Filtering VLAN Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 

Implementing DiffServ . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 

Chapter 4: Monitoring and Statistics 

Viewing System Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 

Display Counters (DC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 

Display Errors (DE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 

Display Bridge Statistics (DB) . . . . . . . . . . . . . . . . . . . . . . . . 205 

Checking System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 

Display States (DS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 

Display Active PUs (AP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 

Display Bridge Addresses (DBA) . . . . . . . . . . . . . . . . . . . . . . 207 

Display Software Alarms (DA) . . . . . . . . . . . . . . . . . . . . . . . . 207 

Display Journal (DJOURNAL) . . . . . . . . . . . . . . . . . . . . . . . . . 208 

Display Exit Record (ER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 

Running Real-time Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 

Display Channel States (DCS) . . . . . . . . . . . . . . . . . . . . . . . . 209 

Continuous Display of Port States (DPORT) . . . . . . . . . . . . . . . 210 

Continuous Display of PU States (DPU). . . . . . . . . . . . . . . . . . 211 

Continuous Display of PVC States (DPVC) . . . . . . . . . . . . . . . . 212 

Continuous Display of PVC DLCI States (DDLCI) . . . . . . . . . . . 213 

Continuous Display of SVC States (DSVC). . . . . . . . . . . . . . . . 214 

Viewing Current Hardware and Software Settings . . . . . . . . . . . . 214 

Display Configuration Parameters (DP). . . . . . . . . . . . . . . . . . 214 

Display Config Text (DCFG). . . . . . . . . . . . . . . . . . . . . . . . . . 215 

Display Slot Information (DSI) . . . . . . . . . . . . . . . . . . . . . . . 216 



Signaling Engine Channels (SEC) . . . . . . . . . . . . . . . . . . . . . 217 

Signaling Engine Information (SEI) . . . . . . . . . . . . . . . . . . . . 217 

Display Map File (DMF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 

Display NAT Table (DN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 

Display the Current Time (DT) . . . . . . . . . . . . . . . . . . . . . . . 220 

Setting the Time (ST command). . . . . . . . . . . . . . . . . . . . 221 

Display Software Version (DV) . . . . . . . . . . . . . . . . . . . . . . . 221 

Manipulating System Files and Settings . . . . . . . . . . . . . . . . . . . 222 

Check File System (CHKFS) . . . . . . . . . . . . . . . . . . . . . . . . . 222 

Display File List (DIR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 

Copy File (COPY) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 

Rename File (RENAME) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 

Delete File (DELETE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 

Defragment File System (DEFRAG) . . . . . . . . . . . . . . . . . . . . 225 

Format File System (FORMAT) . . . . . . . . . . . . . . . . . . . . . . . 225 

Managing the DHCP IP Address . . . . . . . . . . . . . . . . . . . . . . 226 

Managing the DNS Entries . . . . . . . . . . . . . . . . . . . . . . . . . . 226 

Capturing Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 

Setup Capture (SC). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 

Start Capture (STC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 

View Capture (VC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 

End Capture (EC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 

Capture Frame Length (CL) . . . . . . . . . . . . . . . . . . . . . . . . . 233 

Locating Network Components . . . . . . . . . . . . . . . . . . . . . . . . . 234 

Display Routing Table (DR) . . . . . . . . . . . . . . . . . . . . . . . . . 234 

Display Connections (DX) . . . . . . . . . . . . . . . . . . . . . . . . . . 236 

Display Destination Table (DD). . . . . . . . . . . . . . . . . . . . . . . 237 

Trace IP Route (TRACEROUTE) . . . . . . . . . . . . . . . . . . . . . . . 237 

Loopback Test (LT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 

PING Remote Unit (PING) . . . . . . . . . . . . . . . . . . . . . . . . . . 240 

PING Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 

Start Test Tone (STARTTONE) . . . . . . . . . . . . . . . . . . . . . . . 242 

Chapter 5: Example Applications 

IP Routing Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 

Central Site Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 247 

Remote Site Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 248 

Point-to-point Transparent Data Application . . . . . . . . . . . . . . . . 250 



Combined Data and Voice over T1 Application . . . . . . . . . . . . . . 254 



Integrated Voice and LAN Application with Link Backup . . . . . . . . 260 

Local Site Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 


Integrated Voice and SNA over Frame Relay Application . . . . . . . 265 





Index 

Analog and Digital Voice Integration over IP, Using 

NetPerformer PowerCell . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 

Central Site Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 


Analog and Digital Voice Integration over IP, Using SIP . . . . . . . . 285 

Central Site Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 





List of Figures 

The NetPerformer as Convergence Manager using PowerCell . . . . . 27 

The NetPerformer as Convergence Manager over IP . . . . . . . . . . . 27 

Standard NetPerformer Service Scenario. . . . . . . . . . . . . . . . . . . 31 

NetPerformer SIP VoIP Service Scenario . . . . . . . . . . . . . . . . . . . 32 

NetPerformer SIP VoIP to Clarent Gateway . . . . . . . . . . . . . . . . . 33 

ATM Access from the NetPerformer . . . . . . . . . . . . . . . . . . . . . . 42 

SkyPerformer Hybrid Network . . . . . . . . . . . . . . . . . . . . . . . . . . 44 

T1/E1 Voice Trunking via Satellite . . . . . . . . . . . . . . . . . . . . . . . 46 

SkyPerformer Internet Backbone Extension . . . . . . . . . . . . . . . . . 46 

SkyPerformer Frame Relay Network Extension. . . . . . . . . . . . . . . 47 

IP Routing Application Diagram . . . . . . . . . . . . . . . . . . . . . . . . . 246 

Point-to-point Transparent Data Application Diagram . . . . . . . . . . 250 

Combined Data and Voice over T1 Application Diagram . . . . . . . . 254 

Integrated Voice and LAN with Link Backup Application Diagram . . 261 

Integrated Voice and SNA over Frame Relay Application Diagram . 266 

Analog and Digital Voice Integration over IP Using NetPerformer 

PowerCell: Application Diagram . . . . . . . . . . . . . . . . . . . . . . . 278 

Analog and Digital Voice Integration over IP Using SIP: 

Application Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 


List of Figures Doc. No. 620-0120-001 


List of Tables 

MIB categories and corresponding console SE command 

submenus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 


List of Tables Doc. No. 620-0120-001 


Preface 

Audience 

This document, NetPerformer User Guide, provides: 

� An overview of NetPerformer features and the typical components of 

a network based on this product line 

� Planning, power-up and console connection procedures 

� Configuration instructions 

� Monitoring instructions 

� Example applications with typical parameter values used. 

This document does not describe NetPerformer hardware or 

installation procedures. For information on these, consult the Hardware 

Installation Guide for your product. All NetPerformer documents are 

available on the NetPerformer Online Reference CD, which is included 

with your product package. 

Note: For important information concerning changes to console 

operations in standard NetPerformer firmware version V9.2 and 

NetPerformer SIP VoIP V1.1, please consult Changes to Console 

Operations on page 19. 

This document is intended for use by NetPerformer system 

administrators, as well as technicians who are qualified to set up, 

configure and troubleshoot a NetPerformer Enterprise Network. 

Configuration and monitoring of the NetPerformer requires knowledge 

and proficiency in the configuration, operation, maintenance and 

security of all enterprise network elements in your application. You 

should also have a thorough understanding of telecommunications and 

be familiar with the networking strategies and telephony solutions 

currently used by your organization. 

Document Organization 

This document is organized into the following chapters: 

� Chapter 1, Product Overview introduces the NetPerformer, its 

firmware options, features and typical network scenarios. 


Preface Doc. No. 620-0120-001 

Related Documents 

� Chapter 2, Getting Started outlines preparatory steps to configuring 

the NetPerformer, start-up procedures and the various means of 

accessing configuration and monitoring functions. 

� Chapter 3, Configuration describes the NetPerformer SETUP 

command, its submenus and configurable parameters (for users 

with FULL console access only). 

� Chapter 4, Monitoring and Statistics, provides an overview of 

console commands for monitoring the NetPerformer and generating 

system and network statistics (for users with FULL or MONITOR 

access). 

� Chapter 5, Example Applications offers several examples of the 

NetPerformer in typical network applications, with screen dumps of 

parameter settings used. 

An Index is found at the end of this guide. 

This document requires no supplementary installation information if 

you are already familiar with the NetPerformer product line and, for the 

NetPerformer SIP VoIP option, the Clarent Command Center and Class 

5 Call Manager (C5CM). 

NetPerformer Document Set 

For further information on the NetPerformer, consult the following 

documents: 

Note: All of these documents are available on the NetPerformer Online 

Reference CD, which is included with your product package. 

� NetPerformer SDM-9360/9380 Standalone Chassis Hardware 

Installation Guide 

or 

NetPerformer SDM-9500 Rackmount Chassis Hardware Installation 

Guide 

These documents describe the hardware specific to each 

NetPerformer product, including installable options, complete 

installation instructions and firmware download procedures. 

� NetPerformer System Reference Manual (Administration Guide) 

This document provides detailed information on all NetPerformer 

features, menus, commands, parameters and statistics displays. 

Novice users and users with complex network requirements may 

need this level of detail to fully understand all product functions, 

concepts and operations. 



� Addenda to the NetPerformer System Reference Manual 

As a supplement and update to the NetPerformer System Reference 

Manual, each addendum describes all software developments in a 

particular NetPerformer release that concern new features of the 

base software and changes to the NetPerformer user interface. 

� NetPerformer Release Bulletins 

These documents summarize the system specifications, software 

fixes and changes, and post-production documentation changes for 

a particular NetPerformer release. 

� NetPerformer Network Design Guide 

Offers valuable tips on how to design a NetPerformer application for 

maximum efficiency, including an analysis of data and voice traffic 

throughput issues and the impact of traffic flow. Provides examples 

of network setup and traffic measurement using various 

NetPerformer products. 

Note: All of these documents are available on the NetPerformer Online 


In addition, if you are managing your NetPerformer network with 

ACTView 3000 you can refer to the following manual for information on 

the element managers for NetPerformer products and their 

components: 

� WinManager - ACTView 3000 Element Manager User Guide 

Describes the features and functions of all WinManager - ACTView 

3000 element managers for all NMS platforms supported (Windows 

95, Windows NT, Windows 2000 and Sun Solaris). 

Other NetPerformer Documents 

Information about the other components of the Clarent Softswitch 

solution is available from yourNetPerformer distributor. Other 

documents relevant to this application may include: 

� Clarent Class 5 Call Manager User Guide 

� Clarent Command Center User Guide 

� Clarent Gateway User Guide 

� Clarent Database Administration Guide 

� Clarent Application Server User Guide 

� Clarent Assist Administration Guide 

� Clarent Connect User Guide 



Conventions 

Enter 

Enter a Menu Sequence 

Variables 

In this document, an instruction to enter a particular character string 

means: 

1. Type the character string, and then 

2. Press the key. 

An instruction to enter a menu sequence means you should enter 

each menu name separately on succeeding lines of the console display. 

The elements of a menu sequence are separated by the carriage return 

symbol, ↵. 

For example, the instruction: 

Enter the menu sequence: SE ↵ IP ↵ OSPF ↵ AREA 

means you should do the following: 

1. Type SE 

2. Press the key 

3. Type IP 


5. Type OSPF 


7. Type AREA 


A menu sequence may include a variable, which must be replaced with 

an appropriate value when you execute the command. Variables are 

presented in italic font, with spaces replaced by underscoring. 

For example, the instruction: 

Enter the sequence: SE ↵ SLOT ↵ slot_number ↵ LINK 

means you should do the following: 

1. Type SE 


3. Type SLOT 




Parameter Names 

Instructions to the Reader 

5. Type the desired slot number (1, 2, 3 or 4) 


7. Type LINK 


A parameter name as it appears on the NetPerformer console is 

distinguished from the surrounding text by the use of italic font. For 

example, in the instruction: 

� Enable the IP Router, if desired (default ENABLE) 

the parameter name that actually appears on the console is Router. 

Instructions to the reader include notes, cautions and warnings, which 

are distinguished from the rest of the text by distinctive formatting and 

icons. Here is an example of each: 

Note: A note may contain a reference, tip or other information related 

to the subject at hand. The content of a note is intended to be helpful 

or of interest to the reader. 

Caution: A caution contains an instruction that the reader must 

follow in order to prevent damage to equipment, network failure 

or loss of data. The content of a caution must be read 

carefully and explicitly obeyed. 

Warning: A warning contains an instruction that the reader 

must follow in order to prevent electrical shock, death or serious 

injury to personnel. The content of a warning must be read 

carefully and explicitly obeyed. 

Changes to Console Operations 

The following changes to console operations have been made in 

standard NetPerformer firmware version V9.2 and NetPerformer SIP 

VoIP V1.1. If you are familiar with previous versions of the 

NetPerformer firmware, these changes should be taken into 

consideration before you attempt to configure or manage the product. 

� The way you access the NetPerformer console has changed to allow 

for multiple user profiles: 

� The default LOGIN is now ADMIN instead of ACT. 

Note: The default PASSWORD for this login remains SETUP. 



� For full instructions on setting up user profiles, refer to Defining 

User Access Profiles on page 70. 

� Speed dial numbers in the Voice Mapping Table are now always 

variable in size (from 1 to 30 digits). As a result: 

Request for Comments 

Technical Support 

� The length of the speed dial number is no longer defined with a 

global parameter (in the SETUP/GLOBAL submenu), which was 

the case in previous firmware releases. 

� The NetPerformer system now determines that a dialing 

sequence is completed when the global (inter-digits) Dial timer 

expires or when the user terminates dialing with the pound sign 

(#). 

� For details on the global parameters, refer to Defining the Global 

Characteristics on page 71. 

Our Technical Publications group welcomes your feedback. Please help 

us improve future releases of this document by sending us your 

comments and suggestions. You can send e-mail to 

Pubs@NetPerformer.ca. 

NetPerformer Technical Support is designed to meet your full range of 

support needs. From basic service to mission-critical support, we are 

committed to ensuring your success with NetPerformer products. We 

tailor different support plans to meet your evolving business 

requirements. By employing state-of-the-art products and the latest 

technologies available, we provide some of the fastest, most efficient 

service in the industry. 

Our entire support organization is focused on complete customer 

satisfaction and providing immediate solutions to your business needs. 

You can contact NetPerformer Technical Support by calling or sending 

e-mail to our helpdesk facilities: 

Telephone (direct): (450) 619-2279 

E-mail: Support@NetPerformer.ca 

Be prepared to provide the following information: 

� Your name 

� Company name 

� Your location 

� Telephone number 

� Release numbers of NetPerformer and, if applicable, Clarent Call 

Manager, Clarent Gateway and Clarent Command Center 



Training 

� Product serial numbers 

� Detailed problem description 

We offer a variety of classes to reduce your learning curve and make 

your employees more productive. Students learn how to tailor 

NetPerformer products to meet their specific business requirements. 

Each course is developed and delivered by certified instructors who 

have in-depth expertise and extensive technical training experience. 

Customized courses, tailored to meet your business needs, are also 

available. 

To learn more about our training services, contact NetPerformer 

Technical Support or your NetPerformer sales representative. 




Product Overview 

The NetPerformer family of Multi-service Integrated Access Devices is 

the optimal voice and data convergence solution that allows enterprises 

to integrate traffic over a variety of popular corporate WAN 

infrastructures. It is a scalable product that can interoperate with other 

network nodes in a variety of packetized environments in a flexible 

manner. 

Two NetPerformer firmware products are available to suit different 

network needs: 

� Standard NetPerformer: Offers voice transport over various WAN 

infrastructures using PowerCell, a proprietary cell-based protocol 

that ensures Quality of Service and minimum delays. 

Note: PowerCell is the trademarked term for the PVCR protocol 

(Programmable Variable Cell Relay). 

� NetPerformer SIP VoIP: Unites today’s distributed voice 

communications systems with Verso’s worldwide VoIP softswitch 

platform, offering voice transport over IP using standard Session 

Initiation Protocol (SIP). 

Note: In a future software release NetPerformer SIP VoIP will be 

offered as a licensed software option that is activated from the 

standard NetPerformer console. This does not affect the product 

functionality described in this guide. 

Both the standard NetPerformer and NetPerformer SIP VoIP can be 

enhanced with two licensed software options for special network 

communication requirements: 

� ATM (Asynchronous Transfer Mode) Option: Permits the 

integration of a wide variety of end user devices with an ATM 

network, providing a viable internetworking solution for high-volume 

and disparate traffic types. 

� SkyPerformer Satellite Access Option: Provides satellite access 

functionality to the NetPerformer product, creating a hybrid 

terrestrial/satellite network that uses a single hardware platform 

and network management system. 

NetPerformer User Guide 23 

1

Product Overview Doc. No. 620-0120-001 

These two options are sold under special license only, and require 

installation of a product key on every standard NetPerformer or 

NetPerformer SIP VoIP unit that will be used in the application. Use the 

Product License Status (PLS) command to enter the software license 

number: 

BOSTON>PLS 

PRODUCT LICENSE STATUS 

LICENSE> Enter a new license key (NO/YES,def:NO) ? YES 

LICENSE> ENTER LICENSE 

LICENSE> (xxxx-xxxx-xxxxxxxx-xxxx) (def:) ? 

For full instructions consult the following documents: 

� ATM license: Addendum to the System Reference Manual for 

Versions 9.0.0 to 9.2.0 

� SkyPerformer license: SkyPerformer Satellite Access Option User 

Guide. 

Note: These documents are available on the NetPerformer Online 


All NetPerformer products and licensed software options run on the 

same hardware platforms: 

� The SDM-9360/9380 standalone chassis models for branch, regional 

and remote offices. Refer to the NetPerformer SDM-9360/9380 

Hardware Installation Guide for details on hardware features. 

� The SDM-9500 rackmount chassis model for central site offices, 

which can be installed with several SDM-9585 cards. Refer to the 

NetPerformer SDM-9500 Hardware Installation Guide for details. 

These NetPerformer hardware platforms employ the following standard 

and proprietary technologies: 

� Standard: IP/Ethernet circuits, IP RIP v1/v2, IP Multicast PIMDM, 

VoIP using SIP (with NetPerformer SIP VoIP option), OSPF v2, PPP 

links, Frame Relay RFC-1490, SNA (SDLC, LLC, BAN/BNN and DLSw 

RFC-1434), VLAN IEEE 802.1Q-1998, ATM RFC-1483 and RFC-2364 

(with ATM option). 

� Proprietary: Signaling Engine technology for full support of 

standard voice algorithms and both standard and proprietary data 

protocols, PowerCell connections to converge voice and data, Voice 

over PowerCell (with standard NetPerformer), Frame Relay-based 

satellite connections (with SkyPerformer option). 



NetPerformer Software Features 

Scalability and Flexibility 

The NetPerformer is the ultimate voice and data convergence solution 

that provides superior multi-service support to the entire enterprise. It 

elegantly integrates voice and data into a single unified platform to 

tackle the greatest convergence challenges facing the enterprise 

network: 

� Superior voice quality and reliable data delivery through 

prioritization 

� Instant connectivity to most PBX (Private Branch Exchange), key 

system and data networks 

� Integrated routing to a broad array of WAN protocols. 

The results are far-reaching. Employees experience PSTN voice quality 

and effective data delivery, while IT and telecom managers enjoy 

simplified management and increased traffic transport choices. 

The NetPerformer is an extremely flexible and adaptable network 

solution. Its scalable hardware design provides an easy migration path 

for changing network needs. 

� The three NetPerformer models: SDM-9360, SDM-9380 and SDM- 

9500 (with SDM-9585 cards), provide telephony interfaces in 

densities that accommodate large headquarters and small remote 

offices alike. 

� Supporting anywhere from 2 to 240 telephony channels per unit/ 

chassis, the NetPerformer can converge voice and data over leased 

or switched lines, Frame Relay, ATM, PPP links, ISDN PRI and BRI, 

satellite and IP/Ethernet circuits. 

� PBX and PSTN (Public Switched Telephone Network) voice interfaces 

include analog FXS, FXO and E&M, and digital T1, E1, ISDN-PRI, 

ISDN-BRI, including switched QSIG message delivery. 

A simple software upgrade allows customers to extend their capabilities 

to those of the Service Provider, including VoIP services, virtual bridged 

LAN support (VLAN) and new IP-based applications. In this way, a 

NetPerformer node can easily evolve from an integrated access device 

linking businesses over a private voice and data network to a 

communications power nexus: the Clarent C5CM softswitch combined 

with the capabilities of the NetPerformer SIP VoIP gateway. 



Convergence of Multiple Traffic Types 

NetPerformer technology is a stable and proven convergence platform 

that has been employed by global corporations for over 10 years in 

worldwide networks. The NetPerformer integrates traffic from various 

sources and outputs it to one or more network types, bringing a broad 

range of telecommunications services within the reach of the enterprise 

network. 

� With T1 or E1 channelized digital connections, each of the 

embedded DS0s contains voice, fax or modem signals in the form of 

pulse coded modulation (PCM). 

Note: The SDM-9360/9380 and SDM-9585 also support analog 

voice, data (including legacy protocols), LAN and IP/IPX traffic. 

� Voice traffic is internally routed to a DSP resource, which 

compresses each voice channel using a preconfigured advanced 

compression algorithm: ACELP-CN, G.723, G.726 (16 to 40K), 

G.729, G.729A, or PCM64K. 

� Compression reduces the bandwidth required by each voice channel 

from 64 Kbps to a lower number, depending on the algorithm used. 

� Fax and modem signals are also demodulated and converted into a 

data stream. 

� Various signaling schemes (CAS, MF, DTMF, etc.) are used to 

determine the destination of each call. 

� Appropriate protocols and physical interfaces are then used to 

packetize each call and route it to its destination over IP, Frame 

Relay, ATM, PowerCell or satellite connections. 

� Both the standard NetPerformer and NetPerformer SIP VoIP 

transport data over PowerCell 

� Standard NetPerformer transports voice directly over PowerCell 

� NetPerformer SIP VoIP does voice over IP that can be 

subsequently transmitted over PowerCell (requires another 

NetPerformer SIP VoIP at the other end) or standard PPP and 

Ethernet protocols 

� Physical interfaces for routing data traffic include channelized T1/ 

E1, serial WAN/user and Ethernet LAN interfaces. 

� Digital signaling is converted as required in order to maintain 

compatibility with various types of remote units. 



VIDEO 

Intranet 

modem 

pots 

Fax 

Fax 

SNA 

Voice 

LAN 

Enterprise 

Enterprise 

NetPerformer 

Service Service Provider 

Provider 

Figure 1 The NetPerformer as Convergence Manager using PowerCell 

VIDEO 

Intranet 

modem 

pots 

Fax 

Fax 

SNA 

Voice 

LAN 

Enterprise 

Enterprise 


IP/Internet 

Service Service Provider 

Provider 

Figure 2 The NetPerformer as Convergence Manager over IP 

Fractional 

T1/E1 

T1/E1 

Frame Relay 

& 

SkyPerformer 


Leased 

Line 

ATM 

T1/E1 

IP/Internet 

Fractional 

T1/E1 

T1/E1 

Leased 

Line 

Frame Relay 

& 

SkyPerformer 

ATM 

T1/E1


Multi-service Feature Set 

The power and flexibility of the NetPerformer Multi-service Integrated 

Access Device are the outcome of an enhanced feature set: 

� Integrates Internet, Frame Relay, SNA, legacy data, HDLC/ASYNC, 

IP LAN traffic (including VLAN), toll-quality analog and digital voice/ 

fax/modem transmissions over a single communication circuit, 

eliminating parallel voice and data networks 

� Transmits and receives traffic over IP, ATM, public or private Frame 

Relay, leased line networks or satellite 

� Integrates RIP V1/V2 IP, IPX and OSPF networks with central-point 

routing and bridging, including IP Multicast, IP Subnet Broadcasting, 

and PowerCell over IP 

� Provides multi-channel support for simultaneous voice and data 

streams through an optional digital T1, E1 or ISDN-BRI S/T interface 

� PowerCell technology permits concurrent handling of a variety of 

traffic types and configurable prioritization of SNA, legacy data, LAN 

and WAN (PVCR) traffic 

� Support of the SkyPerformer satellite access option, under special 

license 

� Software configurable voice compression topography, enhanced 

voice mapping table and adjustable voice traffic buffers permit 

aligning product functionality to current needs 

� Supports a broad range of voice signaling types: analog FXS, FXO 

and E&M, digital Channel Associated Signaling (CAS), Common 

Channel Signaling (CCS), QSIG, ISDN-PRI and ISDN-BRI S/T 

� Provides a variety of voice algorithms in a configurable, modular 

DSP allocation scheme: ACELP-CN, G723 (low and high), G726 

(from 16K to 40K), G729, G729A and PCM64K 

� On the standard NetPerformer, allows for T1 and E1 transparent 

signaling between 2 PBXs that use CCS, over timeslot 24 (on a T1 

connection) or 16 (on an E1 connection) 

� Permits customization of digital line signaling characteristics for nonstandard 

applications 

� Supports analog PBX connections using E&M interface cards, 

allowing for up to 16 E&M lines and a variety of signaling types: 

Immediate Start, Wink Start, Timed E, as well as customized 

signaling 

� Includes CAS emulation of FXO, FXS, Grounded FXO, Grounded FXS, 

E&M Immediate Start, E&M Wink Start, R2, PLAR 

� Offers a Drop and Insert functionality (Passthrough mode) on digital 

interfaces, useful for dividing timeslots between compressed voice 

traffic that passes through PowerCell over IP, and uncompressed 

traffic that is routed directly to the PSTN 



Traffic Handling 

� Provides Network Address Translation (NAT) support to prevent IP 

address depletion and ensure efficient service in Internet 

applications 

� Replaces SNA leased lines with a single Frame Relay connection 

supporting multiple PVCs and, for voice traffic, SVCs 

� Takes advantage of highly efficient data compression algorithms 

� Provides fax/modem relay between 2 NetPerformer nodes (standard 

NetPerformer only) 

� NetPerformer SIP VoIP provides standard VoIP support using SIP call 

setup, RTP (Real-Time Protocol) for voice transport and T.38 for fax 

� Adds provision for line failure with virtual connections and dial 

backup functions 

� Optimizes bandwidth utilization with traffic prioritization, Bandwidth- 

On-Demand and load balancing 

� Minimizes delays for time-sensitive applications with Weight Fair 

Queueing (WFQ) prioritization schemes over multiple traffic types 

� Ensures standards-compliant interoperability with RFC-1490, SIP 

(on NetPerformer SIP VoIP) and Simple Network Management 

Protocol (SNMP) 

� Facilitates firmware upgrades through FTP download, ZMODEM 

transfer via the console and proprietary access tools 

� Provides traffic capture capabilities for troubleshooting purposes 

� Includes management capabilities such as SNMP support, Telnet 

remote access and direct or dialup console connection; compatible 

with the ACTView 3000 Network Management System (NMS). 

NetPerformer features and product concepts are detailed in the 

NetPerformer System Reference Manual (Administration Guide), which 

is included on the NetPerformer Online Reference CD delivered with 

your product. 

The traffic handling capabilities of the NetPerformer family of products 

are extensive: 

� Switching through intermediate NetPerformers using PowerCell 

technology 

� PVC bundling to concentrate Frame Relay traffic originating from 

multiple FRADs 

� Virtual LAN (VLAN) functionality to logically group nodes on different 

LAN segments and prioritize their traffic. 

� SVCs and Hunt Groups to maximize voice switching capacity (on 

standard NetPerformer only) 



� Support of the ATM cell-based traffic structure (on ATM option only) 

permits access to a variety of network services via ATM from a 

single unit, using AAL1 and AAL5 modes. 

� Voice Traffic Routing (VTR) for local control of how voice traffic is 

forwarded to its intended destination, with the possibility of setting 

up alternate routes using local and long distance services 

� Bandwidth On Demand over leased lines for managing bursty LAN 

traffic while keeping telecommunications costs down 

� Load balancing over leased lines or Frame Relay, to provide highspeed 

support using multiple circuits 

� Dial backup 

� Multiprotocol support with prioritization through class of service 

queues 

� SNA host port reduction 

� High-performance data compression to improve throughput and 

reduce telecommunications costs 

� Administrative filtering to reduce the internetwork load, based on 

protocols, source/destination addresses and user-defined patterns 

� PPP and BOOTP/DHCP Relay support. 

Application Scenarios 

A wide variety of applications can be built from basic network scenarios 

that use PowerCell on the standard NetPerformer or SIP on the 

NetPerformer SIP VoIP option. 

Note: Specific application examples with detailed configuration 

information are provided in Chapter 5, Example Applications. 



NetPerformer PowerCell-based Scenario 

SNA Controller 

PBX 

Ethernet 

Figure 3 Standard NetPerformer Service Scenario 

Fax 


SDM-9230 

PowerCell 

Switching 

The standard NetPerformer can be used to build a private network for 

enterprises of all sizes through virtual connections between different 

network nodes (IP, Frame Relay, etc.) using PowerCell switching. 

� To establish these connections, no direct links are required between 

the remote locations, since PowerCell can switch traffic via the 

central site unit. 

� PowerCell runs over IP, Frame Relay, leased lines, PSTN, ATM and 

satellite 

� Protocol switching, e.g. from IP to Frame Relay, is accomplished 

without IP transport overhead when switching onto the Frame Relay 

network 

� This solution provides the advantages of data compression, multiprotocol 

encapsulation and Quality of Service using up to 8 classes 

of service 

� Voice switching using PowerCell permits defining all call routes 

within the unit using Voice Mapping Tables 

� No softswitch is required in this scenario. 


SDM-9230 


IP 

Frame Relay 

Leased Lines 

PSTN 

ATM 

Satellite 


Ethernet 

Fax 


SDM-9500(9585) 

PBX 

SNA 

Host 

Ethernet 

... 

PBX


NetPerformer SIP VoIP Scenario 

Intelligent Network 

Layer 

Call Control Layer 

Clarent 

Command Center 

SIP 

Clarent 

Call Manager 

Figure 4 NetPerformer SIP VoIP Service Scenario 

Ethernet 

IP 

SIP 

Call Setup 

The NetPerformer SIP VoIP offers a full service scenario for the 

enterprise network using SIP transport. With SIP, the NetPerformer 

provides seamless integration of Frame Relay, ATM and PSTN networks 

under an IP-centric network. 

� Permits a unified voice/data routing service across the entire 

network under a standard IP protocol 

� Provides all participating sites with the call management and control 

features of the IP-centric Clarent Master Network/softswitch 

� Allows all areas of the network to benefit from the throughput and 

cost advantages of Voice over IP, including small branch offices in 

remote locations 

� Provides Quality of Service (QoS) for voice connections and 

excellent response times across all locations 

� Supports traffic types that otherwise could not be transmitted across 

the central data cloud, such as analog PBX, satellite and data 

transmissions 

� Integrates these traffic types with digital voice and data using IP 

over WAN, Frame Relay, ATM and IP trunking. 

Through Centralized Managed Softswitch Voice Architecture, the 

NetPerformer SIP VoIP option allows the network to attain a global 

presence, with enhanced flexibility, scalability and compatibility with 

other gateways. 

32 Verso Technologies 

On-net 

VoIP 

External 

Router 

Ethernet 

Internal Router 

and VoIP 

Gateway 


Ethernet 

VoIP Gateway 


PBX 

PBX



Layer 


Clarent 


SIP 

Clarent 

Call Manager 

Figure 5 NetPerformer SIP VoIP to Clarent Gateway 

Standard NetPerformer Characteristics 

PowerCell Technology 

Ethernet 

IP 

Clearing House 

Off-net 

VoIP 

SIP 

Call Setup 


SDM-9220 

The standard NetPerformer provides an efficient means of merging SNA 

and other legacy data with LAN internetworks. It links Ethernet 

networks over analog or digital dedicated or switched wide area 

network (WAN) services, as well as Frame Relay. Applications using 

diverse traffic types can be integrated as a single network, eliminating 

separate circuits. 

The standard NetPerformer implements unique cell-based traffic 

prioritization and switching over Virtual Connections, and provides 

highly efficient data compression, superior traffic expediency and 

flexibility of the network topology. Reliable response time is guaranteed 

through prioritization of mission-critical protocols such as LLC, SDLC, or 

any user-defined protocol. 

PowerCell is a cell-based protocol that conserves network bandwidth, 

ensures Quality of Service (QoS) and reduces delays. It provides voice 

and data transport over various WAN infrastructures, including IP and 

IP/Ethernet circuits, and offers NetPerformer’s award-winning 


IP 

Clarent Gateway 

On-net 

VoIP 


SDM-9500(9585) 

PSTN 

... 

PBX 

PBX


Data Handling Capabilities 

prioritization and compression technology for superior network 

performance. A PowerCell solution provides the advantages of data 

compression, multi-protocol encapsulation and Quality of Service using 

8 classes of service. 

� PowerCell runs over IP, Frame Relay, leased lines, PSTN, ATM and 

satellite. Protocol switching, e.g. from IP to Frame Relay, is 

accomplished without IP transport overhead when switching onto 

the Frame Relay network. 

� PowerCell switching allows for the creation of a private enterprise 

network that uses virtual connections between different network 

nodes. No direct links are required between the remote locations, 

since PowerCell can switch traffic via the central site unit. 

� Voice switching using PowerCell permits defining all call routes 

within the unit using Voice Mapping Tables. Since no softswitch is 

required, this is an effective low-cost solution for the small to 

medium-sized enterprise. 

� PowerCell QoS can be combined with IP Precedence TOS bit and 

802.1p/q support to provide end-to-end Quality of Service for voice 

and mission-critical data applications. 

The standard NetPerformer takes full advantage of innovative LAN/WAN 

capabilities: 

� Flexible network connections 

� Efficient multiplexing of data from all sources 

� Prioritization levels maintained across the network 

� Routing of IP and IPX traffic; bridging of all other protocols 

� End-to-end routing of cells in a meshed topology 

� Dynamic rerouting in case of line failure 

� Rapid, flexible and inexpensive transport of voice/fax traffic without 

requiring network reconfiguration. 

Other data handling capabilities of the NetPerformer include: 

� Switching through intermediate NetPerformers using Cell Relay 

technology 

� PVC bundling to concentrate Frame Relay traffic originating from 

multiple FRADs 

� Bandwidth On Demand over leased lines for managing bursty LAN 

traffic while keeping telecommunications costs down 

� Load balancing over leased lines or Frame Relay, to provide highspeed 

support using multiple circuits. 

� Dial backup 



� Multiprotocol support 

� SNA host port reduction 

� High-performance data compression to improve throughput and 

reduce telecommunications costs 

� Administrative filtering to reduce the internetwork load, based on 

protocols, source/destination addresses and user-defined patterns 

� PPP and BOOTP/DHCP Relay support. 

Analog and Digital Voice Support 

The NetPerformer supports connections to public and private networks, 

Central Offices (COs), PBXs, Key Telephone System (KTS) extensions, 

standard telephones and fax machines, and integrates their traffic with 

regular LAN/WAN data. It includes a variety of powerful features to 

ensure that voice and fax are reliably integrated with traffic from other 

sources, efficiently transmitted across the network, and that excellent 

voice quality is maintained from source to destination: 

� Analog-to-digital conversion 

� Fragmentation of the voice/fax stream for reduced network latency 

� Toll quality voice compression at 8 Kbps 

� Fax demodulation for improved throughput of fax traffic 

� Variable bit rates for low bandwidth usage during silence and 

signaling tones 

� Full support of a wide variety of interfaces and signaling types 

� Automatic voice/fax prioritization 

� Autodial or switched line activation 

� Echo cancellation. 

The NetPerformer is equipped with voice channels, or ports, for voice/ 

fax transmission. Each interface supports signals from a variety of 

voice/fax sources using industry standard signaling methods. Each 

channel also has its own DSP (Digital Signal Processor) for digitization 

and voice compression facilities. Echo cancellation is provided on all 

channels following the CCITT G.165 standard. 

Analog interfaces include: 

� E&M: “Ear and Mouth”, used between the switching machine’s trunk 

circuit and an associated signaling system 

� FXO: Foreign Exchange Channel Unit - Office End, a loop-start 

signaling method used when connecting to a Central Office (CO) 

� FXS: Foreign Exchange Channel Unit - Station End, a loop-start 

signaling method used when connecting to a telephone unit or 

facsimile machine (POTS line) or a Key Telephone System (KTS 

unit). 



VLAN Support 

Digital interfaces include T1, E1, ISDN-PRI and ISDN-BRI, including 

switched QSIG message delivery. Consult the Hardware Installation 

Guide for your NetPerformer product for further information on these 

interfaces. 

Note: This feature is also available on the NetPerformer SIP VoIP. 

NetPerformer VLAN support follows the IEEE 802.1P-Q standard for 

virtual bridged LANs, and provides: 

� The ability to create, change and manage logical groups of stations 

that communicate as though they were on the same LAN. 

� Common support of all LAN MAC protocols over point-to-point and 

shared media LANs. 

� Sharing of a common media into multiple virtual LANs. 

Note: Although they share the same media, VLANs are independent 

from one another. 

� Restricted traffic movement. Bridges forward unicast, multicast and 

broadcast traffic only on specified LAN segments, configurable by 

the user. 

� Compatibility with existing bridges and end stations. 

Traditional LANs 

Traditionally, all the stations on a LAN are part of the same network. 

Although, they may be subdivided into workgroups for management 

purposes, the network is unaware of this segregation. 

� Any broadcast message that is sent by one station is forwarded to 

all other stations, in all workgroups, and propagated by any bridges 

that are part of the network. 

� In this architecture, there is no way for the bridge to know if there is 

anyone on the other side that requires this broadcast. 

� If relatively independent workgroups share the same physical 

network, the requirement to broadcast all traffic to all LAN segments 

can reduce the overall efficiency of the network. This can become a 

problem in large networks with hundreds or thousands of nodes. 

Virtual LANs 

IEEE recommendation 802.1Q introduces a method for subdividing the 

physical media into multiple virtual LANs (VLANs). 

� This is achieved by adding a four-byte VLAN Tag Header into the 

MAC header. 



� The VLAN Tag Header contains the VLAN ID and a three-bit user 

priority field. This field is used to implement traffic prioritization, 

following IEEE recommendation 802.1P (see Using VLAN to Prioritize 

Traffic on page 38). 

VLANs can be used to logically group together nodes that are on 

different LAN segments. 

� Each node is assigned a VLAN ID, which is included in the VLAN Tag 

Header on all traffic transmitted from that node. 

� The VLAN information is used primarily by the bridge to determine if 

a broadcast message needs to be forwarded on a particular 

interface. 

� The bridge keeps track of which VLAN is present on each LAN 

segment, so it knows on which interface to forward traffic for a 

specific VLAN. 

NetPerformer VLAN Capabilities 

The NetPerformer Ethernet port can be configured to be VLAN-aware. 

� This is accomplished by enabling the VLAN enable parameter and 

assigning a VLAN ID to the Ethernet port, representing the VLAN on 

which the Ethernet port resides. Refer to Configuring a LAN 

Interface on page 84 for the configuration procedure. 

� Traffic destined to the NetPerformer itself (such as Telnet, FTP, PING, 

etc.), must come from the same VLAN to be recognized by the 

NetPerformer. Otherwise, the traffic is treated as though it were on 

another network. 

The Ethernet port processes tagged and untagged frames in the 

following manner: 

� When a tagged frame is received on the Ethernet port: 

� The NetPerformer processes the frame, whether or not the 

Ethernet port has been configured to be VLAN-aware. 

� If the frame is destined for the NetPerformer itself, however, the 

VLAN parameter must be enabled and the received frame must 

match the configured VLAN number. Otherwise, the NetPerformer 

discards the frame. 

� When an untagged frame is received on the Ethernet port: 

� The NetPerformer always processes the frame. 

Note: Even if the Ethernet port has been assigned a VLAN number, 

the NetPerformer is still able to accept and bridge untagged frames. 

� When a tagged frame is sent from the Ethernet port: 

� The NetPerformer bridges the frame on the Ethernet port, even if 

it is not configured to be VLAN-aware. 

Note: To successfully bridge a tagged frame, the VLAN destination 

must be properly configured in a VLAN profile (1 to 10). 



� When an untagged frame is sent from the Ethernet port: 

� The NetPerformer always processes and bridges the frame. 

Note: The NetPerformer implementation of IEEE 802.1P-Q assumes 

that all LAN traffic is already properly tagged and has the priority field 

set to an appropriate value. The NetPerformer does not modify 

these fields en route from one network to another. Traffic that 

is not tagged is bridged in the traditional manner. 

Mapping VLAN IDs to Destinations 

To configure the NetPerformer to support VLANs, the user must build a 

VLAN ID to Destination Mapping Table. The NetPerformer uses this 

table to determine over which PVC or port it should send a frame that 

belongs to a particular VLAN. 

For the VLAN configuration procedure, refer to Setting up a Virtual LAN 

on page 87. 

Using VLAN to Prioritize Traffic 

The NetPerformer employs priority field processing, following the IEEE 

802.1P standard, to prioritize one traffic type over the rest of the 

traffic. For example, it is possible to prioritize voice traffic over LAN 

traffic in a VoIP application to prevent voice clipping when data burst 

occur. 

� When the frames are bridged, the priority field of the VLAN TAG 

Header is carried intact to the destination network. 

Note: If PowerCell transport is used, NetPerformer filters can also 

be defined to set the priority of a frame according to the VLAN Tag 

Header priority field. Refer to Filtering VLAN Priority on page 200. 

� When the frames are routed the VLAN Tag Header is lost, and the 

priority information along with it. However, the NetPerformer can be 

configured to convert the priority information from the VLAN Tag 

Header to another format before routing, to ensure proper 

prioritization of the traffic. 

Note: This is accomplished with the VLAN Priority Conversion 

parameter during configuration of the Ethernet port. Refer to 

Configuring a LAN Interface on page 84. 



NetPerformer SIP VoIP Characteristics 

The NetPerformer SIP VoIP is an IP-centric voice/data integration 

solution that employs Session Initiation Protocol (SIP). This protocol is 

based on existing Internet and SMTP/HTTP conventions that are well 

suited for large point-to-point and any-to-any networks. The 

NetPerformer SIP VoIP is intended for a broad range of applications and 

serves the wide area internetworking needs of central sites, regional 

offices and both large and small branch offices. 

� Converges voice and data over PPP links, Frame Relay RFC-1490, 

ATM RFC-1483 and IP/Ethernet circuits 

� Uses Signaling Engine technology for SIP-based VoIP transport, 

standard voice algorithms and both standard and proprietary data 

protocols and data compression algorithms 

� Provides T1/E1 connectivity, including digital connections to PBXs 

via T1 and E1 using CAS and CCS (QSIG), and offers drop and insert 

multiplexing for both data and voice 

� Maximizes bandwidth usage with high throughput levels, low 

overhead and minimal delays, and guarantees reliable integration of 

voice, fax and data traffic. 

� Optimizes line utilization with cell-based multi-protocol 

prioritization, Bandwidth-On-Demand and Load Balancing, and adds 

provision for line failure with Virtual Connections and dial backup 

functions 

� Significantly reduces communications costs, since it cuts long 

distance charges, handles time-sensitive applications with reduced 

delays, and eliminates the need for dedicated voice and data circuits 

in the network 

� Runs on the same hardware platform as the standard NetPerformer 

product line, and includes most of the standard NetPerformer 

features. 

Session Initiation Protocol (SIP) 

SIP is an efficient VoIP protocol that was built on existing Internet and 

SMTP/HTTP conventions, and in recent years has become the standard 

protocol for VoIP applications. It provides intelligence at the edge of the 

network, which allows the end user to take advantage of recent 

enhancements in voice and Internet applications. 

Both the NetPerformer SIP VoIP and Clarent Call Manager use standard 

SIP. Together, these two products allow carriers to: 

� Deliver new services quickly and inexpensively 

� Offer enterprise customers access to the next generation of IP 

networks that converge data and voice. 



Additional networking capabilities are available to the enterprise market 

through the flexible NetPerformer base feature set, which provides 

integrated access to a wide variety of traffic types: 

� WAN interfaces: T1/E1 channelized, serial ports (V.35, X.21, RS232, 

etc.), ISDN-PRI and ISDN-BRI. 

� WAN protocols: PVCR (PowerCell) for dial backup, Bandwidth On 

Demand and load balancing, QoS (proprietary 8 classes), FR-USER 

over PowerCell and RFC1490, PPP, ATM AAL5 (PowerCell), RFC1483, 

ATMPPP (RFC-2364), FRF.8 (IWF). 

� LAN protocols: Ethernet 10BT, 100BT, IP routing, RIP1, RIP2, OSPF2, 

Multicast, DHCP/BOOTP relay, SNMP, NAT, VLAN. 

� Data support: Frame Relay switching, SNA (SDLC, LLC), HDLC, 

Async, FR-NET switching, data compression. 

� Voice support: ACELP-CN compression, FXO, FXS, E&M, G729(a), 

G711, G726, G723 compression, T1, E1, ISDN-PRI, ISDN-BRI, T.38 

(Fax/IP). 

� Voice signaling: CAS, Immediate Start, Wink Start, R2, etc., QSIG, 

ISDN-PRI/BRI supplementary services (E1), SIP/SDP, RTP. 

ATM Option Characteristics 

Asynchronous Transfer Mode (ATM) is a cell-based technology that 

permits the transmission of a variety of traffic types over public and 

private networks using a common packet structure. All information is 

organized into fixed-length cells which can be sent from a large number 

of service users. With the addition of ATM, large networks can integrate 

voice, data and video more efficiently, and maximize service to all 

destinations while reducing bandwidth requirements. 

The ATM structure is based on the idea of a uniform cell size for all 

payload types, using standardized ATM packets, or cells. The structure 

of the cell payload can differ, allowing for a variety of traffic types to be 

sent in the same way. A virtual circuit is set up from source to 

destination, then all packets are sent along this path in sequence. 

ATM networks are able to adapt to the differences between voice and 

data: 

� Uncompressed voice is generated at a constant rate, whereas for 

data, the bit rate can vary. 

� Voice circuits are always synchronous, and must maintain strict 

adherence to an internal clock. Transmission delays are avoided. 

� Data transfer is often asynchronous, and its timing is irrelevant. 

Transmission delays can be tolerated. 



ATM Switching 

� The bandwidth required for voice transmissions remains constant 

through time, but tends to be bursty for data. With ATM, high 

bandwidth requirements are met by using a greater number of cells. 

The number of cells is reduced during low traffic periods. 

ATM offers greater efficiency, higher speeds and higher capacity as a 

result of its uniform cell size, which facilitates both transmission and 

switching, and its reduced requirements for flow control and error 

handling. 

Virtual Paths (VPs) and Virtual Channels (VCs) are switched (or crossconnected) 

according to the vendor-specific proprietary techniques of 

each ATM switch used. 

� Usually cells are taken from input links and placed into buffers, 

where they can be read out to other links. Switch size is a function 

of buffer speed versus message delay tolerance. 

� The ATM switch can process cells far more rapidly than the 

transmission rate of ATM traffic, so there is usually very little 

switching delay. There are two types of ATM switches: 

� Virtual path switch: Terminates virtual path links, and 

translates the virtual path identifier for a group of virtual 

channels. With this type of switch, all virtual channels are 

switched to a new virtual path link. 

� Virtual channel switch: Translates both the virtual channel and 

the virtual path identifiers, and can switch a virtual channel from 

one virtual path to another. 

� Quality of Service (QoS) levels are negotiated at the time of service 

provisioning, and are application and service dependent. 

ATM Support on the NetPerformer 

The ATM option is available on the NetPerformer when installed with at 

least one T1/E1 card. It is sold under special license only, and requires 

installation of the product key on every NetPerformer unit in the ATM 

application. It can be installed onto either a standard NetPerformer or 

NetPerformer SIP VoIP base. For installation instructions refer to the 

V9.x addendum to the NetPerformer System Reference Manual, 

available on the NetPerformer Online Reference CD. 

With the ATM option, a customer can access different network services 

via ATM from a single unit. Figure 6 illustrates the many ways that the 

NetPerformer can provide ATM access. 



PSTN 

Voice 

Internet 

4 

10 

Gateway Controller 

9 

8 

Figure 6 ATM Access from the NetPerformer 

The circled numbers in Figure 6 refer to the following access types: 

1. Access interface: From the NetPerformer to the ATM network there 

is a single T1 or E1 connection provided from a T1 or E1 interface 

card installed in the NetPerformer unit. 

2. LAN traffic: This traffic, generally IP, can be transported over ATM 

using the following methods: 

� PowerCell technique, using a PVC in ATMPVCR mode. 

Note: PowerCell allows for the convergence of voice, video, LAN 

and SNA traffic onto a single ATM PVC. Frames created by 

PowerCell are transmitted using ATM AAL5, and comply to the 

FRF.8 interworking standard. The remote device must be another 

NetPerformer, which can be connected to either an ATM network 

or a Frame Relay network. 

� Multiprotocol over ATM AAL5 (RFC-1483), using a PVC in 

RFC1483 mode 

� PPP over ATM AAL5 (RFC-2364), using a PVC in ATMPPP mode. 


ATM FR 

IAD 

1 

ATM 

3 

6 

OR 

5 

LAN 

2 

Frame Relay 

Management 

System 

ATM 

Switch 

7 

IAD


3. Frame Relay traffic: This traffic usually comes from an external 

router. Frames from this router are converted to ATM cells using a 

PVC in FRF.8 mode (Service Interworking). 

4. Voice traffic: Voice interfaces can be analog (FXO, FXS, E&M) or 

digital (T1/E1), and are linked to DSPs that support a full range of 

voice processing services. 

� On the standard NetPerformer, Voice over ATM traffic is 

supported with a PVC in AAL1 mode. 

� On the standard NetPerformer and NetPerformer SIP VoIP, Voice 

over ATM is supported with PowerCell, using a PVC in ATMPVCR 

mode. 

5. Link to legacy ATM application: The NetPerformer can be linked 

to an ATM switch using two PVCs: 

� One PVC in RFC1483 or ATMPPP mode for data transport, 

� One PVC in AAL1 mode (standard NetPerformer only) for voice 

transport using circuit emulation. 

Note: Voice compression is not available in this mode. 

6. Link to Frame Relay device: The NetPerformer can be linked to a 

remote Frame Relay device using the following methods: 

� PowerCell technique, using a PVC in ATMPVCR mode, 

� One PVC in RFC1483 mode for data transport, an FRF.8 

interworking device placed between the ATM network and the 

Frame Relay network, and multiple PVCs using AAL5/RTP mode 

for voice transport. 

7. Link to another Integrated Access Device (IAD): Using the 

same methods as in number 6. 

Note: Most service providers are unable to reliably prioritize one 

PVC against another. When the NetPerformer is linked to another 

IAD over ATM, congestion could occur on ingress traffic. 

8. Link to a gateway controller or network management 

system: Usually these devices will be located in enterprise 

headquarters. 

Typically this requires a specific PVC configured in RFC1483 mode 

for access to the operation centers. However, the gateway controller 

and management system could be collocated with the ATM switch 

(as in number 5) or anywhere in the IP network. 

9. Internet access: Can be provided with the following: 

� PPP over ATM AAL5 (RFC-2364), using a PVC in ATMPPP mode, 

� Multiprotocol over ATM AAL5 (RFC-1483), using a PVC in 

RFC1483 mode. 

10. PSTN Access: Can be provided with a PVC in AAL1 mode for voice 

transport using circuit emulation (standard NetPerformer only), as 

described in number 5. 



SkyPerformer Option Characteristics 

SkyPerformer is a licensed software option that provides satellite 

access functionality to the NetPerformer product line. 

� With SkyPerformer, a hybrid terrestrial/satellite network is created 

using a single hardware platform and network management system. 

� This solution is able to exploit the broadcast nature of satellite 

communications, while taking advantage of powerful NetPerformer 

features. 

Note: The SkyPerformer network solution requires external third-party 

satellite modems that operate up to 2 Mbps. 

Figure 7 SkyPerformer Hybrid Network 

The SkyPerformer software is based on Frame Relay standards and 

offers a scalable solution for both remote and central sites: 

� Permits seamless communication with any Frame Relay compliant 

equipment such as FRADs, routers and switches. 

� Goes where terrestrial Frame Relay cannot, providing a costeffective 

solution for small to medium sized satellite networks. 

� Efficiently consolidates voice, data and LAN traffic with terrestrial 

Frame Relay networks and equipment. 

� Offers a hubless VSAT solution that requires neither an expensive 

DAMA computer nor a central site switch (TDMA). 

� Supports a wide variety of satellite network topologies: single or 

distributed star, partially meshed, point-to-point and multipoint 

networks. 

� Interfaces with all third-party satellite modems. 

� As it is mounted on the NetPerformer platform, it offers all the 

advantages and features of the NetPerformer base software. 



The SkyPerformer option offers a superior solution to the point-to-point 

Single Channel Per Carrier (SCPC) approach, as it requires fewer 

satellite carriers, uses less hardware and may dispense with a central 

site PBX or host. This provides a significant reduction in bandwidth and 

considerable cost savings. 

SkyPerformer also provides better performance. There is no double-hop 

satellite delay for voice/data traffic, and no double compression 

required for voice. 

SkyPerformer Applications 

The SkyPerformer satellite network solution is ideal for: 

� Voice/data enterprise solutions via satellite 

� T1/E1 voice trunking via satellite, where digital voice traffic from 

multiple E1 channels is sent to remote sites using a satellite 

connection 

� Internet backbone extension via satellite, where a NetPerformer 

gateway with SkyPerformer can provide Internet access to multiple 

POP/ISP sites via satellite, supporting connections to PSTN, ISDN 

and ADSL modems 

� Public Frame Relay network extension via satellite. 

� Hybrid terrestrial/satellite networks with a mix of voice and data 

� Networks that start small and need to grow. SkyPerformer and its 

NetPerformer base provide modular expansion capabilities. 

� Multiplexer/SCPC modem networks, especially for multipoint 

applications 

� Small to medium-sized enterprise networks: 

� Star networks with up to 150 sites 

� Distributed star networks with an unlimited number of sites 

� Mesh networks with up to 50 sites. 



Switch 

E1 30 

Voice 

E1 30 

Voice 

MAIN 

HEADQUARTERS 

Regional 

Unit 

REMOTE SITES 

Figure 8 T1/E1 Voice Trunking via Satellite 

GATEWAY 

Central 

Site Unit 

INTERNET BACKBONE 

Regional 

Unit 

Figure 9 SkyPerformer Internet Backbone Extension 


2 Mbps 

128 Kbps 

128 Kbps 

128 Kbps 

Regional 

Unit 

Regional 

Unit 

Regional 

Unit 

REMOTE SITES 

POP/ISP 

Branch 

Office Unit 

Dial-up 

Modems 

POP/ISP 

Branch 

Office Unit 

Branch 

Office Unit 

ISDN 

Modems 

POP/ISP 

ADSL 

Modems 

E1 30 

Voice 

E1 30 

Voice 

E1 30 

Voice 

Bypass 

Operators 

PSTN 

Cellular 

Switch 

PSTN 

ISDN 

ADSL


PBX 

LAN 

SNA Host 

SNA Host 

PBX 

Regional 

Unit 

MAIN 

HEADQUARTERS 

Central 

Site Unit 

Figure 10 SkyPerformer Frame Relay Network Extension 

Frame Relay Switching over Satellite 

Router 

Public Frame Relay 

Branch Office 

Unit 

With the SkyPerformer, Frame Relay switching over satellite is achieved 

in the following way: 

� When the SkyPerformer at the main headquarters transmits to the 

remote sites: 

� DLCI addresses are included in the frame headers according to 

Frame Relay standards 

� Supports Multiple-Address Per Carrier (MAPC) 

REMOTE SITES 

Branch Office 

Unit 

Small Branch 

Office Unit 

Branch Office 

Unit 

� A connection is made when the remote unit receives the carrier 

from the transmitting site 

� Each remote unit filters all packets received, and keeps only 

those packets that carry its unique DLCI address. 

� When the remote SkyPerformer units return traffic to the main 

headquarters: 

� Each remote unit transmits at a different frequency 

� The receiving unit filters all packets received using Transmit/ 

Receive Address Filtering. Packets that are not addressed to the 

unit are discarded. 

� When remote SkyPerformer units send traffic to other remote 

units in addition to main headquarters, the result is a partial 

mesh topology. 


PBX 

LAN 

PBX 

PBX 

LAN 

LAN 

LAN


Note: A demodulator can receive at a single frequency only. For 

each frequency required, you must connect a separate demodulator 

to the NetPerformer. For further information and examples, consult 

the SkyPerformer Satellite Access Option User Guide, available on 

the NetPerformer Online Reference CD. 


Getting Started 

This chapter provides information on preparing the NetPerformer unit 

for network configuration (detailed in Chapter 3) and monitoring 

(Chapter 4), including two means of accessing the configuration 

parameters, statistics displays and other functions: 

� The console, using a direct connection, dialup line or TELNET access 

(page 50) 

� The SNMP management system, using TCP/IP routing (page 64). 

This chapter also provides an overview of: 

� Some of the upper-level NetPerformer console commands (page 56) 

� The major SNMP categories of MIB variables (page 64). 

If you are not fully familiar with the NetPerformer console and 

Management Information Base (MIB) you should review this chapter 

before you commence configuration of the unit. 

Note: If you have not already installed the NetPerformer unit in an 

appropriate location, refer to Chapter 4, Hardware Installation of the 

Hardware and Installation Guide for your product. This guide is included 

on the NetPerformer Online Reference CD delivered with the product 

package. 

Setting Up a SIP VoIP Network 

Note: Refer to this section if you are using the NetPerformer SIP VoIP 

option in a SIP-based network. 

The setup of a SIP VoIP network involves the following steps: 

1. Create the SIP VoIP database using a third-party ODBC compliant 

database. See the Clarent Database Administration Guide for 

requirements. 

2. Set up, configure and start both primary and secondary Command 

Centers, referring to the Clarent Command Center User Guide. 

3. Set up, configure and start the Call Managers and any supported 

H.323, SIP or CPE gateways and clients. For more information, see 

Clarent Call Manager User Guide and Clarent Gateway User Guide. 

Once started, a gateway or Call Manager automatically attempts to 

connect to its primary Command Center. 


2

Getting Started Doc. No. 620-0120-001 

Configuring the NetPerformer from the 

Console 

When you first take the NetPerformer unit out of the box, the only 

configuration device you can use is a console terminal, since the unit 

does not yet have an IP address. 

Connecting the Console Terminal 

NetPerformer with Factory Configuration 

When the NetPerformer is loaded with the factory default configuration 

(no IP address defined), the console terminal must be connected 

through a direct or dialup connection to the console port on the unit. 

The console port is autospeed, which means the NetPerformer sets the 

speed of the port as soon as it detects an active connection. 

� Available console speeds are 1200, 2400, 4800, 9600, 19200, 

28800, 38400, 57600 and 115200 bps. 

� The equipment you connect to the console port must operate at one 

of these speeds. 

The device you connect to the console port can be: 

� An asynchronous dumb or TTY terminal, or 

� A PC equipped with asynchronous terminal emulation software. 

NetPerformer with IP Address 

To use an alternate management access device for configuration and 

monitoring purposes, the NetPerformer unit must be defined with an IP 

address. You can either configure the Ethernet port with an IP address, 

or have an IP address assigned to Ethernet port automatically using 

DHCP. 

To configure the IP address: 

� Connect the NetPerformer console following the instructions in 

Direct Connection on page 52 or Dialup Connection on page 53. 

� Access the SETUP/PORT menu from the NetPerformer console 

command set. Refer to Setup (SE) Command on page 60. 

� Select the Ethernet port (ETH). Refer to Configuring a LAN Interface 

on page 84. 

� Set IP address #1 or IP address #2 on the Ethernet port to an IP 

address that is unique in your network. 

To have an IP address assigned to Ethernet port automatically using 

DHCP, refer to the next section, DHCP Connection. 



Once you have configured an IP address for the unit the following 

configuration and management access types may be used as an 

alternative to direct or dialup connection: 

� A TELNET network device, or 

� An SNMP agent. 

Note: Both of these methods are available through IP connectivity over 

LAN/WAN. 

DHCP Connection 

Note: DHCP is not an access method to the NetPerformer but rather 

a way to get an IP address on the NetPerformer Ethernet port 

automatically. A Telnet connection to that IP address is still required to 

access the equipment (see TELNET Command on page 55). 

DHCP (Dynamic Host Configuration Protocol) is used in managing large 

IP networks. It allows individual workstations to extract their 

configurations from a server that has no exact information about the 

workstations until they request the information. In most applications, 

the DHCP server uses the requesting station’s MAC address to uniquely 

identify it. 

The most significant piece of information distributed in this way is the 

IP address. This method of IP address assignment reduces the overall 

work required to administer a large IP network. DHCP is particularly 

useful in delivering a functional and unique IP address to computers 

accessing the Internet. 

DHCP allows for: 

� Dynamic allocation of network addresses and configurations to 

newly attached hosts. 

� Routing of network addresses. 

� Recovery and reallocation of network addresses through a leasing 

mechanism. 

Note: A DHCP lease is the amount of time that the DHCP server 

allows a particular client to use a particular IP address. The lease 

time is configured on the server side. 

These features allow you to unplug a DHCP-enabled NetPerformer unit 

from one network or subnet, plug it into another and have it come alive 

immediately, since it is reconfigured automatically. 

Note: DHCP dynamic reconfiguration requires a DHCP server, the DHCP 

forwarding agent (included with the NetPerformer software), and DHCP 

capability enabled in each client’s TCP/IP support (configurable by the 

user). 

To enable DHCP on the NetPerformer: 

� Connect the NetPerformer console following the instructions in 

Direct Connection on page 52 or Dialup Connection on page 53. 



Direct Connection 

� Access the SETUP/PORT menu from the NetPerformer console 

command set. Refer to Setup (SE) Command on page 60. 

� Select the Ethernet port (ETH). Refer to Configuring a LAN Interface 

on page 84. 

� Set the DHCP parameter of the Ethernet port to ENABLE. 

To connect directly to the console terminal: 

1. In the NetPerformer product package, locate the standard RS-232/ 

V.24 straight through cable with a DB-9 female connector at one end 

and a DB-25 male connector at the other end. 

2. Connect the DB-9 connector on this cable to the NetPerformer 

console port, labelled CONSOLE. 

3. Connect the DB-25 connector to a COM port on the console terminal 

or PC, or to a modem for dialup connection to a remote console. 

4. Power the console terminal ON and ensure that the NetPerformer 

unit is also ON (refer to the Hardware and Installation Guide for your 

product). 

Note: NetPerformer system startup can take several minutes to 

execute. The console cannot be accessed before this process is 

complete. 

5. Press the Enter key on the console terminal keyboard several times, 

until the NetPerformer responds with a prompt for the user login 

(LOGIN:). 

6. Enter the administrator login: ADMIN. 

Note: No other login is available from the factory default 

configuration. At a later time you can define other user logins with 

FULL or MONITOR status (see Defining User Access Profiles on 

page 70). 

7. Enter the password for the ADMIN login. 

� The default password for the administrator login is SETUP. 

Note: To change this password, enter CP at the NetPerformer 

console command prompt, and follow the instructions on the 

screen. 

Caution: Do not lose your new password. If you lose or 

forget your administrator password, contact NetPerformer 

Technical Support to determine whether a bypass 

procedure can be carried out using the service password. 



Dialup Connection 

When the password is entered correctly, the NetPerformer sends the 

product banner to the console screen, as in this example: 

LOGIN:ADMIN 

PASSWORD:***** 

ACCEPTED 

SDM-9360 vX.X.X Verso Technologies, Inc. (c) 2004 

Signaling Engine X.X.X 

DSP Operational Code, (G.711, ACELP) Ver. X.X.X.X 

Console connected on port CSL 

Display commands, type HE 

B302417> 

The last line of this example shows the default command prompt, which 

displays the burned-in serial number of the base board. Once the Unit 

ID is defined using the SETUP/GLOBAL menu (see Defining the Global 

Characteristics on page 71) the console command prompt shows the 

current Unit ID. 

Note: In the screen captures provided in this guide, the console 

command prompts indicate which product or option is portrayed, as 

follows: 

Console Command 

Prompt 

NetPerformer Product or 

Option 

CHICAGO> Standard NetPerformer 

BOSTON> NetPerformer SIP VoIP 

CALGARY> ATM Option 

SEATTLE> SkyPerformer Option 

You can access a local or remote NetPerformer unit using a dialup line 

between an asynchronous modem connected to your console terminal 

and another asynchronous modem connected to the console port on 

the remote unit. 

To connect the modem to the NetPerformer you can use a straight RS- 

232 cable, with two configuration options: 

� Auto-learning mode: Connect a straight RS-232 cable to a modem 

or PC (async terminal), and leave the console port in its default 

auto-learning mode. 

� Manual configuration of the console port: 

� Set the console port to DCE mode using the Interface parameter 

of the SETUP/PORT menu, and use a straight RS-232 cable to 

connect to a PC (async terminal). 

� Set the console port to DTE mode using the Interface parameter 

of the SETUP/PORT menu, and use a straight RS-232 cable to 

connect to a modem. 



Note: Using an RS-232 cross-over cable is supported but not 

required, due to the flexibility of the NetPerformer console. 

To access the remote NetPerformer console: 

1. Ensure that the remote NetPerformer unit is powered ON. 

2. Using dialup software installed on the local console terminal, 

execute the AT command atd0 to set the modem to ignore DTR. 

Note: This step is required since the NetPerformer cannot supply 

DTR to the modem when in auto-sensing mode (the default setting). 

3. Dial the number of the remote modem. 

4. Continue with step 5 on page 52. 

Accessing a Remote NetPerformer Console 

From the local NetPerformer site you can configure and manage any 

remote NetPerformer in the network using the console commands. 

Several access methods are available: 

� The NetPerformer Relay (RE) command (see Relay (RE) Command, 

below). This access method relies on a WAN connection between the 

local and remote sites. Refer to Configuring a WAN Link on page 90. 

� A TELNET connection (see page 55). This method requires IP 

connectivity, including access to an Ethernet LAN and a unique IP 

address defined on both the local and remote units. 

� An SNMP agent (see page 64), which requires IP connectivity and an 

SNMP management device, for example, a PC equipped with the 

ACTView 3000 Network Management System (NMS). 

Relay (RE) Command 

To access a remote console using the Relay command: 

1. Enter RE at the local console command prompt. 

2. Enter the Unit name of the remote NetPerformer. 

3. Press Enter three times to connect to the remote unit. 

4. Enter a user login for the remote unit. 

5. Enter the password for this user login. 

Once the password is accepted, the remote NetPerformer sends its 

product banner to the local console screen. 



Each line from the remote console is preceded by a plus sign (+), as in 

the following example: 

BOSTON>RE 

RELAY 

Unit name (def:) ? CHICAGO 

Press ENTER three times to connect 

Press CTRL/Z three times to exit 

+ 

+LOGIN:ADMIN 

+PASSWORD: ***** 

+ 

+ACCEPTED 

+SDM-9360 vX.X.X Verso Technologies, Inc. (c) 2004 

+Signaling Engine X.X.X.X 

+DSP Operational Code, (G.711, ACELP) Ver. X.X.X.X 

+Console connected on port CSL 

+Display commands, type HE 

+CHICAGO> 

Note: The Relay command cannot be executed from the remote 

console to create a second hop relay to a third unit. 

To return to the local console: 

1. Quit from the remote console: enter QU. 

2. Press the key combination CTRL-Z three times. 

The local product banner and diagnostics are displayed when the 

console returns to the local unit. 

TELNET Command 

TELNET is an application layer implementation of the TCP/IP protocol 

that permits logging onto a remote NetPerformer for configuration and 

diagnostic purposes. With a TELNET connection to a NetPerformer unit, 

you type the same console commands as for a direct or dialup 

connection. It is an entirely transparent emulation application that 

gives the appearance that your terminal is attached directly to the 

remote NetPerformer. 

TELNET access requires an Ethernet LAN connection using either: 

� The local LAN attached to the NetPerformer at your site, or 

� A remote LAN whose data is transmitted to the local unit through a 

WAN connection. 

Note: Because the default IP address of the NetPerformer LAN port is 

not unique (default value 000.000.000.000), you cannot use TELNET to 

access a remote unit until you define the IP address #1 or IP address 

#2 parameter (see Configuring a LAN Interface on page 84) or enable 

DHCP on the unit (see DHCP Connection on page 51). 

To execute TELNET from the local console: 

� Enter TELNET remote_ip_address at the console command line. 

The product banner of the remote unit is displayed at the local 

console when the TELNET connection is complete. 



Console Conventions 

Note: Access to the NetPerformer console via a TELNET connection can 

be restricted to up to five addresses, or disabled altogether. For details, 

refer to TELNET Access on page 80. 

All NetPerformer console operations are controlled by a set of console 

commands that are executed from the command line. 

� To activate a command, type the appropriate command abbreviation 

on the command line and press the Enter key or carriage return on 

your console keyboard. 

Note: Refer to Conventions on page 18 for an explanation of the 

command notation used in this guide. 

� The HELP command provides an alphabetical list of all available 

commands; enter HE. 

� To abort a command or return to the next higher menu level, press 

the Esc key. 

Changing Parameter Values 

Caution: The NetPerformer does not perform full form checking. 

When you configure the unit, it does not carry out intensive 

validation of the parameter values you enter. Be careful to 

enter values that are appropriate for your application. 

When you activate a command, you may be given a list of questions for 

selecting parameter values. 

� To select the default value press the Enter key. 

� To select another value, type it on the command line and press Enter. 

The value you type can be an abbreviation, as long as it is distinct 

from all other valid values. 

Note: For some parameters a list of valid parameter values is not 

provided with the default value. Type ? followed by Enter at the 

command prompt to view a list or range of appropriate values. 

� All changes to parameter values are applied immediately to the 

configuration file. If you do not need to adjust all parameters within 

a category or menu, press the Esc key. 

Note: There are some exceptions to this general rule. For example, 

when setting a customized ring cadence on the unit you must set all 

parameter values, as they are interdependent. 



Arrow Keys 

Caution: New parameter values are not saved automatically 

until the global Auto save configuration delay has expired 

(default 10 seconds). If you reset the NetPerformer (with the 

RU command) or power off the unit within this delay, the 

configuration will revert to the last saved version. To avoid this 

in cases where the save delay is long, execute the Save 

Configuration Profile (SP) command, which manually saves all 

current values of the configuration parameters. 

Use the arrow keys to simplify command entry and correct what you 

type: 

� ↑ (Up Arrow): At a command prompt, recalls the previous 

character string you entered at the console command line. At a 

parameter prompt, displays the previous value to the left in the 

selection list. 

� ↓ (Down Arrow): At a command prompt, recalls the next character 

string you typed at the console command line. At a parameter 

prompt, displays the next value to the right in the selection list. 

� ← (Left Arrow): Moves the command cursor to the next character 

to the left. Use this to insert or delete characters in the string. 

� → (Right Arrow): Moves the command cursor to the next character 

to the right. 

NetPerformer Console Operations 

Commands that govern console operations include: 

� HELP (HE), discussed in the next section 

� Reset Unit (RU), on page 59 

� Quit (QU) on page 59. 

Help (HE) Command 

The console HELP command (HE) provides a list of all NetPerformer 

console commands in alphabetical order. To view the list of all 

NetPerformer commands: 

� Enter HE at the console command prompt. 

The complete command list, as produced from the console of a 

standard NetPerformer by a user with FULL console access, is shown on 

the next page. To execute any of these commands, type its 

abbreviation and press the Enter key. 

Note: The NetPerformer SIP VoIP option does not include the 

commands Continuous Display of SVC States (DSVC), Erase Log File 

(EL) or Load Firmware (LF). 



: 

CALGARY>HE 

HELP 

AP...........Display active PUs 

ARP..........Display/Clear ARP cache 

CA...........Clear software alarms 

CALL.........Manual link activation 

CE...........Clear ERR/DIAG LED 

CHKFS........Check File System 

CL...........Capture PVCR frame length 

CN...........Clear NAT entry 

COPY.........Copy file 

CP...........Change password 

DA...........Display software alarms 

DB...........Display bridge statistics 

DBA..........Display bridge addresses 

DC...........Display counters 

DCFG.........Display config 

DCS..........Display channel states 

DD...........Display destination table 

DDLCI........Continuous display of PVC DLCI states 

DE...........Display errors 

DEFRAG.......Defragment file system 

DELETE.......Delete file 

DIR..........Display file list 

DJOURNAL.....Display journal 

DL...........Display log 

DMF..........Display Map file 

DN...........Display NAT table 

DNS..........Display/Clear DNS cache 

DP...........Display configuration parameters 

DPORT........Continuous display of port states 

DPU..........Continuous display of PU states 

DPVC.........Continuous display of PVC states 

DR...........Display routing table 

DS...........Display states 

DSI..........Display slot information 

DSPA.........DSP allocation menu 

DSVC.........Continuous display of SVC states 

DT...........Display the current time 

DV...........Display software version 

DX...........Display cell relay connections 

EC...........End capture 

EL...........Erase Log file 

EMF..........Erase Map file 

EP...........Extended Parameters 

ER...........Display Exit Record 

FORMAT.......Format file system 

FS...........Install factory configuration 

HANG.........Manual link de-activation 

HE...........Display commands 

LF...........Load Firmware 

LT...........Loopback test 

PING.........PING remote unit 

PLS..........Product license status 

QU...........Terminate current session 

RC...........Reset counters 

RE...........Relay to remote unit 

RP...........Reset port 

RU...........Reset unit 

RZ...........Receive ZModem 

SZ...........Send ZModem 

SC...........Setup capture 

SE...........Configure unit 

SEC..........Signaling Engine channels 

SEI..........Signaling Engine information 

SP...........Save Current Configuration Profile 

ST...........Set time 

STARTTONE....Start test tone 

STC..........Start capture 

TELNET.......Telnet to a remote unit 

TRACEROUTE...Trace IP Route 

UT...........Update time from time server 

VC...........View capture 



Reset Unit (RU) Command 

To reset the unit software: 

� Enter RU at the console command prompt. 

� Enter YES at the confirmation prompt. 

Here is an example: 

Note: This command disconnects the asynchronous terminal console 

from the NetPerformer. To reactivate the console after the reset is 

complete (which may take several minutes) press the Enter key three to 

five times. 

Quit Console (QU) Command 

The Quit command (QU) disconnects the asynchronous terminal 

console from the NetPerformer console port without resetting the 

software. To do this: 

� Enter QU on the command line. 

Configuration Commands 

BOSTON>RU 

RESET UNIT 

Reset unit, please confirm (NO/YES,def:NO) ? YES 

Unit restarted ! 



BOSTON>QU 

QUIT 

Exit from console, please confirm (NO/YES,def:NO) ? YES 

Console disconnected ! 

To reactivate the console press the Enter key three to five times. 

The major configuration commands that can be executed from the 

NetPerformer console are: 

� Setup (SE), discussed in the next section and detailed in Chapter 3, 

Configuration. 

� Factory Setup (FS), on page 62. 



Setup (SE) Command 

The Setup (SE) command allows you to adjust the current configuration 

of the NetPerformer unit. To execute this command. 

1. Enter SE. 

2. Enter the name of the Item you want to configure. 

A list of configurable items is provided for you. Each item is a 

submenu dedicated to the configuration of one aspect of 

NetPerformer functionality. 

3. If several components can be configured using the same Item 

selection, select one of these components. 

For example, the SETUP/PORT menu is used to configure the LAN, 

console and serial ports. To configure port 2, you must set Port 

number to 2: 

CHICAGO>SE 

SETUP 

Item (GLOBAL/PORT/SLOT/PU/SCHEDULE/IP/BRIDGE/PHONE/CALLER ID/FILTER/ 

CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:GLOBAL) ? PORT 

Port number (ETH/CSL/1/2,def:1) ? 2 

PORT #2> Protocol (def:FR-USER) ? 

... 

4. A set of questions, or parameters, is presented for selecting all 

configurable values for the item you have chosen. Respond to each 

parameter prompt by entering the desired value, or press Enter to 

select the default value. 

Note: The default value is displayed after the parameter name, and 

is indicated by def: (see example above). It is optionally preceded by 

a list of valid values, as for the Port number parameter. 

SE Command Submenus 

The SE command submenus (or Items) include the following: 

� GLOBAL: Parameters that affect the unit as a whole. 

� PORT: Parameters controlling the LAN, console and serial (WAN/ 

user) port functions. 

� SLOT: Parameters governing the physical ports and logical channels 

on the interface cards that can be inserted in a slot on the 

NetPerformer unit, including digital T1, E1 and ISDN-BRI S/T, analog 

FXS, FXO and E&M, and the Dual Serial interface card. 

� PU: Parameters for the PUs in an SNA/SDLC application. 

� SCHEDULE: Parameters that define the time periods governing WAN 

link (PVCR) operating modes. 



� IP: Parameters that control IP routing on the NetPerformer. SE/IP 

includes several submenus: 

� GLOBAL: Parameters governing general IP routing characteristics 

that affect the unit as a whole. 

� STATIC: Parameters that enable IP routing to a particular 

destination. 

Note: If IP RIP is disabled on all unit connections, an IP static 

route must be defined for each destination that requires IP 

routing. Otherwise, IP static routes are optional. 

� BOOTP: Parameters required to set up the BOOTP relay agent 

function. 

� OSPF: Parameters that allow the NetPerformer to support a 

network that uses the OSPF routing protocol. 

� TIMEP: Parameters that allow the NetPerformer to adjust the 

system time using the UDP/TCP time protocol. 

� SNMP: Parameters that govern the requests the SNMP agent can 

process with respect to NetPerformer operations, configuration 

and status. 

Note: In order to access the SNMP agent, these parameters 

must be previously set on the console. 

� NAT: Parameters governing NAT operations and connections. 

� TELNET: Parameters that allow network managers to restrict 

access to the NetPerformer via TELNET. 

� FTP: Parameters that allow network managers to restrict access 

to the NetPerformer via TELNET. 

� DNS: Parameters that define DNS (Domain Name Server) 

character-istics required to resolve an IP address based on a 

domain name. 

� BRIDGE: Parameters that enable bridge operations and define the bridge 

characteristics. 

� PHONE: Parameters required to create a directory of phone numbers 

for link backup, Bandwidth On Demand and ISDN phone purposes. 

� CALLER ID: Parameters that define a set of callers authorized to 

access an ISDN connection on the NetPerformer. 

� FILTER: To write user-defined filters that reduce, manage and 

prioritize specific traffic types on the network. 

� CLASS: Parameters that define the bandwidth weights for different 

priority classes. 

� PVC: Parameters for the PVCs used in a Frame Relay or ATM 

application. 

� IPX: Parameters that control IPX routing on the NetPerformer. 

� MAP: Parameters that define speed dial numbers in the Voice 

Mapping Table. 



� CUSTOM: Parameters that permit customization of digital signaling 

and ring characteristics. 

� HUNT: (standard NetPerformer only) Parameters that govern Hunt 

Forwarding for voice and SVC functions. 

� VLAN: Parameters that define the various VLAN segments that can be 

accessed by the NetPerformer. 

� USER: Parameters to create user access profiles that can restrict access 

to sensitive NetPerformer functions. 

� SIP: (NetPerformer SIP VoIP option only) Parameters affecting SIP 

signaling. 

Factory Setup (FS) Command 

The Factory Setup command (FS) returns all NetPerformer 

configuration parameters to their factory default values. To execute this 

command: 

� Enter FS on the console command line. 

� Enter YES at the confirmation prompt. The default factory setup will 

be installed on the NetPerformer unit. 

Warning: When the FACTORY SETUP command is executed, it 

takes effect immediately. You cannot return to your previously 

defined configuration values. We suggest that you make a 

complete inventory of your configuration parameter values 

before you execute this command. To do this, either print out 

the results of the Display Parameters - ALL command (DP/ALL) or 

store your configuration using the FTP get command. 

Note: It is also possible to customize a default configuration that 

preserves essential parameter values when executing the FS 

command. To do this, you must create a file named CFG_RST.TXT 

using the NetPerformer text-based configuration function. To create 

this default configuration file you can either: 

� Rename a CFG.TXT file with the RENAME console command, as 

follows: 

RENAME CFG.TXT CFG_RST.TXT 

or 

� Download file CFG_RST.TXT from another NetPerformer unit. 

Download procedures are provided in the Hardware Installation 

Guide for your particular NetPerformer model. 

Note: Text-based configuration provides an alternative method for 

configuring the NetPerformer, where the configuration file is created 

in text format and can be edited with a text editor. It provides a 

quick method for copying parameter settings from one configurable 

item to another of the same type, or from one NetPerformer unit to 

another. For details, consult the NetPerformer System Reference 

Manual (Administration Guide) or the Addendum to the System 

Reference Manual for V9.0.0 to V9.2.0. 



Here is an example of the Factory Setup command: 

BOSTON>FS 

FACTORY SETUP 

Default factory setup (NO/YES,def:YES) ? YES 

Factory setup, please confirm (NO/YES,def:NO) ? YES 

Factory setup installed ! 

Note: After executing a Factory Setup, we recommend that you 

carefully redefine all ports and PVCs that are required for the network 

application. All unused ports and PVCs should be turned off. 

The factory setup can be customized to the country code you would like 

to use for voice/fax communications. This allows for the integration of 

country-specific default settings for certain voice port parameters, in 

particular, for Japan, Mexico and Brazil. 

To select a country-specific factory setup: 

1. Enter FS at the console command prompt. 

2. Enter NO at the confirmation prompt. 

3. Enter the Country Code. If you do not know the code, enter ? to 

display a list of all available country codes in alphabetical order by 

country. At the end of this list the Country code prompt will be 

displayed again for your input. 

4. Enter YES at the confirmation prompt to start the factory setup. The 

confirmation message includes an indication of the country for which 

the factory setup is made. 

Here is an example of a factory setup customized for Venezuela: 

BOSTON>FS 

FACTORY SETUP 

Default factory setup (NO/YES,def:YES) ? NO 

Country code (0-999,def:1) ? ? 

Algeria ==> 213 

Argentina ==> 54 

Australia ==> 61 

• 

Venezuela ==> 58 

Wales ==> 44 

Yugoslavia ==> 38 

Zaire, Rep. ==> 243 

Zambia ==> 260 

Zimbabwe ==> 263 

Country code (0-999),def:1) ? 58 

Factory setup, please confirm (NO/YES,def:NO) ? YES 

Factory setup installed for Venezuela, 

Unit restarted ! 



Configuring the NetPerformer with SNMP 

SNMP Compatibility 

All NetPerformers in your network can be configured and managed 

under SNMP (Simple Network Management Protocol), a standard 

protocol for monitoring IP gateways and networks. SNMP is a TCPbased 

network management protocol that runs on UDP. Through the 

SNMP agent, you can communicate with any other unit in the network 

using your standard network management system. 

To configure the NetPerformer using SNMP, a connection to an Ethernet 

LAN is required. The SNMP console can be part of the local LAN or a 

remote LAN whose data is transmitted to the local unit through a WAN 

connection. 

SNMP provides a standard means of communicating between network 

management stations and the SNMP agents in the network elements, 

allowing the NetPerformer to send and receive information about 

network resources. The SNMP agent on the NetPerformer takes 

advantage of its port addressing capability to establish separate 

connections between network devices. 

The NetPerformer keeps statistics on the status of its network 

interfaces, incoming and outgoing traffic, dropped frames and error 

messages generated. The SNMP agent allows network managers to 

access these statistics through a set of variables (equivalent to console 

parameters) and traps (equivalent to console alarms). All configuration 

and management operations are a side-effect of fetching or storing to 

these variables. 

The base for SNMP communication is the Management Information 

Base (MIB), which stores information about the network resources. The 

MIB designed for the NetPerformer is composed of two major 

components: 

� MIB II, a standard definition that defines the data layout (length of 

fields, what the field is to contain, and so on) 

� The NetPerformer MIB extension, which incorporates unique 

information about the NetPerformer and its configuration. 

To handle the SNMP agent, the NetPerformer includes support of the 

following layers of the TCP/IP stack: 

� IP (Internet Protocol), the TCP/IP standard protocol that defines the 

IP datagram and provides packet delivery service 

� ARP (Address Resolution Protocol), the TCP/IP protocol that 

supports hardware broadcast across a single network 

� ICMP (Internet Control Message Protocol), part of the IP protocol 

that handles control and error messages 



� UDP (User Datagram Protocol), the TCP/IP protocol that governs the 

transmission of datagrams between application programs on 

different machines. 

On the NetPerformer, the SNMP agent itself is configured with the 

SNMP submenu of the console Setup IP command (SE/IP/SNMP). The 

TCP/IP stack is configured with parameters in the Setup Port (SE/PORT) 

and Setup PVC (SE/PVC) menus, which are accessed through the 

console or the SNMP agent itself. 

Accessing the SNMP Agent 

Your SNMP console may be part of: 

� The local LAN attached to the NetPerformer at your site, or 

� A remote LAN whose data is transmitted to the local unit through a 

WAN connection. 

To reach the NetPerformer using the SNMP agent, the unit must first be 

configured with a unique IP address. Refer to NetPerformer with IP 

Address on page 50. 

Although the structure of SNMP is standard, the means of accessing it 

is not. Various software manufacturers have devised proprietary access 

procedures, and no two are exactly alike. We suggest that you consult 

your SNMP program guide if you are not fully familiar with the startup 

and logon process for your system. 

In general, once you have started SNMP: 

1. Send the NetPerformer MIB to the SNMP program for compilation. 

2. Once the MIB has been compiled, select the SNMP agent for the 

NetPerformer. 

3. When you access the SNMP agent, you will find all system variables 

under the private/enterprise/presticom/netperformer7/npmgmt 

heading. 

4. These variables are grouped by function under several categories, 

for example, npsystem, ifwan, iflan, ifvce and pu. Select the 

category for the function you want to perform. 

Note: A table of correspondences between SNMP categories and 

console submenus is provided in the next section. 

5. When you select a category, two classes are displayed: Info and 

Table. Select Table to view a list of table entries, which are 

subheadings for groups of objects. 

6. When you select a particular table entry you will see a display of the 

individual objects that pertain to that entry. These objects are the 

variables used to fetch and store information concerning the 

network resources. Read/write variables are configurable 

parameters. Read-only variables are provided for information 

purposes and statistical displays. 



Example: If you want to enable SIP registration using SNMP, select the 

following sequence of variables: 

npmgmt -npsip - npSipGlobal - npSipRegistration - enable. 

Note: The above format is used when navigating the NetPerformer 

private MIB with a MIB browser. With the ACTView 3000 Network 

Management System, a more intuitive Graphical User Interface (GUI) is 

available for setting the SNMP parameters, and the MIB variables 

themselves are transparent to the user. 

NetPerformer MIB Categories 

The NetPerformer MIB is organized according to categories, which 

loosely correspond to the Items listed with the Setup (SE) command on 

the NetPerformer console (see SE Command Submenus on page 60). 

Table 1 MIB categories and corresponding console SE 

command submenus 

MIB 

Category Console SE Command 

Submenu(s) 

npsys GLOBAL page 71 

ifwan PORT (port_number), 

SLOT 

(digital_channel_number) 

iflan PORT (ETH) page 84 

ifvce SLOT (channel_number), 

MAP 

pu PU page 192 

schedule SCHEDULE page 199 

bridge BRIDGE page 76 

phone PHONE page 96 

caller CALLER ID page 149 

filter FILTER page 200 

class CLASS page 198 

pvc PVC page 106 

ipx IP/IPX/GLOBAL page 83 

ipxfilter IP/IPX/FILTER page 84 

ipstatic IP/STATIC page 78 

npip IP/GLOBAL page 77 

Section Reference(s) 

in this Guide 

page 90 (WAN) 

page 101 (Frame Relay) 

page 189 (SNA) page 179 

(user) 

page 133 (digital channel) 

page 141 (digital channel) 

page 150 (analog channel) 

page 155 (voice mapping) 



Table 1 MIB categories and corresponding console SE 

command submenus 

MIB 

Category Console SE Command 

Submenu(s) 

ospf IP/OSPF page 119 

bootp IP/BOOTP page 79 

timep IP/TIMEP page 79 

nat IP/NAT page 172 

dns IP/DNS page 82 

hunt HUNT page 162 

npsip SIP page 88 

vlan VLAN page 87 

Other SNMP categories handle functions outside the scope of the 

console SE command: 

� stat, for viewing system statistics 

� intf, which defines the various interface types and their locations 

� slot which defines the slot types and the interfaces they provide 

� ipaddr, for maintaining a list of IP addresses on the unit 

� license, to install an optional firmware license (ATM, SkyPerformer) 

� proxy, for supporting connections to the legacy FP product line 

(standard NetPerformer only). 

The following submenus of the SE command have no equivalent in the 

MIB: 

� USER, TELNET, FTP, for controlling console access 

� CUSTOM, for customization of digital signaling and ring 

� SNMP, for configuration of SNMP characteristics. 

Section Reference(s) 

in this Guide 




Configuration 

This chapter provides the basic information required to properly 

configure a NetPerformer unit from the command console, including: 

� User access profiles (page 70) 

� Global characteristics (page 71) 

� Bridge characteristics (page 76) 

� IP Routing characteristics (page 76) 

� IPX Routing characteristics (page 83) 

� LAN interface characteristics (page 84) 

� Setting up a Virtual LAN (page 87) 

� SIP characteristics, for the NetPerformer SIP VoIP option (page 88) 

� WAN connections (page 90) and satellite links (page 98) 

� Frame Relay connections (page 101) 

� OSPF connections (page 119) 

� DSP allocation of voice algorithms (page 124) 

� Digital T1, E1 and ISDN-BRI S/T voice/data connections (page 125) 

� Analog FXS, FXO and E&M voice connections (page 150) 

� Voice Mapping Table on standard NetPerformer (page 155) and 

NetPerformer SIP VoIP (page 157) 

� Hunt Forwarding on standard NetPerformer (page 162) 

� Custom signaling characteristics (page 163) 

� Network Address Translation (NAT) settings (page 172) 

� Transparent user port characteristics (page 179) 

� SNA device characteristics (page 189) 

� Traffic priority and scheduling (page 197). 

For more details on these topics, refer to the NetPerformer System 

Reference Manual (Administration Guide). Refer to Chapter 2, Getting 

Started for console configuration steps and SNMP management 

techniques. If you are managing the NetPerformer with ACTView 3000, 

refer to the documentation set for that product. 


3

Configuration Doc. No. 620-0120-001 

Note: For most configuration parameters, the range of acceptable 

values and the default value are listed on the console after the 

parameter name. The defaults YES, NO, ENABLE and DISABLE generally 

imply bipolar values. A default value in 4-byte dotted decimal 

representation implies an IP address with a maximum value of 255 for 

each byte. In each section of this chapter, unusual parameter values 

are mentioned after the example from the console. 

Defining User Access Profiles 

Users can have either MONITOR access to the console for monitoring 

NetPerformer operations, or FULL access, which permits configuration 

commands in addition to all other console functions. User profiles are 

configured with the USER submenu of the SETUP console command. 

To assign username and password privileges: 

� Enter the menu sequence: SE ↵ USER. 

The parameters presented at the console are identical for the standard 

NetPerformer and the NetPerformer SIP VoIP option: 

CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:PORT) ? USER 

User profile number (1-10,def:1) ? 2 

USER #2> User Name (def:) ? B SMITH 

USER #2> Change password (NO/YES,def:NO) ? YES 

USER #2> Enter current password: ***** 

USER #2> Enter new password:**** 

USER #2> Re-enter for confirmation:**** 

USER #2> Password changed 

USER #2> Access Privilege (def:FULL) ? MONITOR 

� Up to 10 users can be defined on a single NetPerformer unit. 

� The Access Privilege is either MONITOR or FULL. 

� To permit configuration of the unit, at least one user must have FULL 

access. 

Caution: If you change the User Name of User profile number 1 

from ADMIN to another value, you will no longer be able to use 

the ADMIN username. If, in addition, you have changed the 

Access Privilege of User profile number 1 from FULL to MONITOR, 

you will no longer be able to use the SETUP (SE) command to 

define another User profile with FULL access, or perform any 

other configuration change. Contact NetPerformer Technical 

Support for a workaround using the service password. 

� When a user has MONITOR access, the list of available commands 

shown on page 58 (under FULL access) is reduced to the following: 



LOGIN:B SMITH 

PASSWORD:***** 

ACCEPTED 

Netperformer EG SDM-9360 vX.X.X Verso Technologies, Inc. (c) 2004 


DSP Operational Code, (G.711, G.729/A) Ver. X.X.X.X 


Display commands, type HE 

CHICAGO>HE 

HELP 

AP...........Display active PUs 

CL...........Capture PVCR frame length 

CP...........Change password 

DA...........Display software alarms 

DB...........Display bridge statistics 

DBA..........Display bridge addresses 

DC...........Display counters 

DCFG.........Display config 

DCS..........Display channel states 

DD...........Display destination table 

DDLCI........Continuous display of PVC DLCI states 

DE...........Display errors 

DIR..........Display file list 

DMF..........Display Map file 

DN...........Display NAT table 

DP...........Display configuration parameters 

DPORT........Continuous display of port states 

DPU..........Continuous display of PU states 

DPVC.........Continuous display of PVC states 

DR...........Display routing table 

DS...........Display states 

DSI..........Display slot information 

DSVC.........Continuous display of SVC states 

DT...........Display the current time 

DV...........Display software version 

DX...........Display cell relay connections 

EC...........End capture 

ER...........Display Exit Record 

HE...........Display commands 

LT...........Loopback test 

PING.........PING remote unit 

QU...........Terminate current session 

RE...........Relay to remote unit 

SC...........Setup capture 

SEC..........Signaling Engine channels 

SEI..........Signaling Engine information 

STC..........Start capture 

TELNET.......Telnet to a remote unit 

TRACEROUTE...Trace IP Route 

UT...........Update time from time server 

VC...........View capture 

Defining the Global Characteristics 

The GLOBAL submenu of the SETUP console command includes all 

parameters that affect the unit as a whole. To configure the global 

parameters: 

� Enter the menu sequence: SE ↵ GLOBAL. 

� Change the global parameters from their default values, if desired, 

following the examples below. 



Standard NetPerformer and NetPerformer SIP VoIP Option 

The parameters listed on the standard NetPerformer console are as 

follows: 

B302417>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:GLOBAL) ? GLOBAL 

GLOBAL> Unit name (def:B302417) ? CHICAGO 

GLOBAL> Unit routing version (1-2,def:1) ? 

GLOBAL> Contact name (def:Verso Technologies) ? 

GLOBAL> Unit location (def:Unknown) ? 

GLOBAL> Loopback (def:NO) ? 

GLOBAL> Link timeout delay (0-1000,def:0) ? 

GLOBAL> Transit delay (sec) (1-20,def:4) ? 

GLOBAL> Daylight saving time (def:NO) ? 

GLOBAL> Default IP address (def:000.000.000.000) ? 

GLOBAL> Default IP mask (number of bits) (0-24,def:0) ? 

{000.000.000.000} 

GLOBAL> Default gateway (def:000.000.000.000) ? 

GLOBAL> SNMP trap: IP address #1 (def:000.000.000.000) ? 




GLOBAL> Frame relay status change trap (def:DISABLE) ? 

GLOBAL> Watch power supplies and fans (def:NONE) ? 

GLOBAL> Local unit DLCI address (0-1022,def:0) ? 

GLOBAL> Extension number (no. of digits) (2-4,def:3) ? 

GLOBAL> Country code (0-9999,def:1) ? 

GLOBAL> Jitter buffer (msec) (0-200,inc:10,def:170) ? 

GLOBAL> Enable voice/fax log (def:YES) ? 

GLOBAL> Dial timer (sec) (0-10,def:4) ? 

GLOBAL> High priority voice class (def:YES) ? NO 

GLOBAL> Voice class (1-8,def:4) ? 

GLOBAL> Global CIR for FR over IP (1-100000000,def:64000) ? 

GLOBAL> Timer in ms for FR over IP (1-1000,def:50) ? 

GLOBAL> Max number of voice channels over IP (0-10000,def:10000) ? 

GLOBAL> Delay generated by a comma (ms) (250-4000,inc:250,def:250) ? 

GLOBAL> ISDN G4 Fax PCM switching enable (def:NO) ? 

GLOBAL> Auto save configuration delay (sec) (0-255,def:10) ? 

GLOBAL> Enable VTR (Voice Traffic Routing) (def:NO) ? 

GLOBAL> Enable Domain Dialing (def:YES) ? 

GLOBAL> Enable hunt forwarding (def:YES) ? 

GLOBAL> Enable user access logging (def:NO) ? 

GLOBAL> Exclusive access to console (def:DISABLE) ? 

Note: The parameters Local unit DLCI address, Extension number (no. 

of digits), and Enable voice/fax log do not appear on the NetPerformer 

SIP VoIP console, as they are not required in a SIP-based application. 

In addition, you cannot use Enable VTR, Enable Domain Dialing or 

Enable hunt forwarding on the NetPerformer SIP VoIP option. 

� You must specify a unique Unit name for each NetPerformer in the 

network. PVCR (WAN) connections will not work if two units 

have the same name. The default Unit name is the burned-in 

product serial number, which guarantees unique naming when you 

configure the unit for the first time. 

� Set Loopback to YES to accept loopback on WAN links. This is for 

testing purposes only. 

� The Transit delay affects bridge operations only. 

� Set Daylight saving time to YES only if you would like the unit to 

adjust the time to Daylight Saving Time. 



� If you leave the Default IP address at its default value 

(000.000.000.000) it is considered not defined. The same is true of 

the SNMP trap: IP address parameters. 

� The Frame relay status change trap determines whether a trap is set 

(ENABLE) or not set (DISABLE) when the status of a Frame Relay 

port changes. 

� Watch power supplies and fans can be set to NONE, PS (for power 

supply), FANS or BOTH. 

� Define the Local unit DLCI address when a global DLCI address is 

required for a Frame Relay application. The default value, 0, means 

this address is not defined. 

� The global voice/fax parameters include: 

� Extension number (no. of digits) to specify the length of the 

extension number 

� Country code (default 1 for North America). Enter ? to view a 

complete list of codes on the console screen. 

� Jitter buffer. Used to compensate for a variation in network delay. 

The 0 value enables dynamic jitter buffer, where the DSP 

determines the jitter in the network by calculating the time 

between packets. 

� Enable voice/fax log. Set to YES if you require a log of all voice/ 

fax calls completed from this unit. 

� Dial timer. Set this parameter to the maximum length of time 

required to dial a Speed Dial Number. The NetPerformer 

determines that a dialing sequence is completed when the Dial 

timer expires or when the user terminates dialing with the pound 

sign (#). 

� High priority voice class. Set to YES if you want voice traffic to be 

given high priority with respect to other traffic types. 

� Voice class. Allows you to set the Voice class manually. You can 

do this only if you first set High priority voice class to NO. 

� The global Frame Relay over IP (FRoIP) parameters include: 

� Global CIR for FR over IP, which indicates the maximum 

combined CIR for all PVCs defined for FRoIP 

� Timer in ms for FR over IP, the Check Timer interval that controls 

the timeout of frames on all PVCs defined for FRoIP 

� Max number of voice channels over IP. 

� The Delay generated by a comma pertains to voice dialing only. 

� Set ISDN G4 Fax PCM switching enable to YES to allow the 

NetPerformer to transport G4 fax messages. When the NetPerformer 

detects that an incoming ISDN call is a G4 fax message, it switches 

the traffic to a PCM64K voice channel. If this parameter is set to NO, 

incoming G4 fax is ignored. 



� When Enable user access logging is enabled, the alarm log indicates 

when users access the unit via the console. 

� When Exclusive access to the console is enabled, a second user 

cannot access the console and disconnect the first user’s connection. 

The first user must disconnect the console to allow someone else to 

connect. 

Note: Access timeouts are independent of the Exclusive access to 

console parameter. If you are using a dial-up or Telnet connection to 

the console, you will be disconnected automatically after a period of 

inactivity, even if this parameter is enabled. 

Global Rackmount Chassis Parameters 

The following additional global parameters appear at the console when 

configuring an SDM-9585 card in the SDM-9500 chassis: 

� Rack ID (0-4; default 1). The 0 value indicates that this card is 

installed in the only SDM-9500 chassis at this site. 

� RIP version for the backplane links (DISABLE, V1, V2 BROADCAST, V2 

MULTICAST; default V1). 

� IPX RIP for backplane links; set to ENABLE to support IPX RIP. 

� IPX SAP for backplane links; set to ENABLE to support IPX SAP. 

� OSPF for backplane links; set to ENABLE to support OSPF. 



ATM Option 

When the ATM firmware option is loaded on the NetPerformer, three 

additional global parameters are available to control how this option 

shares memory and configuration space with other NetPerformer 

functions. Here is a screen capture of global parameters presented for 

the ATM option on a standard NetPerformer unit: 

B302419>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:GLOBAL) ? 

GLOBAL> Unit name (def:B302419) ? CALGARY 

GLOBAL> Unit routing version (1-2,def:1) ? 

GLOBAL> Contact name (def:Verso Technologies) ? 

GLOBAL> Unit location (def:Unknown) ? 

... 

... 

GLOBAL> Delay generated by a comma (ms) (250-4000,inc:250,def:250) ? 

GLOBAL> Number of DSPs reserved for AAL1 (0-6,def:0) ? 1 

GLOBAL> Auto save configuration delay (sec) (0-255,def:10) ? 

GLOBAL> Enable VTR (Voice Traffic Routing) (def:NO) ? 

GLOBAL> Enable Domain Dialing (def:YES) ? 

GLOBAL> Enable hunt forwarding (def:YES) ? 

GLOBAL> Enable user access logging (def:NO) ? 

GLOBAL> Exclusive access to console (def:DISABLE) ? 

WARNING: Changing the next two parameters will require 

a unit reset before the new values take effect. 

GLOBAL> Number of data channels reserved (0-32,def:32) ? 

GLOBAL> ATM AAL5 VC mode includes ATMPVCR, ATMPPP, RFC1483 and FRF.8 

Number of ATM AAL5 VCs reserved (0-31,def:5) ? 

� The Number of DSPs reserved for AAL1 must be higher than zero to 

permit AAL1 signaling on the unit. 

Note: AAL1 support requires that a DSP SIMM be installed in the 

last DSP SIMM socket (socket 2 for the SDM-9360, socket 4 for the 

SDM-9380 or SDM-9585; refer to the Hardware and Installation 

Guide for your product). Otherwise, the Number of DSPs reserved 

for AAL1 parameter does not appear. This parameter also does not 

appear on the NetPerformer SIP VoIP option, since AAL1 is not 

supported on this product. 

� The Number of data channels reserved determines the maximum 

number of non-ATM digital channels that can be configured with the 

PVCR, FR-NET, FR-USER, HDLC or PASSTHROUGH protocols. It 

should be lowered from its default value (32 on the SDM-9360, 64 

on the SDM-9380 and SDM-9585) to support a large number of ATM 

VCs. 

� The Number of ATM AAL5 VCs reserved determines the maximum 

number of VCs that can be configured for ATM AAL5 operations. 



Note: The Number of data channels reserved and Number of ATM AAL5 

VCs reserved affect the allocation of shared RAM on the NetPerformer 

unit. When you change one or both of these parameters, the proposed 

shared RAM allocation is displayed on the console screen. You must 

reset the unit with the Reset Unit (RU) command to activate the 

changes. 

Defining Bridge Characteristics 

To enable bridge operations and configure the bridge parameters: 

� Enter the menu sequence: SE ↵ BRIDGE. 

� Set Enabled to YES to enable bridge functions. 

� Change the other bridge parameters from their default values, if 

desired. 



CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:IP) ? BRIDGE 

BRIDGE> Enabled (def:NO) ? YES 

BRIDGE> Spanning Tree Protocol active (def:NO) ? YES 

BRIDGE> Aging time (sec) (10-1000000,def:300) ? 

BRIDGE> Hello messages interval (sec) (1-10,def:2) ? 

BRIDGE> Hello frames maximum age (sec) (6-40,def:20) ? 

BRIDGE> Forward delay (sec) (4-30,def:15) ? 

BRIDGE> Bridge priority (0-65535,def:32767) ? 

Defining IP Routing Characteristics 

Consult this section to: 

� Enable IP operations on the router and configure the global IP 

characteristics (IP/GLOBAL, page 77) 

� Optionally create an IP static route (IP/STATIC, page 78) 

� Set up dynamic IP routing (page 78) 

� Configure the BOOTP/DHCP relay agent (IP/BOOTP, page 79) 

� Adjust the TIMEP real-time clock (IP/TIMEP, page 79) 

� Configure SNMP management parameters (IP/SNMP, page 80) 

� Define TELNET access restrictions (IP/TELNET, page 80) 

� Define FTP access restrictions (IP/FTP, page 81) 

� Define DNS characteristics (IP/DNS, page 82). 



Note: OSPF and NAT characteristics are also defined using the SETUP/ 

IP menu. They are dealt with separately in the sections Configuring an 

OSPF Connection on page 119 and Defining NAT Characteristics on 

page 172. 

Enable IP Router and Set Up Global IP Properties 

To enable IP operations and define global IP characteristics on the unit: 

� Enter the menu sequence: SE ↵ IP ↵ GLOBAL. 

� Set Router to ENABLE to enable the IP router. 

Note: If the IP router is disabled, you can configure the remaining 

IP/GLOBAL parameters, but their new values will have no effect. 

� Change the other global IP parameters from their default values, if 

desired. 



CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:GLOBAL) ? IP 

Item (GLOBAL/STATIC/BOOTP/OSPF/TIMEP/SNMP/NAT/TELNET/FTP/DNS, 

def:GLOBAL) ? GLOBAL 

IP> Router (def:ENABLE) ? 

IP> Route broadcast to end station (def:NO) ? 

IP> OSPF AS boundary router (def:NO) ? YES 

IP> RIP to OSPF metric conversion cost (1-65534,def:2000) ? 

IP> RIP AS boundary router (def:NO) ? 

IP> IP Precedence for FR over IP (0-7,def:0) ? 

IP> IP Precedence for SIP (0-7,def:0) ? 

� Set Route broadcast to end station to YES value to support IP 

Subnet Broadcasting and IP All Subnet Broadcasting. 

� Set OSPF AS boundary router to YES to send RIP entries through 

OSPF frames. 

� RIP to OSPF metric conversion cost is displayed only if OSPF AS 

boundary router is set to YES. 

� Set RIP AS boundary router to YES to send OSPF entries through 

RIP frames. 

� IP Precedence for FR over IP determines the relative priority of 

Frame Relay over IP traffic, and usually represents classes of service 

from 0 to 7. Typically, the 0 value is used when no QoS is 

implemented in the IP backbone network. 

Note: 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. 



IP Static Route 

Dynamic IP Routing 

� (NetPerformer SIP VoIP option only) IP Precedence for SIP 

determines the relative priority of SIP traffic. The higher the setting, 

the higher the priority. 

If IP RIP is disabled on all unit connections, an IP static route must be 

defined for each destination that requires IP routing. IP static 

routes are optional if the unit is configured for dynamic IP routing, for 

example, if IP RIP is enabled on all PVCs. Refer to Dynamic IP Routing, 

below. 

To create an IP static route: 

� Enter the menu sequence: SE ↵ IP ↵ STATIC. 

� Select an IP static entry number. 

� Set Valid to YES to activate this IP static entry. 

Note: If Valid is set to NO, you can configure the remaining IP/ 

STATIC parameters, but their new values will have no effect. 

� Change the other IP static parameters from their default values, if 

desired. 

The sequence of parameters presented at the console is identical for 

the standard NetPerformer and the NetPerformer SIP VoIP option: 

CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:IP) ? IP 


def:GLOBAL) ? STATIC 

IP static entry number (1-200,def:1) ? 

IP STATIC #1> Valid (def:NO) ? YES 

IP STATIC #1> Destination address (def:000.000.000.000) ? 

IP STATIC #1> Subnet mask (number of bits) (0-24,def:0) ? 

{000.000.000.000} 

IP STATIC #1> Next hop (def:000.000.000.000) ? 

� If you leave the Destination address at its default value 


the Next hop parameter. 

Dynamic IP routing permits easy configuration of all NetPerformer units 

in the network. Once you have set an IP address and mask on the LAN 

interface or WAN/PVC connections, you can access the NetPerformer 

from a remote location using TELNET. From there, you can carry out 

additional configuration through the TELNET connection. 

Note: Dynamic IP routing is optional if an IP static route has been 

configured (see page 78). 



To set up dynamic IP routing: 

BOOTP/DHCP Relay Agent 

TIMEP Real-time Clock 

� Enable IP RIP on the LAN connection and/or WAN/PVC connections. 

� Set the IP RIP version on the LAN port, WAN link or PVC. 

For details, refer to Configuring a LAN Interface on page 84, 

Configuring a WAN Link on page 90 or Defining the Frame Relay 

Connections on page 101. 

� IP RIP can be enabled for one direction only (transmit or receive) 

by changing the IP RIP TX/RX mode on the port or PVC. 

� Configure specific IP RIP properties on the LAN, data port or PVC 

connection, as desired. 

To change the BOOTP/DHCP relay agent characteristics: 

� Enter the menu sequence: SE ↵ IP ↵ BOOTP. 

� Set BOOTP to ENABLE to activate the BOOTP/DHCP relay agent. 

� Change the other BOOTP/DHCP parameters from their default 

values, if desired. 



CHICAGO>SE 

SETUP 




def:GLOBAL) ? BOOTP 

BOOTP> BOOTP (def:DISABLE) ? ENABLE 

BOOTP> Max hops (0-16,def:4) ? 

BOOTP> Destination IP address 1 (def:000.000.000.000) ? 




� Four distinct Destination IP Addresses can be defined. If all are left 

at the default value, 000.000.000.000, the BOOTP/DHCP relay agent 

operates in Broadcast Mode. 

To set up the TIMEP function for resynchronization of the real-time 

clock: 

� Enter the menu sequence: SE ↵ IP ↵ TIMEP. 

� Change the TIMEP parameters from their default values, if desired. 



SNMP Management 

TELNET Access 



CHICAGO>SE 

SETUP 




def:GLOBAL) ? TIMEP 

TIMEP> Negative time zone (def:YES) ? 

TIMEP> Time zone offset from GMT (minutes) (0-720,def:300) ? 

TIMEP> Time server protocol (def:NONE) ? UDP 

TIMEP> Time client protocol (def:NONE) ? UDP 

TIMEP> Time client server IP address (def:000.000.000.000) ? 

TIMEP> Time client update interval (minutes) (1-65534,def:1440) ? 

TIMEP> Time client UDP timeout (seconds) (1-255,def:20) ? 

TIMEP> Time client UDP retransmissions (0-255,def:3) ? 

� The Time server protocol can be set to NONE, UDP, TCP or BOTH. 

� The Time client protocol can be set to NONE, UDP or TCP. 

� If you leave the Time client server IP address at its default value 

(000.000.000.000) it is considered not defined. In this case, the 

Update Time From Server (UT) command will not work. 

To configure the SNMP management parameters: 

� Enter the menu sequence: SE ↵ IP ↵ SNMP. 

� Change the SNMP parameters from their default values, if desired. 



CHICAGO>SE 

SETUP 



Item (GLOBAL/STATIC/BOOTP/OSPF/TIMEP/SNMP/NAT/TELNET/FTP/DNS,def:TIMEP) 

? SNMP 

SNMP> Get community (def:PUBLIC) ? 

SNMP> Set community (def:PUBLIC) ? 

SNMP> Trap community (def:PUBLIC) ? 

Access to the NetPerformer console via a TELNET connection can be 

restricted to up to five addresses, or disabled altogether. To define what 

TELNET access is allowed: 

� Enter the menu sequence: SE ↵ IP ↵ TELNET. 

� Leave the Mode at its default value, ENABLE, to permit TELNET 

access to the NetPerformer console. 



FTP Access 

The authorized IP addresses are defined in the subsequent 

parameters. 

� Change the Mode to DISABLE to block TELNET access from any IP 

device. 

No further parameters are presented in this case. 



CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:IP) ? 


def:TIMEP) ? TELNET 

TELNET> Mode (def:ENABLE) ? 

TELNET> TELNET: IP address #1 (def:000.000.000.000) ? 





� Five distinct TELNET IP Addresses can be defined. If all are left at 

the default value, 000.000.000.000, the NetPerformer unit is 

accessible from any IP device that supports TELNET. 

Caution: If you allow the unit to be accessed without IP 

address limitation, then NetPerformer unit access is secured 

only by password. 

Access to the NetPerformer console via an FTP connection can be 

restricted to up to five addresses, or disabled altogether. To define what 

FTP access is allowed: 

� Enter the menu sequence: SE ↵ IP ↵ FTP. 

� Leave the Mode at its default value, ENABLE, to permit FTP access to 

the NetPerformer console. 

The authorized IP addresses are defined in the subsequent 

parameters. 

� Change the Mode to DISABLE to block FTP access from any IP 

device. 

No further parameters are presented in this case. 



DNS Characteristics 



CHICAGO>SE 

SETUP 




def:TELNET) ? FTP 

FTP> Mode (def:ENABLE) ? 

FTP> FTP: IP address #1 (def:000.000.000.000) ? 





� Five distinct FTP IP Addresses can be defined. If all are left at the 

default value, 000.000.000.000, the NetPerformer unit is accessible 

from any IP device that supports FTP. 

Caution: If you allow the unit to be accessed without IP 

address limitation, then NetPerformer unit access is secured 

only by password. 

The NetPerformer uses DNS (Domain Name Server) to resolve an IP 

address based on a domain name, for example, verso.com. The DNS 

characteristics must be defined to ensure correct IP address resolution. 

Note: The NetPerformer supports only the A type of standard DNS 

queries, which carry out host name to IP address translation. In 

addition, DNS address resolution can be used only for the NetPerformer 

PING command (refer to page 240) and the SIP Proxy server IP 

address parameter. 

To configure the DNS characteristics: 

� Enter the menu sequence: SE ↵ IP ↵ DNS. 

� Change the DNS parameters from their default values, if desired. 



CHICAGO>SE 

SETUP 




def:FTP) ? DNS 

DNS> Primary server address (def:000.000.000.000) ? 5.1.0.137 

DNS> Secondary server address (def:000.000.000.000) ? 5.1.0.134 

DNS> Ignore DNS time to live (def:NO) ? 

� If you leave the Primary server address at its default value 


the Secondary server address parameter. 



Note: At least the Primary server address must be defined for DNS 

to work. 

� Set the Ignore DNS time to live parameter to YES if you want the 

NetPerformer to disregard any Time To Live (TTL) information 

provided by the DNS server. In this case, the DNS entries will not 

age or expire. 

Defining IPX Routing Characteristics 

The NetPerformer router supports Internet Packet Exchange (IPX) 

connections for use in Novell networks. These connections are 

configured using two submenus of the SETUP command: one for the 

global IPX characteristics, and the other for the IPX filter definitions. 

Enable IPX Router and Set Up Global IPX Properties 

To enable IPX operations and define global IPX characteristics on the 

unit: 

Enter the menu sequence: SE ↵ IPX ↵ GLOBAL. 

� Set Router to ENABLE to enable the IPX router. 

Note: If the IPX router is disabled, you can configure the remaining 

IPX/GLOBAL parameters, but their new values will have no effect. 

� Change the other global IPX parameters from their default values, if 

desired. 



BOSTON>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/VLAN/USER/SIP,def:PVC) ? IPX 

Item (GLOBAL/FILTER,def:GLOBAL) ? GLOBAL 

IPX> Router (def:DISABLE) ? ENABLE 

IPX> Internal network number (def:00000000) ? 

� If you leave the Internal network number at its default value 


NetPerformer will be unable to forward IPX frames over direct links 

that do not have a configured IPX address. 

Note: To ensure trouble-free IPX routing you should configure the 

IPX RIP, IPX SAP and IPX network number parameters on the port 

and PVC interfaces, as well as the IPX encapsulation parameter on 

the LAN port. For details, refer to Configuring a WAN Link on 

page 90, Defining the Frame Relay Connections on page 101 and 

Configuring a LAN Interface on page 84. 



IPX Filter Definition 

IPX SAP filters permit greater control of SAP table entries, so that only 

the desired services are actually routed. To filter a SAP entry: 

� Enter the menu sequence: SE ↵ IPX ↵ FILTER. 

� Select a Filter entry number. 

� Set Enable to ENABLE to activate this IPX filter. 

Note: If Enable is set to DISABLE, you can configure the remaining 

IPX/FILTER parameters, but their new values will have no effect. 

� Change the other IPX filter parameters from their default values, if 

desired. 

The sequence of parameters presented at the console is identical for 

the standard NetPerformer and the NetPerformer SIP VoIP option: 

CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:PVC) ? IPX 

Item (GLOBAL/FILTER,def:GLOBAL) ? FILTER 

IPX Filter entry number (1-10,def:1) ? 1 

IPX FILTER 1> Enable (def:DISABLE) ? ENABLE 

IPX FILTER 1> SAP (def:0000) ? 

IPX FILTER 1> Type (def:STANDARD) ? 

� The SAP value can be between 0000 and FFFF. 

� Set the Type to STANDARD to filter out all SAP table entries with the 

value of the SAP parameter. Set it to REVERSE to filter out all SAP 

table entries except those with the value of SAP. 

Configuring a LAN Interface 

The LAN interface is a built-in Ethernet port on the base unit. To 

configure the parameters for the Ethernet port: 

� Enter the menu sequence: SE ↵ PORT ↵ ETH. 

� Change the LAN port parameters from their default values, if 

desired. 





CHICAGO>SE 

SETUP 



Port number (ETH/CSL/1/2,def:1) ? ETH 

PORT ETH> Protocol (def:ETH AUTO) ? 

PORT ETH> LAN speed (mbps) (def:AUTO) ? 

PORT ETH> MAC address (def:000000000000) ? 

PORT ETH> DHCP (def:DISABLE) ? 

PORT ETH> IP address #1 (def:000.000.000.000) ? 

PORT ETH> Subnet mask #1 (number of bits) (0-24,def:0) ? 

{000.000.000.000} 

PORT ETH> IP address #2 (def:000.000.000.000) ? 

PORT ETH> Subnet mask #2 (number of bits) (0-24,def:0) ? 

{000.000.000.000} 

PORT ETH> Frame size (128-8192,def:1500) ? 

PORT ETH> IP RIP (def:V1) ? V2 BROADCAST 

PORT ETH> IP RIP TX/RX (def:DUPLEX) ? 

PORT ETH> IP RIP Authentication (def:NONE) ? 

PORT ETH> IP RIP Password (def:) ? 

PORT ETH> OSPF (def:DISABLE) ? ENABLE 

PORT ETH> OSPF Area ID (def:000.000.000.000) ? 

PORT ETH> OSPF Router priority (0-255,def:1) ? 

PORT ETH> OSPF Transit delay (1-360,def:1) ? 

PORT ETH> OSPF Retransmit interval (1-360,def:5) ? 

PORT ETH> OSPF Hello interval (1-360,def:10) ? 

PORT ETH> OSPF Dead interval (1-2000,def:40) ? 

PORT ETH> OSPF Password (def:) ? 

PORT ETH> OSPF Metric cost (1-65534,def:10) ? 

PORT ETH> IGMP enable (def:NO) ? YES 

PORT ETH> IGMP version (1-2,def:2) ? 

PORT ETH> IGMP send report (def:NO) ? 

PORT ETH> IP multicast active (def:NO) ? YES 

PORT ETH> IP multicast protocol (def:NONE) ? PIMDM 

PORT ETH> IP multicast 1 (def:000.000.000.000) ? 




PORT ETH> NAT enable (def:NO) ? YES 

PORT ETH> NAT rule (1-10) (def:) ? 1 

PORT ETH> NAT side (def:INTERNAL) ? 

PORT ETH> VLAN enable (def:NO) ? YES 

PORT ETH> VLAN Number (1-4095,def:1) ? 

PORT ETH> VLAN Priority Conversion (def:NO) ? 

PORT ETH> IPX RIP (def:DISABLE) ? ENABLE 

PORT ETH> IPX SAP (def:DISABLE) ? 

PORT ETH> IPX network number (def:00000000) ? 

PORT ETH> IPX encapsulation (def:ETH 802.2) ? 

PORT ETH> Physical connectivity detection (def:DISABLE) ? 

� The Protocol can be set to OFF, ETH AUTO, ETH 802.3 or ETH V2. 

� The LAN speed (mbps) can be set to AUTO, 10 MBPS or 100 MBPS on 

the SDM-9360, and AUTO or 10 MBPS on the SDM-9380 and SDM- 

9585. 

� If you leave the MAC address at its default value (000000000000) the 

burned-in address will be used. 

� Set DHCP to ENABLE if you want the first Ethernet IP address on the 

NetPerformer unit to be allocated by a DHCP server. 

� IP address #1 and IP address #2, along with their Subnet masks, 

can be used in a dual IP address application. 

� For this application to work, the two IP addresses must be set on 

two separate IP networks or sub-networks. 



� Leave one of these IP addresses at its default value 

(000.000.000.000) when the NetPerformer requires only a single 

IP address. 

Note: If DHCP is set to ENABLE, IP address #1 and Subnet mask #1 

are not available, since they are automatically allocated by the 

DHCP server. 

� IP RIP can be set to DISABLE, V1, V2 BROADCAST or V2 MULTICAST. 

If set to DISABLE, the LAN port will not support IP RIP. 

� IP RIP TX/RX can be set to DUPLEX, TX ONLY or RX ONLY. 

� IP RIP Authentication and IP RIP Password are presented only if IP 

RIP is set to V2 BROADCAST or V2 MULTICAST. 

� IP RIP Authentication can be set to NONE or SIMPLE. 

� The IP RIP Password can have a maximum of 8 characters. 

� Leave OSPF at its default value, DISABLE, if you do not want the LAN 

port to participate in an OSPF network. In this case, the other 

parameters related to OSPF configuration are not presented. 

� Leave IGMP enable at its default value, NO, if you do not want the 

LAN port to support the Internet Group Management Protocol. In 

this case, the other parameters related to IGMP configuration are 

not presented. 

� If you leave IP multicast active at its default value, NO, only the IP 

multicast protocol is requested. The IP multicast protocol can be set 

to NONE or PIMDM. 

� Four distinct IP multicast addresses can be defined. If all are left at 

the default value, 000.000.000.000, no multicast groups will be 

recognized by the LAN port, and IP Multicast will not work. 

Note: You must also define the parameters for an IP Multicast client 

on all WAN links (PVCR ports) and PVCs (PVCR and RFC1490) that 

will participate in the multicast route. Refer to Configuring a WAN 

Link on page 90 and Defining the Frame Relay Connections on 

page 101. 

� Leave NAT enable at its default value, NO, if you do not want the 

LAN port to support Network Address Translation. In this case, the 

other parameters related to NAT configuration are not presented. 

� The NAT side can be set to INTERNAL or EXTERNAL. 

� Leave VLAN enable at its default value, NO, if you do not want the 

LAN port to be VLAN-aware (refer to VLAN Support on page 36). In 

this case, the other parameters related to VLAN configuration are 


� The VLAN Number on the Ethernet port is required only for access to 

the NetPerformer unit using Telnet, FTP or SNMP via a specific VLAN. 

� Set VLAN Priority Conversion to YES if you want the traffic priority 

information in the VLAN Tag Header to be preserved when routing 

broadcast frames. 



� The IPX network number can have any value from 00000000 to 

FFFFFFFF. If you leave it at its default value, 00000000, the network 

node is unknown. 

� IPX encapsulation can be set to ETH 802.2, ETH SNAP, ETH 802.3 or 

ETH II. 

� Set Physical connectivity detection to ENABLE if you would like the 

NetPerformer to log an alarm whenever the LAN port connection 

goes up or down. 

Setting up a Virtual LAN 

To configure the NetPerformer unit as part of a Virtual LAN: 

� Enter the menu sequence: SE ↵ VLAN. 

� Select a VLAN index. 

� Set VLAN active to YES to activate the VLAN functions. 



CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:IPX) ? VLAN 

VLAN> VLAN index (1/2/3/4/5/6/7/8/9/10,def:1) ? 

VLAN 1> VLAN active (def:NO) ? YES 

VLAN 1> VLAN number (0-4095,def:0) ? 1 

VLAN 1> VLAN destname 1 (def:) ? BOSTON 

VLAN 1> VLAN destname 2 (def:) ? CALGARY 

VLAN 1> VLAN destname 3 (def:) ? 

� Three distinct VLAN destination names (VLAN destname) can be 

defined. Enter the Unit ID of another NetPerformer in the network. 

Caution: You must define at least one VLAN destination 

name, or the Virtual LAN will not work. 

In setting up a VLAN, you must also enable VLAN functions on the 

Ethernet port, as described in Configuring a LAN Interface on page 84. 

Note: The VLAN Number on the Ethernet port is required only for 

access to the NetPerformer unit using Telnet, FTP or SNMP via a specific 

VLAN. 



Defining SIP Characteristics on the 

NetPerformer SIP VoIP Option 

Session Initiation Protocol (SIP) is a standard VoIP protocol that is 

available on the NetPerformer SIP VoIP option only. Consult this section 

to: 

� Enable SIP operations on the NetPerformer SIP VoIP option and 

configure the global SIP characteristics (SIP/GLOBAL, page 88) 

� Define the SIP Timer characteristics (SIP/TIMER, page 89) 

� Define the SIP Retries characteristics (SIP/RETRIES, page 90). 

Note: To set up the NetPerformer SIP VoIP option for voice calls you 

also need to build a Voice Mapping Table. Refer to Setting up a Voice 

Mapping Table on the NetPerformer SIP VoIP Option on page 157. 

Enable SIP and Set Up Global Properties 

To enable SIP operations and define global SIP characteristics on the 

unit: 

� Enter the menu sequence: SE ↵ SIP ↵ GLOBAL. 

Note: As an alternative, you can enter the sequence: SE ↵ SIP ↵ ALL 

to access all SIP parameters. 

� Set the Administrative status to ENABLE to enable SIP functions. 

Note: If SIP is disabled, you can configure the remaining SIP/ 

GLOBAL parameters, but their new values will have no effect. 

� Change the other global SIP parameters from their default values, if 

desired. 

Here is a screen capture of SIP global parameters from the 

NetPerformer SIP VoIP console: 

BOSTON>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/VLAN/USER/SIP,def:USER) ? SIP 

SIP> (GLOBAL/TIMER/RETRIES/ALL,def:GLOBAL) ? GLOBAL 

SIP Global> Administrative status (def:ENABLE) ? 

SIP Global> Proxy server address (def:000.000.000.000) ? 

SIP Global> UDP Port (1-65535,def:5060) ? 

SIP Global> Gateway ID (0-999999999,def:0) ? 

SIP Global> Server group (def:) ? CHICAGO 

SIP Global> Registration (def:DISABLE) ? 

SIP Global> ANI digits (def:) ? 25567 



SIP Timer Parameters 

� If you leave the Proxy server address at its default value 


NetPerformer SIP VoIP is only able to place calls directly to 

another NetPerformer SIP VoIP using the DIALIP Map type (see 

Setting up a Voice Mapping Table on the NetPerformer SIP VoIP 

Option on page 157). Calls cannot be routed via a central 

softswitch. 

Note: If a DNS server address is configured on the unit, you can 

enter the domain name of the proxy server instead of its IP address. 

Refer to DNS Characteristics on page 82. 

� Server group can have a maximum of 32 alphanumeric characters, 

and must match the Server group defined in the Clarent Command 

Center Database for this gateway. 

Note: The Server group is often set to the same value as the 

NetPerformer Unit ID/Location. 

� Set Registration to ENABLE to permit SIP registration on the 

NetPerformer SIP VoIP option. This is required if the NetPerformer 

SIP VoIP must interface with Clarent Call Manager. 

� ANI digits can have a maximum of 32 alphanumeric characters. 

To set the SIP timers: 

� Enter the menu sequence: SE ↵ SIP ↵ TIMER. 



� Change the SIP timer parameters from their default values, if 

desired. 

Note: All of these parameter values are in seconds. 

Here is a screen capture of SIP timer parameters from the 


BOSTON>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/VLAN/USER/SIP,def:GLOBAL) ? SIP 

SIP> (GLOBAL/TIMER/RETRIES/ALL,def:GLOBAL) ? TIMER 

SIP Timer> Resend INVITE (10-300000,def:60) ? 

SIP Timer> Receiving ACK (1-1000,def:1) ? 

SIP Timer> Disconnect (BYE or CANCEL) (1-1000,def:1) ? 



SIP Retries Parameters 

To configure the SIP retries: 

� Enter the menu sequence: SE ↵ SIP ↵ RETRIES. 



� Change the SIP retries parameters from their default values, if 

desired. 

Here is a screen capture of SIP retries parameters from the 


Configuring a WAN Link 

Dedicated WAN Link 

BOSTON>SE 

SETUP 


CLASS/ 

PVC/IPX/MAP/CUSTOM/VLAN/USER/SIP,def:SIP) ? 

SIP> (GLOBAL/TIMER/RETRIES/ALL,def:TIMER) ? RETRIES 

SIP Retries> INVITE (1-10,def:6) ? 

SIP Retries> BYE (1-10,def:6) ? 

SIP Retries> CANCEL (1-10,def:6) ? 

SIP Retries> REGISTER (1-10,def:6) ? 

SIP Retries> RESPONSE (200 OK or ERROR) (1-10,def:6) ? 


� Define a dedicated WAN link for PowerCell connections (SE/PORT or 

SE/SLOT/CHANNEL, page 90) 

� Define a backup link (page 93) 

� Define a Bandwidth on Demand (BOD) link (page 95) 

� Define phone profiles for backup and BOD links (SE/PHONE, 

page 96). 

� Define a satellite link (page 98). This option is available only with 

the SkyPerformer Licensed Software. 

A dedicated WAN link can be configured on a serial port (including ports 

built into the base unit and ports on the Dual Serial Port interface card) 

or a channel on a digital interface card. 

� To configure a built-in serial port on the base unit as a dedicated 

WAN link: 

� Enter the menu sequence: SE ↵ PORT. 

� Select the Port number. 

� Set the Protocol to PVCR and the Mode to DEDICATED. 



� Change the other port parameters from their default values, if 

desired. 

� To configure a serial port on the Dual Serial interface card or a 

digital channel as a dedicated WAN link: 

� Enter the menu sequence: SE ↵ SLOT. 

� Select the Slot number. 

� On digital interface card only: enter CHANNEL at the Item 

prompt. 

� Select the Channel number. 

� Set the Protocol to PVCR and the Mode to DEDICATED. 


desired. 


NetPerformer and the NetPerformer SIP VoIP option. Here is a capture 

of dedicated WAN link configuration on a serial port: 

CHICAGO>SE 

SETUP 




PORT #1> Protocol (def:FR-USER) ? PVCR 

PORT #1> Port speed (bps) (1200-2048000,def:56000) ? 

PORT #1> Interface (def:DTE-V35) ? 

PORT #1> Clocking mode (def:INTERNAL) ? 

PORT #1> Mode (def:DEDICATED) ? DEDICATED 

PORT #1> IP address (def:000.000.000.000) ? 

PORT #1> Subnet mask (number of bits) (0-24,def:0) ? 

{000.000.000.000} 

PORT #1> IP RIP (def:V1) ? V2 MULTICAST 

PORT #1> IP RIP TX/RX (def:DUPLEX) ? 

PORT #1> IP RIP Authentication (def:NONE) ? 

PORT #1> IP RIP Password (def:) ? 

PORT #1> OSPF (def:DISABLE) ? ENABLE 

PORT #1> OSPF Area ID (def:000.000.000.000) ? 

PORT #1> OSPF Transit delay (1-360,def:1) ? 

PORT #1> OSPF Retransmit interval (1-360,def:5) ? 

PORT #1> OSPF Hello interval (1-360,def:10) ? 

PORT #1> OSPF Dead interval (1-2000,def:40) ? 

PORT #1> OSPF Password (def:) ? 

PORT #1> OSPF Metric cost (1-65534,def:1785) ? 

PORT #1> IP multicast active (def:NO) ? 

PORT #1> IP multicast protocol (def:NONE) ? 

PORT #1> NAT enable (def:NO) ? YES 

PORT #1> NAT rule (1-10) (def:) ? 

PORT #1> NAT side (def:INTERNAL) ? 

PORT #1> IPX RIP (def:DISABLE) ? 

PORT #1> IPX SAP (def:DISABLE) ? 

PORT #1> IPX network number (def:00000000) ? 

PORT #1> Compression (def:YES) ? 

PORT #1> Remote unit name (def:) ? BOSTON 

PORT #1> Timeout (msec) (1000-30000,def:1000) ? 

PORT #1> Number of retransmission retries (1-1000,def:100) ? 

PORT #1> Maximum number of voice channels (0-10000,def:10000) ? 

PORT #1> Maximum Voice Channels If High Priority Data (0- 

10000,def:10000) ? 

PORT #1> Cell Packetization (def:YES) ? 

� For the Dual Serial card the Port speed is in Kbps, and can be set to 

8, 16, 32, 56, 64, 112, 128, 256, 512, 768, 1024 or 1536. 



Caution: The total speed of both ports on a Dual Serial card 

must not exceed 1536 Kbps. 

� For a digital interface card the Port speed, Interface and Clocking 

mode parameters are not configured. The channel speed is a 

function of the Number of consecutive timeslots times the DS0 

speed, which can be set to 64000 or 56000 bps. Refer to page 136 for 

further information. 

� The Interface parameter is provided for information purposes only, 

and indicates the type of cable that is connected to the port. This is 

useful for checking that you have installed the right kind of cable on 

the port. 

The value of this parameter cannot be changed, as the type of 

interface is detected automatically. 

Note: If no cable is attached to the port, the Interface parameter 

indicates UNDEFINE. 

� Set the Clocking mode to EXTERNAL if DTE cables are installed on 

the port, or to INTERNAL for DCE cables. 

� Ensure that the Mode is set to DEDICATED for a dedicated link. 

� If you leave the IP address at its default value (000.000.000.000) it is 

considered not defined. In this case, the Default IP address 

configured for the unit will be used (see Defining the Global 

Characteristics on page 71). 

Note: The NetPerformer supports unnumbered IP routing when IP 

addresses are not defined (0.0.0.0) on the WAN side. 


If set to DISABLE, the WAN link will not support IP RIP. 

� IP RIP TX/RX can be set to DUPLEX, TX ONLY or RX ONLY. 

� IP RIP Authentication and IP RIP Password are presented only if IP 

RIP is set to V2 BROADCAST or V2 MULTICAST. 

� IP RIP Authentication can be set to NONE or SIMPLE. 

� The IP RIP Password can have a maximum of 8 characters. 

� Leave OSPF at its default value, DISABLE, if you do not want the 

WAN link to participate in an OSPF network. In this case, the other 

parameters related to OSPF configuration are not presented. 

� Leave IGMP enable at its default value, NO, if you do not want the 

WAN link to support the Internet Group Management Protocol. In 

this case, the other parameters related to IGMP configuration are 


� If you leave IP multicast active at its default value, NO, only the IP 

multicast protocol is requested. The IP multicast protocol can be set 

to NONE or PIMDM. 



Backup Link 

� Four distinct IP multicast addresses can be defined. If all are left at 

the default value, 000.000.000.000, no multicast groups will be 

recognized by the WAN link, and IP Multicast will not work. 

Note: For an IP Multicast application, you must also define the IP 

Multicast parameters on the LAN port. Refer to Configuring a LAN 

Interface on page 84. 

� Leave NAT enable at its default value, NO, if you do not want the 

WAN link to support Network Address Translation. In this case, the 

other parameters related to NAT configuration are not presented. 

� The NAT side can be set to INTERNAL or EXTERNAL. 

� The IPX network number can have any value from 00000000 to 

FFFFFFFF. If you leave it at its default value, 00000000, the network 

node is unknown. 

� IPX encapsulation can be set to ETH 802.2, ETH SNAP, ETH 802.3 or 

ETH II. 

� The Remote unit name should be defined with the Unit ID of another 


� If the Maximum number of voice channels is left at its default value 

(10000), no call blocking is performed on this link. 

� Use Maximum Voice Channels If High Priority Data to limit the 

number of voice calls when a transparent data port (HDLC, T-ASYNC, 

R-ASYNC or PASSTHRU) is set to high priority with the Class 

parameter. The DSR, DCD, DTR and RTS modem signals (RI and RL 

in X.21) must be active for this to take place. 

If Maximum Voice Channels If High Priority Data is left at its default 

value (10000), no call blocking is performed on this link. 

A backup link can be established between two PVCR ports if one is 

configured to activate a call if a link goes down (CALL-BKUP mode) and 

the other is configured to answer the call (ANSWER mode). 

Note: A digital channel cannot be used as either the calling or 

answering side of a backup link when the channel is configured with 

CAS, transparent (TRSP-ORIG or TRSP-ANSW) or no signaling. 

Calling Side of the Backup Link 

To configure the port on the calling side: 

� Set the Protocol to PVCR and the Mode to CALL-BKUP. 




NetPerformer and the NetPerformer SIP VoIP option. 

BOSTON>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/VLAN/USER/SIP,def:PORT) ? 


PORT #1> Protocol (def:PVCR) ? PVCR 


PORT #1> Interface (def:UNDEFINE) ? 


PORT #1> Mode (def:DEDICATED) ? CALL-BKUP 

PORT #1> Backup termination mode (def:MANUAL) ? 

PORT #1> Delay before call activation (sec) (1-1000,def:10) ? 

PORT #1> Delay before call deactivation (sec) (1-1000,def:120) ? 

PORT #1> Call activation timer (sec) (30-1000,def:30) ? 

PORT #1> Port to back (def:ANY) ? 

PORT #1> Dialer (def:DTR) ? 


... 

� The Backup termination mode can be set to AUTOMATIC or MANUAL. 

� Port to back can be set to ANY, ALL, or a specific serial port or digital 

channel configured with the PVCR protocol. 

� The Dialer can be set to DTR, X21-L1, V25-H, V25-B, AT-9600, AT- 

19200, AT-28800, AT-38400, AT-57600 or AT-115200. 

Answering Side of the Backup Link 

To configure the port on the answering side: 

� Set the Protocol to PVCR and the Mode to ANSWER. 



BOSTON>SE 

SETUP 


CLASS/ 

PVC/IPX/MAP/CUSTOM/VLAN/USER/SIP,def:PORT) ? 






PORT #1> Mode (def:DEDICATED) ? ANSWER 



... 

� The Dialer can be set to DTR, X21-L1, V25-H, V25-B, AT-9600, AT- 

19200, AT-28800, AT-38400, AT-57600 or AT-115200. 



Bandwidth on Demand Link 

A Bandwidth on Demand (BOD) link can be established between two 

PVCR ports if one is configured to activate a call when traffic becomes 

heavy (CALL-BOD mode) and the other is configured to answer the call 

(ANSWER mode). 

� Bandwidth On Demand can only be used when the main link is a 

dedicated PVCR port. 

� A digital channel cannot be used as either the calling or 

answering side of a BOD link when the channel is configured with 

CAS, transparent (TRSP-ORIG or TRSP-ANSW) or no signaling. 

Calling Side of the BOD Link 

To configure the port on the calling side: 

� Set the Protocol to PVCR and the Mode to CALL-BOD. 



BOSTON>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/VLAN/USER/SIP,def:PORT) ? 






PORT #1> Mode (def:CALL-BKUP) ? CALL-BOD 

PORT #1> Delay before BOD call activation (sec) (1-1000,def:120) ? 

PORT #1> Delay before BOD call deactivation (sec) (1-1000,def:120) ? 

PORT #1> BOD level (%) (5-95,def:80) ? 


PORT #1> Delay before call deactivation (sec) (1-1000,def:120) ? 


PORT #1> Port to back (def:ANY) ? 



... 

� The BOD level determines the threshold at which this link will be 

activated, in terms of the percentage of bandwidth used. 

Answering Side of the BOD Link 

To configure the port on the answering side: 

� Set the Protocol to PVCR and the Mode to ANSWER, as described for 

a backup link (see page 94). 



Defining the Phones for Backup and BOD Links 

PVCR ports defined as the calling side of a backup or BOD link require 

phone profiles to execute the calls correctly. Both modem and ISDN 

connections are supported. 

Modem Connection 

To configure a phone profile for a modem connection: 

� Enter the menu sequence: SE ↵ PHONE. 

� Select the Profile number. 

� Leave the Dialer type at its default value, MODEM. 



CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:BRIDGE) ? PHONE 

Define phone profile for BACKUP links 

PHONE> Profile number (1-64,def:1) ? 

PHONE> #1> Remote unit (def:) ? CALGARY 

PHONE> #1> Next hop (def:) ? BOSTON 

PHONE> #1> Cost (0-65534,def:1) ? 

PHONE> #1> Dialer type (def:MODEM) ? 

PHONE> #1> Phone number (def:) ? 6595090 

� The Remote unit should be defined with the Unit ID of the remote 

NetPerformer unit. 

� Next hop should be defined with the Unit ID of the intermediate unit 

that is used to reach the remote unit via the main link. Set Next hop 

to the local Unit ID when no intermediate unit is present, that is, 

when there is a direct connection to the remote unit. 

ISDN Connection 

To configure a phone profile for an ISDN connection: 

� Enter the menu sequence: SE ↵ PHONE. 


� Set the Dialer type to ISDN. 



Wait-User Mode 

Inactive Mode 



BOSTON>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/VLAN/USER/SIP,def:BRIDGE) ? PHONE 

Define phone profile for BACKUP links 

PHONE> Profile number (1-64,def:1) ? 

PHONE> #1> Remote unit (def:) ? CALGARY 

PHONE> #1> Next hop (def:) ? BOSTON 

PHONE> #1> Cost (0-65534,def:1) ? 

PHONE> #1> Dialer type (def:MODEM) ? ISDN 

PHONE> #1> Remote number (def:) ? 5551234 

PHONE> #1> Remote subaddress (def:) ? 01 

PHONE> #1> Local number (def:) ? 6595090 

PHONE> #1> Local subaddress (def:) ? 01 

PHONE> #1> Number of links (1-64,def:1) ? 

� The Remote unit should be defined with the Unit ID of the remote 


� Next hop should be defined with the Unit ID of the intermediate unit 

that is used to reach the remote unit via the main link. Set Next hop 

to the local Unit ID when no intermediate unit is present, that is, 

when there is a direct connection to the remote unit. 

In Wait-User mode, the PVCR link is activated and deactivated based on 

the presence of active modem signals on HDLC user ports (DCD for a 

DCE connection; DTR for a DTE connection). 

To configure a WAN port in Wait-User mode: 

� Set the port Protocol to PVCR 

� Set the Mode to WAIT-USER. 

The parameters listed are the same as those for DEDICATED mode (see 

page 91). 

In Inactive mode the PVCR link is turned off. This mode can be useful 

when combined with the NetPerformer Scheduling function (refer to 

Schedule Parameters on page 199). 

To configure a WAN port in Inactive mode: 

� Set the port Protocol to PVCR 

� Set the Mode to INACTIVE. 

The parameters listed are the same as those for DEDICATED mode (see 

page 91). 



Satellite Link 

Note: The SkyPerformer firmware license must be installed on the 

NetPerformer unit to support satellite link configuration. 

In a SkyPerformer application a satellite link can be configured on a 

serial port (including those on the Dual Serial Port interface card). 

� To configure a built-in serial port on the base unit as a satellite link: 



� Set the Protocol to SP. 


desired. 

� To configure a serial port on the Dual Serial interface card as a 

satellite link: 




� Set the Protocol to SP. 


desired. 

MODULATOR Port 



of a satellite link configured as a MODULATOR on a built-in serial port: 

SEATTLE>SE 

SETUP 



Port number (ETH/CSL/1/2,def:CSL) ? 1 

PORT #1> Protocol (def:SP) ? SP 

PORT #1> Type (def:DEMODULATOR) ? MODULATOR 


PORT #1> Fallback speed (def:ENABLE) ? 




PORT #1> Congestion flow control (def:ON) ? 

PORT #1> CLLM function (def:OFF) ? 



10000,def:10000) ? 

� The Type can be set to MODULATOR, DEMODULATOR, EXPANSION or 

AGGREGATE. 

� Select MODULATOR if the port connects to an external modulator 

(TX satellite modem) or modem (modulator and demodulator). 

You can define more than one MODULATOR port on an single unit. 



Note: The Type cannot be set to MODULATOR if an AGGREGATE 

port has already been defined on the unit. 

� Select DEMODULATOR if the port connects to an external 

demodulator (RX satellite modem). You can define several 

DEMODULATOR ports on a single unit. 

� Select EXPANSION if the port connects to an expansion chassis. A 

maximum of one EXPANSION port can be defined per unit. 

Note: The Type cannot be set to EXPANSION if an AGGREGATE 

port has already been defined on the unit. 

� Select AGGREGATE if the port is on an expansion chassis that 

connects to the main chassis. A maximum of one AGGREGATE 

port can be defined per unit. 

Note: The Type cannot be set to AGGREGATE if a MODULATOR or 

EXPANSION port has already been defined on the unit. 

� On the Dual Serial interface card, the Port speed can be 8, 16, 32, 

56, 64, 112, 128, 256, 512, 768, 1024 or 1536 kbps. 

� Fallback speed is disabled if Congestion flow control is ON. If you 

prefer to use fallback rather than flow control for this port, enter 3 

carriage returns at the console to reach the Congestion flow control 

parameter. Then enter OFF. 

Note: Fallback speed is not available on the Dual Serial interface 

card. 




the port. 







� Cell Packetization is always on when Frame Relay over IP is enabled. 


(10000), no call blocking is performed on this connection. 







value (10000), no call blocking is performed on this connection. 



DEMODULATOR Port 

Here is a capture of a satellite link configured as a DEMODULATOR port: 

SEATTLE>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:PORT) ? PORT 


PORT #2> Protocol (def:PVCR) ? SP 

PORT #2> Type (def:DEMODULATOR) ? DEMODULATOR 






PORT #2> Modulator port (def:1) ? 

� The Modulator port can be set to a port number or NONE. Select an 

SP port that is configured with the MODULATOR Type. 

� The other parameters behave as for the MODULATOR Port on 

page 98. 

EXPANSION Port 

Here is a capture of a satellite link configured as an EXPANSION port: 

SEATTLE>SE 

SETUP 





PORT #1> Type (def:MODULATOR) ? EXPANSION 










10000,def:10000) ? 

PORT #1> Modulator port (def:1) ? 

� The Modulator port can be set to a port number or NONE. Select an 

SP port that is configured with the MODULATOR Type. 

� The other parameters behave as for the MODULATOR Port on 

page 98. 



AGGREGATE Port 

Here is a capture of a satellite link configured as an AGGREGATE port: 

SEATTLE>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:PORT) ? 



PORT #2> Type (def:DEMODULATOR) ? AGGREGATE 










10000,def:10000) ? 

� These parameters behave as for the MODULATOR Port on page 98. 

Defining the Frame Relay Connections 

The Frame Relay connections require: 

� A connection to the Frame Relay network, including optional SVCs 

(FR-USER port, page 102) 

� A connection to a Frame Relay end-user device (FR-NET port, 

page 104) 

� One or more PVCs, which allow: 

� Accessing a remote NetPerformer using PowerCell (PVCR PVC, 

page 106) 

� Accessing a remote RFC1490-compatible Frame Relay Access 

Device (FRAD) (RFC1490 PVC, page 108) 

� Multiplexing data from a Frame Relay or X.25 end-user device 

(Multiplex PVC, page 109) 

� On standard NetPerformer only: Sending broadcast voice traffic 

frames to the Frame Relay switch (Broadcast PVC, page 110) 

� Switching data from one end-user device directly to the network 

and destination end-user device without alteration on the frame 

(Transparent PVC, page 111) 

� One or more ATM PVCs on the ATM firmware option, which in 

addition to the PVC modes above allows: 

� Sending voice (analog or digital), data, video or LAN traffic over 

ATM AAL5 using PowerCell, and accessing a remote NetPerformer 

or FRAD (ATMPVCR PVC, page 111) 



FR-USER Port Parameters 

� On standard NetPerformer only: sending uncompressed voice 

traffic (analog or digital) over ATM AAL1 using circuit emulation, 

providing a link to a legacy ATM application, and accessing the 

PSTN or ATM switch (AAL1 PVC, page 113) 

� Transporting Frame Relay traffic from an external router over 

ATM using Service Interworking (FRF.8 PVC, page 114) 

� Sending multiprotocol data or LAN traffic over ATM AAL5 using 

RFC-1483, providing a link to a legacy ATM application, and 

accessing a gateway controller, network management system or 

the Internet (RFC1483 PVC, page 116) 

� Sending data or LAN traffic using PPP over ATM AAL5 (RFC- 

2364), and accessing an ATM switch or the Internet (ATMPPP 

PVC, page 117). 

� One or more PVCs on the SkyPerformer firmware option, which in 

addition to the standard NetPerformer PVC modes allows: 

� Multiplexing DEMODULATOR traffic between NetPerformer units 

(usually SDM-9585 cards) running the SkyPerformer option (SP- 

MULTIPLEX, page 118) 

The multiplexed DEMODULATOR traffic is returned to the main 

card equipped with a MODULATOR port. 

Note: SP-MULTIPLEX PVCs can connect only with remote SP- 

MULTIPLEX PVCs. 

Note: Two PVC modes, FP and FP-MULTIPLEX, are reserved for setting 

up a gateway to Verso Technologies’ legacy products (SDM-FP, SDM-JFP 

and SDM-DX). For further information on these modes, consult the 

NetPerformer System Reference Manual (Administration Guide). 

To configure a connection to the Frame Relay network, set up a FR- 

USER port or channel: 

� To configure a built-in serial port on the base unit as a FR-USER 

connection: 



� Set the Protocol to FR-USER. 


desired. 


digital channel as a FR-USER connection: 






prompt. 


� Set the Protocol to FR-USER. 


desired. 

Here is a capture of FR-USER port configuration on a standard 

NetPerformer built-in serial port: 

CHICAGO>SE 

SETUP 




PORT #1> Protocol (def:FR-USER) ? FR-USER 


PORT #1> Fallback speed (def:DISABLE) ? 



PORT #1> Management interface (def:LMI) ? 


PORT #1> Enquiry timer (sec) (1-30,def:10) ? 

PORT #1> Report cycle (1-256,def:6) ? 





10000,def:10000) ? 

PORT #1> Drop signals on LMI down (def:NO) ? 

PORT #1> SVC address type (def:NONE) ? E.164 

PORT #1> SVC network address (def:) ? 

PORT #1> SVC max Tx Ack timeout T200 (1-5,def:1) ? 

PORT #1> SVC inactive timeout T203 (1-60,def:30) ? 

PORT #1> SVC Iframe retransmissions N200 (1-16,def:3) ? 

PORT #1> SVC setup timeout T303 (1-30,def:4) ? 

PORT #1> SVC disconnect timeout T305 (1-30,def:30) ? 

PORT #1> SVC release timeout T308 (1-30,def:4) ? 

PORT #1> SVC call proceeding timeout T310 (1-30,def:4) ? 

PORT #1> SVC status enquiry timeout T322 (1-30,def:4) ? 

� The SVC parameters are not presented at the console of the 

NetPerformer SIP VoIP option. All other parameters are the same as 

those for the standard NetPerformer. 


56, 64, 112, 128, 256, 512, 768, 1024 or 1536 kbps. 






card. 



� The Management interface can be set to LMI, ANNEX-D, Q.933 or 

NONE. 

Note: It must be set to ANNEX-D when using SVCs. 



FR-NET Port Parameters 











� The SVC address type can be set to NONE, E.164 or X.121. You must 

pick E.164 or X.121 to continue with SVC configuration. 

� The SVC network address is a maximum of 15 digits. 

� The SVC maximum Tx Ack timeout sets the maximum delay allowed 

between each transmission and its acknowledgement. 

To configure a connection to a Frame Relay end-user device, set up a 

FR-NET port or channel: 

� To configure a built-in serial port on the base unit as a FR-NET 

connection: 



� Set the Protocol to FR-NET. 


desired. 


digital channel as a FR-NET connection: 




prompt. 


� Set the Protocol to FR-NET. 


desired. 





of FR-NET configuration on a serial port: 

CHICAGO>SE 

SETUP 




PORT #2> Protocol (def:PVCR) ? FR-NET 


PORT #2> Fallback speed (def:DISABLE) ? 



PORT #2> Modem control signal (def:STATIC) ? 

PORT #2> Frame delay (msec) (def:0.0) ? 








10000,def:10000) ? 

PORT #2> Reference port for conditional LMI (0-2000,def:0) ? 



56, 64, 112, 128, 256, 512, 768, 1024 or 1536 kbps. 






card. 



� The Modem control signal can be set to STATIC or DYNAMIC. 

Note: Modem control signal is not available on the Dual Serial 

interface card or the T1 and E1 digital interface cards. 

� The Frame delay can be set to 0.0, 0.5, 1.0, 1.5 or 2.0 msec. 

Note: Frame delay is not available on the Dual Serial interface card 

or the T1 and E1 digital interface cards. 

� The Management interface can be set to LMI, ANNEX-D, Q.933 or 

NONE. 






PVCR PVC Parameters 








� For the Reference port for conditional LMI, select a FR-USER port or 

channel. The default value, 0, means this function is disabled. 

To configure a PVC that can access a remote NetPerformer using 

PowerCell: 

� Enter the menu sequence: SE ↵ PVC. 

� Select the PVC number. 

� Set the Mode to PVCR. 

� Change the other PVC parameters from their default values, if 

desired. 





CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:CLASS) ? PVC 

PVC number (1-300,def:1) ? 1 

PVC #1> Mode (def:PVCR) ? PVCR 

PVC #1> Port (def:1) ? 

PVC #1> DLCI address (0-1022,def:0) ? 

PVC #1> Committed Information rate (4000-2048000,def:56000) ? 

PVC #1> Burst Information rate (4000-2048000,def:56000) ? 

PVC #1> Remote unit name (def:) ? BOSTON 

PVC #1> Type (def:DEDICATED) ? 

PVC #1> Timeout (msec) (1000-30000,def:1000) ? 

PVC #1> Number of retransmission retries (1-1000,def:100) ? 

PVC #1> Compression (def:YES) ? 

PVC #1> IP address (def:000.000.000.000) ? 

PVC #1> Subnet mask (number of bits) (0-24,def:0) ? {000.000.000.000} 

PVC #1> NAT enable (NO/YES,def:NO) ? YES 

PVC #1> NAT rule (def:) ? 1 

PVC #1> NAT side (def:INTERNAL) ? 

PVC #1> IP RIP (def:V1) ? V2 BROADCAST 

PVC #2> IP RIP TX/RX (def:DUPLEX) ? 

PVC #2> IP RIP Authentication (def:NONE) ? 

PVC #2> IP RIP Password (def:) ? 

PVC #2> OSPF (def:DISABLE) ? ENABLE 

PVC #2> OSPF Area ID (def:000.000.000.000) ? 

PVC #2> OSPF Transit delay (1-360,def:1) ? 

PVC #2> OSPF Retransmit interval (1-360,def:5) ? 

PVC #2> OSPF Hello interval (1-360,def:10) ? 

PVC #2> OSPF Dead interval (1-2000,def:40) ? 

PVC #2> OSPF Password (def:) ? 

PVC #2> OSPF Metric cost (1-65534,def:1785) ? 

PVC #1> IP multicast active (def:NO) ? 

PVC #1> IP multicast protocol (def:NONE) ? 

PVC #1> IPX RIP (def:DISABLE) ? 

PVC #1> IPX SAP (def:DISABLE) ? 

PVC #1> IPX NETWORK NUMBER (def:00000000) ? 

PVC #1> Broadcast group (def:NO) ? 

PVC #1> Maximum number of voice channels (0-10000,def:10000) ? 

PVC #1> Maximum Voice Channels If High Priority Data (0- 

10000,def:10000) ? 

PVC #1> Frame over IP, source (def:000.000.000.000) ? 

PVC #1> Frame over IP, destination (def:000.000.000.000) ? 

� The Port parameter refers to a FR-USER or FR-NET port or channel. 

For a SkyPerformer application, set it to the number of an SP port 

set in MODULATOR mode. Select 0 to assign this PVC to a virtual IP 

port and enable Frame Relay over IP (FRoIP). 

� Leave the DLCI address at its default value, 0, for auto-learning. 

Note: Each PVC connection for a particular reference port must 

have a unique DLCI address. If you do not choose a unique DLCI 

address, you will be alerted of the conflict and requested to select a 

different value for this parameter. 

Caution: For an FRoIP or SkyPerformer application you must 

change the DLCI address to a non-zero value. There is no 

link management for FRoIP, and DLCI auto-learning is not 

permitted on the SkyPerformer. 

� The Burst Information rate is not required for FRoIP. 



RFC1490 PVC Parameters 

� The Type can be set to DEDICATED, ANSWER or CALL-BKUP. These 

choices are configured in much the same way as for a backup WAN 

link (see Backup Link on page 93). 

On a CALL-BKUP PVC, the Backup parameter can be set to ANY or 

ALL. 

� If you leave the IP address at its default value, 000.000.000.000, the 

PVC will operate in unnumbered IP mode. 


� All parameters affecting IP RIP, NAT, OSPF, IP Multicast and IPX are 

similar to those used for configuring a WAN link (see Dedicated WAN 

Link on page 90). 

� Set Broadcast group to YES to assign this PVC to a broadcast group. 

� The Frame over IP, source parameter defines the source IP address 

in an FRoIP application. It can be set to the local unit WAN or LAN IP 

address. If you leave Frame over IP, source at its default value, 

000.000.000.000, the Ethernet LAN IP address #1 parameter will be 

used as the source IP address for FRoIP traffic originating from the 

unit. 

� The Frame over IP, destination parameter represents the 

destination IP address in an FRoIP application. If you leave Frame 

over IP, destination at its default value, 000.000.000.000, the 

destination IP address is not defined, and an FRoIP connection 

cannot be established. 

To configure a PVC that can access a remote RFC1490-compatible 

FRAD: 



� Set the Mode to RFC1490. 


desired. 



Multiplex PVC Parameters 



CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:PVC) ? 


PVC #4> Mode (def:OFF) ? RFC1490 

PVC #4> Port (def:1) ? 1 

PVC #4> DLCI address (0-1022,def:0) ? 103 





PVC #4> Subnet mask (number of bits) (0-24,def:0) ? {000.000.000.000} 

PVC #4> NAT enable (def:NO) ? 

PVC #4> Frame size (128-8192,def:1500) ? 

PVC #4> IP RIP (def:V1) ? V2 MULTICAST 


PVC #4> IP RIP Authentication (def:NONE) ? 

PVC #4> IP RIP Password (def:) ? 

PVC #4> OSPF (def:DISABLE) ? 






PVC #4> BRG connection (def:NO) ? 

PVC #4> IP connection (def:YES) ? 

PVC #4> IPX connection (def:YES) ? 

PVC #4> LLC connection (def:YES) ? 

� The Remote unit name is optional, and serves for information 

purposes only, e.g. in PVC UP/DOWN alarms. 

Caution: Ensure that this Remote unit name does not 

interfere with an existing Remote unit name in a mixed 

network of PVCR and RFC-1490 links, as a name conflict will 

prevent proper connection. 

� Refer to the section PVCR PVC Parameters on page 106 for notes on 

the other parameters listed with this PVC mode. 

To configure a PVC that can multiplex data from a Frame Relay or X.25 

end-user device: 



� Set the Mode to MULTIPLEX. 


desired. 



Broadcast PVC Parameters 



CHICAGO>SE 

SETUP 



PVC number (1-300,def:4) ? 

PVC #4> Mode (def:PVCR) ? MULTIPLEX 





PVC #4> Remote unit name (def:BOSTON) ? 

PVC #4> Remote PVC number (1-300,def:4) ? 

PVC #4> Class number (def:3) ? 


� The Class number can be set to 1, 2, 3, 4, 5, 6, 7, 8 or HIGH 

PRIORITY. 

Note: Use the SETUP/CLASS submenu to define the relative weight 

and preferred route for each numeric priority class. Refer to Class 

Parameters on page 198. 

� Refer to the section PVCR PVC Parameters on page 106 for other 

notes on the parameters listed with this PVC mode. 

Note: Broadcast PVCs are available on the standard NetPerformer only. 

To configure a PVC that can send broadcast voice traffic frames to the 

multicast server (the Frame Relay switch): 



� Set the Mode to BROADCAST. 


desired. 

Here is a capture of the parameters that are presented at the standard 

NetPerformer console: 

CHICAGO>SE 

SETUP 




PVC #5> Mode (def:OFF) ? BROADCAST 




� The DLCI Address defines the Mdlci for this application. 





Transparent PVC Parameters 

To configure a PVC that can switch data from one end-user device 

directly to the network and destination end-user device without 

alteration on the frame: 



� Set the Mode to TRANSP. 

ATMPVCR PVC Parameters 


desired. 



CHICAGO>SE 

SETUP 




PVC #7> Mode (def:OFF) ? TRANSP 

PVC #7> User port (def:1) ? 

PVC #7> Network port (def:1) ? 2 

PVC #7> User DLCI (0-1022,def:0) ? 107 

PVC #7> Network DLCI (0-1022,def:0) ? 110 



� The User port parameter must refer to a FR-USER or FR-NET port or 

channel. 

� The Network port parameter must refer to a FR-NET or X.25 port or 

channel. 

� Leave the User DLCI at its default value, 0, for auto-learning. 

� The Network DLCI must be changed from its default value, 0, for an 

operative connection. 

Note: ATMPVCR PVCs are available with the ATM license only. 

To configure a PVC that can send voice (analog or digital), data, video 

or LAN traffic over ATM AAL5 using PowerCell, and access a remote 

NetPerformer or FRAD: 



� Set the Mode to ATMPVCR. 


desired. 





CALGARY>SE 

SETUP 




PVC #20> Mode (def:OFF) ? ATMPVCR 

PVC #20> VPI address (0-255,def:0) ? 101 

PVC #20> VCI address (0-65535,def:0) ? 102 

PVC #20> Peak cell rate (0-3622,def:1000) ? 

PVC #20> Payload information rate is 384000 bps 

PVC #20> Total information rate is 424000 bps 


PVC #20> Timeout (msec) (1000-30000,def:1000) ? 

PVC #20> Number of retransmission retries (1-1000,def:100) ? 



PVC #20> Subnet mask (number of bits) (0-24,def:0) ? 

{000.000.000.000} 


PVC #20> IP RIP (def:V1) ? 








PVC #20> Maximum number of voice channels (0-10000,def:10000) ? 

PVC #20> Maximum Voice Channels If High Priority Data (0- 

10000,def:10000) ? 

PVC #20> Cell Packetization (def:YES) ? 

� The VPI address parameter determines the address of the Virtual 

Path Indicator (VPI). If you leave this parameter at its default value, 

0, this address is not defined. 

� The VCI address parameter determines the address of the Virtual 

Channel Indicator (VCI). If you leave this parameter at its default 

value, 0, this address is not defined. 

Caution: If the VPI is also set to 0, the VCI address is invalid. 

� A maximum of 31 virtual channels (VCs) can be configured on 

the unit. 

� VCI address values from 0 to 32 are normally reserved, but can 

be used if desired. 

� VPI 0/VCI 3 and VPI 0/VCI 4 are used for Raw Cell traffic. 

Note: Two PVCs cannot have the same VPI/VCI combination. If you 

try to enter an address that is already used, the NetPerformer 

displays a warning specifying which PVC already has this address. 

� The Peak cell rate is the maximum cell rate (in cells per second) that 

is required by the application. It can go up to 3622 cells/sec. on a T1 

connection, or 4679 cells/sec. on an E1 connection. 

Note: If 30 timeslots are used on an E1 ATM channel, the SAR 

driver limits the Peak cell rate to 4528 cells/sec., even if this 

parameter is set to a higher value. 



AAL1 PVC Parameters 

� After you define the Peak cell rate, the NetPerformer automatically 

calculates and displays: 

� Payload information rate: the cell rate multiplied by the cell size, 

excluding ATM cell headers 

� Total information rate: the cell rate multiplied by the cell size, 

including ATM cell headers. 



Note: AAL1 PVCs are available with the ATM license on the standard 

NetPerformer only. 

To configure a PVC that can send uncompressed voice traffic (analog or 

digital) over ATM AAL1 using circuit emulation, provide a link to a 

legacy ATM application, and access the PSTN or ATM switch: 



� Set the Mode to AAL1. 


desired. 



CALGARY>SE 

SETUP 



PVC number (1-300,def:20) ? 21 

PVC #21> Mode (def:OFF) ? AAL1 






PVC #21> PVC name (def:) ? CALGARY-AAL1 

WARNING !!! Modifying the subchannels settings will reset all AAL1 VCs. 

PVC #21> Number of subchannels (1-24,def:1) ? 

PVC #21> Super frame format (def:DS1-SF) ? 

PVC #21> Local inbound voice level (db) (def:0) ? 

PVC #21> Local outbound voice level (db) (def:-3) ? 

PVC #21> Echo canceler (def:ENABLE) ? 

PVC #21> Double talk threshold (db) (def:6) ? 

PVC #21> Idle code (def:7F) ? 

PVC #21> Jitter buffer(ms) (30-240,def:100) ? 

PVC #21> Signaling type (def:IMMEDIATE START) ? 

PVC #21> TONE type (def:DTMF) ? 

PVC #21> TONE regeneration (0-255,def:30) ? 

PVC #21> TONE ON (ms) (30-1000,def:100) ? 

PVC #21> TONE OFF (ms) (30-1000,def:100) ? 

PVC #21> Pulse make/break ratio (30-50,inc:4,def:34) ? 

PVC #21> Delete digits (0-4,def:0) ? 

PVC #21> Fwd digits (def:NONE) ? ALL 

PVC #21> Fwd delay (0-255,def:0) ? 

PVC #21> Fwd type (def:TONE) ? 



FRF.8 PVC Parameters 

� Refer to the section ATMPVCR PVC Parameters on page 111 for 

notes on the VPI address, VCI address and Peak cell rate. 

� The PVC name is used to refer to this PVC when defining the 

destination of an associated Voice Mapping Table (MAP) entry. 

� The Number of subchannels specifies how many voice subchannels 

are assigned to this PVC. This determines the number of voice 

connections that are supported by this AAL1 transport service. 

� Each subchannel uses 75 Kbps of bandwidth. 

� A maximum of 20 subchannels is allowed on a T1 connection, or 

24 subchannels on an E1 connection. 

Caution: Use care when changing the Number of subchannels 

parameter, as all AAL1 VCs are reset when it is modified. 

� The Super frame format can be set to: 

� DS1-SF: for North American superframe with 12 frames and 2-bit 

(AB) signaling 

� DS1-ESF: for North American extended superframe with 24 

frames and 4-bit (ABCD) signaling 

� E1: for other countries. 

� The Signaling type can be set to IMMEDIATE START, R2, FXO, FXS, 

GND FXO, GND FXS, PLAR, WINK START, R2-CHINA, DELAY DIAL or 

CUSTOM. 

� The TONE type can be set to DTMF, MF or R2. 

� Fwd digits can be set to NONE, ALL or EXT. 

� Fwd delay and Fwd type are presented only if Fwd digits is set to ALL 

or EXT. 

� Fwd type can be set to TONE or PULSE. 

Note: FRF.8 PVCs are available with the ATM license only. 

To configure a PVC that can transport Frame Relay traffic from an 

external router over ATM using Service Interworking: 



� Set the Mode to FRF.8. 


desired. 





CALGARY>SE 

SETUP 



PVC number (1-300,def:21) ? 22 

PVC #22> Mode (def:OFF) ? FRF.8 






PVC #22> Frame Relay port (def:1) ? 2 




PVC #22> Header translation (def:YES) ? 

PVC #22> ATM CLP bit (def:DE) ? 

PVC #22> ATM EFCI bit (def:FECN) ? 

PVC #22> Frame relay DE bit (def:CLP) ? 

PVC #22> Frame relay FECN bit (def:EFCI) ? 

PVC #22> Congestion queue size (0-100000,def:4000) ? 

PVC #22> Maximum queue size (0-100000,def:8000) ? 



� The Frame Relay port parameter must refer to the port or channel 

that provides the Frame Relay access link. 

� Leave Header translation at its default value, YES, if you want the 

RFC-1483 header to be translated to RFC-1490, and vice versa. Set 

it to NO for transparent mode, where the user data is unchanged as 

it passes from one side to the other. 

� The ATM CLP bit determines whether the Cell Loss Priority (CLP) bit 

is: 

� 0: Reset 

� 1: Set 

� DE: A copy of the Discard Eligibility (DE) bit of each Frame Relay 

frame received. 

� The ATM EFCI bit determines whether the Explicit Forward 

Congestion Indicator (EFCI) bit is: 

� 0: Reset 

� 1: Set 

� FECN: A copy of the Forward Explicit Congestion Notification 

(FECN) bit of each Frame Relay frame received. 

� The Frame relay DE bit determines whether the DE bit is: 

� 0: Reset 

� 1: Set 

� CLP: A copy of the CLP bit of each ATM frame received. 



� The Frame relay FECN bit determines whether the FECN bit is: 

� 0: Reset 

� 1: Set 

RFC1483 PVC Parameters 

� EFCI: A copy of the EFCI bit of each ATM frame received. 

Note: RFC1483 PVCs are available with the ATM license only. 

To configure a PVC that can send multiprotocol data or LAN traffic over 

ATM AAL5 using RFC-1483, provide a link to a legacy ATM application, 

and access a gateway controller, network management system or the 

Internet: 



� Set the Mode to RFC1483. 


desired. 



CALGARY>SE 

SETUP 



PVC number (1-300,def:22) ? 23 

PVC #23> Mode (def:OFF) ? RFC1483 






PVC #23> Remote unit name (def:) ? CHICAGO 

PVC #23> BRG connection (def:NO) ? 

PVC #23> IP connection (def:YES) ? 



{000.000.000.000} 







PVC #23> IPX connection (def:YES) ? 










ATMPPP PVC Parameters 





� Refer to the section PVCR PVC Parameters on page 106 for notes on 

the other parameters listed with this PVC mode. 

Note: ATMPPP PVCs are available with the ATM license only. 

To configure a PVC that can send data or LAN traffic using PPP over ATM 

AAL5 (RFC-2364), and access an ATM switch or the Internet: 



� Set the Mode to ATMPPP. 


desired. 



CALGARY>SE 

SETUP 



PVC number (1-300,def:23) ? 24 

PVC #24> Mode (def:OFF) ? ATMPPP 






PVC #24> Remote unit name (def:) ? CHICAGO 

PVC #24> LLC encapsulation (def:NO) ? 



{000.000.000.000} 







PVC #24> Configuration restart timer (0-255,def:3) ? 

PVC #24> Configuration restart counter (0-255,def:255) ? 

PVC #24> MRU (0-1500,def:1500) ? 

PVC #24> Remote IP-Address (def:000.000.000.000) ? 

PVC #24> Incoming password type (def:CHAP (MD5)) ? 

PVC #24> Incoming user name (def:) ? 

PVC #24> Incoming password (def:) ? 

PVC #24> Outgoing password type (def:CHAP (MD5)) ? 

PVC #24> Outgoing user name (def:) ? 

PVC #24> Outgoing password (def:) ? 

PVC #24> Authentication retries, 255 = forever (0-255,def:3) ? 

PVC #24> Fail delay (minutes) (0-255,def:0) ? 

PVC #24> Maximum challenge interval (minutes) (1-255,def:60) ? 

PVC #24> Authentication timeout (seconds) (1-255,def:10) ? 











� Set LLC encapsulation to YES if the IP frame should be encapsulated 

with an RFC-1483 header. 

� Set the MRU to the maximum number of bytes allowed in the 

Information and Padding fields of the PPP encapsulated frame. This 

parameter determines the size of the MRU that the PVC requests 

from the peer. 

Note: MRU negotiation is always active. The value that is negotiated 

cannot exceed the value specified by the MRU parameter for this 

PVC. 

� All other parameters are similar to those used for configuring a PPP 

port or channel (see PPP Port Parameters on page 185). 

Note: 

� The Magic Number is always requested and accepted. 

� Old Addresses Negotiation is not accepted. 

� If the Remote IP-Address is set to 0.0.0.0, then IP addresses are 

both requested and accepted. If it is set to another value, IP 

addresses are neither requested nor accepted. 

SP-Multiplex PVC Parameters 

Note: SP-Multiplex PVCs are available with the SkyPerformer firmware 

license only. 

SP-Multiplex PVCs multiplex DEMODULATOR traffic between 

NetPerformer units, typically SDM-9585 cards. They can connect only 

with SP-Multiplex PVCs defined on the remote NetPerformer unit. The 

multiplexed DEMODULATOR traffic is returned to the main card 

equipped with a MODULATOR port. 

To configure an SP-Multiplex PVC: 



� Set the Mode to SP-MULTIPLEX. 


desired. 





� The Port parameter must refer to an SP port set in MODULATOR or 

DEMODULATOR mode. 

� Refer to the section Multiplex PVC Parameters on page 109 for notes 

on the other parameters listed with this PVC mode. 

Configuring an OSPF Connection 


OSPF Global Parameters 

SEATTLE>SE 

SETUP 




PVC #4> Mode (def:OFF) ? SP-MULTIPLEX 






PVC #4> Remote PVC number (1-300,def:4) ? 

PVC #4> Class number (def:3) ? 


� Configure the global OSPF parameters (IP/OSPF/GLOBAL, page 119) 

� Enable OSPF connections (page 120) 

� Define the OSPF Area characteristics (IP/OSPF/AREA, page 121) 

� Define the Range of all areas that connect to the backbone via an 

area border router (IP/OSPF/RANGE, page 122) 

� Define an OSPF virtual link (IP/OSPF/VLINK, page 123). 

To define global OSPF characteristics on the unit: 

� Enter the menu sequence: SE ↵ IP ↵ OSPF↵ GLOBAL. 

� Change the global OSPF parameters from their default values, if 

desired. 



Enable OSPF Connections 



CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:PVC) ? IP 

Item (GLOBAL/STATIC/BOOTP/OSPF/TIMEP/SNMP/NAT/TELNET/FTP,def:GLOBAL) ? 

OSPF 

Item (GLOBAL/AREA/RANGE/VLINK,def:GLOBAL) ? GLOBAL 

OSPF GLOBAL> Router ID (def:000.000.000.000) ? 

OSPF GLOBAL> Auto virtual link (def:NO) ? 

OSPF GLOBAL> Global area ID (def:000.000.000.000) ? 

� If you leave the Router ID at its default value (000.000.000.000) it is 

considered not defined. In this case, the NetPerformer unit will be 

unable to receive or broadcast any OSPF routes. 

Note: You must configure a Router ID for each router in the network 

that will use OSPF, and each Router ID must be unique. 

� Set Auto virtual link to YES if you want OSPF virtual links to be 

enabled as they are required. 

� If you leave the Global area ID at its default value (000.000.000.000) 

the NetPerformer’s global Default IP address is included in the OSPF 

backbone. 

To enable OSPF routing on a NetPerformer connection (WAN link, LAN 

port or PVC): 

� Access the appropriate sub-menu for the connection you want to 

bring into the OSPF network: 

� For a LAN port, enter the menu sequence SE ↵ PORT followed by 

ETH. 

� For a WAN link, enter the menu sequence SE ↵ PORT followed by 

the port number, or SE ↵ SLOT ↵ CHANNEL followed by the 

channel number. 

� For a PVC, enter the menu sequence SE ↵ PVC followed by the 

PVC number. 

For details, refer to Configuring a LAN Interface on page 84, 

Configuring a WAN Link on page 90 or Defining the Frame Relay 


� (Optional) Disable IP RIP on the connection: 

Enter carriage returns until you reach the IP RIP parameter, then 

enter DISABLE. 

� Set the OSPF Enable parameter to ENABLE. 

� Change the other OSPF parameters from their default values, if 

desired. 



Area Parameters 


NetPerformer and the NetPerformer SIP VoIP option. Here is an 

example of enabling OSPF on a LAN connection: 

CHICAGO>SE 

SETUP 



Port number (ETH/CSL/1/2,def:1) ? ETH 

... 

PORT ETH> OSPF (def:DISABLE) ? ENABLE 

PORT ETH> OSPF Area ID (def:000.000.000.000) ? 

PORT ETH> OSPF Router priority (0-255,def:1) ? 

PORT ETH> OSPF Transit delay (1-360,def:1) ? 

PORT ETH> OSPF Retransmit interval (1-360,def:5) ? 

PORT ETH> OSPF Hello interval (1-360,def:10) ? 

PORT ETH> OSPF Dead interval (1-2000,def:40) ? 

PORT ETH> OSPF Password (def:) ? 

PORT ETH> OSPF Metric cost (1-65534,def:10) ? 

� Leave the OSPF Area ID at its default value (000.000.000.000) to 

include this connection in the OSPF backbone. 

� The OSPF Router priority is defined on a LAN interface only, and is 

used to determine the designated router. 

� Set the Hello interval on the LAN port to its maximum value, 360 

sec., if you want the IP address of the NetPerformer unit to be 

broadcast throughout the OSPF network. 

Note: The IP address of the LAN port will be broadcast across the 

OSPF network without disturbing the RIP network, which will receive 

an OSPF Hello packet only once in a while. 

� The OSPF Password is a maximum of 8 ASCII characters. 

To define the OSPF Area characteristics: 

� Enter the menu sequence: SE ↵ IP ↵ OSPF↵ AREA. 

� Select an Area entry number. 

� Change the other area parameters from their default values, if 

desired. 



Range Parameters 



CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:PVC) ? IP 

Item (GLOBAL/STATIC/BOOTP/OSPF/TIMEP/SNMP/NAT/TELNET/FTP,def:GLOBAL) ? 

OSPF 

Item (GLOBAL/AREA/RANGE/VLINK,def:GLOBAL) ? AREA 

OSPF Area entry number (1-10,def:1) ? 

OSPF AREA 1> Area ID (def:000.000.000.000) ? 

OSPF AREA 1> Enable (def:ENABLE) ? 

OSPF AREA 1> Authentication type (def:NONE) ? 

OSPF AREA 1> Import AS extern (def:YES) ? 

OSPF AREA 1> Stub metric (1-255,def:1) ? 

� If you leave the Area ID at its default value (000.000.000.000) it is 

not defined. 

� Enable this area with ENABLE. 

� The Authentication type can be NONE or SIMPLE. 

� Set Import AS extern to YES to flood AS external advertisements 

throughout the area. Set it to NO to define this area as a stub area. 

Note: Ranges are required only for those areas that connect to the 

backbone via an area border router. 

To define the OSPF Range characteristics: 

� Enter the menu sequence: SE ↵ IP ↵ OSPF↵ RANGE. 

� Select a Range entry number. 

� Change the other range parameters from their default values, if 

desired. 



CHICAGO>SE 

SETUP 




def:GLOBAL) ? OSPF 

Item (GLOBAL/AREA/RANGE/VLINK,def:AREA) ? RANGE 

OSPF Range entry number (1-10,def:1) ? 

OSPF RANGE 1> Range net (def:000.000.000.000) ? 

OSPF RANGE 1> Range mask (def:000.000.000.000) ? 

OSPF RANGE 1> Enable (def:ENABLE) ? 

OSPF RANGE 1> Status (def:ADVERTISE) ? 

OSPF RANGE 1> Add to area (def:000.000.000.000) ? 

� The Range net and Range mask identify the group of subnets in this 

range. 

� Enable this range with ENABLE. 



Virtual Link Parameters 

� The Status can be DON’T ADV or ADVERTISE. 

� For the Add to area parameter, enter the area to which this range 

belongs. 

Note: To allow for virtual link configuration, the NetPerformer unit must 

be an area border router. 

To define the OSPF Virtual Link characteristics: 

� Enter the menu sequence: SE ↵ IP ↵ OSPF↵ VLINK. 

� Select a Virtual link entry number. 

� Change the other virtual link parameters from their default values, if 

desired. 



CHICAGO>SE 

SETUP 




def:OSPF) ? OSPF 

Item (GLOBAL/AREA/RANGE/VLINK,def:RANGE) ? VLINK 

OSPF Virtual link entry number (1-10,def:1) ? 

OSPF VLINK 1> Transit area ID (def:000.000.000.000) ? 

OSPF VLINK 1> Neighbor’s router ID (def:000.000.000.000) ? 

OSPF VLINK 1> Enable (def:ENABLE) ? 

OSPF VLINK 1> Transit delay (1-360,def:1) ? 

OSPF VLINK 1> Retransmit interval (1-360,def:5) ? 

OSPF VLINK 1> Hello interval (1-360,def:10) ? 

OSPF VLINK 1> Dead interval (1-2000,def:60) ? 

OSPF VLINK 1> Password (def:) ? 

� The Transit area ID identifies the common non-backbone area to 

which both endpoint routers are attached. Select an Area ID that 

has already been defined (see page 121). 

Caution: Do not leave this parameter at its default value, 

000.000.000.000, which specifies the backbone. 

� Set the Neighbor’s router ID to the Global area ID of the other 

endpoint of the virtual link. 

� Enable this virtual link with ENABLE. 

� The Password is a maximum of 8 ASCII characters. 



Allocating DSPs 

The DSP Allocation (DSPA) command allows you to allocate voice 

codecs to the DSPs installed in the NetPerformer unit. 

Note: The DSPA command is available to users with FULL console 

access only. To change access privileges for a particular user, refer to 

Defining User Access Profiles on page 70. 

To allocate the voice codecs: 

� Enter DSPA at the console command prompt. 

� Redefine the voice protocol allocation, if desired: 

� You can choose from ACELP-CN, G.723, G.726 16K, G.726 24K, 

G.726 32K, G.726 40K, G.729 or G.729 A. 

Note: PCM64K is included with any combination. 

� Use the up and down arrow keys to navigate to the allocation 

value you want to change. 

� Enter the new percentage value. 

Note: The NetPerformer keeps a running total of the percentage of 

DSPs that are already allocated. You cannot enter a new value 

that would make this total go over 100%. 

Caution: Do not allocate more protocols than the 

number of DSPs installed in the unit. If you do, the voice 

channels will not work. There is no internal software 

protection against this. For example, it is possible to 

configure 25% ACELP-CN, 25% G.723, 25% G.729 and 25% 

G.729A, even if there are only 3 DSPs in the unit. With this 

allocation you will also be able to configure G.729A on the 

voice channels. However, these channels will not work. 



Here is an example from the standard NetPerformer console: 

CHICAGO>DSPA 

DSP ALLOCATION 

-------------------------------------------------------------------------------- 

| DSP Allocation Table (Number of DSPs running: 06) | 

-------------------------------------------------------------------------------- 

| Voice Protocol % of Allocation | 

| ACELP-CN 20 % | 

| | 

| G.723 20 % | 

| | 

| G.726 16K 10 % | 

| | 

| G.726 24K 10 % | 

| | 

| G.726 32K 20 % | 

| | 

| G.726 40K 0 % | 

| | 

| G.729 20 % | 

| | 

| G.729 A 0 % | 

| --------- | 

| Percentage Allocated 100 % | 

| | 

-------------------------------------------------------------------------------- 

Use , and arrow to navigate. Press to save and exit. 

Press to exit this menu. 

The default voice protocol allocation depends on the base unit 

firmware: 

� The standard NetPerformer has 100% ACELP-CN by default. 

� The NetPerformer SIP VoIP option has 100% G.729A by default. 

Configuring a T1, E1 or ISDN-BRI Connection 


� Define the physical ports provided by an optional digital interface 

card (SE/SLOT/LINK), including: 

� T1 interface, page 125 

� E1 interface, page 128 

� ISDN-BRI S/T interface, page 130. 

� Define the digital data/voice channels on the T1, E1 and ISDN-BRI 

interface cards (SE/SLOT/CHANNEL, page 133). 

� (Optional) Define a set of callers that are authorized to access an 

ISDN connection on the unit (SE/CALLER ID, page 149). 

T1 Physical Port Parameters (LINK) 

To define the physical port on a T1 interface card: 



� Enter LINK. 



� Set the Status to ENABLE to activate the physical link. 

Note: If the physical link is disabled, all data/voice channels 

associated with this port are disabled, but the channel configuration 

is not lost. 

� Change the other digital link parameters from their default values, if 

desired. 

Here is a capture of T1 link configuration from the standard 


CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:GLOBAL) ? SLOT 

SLOT> Slot number (1/2/3/4,def:2) ? 3 

Item (LINK/CHANNEL,def:LINK) ? LINK 

PORT #300> Status (def:DISABLE) ? ENABLE 

PORT #300> Clock recovery (def:DISABLE) ? 

PORT #300> Digital port clock source (def:INTERNAL) ? 

PORT #300> Signaling mode (def:NONE) ? NONE 

PORT #300> Pcm encoding law (def:MU-LAW) ? 

PORT #300> Idle code (def:7F) ? 

PORT #300> Zero suppression mode (def:B8ZS) ? 

PORT #300> Gain limit (def:-30DB) ? 

PORT #300> Framing mode (def:ESF) ? D4 

PORT #300> Line Build Out (def:0-133FT) ? 

PORT #300> Yellow alarm encoding (def:BIT2) ? 

PORT #300> Generate ring back locally (def:DISABLE) ? 

PORT #300> Loopback (def:DISABLE) ? 

� Set Clock recovery to ENABLE if you want the clock received on this 

port to provide the clock for other digital ports. 

� Digital port clock source can be used in conjunction with Clock 

recovery to optimize the clock distribution. Set Digital port clock 

source to the slot containing the digital interface card that is 

connected to the network (1, 2, 3, 4, INTERNAL). Default INTERNAL 

allows the NetPerformer card to use its internal reference clock. 

Note: Select values 1 to 4 if you want all transmit clocks to be 

driven by the receive clock of the digital interface card that is 

installed in that slot number. Select INTERNAL if you want all 

transmit clocks to be driven by the internal reference clock (up to 

1.544 Mbps for T1, up to 2.048 Mbps for E1, or up to 128 Kbps for 

ISDN-BRI S/T). 

� On the standard NetPerformer, the Signaling mode can be set to 

NONE, ROB BIT, TRSP-ORIG, TRSP-ANSW, NTT, KDD, 4ESS, 5ESS, 

DMS100, NI2 or QSIG. 

� Set to NONE for a data-only connection. 

� Set to ROB BIT for T1 Robbed-bit signaling. 

� Set to TRSP-ORIG (originate) or TRSP-ANSW (answer) for 

transparent HDLC-based or PCM64K-based transport. 



Note: The TRSP-ORIG and TRSP-ANSW signaling modes are not 

available on the NetPerformer SIP VoIP option. They are used to 

establish a permanent point-to-point transparent signaling 

connection between digital interfaces (T1 or E1). 

� Set to NTT, KDD, 4ESS, 5ESS, DMS100, NI2 or QSIG for a voice/ 

data connection using CCS. 

Note: NTT and KDD are used for ISDN access in Japan. 4ESS, 

5ESS, DMS100 and NI2 are used for ISDN access in other 

countries (mainly North America). 

� The PCM encoding law can be set to A-LAW or MU-LAW. 

� Valid Idle code values are from 00 to FF. 

� The Zero suppression mode can be set to B8ZS, AMI or B7ZS. 

� The Gain limit can be set to -30DB or -36DB. 

� The Framing mode can be set to ESF or D4. 

� The Line Build Out adjusts waveshaping on the T1 driver to match 

lines of different lengths. It can be set to 0-133FT, 133-266FT, 266- 

399FT, 399-533FT, 533-655FT, -7.5DB, -15DB or -22.5DB. 

� Yellow alarm encoding can be set to BIT2, FBIT12 or NONE. This 

parameter is listed when the Signaling mode is set to NONE and the 

Framing mode is set to D4. 

� A Yellow Alarm is logged for a Far End Alarm failure. This 

happens when bit 2 of all channels is at zero for a significant 

length of time (BIT2) or when the F-bit of the 12th frame of the 

superframe is at zero for two successive frames (FBIT12). 

� When a Yellow Alarm occurs, the yellow LED labelled ALM on the 

right side of the digital port turns on. The NetPerformer assumes 

that the physical link is out of sync when a yellow alarm is 

detected, and will bring down any active channels on that link. 

� Set Yellow alarm encoding to NONE to ignore yellow alarms, for 

example, if a high number of false alarms occurs. False alarms 

can occur only in a data-only application. 



CCS Signaling Modes 

For the CCS signaling modes (Signaling mode set to NTT, KDD, 4ESS, 

5ESS, DMS100, NI2 or QSIG) a few additional parameters are presented: 

CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:SLOT) ? SLOT 



PORT #300> Status (def:ENABLE) ? 



PORT #300> Signaling mode (def:NONE) ? NTT 

PORT #300> CCS side (def:USER) ? 

PORT #300> Channel selection mode (def:PREFERRED) ? 

PORT #300> Local number (def:) ? 6595090 

PORT #300> Local subaddress (def:) ? 01 


... 

� The CCS side can be set to USER or NETWORK. The two sides of a 

CCS connection must have opposite values for this 

parameter. 

� Set to USER when the unit is facing the network side of the 

application. 

� Set to NETWORK when the unit is facing the user side of the 

application. 

Note: When Signaling mode is set to QSIG, this parameter is 

replaced with the QSIG master parameter. Set QSIG master to YES 

if this side connects to equipment that is defined as slave. The two 

sides of a QSIG connection must have opposite values for 

this parameter. 

� The Channel selection mode can be set to PREFERRED or 

EXCLUSIVE. 

� The Local number defines the local ISDN number of the channel, 

and Local subaddress uniquely identifies the NetPerformer unit in an 

application where more than one device can be reached using a 

single ISDN number. 

E1 Physical Port Parameters (LINK) 

To define the physical port on an E1 interface card: 







is not lost. 




desired. 

Here is a capture of E1 link configuration from the standard 


CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:PU) ? SLOT 







PORT #100> Pcm encoding law (def:A-LAW) ? 

PORT #100> Idle code (def:7E) ? 

PORT #100> Zero suppression mode (def:HDB3) ? 

PORT #100> Gain limit (def:-12DB) ? 

PORT #100> CRC4 mode (def:ENABLE) ? 

PORT #100> International bit (def:ENABLE) ? 

PORT #100> ETS 300 011 mode (def:DISABLE) ? 



� On the standard NetPerformer, the Signaling mode can be set to 

NONE, CAS, EURO-ISDN, QSIG, TRSP-ORIG or TRSP-ANSW. 


� Set to CAS for a voice/data connection using CAS. 

� Set to EURO-ISDN or QSIG for a voice/data connection using CCS. 

� Set to TRSP-ORIG (originate) or TRSP-ANSW (answer) for 

transparent HDLC-based or PCM64K-based transport. 

Note: The TRSP-ORIG and TRSP-ANSW signaling modes are not 

available on the NetPerformer SIP VoIP option. They are used to 

establish a permanent point-to-point transparent signaling 

connection between digital interfaces (T1 or E1). 

� The Zero suppression mode can be set to HDB3 or AMI. 

� The Gain limit can be set to -12DB or -43DB. 

� Refer to T1 Physical Port Parameters (LINK) on page 125 for notes 

on the other parameters listed for E1 link configuration. 



CCS Signaling Modes 

For the CCS signaling modes (Signaling mode set to EURO-ISDN or 

QSIG) a few additional parameters are presented: 

CHICAGO>SE 

SETUP 








PORT #100> Signaling mode (def:NONE) ? EURO-ISDN 






... 

� When Signaling mode is set to QSIG, the CCS side parameter is 





� Refer to page 128 for other notes on these parameters. 

ISDN-BRI S/T Physical Port Parameters (LINK) 

To define a physical port on an ISDN-BRI S/T interface card: 




Note: The port number indicator in subsequent parameters is 00 

when Port number is set to 1, or 50 when Port number is set to 2, 

e.g. PORT #300 indicates Slot 3, Port 1. 





is not lost. 


desired. 





CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:GLOBAL) ? SLOT 


Port number (1/2,def:1) ? 1 

Item (LINK/CHANNEL,def:CHANNEL) ? LINK 



PORT #300> Digital port clock source (def:INTERNAL) ? ? 






PORT #300> Terminal Endpoint Identifier (TEI) (def:AUTOMATIC) ? 


PORT #300> Power Mode (def:OFF) ? 



� The Signaling mode can be set to NONE, EURO-ISDN, QSIG, INS-NET, 

KDD, NI1, NI2, 5ESS or DMS100. 


� Set to EURO-ISDN, QSIG, INS-NET, KDD, NI1, NI2, 5ESS or DMS100 

for a voice/data connection using CCS. 

Note: INS-NET and KDD are used for ISDN access in Japan. NI1, 

NI2, 5ESS and DMS100 are used for ISDN access in other 

countries (mainly North America). 

� The Terminal Endpoint Identifier (TEI) can be set to AUTOMATIC, 0, 

or an integer from 1 to 63. 

� Set the Pcm encoding law to MU-LAW for the Japanese signaling 

modes INS-NET and KDD. 

� The NetPerformer can supply power through an NT port to external 

TE equipment. The Power Mode parameter determines the power 

feed mode that is used: 

� OFF: No power is provided to the external TE device. 

� PHANTOM: Fixed power is provided to the attached device using 

a standard I.430 Phantom supply. 

Note: The Power Mode parameter is listed only when the ISDN-BRI 

S/T port is set to NT termination mode, using jumpers on the ISDN- 

BRI S/T card. If the ISDN-BRI S/T port is set to TE termination 

mode, the power source is automatically disabled by the hardware. 



� To view the current NT/TE termination mode, execute the Display 

States (DS) command, select the SLOT Item and specify which 

slot you want to view: 

CHICAGO>DS 

DISPLAY STATES 

Item (GLOBAL/PORT/PU/PVC/SLOT/SVC/VLAN,def:GLOBAL) ? SLOT 

SLOT> Slot number (1/2/3/4/ALL,def:1) ? 3 

SLOT 3 - PORT 1> 

PORT #300> Protocol.............................ISDN BRI 

PORT #300> State................................OUT OF SYNC 

PORT #300> D-Channel state......................DOWN 

PORT #300> Interface............................BRI-NT 

SLOT 3 - PORT 2> 

PORT #350> Protocol.............................ISDN BRI 

PORT #350> State................................OUT OF SYNC 

PORT #350> D-Channel state......................DOWN 

PORT #350> Interface............................BRI-TE 

Modem signals: d(S)r d(T)r (D)cd (R)ts (C)ts r(I) (-)off 

� The Interface statistic displays BRI-NT for a port set to NT 

termination mode, or BRI-TE for a port set to TE termination 

mode. 

� To change the current hardware setting, refer to the Hardware 

Installation Guide for your particular NetPerformer model. 

� Refer to T1 Physical Port Parameters (LINK) on page 125 and CCS 

Signaling Modes on page 128 for notes on the other parameters 

listed for ISDN-BRI S/T link configuration. 

Non-Japanese CCS Signaling Modes 

When the Signaling mode is set to NI1, NI2, 5ESS, DMS100 or QSIG, two 

additional parameters are presented to define the Local SPID 1 and 2: 

CHICAGO>SE 

SETUP 




Port number (1/2,def:1) ? 2 





PORT #350> Signaling mode (def:NONE) ? NI1 



PORT #350> Local number (def:) ? 

PORT #350> Local subaddress (def:) ? 

PORT #350> Local SPID 1 (def:) ? 

PORT #350> Local SPID 2 (def:) ? 

PORT #350> Terminal Endpoint Identifier (TEI) (def:AUTOMATIC) ? 

... 

� Local SPID 1 and Local SPID 2 define the optional Service Profile 

Identifiers (SPIDs) that are included with the call setup message. 



� When Signaling mode is set to QSIG, the CCS side parameter is 





Digital Voice/Data Channel Parameters (CHANNEL) 

The digital channels of a T1, E1 or ISDN-BRI S/T card transport data or 

voice, depending on: 

� The Signaling mode set on the LINK. Refer to page 125 for T1 

signaling modes, page 128 for E1 signaling modes, and page 130 for 

ISDN-BRI S/T signaling modes. 

� The Protocol set on the CHANNEL. The protocols that are available 

depend on the Signaling mode set on the LINK, and the voice codecs 

allocated to the DSPs. Refer to Allocating DSPs on page 124. 

To define a digital voice/data channel on a T1, E1 or ISDN-BRI interface 

card: 



� Enter CHANNEL. 

� Select the Channel Number, e.g. 102, where the first digit indicates 

the slot and the last two digits indicate the channel. 

� Set the Protocol. Refer to Data Channel Parameters on page 134 

and Voice Channel Parameters on page 141 for protocol-specific 

examples and information. 

� Depending on the DSP allocation, the Protocol can be set to the 

following voice algorithms: 

ACELP-CN, G723, G726 16K, G726 24K, G726 32K, G726 40K, G729 

or G729A 

� If the Signaling mode is set to NONE, the Protocol can be set to: 

OFF, HDLC, PVCR, FR-NET, FR-USER, PPP, ACELP-CN (and/or 

other voice protocols, listed above), PCM64K, TRANSPARENT 

(standard NetPerformer only) or PASSTHROUGH 

Note: The TRANSPARENT protocol, as well as the TRSP-ORIG and 

TRSP-ANSW signaling modes, are not available on the 

NetPerformer SIP VoIP option. They are used to establish a 

permanent point-to-point transparent signaling connection 

between digital interfaces (T1 or E1). 

� If the Signaling mode is set to TRSP-ORIG, TRSP-ANSW, CAS or 

ROB BIT, the Protocol can be set to: 

OFF, HDLC, PVCR, FR-NET, FR-USER, ACELP-CN (and/or other 

voice protocols, listed above), PCM64K, TRANSPARENT (standard 

NetPerformer only) or PASSTHROUGH 



� If the Signaling mode is set to EURO-ISDN, QSIG, INS-NET, NTT, 

KDD, NI1, NI2, 4ESS, 5ESS, DMS100 or QSIG, the Protocol can be 

set to: 

OFF, PVCR, FR-NET, FR-USER, PPP, ACELP-CN (and/or other 

voice protocols, listed above) or PCM64K. 

Note: In addition to the above, the Protocol can be set to ATM on a 

standard NetPerformer or NetPerformer SIP VoIP installed with the 

ATM licensed firmware option. In a future release, the SP protocol 

may also be offered on a T1/E1 digital interface for a standard 

NetPerformer or NetPerformer SIP VoIP installed with the 

SkyPerformer licensed firmware option. 

� Change the other digital channel parameters from their default 


� Data channels are described in the next section. 

� Voice channels are described starting from page 141. 

Data Channel Parameters 

The following data protocols can be configured on a T1, E1 or ISDN-BRI 

interface card: 

� HDLC (page 135) 

� PVCR (page 136) 

� FR-NET (page 137) 

� FR-USER (page 138) 

� Synchronous PPP (page 139) 

� PASSTHROUGH (page 140) 

� TRANSPARENT (page 140) 



HDLC Protocol 

Note: HDLC is available only when the Signaling mode on the LINK is 

set to NONE, TRSP-ORIG, TRSP-ANSW, CAS or ROB BIT. 



CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:SLOT) ? 

SLOT> Slot number (1/2/3/4,def:3) ? 

Item (LINK/CHANNEL,def:LINK) ? CHANNEL 

SLOT> Channel Number (301-324/ALL,def:301) ? 301 

PORT #301> Protocol (def:OFF) ? HDLC 

PORT #301> Timeslot (1-24,def:1) ? 1 

PORT #301> Number of consecutive timeslots (1-24,def:1) ? 

PORT #301> DS0 speed (bps) (def:64000) ? 

PORT #301> CRC encoding (def:NRZ) ? 


PORT #301> Transmission start level (def:AUTO) ? 

PORT #301> Idle (def:FLAG) ? 


PORT #301> Remote unit (def:) ? 

PORT #301> Class (def:3) ? 

PORT #301> Remote port number (1-65534,def:301) ? 

� Select the Timeslot that you want to include in the channel. The 

default value is the next available timeslot. 

Note: You must select an unused timeslot. If the timeslot you select 

is already used by another channel, you will see the message Time 

slot assignment conflict with channel X, where X is the channel to which 

this timeslot is assigned. 

� The Number of consecutive timeslots is a maximum of 24 on a T1 

interface card. The number available on an E1 interface card 

depends on the Signaling mode defined on the LINK: 

� If the Signaling mode is NONE, time slot 16 is available for data. 

An E1 channel can have up to 31 timeslots when no signaling is 

used. 

For example, if a channel is defined to start at timeslot 15 for 3 

consecutive timeslots, it will use timeslots 15, 16 and 17. 

� If signaling is used on the E1 link, timeslot 16 is reserved, and 

the maximum number of timeslots that can be assigned to an E1 

channel is 30. 

In this case, a channel starting at timeslot 15 for 3 consecutive 

timeslots will use timeslots 15, 17 and 18. 

Note: The range of consecutive timeslots that are still available is 

dynamically adjusted to the current configuration. For example, if 

you assign timeslots 1-4 to a particular channel on a T1 interface 

card, the default value of the Timeslot parameter will be 5 for the 

next channel you configure, and the maximum Number of 

consecutive timeslots will be reduced to 20. 

� The DS0 speed can be set to 64000 or 56000 bps. 



� The other parameters behave as for a serial port set to the HDLC 

protocol. Refer to HDLC Port Parameters on page 180. 

PVCR Protocol 

Note: PVCR is available with all LINK signaling modes. 



CHICAGO>SE 

SETUP 




Item (LINK/CHANNEL,def:CHANNEL) ? 


PORT #302> Protocol (def:OFF) ? PVCR 

PORT #302> Timeslot (1-24,def:2) ? 



PORT #302> Mode (def:DEDICATED) ? 



{000.000.000.000} 

PORT #302> IP RIP (def:V1) ? 


PORT #302> OSPF (def:DISABLE) ? 

PORT #302> IP multicast active (def:NO) ? 

PORT #302> IP multicast protocol (def:NONE) ? 

PORT #302> NAT enable (def:NO) ? 

PORT #302> IPX RIP (def:DISABLE) ? 

PORT #302> IPX SAP (def:DISABLE) ? 

PORT #302> IPX network number (def:00000000) ? 

PORT #302> Compression (def:YES) ? 

PORT #302> Remote unit name (def:) ? 

PORT #302> Timeout (msec) (1000-30000,def:1000) ? 

PORT #302> Number of retransmission retries (1-1000,def:100) ? 



10000,def:10000) ? 


� Link backup (Mode parameter set to CALL-BKUP) and Bandwidth On 

Demand (Mode parameter set to CALL-BOD) are available only when 

the Signaling mode on the LINK is set to EURO-ISDN, QSIG, INS-NET, 

NTT, KDD, NI1, NI2, 4ESS, 5ESS, DMS100 or QSIG. 

If the Signaling mode is set to NONE, TRSP-ORIG, TRSP-ANSW, CAS 

or ROB BIT, the Mode of the PVCR channel can be DEDICATED or 

INACTIVE only. 

� Refer to HDLC Protocol on page 135 for notes on the Timeslot, 

Number of consecutive timeslots and DS0 speed parameters. 

� The other parameters behave as for a serial port set to the PVCR 

protocol. Refer to Configuring a WAN Link on page 90. 



FR-NET Protocol 

Note: FR-NET is available with all LINK signaling modes. 



CHICAGO>SE 

SETUP 






PORT #303> Protocol (def:OFF) ? FR-NET 











10000,def:10000) ? 

PORT #303> Reference port for conditional LMI (0-2000,def:0) ? 




� If the Signaling mode is set to EURO-ISDN, QSIG, INS-NET, NTT, KDD, 

NI1, NI2, 4ESS, 5ESS, DMS100 or QSIG, the Timeslot and Number of 

consecutive timeslots are selected automatically, and the following 

additional parameters are listed after Drop signals on LMI down: 

... 



PORT #313> Phone entry index (1-64,def:1) ? 

The Phone entry index refers to a phone profile for an ISDN 

connection, defined using the SETUP/PHONE submenu. Refer to 

ISDN Connection on page 96. 

� The other parameters behave as for a serial port set to the FR-NET 

protocol. Refer to FR-NET Port Parameters on page 104. 



FR-USER Protocol 

Note: FR-USER is available with all LINK signaling modes. 



CHICAGO>SE 

SETUP 






PORT #304> Protocol (def:OFF) ? FR-USER 







PORT #304> Report cycle (1-256,def:6) ? 





10000,def:10000) ? 


PORT #304> SVC address type (def:NONE) ? 



� If the Signaling mode is set to EURO-ISDN, QSIG, INS-NET, NTT, KDD, 

NI1, NI2, 4ESS, 5ESS, DMS100 or QSIG, the Timeslot and Number of 

consecutive timeslots are selected automatically, and the following 

additional parameters are listed after Drop signals on LMI down: 

... 







� No SVC parameters are available on the NetPerformer SIP 

VoIP option. 

� The other parameters behave as for a serial port set to the FR-USER 

protocol. Refer to FR-USER Port Parameters on page 102. 



Synchronous PPP Protocol 

Note: Synchronous PPP is available only when the Signaling mode on 

the LINK is set to NONE, EURO-ISDN, QSIG, INS-NET, NTT, KDD, NI1, NI2, 

4ESS, 5ESS, DMS100 or QSIG. 



CHICAGO>SE 

SETUP 






PORT #314> Protocol (def:OFF) ? PPP 

PORT #314> Timeslot.............................14 

PORT #314> Number of consecutive timeslots......1 




{000.000.000.000} 




PORT #314> Silent (def:SEND REQUEST) ? 

PORT #314> Link control protocol timeout (seconds) (1-255,def:3) ? 

PORT #314> Link control protocol retries, 255 = forever (0-255,def:255) 

? 

PORT #314> Negotiate MRU (def:NO) ? 

PORT #314> Use MRU proposed by peer (def:NO) ? 

PORT #314> Request Magic Number (def:YES) ? 

PORT #314> Accept Magic Number Request (def:YES) ? 

PORT #314> Accept Addresses Old Negotiation (def:NO) ? 

PORT #314> Request IP-Address (def:NO) ? 

PORT #314> Accept IP-Address Request (def:NO) ? 

PORT #314> Remote IP-Address (def:000.000.000.000) ? 




PORT #314> PPP dial index (def:NONE) ? 2 

IPDIAL 2> Incoming password type (def:NONE) ? 

IPDIAL 2> Incoming user name (def:) ? 

IPDIAL 2> Incoming password (def:) ? 

IPDIAL 2> Outgoing password type (def:NONE) ? 

IPDIAL 2> Outgoing user name (def:) ? 

IPDIAL 2> Outgoing password (def:) ? 

IPDIAL 2> Authentication retries, 255 = forever (0-255,def:3) ? 

IPDIAL 2> Fail delay (minutes) (0-255,def:0) ? 

IPDIAL 2> Maximum challenge interval (minutes) (1-255,def:60) ? 

IPDIAL 2> Authentication timeout (seconds) (1-255,def:10) ? 

� The Timeslot and Number of consecutive timeslots are selected 

automatically. 

� The other parameters behave as for a serial port set to the PPP 

protocol. Refer to PPP Port Parameters on page 185. 



PASSTHROUGH Protocol 

Note: PASSTHROUGH is available only when the Signaling mode on the 

LINK is set to NONE, TRSP-ORIG, TRSP-ANSW, CAS or ROB BIT. 



CHICAGO>SE 

SETUP 






PORT #308> Protocol (def:OFF) ? PASSTHROUGH 



PORT #308> Partner channel (def:NONE) ? 307 



� On a PASSTHROUGH channel a DS0 speed of 64000 indicates that 

the channel has 8 bits of data with no signaling. 56000 indicates it is 

a voice channel with signaling data that must be carried from one 

link to the other. 

� The Partner Channel defines the channel with which this channel 

exchanges passthrough traffic. Select another channel that has been 

defined with the PASSTHROUGH protocol. 

TRANSPARENT Protocol 

The TRANSPARENT protocol is used to establish a permanent point-topoint 

transparent signaling connection between digital interfaces (T1 or 

E1). TRANSPARENT is available on the standard NetPerformer only, 

when the Signaling mode on the LINK is set to NONE, TRSP-ORIG, TRSP- 

ANSW, CAS or ROB BIT. 



CHICAGO>SE 

SETUP 






PORT #309> Protocol (def:OFF) ? TRANSPARENT 


VOICE #309> Remote unit (def:NONE) ? BOSTON 

VOICE #309> Remote port number (1-65534,def:309) ? 

� The number of timeslots used is 1. 

� The Remote unit should be defined with the Unit ID of another 


� The default Remote port number is the local port number. 



Voice Channel Parameters 

The following voice protocols can be configured on a T1, E1 or ISDN- 

BRI interface card (depending on which voice codecs have been 

allocated to the DSPs; see Allocating DSPs on page 124): 

� ACELP-CN (page 141) 

� G723 (page 144) 

� G726 16K, G726 24K, G726 32K and G726 40K (page 145) 

� G729 (page 146) 

� G729A (page 147) 

� PCM64K (page 148). 

ACELP-CN Protocol 


NetPerformer console for the ACELP-CN protocol: 

CHICAGO>SE 

SETUP 






PORT #305> Protocol (def:OFF) ? ACELP-CN 


VOICE #305> DSP packets per frame 1234 

VOICE #305> 8K packetization selection (Y/N) ? YNNN 


VOICE #305> 6K packetization selection (Y/N) ? NNNNN 

VOICE #305> Comfort noise level (0-10,def:0) ? 

VOICE #305> Signaling type (def:IMMEDIATE START) ? 

VOICE #305> Local inbound voice level (db) (def:0) ? 

VOICE #305> Local outbound voice level (db) (def:-3) ? 

VOICE #305> Priority Level (0-10,def:0) ? 

VOICE #305> Echo canceler (def:ENABLE) ? 

VOICE #305> Double talk threshold (db) (def:6) ? 

VOICE #305> Pulse frequency (pps) (def:10) ? 

VOICE #305> Activation type (def:PREDEFINED) ? AUTODIAL 

VOICE #305> Speed dial number (def:NONE) ? 435 

VOICE #305> Link down busy (def:NO) ? 

VOICE #305> TONE type: (def:DTMF) ? 

VOICE #305> TONE regeneration: (0-255,def:255) ? 

VOICE #305> TONE ON (msec) (30-1000,inc:10,def:100) ? 

VOICE #305> TONE OFF (msec) (30-1000,inc:10,def:100) ? 

VOICE #305> Pulse make/break ratio (30-50,inc:4,def:34) ? 

VOICE #305> Fax/modem relay (def:FAX) ? 

VOICE #305> Maximum fax/modem rate (def:14400) ? 

VOICE #305> Remote unit (def:NONE) ? 


VOICE #305> Accept incoming ATM AAL1 calls (def:NO) ? 

� The number of timeslots used is 1. You can select which Timeslot 

you would like to use. 

� To set the buffering scheme for 8K and 6K packetization, enter N 

(no) or Y (yes) beneath the numbers indicated for the DSP packets 

per frame. Buffering adjusts the fallback options for this voice 

channel, and can be set to any available combination, providing 

fallback levels up to 5. 



� The Signaling type can be set to IMMEDIATE START, FXO, FXS, 

GND FXO, GND FXS, PLAR, WINK START or CUSTOM. 

Note: This parameter is available only when the Signaling mode on 

the LINK is set to CAS or ROB BIT. 

� If the Signaling type is set to FXO or GND FXO, additional 

parameters are presented for definition of the FXO seizure delay 

and FXO timeout: 

CHICAGO>SE 

SETUP 






PORT #305> Protocol (def:OFF) ? ACELP-CN 







VOICE #305> Signaling type (def:IMMEDIATE START) ? FXO 

VOICE #305> FXO seizure delay (def:DISABLE) ? 

VOICE #305> FXO timeout (sec) (6-99,def:30) ? 

... 

� The Local inbound voice level can be set to any integer value from - 

22 dB to 8 dB. 

� The Local outbound voice level can be set to any integer value from 

-22 dB to 12 dB. 

� Pulse frequency can be set to 10 or 20 pps. 

� The Priority Level and Link down busy parameters are requested on 

the standard NetPerformer only. 

� Link down busy can be set to NO, YES or BROADCAST. 

� The Activation type can be set to: 

� PREDEFINED, SWITCHED, AUTODIAL or BROADCAST on the 

standard NetPerformer 

� SWITCHED or AUTODIAL on the NetPerformer SIP VoIP option. 

� The Speed dial number is requested only when the Activation type is 

set to AUTODIAL. 

� The Fwd digits, Fwd type and Fwd delay parameters are requested 

when the Activation type is set to SWITCHED. 

� Fwd digits can be set to NONE or ALL on the NetPerformer SIP 

VoIP option; NONE, ALL or EXT on the standard NetPerformer. 

� Fwd type and Fwd delay are available only when the Signaling 

mode on the LINK is set to CAS or ROB BIT, and are presented at 

the console only if Fwd digits is set to ALL or EXT. 

� The Fwd type can be set to TONE or PULSE. 



� The Broadcast direction (RX or TX) and PVC number are requested 

when the Activation type is set to BROADCAST (standard 

NetPerformer only). 

� When the Activation type is set to SWITCHED on the standard 

NetPerformer, the Hunt Group active, Delete digits and Port 

extension number parameters are presented: 

... 


VOICE #101> Hunt Group active (def:NONE) ? 

VOICE #101> Delete digits (0-4,def:0) ? 

VOICE #101> Port extension number (def:101) ? 

VOICE #301> Fwd digits (def:NONE) ? 

... 

� The TONE type can be set to DTMF or MF. 

� The DTMF TONE regeneration parameter settings are as follows: 

Parameter Value DTMF Tone Regeneration 

0 always OFF 

1 always ON 

other numeric value number of seconds ON 

� On the NetPerformer SIP VoIP option, the parameters listed after 

Pulse make/break ratio are different from those listed on the 

standard NetPerformer console: 

... 


VOICE #104> Fax relay (def:FAX) ? 

VOICE #104> Maximum fax rate (def:14400) ? 

VOICE #104> Fax redundancy level (def:3) ? 

VOICE #104> Fwd digits (def:ALL) ? 

VOICE #104> Fwd type (def:TONE) ? 

VOICE #104> Fwd delay (msec) (0-10000,inc:250,def:0) ? 

VOICE #104> Enable DTMF ON-TIME configuration (def:NO) ? YES 

VOICE #104> DTMF ON-TIME duration (msec) (20-50,def:35) ? 

VOICE #104> Egress ANI operation mode (def:NONE) ? 

VOICE #104> Egress CHANNEL ANI digits (def:) ? 

VOICE #104> Ingress ANI operation mode (def:NONE) ? 

VOICE #104> Ingress CHANNEL ANI digits (def:) ? 

� Fax/modem relay on the standard NetPerformer can be set to NONE, 

FAX or BOTH. Fax relay on the NetPerformer SIP VoIP option can be 

set to NONE or FAX only. 

� The Maximum fax/modem rate (on standard NetPerformer) and 

Maximum fax rate (on NetPerformer SIP VoIP option) can be set to 

4800, 7200, 9600, 12000 or 14400. 

� The Fax redundancy level (on NetPerformer SIP VoIP option only) is 

used by a T.38 fax to retransmit fax negotiations in case of failure. 

Set this parameter to the number of retries permitted: 0, 1, 2 or 3. 

� The DTMF ON-TIME duration is requested only if you set the Enable 

DTMF ON-TIME configuration parameter to YES. 



� Egress ANI operation mode and Ingress ANI operation mode on the 

NetPerformer SIP VoIP option can be set to NONE, INSERT or 

ALWAYS. 

G723 Protocol 


NetPerformer console for the G723 protocol: 

CHICAGO>SE 

SETUP 






PORT #107> Protocol (def:OFF) ? G723 



VOICE #107> 6.4K packetization selection (Y/N) ? YNN 


VOICE #107> 5.3K packetization selection (Y/N) ? NNN 

VOICE #107> Comfort noise level (def:OFF) ? 







VOICE #107> Ring type (def:USA) ? 

VOICE #107> Activation type (def:PREDEFINED) ? 












� The buffering scheme is based on 6.4K and 5.3K packetization, and 

provides fallback levels up to 3. 

Note: If you set a Y for the 6.4K packetization selection parameter 

in the same position as a Y defined for the 5.3K packetization 

selection parameter, the buffering scheme will use the 6.4K 

packetization selection definition. 


GND FXO, GND FXS, PLAR, WINK START, R2-CHINA or CUSTOM. 



� The Ring type can be set to USA, UK, CANADA, GERMANY, FRANCE, 

ITALY, SPAIN, ISRAEL, JAPAN, AUSTRALIA, RUSSIA, POLAND or 

BRAZIL. 



� Configuration of a G.723 voice channel otherwise resembles that 

described for the ACELP-CN Protocol on page 141. Difference 

between the standard NetPerformer and NetPerformer SIP VoIP 

consoles are also noted there. 

G726 16K, G726 24K, G726 32K and G726 40K Protocols 

The G726 16K, G726 24K, G726 32K and G726 40K protocols are all 

configured in the same way, except for the Protocol setting. Here is a 

capture of the parameters that are presented at the standard 


CHICAGO>SE 

SETUP 






PORT #108> Protocol (def:OFF) ? G726 16K 



VOICE #108> Silence suppression level (1-5,def:1) ? 



















� There is no buffering (packetization selection) or Comfort Noise 

configuration on a G726 voice channel. 

� The Signaling type and Ring type parameters can be set to the same 

values as for a G723 voice channel, above. 

� Note that the Silence suppression level can be adjusted on a G726 

voice channel. This parameter is also requested when the protocol is 

set to G729, G729A or PCM64K. 

� Configuration of a G726 voice channel otherwise resembles that 






G729 Protocol 


NetPerformer console for the G729 protocol: 

CHICAGO>SE 

SETUP 






PORT #112> Protocol (def:OFF) ? G729 



VOICE #112> Packetization selection (Y/N) ? YNNNNNNN 




















� The buffering scheme is based on 8K packetization, providing 

fallback levels up to 8. 


GND FXO, GND FXS, PLAR, WINK START, R2-CHINA or CUSTOM. 



� Note that the Silence suppression level can be adjusted on a G729 

voice channel. 

� Configuration of a G729 voice channel otherwise resembles that 






G729A Protocol 

Here is a capture of the parameters that are presented at the 

NetPerformer SIP VoIP console for the G729A protocol: 

BOSTON>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/VLAN/USER/SIP,def:SLOT) ? 




PORT #307> Protocol (def:OFF) ? G729A 

PORT #307> Timeslot (1-24,def:6) ? 7 


VOICE #307> Packetization selection (Y/N) ? NYNNNNNN 








VOICE #307> Activation type (def:SWITCHED) ? 





VOICE #307> Fax relay (def:FAX) ? 

VOICE #307> Maximum fax rate (def:14400) ? 

VOICE #307> Fax redundancy level (def:3) ? 

VOICE #307> Fwd digits (def:ALL) ? 

VOICE #307> Fwd type (def:TONE) ? 

VOICE #307> Fwd delay (msec) (0-10000,inc:250,def:0) ? 

VOICE #307> Enable DTMF ON-TIME configuration (def:NO) ? YES 

VOICE #307> DTMF ON-TIME duration (msec) (20-50,def:35) ? 

VOICE #307> Egress ANI operation mode (def:NONE) ? INSERT 

VOICE #307> Egress CHANNEL ANI digits (def:) ? 

VOICE #307> Ingress ANI operation mode (def:NONE) ? ALWAYS 


� This example shows the differences between the standard 

NetPerformer and NetPerformer SIP VoIP consoles with respect to 

voice channel configuration. Refer to the notes provided in ACELP- 

CN Protocol on page 141. 

� Configuration of a G729A voice channel resembles that of a G729 

channel, described above, in all respects except the Protocol value 

entered. 



PCM64K Protocol 


NetPerformer console for the PCM64K protocol: 

CHICAGO>SE 

SETUP 






PORT #306> Protocol (def:OFF) ? PCM64K 


VOICE #306> Signaling type (def:IMMEDIATE START) ? FXO 













VOICE #306> TONE type: (def:DTMF) ? ? 

VOICE #306> TONE type: (DTMF/MF,def:DTMF) ? 









� The Signaling type can be set to IMMEDIATE START, FXO, FXS, GND 

FXO, GND FXS, PLAR, WINK START or CUSTOM. 

� Note: This parameter is available only when the Signaling mode on 


� The FXO seizure delay and FXO timeout appear only if the Signaling 

type is set to FXO or GND FXO. 

� The Ring type parameter appears only if the Signaling type is set to 

FXO, GND FXO or FXS. 



ISDN Caller ID Parameters 

� Note that a buffering scheme is available on the NetPerformer SIP 

VoIP option for the PCM64K protocol, providing fallback levels up to 

2: 

BOSTON>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/VLAN/USER/SIP,def:SLOT) ? 




PORT #305> Protocol (def:OFF) ? PCM64K 



VOICE #305> Packetization selection (Y/N) ? NY 


... 

� Configuration of a PCM64K voice channel otherwise resembles that 

of a G726 channel (see page 145). 

You can optionally define a set of callers that are authorized to access 

an ISDN connection on the NetPerformer. To configure a CALLER ID 

profile: 

� Enter the menu sequence: SE ↵ CALLER ID. 


� Enter appropriate values for the other CALLER ID parameters. 



CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:PHONE) ? CALLER ID 

Define authorized ISDN callers 

CALLER ID> Profile number (1-64,def:1) ? 1 

CALLER ID> #1> ISDN Number (def:) ? 4567890 

CALLER ID> #1> Sub address (def:) ? 1234 

� The ISDN Number defines the number of an authorized incoming 

call, and can be up to 21 digits long. 

� The Sub address is optional, and identifies a specific end device or 

service if multiple devices or services are available at the same 

ISDN number. 



Configuring an Analog Voice Connection 


� Define the physical port provided by an optional analog interface 

card (SE/SLOT/LINK), including the FXS, FXO and E&M interfaces 

(page 150). 

� Define the voice channels on the analog interface cards (SE/SLOT/ 

CHANNEL), including: 

� FXS channels (page 152) 

� FXO channels (page 153) 

� E&M channels (page 154). 

Analog Physical Port Parameters (LINK) 

To define the physical port on an FXS, FXO or E&M interface card: 




� Set the Status to ENABLE to activate the port. 

Note: If the physical link is disabled, all voice channels associated 

with this port are disabled, but the channel configuration is not lost. 

� Set the PCM encoding law to A-LAW or MU-LAW. 

The parameters presented at the console are identical on the standard 

NetPerformer and the NetPerformer SIP VoIP option for all analog 

interface cards: 

CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:PORT) ? SLOT 





Analog Voice Channel Parameters (CHANNEL) 

The analog channels of an FXS, FXO or E&M card transport voice traffic 

only. The voice protocols that are available on a particular card depend 

on the voice codecs allocated to the DSPs. Refer to Allocating DSPs on 

page 124. 

To define an analog voice channel on an FXS, FXO or E&M interface 

card: 





� Enter CHANNEL. 

� Select the Port number. Two ports are available on the FXS and FXO 

cards, numbered 1 and 2. Four ports are available on the E&M card, 

numbered 1 to 4. 

Note: All subsequent parameters carry a voice channel indicator, 

e.g. VOICE #102, where the first digit indicates the Slot number and 

the last digit indicates the Port number. 

� Set the Protocol. Depending on the DSP allocation, the Protocol can 

be set to the following voice algorithms: 

� ACELP-CN, G723, G726 16K, G726 24K, G726 32K, G726 40K, G729 

or G729A, PCM64K 

� Change the other analog channel parameters from their default 

values, if desired. The parameters listed differ slightly on the FXS, 

FXO and E&M interface cards. 

Note: In the following sections, only ACELP-CN examples are 

shown. Refer to Voice Channel Parameters on page 141 for notes on 

configuring the other voice protocols. 



FXS Channels 

Here is a capture of the voice channel parameters that are presented at 

the standard NetPerformer console for the FXS interface card: 

CHICAGO>SE 

SETUP 


CLASS/ 

PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:PORT) ? SLOT 



SLOT> Port number (1-2,def:1) ? 1 

VOICE #101> Protocol (def:OFF) ? ACELP-CN 

























VOICE #101> Ingress ANI operation mode (def:NONE) ? 


� Refer to Voice Channel Parameters on page 141 for notes on these 

parameters. 

� Note that the Ingress ANI operation mode and Ingress CHANNEL 

ANI digits parameters are requested on both the standard 

NetPerformer and NetPerformer SIP VoIP option. 

� The Speed dial number is requested when the Activation type is set 

to AUTODIAL. 

� The Fwd digits, Fwd type and Fwd delay parameters are requested 

when the Activation type is set to SWITCHED. 

� The Hunt Group active parameter is requested on the standard 

NetPerformer when the Activation type is set to SWITCHED or 

AUTODIAL. It can be set to A, B, C, D, E, F or NONE. 

� The Broadcast direction (RX or TX) and PVC number are requested 

when the Activation type is set to BROADCAST (standard 

NetPerformer only). 

� Other differences between the standard NetPerformer and 

NetPerformer SIP VoIP consoles for voice channel configuration are 

described in the section ACELP-CN Protocol on page 141. 



FXO Channels 


the standard NetPerformer console for the FXO interface card: 

CHICAGO>SE 

SETUP 











VOICE #201> Comfort noise level (def:0) ? 









VOICE #201> Impedance (def:DEFAULT) ? 














� Note the addition of the FXO seizure delay, FXO timeout and 

Impedance parameters. These parameters are requested for all 

Protocol types on the FXO card. 

� The Impedance can be set to DEFAULT or any multiple of 25 from 

500 to 1000. 

� Refer to Voice Channel Parameters on page 141 for notes on the 

other parameters. 

� Differences between the standard NetPerformer and NetPerformer 

SIP VoIP consoles for voice channel configuration are described in 

the section ACELP-CN Protocol on page 141. 



E&M Channels 


the standard NetPerformer console for the E&M interface card: 

CHICAGO>SE 

SETUP 











VOICE #401> Comfort noise level (def:0) ? 

VOICE #401> E&M signaling type (def:IMMEDIATE START) ? 

VOICE #401> Analog E&M type (def:4 WIRE) ? 

VOICE #401> TE timer (sec) (0-255,def:0) ? 



















� Note the addition of the E&M signaling type, Analog E&M type and 

TE timer parameters. These parameters are requested for all 

Protocol types on the E&M card. 

� The E&M signaling type can be set to IMMEDIATE START, 

WINK START or CUSTOM. 

� The Analog E&M type can be set to 2 WIRE or 4 WIRE. 

� The TE timer specifies the delay, in seconds, at which the E-lead 

follows the M-lead for Timed-E signaling. 

� Refer to Voice Channel Parameters on page 141 for notes on the 

other parameters. 

� Differences between the standard NetPerformer and NetPerformer 

SIP VoIP consoles for voice channel configuration are described in 

the section ACELP-CN Protocol on page 141. 



Configuring the Voice Mapping Table 

Although both the standard NetPerformer and the NetPerformer SIP 

VoIP option use Voice Mapping Table (MAP) entries to define how voice 

calls are set up, the way the MAP entries are defined differ extensively 

between the two product types. 

Setting up a Voice Mapping Table on the Standard 


The Voice Mapping Table on the standard NetPerformer includes 

definitions of speed dial numbers used for voice channels configured 

with Switched or Autodial activation. You can add, modify or delete a 

MAP entry. 

Adding a MAP Entry 

To define a new MAP entry for a Switched or Autodial voice channel: 

� Enter the menu sequence: SE ↵ MAP. 

� Set the Operation to ADD. 

� Enter a unique User entry digits string. 

� Change the other MAP parameters from their default values, if 

desired. 

Here is a capture of the MAP parameters that are presented at the 


CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:IPX) ? MAP 

Define speed dial numbers for voice mapping table 

MAP> Operation (ADD/MODIFY/DELETE,def:ADD) ? ADD 

MAP> User entry digits string (def:) : 459 

MAP> Destination name (def:) : BOSTON 

MAP> Remote extension number source (HUNT/USER/MAP,def:HUNT) ? 

MAP> Hunt group (A/B/C/D/E/F/ANY,def:A) ? 

MAP> Extended digits source (NONE/USER/MAP,def:NONE) ? USER 

MAP> Number of user extended digits, max length 30 (def:0) : 3 

MAP> Use SVC connection (NO/YES,def:NO) ? YES 

MAP> SVC address type (E.164/X.121,def:E.164) ? 

MAP> SVC network address (def:) : 123456 

MAP> Add another map entry (NO/YES,def:NO) ? 

Saving map entry... 

� The character * can be used as a wildcard character for the User 

entry digits string, if desired. 

Note: With the Voice Traffic Routing (VTR) function, the character ! 

(exclamation mark) can be used as a special wildcard character to 

concatenate user-dialed digits to the extended digits. During call 

setup the ! is replaced by the extended digits dialed by the user. For 



details on VTR, consult the NetPerformer System Reference Manual 

(Administration Guide) or the Addendum to the NetPerformer 

System Reference Manual for V9.0.0 to V9.2.0. 

� Set the Destination name to the Unit ID of another unit. Use * as a 

wildcard character, if desired. 

� The Remote extension number source can be set to HUNT, USER or 

MAP. 

� When it is set to HUNT you must specify the Hunt group: A, B, C, 

D, E, F or ANY. 

� When it is set to MAP you must specify the Destination extension 

number. 

� The Extended digits source can be set to NONE, USER or MAP. 

� When it is set to USER you must specify the Number of user 

extended digits. 

� When it is set to MAP you must specify the Extended digits to 

forward. 

� The SVC address type and SVC network address are requested only 

of the Use SVC connection parameter is set to YES. 

� The SVC network address defines the address of the remote 

location, and can be up to 15 characters long. 

Note: If you are using SVCs, the Management interface of the FR- 

USER port must be set to ANNEX-D. For the voice channels, set Fax/ 

Modem Relay to NONE if you do not intend to use fax/modem 

communications. If both SVCs and fax/modem will be used, the 

Maximum fax/modem rate of the voice channel must be set to the 

maximum speed the voice channel may require for fax or modem 

communications. 

� Enter YES at Add another map entry if you would like to create 

another new MAP entry. 

Modifying a MAP Entry 

You can modify a MAP entry that has already been defined: 


� Set the Operation to MODIFY. 

� Enter the User entry digits string of the MAP entry you want to 

modify. 

� Change the other MAP parameters from their current values, if 

desired. 

� Enter YES at Modify another map entry if you would like to modify 

another existing MAP entry. 



Deleting a MAP Entry 

To delete an entry from the Voice Mapping Table: 


� Set the Operation to DELETE. 

� Enter the User entry digits string of the MAP entry you want to 

delete. 

Caution: The MAP entry will be deleted immediately, with no 

confirmation requested. Enter the User entry digits string 

with care. 

� Enter YES at Delete another map entry if you would like to delete 


Note: You can delete all entries in the Voice Mapping Table 

simultaneously with the Erase Map File (EMF) command. Enter EMF at 

the console command prompt. 

Setting up a Voice Mapping Table on the NetPerformer SIP 

VoIP Option 

The Voice Mapping Table on the NetPerformer SIP VoIP option includes 

definitions of all dial numbers used for call setup on a voice channel. 

You can add, modify or delete a MAP entry. 

Adding a MAP Entry 

To define a new MAP entry for a voice channel: 


� Set the Operation to ADD. 

� Select the Map type (DIALSTRING, DIALIP or SUPERMAP). 

� For the DIALSTRING and DIALIP Map types, enter a unique Digits 

string. 

� Change the other MAP parameters from their default values, if 

desired. 



Here is a capture of the MAP parameters that are presented at the 


BOSTON>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/VLAN/USER/SIP,def:IPX) ? MAP 

Define speed dial numbers for voice mapping table 

MAP> Operation (ADD/MODIFY/DELETE,def:ADD) ? ADD 

MAP> Map type (DIALSTRING/DIALIP/SUPERMAP,def:DIALSTRING) ? DIALSTRING 

MAP> Digits string (def:) : 450 

MAP> Digits string length, max 30 (def:3) : 10 

MAP> Egress hunt group pattern (SEQUENTIAL/ROTARY/NONE,def:NONE) ? 

SEQUENTIAL 

MAP> Egress hunt group ports (i.e. 101,102,203 or 101,103-106) (def:) : 

201 

MAP> Strip prefix number of digits (def:I0 E0) : I2 E3 

MAP> Ingress/Egress prepend string (def:) : E604 

MAP> Ingress/Egress append string (def:) : I50E9 

MAP> Add another map entry (NO/YES,def:NO) ? YES 

MAP> Map type (DIALSTRING/DIALIP/SUPERMAP,def:DIALSTRING) ? DIALIP 

MAP> Digits string (def:) : 398 

MAP> Digits string length, max 30 (def:3) : 5 


ROTARY 


101-125 

MAP> Strip prefix number of digits (def:I0 E0) : 

MAP> Ingress/Egress prepend string (def:) : 

MAP> Ingress/Egress append string (def:) : 

MAP> Enter an IP address (def:000.000.000.000) ? 105.254.0.1 

MAP> Add another map entry (NO/YES,def:YES) ? 

MAP> Map type (DIALSTRING/DIALIP/SUPERMAP,def:DIALSTRING) ? SUPERMAP 


SEQUENTIAL 


101,201,203,103,104 

MAP> Strip prefix number of digits (def:I0 E0) : 

MAP> Ingress/Egress prepend string (def:) : 

MAP> Ingress/Egress append string (def:) : 

MAP> Add another map entry (NO/YES,def:YES) ? NO 

Saving map entry... 

The above example shows how all three Map types are configured: 

� The DIALSTRING Map type uses the Proxy server IP address 

specified in the SIP global parameters. Refer to Enable SIP and Set 

Up Global Properties on page 88. 

� For the DIALIP Map type, you must specify the IP address with the 

Enter an IP address parameter, which is requested later in the MAP 

definition. 

� The SUPERMAP Map type uses a digits string composed of 30 

wildcard characters (all asterisks: *). 

� It acts as a default entry for all VoIP calls, and accepts all digit 

strings with a minimum of 1 and maximum of 30 characters. 

� The NetPerformer determines that a dialing sequence is 

completed when the global (inter-digits) Dial timer expires or 

when the user terminates dialing with the pound sign (#). Refer 

to Defining the Global Characteristics on page 71. 



� The SUPERMAP entry uses the Proxy server IP address specified 

in the SIP global parameters. 

� Only one SUPERMAP entry can be defined on the NetPerformer 

SIP VoIP unit. 

� The SUPERMAP is always the last MAP entry to be processed. 

That is, the NetPerformer SIP VoIP option always tries to find a 

match using the other MAP entries in the Voice Mapping Table 

before attempting the SUPERMAP entry. 

Note: If you need to represent a range of digits to several 

destinations from another central site, define one or more 

DIALSTRING entries with wildcard characters (*) in the Digits string. 

For example, the Digits string 2** may be used to represent several 

different destinations, and permits the use of all numbers from 200 

to 299 to set up a call. 

� The Egress hunt group pattern can be set to: 

� SEQUENTIAL: for an ascending sequential search of all voice 

channels specified by the Egress hunt group ports parameter, 

always beginning with the first port defined in the sequence. 

� ROTARY: for an ascending sequential search of the Egress hunt 

group ports, beginning with the port after the last port 

investigated in the previous hunt. 

� NONE: suitable for outgoing calls, only. Incoming calls will fail 

with the alarm message SIP not available. 

Note: The hunt process continues until either an available port is 

found (and the NetPerformer proceeds with call connection) or the 

first port of the hunt process is reached again (and the NetPerformer 

produces a busy signal). 

� Values for the Strip prefix number of digits, Ingress/Egress prepend 

string and Ingress/Egress append string parameters can be 

identified with I for ingress and/or E for egress. Refer to Ingress and 

Egress Dial Rule Definitions, below. 

� The Strip prefix number of digits is the number of digits that are 

deleted from the beginning of the Digits string before proceeding 

with call setup over IP (ingress side) or over the destination voice 

hunt ports (egress side). 

� The Ingress/Egress prepend string defines the digits that are 

added at the beginning of the dial string. 

� The Ingress/Egress append string defines the digits that are 

added at the end of the dial string. 

Ingress and Egress Dial Rule Definitions 

For a single MAP entry, rules can be applied on both inbound and 

outbound calls by allowing for the parsing of ingress and egress rule 

definitions. The letters I (for ingress) and E (for egress) distinguish the 

two sides in the rule definition string. 



� The I and E values can be concatenated, separated by a space or a 

slash in the rule definition string. 

� Examples of valid values for Strip prefix number of digits are I3E4 

and I3 E4, both of which remove 3 digits on the ingress side and 4 

digits on the egress side. 

Ingress Dial Rule Example 

� Digits string: 987****** 

� Strip prefix number of digits: I3 

If in ingress, strip the first 3 digits of the dial string. 

� Ingress/Egress prepend string: I1234 

If in ingress, add the string 1234 at the beginning of the dial string. 

� Ingress/Egress append string: I4567 

If in ingress, add the string 4567 at the end of the dial string. 

With this definition, the dial string 987654321 in ingress results in 

12346543214567 before the NetPerformer proceeds with call setup over 

IP. 

Egress Dial Rule Example 

� Digits string: 1234********** 

� Strip prefix number of digits: E10 

If in egress, strip the first 10 digits of the received string. 

� Ingress/Egress prepend string: E9, 

If in egress, add the string 9, at the beginning of the received string. 

� Ingress/Egress append string: E8 

If in egress, add an 8 at the end of the received string. 

With this definition, the dial string 12346543214567 in egress results in 

9,45678 before being forwarded to the voice ports defined with Egress 

hunt group ports. 

Note: To allow these digits to be passed to the attached PBX or PSTN 

network, the Fwd digits parameter on the voice channel must be set to 

ALL. 

Ingress/Egress Dial Rule Example 

� Digits string: 987****** 

� Strip prefix number of digits: I2E3 

If in ingress, strip the first 2 digits. If in egress, strip the first 3 

digits. 

� Ingress/Egress prepend string: I123E45 



If in ingress, prepend the string 123. If in egress, prepend the string 

45. 

� Ingress/Egress append string: I456E9 

If in ingress, append the string 456. If in egress, append the string 9. 

With this definition, the dial string 987654321 in ingress results in 

1237654321456 before the NetPerformer proceeds with call setup over 

IP. The dial string 987654321 in egress results in 456543219 before 

forwarding the digits to the PBX or PSTN. 

Modifying a MAP Entry 

You can modify a MAP entry that has already been defined: 


� Set the Operation to MODIFY. 

� At the Modify map type prompt: 

� Enter SUPERMAP to modify the SUPERMAP entry, or 

� Enter STANDARD to modify a DIALSTRING or DIALIP entry. 

� If you selected STANDARD for the Modify map type prompt, enter 

the Digits string of the MAP entry you want to modify. 

Note: The Dial string is not required if you are modifying the 

SUPERMAP entry. 

� Change the other MAP parameters from their current values, if 

desired. 

� Enter YES at Modify another map entry if you would like to modify 


Deleting a MAP Entry 

To delete an entry from the Voice Mapping Table: 


� Set the Operation to DELETE. 

� At the Delete map type prompt: 

� Enter SUPERMAP to delete the SUPERMAP entry, or 

� Enter STANDARD to delete a DIALSTRING or DIALIP entry. 

� If you selected STANDARD for the Delete map type prompt, enter 

the Digits string of the MAP entry you want to delete. 

Note: The Dial string is not required if you are deleting the 

SUPERMAP entry. 

Caution: The MAP entry will be deleted immediately, with no 

confirmation requested. Enter the Digits string with care. 



� Enter YES at Delete another map entry if you would like to delete 


Note: You can delete all entries in the Voice Mapping Table 

simultaneously with the Erase Map File (EMF) command. Enter EMF at 

the console command prompt. 

Configuring Hunt Forwarding on the Standard 


Hunt Forwarding is available for voice and SVC functions on the 

standard NetPerformer. To define the Hunt Forwarding parameters: 

� Enter the menu sequence: SE ↵ HUNT. 

� Select the Hunt group (A, B, C, D, E or F). 

� Change the other Hunt parameters from their default values, if 

desired. 

Here is a capture of the Hunt parameters that are presented at the 


CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:CUSTOM) ? HUNT 

HUNT> Hunt group (A/B/C/D/E/F,def:A) ? A 

HUNT A> Next destination (def:) ? BOSTON 

HUNT A> Next DLCI (0-1022,def:0) ? 103 

HUNT A> Next SVC network address (def:) ? 12345 

� If you leave the Next destination undefined, the Hunt mechanism 

will check the Next SVC network address parameter for the next 

destination. 

� If you leave the Next DLCI parameter at its default value, 0, the 

Hunt mechanism will not use a DLCI to carry out hunt forwarding for 

this Hunt group. 

� If you leave the Next SVC network address undefined, the Hunt 

mechanism will not use an SVC network address to carry out hunt 

forwarding for this Hunt group. 

Note: If the Next destination parameter is also undefined, the Hunt 

mechanism will not carry out any form of hunt forwarding for this 

Hunt group. 



Defining Custom Signaling Characteristics 

Line signaling is the call state signaling used to establish and clear a 

call. The NetPerformer allows you to define custom signaling 

characteristics that may be required for call setup in your application, 

especially if you are using non-standard equipment. 

� The main board of the NetPerformer sends these customized 

parameter values to the Signaling Engine for control of the signaling 

and ring on analog and digital voice connections. For further 

information on line signaling characteristics, refer to the Hardware 

Installation Guide for your NetPerformer model. 

� The way you define the line signaling characteristics affects the way 

a voice channel is brought up, maintained and terminated when it is 

configured with the CUSTOM Signaling type. 

Note: The voice channel Signaling type must be set to 

CUSTOM for line signaling customization to take effect. 

Caution: The procedures described in this section are intended 

for experienced users and technical personnel only. Inappropriate 

changes to line signaling characteristics can introduce unwanted 

delays and prevent call completion or proper call termination. If 

you are not fully familiar with line signaling 

characteristics, do not make any changes to the 

NetPerformer configuration using the CUSTOM submenu. 

Note: If you do not configure custom signaling, the NetPerformer will 

use the standard values associated with the line signaling protocol. This 

protocol is determined from the current value of the Signaling type 

parameter for the voice channel. Refer to Digital Voice/Data Channel 

Parameters (CHANNEL) on page 133 and Analog Voice Channel 

Parameters (CHANNEL) on page 150). 

Customizing the Line Signaling 

To customize the line signaling characteristics to support non-standard 

equipment: 

� Enter the menu sequence: SE ↵ CUSTOM ↵ SIGNALING. 

Note: You can access all Custom parameters by entering the menu 

sequence: SE ↵ CUSTOM ↵ ALL. 

� Set Load standard signaling template to YES to load a standard 

signaling template, if desired. 

Caution: This will overwrite the current configuration of all 

custom signaling parameters. You must confirm this 

action. 

� Each template defines a standard line signaling protocol, 

including the default parameter values associated with that 

protocol. 



� When you start with a standard signaling template, you need to 

change only those parameters that are unique to your 

application. 

Note: If you do not load a standard signaling template (Load 

standard signaling template set to NO), the software will use the 

last-configured Custom Signaling values as the starting definition. 

� If you confirm Load standard signaling template with YES, select the 

standard signaling template at the Select template prompt. 

Select template can be set to IMMEDIATE START, R2, FXO, FXS, GND 

FXO, GND FXS, PLAR, WINK START or R2-CHINA. 

� Select a Configuration item, choosing from: IDLE, SEIZURE, 

PULSE DIAL, WINK, CLEAR BACK, CLEAR FORWARD, ANSWERED, 

RING or ALL. 

� Change the custom signaling parameters from their default values, 

if desired. 

Note: Parameters denoting a length of time are entered in 

milliseconds. All other entries must be made in hexadecimal 

notation. 


NetPerformer and the NetPerformer SIP VoIP option. Here is an 

example where the currently configured signaling type (IMMEDIATE 

START) is used as the basis for customization: 

CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:MAP) ? CUSTOM 

CUSTOM PARAMETERS> Item (SIGNALING/RING CADENCE/ERROR CAUSE CODE/ 

ALL,def:ALL) ? SIGNALING 

Load standard signaling template (NO/YES,def:NO) ? NO 

CUSTOM SIG> Current signaling type..............IMMEDIATE START 

Configuration item (IDLE/SEIZURE/PULSE DIAL/WINK/CLEAR BACK/ 

CLEAR FORWARD/ANSWERED/RING/ALL,def:ALL) ? IDLE 

CUSTOM SIG> Idle detect minimum time (ms) (0-1000000,def:600) ? 

CUSTOM SIG> Idle detect maximum time (ms) (0-1000000,def:0) ? 

CUSTOM SIG> Idle detect start pattern (def:00000000) ? 

CUSTOM SIG> Idle detect start pattern mask (def:0000000C) ? 

CUSTOM SIG> Idle detect finish pattern (def:00000000) ? 

CUSTOM SIG> Idle detect finish pattern mask (def:00000000) ? 

CUSTOM SIG> Idle generate start time (ms) (0-1000000,def:0) ? 

CUSTOM SIG> Idle generate finish time (ms) (0-1000000,def:0) ? 

CUSTOM SIG> Idle generate start pattern (def:00000000) ? 

CUSTOM SIG> Idle generate start pattern mask (def:0000000C) ? 

CUSTOM SIG> Idle generate finish pattern (def:00000000) ? 

CUSTOM SIG> Idle generate finish pattern mask (def:0000000C) ? 



Here is an example where another signaling template (R2) has been 

loaded as the basis for customization: 

CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:GLOBAL) ? CUSTOM 



Load standard signaling template (NO/YES,def:NO) ? YES 

Warning, this will override the custom signaling currently configured. 

Are you sure (NO/YES,def:NO) ? YES 

Select template (def:IMMEDIATE START) ? R2 


CLEAR FORWARD/ANSWERED/RING/ALL,def:ALL) ? SEIZURE 

CUSTOM SIG> Seizure detect minimum time (ms) (0-1000000,def:50) ? 

CUSTOM SIG> Seizure detect maximum time (ms) (0-1000000,def:0) ? 

CUSTOM SIG> Seizure detect start pattern (def:00000000) ? 

CUSTOM SIG> Seizure detect start pattern mask (def:0000000C) ? 

CUSTOM SIG> Seizure detect finish pattern (def:00000000) ? 

CUSTOM SIG> Seizure detect finish pattern mask (def:00000000) ? 

CUSTOM SIG> Seizure generate start time (ms) (0-1000000,def:524287) ? 

CUSTOM SIG> Seizure generate finish time (ms) (0-1000000,def:524287) ? 

CUSTOM SIG> Seizure generate start pattern (def:00000000) ? 

CUSTOM SIG> Seizure generate start pattern mask (def:0000000C) ? 

CUSTOM SIG> Seizure generate finish pattern (def:0007FFFF) ? 

CUSTOM SIG> Seizure generate finish pattern mask (def:0007FFFF) ? 

The parameters listed for each Configuration item are discussed 

separately in the following sections. 

Idle Parameters 

To define customized IDLE line signaling characteristics: 

� Set the Configuration item to IDLE. 

� Change the IDLE signaling parameters from their default values, if 

desired. 

An example of the IDLE parameters is given on page 164. 

Seizure Parameters 

To define customized SEIZURE line signaling characteristics: 

� Set the Configuration item to SEIZURE. 

� Change the SEIZURE signaling parameters from their default values, 

if desired. 

An example of the SEIZURE parameters is given on page 165. 

Pulse Dial Parameters 

To define customized PULSE DIAL line signaling characteristics: 

� Set the Configuration item to PULSE DIAL. 

� Change the PULSE DIAL signaling parameters from their default 




Here is an example using the IMMEDIATE START signaling template: 

CHICAGO>SE 

SETUP 








CLEAR FORWARD/ANSWERED/RING/ALL,def:ALL) ? PULSE DIAL 

CUSTOM SIG> Pulse dial detect make minimum time (ms) (0-1000000,def:30) 

? 

CUSTOM SIG> Pulse dial detect make maximum time (ms) (0-1000000,def:50) 

? 

CUSTOM SIG> Pulse dial detect break minimum time (ms) (0-1000000,def:50) 

? 

CUSTOM SIG> Pulse dial detect break maximum time (ms) (0-1000000,def:80) 

? 

CUSTOM SIG> Pulse dial detect start pattern (def:00000008) ? 

CUSTOM SIG> Pulse dial detect start pattern mask (def:0000000C) ? 

CUSTOM SIG> Pulse dial detect finish pattern (def:00000000) ? 

CUSTOM SIG> Pulse dial detect finish pattern mask (def:0000000C) ? 

CUSTOM SIG> Pulse dial generate start time (ms) (0-1000000,def:40) ? 

CUSTOM SIG> Pulse dial generate finish time (ms) (0-1000000,def:60) ? 

CUSTOM SIG> Pulse dial generate inter digit time (ms) (0- 

1000000,def:400) ? 

CUSTOM SIG> Pulse dial generate start pattern (def:00000008) ? 

CUSTOM SIG> Pulse dial generate start pattern mask (def:0000000C) ? 

CUSTOM SIG> Pulse dial generate finish pattern (def:00000000) ? 

CUSTOM SIG> Pulse dial generate finish pattern mask (def:0000000C) ? 

Wink Parameters 

To define customized WINK line signaling characteristics: 

� Set the Configuration item to WINK. 

� Change the WINK signaling parameters from their default values, if 

desired. 


CHICAGO>SE 

SETUP 








CLEAR FORWARD/ANSWERED/RING/ALL,def:ALL) ? WINK 

CUSTOM SIG> Wink detect minimum time (ms) (0-1000000,def:524287) ? 

CUSTOM SIG> Wink detect maximum time (ms) (0-1000000,def:524287) ? 

CUSTOM SIG> Wink detect start pattern (def:0007FFFF) ? 

CUSTOM SIG> Wink detect start pattern mask (def:0007FFFF) ? 

CUSTOM SIG> Wink detect finish pattern (def:0007FFFF) ? 

CUSTOM SIG> Wink detect finish pattern mask (def:0007FFFF) ? 

CUSTOM SIG> Wink generate start time (ms) (0-1000000,def:524287) ? 

CUSTOM SIG> Wink generate finish time (ms) (0-1000000,def:524287) ? 

CUSTOM SIG> Wink generate start pattern (def:0007FFFF) ? 

CUSTOM SIG> Wink generate start pattern mask (def:0007FFFF) ? 

CUSTOM SIG> Wink generate finish pattern (def:0007FFFF) ? 

CUSTOM SIG> Wink generate finish pattern mask (def:0007FFFF) ? 



Clear Back Parameters 

To define customized CLEAR BACK line signaling characteristics: 

� Set the Configuration item to CLEAR BACK. 

� Change the CLEAR BACK signaling parameters from their default 



CHICAGO>SE 

SETUP 








CLEAR FORWARD/ANSWERED/RING/ALL,def:ALL) ? CLEAR BACK 

CUSTOM SIG> Clear back detect minimum time (ms) (0-1000000,def:50) ? 

CUSTOM SIG> Clear back detect maximum time (ms) (0-1000000,def:500) ? 

CUSTOM SIG> Clear back detect start pattern (def:0000000C) ? 

CUSTOM SIG> Clear back detect start pattern mask (def:0000000C) ? 

CUSTOM SIG> Clear back detect finish pattern (def:0007FFFF) ? 

CUSTOM SIG> Clear back detect finish pattern mask (def:0007FFFF) ? 

CUSTOM SIG> Clear back generate start time (ms) (0-1000000,def:100) ? 

CUSTOM SIG> Clear back generate finish time (ms) (0-1000000,def:524287) 

? 

CUSTOM SIG> Clear back generate start pattern (def:0000000C) ? 

CUSTOM SIG> Clear back generate start pattern mask (def:0000000C) ? 

CUSTOM SIG> Clear back generate finish pattern (def:0007FFFF) ? 

CUSTOM SIG> Clear back generate finish pattern mask (def:0007FFFF) ? 

Clear Forward Parameters 

To define customized CLEAR FORWARD line signaling characteristics: 

� Set the Configuration item to CLEAR FORWARD. 

� Change the CLEAR FORWARD signaling parameters from their 

default values, if desired. 


CHICAGO>SE 

SETUP 








CLEAR FORWARD/ANSWERED/RING/ALL,def:ALL) ? CLEAR FORWARD 

CUSTOM SIG> Clear forward detect minimum time (ms) (0-1000000,def:50) ? 

CUSTOM SIG> Clear forward detect maximum time (ms) (0-1000000,def:500) ? 

CUSTOM SIG> Clear forward detect start pattern (def:00000008) ? 

CUSTOM SIG> Clear forward detect start pattern mask (def:0000000C) ? 

CUSTOM SIG> Clear forward detect finish pattern (def:0007FFFF) ? 

CUSTOM SIG> Clear forward detect finish pattern mask (def:0007FFFF) ? 

CUSTOM SIG> Clear forward generate start time (ms) (0-1000000,def:100) ? 

CUSTOM SIG> Clear forward generate finish time (ms) (0- 

1000000,def:524287) ? 

CUSTOM SIG> Clear forward generate start pattern (def:00000008) ? 

CUSTOM SIG> Clear forward generate start pattern mask (def:0000000C) ? 

CUSTOM SIG> Clear forward generate finish pattern (def:0007FFFF) ? 

CUSTOM SIG> Clear forward generate finish pattern mask (def:0007FFFF) ? 



Answered Parameters 

To define customized ANSWERED line signaling characteristics: 

� Set the Configuration item to ANSWERED. 

� Change the ANSWERED signaling parameters from their default 



CHICAGO>SE 

SETUP 








CLEAR FORWARD/ANSWERED/RING/ALL,def:ALL) ? ANSWERED 

CUSTOM SIG> Answer detect minimum time (ms) (0-1000000,def:50) ? 

CUSTOM SIG> Answer detect maximum time (ms) (0-1000000,def:500) ? 

CUSTOM SIG> Answer detect start pattern (def:00000004) ? 

CUSTOM SIG> Answer detect start pattern mask (def:0000000C) ? 

CUSTOM SIG> Answer detect finish pattern (def:0007FFFF) ? 

CUSTOM SIG> Answer detect finish pattern mask (def:0007FFFF) ? 

CUSTOM SIG> Answer generate start time (ms) (0-1000000,def:100) ? 

CUSTOM SIG> Answer generate finish time (ms) (0-1000000,def:524287) ? 

CUSTOM SIG> Answer generate start pattern (def:00000004) ? 

CUSTOM SIG> Answer generate start pattern mask (def:0000000C) ? 

CUSTOM SIG> Answer generate finish pattern (def:0007FFFF) ? 

CUSTOM SIG> Answer generate finish pattern mask (def:0007FFFF) ? 

Ring Parameters 

To define customized RING line signaling characteristics: 

� Set the Configuration item to RING. 

� Change the RING signaling parameters from their default values, if 

desired. 


CHICAGO>SE 

SETUP 








CLEAR FORWARD/ANSWERED/RING/ALL,def:ALL) ? RING 

CUSTOM SIG> Ring generate start pattern (def:0007FFFF) ? 

CUSTOM SIG> Ring generate start pattern mask (def:0007FFFF) ? 

CUSTOM SIG> Ring generate finish pattern (def:0007FFFF) ? 

CUSTOM SIG> Ring generate finish pattern mask (def:0007FFFF) ? 



Customizing the Ring Cadence 

The ring cadence consists of one or two initial cadences, followed by 

one or two cadences that loop continuously. By default, the 

NetPerformer ring cadence is set to the North American standard, 

where both the initial and looped cadences are 2 seconds on, 4 seconds 

off. 

To customize the ring cadence that the NetPerformer uses when 

generating a ring: 

� Enter the menu sequence: SE ↵ CUSTOM ↵ RING CADENCE. 



� Change the RING CADENCE parameters from their default values, if 

desired. 



CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:CUSTOM) ? 


ALL,def:SIGNALING) ? RING CADENCE 

CUSTOM RING> Specify initial cadence (NO/YES,def:NO) ? YES 

CUSTOM RING> Initial ring on period (ms) (1-10000,def:2000) ? 

CUSTOM RING> Initial ring off period (ms) (1-10000,def:4000) ? 

CUSTOM RING> Add more initial cadence parameters (NO/YES,def:NO) ? YES 

CUSTOM RING> Initial ring on period (ms) (1-10000,def:2000) ? 


CUSTOM RING> Loop ring on period (ms) (1-10000,def:2000) ? 

CUSTOM RING> Loop ring off period (ms) (1-10000,def:4000) ? 

� Set Specify initial cadence to YES if you want to define an Initial ring 

on period and Initial ring off period. For example, the ring used in 

the United Kingdom has a slightly different cadence on the first ring 

(the initial cadence) than the following rings (the loop cadence). 

Note: If you leave this parameter at its default value, NO, the 

cadence of all rings is defined with the loop cadence parameters. 

� The Initial ring on period is the duration that the phone will ring 

on the first ring. 

� The Initial ring off period is the interval between the end of the 

first ring and the start of the second ring. 

� Set Add more initial cadence parameters to YES if you want the 

NetPerformer to generate a second special ring cadence before it 

commences the looped ring cadence. 

� Set the Loop ring on period to the duration that the phone should 

ring on the second and subsequent rings (or on all rings if an initial 

cadence is not defined). For example, the North American ring 

cadence has a Loop ring on period of 2000 ms. 



� Set the Loop ring off period to the interval between the end of the 

second ring and the start of the third ring, and between all 

subsequent rings (or between all rings if an initial cadence is not 

defined). For example, the North American ring cadence has a Loop 

ring off period of 4000 ms. 

� If Specify initial cadence is set to NO an additional prompt, Add 

more cadence parameters, appears at the end of the parameter 

listing. Enter YES at this prompt if you want the NetPerformer to 

include a second ring on/ring off sequence in the looped ring 

cadence. The Loop ring on period and Loop ring off period 

parameters will be listed again. 

Note: Since the Custom Ring Cadence parameters are highly 

dependent on each other in producing the ring cadence, you must enter 

valid values (or press the Enter key, ↵) for all parameters presented in 

the SETUP/CUSTOM/RING CADENCE submenu. You cannot escape early 

from this menu with the key. 

Examples of Custom Ring Definitions 

You can define four different Custom Ring Cadence scenarios on the 

NetPerformer: 

� 1 continuously looped ring cadence: 

CHICAGO>SE 

SETUP 





CUSTOM RING> Specify initial cadence (NO/YES,def:NO) ? NO 

CUSTOM RING> Loop ring on period (ms) (1-10000,def:2000) ? 1500 

CUSTOM RING> Loop ring off period (ms) (1-10000,def:4000) ? 3000 

Result: on-1500, off-3000, on-1500, off-3000, on-1500, off-3000, 

on-1500, off-3000, on-1500, off-3000... 

� 2 different initial ring cadences followed by 1 continuously looped 

ring cadence: 

CHICAGO>SE 

SETUP 






CUSTOM RING> Initial ring on period (ms) (1-10000,def:2000) ? 500 

CUSTOM RING> Initial ring off period (ms) (1-10000,def:4000) ? 500 

CUSTOM RING> Add more initial cadence parameters (NO/YES,def:NO) ? YES 






on-2000, off-500, on-2000, off-500... 



� 1 initial ring cadence followed by 2 different looped ring cadences 

that alternate continuously: 

CHICAGO>SE 

SETUP 







CUSTOM RING> Initial ring off period (ms) (1-10000,def:4000) ? 500 

CUSTOM RING> Add more initial cadence parameters (NO/YES,def:NO) ? NO 



CUSTOM RING> Add more cadence parameters (NO/YES,def:NO) ? YES 




on-1000, off-500, on-2000, off-500... 

� 3 looped ring cadences executed in rotation continuously: 

CHICAGO>SE 

SETUP 





CUSTOM RING> Specify initial cadence (NO/YES,def:NO) ? NO 


CUSTOM RING> Loop ring off period (ms) (1-10000,def:4000) ? 500 








on-500, off-500, on-1000, off-500, on-2000, off-500... 

Customizing the Error Cause Code 

To customize the error cause codes that the NetPerformer will use when 

line signaling problems are encountered: 

� Enter the menu sequence: SE ↵ CUSTOM ↵ ERROR CAUSE CODE. 



� Change the ERROR CAUSE CODE parameters from their default 


Note: If you do not change their values, they will be 

indistinguishable from each other, as all are set to 0 by default. 





Defining NAT Characteristics 


Network Considerations 

CHICAGO>SE 

SETUP 




ALL,def:RING CADENCE) ? ERROR CAUSE CODE 

ERROR CAUSE CODE> Voice algorithm mismatch (0-127,def:0) ? 20 

ERROR CAUSE CODE> No destination in map (0-127,def:0) ? 30 

ERROR CAUSE CODE> Network clear switch down (0-127,def:0) ? 40 

� Enable NAT connections (page 173) 

� Define the NAT rules (IP/NAT/RULE, page 174) 

� Define the NAT ports (IP/NAT/PORT, page 176) 

� Define the NAT timeouts (IP/NAT/TIMEOUT, page 177) 

� Define specific NAT services (IP/NAT/SERVICE, page 178). 

Although Network Address Translation (NAT) provides a simple solution 

to IP address depletion, it is not always appropriate for all types of 

networks. NAT must be configured very carefully, or avoided altogether, 

for the following types of networks and protocols: 

� Private networks (for example, a corporate network) that use a 

public backbone to communicate between locations. This type of 

application usually involves a large number of hosts communicating 

across the backbone, and requires a large translation table. Also, 

more applications in these networks will use configured addresses 

rather than going to a name server. 

Note: A workaround using encapsulation at the border routers can 

be set up, with one global address at each NAT router used for 

tunneling through the backbone. This is supported on the 

NetPerformer using a NAPT configuration. 

� Any network that does not have a sparse end-to-end traffic matrix. 

Once again, such networks require large NAT translation tables, 

which impedes overall performance. 

� Encrypted protocols or applications with address content in the 

payload cannot be supported by NAT because of their dependence 

on the use of these addresses. 



Configuration Hints 

Enabling NAT 

Note: If a protocol contains IP addresses or transport identifiers 

inside the packet payload, and the NetPerformer does not support 

the protocol used, the end results of NAT cannot be guaranteed. 

� The fundamental role of NAT is to change the address in the IP 

header of a packet. Therefore, techniques that protect the content 

of IP headers (such as IPsec, AH and ESP) cannot be used in 

conjunction with NAT. 

Note: Security techniques that do not depend on IP addresses will 

work correctly with NAT, for example, application layer techniques 

such as TLS, SSL and SSH. Also, end-to-end ESP-based transport 

mode authentication and confidentiality are permissible for packets 

such as ICMP, whose IP payload content is not affected by 

translation of the outer IP header. 

The following points should be kept in mind when you set up your 

network for NAT. 

� There must be no overlap between the local IP addresses on the 

internal network and the globally unique NAT IP addresses on the 

external network. Any given address must be clearly identifiable as 

either a local address or a global address. 

� You must take great care to define all addresses and 

correspondences between IP and NAT IP addresses correctly, to 

avoid the routing problems associated with misaddressing. 

� You can introduce NAT incrementally, if desired. If an existing stub 

domain is running out of unique internal addresses, you can change 

the addresses subnet by subnet to local IP addresses, and let NAT 

use the freed up addresses for communication outside the domain. 

� The router running NAT should never advertise the internal networks 

to the backbone. Only those networks that have been assigned 

global addresses may be known outside the stub. 

Note: Global information that NAT receives from a stub border 

router can be advertised in the stub domain in the usual way. 

To enable NAT on a NetPerformer connection (WAN link, PPP port, LAN 

port or PVC): 

� Access the appropriate sub-menu for the connection you want to 

include in NAT: 

� For a LAN port, enter the menu sequence SE ↵ PORT followed by 

ETH. For details, refer to Configuring a LAN Interface on page 84. 



IP NAT Rule Parameters 

� For a WAN link or PPP port, enter the menu sequence SE ↵ PORT 

followed by the port number, or SE ↵ SLOT ↵ CHANNEL followed 

by the channel number. For details, refer to Configuring a WAN 

Link on page 90 or PPP Port Parameters on page 185 

� For a PVC, enter the menu sequence SE ↵ PVC followed by the 

PVC number. For details, refer to Defining the Frame Relay 


Note: The PVC Mode must be set to PVCR or RFC-1490. 

� Set the NAT Enable parameter to YES. 

� Select which NAT rule will be used for this connection. 

� Specify whether the NAT side is INTERNAL or EXTERNAL. 

A NAT rule defines the correspondence between internal IP addresses 

and external, globally unique NAT IP addresses. On the NetPerformer, 

the IP NAT rules determine the type of address translation that takes 

place, the range of addresses before and after translation, and which 

rule is executed if more than one applies. 

Note: IP NAT Rules are applied in ascending numerical order. For 

example, an attempt to match a packet to RULE #1 is executed before 

RULE #10. Although more than one IP NAT Rule may apply to a single 

frame, only one can be executed – the lowest numbered rule. 

To define the IP NAT rules: 

� Enter the menu sequence: SE ↵ IP ↵ NAT ↵ RULE. 

� Select an IP NAT rule number. 

� Change the other IP NAT rule parameters from their default values, 

if desired. 



CHICAGO>SE 

SETUP 




def:GLOBAL) ? NAT 

Item (RULE/PORT/TIMEOUT/SERVICE,def:RULE) ? RULE 

IP NAT rule number (1/2/3/4/5/6/7/8/9/10,def:1) ? 1 

IP NAT RULE #1> Translation type (def:DYNAMIC) ? 

IP NAT RULE #1> IP source address min (def:000.000.000.000) ? 

IP NAT RULE #1> IP source address max (def:000.000.000.000) ? 

IP NAT RULE #1> NAT IP source address min (def:000.000.000.000) ? 

IP NAT RULE #1> NAT IP source address max (def:000.000.000.000) ? 

IP NAT RULE #1> IP destination address min (def:000.000.000.000) ? 

IP NAT RULE #1> IP destination address max (def:000.000.000.000) ? 

IP NAT RULE #1> NAT IP destination address min (def:000.000.000.000) ? 

IP NAT RULE #1> NAT IP destination address max (def:000.000.000.000) ? 

IP NAT RULE #1> Pool size (0-2500,def:100) ? 



� The Translation type can be STATIC or DYNAMIC. 

When the Translation type is set to STATIC, NAT IP source and 

destination parameters refer to network addresses rather than a 

smaller range of IP addresses: 

CHICAGO>SE 

SETUP 



Item (GLOBAL/STATIC/BOOTP/OSPF/TIMEP/SNMP/NAT/TELNET/FTP/DNS,def:NAT) ? 

Item (RULE/PORT/TIMEOUT/SERVICE,def:RULE) ? RULE 

IP NAT rule number (1/2/3/4/5/6/7/8/9/10,def:1) ? 2 

IP NAT RULE #2> Translation type (def:DYNAMIC) ? STATIC 

IP NAT RULE #2> IP source address min (def:000.000.000.000) ? 

IP NAT RULE #2> IP source address max (def:000.000.000.000) ? 

IP NAT RULE #2> NAT IP source network (def:000.000.000.000) ? 

IP NAT RULE #2> NAT IP source network mask (0-24,def:0) ? 

{000.000.000.000} 

IP NAT RULE #2> IP destination address min (def:000.000.000.000) ? 

IP NAT RULE #2> IP destination address max (def:000.000.000.000) ? 

IP NAT RULE #2> NAT IP destination network (def:000.000.000.000) ? 

IP NAT RULE #2> NAT IP destination network mask (0-24,def:0) ? 

{000.000.000.000} 

IP NAT RULE #2> Pool size (0-2500,def:100) ? 

� Set IP source address min to the lowest IP address in the range of IP 

source addresses that must be translated, and IP source address 

max to the highest IP address in that range. 

� For DYNAMIC translation, set NAT IP source address min to the 

lowest IP address in the range of NAT IP source addresses that are 

used to translate local (or internal) IP addresses, and set NAT IP 

source address max to the highest IP address in that range. 

� For STATIC translation, set NAT IP source network and NAT IP source 

network mask to the source network that is used to translate local 

(or internal) IP addresses. 

� Set IP destination address min to the lowest IP address in the range 

of IP destination addresses that must be translated, and IP 

destination address max to the highest IP address in that range. 

For basic NAT the destination address is not translated; leave these 

parameters at their default value, 0.0.0.0. 

� For DYNAMIC translation, set NAT IP destination address min to the 

lowest IP address in the range of NAT IP destination addresses that 

are used to translate local (or internal) IP addresses, and set NAT IP 

destination address max to the highest IP address in that range. 

For basic NAT the destination address is not translated; leave these 

parameters at their default value, 0.0.0.0. 

� For STATIC translation, set NAT IP destination network and NAT IP 

destination network mask to the destination network that is used to 

translate local (or internal) IP addresses. 

For basic NAT the destination address is not translated; leave this 

parameter at its default value, 0.0.0.0. 



� Set the Pool size to the maximum number of entries that can be 

maintained in the translation table for this particular rule. 

Method of Operation 

IP NAT Port Parameters 

� If only one NAT IP source address is defined (NAT IP source address 

min = NAT IP source address max), the NetPerformer performs port 

translation (NAPT) and will overload the new IP address (only the 

source port is changed). 

� If the range of NAT IP source addresses is greater than one IP 

address, no port translation is performed. 

� If both NAT IP source address min and NAT IP source address max 

are set to 0.0.0.0, the NetPerformer will use the IP address that is 

negotiated during link establishment. This method is available for 

PPP ports only. 

� If both IP destination address min and IP destination address max 

are set to 0.0.0.0, no translation is performed on the destination 

port. 

To define the IP NAT port for NAPT translation: 

� Enter the menu sequence: SE ↵ IP ↵ NAT ↵ PORT. 

� Change the IP NAT port parameters from their default values, if 

desired. 



CHICAGO>SE 

SETUP 



Item (GLOBAL/STATIC/BOOTP/OSPF/TIMEP/SNMP/NAT/TELNET/FTP,def:NAT) ? NAT 

Item (RULE/PORT/TIMEOUT/SERVICE,def:RULE) ? PORT 

IP NAT PORT> NAPT min port (1-65534,def:60000) ? 

IP NAT PORT> NAPT max port (1-65534,def:61000) ? 

IP NAT PORT> NAPT pool size (0-2500,def:1000) ? 

� Set NAPT min port to the minimum and NAPT max port to the 

maximum TCP/UDP port number (or ICMP Query ID) used for NAPT 

translation. 

Note: NAPT translates the source address only. 

� Set the NAPT pool size to the maximum number of entries that can 

be maintained in the translation table. When ports are allocated, the 

NAPT pool size is used only if the range defined by the NAPT min 

port and NAPT max port parameters is greater than this value. 

Otherwise, the number of available ports determines the actual pool 

size. 



Note: If you are using a PPP port only, and the NAT IP source address 

parameters (min and max) for the NAT Rule are set to 0.0.0.0, then the 

PPP port address will be used for NAPT translation. 

IP NAT Timeout Parameters 

To define the IP NAT timeouts: 

� Enter the menu sequence: SE ↵ IP ↵ NAT ↵ TIMEOUT. 

� Change the IP NAT timeout parameters from their default values, if 

desired. 



CHICAGO>SE 

SETUP 




Item (RULE/PORT/TIMEOUT/SERVICE,def:PORT) ? TIMEOUT 

IP NAT TIMEOUT> Timeout (in minutes) (1-10000,def:1440) ? 

IP NAT TIMEOUT> TCP timeout (in minutes) (1-10000,def:1440) ? 

IP NAT TIMEOUT> TCP FIN/RST timeout (in minutes) (1-10000,def:1) ? 

IP NAT TIMEOUT> TCP SYN timeout (in minutes) (1-10000,def:2) ? 

IP NAT TIMEOUT> UDP timeout (in minutes) (1-10000,def:5) ? 

IP NAT TIMEOUT> DNS timeout (in minutes) (1-10000,def:2) ? 

IP NAT TIMEOUT> ICMP timeout (in minutes) (1-10000,def:2) ? 

� The Timeout (in minutes): determines how long a NAT entry can 

remain inactive before it is removed from the translation table. 

� The other timeouts govern NAPT functions: 

� TCP timeout (in minutes): how long a TCP NAT entry (NAPT) can 


� TCP FIN/RST timeout (in minutes): how long a TCP NAT entry can 

remain in the translation table after an RST or FIN bit is detected. 

� TCP SYN timeout (in minutes): how long a TCP NAT entry can 

remain in the translation table after a SYN bit is detected and no 

further data is received. 

� UDP timeout (in minutes): how long a UDP NAT entry can remain 

inactive before it is removed from the translation table. 

� DNS timeout (in minutes): how long a DNS NAT entry (TCP or 

UDP) can remain inactive before it is removed from the 

translation table. 

� ICMP timeout (in minutes): how long an ICMP NAT entry can 




IP NAT Service Parameters 

The IP NAT Service parameters are used in NAPT to enable specific 

static port translation. This allows for a direct association between an 

external connection on a specific port and a specific internal address. 

� A Service is used only when it is associated with a specific NAPT 

rule, and only on incoming external traffic. Twice NAT using NAPT is 

not supported. 

� When a frame arrives, if an entry is not found in the translation table 

the NetPerformer verifies whether the frame corresponds to an IP 

NAT Service. If it does, it performs the port translation defined by 

the Service. 

� This translation method allows access to, for example, an FTP or 

Internet server that is hidden behind a NAT (NAPT) translation 

process. 

To define an IP NAT Service: 

� Enter the menu sequence: SE ↵ IP ↵ NAT ↵ SERVICE. 

� Enter the number of the IP NAT service. 

� Change the IP NAT service parameters from their default values, if 

desired. 



CHICAGO>SE 

SETUP 




Item (RULE/PORT/TIMEOUT/SERVICE,def:TIMEOUT) ? SERVICE 

IP NAT service (1/2/3/4/5/6/7/8/9/10,def:1) ? 1 

IP NAT SERVICE #1> Associated rule number (0-10,def:0) ? 1 

IP NAT SERVICE #1> Internal service address (def:000.000.000.000) ? 

IP NAT SERVICE #1> Internal service port (1-65534,def:1) ? 

IP NAT SERVICE #1> External service port (1-65534,def:1) ? 

� Set the Associated rule number to the number of the NAPT rule you 

want to associate with this Service. Leave this parameter at its 

default value, 0, to disable any association with a rule. 

� Set the Internal service address and Internal service port to the IP 

address and port of the internal service that the External service 

port will reach. 

Method of Operation 

If NAT is configured in NAPT, each incoming frame is processed by the 

NAT services, as follows: 

� If no entry is found in the translation table, the NAT service parses 

the frame and tries to detect a matching situation. 



� If a match is found, the NAT service creates an entry in the 

translation table and performs the translation. 

� If there is no match, the frame is discarded. 

Defining Transparent User Port 

Characteristics 

A transparent user port is a serial port (including those on the Dual 

Serial Port interface card) or digital channel that is configured with one 

of the following protocols: 

� HDLC (page 180) 

� DDCMP (page 182); for a built-in serial port on the base unit only 

� T-ASYNC (page 182); for a built-in serial port on the base unit only 

� R-ASYNC (page 183); for a built-in serial port on the base unit only 

� BSC (page 184); for a built-in serial port on the base unit only 

� COP (page 184); for a built-in serial port on the base unit only 

� PASSTHRU (page 185); for a built-in serial port on the base unit only 

� PPP (page 185) 

� X25 (page 189); on serial port only (both built-in and Dual Serial 

interface card). 

To configure a built-in serial port on the base unit as a transparent user 

port: 



� Set the Protocol to the desired user protocol. 


desired. 

To configure a serial port on the Dual Serial interface card or a digital 

channel as a transparent user port: 



� On digital interface card only: enter CHANNEL at the Item prompt. 


� Set the Protocol to the desired user protocol. 


desired. 



HDLC Port Parameters 

Note: All screen captures in this section are taken from built-in serial 

ports on the base unit. Differences on the Dual Serial interface card are 

noted where applicable. Consult the section Data Channel Parameters 

on page 134 for examples taken from digital channels. 

Note: HDLC is available on a digital channel, a serial port on the Dual 

Serial interface card and a built-in serial port on the base unit. 

The parameters presented at the console for the HDLC protocol are 

identical for the standard NetPerformer and the NetPerformer SIP VoIP 

option: 

CHICAGO>SE 

SETUP 




PORT #1> Protocol (def:FR-USER) ? HDLC 










PORT #1> Remote unit (def:) ? BOSTON 




8, 16, 32, 56, 64, 112, 128, 256, 512, 768, 1024 or 1536. 

� The following parameters are not configurable on the Dual Serial 

card: Modem control signal, CRC encoding, Transmission start level 

and Frame delay. 

� For a digital channel the Port speed, Interface and Clocking mode 

parameters are not configured. The channel speed is a function of 

the Number of consecutive timeslots times the DS0 speed, which 

can be set to 64000 or 56000 bps. Refer to page 136 for further 

information on setting digital channel timeslots and total speed. 

� Fallback speed is not available on the Dual Serial interface card or a 

digital channel. 




the port. 









Note: Clocking mode is not presented on a digital channel. 

� The Modem control signal can be set to STATIC, DYNAMIC, 

STATPASS, DYNAPASS, STATFIX or DYNAFIX. 

Note: Set to STATPASS or DYNAPASS to reflect the state of the 

remote port. This is useful, for example, if voice calls are to be 

limited when high priority data is transmitted from this data port. 

� CRC encoding can be set to NRZ, NRZI, NRZ-CRC0 or NRZI-CRC0. 

� The Transmission start level defines the number of cells that are 

queued in the transmitter before starting transmission, and can be 

set to AUTO, MAX, 8, 16, 24, 32, 48, 96, 144, 192, 256, 512, 1024 or 

2048. 

� The Idle character can be set to MARK, FLAG or MARKD. 

Note: The MARKD setting is not available on the Dual Serial 

interface card. 

� The Frame delay can be set to 0.0, 0.5, 1.0, 1.5 or 2.0 msec. 




PRIORITY. 




� The default Remote port number is the local port number. 



DDCMP Port Parameters 

T-ASYNC Port Parameters 

Note: DDCMP is available only for a built-in serial port on the base unit. 

The parameters presented at the console for the DDCMP protocol are 


option: 

CHICAGO>SE 

SETUP 


CLASS/ 

PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:PORT) ? PORT 


PORT #2> Protocol (def:HDLC) ? DDCMP 










� These parameters are described in HDLC Port Parameters on 

page 180. 

When configured with the Transparent Asynchronous (T-ASYNC) 

protocol, the NetPerformer transmits asynchronous traffic over the link 

without interpretation. If an error occurs on the link while characters 

are being transmitted, these characters will be lost. 

Note: T-ASYNC is available only for a built-in serial port on the base 

unit. 

The parameters presented at the console for the T-ASYNC protocol are 


option: 

CHICAGO>SE 

SETUP 




PORT #1> Protocol (def:HDLC) ? T-ASYNC 



PORT #1> Clocking mode (def:ASYNC) ? 

PORT #1> Format (def:8-NONE) ? 





� The Clocking mode can be set to ASYNC, ISO-INT or ISO-EXT. 

� The Format can be set to 8-NONE, 7-NONE, 7-ODD, 7-EVEN, 7-SPACE, 

7-MARK, 7-IGNORE, 8-EVEN, 8-ODD or 8N-2STOP. 



R-ASYNC Port Parameters 

� The Modem control signal can be set to STATIC, STATPASS or 

STATFIX. 

� The other parameters are described in HDLC Port Parameters on 

page 180. 

When configured with the Reliable Asynchronous (R-ASYNC) protocol, 

the NetPerformer retransmits asynchronous user traffic to the remote 

port when errors occur on the link. 

Note: R-ASYNC is available only for a built-in serial port on the base 

unit. 

The parameters presented at the console for the R-ASYNC protocol are 


option: 

CHICAGO>SE 

SETUP 




PORT #2> Protocol (def:DDCMP) ? R-ASYNC 




PORT #2> Format (def:8-NONE) ? 

PORT #2> Reception flow control (def:NONE) ? 

PORT #2> Transmission flow control (def:NONE) ? 

PORT #2> Transmit holding time (sec) (0-1000,def:0) ? 




� Reception flow control and Transmission flow control can be set to 

NONE, XON_XOFF or HARDWARE. 

� If the Transmit holding time is left at its default value, 0, no delay is 

provided for flow control during transmission. 

� The other parameters are described in T-ASYNC Port Parameters on 

page 182, and HDLC Port Parameters on page 180. 



BSC Port Parameters 

COP Port Parameters 

Note: BSC is available only for a built-in serial port on the base unit. 

The parameters presented at the console for the BSC protocol are 


option: 

CHICAGO>SE 

SETUP 




PORT #1> Protocol (def:T-ASYNC) ? BSC 










� These parameters are described in HDLC Port Parameters on 

page 180. 

Note: COP is available only for a built-in serial port on the base unit. 

The parameters presented at the console for the COP protocol are 


option: 

CHICAGO>SE 

SETUP 




PORT #2> Protocol (def:R-ASYNC) ? COP 







PORT #2> Idle (def:MARK) ? 

PORT #2> Synchronization character (def:1616) ? 

PORT #2> Number of desynch. characters (1-100,def:3) ? 

PORT #2> Desynchronization character (def:FF) ? 




� The Idle character can be set to SPACE or MARK. 

� The Synchronization character can be any 4-digit hexadecimal 

value. 

� The Desynchronization character can be set to 00 or FF. 


page 180. 



PASSTHRU Port Parameters 

PPP Port Parameters 

When configured with the PASSTHRU protocol, the NetPerformer 

provides a connection between the local and remote locations, where 

all bits from the two PASSTHRU serial ports are transported to the other 

side without interpretation. Clocking is synchronized using a software 

phase-lock loop mechanism, which prevents underruns and overruns 

on the ports. 

Note: PASSTHRU is available only for a built-in serial port on the base 

unit. It should not be confused with the PASSTHROUGH protocol that 

can be defined on a digital channel. On digital interfaces, the 

PASSTHROUGH protocol provides a cross-connect/drop-insert switched 

connection between digital T1 or E1 timeslots on the same unit (see 

PASSTHROUGH Protocol on page 140). 

The parameters presented at the console for the serial port PASSTHRU 

protocol are identical for the standard NetPerformer and the 

NetPerformer SIP VoIP option: 

CHICAGO>SE 

SETUP 




PORT #1> Protocol (def:PVCR) ? PASSTHRU 





PORT #1> Transmission start level (3-12,def:3) ? 




� The Modem control signal can be set to STATIC, STATPASS or 

STATFIX. 

� The Transmission start level defines the number of 48-byte blocks 

that are queued in the transmitter before starting transmission. 


page 180. 

Note: PPP is available on a digital channel, a serial port on the Dual 

Serial interface card, a built-in serial port on the base unit, and the 

console port. 

Two types of PPP are available: synchronous and asynchronous: 

� A digital channel supports synchronous PPP only, and only for 

certain signaling modes on the LINK. Refer to Synchronous PPP 

Protocol on page 139. 

� A serial port on the Dual Serial interface card supports synchronous 

PPP only. 



� The console port can be configured with asynchronous PPP only. 

� A built-in serial port on the base unit supports either synchronous or 

asynchronous PPP. 

The parameters presented at the console for the PPP protocol are 


option. Here is an example of synchronous PPP configured on a builtin 

serial port: 

CHICAGO>SE 

SETUP 



Port number (ETH/CSL/1/2,def:2) ? 

PORT #2> Protocol (def:PPP) ? 

PORT #2> Port Clocking (def:ASYNC) ? SYNC 











{000.000.000.000} 

PORT #2> IP RIP (def:V1) ? V2 MULTICAST 


PORT #2> IP RIP Authentication (def:NONE) ? 

PORT #2> IP RIP Password (def:) ? 




PORT #2> Link control protocol retries, 255 = forever (0-255,def:255) ? 

PORT #2> Negotiate MRU (def:NO) ? YES 

PORT #2> Proposed MRU (0-3000,def:1500) ? 

PORT #2> Use MRU proposed by peer (def:NO) ? YES 

PORT #2> Maximum accepted MRU from peer (0-3000,def:1500) ? 







PORT #2> PPP dial index (def:NONE) ? 4 

PORT #2> Mode (def:DEDICATED) ? 

IPDIAL 4> Backup IP address (def:000.000.000.000) ? 

IPDIAL 4> Phone number (def:) ? 

IPDIAL 4> Incoming password type (def:NONE) ? 

IPDIAL 4> Incoming user name (def:) ? 

IPDIAL 4> Incoming password (def:) ? 

IPDIAL 4> Outgoing password type (def:NONE) ? 

IPDIAL 4> Outgoing user name (def:) ? 

IPDIAL 4> Outgoing password (def:) ? 

IPDIAL 4> Authentication retries, 255 = forever (0-255,def:3) ? 

IPDIAL 4> Fail delay (minutes) (0-255,def:0) ? 

IPDIAL 4> Maximum challenge interval (minutes) (1-255,def:60) ? 

IPDIAL 4> Authentication timeout (seconds) (1-255,def:10) ? 



Here is an example of asynchronous PPP configured on a built-in 

serial port: 

CHICAGO>SE 

SETUP 




PORT #2> Protocol (def:FR-NET) ? PPP 

PORT #2> Port Clocking (def:ASYNC) ? ASYNC 




PORT #2> Reception flow control (def:NONE) ? 

PORT #2> Transmission flow control (def:NONE) ? 

PORT #2> Transmit holding time (sec) (0-1000,def:0) ? 



{000.000.000.000} 






PORT #2> Link control protocol retries, 255 = forever (0-255,def:255) ? 

PORT #2> Negotiate MRU (def:NO) ? YES 

PORT #2> Proposed MRU (0-3000,def:1500) ? 

PORT #2> Use MRU proposed by peer (def:NO) ? YES 

PORT #2> Maximum accepted MRU from peer (0-3000,def:1500) ? 

PORT #2> Negotiate ACCM with peer (rcv) (def:YES) ? 

PORT #2> Requested ACCM characters (def:000A0000) ? 

PORT #2> Accept ACCM negotiation from peer (xmt) (def:YES) ? 

PORT #2> Acceptable ACCM characters (def:000A0000) ? 







PORT #2> PPP dial index (def:NONE) ? 

� Set Port Clocking to SYNC for synchronous PPP, or ASYNC for 

asynchronous PPP. 

Note: This parameter is not presented on a Dual Serial interface 

card or digital channel (which support only synchronous PPP), or on 

the console port (which supports only asynchronous PPP). 


8, 16, 32, 56, 64, 112, 128, 256, 512, 768, 1024 or 1536. 

� For synchronous PPP the Clocking mode can be set to EXTERNAL or 

INTERNAL. For asynchronous PPP it can be set to ASYNC, ISO-INT or 

ISO-EXT. 

� For a digital channel the Port speed, Interface and Clocking mode 

parameters are not configured. The channel speed is a function of 

the Number of consecutive timeslots times the DS0 speed, which 

can be set to 64000 or 56000 bps. Refer to page 136 for further 

information on setting digital channel timeslots and total speed. 

� Modem control signal, CRC encoding, Transmission start level, Idle 

and Frame delay are configured for synchronous PPP only. 





page 180. 

Note: These parameters are not configurable on the Dual Serial 

card. 

� Reception flow control, Transmission flow control and Transmit 

holding time are configured for asynchronous PPP only. These 

parameters are described in R-ASYNC Port Parameters on page 183. 

� The IP address, Subnet mask, IP RIP, IP RIP TX/RX, IP RIP 

Authentication, IP RIP Password and NAT enable parameters behave 

in the same way as for a WAN link. Refer to Dedicated WAN Link on 

page 90. 

� The remaining parameters determine how PPP address negotiation 

is carried out: 

� Silent can be set to SEND REQUEST or WAIT FOR REQUEST. 

� If you leave Link control protocol retries at its default value, 255, 

the unit will retry forever. 

� The Proposed MRU is requested only if Negotiate MRU is set to 

YES. 

� The Maximum accepted MRU from peer is requested only if Use 

MRU proposed by peer is set to YES. 

� For asynchronous PPP configuration, Requested ACCM characters 

is requested only if Negotiate ACCM with peer (rcv) is set to YES, 

and Acceptable ACCM characters is requested only if Accept 

ACCM negotiation from peer (xmt) is set to YES. 

� On an ISDN digital channel, the following additional parameters are 

listed after Remote IP-Address: 

... 







� The PPP dial index can be set to NONE or an integer from 1 to 16. If 

it is set to an integer, the IPDIAL parameters are presented. 

Note: For the console port and a built-in serial port on the base 

unit, the Mode must also be defined. Set it to DEDICATED for a 

dedicated connection, ANSWER for the answering side of a backup 

connection, or CALL-BKUP for the calling side of a backup 

connection. 

� On the console port and a built-in serial port on the base unit, define 

the parameters used for a backup connection: Backup IP address 

and Phone number. 



X25 Port Parameters 

� The Incoming password type and Outgoing password type can be 

set to NONE, PAP or CHAP (MD5). 

� On the console port, after the IPDIAL parameters you are prompted 

to confirm the switch to PPP mode with the message About to switch 

console to PPP mode. 

� Enter GO PPP to confirm the switch to PPP operations. 

� Enter BACK TO CONSOLE to continue using the console port for 

configuration and monitoring functions. 

Note: X25 is available on both a built-in serial port on the base unit and 

a serial port on the Dual Serial interface card. 

The parameters presented at the console for the X25 protocol are 


option: 

CHICAGO>SE 

SETUP 




PORT #1> Protocol (def:FR-USER) ? X25 




PORT #1> Clocking mode (def:EXTERNAL) ? 

PORT #1> X25 frame relay encapsulation (def:ANNEX-F) ? 

PORT #1> PVC number (1-300,def:1) ? 


8, 16, 32, 56, 64, 112, 128, 256, 512, 768, 1024 or 1536. 

� Fallback speed is not available on the Dual Serial interface card. 

� The X25 frame relay encapsulation method can be set to ANNEX-F or 

ANNEX-G. 

� Set the PVC number to the Multiplex or Transparent PVC that will 

transport the encapsulated X.25 traffic to the remote side. 

Defining SNA Device Characteristics 

An SNA application requires the following: 

� A connection to the SNA/SDLC network, including: 

� A primary SDLC port that connects to one or more PUs (P-SDLC 

port, page 190) 

� A secondary SDLC port that connects to the IBM front-end 

processor or mainframe (S-SDLC port, page 190). 



� One or more PUs (page 192), each of which interfaces with two 

sides using: 

� SNA/SDLC protocol (SDLC side, page 193) 

� LAN LLC protocol (LLC side, page 194) 

� RFC-1434 Data Link Switch (DLSw) protocol (DLSW side, 

page 195) 

� NetPerformer PowerCell (PVCR) protocol (LINKS side, page 196) 

� BAN routing (BAN side, page 196) 

� BNN routing (BNN side, page 197). 

SNA/SDLC Port Configuration 

An SDLC connection to the SNA network can be set up on a built-in 

serial port on the base unit or a serial port on the Dual Serial interface 

card: 

� To configure a built-in serial port on the base unit as an SDLC 

connection: 



� Set the Protocol to P-SDLC for a primary SDLC port, or to S-SDLC 

for a secondary SDLC port. 


desired. 

� To configure a serial port on the Dual Serial interface card as an 

SDLC connection: 




� Set the Protocol to P-SDLC for a primary SDLC port, or to S-SDLC 

for a secondary SDLC port. 


desired. 



The parameters presented at the console for SDLC port configuration 

are identical for the standard NetPerformer and the NetPerformer SIP 

VoIP option. Here is a capture of P-SDLC port configuration on a built-in 

serial port: 

CHICAGO>SE 

SETUP 



Port number (ETH/CSL/1/2,def:CSL) ? 1 

PORT #1> Protocol (def:PVCR) ? P-SDLC 









PORT #1> SDLC duplex mode (def:HALF) ? 

PORT #1> Group poll (def:NO) ? 

PORT #1> Group address (def:AE) ? 

PORT #1> Poll delay (msec) (0-1000,def:10) ? 


8, 16, 32, 56, 64, 112, 128, 256, 512, 768, 1024 or 1536. 

� The following parameters are not configurable on the Dual Serial 

card: Fallback speed, CRC encoding, Modem control signal and 

Transmission start level. 




the port. 







� CRC encoding can be set to NRZ or NRZI. 


� The Transmission start level defines the number of cells that are 

queued in the transmitter before starting transmission, and can be 

set to AUTO, MAX, 8, 16, 24, 32, 48, 96, 144, 192, 256, 512, 1024 or 

2048. 

� The Idle character can be set to MARK, FLAG or MARKD. 

Note: The MARKD setting is not available on the Dual Serial 

interface card. 

� The SDLC duplex mode can be set to HALF or FULL. 

� The Group address can be defined with any hexadecimal value from 

00 to FF. 



PU Configuration 

PU configuration consists of a few parameters common to all PU types, 

followed by parameters that define the two sides of the connection. 

Common Parameters 

To configure a PU: 

� Enter the menu sequence: SE ↵ PU. 

� Select the PU number. 

� Select the Operating mode. This determines the two sides of the PU. 

� Change the other PU parameters from their default values, if 

desired. 



CHICAGO>SE 

SETUP 


CLASS/ 

PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:GLOBAL) ? PU 

PU number (1-64,def:1) ? 1 

PU #1> Operating mode (def:OFF) ? SDLC-LLC 

PU #1> Controller active (def:NO) ? YES 

PU #1> Delay before connection (1-1000,def:60) ? 

PU #1> SDLC port (def:1) ? 

... 

� The Operating mode can be set to OFF, SDLC-LLC, SDLC-SDLC, 

SDLC-DLSW, SDLC-LINKS, LLC-DLSW, LLC-LINKS, DLSW-LINKS, 

SDLC-BAN, SDLC-BNN, LLC-BAN, LLC-BNN, DLSW-BAN, DLSW-BNN, 

BAN-LINKS or BNN-LINKS. 

Caution: The NetPerformer DLSw driver follows the RFC-1434 

specification, and does not handle some of the modifications to 

this specification such as RFC-1795. Some recent DLSw 

protocols for handling SNA and NetBIOS traffic over a TCP/IP 

internetwork are not supported. A PU configured with a 

DLSW side will not work if your application uses the 

latest DLSw encapsulation techniques. 

� Set Controller active to YES to activate the PU. 

Caution: If the attached SNA/SDLC device is up and running 

we recommend that you leave Controller active at its default 

value, NO, until all other parameters are defined. Then repeat 

the menu sequence: SE ↵ PU, press until you reach the 

Controller active parameter, and set it to YES. 



Parameters for SDLC Side 

When one side of the PU connection is SDLC, the following parameters 

are presented at the console: 

... 

PU #1> SDLC port (def:1) ? 

PU #1> SDLC address (def:01) ? 

PU #1> SDLC retransmission timeout (msec) (100-30000,def:3000) ? 

PU #1> SDLC number of retransmission retries (1-1000,def:10) ? 

PU #1> SDLC transmission window size (1-7,def:7) ? 

PU #1> SDLC frame size (def:512) ? 

� These parameters appear when the PU Operating mode is set to 

SDLC-LLC, SDLC-DLSW, SDLC-LINKS, SDLC-BAN or SDLC-BNN. 

� Set the SDLC port to a serial port configured with the P-SDLC or 

S-SDLC protocol. 

� The SDLC address can be defined with any hexadecimal value from 

00 to FF. 

� The SDLC frame size can be set to 128, 256, 512, 1024, 2048, 4096 or 

8192. 

When both sides of the PU connection are set to SDLC (SDLC-SDLC 

Operating mode), primary and secondary ports are distinguished: 

CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:PU) ? 


PU #2> Operating mode (def:OFF) ? SDLC-SDLC 

PU #2> Controller active (def:NO) ? YES 

PU #2> Delay before connection (1-1000,def:60) ? 

PU #2> SDLC primary port (def:1) ? 

PU #2> SDLC primary address (def:02) ? 

PU #2> SDLC secondary port (def:1) ? 2 

PU #2> SDLC secondary address (def:02) ? 04 

PU #2> SDLC retransmission timeout (msec) (100-30000,def:3000) ? 

PU #2> SDLC number of retransmission retries (1-1000,def:10) ? 

PU #2> SDLC transmission window size (1-7,def:7) ? 

PU #2> XID support (def:YES) ? 

� Set the SDLC primary port and SDLC secondary port to serial ports 

configured with the respective SDLC protocols (P-SDLC, S-SDLC). 

� The SDLC primary address and SDLC secondary address can be 

defined with any hexadecimal value from 00 to FF. The default value 

of both parameters is equal to the PU number. 

Note: To support PU Type 4, where 2 FEPs are connected via an 

SDLC line, both of these addresses must be set to FF. 

� XID support can be set to either YES (on) or NO (off). 



Parameters for LLC Side 

When one side of the PU connection is LLC, the following parameters 


... 

PU #1> LLC Role (def:SEC) ? 

PU #1> LLC destination address (def:000000000000) ? 

PU #1> LLC source SAP (def:04) ? 

PU #1> LLC destination SAP (def:04) ? 

PU #1> LLC retransmission timeout (msec) (1000-30000,def:3000) ? 

PU #1> LLC maximum successive retries (1-1000,def:10) ? 

PU #1> LLC transmission window size (1-31,def:7) ? 

PU #1> LLC dynamic window (1-1000,def:10) ? 

PU #1> LLC frame size (def:512) ? 

PU #1> XID support (def:AUTO) ? MANUAL 

PU #1> XID identification number (def:00000000) ? 

PU #1> XID format (def:0) ? 

PU #1> XID PU type (def:1) ? 


SDLC-LLC, LLC-DLSW, LLC-LINKS, LLC-BAN or LLC-BNN. 

� The LLC Role can be set to PRI (primary) or SEC (secondary). 

Note: This parameter is not requested for the SDLC-LLC mode. 

� Set the LLC destination address to the MAC address of the attached 

SNA equipment. 

� The LLC source SAP and LLC destination SAP can be set to any twodigit 

hexadecimal multiple of 4, from 04 to DC. 

� The LLC frame size can be set to 128, 256, 512 or 1024. 

Note: If required, the NetPerformer can split frames to match 

different frame sizes during conversion. 

� XID support can be set to MANUAL or AUTO. 

� If set to AUTO, the other XID parameters are not presented. 

� Use the MANUAL setting only if the PU does not generate its own 

XID (typically for a PU2.0 on a leased, non-switched line). 

� Set the XID identification number to an 8-digit number composed of 

the PU ID block and ID number. 

� The XID format can be set to 0 or 1. 

� The XID PU type can be set to 1 or 2. 

Note: If the PU is type 2.1, use the AUTO setting of the XID support 

parameter. 



Parameters for DLSW Side 

When one side of the PU connection is DLSW, the following parameters 


... 

PU #3> DLS Role (def:SEC) ? 

PU #3> DLS destination address (def:000000000000) ? 

PU #3> DLS source SAP (def:04) ? 

PU #3> DLS destination SAP (def:04) ? 

PU #3> DLS source IP address (def:000.000.000.000) ? 

PU #3> DLS destination IP address (def:000.000.000.000) ? 

PU #3> DLS frame size (def:512) ? 






SDLC-DLSW, LLC-DLSW, DLSW-LINKS, DLSW-BAN or DLSW-BNN. 

Caution: The NetPerformer DLSw driver follows the RFC-1434 

specification, and does not handle some of the modifications to 

this specification such as RFC-1795. Some recent DLSw 

protocols for handling SNA and NetBIOS traffic over a TCP/IP 

internetwork are not supported. A PU configured with a 

DLSW side will not work if your application uses the 

latest DLSw encapsulation techniques. 

� The DLS Role can be set to PRI (primary) or SEC (secondary). 

Note: This parameter is not requested for the SDLC-DLSW or 

LLC-DLSW modes. 

� Set the DLS destination address to the MAC address of the attached 

equipment. 

� The DLS source SAP and DLS destination SAP can be set to any twodigit 

hexadecimal multiple of 4, from 04 to DC. 

� The DLS source IP address identifies the port used to reach the 

remote DLSw connection. If left at its default value 

(000.000.000.000), this address is not defined, which means the 

DLSw PU cannot communicate over IP and will not be operational. 

� The DLS destination IP address identifies the remote PU. If left at its 

default value (000.000.000.000), this address is not defined. 

� The DLS frame size can be set to 128, 256, 512, 1024, 2048, 4096 or 

8192. 

� The XID parameters behave in the same way as for the Parameters 

for LLC Side on page 194. 



Parameters for Links Side 

When one side of the PU connection is LINKS, the following parameters 


... 

PU #4> Remote unit (def:) ? BOSTON 

PU #4> Class (def:2) ? 

PU #4> Remote PU number (1-64,def:4) ? 

PU #4> XID support (def:YES) ? 


SDLC-LINKS, LLC-LINKS, DLSW-LINKS, BAN-LINKS or BNN-LINKS. 




PRIORITY. 




� The default Remote PU number is the local PU number. 

� XID support can be set to either YES (on) or NO (off). 

Parameters for BAN Side 

When one side of the PU connection is BAN, the following parameters 


... 

PU #8> BAN/BNN Role (def:SEC) ? 

PU #8> BAN destination address (def:000000000000) ? 

PU #8> BAN/BNN source SAP (def:04) ? 

PU #8> BAN/BNN destination SAP (def:04) ? 

PU #8> BAN/BNN retransmission timeout (msec) (1000-30000,def:3000) ? 

PU #8> BAN/BNN maximum successive retries (1-1000,def:10) ? 

PU #8> BAN/BNN transmission window size (1-31,def:7) ? 

PU #8> BAN/BNN dynamic window (1-1000,def:10) ? 

PU #8> BAN/BNN frame size (def:512) ? 

PU #8> BAN routing (def:SOURCE) ? 






SDLC-BAN, LLC-BAN, DLSW-BAN or BAN-LINKS. 

� The BAN/BNN Role can be set to PRI (primary) or SEC (secondary). 

Note: This parameter is not requested for the SDLC-BAN, LLC-BAN 

or DLSW-BAN modes. 

� Set the BAN destination address to the MAC address of the attached 

equipment. 



� The BAN/BNN source SAP and BAN/BNN destination SAP can be set 

to any two-digit hexadecimal multiple of 4, from 04 to DC. 

� The BAN/BNN frame size can be set to 128, 256, 512, 1024, 2048, 

4096 or 8192. 

� BAN routing can be set to TRANSPARENT, SOURCE or SOURCE-A. 

� The XID parameters behave in the same way as for the Parameters 

for LLC Side on page 194. 

Parameters for BNN Side 

When one side of the PU connection is BNN, the following parameters 


... 

PU #9> BAN/BNN Role (def:SEC) ? 

PU #9> BNN PVC number (1-300,def:1) ? 

PU #9> BNN FID type (def:FID2) ? ? 

PU #9> BAN/BNN source SAP (def:04) ? 

PU #9> BAN/BNN destination SAP (def:04) ? 

PU #9> BAN/BNN retransmission timeout (msec) (1000-30000,def:3000) ? 

PU #9> BAN/BNN maximum successive retries (1-1000,def:10) ? 

PU #9> BAN/BNN transmission window size (1-31,def:7) ? 

PU #9> BAN/BNN dynamic window (1-1000,def:10) ? 

PU #9> BAN/BNN frame size (def:512) ? 






SDLC-BNN, LLC-BNN, DLSW-BNN or BNN-LINKS. 

� The BAN/BNN Role is not requested for the SDLC-BNN, LLC-BNN or 

DLSW-BNN modes. 

� Set the BNN PVC number to the PVC that will be used for this 

connection. 

� The BNN FID type can be set to FID2, FID4 or APPN. 

� The BAN/BNN parameters behave in the same way as for the 

Parameters for BAN Side on page 196, and the XID parameters 

behave in the same way as for the Parameters for LLC Side on 

page 194. 

Traffic Priority and Scheduling 


� Assign traffic to priority classes (SE/CLASS, page 198) 

� Set up a schedule for automatic WAN link activation (SE/SCHEDULE, 

page 199) 

� Define any traffic filters that may be required for your application 

(SE/FILTER, page 200). 



Class Parameters 

To configure a priority class on the NetPerformer unit: 

� Enter the menu sequence: SE ↵ CLASS. 

� Select the CLASS number. 

� Change the other Class parameters from their default values, if 

desired. 



CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:GLOBAL) ? CLASS 

CLASS number (DEFAULT/1/2/3/4/5/6/7/8,def:1) ? 1 

CLASS #1> Weight (1-16,def:1) ? 

CLASS #1> Preferred route (def:) ? BOSTON 

� Set the Weight to an integer value from 1 to 16. The higher the 

number, the higher the priority. 

� The Preferred route should be defined with the Unit ID of another 


Default Class 

A default priority class can be defined on the unit. This class is used 

for the LAN traffic (IP, IPX or Bridge). 

Note: To re-direct LAN traffic into other classes of priority, you must 

define a filter. Refer to Filter Parameters on page 200). 

To set the default class: 

� Enter the menu sequence: SE ↵ CLASS. 

� Enter DEFAULT at the CLASS number prompt. 

� Set Default class to the number of the class you would like to use for 

LAN traffic (class 0 to 8). 

Note: Class 0 is a very low priority class that should be used only for 

administrative operations such as exchanging the unit routing table 

or sending the Relay command to a remote unit. Unless your LAN 

traffic is exclusively very low priority management traffic with low 

bandwidth requirements, we recommend that you do not move 

LAN data to Class 0 with the Default class parameter. 



Schedule Parameters 

Here is a capture of default class configuration: 

CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:FILTER) ? CLASS 

CLASS number (DEFAULT/1/2/3/4/5/6/7/8,def:1) ? DEFAULT 

CLASS> Default class (0-8,def:1) ? 1 

To define a schedule for WAN link activation on the NetPerformer unit: 

� Enter the menu sequence: SE ↵ SCHEDULE. 

� Select the PERIOD number. 

� Change the other Schedule parameters from their default values, if 

desired. 



CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:GLOBAL) ? SCHEDULE 

PERIOD number (1-10,def:1) ? 1 

PERIOD #1> PORT 1 Operating mode (def:INACTIVE) ? DEDICATED 

PERIOD #1> PORT 2 Operating mode (def:INACTIVE) ? CALL-BKUP 

PERIOD #1> Day (def:ALL) ? MONDAY 

PERIOD #1> Begin time (def:00:00) ? 

PERIOD #1> End time (def:23:59) ? 

PERIOD #1> Enable (def:NO) ? YES 

� The PORT 1 Operating mode and PORT 2 Operating mode can be set 

to DEDICATED, ANSWER, CALL-BKUP, CALL-BOD, INACTIVE or 

WAIT USER. 

For information on these operating modes, refer to Configuring a 

WAN Link on page 90. 

� The Day, Begin time and End time parameters define the time period 

during which the operating modes will apply. 

� The Day can be set to ALL, SUNDAY, MONDAY, TUESDAY, 

WEDNESDAY, THURSDAY, FRIDAY, SATURDAY, WORKDAY or 

WEEKEND. 

� The Begin time and End time are defined with 24-hour clock 

notation. 

� Set Enable to YES to activate this period. 

Note: If you activate more than one period, make sure that their 

times do not overlap. 



Filter Parameters 

To define a traffic filter on the NetPerformer unit: 

� Enter the menu sequence: SE ↵ FILTER. 

� Select the FILTER number. 

� Set Active to YES to activate this filter. 

� Enter the filter definition at the Definition prompt. 



CHICAGO>SE 

SETUP 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER,def:CALLER ID) ? FILTER 

FILTER number (1-32,def:1) ? 

FILTER #1> Active (def:NO) ? YES 

FILTER #1> Definition (def:) ? SNA>X 

� The Definition can contain up to 64 alphanumeric characters, and 

can be configured to: 

� Assign a particular data type to a particular priority class. For 

example, TELNET>3. 

� Assign a specific destination address, port or frame value to a 

particular priority class. For example, 

IP(200.1.1.0,255.255.255.0)>3. 

� Discard a particular data type or frame value. For example, 

FTP>X. 

Note: A list of filter types is provided in the NetPerformer System 

Reference Manual (Administration Guide). 

Filtering VLAN Priority 

To filter VLAN traffic for Quality of Service (QoS) requirements, you can 

assign a priority to a particular NetPerformer Class of Service: HIGH or 

1 to 8, with the MACQOS filter. 

� This filter maps the 802.1P priority level and queues that traffic onto 

a NetPerformer Class of Service. 

� NetPerformer Classes of Service are used to prioritize VLAN traffic 

when bridging via PowerCell (PVCR). 

Here is an example of the MACQOS filter: 

CHICAGO>SE 

SETUP 



FILTER number (1-32,def:1) ? 2 


FILTER #1> Definition (def:) ? MACQOS(111,111)>HIGH 



� The Definition sets up a range between 000 and 111 which represents 

the three-bit User Priority field in the VLAN Tag Header. The 

Definition must have the following syntax: 

MACQOS(min_value_of_range,max_value_of_range)>class_of_serv 

ice 

where: min_value_of_range is a 3-bit binary value representing the 

lowest VLAN priority value 

max_value_of_range is a 3-bit binary value representing the 

highest VLAN priority value 

class_of_service represents the NetPerformer class of 

service, and ranges from 1 to 8 plus the HIGH priority level 

usually used for voice. 

Implementing DiffServ 

DiffServ allows specific protocols with low-latency or high-bandwidth 

demands to be routed more efficiently than other protocols. In 

particular, DiffServ allows prioritization of IP frames received from user 

devices such as IP phones. The most common DiffServ application is 

the prioritization of voice packets over data packets. 

On the NetPerformer, DiffServ is implemented using the IPQOS filter. 

� This filter maps the 6-bit differentiated service (DS) field in the IP 

header to a NetPerformer Class of Service. 

� This mapping provides a total of 32 filter definitions, providing a 

good level of flexibility in various applications. 

� The DS field can be set according to the priority given to a specific 

kind of traffic or protocol. This allows the network to process those 

packets more efficiently, and accommodate any real-time high 

bandwidth requirements this traffic may have. 

Here is an example of the IPQOS filter: 

CHICAGO>SE 

SETUP 



FILTER number (1-32,def:1) ? 


FILTER #1> Definition (def:) ? IPQOS(000000,010111)>3 

� The Definition must have the following syntax: 

IPQOS(min_value_of_range,max_value_of_range)>class_of_service 

where: min_value_of_range is a 6-bit binary value representing the 

lowest DS field value 

max_value_of_range is a 6-bit binary value representing the 

highest DS field value 



class_of_service represents the NetPerformer class of 

service, and ranges from 1 to 8 plus the HIGH priority level 

usually used for voice. 

Note: If two IPQOS filters are defined with an overlapping range of 

values, the overlapped portion is assigned to the filter with the 

lowest FILTER number (1 to 32). 


Monitoring and Statistics 

This chapter presents some of the monitoring functions and statistics 

displays that are available from the NetPerformer console. They are 

useful tools both during the configuration process and for 

troubleshooting purposes. 

Note: Unless noted otherwise, these commands can be executed by 

users with FULL or MONITOR console access. 

NetPerformer monitoring and statistics functions include the following 

general categories: 

� System statistics, including the counters and number of errors for 

each network connection (page 203) 

� System status, including the status of each connection, the alarm 

log, configuration journal and exit record (page 206) 

� Real-time displays of connection activity (page 209) 

� Summaries of current hardware and software settings (page 214) 

� Commands for manipulating system files and settings (page 222) 

� Capturing and viewing the traffic that passes across a particular 

network connection (page 227) 

� Locating network components through routing and connection 

tables, and ensuring their accessibility by sending loopbacks, PINGs 

and tones across the network (page 234). 

Note: Most of the commands presented in this chapter are available on 

both the standard NetPerformer and the NetPerformer SIP VoIP option, 

and provide the same displays on both products. Exceptions to this 

general rule, where one product differs from the other, are noted with 

the description of the command. 

Viewing System Statistics 

Display Counters (DC) 

The NetPerformer is able to display system statistics, including the 

counters and number of errors for each network connection. 

The Display Counters command (DC) shows all counters stored in 

memory, including the mean or peak values of transmitter and receiver 

rates on all ports. 


4

Monitoring and Statistics Doc. No. 620-0120-001 

Display Errors (DE) 

To display the counters for a particular network connection: 

� Enter DC at the NetPerformer console command prompt. 

� Enter the name of the connection type you want to inspect. 


CHICAGO>DC 

DISPLAY COUNTERS 

Item (CONFIG/PORT/PVC/IP/BOOTP/TIMEP/SLOT/Q922/Q933/NAT/SVC/QOS, 

def:CONFIG) ? 

CONFIG> Number of skipped headers...............0 

CONFIG> Number of skipped parameters............0 

CONFIG> Configuration file size.................1 K 

CONFIG> Total memory used by the cfg profile....157 K 

CONFIG> Number of journal entry fail............0 

Here is an example from the NetPerformer SIP VoIP option, which 

offers SIP counters instead of SVC counters: 

BOSTON>DC 

DISPLAY COUNTERS 

Item (CONFIG/PORT/PVC/IP/BOOTP/TIMEP/SLOT/Q922/Q933/NAT/SIP/QOS, 

def:CONFIG) ? BOOTP 

Number of BOOTREQUEST frames received...........0 

Number of BOOTREQUEST frames sent...............0 

Number of BOOTREPLY frames received.............0 

Number of BOOTREPLY frames sent.................0 

� To interpret the results of the DC command, refer to the 

NetPerformer System Reference Manual (Administration Guide). 

� Use the Reset Counters (RC) command to return all statistics 

counters to zero; enter RC at the console command prompt. 

Note: The RC command is available to users with FULL console 

access only. To change access privileges for a particular user, refer 

to Defining User Access Profiles on page 70. 

To display the number of errors that have occurred on a particular 

network connection: 

� Enter DE. 

� Enter the name of the connection type you want to inspect. 

Here is an example from the NetPerformer SIP VoIP console: 

BOSTON>DE 

DISPLAY ERRORS 

Item (PORT/PVC/PU/GROUP/CHANNEL/DICT/BOOTP/TIMEP/SLOT/Q922/NAT, 

def:PORT) ? PVC 

PVC 1> Number of errors.........................0 

PVC 1> Number of restarts.......................0 

PVC 1> Number of invalid frames discarded.......0 

PVC 1> Number of frames discarded (overrun).....0 

PVC 1> Number of invalid octets discarded.......0 

PVC 1> Number of octets discarded (overrun).....0 



Here is an example from the standard NetPerformer, which offers a 

display of SVC errors in addition to the rest: 

CHICAGO>DE 

DISPLAY ERRORS 

Item (PORT/PVC/PU/GROUP/CHANNEL/DICT/BOOTP/TIMEP/SLOT/SVC/Q922/NAT, 

def:PORT) ? PU 

PU 4> Number of compressor error................0 

PU 4> Number of channel overflow error..........0 

PU 4> Number of channel abort error.............0 

PU 4> Number of channel sequence error..........0 

� To interpret the results of the DE command and determine whether 

corrective action is required, refer to the NetPerformer System 


� Use the Reset Counters (RC) command to return all statistics 

counters to zero; enter RC at the console command prompt. 

Note: The RC command is available to users with FULL console 



Display Bridge Statistics (DB) 

The Display Bridge (DB) command displays the current status of the 

bridge and all ports participating in the bridge topology. To access the 

bridge statistics: 

� Enter DB. 

Here is an example of the bridge counters and other information 

provided with this command: 

BOSTON>DB 

DISPLAY BRIDGE STATISTICS 

BRIDGE> Address discard.........................0 

BRIDGE> Transparent frame discard...............0 

BRIDGE> Designated root.........................7FFF00200AB00AA1 

BRIDGE> Root cost...............................0 

BRIDGE> Root port...............................NONE 

BRIDGE> Frame filtered..........................0 

BRIDGE> Frame timeout discard...................0 

Note: To view all active bridge addresses, use the Display Bridge 

Addresses (DBA) command, described on page 207. 



Checking System Status 

Display States (DS) 

Display Active PUs (AP) 

Several console commands are available to help you ascertain the 

current status of the NetPerformer and its connections. 

To display the current status of a particular network connection or 

component: 

1. Enter DS. 

2. Enter the name of the connection type you want to inspect. 

Here is an example from the standard NetPerformer: 

CHICAGO>DS 


Item (GLOBAL/PORT/PU/PVC/SLOT/SVC/VLAN,def:GLOBAL) ? 

GLOBAL> DIAG LED................................OFF 

� Enter the menu sequence: DS ↵ GLOBAL to view the current status 

of the Error LED from the console. Use the Clear ERR/DIAG LED (CE) 

command to extinguish this LED; enter CE. 

Note: The CE command is available to users with FULL console 



Here is an example from the NetPerformer SIP VoIP option, which 

offers SIP states instead of SVC states: 

BOSTON>DS 


Item (GLOBAL/PORT/PU/PVC/SIP/SLOT/VLAN,def:GLOBAL) ? SIP 

SIP> Version....................................SIP/2.0 

SIP> Current operational state..................DOWN (No LAN IP address) 

SIP> Registration status........................Unregistered 

To interpret the results of the DS command, refer to the NetPerformer 

System Reference Manual (Administration Guide). 

The Active PU (AP) command identifies which PUs are currently active 

in SNA/SDLC polling mode. 

To view a list of currently active PUs: 

� Enter AP at the console command prompt. 




BOSTON>AP 

ACTIVE PU 

Active PU> 1,2,3,4,5,6,7 

Display Bridge Addresses (DBA) 

The Display Bridge Addresses (DBA) command lists all active bridge 

addresses and displays all MAC addresses that have been learned by 

the bridge in transparent mode. 

To view the list of bridge addresses: 

� Enter DBA at the console command prompt. 


BOSTON>DBA 

DISPLAY BRIDGE ADDRESSES 

ADDRESS PORT TIME(sec) 

002083000435 LAN 1180 

0020830008B0 1 276 

Display Software Alarms (DA) 

NetPerformer alarms indicate communication activation or deactivation, 

unit failure or restart, and information such as notification of power-on, 

user actions and firmware download. To display the most recent 

alarms: 

� Enter DA at the console command prompt. 


CHICAGO>DA 

DISPLAY ALARMS 





Time> MON 2004/02/16 13:44:47 

Alarm> SOFT START (PWR) MON 2004/02/16 13:32:10 

Alarm> SOFT START (RST) MON 2004/02/16 13:28:58 

Alarm> FIRMWARE STORED MON 2004/02/16 13:28:00 

Alarm> SIGNALING ENGINE STORED MON 2004/02/16 13:27:35 

Alarm> FILE QU207101.BIN STORED MON 2004/02/16 13:27:19 

... 

� For each alarm, the display includes the type of alarm and the date 

and time it occurred. 

� To interpret these alarms, refer to the NetPerformer System 




� Use the Clear Alarms (CA) command to empty the alarm buffer; 

enter CA at the console command prompt. 

Note: The CA command is available to users with FULL console 



Display Journal (DJOURNAL) 

The Display Journal Log (DJOURNAL) command displays the contents of 

the configuration log file, JOURNAL.TXT. This can be useful for viewing 

a historical journal of all events that have affected the unit 

configuration, and for reporting a configuration problem to 

NetPerformer Technical Support. 

Note: The DJOURNAL command is available to users with FULL console 

access only. 

To view the journal: 

� Enter DJOURNAL at the console command prompt. 

� Set Display full log to YES to view the date, time, username and 

connection type for each journal entry. If Display full log is set to 

NO, only the date and time are displayed with each entry. 

� Enter YES at the prompt Wait for after each screen if you 

would like to view the file one screen at a time. 


CHICAGO>DJOURNAL 

DISPLAY JOURNAL LOG 

Display full log (NO/YES,def:NO) ? YES 

Wait for after each screen (NO/YES,def:YES) ? YES 

Time> MON 2002/02/18 14:11:52 

2002/02/18 13:45:27 ADMIN LOCAL 

CONFIGURATION UPDATED 

2002/02/18 13:32:21 BOOT_SEQUENCE LOCAL 

TEXT CONFIGURATION FILE READ 


UNIT RESTARTED 


CONFIGURATION UPDATED 


NO USERS AND LICENSES PROFILE CAN BE RETRIEVED 


UNIT RESTARTED 

Note: In this display, all strings are truncated to fit the screen. The full 

strings are available in the file JOURNAL.TXT, which can be retrieved 

from the unit using the FTP get command. 



Display Exit Record (ER) 

The Display Exit Record (ER) command allows you to view the exit 

record produced when a fatal alarm occurs. It also includes information 

on the product hardware and firmware versions installed. This can be 

useful for reporting an operational problem to NetPerformer Technical 

Support. 

To view the exit record: 

� Enter ER at the console command prompt. 


BOSTON>ER 

DISPLAY EXIT RECORD 

Wait for after each screen (NO/YES,def:YES) ? YES 


Code base X.X.X Verso Technologies, Inc. (c) 2004 


SE interface hardware info (Slot 2): 

Type: Dual Serial 

Board ID: 15 (PCB Rev A) 

FPGA software version: 6 


Portable SIP Stack 1.0.9 

DBG vX.X.X Verso Technologies, Inc. (c) 2004 

BOOT vX.X.X Verso Technologies, Inc. (c) 2004 

Hardware Info> Main Board Id: 3 

Released Version. 


Time> THU 2004/02/19 14:29:21 

Alarm> BACKUP CALL THU 2004/02/19 14:19:25 

Alarm> ALARMS CLEARED THU 2004/02/19 14:13:55 

005D3538: FF737F73 DAFBF6BF-AFEFFF7E FFFFE5FF .s.s.......~.... 

005D3548: DFFFF9F7 9FDBE7FF-F9BF7BFF FEF4FCFF ..........{..... 

 

005D3558: DAF9F5FD 8DE7D6FF-EDFDFFFF FBFCEDDE ................ 

005D3568: FBFFEDFF 7DE7FDFD-FEFFE7FF FFEFED1F ....}........... 

005D3578: FFF7FFFF BFFFFECF-BBBFFEFF E7FD7FEF ................ 

005D3588: DFFCFDFF BFFBFF7F-DF7E5EEE E9F79DFE .........~^..... 

005D3598: FFFFBFF7 DEFFFEFF-9FAF6FFD F7F9FFFF ..........o..... 

005D35A8: 9DFFF55E FCFFEB77-EDF9FFFF FBDF5F7C ...^...w......_| 

005D35B8: 7FFF3BFD EE47FFBF-FFEFEFFF FBFBFF3C ..;..G.........< 

005D35C8: DF77797F D7EFFFDF-FFDFFFFF DFFFF7EF .wy............. 

005D35D8: FEC3FFFE FDEFBBBF-EFBDF8FF EFBBBD65 ...............e 

005D35E8: FCEFEFFF FFFEF77F-BDFFF7FB D7FF2ECA ................ 

005D35F8: 9FDE6FFD FFF5FDFD-FFFFFD6D FFFDF7BB ..o........m.... 

... 

Running Real-time Displays 

The NetPerformer console provides several real-time statistical displays 

for in-depth study of current system status. 

Display Channel States (DCS) 

The Display Channel States command (DCS) shows the status of all 

digital channels in real time. To execute this command: 

� Enter DCS at the console command prompt. 



Here is an example from a standard NetPerformer console: 

CHICAGO>DCS 

DISPLAY CHANNEL STATES 

----------------------------------- SLOT 3 : FXS ------------------------------ 

| # Status Remote Unit Name # Rate | # Status Remote Unit Name # Rate | 

|301 ONLINE 9350 1 8.0Kx1| | 

------------------------------------------------------------------------------- 

Use LEFT and RIGHT arrow keys to change slot. Press any other key to exit. 


BOSTON>DCS 

DISPLAY CHANNEL STATES 

----------------------------------- SLOT 2 : FXS ------------------------------ 

# Status DNIS Rate | # Status DNIS Rate 

01 CONNECT 14506192262 G729A 2ppf | 

------------------------------------------------------------------------------- 

Use LEFT and RIGHT arrow keys to change slot. Press any other key to exit. 

� Select a slot using the left and right arrow keys. The slot number 

and type of interface card installed in that slot are displayed above 

the channel display. 

� The various statistics displayed on the screen are updated 

dynamically. 

� To quit from this command, press any key other than the left or 

right arrow keys. 

Continuous Display of Port States (DPORT) 

The Display Port States (DPORT) command provides a real time status 

display of all serial ports and interface card channels (including ports on 

the dual serial interface card). 

To execute this command: 

� Enter DPORT at the console command prompt. 




BOSTON>DPORT 

DISPLAY PORT STATES 

-------------------------------------------------------------------------------- 

|PORT# PROTOCOL INTERFACE SPEED MODEM STATE DELAY | 

| (BPS) SIGNALS | 

-------------------------------------------------------------------------------- 

| 1 FR-USER DCE-V35 128k S-D--- WAIT | 

| 2 PVCR UNDEFINED 56000 ------ OFF | 

| 101 PVCR T1 1536k ST-RC- CALL | 

| 201 ACELP-CN T1 NO DSP ------ IDLE | 

| 301 ACELP-CN ANALOG FXS NO DSP ------ IDLE | 

| 401 PPP DTE-V35 0 -T-R-- CALL | 

| 402 HDLC UNDEFINED 0 ------ CALL | 

| | 

| | 

| | 

| | 

| | 

| | 

| | 

| | 

| | 

| | 

| | 

| Modem signals: d(S)r d(T)r (D)cd (R)ts (C)ts r(I) (-)off | 

-------------------------------------------------------------------------------- 

Use HOME, END, UP and DOWN arrow keys to scroll. Press any other key to exit. 

� In this example: 

� Ports 1 and 2 are the two built-in serial ports on the SDM-9360 

base unit 

� Port 101 is the first channel on a T1 interface card installed in 

slot 1. This channel is configured for data transport 

� Port 201 is the first channel on another T1 interface card installed 

in slot 2. This channel is configured for voice transport 

� Port 301 is the first voice channel on an FXS interface card 

installed in slot 3 

� Ports 401 and 402 are on a dual serial interface card installed in 

slot 4. 


dynamically. 

� To quit from this command, press any key other than , 

or the up and down arrow keys. 

Continuous Display of PU States (DPU) 

The Display PU States (DPU) command shows the status of all PUs in 

real time. To execute this command: 

� Enter DPU at the console command prompt. 




CHICAGO>DPU 

DISPLAY PU STATES 

-------------------------------------------------------------------------------- 

| PU# STATE SESSIONS STATE: #SA=5 #SP=2 | 

| | 

-------------------------------------------------------------------------------- 

| 1 WAIT SEC ACTIVE | 

| 2 CONNECTED | 


| 4 WAIT PRI CONN | 



| 7 PAUSE | 


| 9 CONNECTION OFF | 





| | 

| | 

| | 

| | 

-------------------------------------------------------------------------------- 



dynamically. 



Continuous Display of PVC States (DPVC) 

The Display PVC States (DPVC) command shows the status of all PVCs 

in real time. The information is organized according to PVC number, in 

ascending order. 


� Enter DPVC at the console command prompt. 


CHICAGO>DPVC 

DISPLAY PVC STATES 

----------------------------------------------------------------------------- 

|PVC MODE INFO. SPEED CRV DLCI DESTINATION STATE &| 

| SIGNALS (BPS) NAME DELAY(MS)| 

----------------------------------------------------------------------------- 

| 1 MULTIPLEX USER -A--- 56000 100 NEW YORK DATA 13| 

| 2 PVCR off line 56000 101 PHILADELPHIA DOWN | 

| 3 PVCR USER -A--- 56000 102 PARIS DATA 19| 

| 4 PVCR off line 56000 0 DOWN | 





| 9 | 

| 10 | 

| 11 | 

| 12 | 

| 13 | 

| 14 | 

| 15 | 

| 16 | 

| 17 | 

| | 

|Information signals: NETwork/USER (N)ew (A)ctive (C)ir (F)ecn (B)ecn (-)off| 

----------------------------------------------------------------------------- 





dynamically. 



Continuous Display of PVC DLCI States (DDLCI) 

The Display PVC DLCI States (DDLCI) command also shows the status 

of all PVCs in real time. Unlike the DPVC command, however, the 

information is organized according to DLCI number, in ascending order. 


� Enter DDLCI at the console command prompt. 


CHICAGO>DDLCI 

DISPLAY PVC DLCI STATES 

-------------------------------------------------------------------------------- 

|DLCI PVC MODE INFO. SPEED PORT DESTINATION STATE & | 

| SIGNALS (BPS) NAME DELAY(MS) | 

-------------------------------------------------------------------------------- 

|100 1 PVCR USER -A--- 2048 k 16384 BOSTON DATA 5ms | 

|200 2 PVCR USER ----- 56000 1 CALL | 

| | 

| | 

| | 

| | 

| | 

| | 

| | 

| | 

| | 

| | 

| | 

| | 

| | 

| | 

| | 

| | 

| Information signals: NETwork/USER (N)ew (A)ctive (C)ir (F)ecn (B)ecn (-)off | 

-------------------------------------------------------------------------------- 


� In this example the first PVC runs over IP, as indicated by port 

number 16384. 


dynamically. 





Continuous Display of SVC States (DSVC) 

The Display SVC States (DSVC) command shows the status of all SVCs 

in real time. To execute this command: 

� Enter DSVC at the console command prompt. 


CHICAGO>DSVC 

DISPLAY SVC STATES 

-------------------------------------------------------------------------------- 

|SVC MODE INFO. SPEED CRV DLCI DESTINATION STATE & | 

| SIGNALS (BPS) NAME DELAY(MS) | 

-------------------------------------------------------------------------------- 

| 1 PVCR USER -A--- 20160 32771 20 9350 DATA 20ms | 

| 2 OFF USER ----- 0 0 0 OFF | 

| 3 OFF USER ----- 0 0 0 OFF | 

| 4 OFF USER ----- 0 0 0 OFF | 

| 5 OFF USER ----- 0 0 0 OFF | 

| 6 OFF USER ----- 0 0 0 OFF | 

| 7 OFF USER ----- 0 0 0 OFF | 

| 8 OFF USER ----- 0 0 0 OFF | 

| 9 OFF USER ----- 0 0 0 OFF | 

| 10 OFF USER ----- 0 0 0 OFF | 

| 11 OFF USER ----- 0 0 0 OFF | 

| 12 OFF USER ----- 0 0 0 OFF | 

| 13 OFF USER ----- 0 0 0 OFF | 

| 14 OFF USER ----- 0 0 0 OFF | 

| 15 OFF USER ----- 0 0 0 OFF | 

| 16 OFF USER ----- 0 0 0 OFF | 

| 17 OFF USER ----- 0 0 0 OFF | 

| | 

| Information signals: NETwork/USER (N)ew (A)ctive (C)ir (F)ecn (B)ecn (-)off | 

-------------------------------------------------------------------------------- 



dynamically. 



Viewing Current Hardware and Software 

Settings 

A wide variety of commands are available for studying the current 

hardware and software settings on the NetPerformer unit. 

Display Configuration Parameters (DP) 

The DP command provides a complete list of current values for all 

configuration parameters. To display the configuration parameters and 

their values: 

� Enter DP at the console command prompt. 

� Enter the name of the submenu of parameters you want to inspect, 

or 

� Enter ALL to display all configuration parameters. 

Note: This option also lists all currently active extended 

parameters. 



Here is an example of how to list a single submenu of parameters: 

Depending on the submenu you select: 

� You may be requested to specify a single connection for viewing, 

e.g. a single port, channel, PU, PVC. 

� The DP command may display enabled connections only, rather than 

all the connections you have configured, e.g. DP/SCHEDULE. 

Here is an example of how to list all configuration parameters: 

Display Config Text (DCFG) 

CHICAGO>DP 

DISPLAY PARAMETERS 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER/ALL,def:GLOBAL) ? PU 


PU #4> Operating mode...........................SDLC-LINKS 

PU #4> Controller active........................YES 

PU #4> Delay before connection..................60 

PU #4> SDLC port................................2 

PU #4> SDLC address.............................04 

PU #4> SDLC retransmission timeout (msec).......3000 

PU #4> SDLC number of retransmission retries....10 

PU #4> SDLC transmission window size............7 

PU #4> SDLC frame size..........................512 

PU #4> Remote unit..............................BOSTON 

PU #4> Class....................................6 

PU #4> Remote PU number.........................4 

PU #4> XID support..............................NO 

CHICAGO>DP 

DISPLAY PARAMETERS 


CLASS/PVC/IPX/MAP/CUSTOM/HUNT/VLAN/USER/ALL,def:PU) ? ALL 

Wait for after each screen (NO/YES,def:YES) ? NO 





GLOBAL> Unit name...............................CHICAGO 

GLOBAL> Unit routing version....................1 

GLOBAL> Contact name............................Verso Technologies 

GLOBAL> Unit location...........................Unknown 

GLOBAL> Loopback................................NO 

GLOBAL> Link timeout delay......................0 

GLOBAL> Transit delay (sec).....................4 

GLOBAL> Daylight saving time....................NO 

... 

� If you would like to view this display one screen at a time, enter YES 

at the prompt Wait for after each screen. 

The Display Config Text (DCFG) command displays the entire contents 

of the current text-based configuration file, CFG.TXT. This provides a list 

of all configuration parameters that have been changed from their 

default values, which can be useful for both reporting and 

troubleshooting purposes. Information on product hardware and 

firmware versions is provided under the [HEADER] section. 



To view the text-based configuration file: 

� Enter DCFG at the console command prompt. 

� Enter YES at the prompt Wait for after each screen if you 

would like to view the file one screen at a time. 


BOSTON>DCFG 

DISPLAY CONFIG TEXT 


[HEADER] 

VERSION=1.0 


Code base vX.X.X Verso Technologies, Inc. (c) 2004 












THU 2004/02/19 14:19:25 

[npsys] 

Name=BOSTON 

SlotType=0A44474200000000000000000000000000000000 

FastSePolling=YES 

[ifwan 1] 

Protocol=PVCR 

Mode=ANSWER 

[END] 

Display Slot Information (DSI) 

The Display Slot Information command (DSI) identifies the type of card, 

if any, that is installed in each of the 4 slots on the NetPerformer unit. 


� Enter DSI at the console command prompt. 


CHICAGO>DSI 

DISPLAY SLOT INFORMATION 

SIGNALING ENGINE - S/N: DATA: 

SLOT 1> Analog FXS Interface - 2 ports 

SLOT 2> Serial Interface 

SLOT 3> T1 Interface 

SLOT 4> No card installed 



Signaling Engine Channels (SEC) 

The Signaling Engine Channels (SEC) command displays Signaling 

Engine channel information, including the correspondences between 

slots and SE channels. To display this information: 

� Enter SEC at the console command prompt. 


BOSTON>SEC 

SIGNALING ENGINE CHANNELS 

SLOT> Slot number (1/2/3/4/ALL,def:ALL) ? 

SLOT 1> 

PORT 101 --> CHANNEL 0 

SLOT 2> 

VOICE 201 --> CHANNEL 1 

SLOT 3> 

VOICE 301 --> CHANNEL 2 

SLOT 4> 



Signaling Engine Information (SEI) 

The Signaling Engine Information (SEI) command displays information 

concerning: 

� Signaling Engine software version and status 

� The type of card, if any, that is installed in each of the 4 slots on the 

NetPerformer unit 

� DSP software version 

� Status of all DSP SIMMs installed in the unit. 

To display this information: 

� Enter SEI at the console command prompt. 




Display Map File (DMF) 

BOSTON>SEI 

SIGNALING ENGINE INFORMATION 

SIGNALING ENGINE SOFTWARE: SE920A09.BIN 


Processor State: RUNNING 

SLOT 1> Analog FXS Interface - 2 ports 

SLOT 2> Serial Interface 

SLOT 3> T1 Interface 

SLOT 4> No card installed 

DSP SOFTWARE: QU207101.BIN 

Subfile 100: 100Mhz Bootstrap File Ver. X.X.X.X 

Subfile 2: Operational Code, (G.711, G.729/A) Ver. X.X.X.X 

DSP SIMM 1 DSP SIMM 2 

1 NO DSP 7 RUNNING(2) 






There are two commands that display map file contents: 

� Display Map File (DMF), which shows the entire map file: 

Enter DMF. 

� Display Parameters (DP), which shows a single map entry: 

Enter the menu sequence: DP ↵ MAP. 

Note: The DP command was discussed earlier in Display 

Configuration Parameters (DP) on page 214. 



Here is an example of the DMF command from the standard 


CHICAGO>DMF 

DISPLAY MAP FILE 

MAP VERSION: A.3 

MAP #1> Type....................................NAME 

MAP #1> Entry digits............................456 

MAP #1> Destination Name........................1234567890123456 

MAP #1> Destination Extension number source.....MAP 

MAP #1> Destination Extension number............12 

MAP #1> Extended digits source..................USER 

MAP #1> Number of extended digits...............0 

MAP #1> Use SVC connection......................YES 

MAP #1> SVC address type........................X.121 

MAP #1> SVC network address.....................123456789012345 

MAP #2> Type....................................NAME 


MAP #2> Destination Name........................BOSTON 

MAP #2> Destination Extension number source.....HUNT 

MAP #2> Destination Extension number............A 

MAP #2> Extended digits source..................NONE 

MAP #2> Extended digits to forward..............NONE 

MAP #2> Use SVC connection......................NO 

MAP #3> Type....................................NAME 


MAP #3> Destination Name........................BOSTON 

MAP #3> Destination Extension number source.....USER 

MAP #3> Destination Extension number............NONE 


MAP #3> Extended digits to forward..............NONE 

MAP #3> Use SVC connection......................YES 

MAP #3> SVC address type........................E.164 

MAP #3> SVC network address.....................123456789012345 


BOSTON>DMF 

DISPLAY MAP FILE 

MAP VERSION: B.3 

MAP #1> Type....................................DIAL STRING + IP 

MAP #1> Digits string...........................5143984000 

MAP #1> Digits string length....................15 

MAP #1> Strip prefix number of digits...........I0 E0 

MAP #1> Prepend string.......................... 

MAP #1> Append string........................... 

MAP #1> IP address..............................105.254.0.1 

MAP #1> Egress hunt group pattern...............ROTARY 

MAP #1> Egress hunt group ports.................101-124 

MAP #2> Type....................................DIAL STRING 

MAP #2> Digits string...........................4506595090 



MAP #2> Prepend string..........................I1604 

MAP #2> Append string...........................I67820 

MAP #2> Egress hunt group pattern...............SEQUENTIAL 

MAP #2> Egress hunt group ports.................201 

MAP #3> Type....................................SUPERMAP 





MAP #3> Egress hunt group ports.................101,103-104,201,203 



Display NAT Table (DN) 

� Use the Erase Map File (EMF) command to remove one or more 

entries from the Voicing Mapping table; enter EMF at the 

NetPerformer console command prompt. 

Note: The EMF command is available to users with FULL console 



The Display NAT Table Information (DN) command displays the NAT 

translation table, which includes: 

� Source and destination IP and NAT IP addresses 

� Source and destination TCP/UDP ports and NAT (NAPT) ports 

� The current timeout for each address mapping. 


� Enter DN at the console command prompt. 

In the following example, the first two entries are in NAT mode, and the 

last is in NAPT mode: 

BOSTON>DN 

DISPLAY NAT TABLE INFORMATION 

IP NAT rule number (1/2/3/4/5/6/7/8/9/10/ALL,def:1) ? 1 

Active translation entries: 

Rule IP Nat IP Port Nat Port Timeout 

Source : 1 010.000.000.001 205.168.043.010 0 0 

Destination: 206.001.001.001 206.001.001.001 0 0 1440 

Source : 1 010.000.000.003 205.168.043.012 0 0 

Destination: 206.001.001.002 206.001.001.002 0 0 1439 

Source : 1 010.000.000.003 205.168.043.012 21 60000 

Destination: 206.001.001.003 206.001.001.003 21 21 1439 

� Use the Clear NAT Entry (CN) command to remove one or more 

entries from the NAT translation table; enter CN at the NetPerformer 

console command prompt, then select SINGLE, RULE or ALL entries. 

Note: The CN command is available to users with FULL console 



Display the Current Time (DT) 

The Display Time (DT) command shows the current date and time. To 

execute this command: 

� Enter DT at the console command prompt. 




CHICAGO>DT 

DISPLAY TIME 

Time> MON 2004/02/16 14:23:06 

Setting the Time (ST command) 

Use the Set Time (ST) command to change the date and time on the 


Note: The ST command is available to users with FULL console access 

only. To change access privileges for a particular user, refer to Defining 

User Access Profiles on page 70. 

To execute the ST command: 

� Enter ST at the console command prompt. 

� Modify the Year, Month, Day of the month, Day of the week, Hour, 

Minute and Second settings, as required. 

� Enter YES at the Confirm new time prompt to accept the changes. 


CHICAGO>ST 

SET TIME 

CLOCK> Year (1992-2030,def:2004) ? 

CLOCK> Month (1-12,def:2) ? 

CLOCK> Day of the month (1-28,def:16) ? 17 

CLOCK> Day of the week (def:MONDAY) ? TUESDAY 

CLOCK> Hour (0-23,def:14) ? 

CLOCK> Minute (0-59,def:23) ? 

CLOCK> Second (0-59,def:14) ? 

Time> TUE 2004/02/17 14:23:14 

Accept new time? (NO/YES,def:YES) ? YES 

Display Software Version (DV) 

The Display Version (DV) command displays the product name, 

software versions and location of the console connection. To execute 

this command: 

� Enter DV at the console command prompt. 


CHICAGO>DV 

DISPLAY VERSION 








Manipulating System Files and Settings 

The NetPerformer includes a set of system commands for manipulating 

files installed on the unit. These commands are similar in name and 

function to commonly used MS-DOS® commands. Two other 

commands, DHCP Client and DNS Cache, are provided for managing 

DHCP and DNS system settings. 

Check File System (CHKFS) 

Display File List (DIR) 

BOSTON>DV 

DISPLAY VERSION 





The Check File System (CHKFS) command verifies the integrity of all 

system files, and lists the number of free, allocated and fragmented 

blocks as well as the amount of free space available. 

Note: The CHKFS command is available to users with FULL console 

access only. 


� Enter CHKFS at the console command prompt. 


BOSTON>CHKFS 

CHECK FILE SYSTEM 

In progress... 

Number of free blocks = 1966 

Number of allocated blocks = 1872 

Free space = 5230592 bytes 

File system checked OK! 

The Display File List (DIR) command displays information concerning: 

� The software files installed on the NetPerformer unit, including 

current, backup and renamed files 

� The amount of used space and free space in the configuration buffer. 

Note: For a list of subfiles of the DSP software (QUADRA, or QU*.BIN) 

use the Signaling Engine Information (SEI) command, described on 

page 217. 



Copy File (COPY) 

To execute the DIR command: 

� Enter DIR at the console command prompt. 


BOSTON>DIR 

DISPLAY FILE LIST 

CURRENT.ALR 336 BYTES 2002/04/24 16:44:06 

SE110A05.BIN 556032 BYTES 2002/04/24 13:19:38 

GA110A05.BAK 1563648 BYTES 2002/04/24 13:19:59 

CFG_BKP.TXT 1864 BYTES 2002/04/24 16:37:17 

CFG.TXT 1836 BYTES 2002/04/24 16:44:12 

SE920A16.BIN 556032 BYTES 2002/04/15 15:09:25 

QU207103.BIN 485476 BYTES 2002/04/15 15:09:32 

GA920A16.BIN 1359872 BYTES 2002/04/15 15:09:49 

JOURNAL.TXT 29626 BYTES 2002/04/15 15:11:21 

INFO.HID 601 BYTES 2002/04/24 17:11:59 

Used space = 4555323 bytes 

Free space = 3258368 bytes 

For each file in the list, the DIR command shows: 

� The short name of the file in standard filename.extension format, 

where filename is a maximum of 8 characters and extension is 3 

characters 

� The size of the file, in bytes 

� The date and time that the file was downloaded to the NetPerformer 

unit. 

The Copy File (COPY) command allows you to create a new file that is 

identical to a file already installed on the NetPerformer unit. 

Note: The COPY command is available to users with FULL console 

access only. To change access privileges for a particular user, refer to 

Defining User Access Profiles on page 70. 

To execute the COPY command: 

� Enter COPY old_filename.extension new_filename.extension, 

where: 

new_filename is a maximum of 8 characters and extension is 3 

characters. 

Note: The name you assign to new_filename must be different from 

all other files on the system. 


CHICAGO>COPY CFG.TXT NEWCFG.TXT 

COPY FILE 

In progress...Completed 



Rename File (RENAME) 

Delete File (DELETE) 

The Rename File (RENAME) command allows you to change the name 

of a file already installed on the NetPerformer unit. 

Note: The RENAME command is available to users with FULL console 

access only. 


� Enter RENAME old_filename.extension new_filename.extension, 

where: 

new_filename is a maximum of 8 characters and extension is 3 

characters. 

Note: The name you assign to new_filename must be different from 

all other files on the system. 

Caution: Do not change the name of any file which may be called 

by a system function or referenced by another file, as this will 

have serious consequences for NetPerformer operations. If in 

doubt, contact NetPerformer Technical Support for confirmation 

before you change the filename. 

Here is an example of the RENAME command: 

CHICAGO>RENAME NEWCFG.TXT MSTR_CFG.TXT 

RENAME FILE 

In progress...File renamed! 

The Delete File (DELETE) command allows you to erase a file from the 


Note: The DELETE command is available to users with FULL console 

access only. 


� Enter DELETE filename.extension, where: 

filename is a maximum of 8 characters and extension is 3 

characters. 


Caution: Do not delete any file which may be called by a system 

function or referenced by another file, as this will have serious 

consequences for NetPerformer operations. If in doubt, contact 

NetPerformer Technical Support for confirmation before you 

delete the file. 



Here is an example of the DELETE command: 

CHICAGO>DELETE NEWCFG.TXT 

DELETE FILE 

Delete file NEWCFG.TXT, please confirm (NO/YES,def:NO) ? YES 

In progress...File removed! 

Defragment File System (DEFRAG) 

The Defragment File System (DEFRAG) command allows you to clean 

the NetPerformer file system of fragmented blocks. 

Note: The DEFRAG command is available to users with FULL console 

access only. 


� Enter DEFRAG. 



BOSTON>DEFRAG 

DEFRAGMENT FILE SYSTEM 

Clean file system, please confirm (NO/YES,def:NO) ? YES 

In progress...File system cleaned! 

Format File System (FORMAT) 

The Format File System (FORMAT) command erases all files in the 

system and reinitializes the file system. This allows the NetPerformer 

unit to receive new files through a download process. 

Note: The FORMAT command is available to users with FULL console 

access only. 

Caution: If this command is executed without prior preparation 

for downloading new files, all NetPerformer operations will cease. 

The FORMAT command must not be executed without the 

supervision of NetPerformer Technical Support. 

To execute the FORMAT command: 

� Enter FORMAT. 

� Enter YES at the first confirmation prompt. 

� Enter YES again at the second confirmation prompt. 




Managing the DHCP IP Address 

Managing the DNS Entries 

BOSTON>FORMAT 

FORMAT FILE SYSTEM 

Format file system (NO/YES,def:NO) ? YES 

Format file system, please confirm (NO/YES,def:NO) ? YES 

In progress...File system format OK! 

A new command, DHCP Client, has been added to the NetPerformer 

console to manage the DHCP IP address assigned by the DHCP server. 


� Enter DHCP at the console command line. 

� Select one of the following operations: 

� RELEASE: Clears the IP address that was learned from the DHCP 

server. 

� RENEW: Gets a new IP address from the DHCP server. 


CHICAGO>DHCP 

DHCP CLIENT 

Operation (RELEASE/RENEW,def:RELEASE) ? RELEASE 

Release IP address, please confirm (NO/YES,def:NO) ? YES 

A new command has been added to the NetPerformer console to 

manage the DNS entries: DNS Cache (DNS). This command allows the 

user to view or delete the DNS entries that were defined with the 

SETUP/IP/DNS submenu (described on page 82). 

Note: The DNS command is available to users with FULL console access 

only. 

To execute the DNS command: 

� Enter DNS at the NetPerformer console command prompt. 

� At the Operation prompt, enter: 

� DISPLAY, to view the current DNS characteristics, or 

� CLEAR, to delete the DNS characteristics. 



Capturing Traffic 

Setup Capture (SC) 

Here is an example from the NetPerformer console: 

CHICAGO>DNS 

DNS CACHE 

Operation (DISPLAY/CLEAR,def:DISPLAY) ? DISPLAY 

DESTINATION IP ADDRESS TTL 

A.ACME.COM 192.168.001.001 30 s 

TEST.ACME.COM 172.016.035.233 1 h 

The NetPerformer offers commands which allow you to capture traffic 

passing across one or more interfaces, and view an analysis of this 

traffic at a later time. 

Use the Setup Capture (SC) command to determine which interfaces on 

the NetPerformer unit will be scanned during execution of the traffic 

capture. The actual capture may be executed with this command, or at 

a later time using the Start Capture (STC) command (see page 230). 

To execute the SC command: 

� Enter SC at the console command prompt. 

� Select a Capture ITEM: 

� ATM: (on NetPerformer installed with the ATM firmware option 

only) to capture AAL1VC, INTERFACE, VC or RAW CELL traffic. For 

AAL1VC and VC, select the ATM VC number. 

� DSP: Select the DSP number, and confirm whether DSP Pings 

and/or DSP Data should be included with the capture 

� PORT: Select the desired port 

� PU: Select the PU number 

� PVC: Select the PVC number 

� SE: to capture internal messages between the main card and the 

Signaling Engine with real traffic. Select the Capture type 

(NORMAL or ISDN DECODE), Slot number and Channel Number 

� SLOT: Select the Slot number and Channel Number 

� SVC: (on standard NetPerformer only) Select the SVC number 

� SIP: (on NetPerformer SIP VoIP option only) to capture voice 

channel to SIP information. Select the Slot number and Channel 

Number, and confirm whether SEAPI, SEV-to-CCIP, CCIP-to-SIP, 

RTP/FAX data and/or RTCP should be included with the capture. 



� Select more than one Capture ITEM by entering YES at the Capture 

another item confirmation prompt. 

� Set the Capture mode: 

� FULL: The capture will terminate when the capture buffer is 

filled. 

� CONTINUE: The capture will terminate according to the specified 

Capture ending. 

� Set the Capture ending: 

� MANUAL: The capture will terminate when you press the 

key (FOREGROUND mode only) or execute the End Capture (EC) 

command (see page 233). 

� TRIG: The capture will terminate when a special trigger is 

received across one of the captured interfaces. 

Note: If you select a trigger ending, you will be prompted for the 

Trigger offset, which determines which byte in the header 

contains the trigger value, the Trigger mask, which defines the 

relevant bits that will be examined for the trigger value, and the 

Trigger value, which is the value that must be found in the 

header before the NetPerformer will end the capture. 

� Set the Capture activation mode: 

� FOREGROUND: The capture status will be displayed during 

execution of the capture. 

� BACKGROUND: The capture status will not be displayed during 

execution. Once capture setup is complete, you return 

immediately to the NetPerformer console command prompt. 

Note: You can terminate the capture before its normal 

termination by executing the End Capture (EC) command (see 

page 233). 

� Enter YES at the Start capture confirmation prompt to begin the 

traffic capture immediately. Enter NO if you would like to execute 

the capture at a later time, using the STC command. 



Here is an example of how several capture items are selected for an 

immediate traffic capture that is executed in FOREGROUND mode: 

BOSTON>SC 

SETUP CAPTURE 

Capture ITEM (ATM/DSP/PORT/PU/PVC/SE/SLOT/SIP,def:PORT) ? PORT 

Capture port (ETH/CSL/1/2,def:ETH) ? ETH 

Capture another item, please confirm (NO/YES,def:NO) ? YES 

Capture ITEM (ATM/DSP/PORT/PU/PVC/SE/SLOT/SIP,def:PORT) ? SLOT 


SLOT> Channel Number (301,def:301) ? 305 

Capture another item, please confirm (NO/YES,def:NO) ? YES 

Capture ITEM (ATM/DSP/PORT/PU/PVC/SE/SLOT/SIP,def:SLOT) ? DSP 

Capture DSP number (7/8/9/10/11/12/ALL,def:7) ? ALL 

Capture DSP Pings (NO/YES,def:YES) ? YES 

Capture DSP Data (NO/YES,def:YES) ? YES 

Capture another item, please confirm (NO/YES,def:YES) ? 

Capture ITEM (ATM/DSP/PORT/PU/PVC/SE/SLOT/SIP,def:DSP) ? PORT 

Capture port (ETH/CSL/1/2,def:ETH) ? CSL 


Capture ITEM (ATM/DSP/PORT/PU/PVC/SE/SLOT/SIP,def:PORT) ? PVC 

Capture PVC (1-300,def:1) ? 2 


Capture ITEM (ATM/DSP/PORT/PU/PVC/SE/SLOT/SIP,def:PVC) ? SE 

Capture type (NORMAL/ISDN DECODE,def:NORMAL) ? 

SLOT> Slot number (1/2/3/4/ALL,def:1) ? 

SLOT> Channel Number (101,def:101) ? 


Capture ITEM (ATM/DSP/PORT/PU/PVC/SE/SLOT/SIP,def:SE) ? ATM 

Capture ITEM (AAL1VC/INTERFACE/VC/RAW CELL,def:INTERFACE) ? VC 

Capture ATM VC (1-300,def:1) ? 10 

Capture another item, please confirm (NO/YES,def:YES) ? NO 

Capture mode (FULL/CONTINUE,def:CONTINUE) ? 

Capture ending (MANUAL/TRIG,def:MANUAL) ? 

Capture activation (FOREGROUND/BACKGROUND,def:FOREGROUND) ? 

Start capture, please confirm (NO/YES,def:YES) ? YES 

Baseboard: 63, 3 Kb ( 2 %) 

The capture is terminated 

Here is an example of SIP information capture: 

BOSTON>SC 

SETUP CAPTURE 

Capture ITEM (ATM/DSP/PORT/PU/PVC/SE/SLOT/SIP/SPECIAL,def:PORT) ? SIP 


SLOT> Channel Number (201,def:201) ? 

Capture SEAPI (NO/YES,def:NO) ? YES 

Capture SEVCCIP (NO/YES,def:NO) ? YES 

Capture CCIPSIP (NO/YES,def:NO) ? YES 

Capture RTP/FAX data (NO/YES,def:NO) ? YES 

Capture RTCP (NO/YES,def:NO) ? YES 

Capture another item, please confirm (NO/YES,def:NO) ? 

Capture mode (FULL/CONTINUE,def:FULL) ? 

Capture activation (FOREGROUND/BACKGROUND,def:FOREGROUND) ? 

Start capture, please confirm (NO/YES,def:YES) ? 

Baseboard: 1146, 113 Kb ( 88 %) 




Start Capture (STC) 

View Capture (VC) 

The Start Capture (STC) command executes a capture that has been 

previously defined with the Setup Capture (SC) command. The way the 

capture is executed and terminated follows the SC command settings. 

To execute the STC command: 

� Enter STC at the console command prompt. 


CHICAGO>STC 

START CAPTURE 

To modify the setup of your capture use Setup Capture (SC) 

Baseboard: 10, 1 Kb ( 0 %) 


The View Capture (VC) command lets you view the traffic that was 

captured by the Setup Capture (SC) or Start Capture (STC) command. 

You can select all or a subset of the interfaces captured. The display 

includes: 

� Software and hardware versions running on the unit 

� Start and stop times for the capture 

� Relative time for each data block 

� Traffic direction (TX or RX) 

� Interface type 

� Type and length of each block 

� The actual traffic, in hexadecimal format. 

� Decoding of the control field (if this option is selected). 

To execute the VC command: 

� Enter VC at the console command prompt. 

� For each interface that was captured, include (YES) or exclude (NO) 

its traffic from the capture display, following the console prompts. 

� To include control field decoding with the display of a particular 

traffic type, enter YES at the Decode control field prompt and set 

the following: 

� For a port in HDLC mode, the Decode Modulo. 

� For all captures, the Decode With Starting Block Number. 

� Set Wait for after each screen to YES if you want to 

analyze the traffic one screen at a time from the console. 



Here is an example of console port traffic displayed with the VC 

command: 

BOSTON>VC 

VIEW CAPTURE 

Include Port ETH (NO/YES,def:YES) ? NO 

Include Slot 3 Channel 305 (NO/YES,def:YES) ? NO 

Decode control field (NO/YES,def:YES) ? 

Include DSP All (NO/YES,def:YES) ? NO 

Include Port CSL (NO/YES,def:YES) ? YES 

Decode control field (NO/YES,def:YES) ? YES 

Include PVC 2 (NO/YES,def:YES) ? NO 

Include Unrequested Blocks? (NO/YES,def:YES) ? 

Decode Modulo (8/128,def:8) ? 

Decode With Starting Block Number (1-65,def:1) ? 










Portable SIP Stack X.X.X 





Capture started> THU 2004/02/19 14:56:44 

Capture ended> THU 2004/02/19 14:56:54 

TIME(SEC)DIR INDEX TYPE LNG DATA 

0.000 TX WAN CSL VAR 41 BLOCK = 1 

0D0A0D20 20426173 65626F61 72643A20 

20202020 20302C20 20202020 2030204B 

62202820 20302025 29 


0D202042 61736562 6F617264 3A202020 

20202031 2C202020 20202030 204B6220 


28202030 202529 


... 

0D202042 61736562 6F617264 3A202020 

20203237 2C202020 20202031 204B6220 

28202031 202529 



Here is an example of SIP information display with the VC command: 

BOSTON>VC 

VIEW CAPTURE 

Include Slot 2 Channel 201 (NO/YES,def:YES) ? 

Decode control field (NO/YES,def:YES) ? 

Include Unrequested Blocks? (NO/YES,def:YES) ? 

Decode With Starting Block Number (1-740,def:1) ? 






Type: ISDN BRI 

Board ID: 2 


DSP Operational Code, (G.711, G.729/A) Ver. 2.0.71.2 


DBG v2.3.0 (R8) Verso Technologies, Inc. (c) 2004 

BOOT v1.1.0 Verso Technologies, Inc. (c) 2004 


Hardware Info> Slave Board Id: 4 

Hardware Info> Slave Board FPGA Id: 10 

Hardware Info> Slave Board MACH Id: 0 

ATM 860SAR detected 


Capture started> THU 2004/02/05 16:31:41 

Capture ended> THU 2004/02/05 16:32:00 

TIME(SEC)DIR INDEX TYPE LNG DATA 

0.000 RX SEAPI 201 CMD 24 BLOCK = 1 

COMMAND: SETUP 

REFERENCE: 201 

SEAPI CHANNEL: 0 

0.000 RX SEAPI 201 IE 108 BLOCK = 2 

CC MESSAGE HEADER 

LENGTH: 5 

MSG LENGTH: 108 

CHANNEL: 0 

CRV: 00000002 

PORT: 1 

TIME SLOT: 0 

CHANNEL IE: 0 

CRV IE: 00000002 

SIGNALING IE: 

LENGTH: 2 

00000003 00000000 

BEARER CAPS IE: 

LENGTH: 7 

00000000 00000001 00000000 00000000 

00000000 00000000 00000000 

0.000 SEV->CCIP 201 SIP REQ/IND 36 BLOCK = 3 

REQ: SEV_IE_IND 

00006E23 000000C9 0000006C 0062942C 

00000001 001938C4 0062942C 00000000 

00000000 

0.000 SEV->CCIP 201 SIP REQ/IND 36 BLOCK = 4 

REQ: SEV_OFF_HOOK_IND 

00006E14 000000C9 00000020 00000000 

00000001 00000001 00771AA8 00000000 

00771AC0 

0.000 STATE FCT 201 EVENT 3 BLOCK = 5 

EVENT: INT_SETUP_IND 

STATE: CCIP_STATE_IDLE 

810902 

0.000 SEV


End Capture (EC) 

This command is used to terminate a capture that is executing in 

BACKGROUND mode before the capture terminates normally. To 

execute this command: 

� Enter EC. 


CHICAGO>EC 

END CAPTURE 


Capture Frame Length (CL) 

The Capture Frame Length (CL) command analyzes and displays frame 

length statistics for traffic sent from a Frame Relay port or PVC. These 

statistics can be helpful for troubleshooting transmission problems on 

some public Frame Relay networks. To execute this command: 

� Enter CL at the console command prompt. 

� Select one of the CL command options: 

� START: Set the Number of frames you want analyzed, set the 

Type to PORT or PVC, and enter the port or PVC number. 

The CL command operates in background mode. Let it run for a 

sufficient amount of time before viewing the frame length 

analysis. 

� STOP: To stop the capture before the entire frame sample has 

been collected. 

� DISPLAY: To view the frame length analysis. 

� DELETE: To delete the contents of the capture buffer. 

Note: Since each capture overwrites the buffer contents, you do 

not need to clear the buffer before executing another capture. 



Here is an example of all of the CL command options: 

Locating Network Components 

The NetPerformer includes several commands that display routing 

tables and other interface connections, and test the validity of these 

connections. 

Display Routing Table (DR) 

CHICAGO>CL 

CAPTURE FRAME LENGTH 

Operation (START/STOP/DELETE/DISPLAY,def:START) ? START 

Number of frames (0-10000,def:1000) ? 

Type (PORT/PVC,def:PORT) ? 

Capture port (1/2,def:1) ? 

Capture of frame length is running ! 

CHICAGO>CL 


Operation (START/STOP/DELETE/DISPLAY,def:START) ? STOP 

CHICAGO>CL 


Operation (START/STOP/DELETE/DISPLAY,def:STOP) ? DISPLAY 

Number of frames .......................... 27 

Smallest frame ............................ 7 

Largest frame ............................. 141 

Mean length ............................... 19 

Distribution: less than 10 bytes ........ 22 

10 to 19 bytes ........ 0 

20 to 29 bytes ........ 0 

30 to 49 bytes ........ 2 

50 to 74 bytes ........ 2 

75 to 99 bytes ........ 0 

100 to 249 bytes ........ 1 

250 to 499 bytes ........ 0 

500 to 749 bytes ........ 0 

750 to 999 bytes ........ 0 

1000 to 1499 bytes ........ 0 

1500 to 1999 bytes ........ 0 

2000 to 3999 bytes ........ 0 

more than 4000 bytes ........ 0 

CHICAGO>CL 


Operation (START/STOP/DELETE/DISPLAY,def:DISPLAY) ? DELETE 

The Display Routing Table (DR) command provides the current status of 

all network connections that use IP or IPX routing and travel via the 

NetPerformer unit. The DR command displays several types of IP and 

IPX routing tables: 

� IP UNICAST RIP 

� IP UNICAST MULTIHOMED 

� IP MULTICAST GROUP 

� IP MULTICAST IGMP 

� IPX RIP 

� IPX SAP 



To view a routing table: 

� Enter DR at the console command prompt. 

� Enter the targeted routing table type as a menu sequence. 

For example, to view the IP UNICAST RIP routing table, enter the 

menu sequence: IP ↵ UNICAST ↵ RIP. 

Here are examples of the IP Unicast routing tables: 

BOSTON>DR 

DISPLAY ROUTING TABLE 

Item (IP/IPX,def:IP) ? IP 

Item (UNICAST/MULTICAST,def:UNICAST) ? UNICAST 

Item (RIP/MULTIHOMED,def:RIP) ? RIP 

The routing table has 4 entry(ies) 

DESTINATION VAL COST INTRF NEXT HOP AGE MASK TYPE PROT 

128.128.000.000 Y 0 LAN-1 128.128.000.001 0 s 255.255.000.000 SUB LOCAL 

128.128.000.001 Y 0 LAN-1 128.128.000.001 0 s 255.255.255.255 HOST LOCAL 

128.128.000.002 Y 1 2001 000.000.000.000 12 s 255.255.255.255 HOST RIP 

128.129.000.000 Y 1 2001 000.000.000.000 12 s 255.255.000.000 NET RIP 

BOSTON>DR 


Item (IP/IPX,def:IP) ? 

Item (UNICAST/MULTICAST,def:UNICAST) ? 

Item (RIP/MULTIHOMED,def:RIP) ? MULTIHOMED 

DESTINATION MASK VALID METRIC INTRF TTL 

128.128.000.000 255.255.000.000 Y 0 LAN-1 10 m 

128.128.000.001 255.255.000.000 Y 0 LAN-1 10 m 

128.128.000.002 255.255.000.000 Y 1 2001 10 m 

Here are examples of the IP Multicast routing tables: 

BOSTON>DR 



Item (UNICAST/MULTICAST,def:MULTICAST) ? MULTICAST 

Item (GROUP/IGMP,def:GROUP) ? GROUP 

Group: 225.000.001.001 

Source: 005.000.001.128 upstream neighbor: 005.061.002.002 

Incoming interface: 2 # frames received: 10958 

Outgoing interface: LAN # frames transmitted: 10958 

Group: 225.000.002.002 




Group: 225.000.003.003 




Group: 225.000.004.004 




BOSTON>DR 



Item (UNICAST/MULTICAST,def:UNICAST) ? MULTICAST 

Item (GROUP/IGMP,def:IGMP) ? IGMP 

ADDRESS INTRF AGE TTL LAST REPORTER 

225.000.001.001 LAN 399 s 234 s 005.001.000.001 

225.000.002.002 LAN 407 s 238 s 005.001.000.001 

225.000.003.003 LAN 403 s 231 s 005.001.000.001 

225.000.004.004 LAN 402 s 232 s 005.001.000.001 



Display Connections (DX) 

Here are examples of the IPX routing tables available with the DR 

command: 

CHICAGO>DR 


Item (IP/IPX,def:IPX) ? IPX 

Item (RIP/SAP,def:SAP) ? RIP 

The RIP table has 8 entry(ies) 

NETWORK NUMBER TICKS HOP COUNT NEXT HOP AGE 

30212251 2 1 FCFEE67F 57 s 

B45A3DAD 2 1 FCFEE67F 57 s 

B9360001 3 2 00000000 25 s 

B9360002 4 3 00000000 25 s 

B9360003 2 1 00000000 25 s 

B9360004 3 2 00000000 25 s 

BADBABE0 3 2 FCFEE67F 50 s 

FCFEE67F 1 0 FCFEE67F 0 s 

CHICAGO>DR 


Item (IP/IPX,def:IPX) ? IPX 

Item (RIP/SAP,def:RIP) ? SAP 

The SAP table has 10 entry(ies) 

NET NUM NODE SOCKET SERVICE NAME TYPE HOP COUNT AGE 

30212251 000000000001 0000 PRE-RD-001 027B 1 37 s 

30212251 000000000001 0005 PRESTICOM________________ 026B 1 37 s 

30212251 000000000001 0451 PRE-RD-001 0004 1 37 s 

30212251 000000000001 4006 PRESTICOM________________ 0278 1 37 s 

30212251 000000000001 4014 ISPRE-RD-0011872400800000 0102 1 37 s 

30212251 000000000001 4015 LDPNVIRUS_PROTECT_5122213 0102 1 37 s 

30212251 000000000001 4016 IVPRE-RD-0011872400800000 0102 1 37 s 

30212251 000000000001 401F PRE-RD-001 0237 1 37 s 

30212251 000000000001 4800 PRE-RD-001 0238 1 37 s 

30212251 000000000001 8059 BSER4.00-6.10_30212251000 004B 1 37 s 

The Display Connections (DX) command displays all active PowerCell 

(PVCR link), IP and IPX (LAN port) and console (Relay) connections on 

the NetPerformer unit. To execute this command: 

� Enter DX at the console command prompt. 


BOSTON>DX 

DISPLAY CONNECTIONS 

GROUP to CHICAGO [SDM-9360] 

LINK 1 [port] 

CLASS 1 

CHANNEL IP to CHICAGO : (tx1/rx1) compressed 

CHANNEL IPX to CHICAGO : (tx2/rx2) compressed 

CLASS 0 

CHANNEL MGMT1 to CHICAGO : (tx3/rx3) uncompressed 

CHANNEL RELAY to CHICAGO : (tx3/rx3) uncompressed 



Display Destination Table (DD) 

The Display Destination Table (DD) command provides a display of the 

current status of all destinations reached via ports and PVCs configured 

with the PVCR protocol. To execute this command: 

� Enter DD at the console command prompt. 


CHICAGO>DD 

DISPLAY DESTINATION TABLE 

The destination table has 3 entry(ies) 

DESTINATION VAL COST INTRF NEXT HOP AGE 

NEWYORK Y 0 1 MONTREAL 0 s 

LOSANGELES Y 0 2 MONTREAL 0 s 

CHICAGO Y 1 2 LOSANGELES 646 s 

� You can also enter a character string as an argument to refine the 

results of this command. 

Note: This option is not available if the unit is configured with Unit 

Routing Version 1. Refer to Defining the Global Characteristics on 

page 71. 

For example, enter a shortened version of a Unit ID to view the 

status of all destinations that match this character string: 

BOSTON>DD CHICAGO 

DISPLAY DESTINATION TABLE 

Send request...Wait response. 

The matching list with 'CHICAGO' has 3 entry(ies) 

DESTINATION VAL COST 

CHICAGO.0 YES 1 



Note: The INTRF (Interface), NEXT HOP and AGE statistics are available 

only when you execute the DD command without an argument. 

Trace IP Route (TRACEROUTE) 

The TRACEROUTE command shows the path taken by IP packets 

between two points in the network. This path is represented by a list of 

the IP addresses of various routers that the packets pass through to 

reach their final destination. TRACEROUTE is similar to the TRACERT 

command available with Microsoft Windows®. 

TRACEROUTE can be used to: 

� Troubleshoot PowerCell over IP, as it shows the path that IP packets 

take from the NetPerformer to a particular IP address. 



Loopback Test (LT) 

� Find out how many routers separate two NetPerformer units in a 

Voice over IP application, which can help determine the cause of 

choppy voice quality. 

To execute the TRACEROUTE command: 

� Enter TRACEROUTE IP_address, or 

� Enter TRACEROUTE and enter appropriate values for the IP address, 

Timeout in milliseconds and Number of hops to trace. 


BOSTON>TRACEROUTE 192.146.35.75 

TRACEROUTE 

Tracing route to: 192.146.035.075 

Traceroute in progress... 

Hops IP address 

1 1 ms 0 ms 0 ms 005.000.003.001 

2 1 ms 1 ms 1 ms 192.146.035.010 

3 2 ms 1 ms 1 ms 192.146.035.075 

Traceroute complete 

The Loopback Test (LT) command permits troubleshooting point-topoint 

serial connections (WAN/user) on the NetPerformer unit. 

To execute the LT command: 

� Install a loopback connector (or similar device) on the port. This 

connector should loop the data back to the local console. Ensure 

that the connector you use is appropriate to the port interface type. 

Note: There is no need to install a cable on the port. 

� Enter LT at the console command prompt. 

� At the Display old loopback counters prompt, enter YES to view the 

latest loopback test results, or NO to pass to the next question. 

� Select the Port number that you want to test. 

� Set the LOOP Type to MANUAL if you want the port to send a frame, 

wait for the echo and validate the result. Set the LOOP Type to 

ECHO if you want the port to send back all frames that it receives. 

� Several port parameters are presented for configuration. These are 

required since the NetPerformer cannot access regular port 

parameter values during a loopback test. 

� If in ECHO mode, specify the LOOP Time Duration for Echo (sec). 

� If in MANUAL mode, specify the LOOP Number of frames to send. 

� Enter the LOOP Length, which is the number of bytes to be sent 

from each frame. If a frame is longer than the length you specify, 

only the first part of the frame will be sent. 



� Specify the LOOP Timeout in milliseconds, which is the maximum 

delay before the frame will be received back at the port. The default 

value, 1000, is sufficient for a simple test with a low number of 

frames. 

� Set LOOP Background to YES if you want the test to be executed in 

the background. Enter NO to have the test results appear on the 

screen as the test is being executed. A new row of data will be 

displayed every 5 seconds for the duration of the test. 

� If the loopback is in background mode, enter the Number of test 

repetitions. 

Here are examples of how the LT command is started in MANUAL mode, 

stopped before normal termination, and the test results displayed: 

CHICAGO>LT 

LOOPBACK TEST 

LOOP Display old loopback counters (NO/YES,def:NO) ? NO 

Port number (1/2/3,def:1) ? 1 

LOOP Type (MANUAL/ECHO,def:MANUAL) ? MANUAL 

LOOP Protocol mode (SYNC/ASYNC,def:SYNC) ? SYNC 

LOOP Interface (DCE-RS232,def:DCE-RS232) ? 

LOOP Clocking mode (INTERNAL/EXTERNAL,def:INTERNAL) ? 

LOOP Speed (bps) (1200-2000000,def:1200) ? 

LOOP Coding (NRZ/NRZI,def:NRZ) ? 

LOOP Idle (MARK/FLAG,def:MARK) ? 

LOOP Number of frames to send (1-1000,def:1) ? 25 

LOOP Length (2-4096,def:2) ? 

LOOP Timeout in milliseconds (0-1000000,def:1000) ? 

LOOP Background (NO/YES,def:NO) ? YES 

LOOP Number of test repetitions (1-20,def:1) ? 2 

CHICAGO>LT 

LOOPBACK TEST 

LOOP Display background (NO/YES,def:NO) ? 

LOOP Stop the loopback function (NO/YES,def:NO) ? YES 

 

CHICAGO>LT 

LOOPBACK TEST 

LOOP Display old loopback counters (NO/YES,def:NO) ? YES 

LOOPBACK to Port #1 

Time Tx Rx TimeoutTx TimeoutRx Error MinResp MaxResp MeanResp 

======= ==== ==== ========= ========= ===== ======= ======= ======== 

5.009 4 0 4 0 0 0.000 0.000 0.000 

10.034 10 0 9 0 0 0.000 0.000 0.000 

15.059 15 0 14 0 0 0.000 0.000 0.000 

20.084 20 0 19 0 0 0.000 0.000 0.000 

Port number (1/2/3,def:1) ? 

 

Here is an example how the LT command is started in ECHO mode: 

BOSTON>LT 

LOOPBACK TEST 

LOOP Display old loopback counters (NO/YES,def:NO) ? NO 

Port number (1/2/3,def:1) ? 1 

LOOP Type (MANUAL/ECHO,def:MANUAL) ? ECHO 

LOOP Protocol mode (SYNC/ASYNC,def:SYNC) ? ASYNC 

LOOP Interface (DCE-RS232,def:DCE-RS232) ? 

LOOP Clocking mode (def:ASYNC) ? 

LOOP Speed (bps) (1200-115200,def:1200) ? 

LOOP Time Duration for Echo (sec) (1-3600,def:60) ? 

The port is now in echo mode and if you are in RELAY mode 

Press CTRL/Z three times to exit 



PING Remote Unit (PING) 

The Ping Remote Unit (PING) command pings any NetPerformer units or 

IP devices to determine if they are still alive, that is, responding to the 

ping. This can be used to test the current status of gateway/router 

connections. To execute this command: 

� Enter PING at the console command prompt. 

� At the Display old PING counters prompt, enter YES to view the 

latest PING results, or NO to pass to the next question. 

� Select the ping type: 

� CR: to send a ping along PowerCell (PVCR) routes. You will be 

requested to specify the PING destination. Enter the Unit name of 

the destination NetPerformer unit. 

� IP: to send a ping via other routers. You will be requested to 

specify the PING destination (an IP address), Source IP address 

and PING length (in bytes). 

� ATM: to send a ping via ATM connections. You will be requested 

to specify the PING VPI, PING VCI and PING Loopback type (END- 

TO-END or SEGMENT). 

� Enter the desired PING test duration in seconds. This is the duration 

of the entire test, including retries. 

� Specify the PING timeout in milliseconds. If no response is detected 

during this time, another ping is sent to the gateway. This cycle will 

continue until either a response is received or the configured test 

duration runs out. 

� Set the Delay between PINGs in milliseconds to the minimum delay 

required between each ping. 

� Set Background to YES if you want the ping to be performed in the 

background. Enter NO to have the ping results appear on the screen 

as the ping is being executed. A new row of data will be displayed 

every 5 seconds for the duration of the test. 

� If the ping is in BACKGROUND mode, enter the Number of test 

repetitions. 



Here is an example of pinging a PowerCell address (CR option): 

BOSTON>PING 

PING REMOTE UNIT 

Display old PING counters (NO/YES,def:NO) ? YES 

PING to: 000.000.000.000 

Time Transmit Receive Timeout Error MinResp MaxResp MeanResp 

6.030 5 0 5 0 0.000 0.000 0.000 

PING Type (IP/CR/ATM,def:IP) ? CR 

PING destination (def:) ? CHICAGO 

PING test duration in seconds (0-1000000,def:5) ? 

PING timeout in milliseconds (0-1000000,def:1000) ? 

Delay between PINGs in milliseconds (0-1000000,def:100) ? 

Background (NO/YES,def:NO) ? 

Ping in progress... 

PING to: CHICAGO 


5.005 30 29 0 0 0.066 0.071 0.070 

6.030 30 30 0 0 0.066 0.071 0.070 

Here is an example of pinging an IP address: 

BOSTON>PING 


Display old PING counters (NO/YES,def:NO) ? NO 

PING Type (IP/CR/ATM,def:IP) ? IP 

PING destination (def: ) ? 128.129.0.1 

Source IP address (def:128.128.000.001) ? 

PING length (0-4096,def:64) ? 






PING to: 128.129.000.001 


5.005 30 29 0 0 0.041 0.071 0.069 

5.029 30 30 0 0 0.041 0.071 0.069 

Here is an example of pinging an ATM connection: 

BOSTON>PING 


Display old PING counters (NO/YES,def:NO) ? 

PING Type (IP/CR/ATM,def:IP) ? ATM 

PING VPI (0-255,def:0) ? 10 

PING VCI (0-65535,def:0) ? 10 

PING Loopback type (END-TO-END/SEGMENT,def:END-TO-END) ? 






PING to: VPI# 10 VCI# 10 


5.005 30 29 0 0 0.066 0.071 0.070 

6.030 30 30 0 0 0.066 0.071 0.070 

PING Command 

The PING command has been modified in NetPerformer V9.2.0 and 

NetPerformer SIP VoIP option to support host domain names in addition 

to IP addresses. To PING a host domain name: 

� Enter the host name with the PING command at the NetPerformer 

console command prompt, or 



� Define the PING destination parameter of the PING command with a 

host name instead of an IP address. When displaying the PING 

results, the NetPerformer interprets the domain name in standard 4byte 

IP address notation. 

Here is an example of pinging a domain name by entering the host 

name with the PING command at the NetPerformer console command 

prompt: 

CHICAGO>PING WWW.VERSO.COM 



PING to: 010.001.001.005 


5.005 26 25 0 0 0.097 0.106 0.098 

6.030 26 26 0 0 0.097 0.106 0.098 

Here is an example of pinging a domain name by defining the PING 

destination parameter of the PING command with a host name instead 

of an IP address: 

CHICAGO>PING 


Display old PING counters (NO/YES,def:NO) ? 

PING Type (IP/CR/ATM,def:IP) ? 

PING destination (def:5.0.1.1) ? WWW.VERSO.COM 

Source IP address (def:176.012.037.081) ? 

PING length (0-4096,def:64) ? 






PING to: 010.001.001.005 


5.005 26 25 0 0 0.097 0.120 0.098 

6.030 26 26 0 0 0.097 0.120 0.098 

Start Test Tone (STARTTONE) 

The Start Test Tone (STARTTONE) command is used to send a tone 

frequency on a NetPerformer voice port (phone line) for testing 

purposes. 


� Enter STARTTONE at the console command prompt. 


� Select the Frequency (Hz) of the tone. 

� Select the Amplitude (dBm) of the tone. 


BOSTON>STARTTONE 

START TEST TONE 


Frequency (Hz) > (300/404/1004/2713/2804/3300,def:300) ? 

Amplitude (dBm) > (0/-5/-10/-15/-20/-25/-30,def:0) ? 



When STARTTONE is executed a tone is sent over the NetPerformer 

phone line specified by the slot number, as long as the voice port is not 

hanged up. 

Note: Execute the STARTTONE command again to change the tone 

Frequency and/or Amplitude that is sent on the phone line. If the 

Amplitude is set to 0, no tone is generated. 




Example Applications 

This chapter presents seven different examples which guide you 

through NetPerformer setup in a variety of scenarios: 

� IP routing application (page 246) 

� Point-to-point transparent data application (page 250) 

� Combined data and voice over T1 application (page 254) 

� Integrated voice and LAN application with link backup (page 260) 

� Integrated voice and SNA over Frame Relay application (page 265) 

� Analog and digital voice integration over IP, using NetPerformer 

PowerCell (page 277) 

� Analog and digital voice integration over IP, using SIP (page 285). 

Care has been taken to provide as much detail as possible for easy 

configuration of each of the required components. Details on the 

configuration of each network component are provided in Chapter 3, 

Configuration. If you are not already familiar with NetPerformer console 

operation, refer to Chapter 2, Getting Started. 


5

Example Applications Doc. No. 620-0120-001 

IP Routing Application 

Ethernet 

Central Site 


SDM-9500(9585) 

128.128.0.1 

LOS ANGELES 

Note: This application is supported by both the standard NetPerformer 

and the NetPerformer SIP VoIP option. 

In this application: 

� The central site server in Los Angeles communicates with remote 

sites in Boston and Chicago using IP routing over a Frame Relay 

network. 

� The Ethernet port on each NetPerformer unit connects to the IP 

Server/Client equipment. 

� A serial data port on each unit is configured with the FR-USER 

protocol, permitting transmission of the IP traffic over the Frame 

Relay network. 

� Each DLCI address is assigned to a unique PVC at the corresponding 

site. 

Port 1 

Fr-User 

DLCI 100 

DLCI 101 

IP/ 

Frame Relay 

Figure 11 IP Routing Application Diagram 

Port 1 


Port 1 



SDM-9360 


SDM-9380 

128.129.0.1 


DLCI 50 

DLCI 40 

Remote Sites 

BOSTON 

CHICAGO 

Ethernet 

128.130.0.1 

Ethernet


Central Site Configuration 

The following are essential parameter values for configuring the SDM- 

9585 unit located at the central site in Los Angeles: 

GLOBAL> Unit name...............................LOS ANGELES 



GLOBAL> Unit location...........................HEAD OFFICE 

PORT ETH> Protocol..............................ETH AUTO 

PORT ETH> Link integrity........................YES 

PORT ETH> MAC address...........................000000000000 

PORT ETH> DHCP..................................DISABLE 

PORT ETH> IP address #1.........................128.128.000.001 

PORT ETH> Subnet mask #1 (number of bits).......0 {255.255.000.000} 



PORT ETH> Frame size............................1500 

PORT ETH> IP RIP................................V1 

PORT ETH> IP RIP TX/RX..........................DUPLEX 

PORT #1> Protocol...............................FR-USER 

PORT #1> Port speed (bps).......................256000 

PORT #1> Fallback speed.........................DISABLE 

PORT #1> Interface..............................DTE-V35 

PORT #1> Clocking mode..........................EXTERNAL 

PORT #1> Management interface...................LMI 

IP> Router......................................ENABLE 

PVC #1> Mode....................................PVCR 

PVC #1> Port....................................1 

PVC #1> DLCI address............................100 

PVC #1> Committed Information rate..............112000 

PVC #1> Burst Information rate..................128000 

PVC #1> Remote unit name........................ 

PVC #1> Type....................................DEDICATED 

PVC #1> Timeout (msec)..........................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)............0 {000.000.000.000} 

PVC #1> NAT enable..............................NO 

PVC #1> IP RIP..................................V1 

PVC #1> IP RIP TX/RX............................DUPLEX 

PVC #2> Mode....................................PVCR 

PVC #2> Port....................................1 









PVC #2> IP address..............................000.000.000.000 



PVC #2> IP RIP..................................V1 




Remote Site Configuration 


9360 unit located at the remote site in Boston: 

GLOBAL> Unit name...............................BOSTON 



GLOBAL> Unit location...........................EASTERN BRANCH 


PORT ETH> LAN speed (mbps)......................AUTO 

















PVC #1> Mode....................................PVCR 

PVC #1> Port....................................1 









PVC #1> IP address..............................000.000.000.000 



PVC #1> IP RIP..................................V1 





9380 unit located at the remote site in Chicago: 




GLOBAL> Unit location...........................CENTRAL BRANCH 



















PVC #1> Mode....................................PVCR 

PVC #1> Port....................................1 









PVC #1> IP address..............................000.000.000.000 



PVC #1> IP RIP..................................V1 




Point-to-point Transparent Data Application 

Ethernet 

2 

3 

Central Site 


SDM-9500(9585) 

LOS ANGELES 




� Non-Frame Relay point-to-point equipment is able to take 

advantage of Frame Relay transmission via the NetPerformer. 

� The central site router in Los Angeles communicates with routers at 

the remote sites in Boston and Chicago using HDLC over the Frame 


� At the end points, the non-Frame Relay equipment is connected via 

single (remote) or dual (central site) transparent ports. 


protocol, permitting transmission of the HDLC data over the Frame 


� Each DLCI address is assigned to a unique PVC at the corresponding 

site. 

Port 1 


DLCI 100 

DLCI 101 

IP/ 

Frame Relay 

Port 1 


Port 1 


Figure 12 Point-to-point Transparent Data Application Diagram 


DLCI 50 

DLCI 40 

Remote Sites 


SDM-9360 

BOSTON 


SDM-9380 

CHICAGO 

2 

2 

Ethernet 

Ethernet















PORT #2> Protocol...............................HDLC 


PORT #2> Fallback speed.........................ENABLE 

PORT #2> Interface..............................DCE-V35 

PORT #2> Clocking mode..........................INTERNAL 

PORT #2> CRC encoding...........................NRZ 

PORT #2> Modem control signal...................STATIC 

PORT #2> Transmission start level...............AUTO 

PORT #2> Idle...................................FLAG 

PORT #2> Frame delay (msec).....................0.0 

PORT #2> Remote unit............................BOSTON 

PORT #2> Class..................................3 

PORT #2> Remote port number.....................2 









PORT #3> Idle...................................FLAG 


PORT #3> Remote unit............................CHICAGO 

PORT #3> Class..................................3 


PVC #1> Mode....................................PVCR 

PVC #1> Port....................................1 









PVC #2> Mode....................................PVCR 

PVC #2> Port....................................1 
































PORT #2> Idle...................................FLAG 


PORT #2> Remote unit............................LOS ANGELES 

PORT #2> Class..................................3 


PVC #1> Mode....................................PVCR 

PVC #1> Port....................................1 































PORT #2> Idle...................................FLAG 



PORT #2> Class..................................3 


PVC #1> Mode....................................PVCR 

PVC #1> Port....................................1 











Combined Data and Voice over T1 Application 

PBX 

Slot 2 

T1 




� The voice connection is set up with PREDEFINED line activation on 

the standard NetPerformer. On the NetPerformer SIP VoIP option, 

use AUTODIAL line activation. 

� The central site unit (in Los Angeles) communicates with two remote 

NetPerformer units in Boston and Chicago using a T1 line. 

� The Los Angeles and Boston units are equipped with T1 interface 

cards. The Chicago unit is an SDM-8200 with internal DSU, 

providing a single DS0 channel. 

� The connection from Los Angeles to Boston includes voice-over-WAN 

support at 384 Kbps, using one channel configured at both sites with 

6 timeslots. 

� An additional 64 Kbps data link is provided between Los Angeles and 

Chicago over time slot 7. 

� All channels participating in the network are configured with the 

FR-USER protocol, permitting transmission between the three units 

over Frame Relay via the PSTN network and a Frame Relay switch. 

Central Site 


SDM-9500(9585) 

LOS ANGELES 

� Time slots 1-6 configured to Boston 

� Time slot 7 configured to Chicago 

� Time slots 8-22 used by PBX for local calls 

(PASSTHRU) 

� Time slots 23-24 used by PBX for Predefined 

voice connections to Boston 

Slot 1 

T1 

PSTN 

DLCI 100 

DLCI 101 

Frame Relay 

T1 


DSO 


Figure 13 Combined Data and Voice over T1 Application Diagram 

Remote Sites 


SDM-9360 

BOSTON 


SDM-8200 

CHICAGO 


DLCI 50 

DLCI 40









T1 in Slot 1 

PORT #100> Status...............................ENABLE 

PORT #100> Clock recovery.......................ENABLE 

PORT #100> Digital port clock source............1 

PORT #100> Signaling mode.......................NONE 

PORT #100> Pcm encoding law.....................MU-LAW 

PORT #100> Idle code............................7F 

PORT #100> Zero suppression mode................B8ZS 

PORT #100> Gain limit...........................-30DB 

PORT #100> Framing mode.........................ESF 

PORT #101> Protocol.............................FR-USER 

PORT #101> Timeslot.............................1 


PORT #101> DS0 speed (bps)......................64000 

PORT #101> Management interface.................LMI 


PORT #102> Timeslot.............................7 




PORT #103> Protocol.............................PASSTHROUGH 

PORT #103> Timeslot.............................8 


PORT #103> Partner channel......................203 


PORT #104> Timeslot.............................9 




PORT #105> Timeslot.............................10 




PORT #106> Timeslot.............................11 




PORT #107> Timeslot.............................12 




PORT #108> Timeslot.............................13 




PORT #109> Timeslot.............................14 




PORT #110> Timeslot.............................15 



(continued next page) 



: 


PORT #111> Timeslot.............................16 




PORT #112> Timeslot.............................17 




PORT #113> Timeslot.............................18 




PORT #114> Timeslot.............................19 




PORT #115> Timeslot.............................20 




PORT #116> Timeslot.............................21 




PORT #117> Timeslot.............................22 



T1 in Slot 2 


PORT #200> Clock recovery.......................DISABLE 


PORT #200> Signaling mode.......................ROB BIT 






PORT #201> Protocol.............................ACELP-CN 

PORT #201> Timeslot.............................23 

VOICE #201> DSP packets per frame...............1234 

VOICE #201> 8K packetization selection (Y/N)....YNNN 


VOICE #201> 6K packetization selection (Y/N)....NNNNN 

VOICE #201> Comfort noise level.................0 

VOICE #201> Signaling type......................IMMEDIATE START 

VOICE #201> Local inbound voice level (db)......0 

VOICE #201> Local outbound voice level (db).....0 

VOICE #201> Priority Level......................0 

VOICE #201> Echo canceler.......................ENABLE 

VOICE #201> Double talk threshold (db)..........6 

VOICE #201> Pulse frequency (pps)...............10 

VOICE #201> Activation type.....................PREDEFINED 

VOICE #201> Link down busy......................NO 

VOICE #201> TONE type:..........................DTMF 

VOICE #201> TONE regeneration:..................255 

VOICE #201> TONE ON (msec)......................100 

VOICE #201> TONE OFF (msec).....................100 

VOICE #201> Pulse make/break ratio..............34 

VOICE #201> Fax/modem relay.....................FAX 

VOICE #201> Maximum fax/modem rate..............14400 

VOICE #201> Remote unit.........................BOSTON 

VOICE #201> Remote port number..................201 




: 


PORT #202> Timeslot.............................24 


VOICE #202> 8K packetization selection (Y/N)...YNNN 


VOICE #202> 6K packetization selection (Y/N)...NNNNN 





















PORT #203> Timeslot.............................8 




PORT #204> Timeslot.............................9 




PORT #205> Timeslot.............................10 




PORT #206> Timeslot.............................11 




PORT #207> Timeslot.............................12 




PORT #208> Timeslot.............................13 




PORT #209> Timeslot.............................14 




PORT #210> Timeslot.............................15 




PORT #211> Timeslot.............................16 






: 


PORT #212> Timeslot.............................17 




PORT #213> Timeslot.............................18 




PORT #214> Timeslot.............................19 




PORT #215> Timeslot.............................20 




PORT #216> Timeslot.............................21 




PORT #217> Timeslot.............................22 



PVC #1> Mode....................................PVCR 

PVC #1> Port....................................101 









PVC #2> Mode....................................PVCR 

PVC #2> Port....................................102 


















T1 in Slot 1 











PORT #101> Timeslot.............................1 




FXS in Slot 2 



VOICE #201> Protocol............................ACELP-CN 











VOICE #201> Ring type...........................USA 











VOICE #201> Remote unit.........................LOS ANGELES 





: 

























PVC #1> Mode....................................PVCR 

PVC #1> Port....................................101 









The SDM-8200 at the Chicago site is configured with one DS0 channel 

to the Los Angeles unit at 64 Kbps. For configuration details, consult 

the SDM-8200 Quick Setup Guide. 

Integrated Voice and LAN Application with 

Link Backup 




� The voice connection is set up with PREDEFINED line activation on 

the standard NetPerformer. On the NetPerformer SIP VoIP option, 

use AUTODIAL line activation. 

� The NetPerformer transmits voice and LAN data across a WAN link 

using Cell Relay. 

� On each NetPerformer, one serial data port is configured with the 

PVCR protocol for WAN link functions. 

� An integrated ISDN-BRI S/T interface is installed on each 

NetPerformer unit for link backup. 



PBX 

� IP data is routed across the Ethernet LAN port on each NetPerformer 

unit. 

� Attached voice equipment includes a PBX at each site with a trunkside 

E&M connection, and an FXS connection to a “hot line” 

telephone. 

� The two hot line telephones use PREDEFINED line activation 

(AUTODIAL on the NetPerformer SIP VoIP option). 

E&M 

Slot 2 

128.128.0.1 

Ethernet 

Figure 14 Integrated Voice and LAN with Link Backup Application Diagram 

Local Site Configuration 

Predefined 

Local Site Remote Site 


SDM-9380 

LOS ANGELES 

Call-Bkup 

Slot 1 

1 PVCR 1 

ISDN-BRI 

Answer 

Slot 1 


SDM-9360 

BOSTON 

E&M 

Slot 2 

128.129.0.1 

The following are essential parameter values for configuring the local 

SDM-9585 unit located in Los Angeles: 



Ethernet 
















PORT #1> Protocol...............................PVCR 




PORT #1> Mode...................................DEDICATED 

PORT #1> IP address.............................000.000.000.000 

PORT #1> Subnet mask (number of bits)...........0 {000.000.000.000} 

PORT #1> IP RIP.................................V1 

PORT #1> IP RIP TX/RX...........................DUPLEX 

PBX


: 

BRI S/T in Slot 1 




PORT #100> Signaling mode.......................5ESS 

PORT #100> CCS side.............................USER 

PORT #100> Channel selection mode...............PREFERRED 

PORT #100> Local number.........................8188714539 

PORT #100> Local subaddress..................... 

PORT #100> Local SPID 1......................... 


PORT #100> Terminal Endpoint Identifier (TEI)...AUTOMATIC 


PORT #101> Protocol.............................PVCR 

PORT #101> Timeslot.............................1 



PORT #101> Mode.................................CALL-BKUP 

PORT #101> Backup termination mode..............AUTOMATIC 

PORT #101> Delay before call activation (sec)...10 

PORT #101> Delay before call deactivation (sec) 120 

PORT #101> Call activation timer (sec)..........30 

PORT #101> Port to back.........................ANY 

PORT #101> IP address...........................000.000.000.000 

PORT #101> Subnet mask (number of bits).........0 {000.000.000.000} 

PORT #101> IP RIP...............................V1 

PORT #101> IP RIP TX/RX.........................DUPLEX 

PORT #101> OSPF.................................DISABLE 

PORT #101> IP multicast active..................NO 

PORT #101> IP multicast protocol................NONE 

PORT #101> NAT enable...........................NO 

PORT #101> IPX RIP..............................DISABLE 

PORT #101> IPX SAP..............................DISABLE 

PORT #101> IPX network number...................00000000 

PORT #101> Compression..........................YES 

PORT #101> Remote unit name.....................BOSTON 

E&M in Slot 2 









VOICE #201> E&M signaling type..................IMMEDIATE START 

VOICE #201> Analog E&M type.....................4 WIRE 

VOICE #201> TE timer (sec)......................0 






















: 

FXS in Slot 3 




























PHONE> #1> Remote unit..........................BOSTON 

PHONE> #1> Next hop.............................LOS ANGELES 

PHONE> #1> Cost.................................0 

PHONE> #1> Dialer type..........................ISDN 

PHONE> #1> Remote number........................4198675222 

PHONE> #1> Remote subaddress.................... 

PHONE> #1> Local number.........................8188714539 

PHONE> #1> Local subaddress..................... 

PHONE> #1> Number of links......................1 

The following are essential parameter values for configuring the remote 

SDM-9360 unit located in Boston: 



















: 

PORT #1> Protocol...............................PVCR 




PORT #1> Mode...................................DEDICATED 

PORT #1> IP address.............................000.000.000.000 

PORT #1> Subnet mask (number of bits)...........0 {000.000.000.000} 

PORT #1> IP RIP.................................V1 

PORT #1> IP RIP TX/RX...........................DUPLEX 















PORT #101> Timeslot.............................1 



PORT #101> Mode.................................ANSWER 



PORT #101> IP RIP...............................V1 


E&M in Slot 2 









VOICE #201> E&M signaling type..................IMMEDIATE START 

VOICE #201> Analog E&M type.....................4 WIRE 

VOICE #201> TE timer (sec)......................0 





















Integrated Voice and SNA over Frame Relay 

Application 

Note: This application is more suitable for the standard NetPerformer. 


� The voice connections are set up with PREDEFINED and SWITCHED 

line activation on the standard NetPerformer. 

� The NetPerformer transmits voice, SNA/SDLC and transparent HDLC 

data over a Frame Relay network. 

� The IBM Host in Los Angeles is accessed from an Ethernet LAN, 

which connects to an Ethernet port on the Central Site 


� At the remote sites, the SNA/SDLC data is directed to IBM 

controllers via primary SDLC ports on the NetPerformer units. 

� HDLC data from an asynchronous multiplexer in Los Angeles is 

transmitted to another in Chicago via transparent data connections. 


protocol, permitting transmission of all traffic types over the Frame 

Relay network. The required DLCI addresses are assigned to PVCs at 

each site. 

� Both predefined and switched voice transmissions are integrated 

with the rest using FXS voice ports. 

� A backup link using an integrated ISDN-BRI S/T interface is installed 

between the three sites, allowing Cell Relay to take over if the 

Frame Relay network should fail. The calls are initiated by the 

remote sites, and share one interface at the central site. 



Central Site 

SNA 

Host 

LLC 

Ethernet 

Multiplexer 

Switched 

FXS FXS FXS FXS 

LOS ANGELES 

2 

HDLC 

1 


Slot 1 

Switched 

Switched 

300 

FXS 


2 

P-SDLC 

1 


Remote Sites 

Figure 15 Integrated Voice and SNA over Frame Relay Application Diagram 

100 

FXS CHICAGO 

Multiplexer 

Predefined 

Frame Relay 

1 


200 

Slot 1 

3 

HDLC 

ISDN-BRI 


BOSTON 

Slot 1 

Switched 

2 SNA Controller 

P-SDLC 

Slot 3 

P-SDLC 

SNA Controller













GLOBAL> Default IP address......................000.000.000.000 

GLOBAL> Default IP mask (number of bits)........0 {000.000.000.000} 

GLOBAL> Default gateway.........................000.000.000.000 

GLOBAL> SNMP trap: IP address #1................000.000.000.000 




GLOBAL> Frame relay status change trap..........DISABLE 

GLOBAL> Watch power supplies and fans...........NONE 

GLOBAL> Local unit DLCI address.................0 

GLOBAL> Extension number (no. of digits)........2 

GLOBAL> Country code............................1 

GLOBAL> Jitter buffer (msec)....................40 
















PORT #2> Idle...................................FLAG 


PORT #2> Remote unit............................CHICAGO 

PORT #2> Class..................................3 


















: 


PORT #101> Timeslot.............................1 











PORT #101> IP RIP...............................V1 










PORT #101> Remote unit name.....................BOSTON 


PORT #102> Timeslot.............................2 











PORT #102> IP RIP...............................V1 










PORT #102> Remote unit name.....................CHICAGO 

FXS in Slot 2 






























: 














VOICE #202> Activation type.....................SWITCHED 









VOICE #202> Hunt Group active...................NONE 

VOICE #202> Delete digits.......................0 

VOICE #202> Port extension number...............22 

PU #1> Operating mode...........................LLC-LINKS 



PU #1> LLC Role.................................SEC 

PU #1> LLC destination address..................400000000001 

PU #1> LLC source SAP...........................04 

PU #1> LLC destination SAP......................04 

PU #1> LLC retransmission timeout (msec)........3000 

PU #1> LLC maximum successive retries...........10 

PU #1> LLC transmission window size.............7 

PU #1> LLC dynamic window ......................10 

PU #1> LLC frame size...........................512 


PU #1> Class....................................2 


PU #1> XID support..............................AUTO 




PU #2> LLC Role.................................SEC 


PU #2> LLC source SAP...........................08 

PU #2> LLC destination SAP......................08 







PU #2> Class....................................2 






PU #3> LLC Role.................................SEC 


PU #3> LLC source SAP...........................0C 

PU #3> LLC destination SAP......................0C 






PU #3> Remote unit..............................CHICAGO 

PU #3> Class....................................2 






: 

PHONE> #1> Remote unit..........................BOSTON 


PHONE> #1> Cost.................................0 







PHONE> #2> Remote unit..........................CHICAGO 


PHONE> #2> Cost.................................0 







PVC #1> Mode....................................PVCR 

PVC #1> Port....................................1 




PVC #1> Remote unit name........................BOSTON 





PVC #2> Mode....................................PVCR 

PVC #2> Port....................................1 




PVC #2> Remote unit name........................CHICAGO 






MAP #1> Destination name........................CHICAGO 

MAP #1> Destination extension number source.....USER 

MAP #1> Destination extension number............NONE 



MAP #2> Destination name........................BOSTON 




































PORT #2> Protocol...............................P-SDLC 








PORT #2> Idle...................................MARK 

PORT #2> SDLC duplex mode.......................HALF 















PORT #101> Timeslot.............................1 







: 


PORT #102> Timeslot.............................2 











PORT #102> IP RIP...............................V1 










PORT #102> Remote unit name.....................CHICAGO 

FXS in Slot 2 























































: 

DUAL SERIAL in Slot 3 

PORT #301> Protocol.............................P-SDLC 

PORT #301> Port speed (bps).....................56000 

PORT #301> Interface............................DCE-V35 

PORT #301> Clocking mode........................INTERNAL 

PORT #301> Idle.................................MARK 

PORT #301> SDLC duplex mode.....................HALF 




PU #1> SDLC port................................2 

PU #1> SDLC address.............................C1 





PU #1> Remote unit..............................LOS ANGELES 

PU #1> Class....................................2 


PU #1> XID support..............................YES 




PU #2> SDLC port................................301 







PU #2> Class....................................2 



PHONE> #1> Remote unit..........................CHICAGO 

PHONE> #1> Next hop.............................BOSTON 

PHONE> #1> Cost.................................0 







PVC #1> Mode....................................PVCR 

PVC #1> Port....................................1 




PVC #1> Remote unit name........................LOS ANGELES 





PVC #2> Mode....................................PVCR 

PVC #2> Port....................................1 

















: 


MAP #2> Destination name........................LOS ANGELES 

































PORT #2> Protocol...............................P-SDLC 








PORT #2> Idle...................................MARK 

PORT #2> SDLC duplex mode.......................HALF 









PORT #3> Idle...................................FLAG 



PORT #3> Class..................................3 





: 















PORT #101> Timeslot.............................1 






PORT #101> IP RIP...............................V1 











PORT #102> Timeslot.............................2 






PORT #102> IP RIP...............................V1 










FXS in Slot 2 






: 






















































PU #1> SDLC port................................2 







PU #1> Class....................................2 






: 

PVC #1> Mode....................................PVCR 

PVC #1> Port....................................1 




PVC #1> Remote unit name........................LOS ANGELES 





PVC #2> Mode....................................PVCR 

PVC #2> Port....................................1 



















Analog and Digital Voice Integration over IP, 

Using NetPerformer PowerCell 

Note: This application is more suitable for the standard NetPerformer. 


� IP routing between the NetPerformer units in Los Angeles and 

Boston is carried out through the NetPerformer integrated router 

function, using PowerCell over a dedicated link. 

� IP routing from Boston to Chicago is done via an integrated 

NetPerformer connection to an external Cisco router using a PPP 

link. 

� The PowerCell connection between the Boston and Chicago 

NetPerformer units is carried out over IP though the Cisco router. 

� Voice connections between Los Angeles and Chicago are switched 

from IP to Frame Relay and vice-versa. 



PBX 

Central Site 

Slot 2 

T1 

LOS ANGELES 

128.128.0.1 

Ethernet 

Slot 1 

T1 

Figure 16 Analog and Digital Voice Integration over IP Using NetPerformer 

PowerCell: Application Diagram 


PVCR 

768 Kbps 





IP 

PPP 

768 Kbps 

10.1.1.2 

255.255.255.0 

Slot 1 


with PVCR/IP 

Slot 2 

FXS 

T1 

10.1.1.1 

BOSTON 

128.129.0.1 

255.255.255.0 

Ethernet 

External 

Router 

128.130.0.1 

Ethernet 

Remote Sites 

PVCR/IP 

128.130.0.100 

CHICAGO 

Slot 2 

FXS 
































PORT ETH> IP RIP TX/RX..........................DUPLEX


: 

T1 in Slot 1 











PORT #101> Timeslot.............................1 



PORT #101> Mode.................................DEDICATED 



PORT #101> IP RIP...............................V1 


T1 in Slot 2 











PORT #201> Timeslot.............................1 





























: 


PORT #202> Timeslot.............................2 



























































GLOBAL> Enable voice/fax log....................YES 

GLOBAL> Dial timer (sec)........................2 

GLOBAL> High priority voice class...............YES 

GLOBAL> Global CIR for FR over IP...............768000 

GLOBAL> Timer in ms for FR over IP..............50 




: 












T1 in Slot 1 











PORT #101> Timeslot.............................1 



PORT #101> Mode.................................DEDICATED 



PORT #101> IP RIP...............................V1 










PORT #101> Remote unit name.....................LOS ANGELES 

PORT #102> Protocol.............................PPP 

PORT #102> Timeslot.............................13 



PORT #102> CRC encoding.........................NRZ 

PORT #102> Modem control signal.................STATIC 

PORT #102> Transmission start level.............AUTO 

PORT #102> Idle.................................FLAG 

PORT #102> Frame delay (msec)...................0.0 



PORT #102> IP RIP...............................V1 



PORT #102> Silent...............................SEND REQUEST 

PORT #102> Link control protocol timeout (seconds) 3 

PORT #102> Link control protocol retries, 255 = forever 255 

PORT #102> Negotiate MRU........................NO 

PORT #102> Use MRU proposed by peer.............NO 

PORT #102> Request Magic Number.................YES 

PORT #102> Accept Magic Number Request..........YES 

PORT #102> Accept Addresses Old Negotiation.....NO 

PORT #102> Request IP-Address...................NO 

PORT #102> Accept IP-Address Request............NO 

PORT #102> Remote IP-Address....................000.000.000.000 

PORT #102> PPP dial index.......................NONE 

FXS in Slot 2 






: 



























PVC #1> Mode....................................PVCR 

PVC #1> Port....................................0 









PVC #1> Broadcast group.........................NO 

PVC #1> Maximum number of voice channels........10000 

PVC #1> Maximum Voice Channels If High Priority Data 10000 

PVC #1> Frame over IP, source...................000.000.000.000 

PVC #1> Frame over IP, destination..............128.130.000.100 










EXTENDED PARAMETERS 

IP> MULTIHOMEDTYPE..............................DISABLED 



The following is the Cisco configuration located at the remote site in 

Chicago. 

Note: This is the Cisco configuration that was used by NetPerformer 

personnel when testing this example: 

Cisco#show configuration 

Using 679 out of 32762 bytes 

! 

version 11.1 

service udp-small-servers 

service tcp-small-servers 

! 

hostname Cisco 

! 

enable password **** 

! 

no ip domain-lookup 

! 

interface Ethernet0 

ip address 128.130.0.1 255.255.0.0 

interface Serial0 

ip address 10.1.1.2 255.255.255.0 

encapsulation ppp 

router rip 

network 128.128.0.0 

network 128.129.0.0 

network 128.130.0.0 

network 10.0.0.0 
























GLOBAL> Enable voice/fax log....................YES 


GLOBAL> High priority voice class...............YES 

GLOBAL> Global CIR for FR over IP...............768000 

GLOBAL> Timer in ms for FR over IP..............50 




: 










PORT ETH> IP RIP................................DISABLE 


FXS in Slot 2 





























PVC #1> Mode....................................PVCR 

PVC #1> Port....................................0 









PVC #1> Broadcast group.........................NO 

PVC #1> Maximum number of voice channels........10000 

PVC #1> Maximum Voice Channels If High Priority Data 10000 

PVC #1> Frame over IP, source...................000.000.000.000 

PVC #1> Frame over IP, destination..............128.129.000.001 











EXTENDED PARAMETERS 

IP> MULTIHOMEDTYPE..............................DISABLED 



Analog and Digital Voice Integration over IP, 

Using SIP 


Layer 


Clarent 


SIP 

Note: This application is supported by the NetPerformer SIP VoIP 

option only. 


� This IP network is built with a NetPerformer SIP VoIP unit 

communicating to Cisco routers using PPP. 

Note: If all locations used external Cisco routers, then the 

NetPerformer would just be used as a VoIP gateway transmitting IP 

traffic over the Ethernet port. 

� Voice over IP call setups are managed through a centralized 

softswitch using SIP (Session Initiation Protocol). 

� In this scenario, no PowerCell over IP connections are required to 

transport voice between NetPerformer SIP VoIP units. 

� Standard RTP and T.38 IP protocols are used to transport voice and 

fax, respectively. 

128.128.0.100 

Clarent 

Call Manager 

Figure 17 Analog and Digital Voice Integration over IP Using SIP: Application 

Diagram 


Ethernet 

IP/PPP 

SIP 

Call Setup 

For configuration of the central site Clarent softswitch, refer to the 

Clarent Command Center and Call Manager documentation. 


On-net 

VoIP 

External 

Router 

10.1.1.2 

255.255.255.0 

128.130.0.1 

Ethernet 


and VoIP Gateway 

Slot 2 

FXS 

Slot 1 BOSTON 

10.1.1.1 

255.255.255.0 

VoIP Gateway 

128.130.0.100 

CHICAGO 

128.129.0.1 

Ethernet 

Slot 2 

T1 

PBX




9360 NetPerformer SIP VoIP unit located at the remote site in Boston: 
































T1 in Slot 1 










PPP link to Chicago 


PORT #101> Timeslot.............................1 






PORT #101> Idle.................................FLAG 




PORT #101> IP RIP...............................V1 


















: 

PPP link to centralized softswitch location 


PORT #102> Timeslot.............................13 






PORT #102> Idle.................................FLAG 




PORT #102> IP RIP...............................V1 















FXS in Slot 2 



VOICE #201> Protocol............................G729A 


VOICE #201> Packetization selection (Y/N)......NYNNNNNN 

VOICE #201> Silence suppression level...........1 












VOICE #201> Fax relay...........................FAX 

VOICE #201> Maximum fax rate....................14400 

VOICE #201> Fax redundancy level................3 

VOICE #201> Fwd digits..........................NONE 



MAP #1> Digits string...........................******************* 






MAP #1> Egress hunt group ports.................201 

SIP Global> Administrative status...............ENABLE 

SIP Global> Proxy server address................128.128.0.100 

SIP Global> UDP Port............................5060 

SIP Global> Gateway ID..........................2901 

SIP Global> Server group........................BOSTON 

SIP Global> Registration........................ENABLE 

SIP Global> ANI digits.......................... 

SIP Timer> Resend INVITE........................60 

SIP Timer> Receiving ACK........................1 

SIP Timer> Disconnect (BYE or CANCEL)...........1 

SIP Retries> INVITE.............................6 

SIP Retries> BYE................................6 

SIP Retries> CANCEL.............................6 

SIP Retries> REGISTER...........................6 

SIP Retries> RESPONSE (200 OK or ERROR).........6 



The following is the Cisco configuration located at the remote site in 

Chicago. 

Note: This is the Cisco configuration that was used by NetPerformer 

personnel when testing this example: 

Cisco#show configuration 

Using 679 out of 32762 bytes 

! 

version 11.1 

service udp-small-servers 

service tcp-small-servers 

! 

hostname Cisco 

! 

enable password **** 

! 

no ip domain-lookup 

! 

interface Ethernet0 

ip address 128.130.0.1 255.255.0.0 

interface Serial0 

ip address 10.1.1.2 255.255.255.0 

encapsulation ppp 

router rip 

network 128.128.0.0 

network 128.129.0.0 

network 128.130.0.0 

network 10.0.0.0 


9380 NetPerformer EG unit located at the remote site in Chicago: 






























PORT ETH> IP RIP................................DISABLE 





: 

T1 in Slot 2 



PORT #200> Digital port clock source............INTERNAL 







PORT #201> Protocol.............................G729A 

PORT #201> Timeslot.............................1 


















VOICE #201> Fwd digits..........................ALL 

VOICE #201> Fwd type............................TONE 

VOICE #201> Fwd delay (msec)....................0 

PORT #202> Protocol.............................G729A 

PORT #202> Timeslot.............................2 


















VOICE #202> Fwd digits..........................ALL 

VOICE #202> Fwd type............................TONE 

VOICE #202> Fwd delay (msec)....................0 



MAP #1> Digits string...........................******************* 






MAP #1> Egress hunt group ports.................201-202 




: 

SIP Global> Administrative status...............ENABLE 

SIP Global> Proxy server address................128.128.0.100 

SIP Global> UDP Port............................5060 

SIP Global> Gateway ID..........................3010 

SIP Global> Server group........................CHICAGO 

SIP Global> Registration........................ENABLE 

SIP Global> ANI digits.......................... 

SIP Timer> Resend INVITE........................60 

SIP Timer> Receiving ACK........................1 

SIP Timer> Disconnect (BYE or CANCEL)...........1 

SIP Retries> INVITE.............................6 

SIP Retries> BYE................................6 

SIP Retries> CANCEL.............................6 

SIP Retries> REGISTER...........................6 

SIP Retries> RESPONSE (200 OK or ERROR).........6 


Index 

A 

Access 

SNMP 64 

TELNET 55 

user profiles 70 

Access profile 70 

ACELP-CN 141 

Activation 

of console commands 56 

of WAN link 199 

Alarms 

displaying 207 

Allocating DSPs 124 

Analog interface card 

Link parameters 150 

Analog interfaces 35 

Analog/digital voice application 277, 285 

ANSWER mode 93 

AP command 206 

Applications 

Analog/digital Voice over IP using PowerCell 

277 

Analog/digital Voice over IP using SIP 285 

basic scenarios 30 

Data/voice over T1 254 

detailed scenarios 245 

IP routing 246 

Link backup 260 

NetPerformer SIP VoIP 32 

standard NetPerformer 31 

Transparent data 250 

Voice/LAN 260 

Voice/SNA over Frame Relay 265 

ATM option 40 

configuring PVCs 111, 113, 114, 116, 117 

Global parameters 75 

B 

Backup link 93 

Example application 260 

phone profile 96 

PPP connection 188 

BOD link 95 

BOOTP/DHCP relay agent 79 

Bridge 

parameters 76 

statistics 205 

viewing addresses 207 

BSC 184 


C 

CALL-BKUP mode 93 

CALL-BOD mode 95 

CALLER ID profile 149 

Cancelling a function 56 

Capture traffic 227 

executing 230 

setting up 227 

terminating 233 

viewing 230 

CCS signaling modes 

E1 link configuration 130 

ISDN-BRI S/T link configuration 132 

T1 link configuration 128 

Channel parameters 

analog 150 

digital 133 

CHKFS command 222 

CL command 233 

Class parameters 198 

CN command 220 

Command 

entering 56 

termination of 56 

Command list 57 

Configuration 

access methods 51 

commands 59 

listing current values 214 

saving 57 

viewing changes 215 

Configuration parameters 

inventory of 62 

Connection status 206 

Connections, displaying 236 

Console 

access 70 

connecting 50 

disconnecting 59

Index Doc. No. 620-0120-001 

MONITOR access 70 

reactivating 59 

setting up 50 

Console commands 

activating 56 

listing 57 

Console conventions 56 

Console terminal 50 

cable for 52 

dialup connection 53 

direct connection 52 

remote, accessing 54 

speed 50 

Convergence, traffic 26 

COP 184 

COPY command 223 

Counters 204 

Custom error cause code 171 

Custom ring cadence 169 

Custom signaling 163 

Answered 168 

Clear Back 167 

Clear Forward 167 

Common parameters 163 

Idle 165 

Pulse Dial 165 

Ring 168 

Seizure 165 

Wink 166 

D 

DA command 207 

Data channel parameters 134 

Data traffic support 34 

DB command 205 

DBA command 207 

DC command 204 

DCFG command 215 

DCS command 209 

DD command 237 

DDCMP 182 

DDLCI command 213 

DDLCI, status 213 

DE command 204 

Dedicated WAN link 90 

Default value, selecting 56 

DEFRAG command 225 

DELETE command 224 

Destination table, for PVCR 237 

DHCP Client 

allocating IP address 85 

managing IP address 226 

DHCP command 226 

DHCP connection 51 

Dial rules 159 

DiffServ 201 

Digital channel status 209 

DIR command 222 

Disconnecting console 59 

Display Parameters command 214 

DJOURNAL command 208 

DMF command 218 

DN command 220 

DNS 

managing entries 226 

parameters 82 

DNS command 226 

DP command 214 

DPORT command 210 

DPU command 211 

DPVC command 212 

DR command 234 

DS command 206 

DSI command 216 

DSPA command 124 

DSPs 

allocating 124 

status 217 

DSVC command 214 

DT command 220 

DV command 221 

DX command 236 

Dynamic IP routing 78 


E 

E&M 154 

E&M card 150 

E1 card 128 

channel parameters 133 

EC command 233 

Egress dial rules 159 

EMF command 220 

ER command 209 

Error cause code 171 

Errors 204 

Ethernet parameters 84 

F 

Factory defaults, configuring 62 

Features, software 25, 28 

File list, displaying 222 

Filter 

for IPX SAP entries 84 

parameters 200 

Firmware 

base products 23 

displaying version 221 

licensed options 23 

FORMAT command 225


Frame length 233 

Frame Relay connections 102, 104, 106, 108, 109, 

110, 111, 113, 114, 116, 117, 118 

FR-NET 

on digital channel 137 

port 104 

FR-USER 


port 102 

FS command 62 

FTP access 81 

FXO 153 

card 150 

FXS 152 

card 150 

G 

G723 144 

G726 145 

G729 146 

G729A 147 

Global parameters 71 

ATM option 75 

for rackmount chassis 74 

H 

Hardware, viewing current 214 

HDLC 


on serial port 180 

HE command 

with FULL access 57 

with MONITOR access 70 

Help command 57 

Hunt forwarding 162 

I 

Ingress dial rules 159 

Integration 

Analog/digital voice 277, 285 

Voice/data 254 

Voice/LAN 260 

Voice/SNA 265 

Interfaces 

analog 35 

IP 

enabling 77 

routing, application example 246 

routing, dynamic 78 

static route 78 

IP address 

DHCP 85, 226 

managing, for DNS 226 

IPQOS filter 201 

IPX 

enabling 83 

routing, global characteristics 83 

routing, SAP filter 84 

ISDN connection 

CALLER ID profile 149 

phone profile 96 

ISDN-BRI S/T card 


link parameters 130 


J 

JOURNAL.TXT file 208 

L 

LAN configuration 84 

Licensed options 23 

installing 24 


Listing files 222 

Loading firmware 222 

Local unit, regaining console control 55 

Login 52 

Loopback test 238 

LT command 238 

M 

MACQOS filter 200 

MAP 

parameters, on NetPerformer SIP VoIP 157 

parameters, on standard NetPerformer 155 

viewing entries 218 

MIB, for NetPerformer 64 

categories 66 

N 

NAT 

enabling 173 


Port 176 

Rules 174 

Service 178 

Timeout 177 


NetPerformer MIB 64 

categories 66 

NetPerformer SIP VoIP 

application 32 

characteristics 39 

Network management 

using SNMP 64

Index Doc. No. 620-0120-001 

O 

OSPF 

Area parameters 121 

enabling 120 

global parameters 119 


Range parameters 122 

Virtual Link parameters 123 

P 

Parameters 

AAL1 PVC 113 

analog link 150 

analog voice channel 150 

ATMPPP PVC 117 

ATMPVCR PVC 111 

BOOTP/DHCP 79 

Bridge 76 

Broadcast PVC 110 

BSC port 184 

Class 198 

COP port 184 

Custom error cause code 171 

Custom ring cadence 169 

Custom signaling 163 

Custom signaling, Answered 168 

Custom signaling, Clear Back 167 

Custom signaling, Clear Forward 167 

Custom signaling, common 163 

Custom signaling, Idle 165 

Custom signaling, Pulse Dial 165 

Custom signaling, Ring 168 

Custom signaling, Seizure 165 

Custom signaling, Wink 166 

data channel 134 

DDCMP port 182 

digital voice channel 141 

digital voice/data channel 133 

DNS 82 

E1 link 128 

Ethernet port 84 

Filter 200 

FRF.8 PVC 114 

FR-NET port 104 

FR-USER port 102 

FTP 81 

Global 71 

Global, for ATM option 75 

Global, for rackmount chassis 74 

HDLC port 180 

Hunt forwarding 162 

IP Global 77 

IP Static 78 

IPX Filter 84 

IPX Global 83 

ISDN-BRI S/T link 130 

listing 214 

listing values 56 

MAP, on NetPerformer SIP VoIP 157 

MAP, on standard NetPerformer 155 

Multiplex PVC 109 

NAT 172 

OSPF 119 

OSPF Area 121 

OSPF Global 119 

OSPF Range 122 

OSPF Virtual Link 123 

PASSTHRU port 185 

Phone for backup links 96 

PPP port 185 

P-SDLC port 190 

PU, BAN 196 

PU, BNN 197 

PU, common 192 

PU, DLSW 195 

PU, LINKS 196 

PU, LLC 194 

PU, SDLC 193 

PVCR port 90 

PVCR PVC 106 

R-ASYNC port 183 

RFC1483 PVC 116 

RFC1490 PVC 108 

Schedule 199 

selecting values 56 

SIP Global 88 

SIP Retries 90 

SIP Timer 89 

SNMP 80 

SP port 98 

SP-Multiplex PVC 118 

S-SDLC port 190 

T1 link 125 

T-ASYNC port 182 

TELNET 80 

TIMEP 79 

Transparent PVC 111 

User 70 

User port 179 

VLAN 87 

X25 port 189 

PASSTHROUGH, on digital channel 140 

PASSTHRU, on serial port 185 

Password 52 

PCM64K 148 

Phone profile 96 

PING command 240 

PLS command 24 

Point-to-point application 250 



Port 

BSC 184 

COP 184 

DDCMP 182 

FR-NET 104 

FR-USER 102 

HDLC 180 

LAN 84 

PASSTHRU 185 

PPP 185 

R-ASYNC 183 

Satellite 98 

SNA/SDLC 190 

status 210 

T-ASYNC 182 

User 179 

WAN 90 

X25 189 

PowerCell 33 


PPP 


on serial port 185 

Prioritization 

classes 198 

traffic 197 

using DiffServ 201 

using VLAN 38 

VLAN 200 

Product 

firmware 23 

technologies 24 

PU 

BAN parameters 196 

BNN parameters 197 

Common parameters 192 

DLSW parameters 195 

LINKS parameters 196 

LLC parameters 194 

SDLC parameters 193 

status 206, 211 

PVC 

AAL1 113 

ATMPPP 117 

ATMPVCR 111 

Broadcast 110 

FRF.8 114 

Multiplex 109 

PVCR 106 

RFC1483 116 

RFC1490 108 

SP-Multiplex 118 

status 212 

Transparent 111 

PVCR 

destination table 237 


port, backup 93 

port, BOD 95 

port, WAIT-USER mode 97 


Q 

QU command 59 

R 

R-ASYNC 183 

RC command 204 

RE command 54 

Real-time statistics displays 209 

Relay to remote unit 54 

RELEASE IP address 226 

Remote unit indicator 55 

RENAME command 224 

RENEW IP address 226 

Reset counters 204 

Ring cadence 169 

Routing table, displaying 234 

RU command 59 

S 

Satellite link 98 

Satellite switching 47 

SC command 227 

Schedule 197 


SE command 60 

submenus 60 

SEC command 217 

SEI command 217 

Setup command 60 

Signaling Engine 

viewing channels 217 

viewing status 217 

SIP 39 


enabling 88 

retries 90 

timers 89 

SIP VoIP network 

setting up 49 

SkyPerformer option 44 

applications 45 

configuring ports 98 

configuring PVCs 118 

Slot, viewing 216 

SNA/SDLC connections 190, 192, 193, 194, 195, 

196, 197

Index Doc. No. 620-0120-001 

SNMP 64 

parameters 80 

using 65 

Software 

features 25, 28 

viewing current settings 214 

SP command 57 

SP port 98 

ST command 221 

Standard NetPerformer 


characteristics 33 

STARTTONE command 242 

Startup, console display 53 

Static route 78 

Statistics 

bridge 205 

hardware and software settings 214 

real-time 209 

system 203 

Status 

of connection 206 

of system 206 

STC command 230 

SVC status 214 

System statistics 203 

System status 206 

T 

T1 application 254 

T1 card 



T-ASYNC 182 

TELNET access 55, 78, 80 

Terminating a command 56 

Text-based configuration 62, 208 

TIMEP clock resynchronization 79 

TRACEROUTE command 237 

Traffic 

capturing 227 

convergence 26 

filtering 200 

handling 29 

prioritization 197 

Traffic filtering 201 

Transparent data application 250 

Transparent user port 179 

TRANSPARENT, on digital channel 140 

U 

Unit settings, viewing 214 

User parameters 70 

User port, transparent 179 

User profile 70 


V 

VC command 230 

Version, displaying 221 

Viewing log file 208 

VLAN 

configuring 87 

prioritizing 200 

support 36 

Voice channel parameters 

analog 150 

digital 141 

Voice codecs, allocating 124 

Voice Mapping Table 

on NetPerformer SIP VoIP 157 

on standard NetPerformer 155 


Voice traffic support 35 

Voice/data integration 254, 265 

Voice/LAN application 260 

Voice/SNA over Frame Relay application 265 

VoIP application 

with PowerCell 277 

with SIP 285 

W 

WAIT-USER mode 97 

WAN link 90 

scheduling activation 199 

Wildcard 

in MAP entry 155 

in SUPERMAP entry 158 

X 

X25 189

Verso Technologies Inc. 

400 Galleria Parkway, Suite 300 

Atlanta, GA 30339 

USA Document Part No. 620-0120-001 Rev. B1

NetPerformer User Guide

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?