1. Manuals
  2. Brands
  3. Inalp Networks Manuals
  4. Software
  5. SmartWare R2.00
  6. Software configuration manual

Inalp Networks SmartWare R2.00 Software Configuration Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Software
Configuration
Guide
SmartWare Release 2.00
Customer Deliverable Documentation
Part Number 80-0123
English
Revision 1.03, March 14, 2002

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the SmartWare R2.00 and is the answer not in the manual?

Questions and answers

Related Manuals for Inalp Networks SmartWare R2.00

Summary of Contents for Inalp Networks SmartWare R2.00

  • Page 1: Software Configuration

    Software Configuration Guide SmartWare Release 2.00 Customer Deliverable Documentation Part Number 80-0123 English Revision 1.03, March 14, 2002...

  • Page 3: Legal Notice

    The information provided is subject to change without notice. In no event shall Inalp Networks AG or its employees and associated companies be liable for any incidental, special, indirect or consequential damages whatsoever, including but not limited to lost profits, arising out of or related to this manual or the information contained within it, even if Inalp Networks AG has been advised of, known, or should have known, the possibility of such damages.

  • Page 4: Table Of Contents

    Table of Contents TABLE OF CONTENTS Terms and Definitions ........................... 14 Introduction ............................14 SmartWare Architecture Terms and Definitions ................. 14 Applications ............................21 Introduction ............................21 Carrier Networks..........................21 Enterprise Networks........................22 LAN Telephony ..........................23 System Overview ..........................25 Introduction ............................

  • Page 5: Table Of Contents

    Table of Contents 6.10 Create an Operator Account......................45 6.11 Create an Administrator Account....................45 6.12 Displaying the CLI Version ......................46 6.13 Display Account Information......................46 6.14 Switching to Another Account....................... 47 6.15 Checking Identity and Connected Users ..................47 6.16 End a Telnet or Console Port Session....................
  • Page 6 Table of Contents 10.11 Displaying the System Event Log ....................82 10.12 Displaying the System Reset Log....................82 10.13 Controlling Command Execution ....................83 10.14 Displaying the Checksum of a Configuration................84 IP Context Overview........................... 85 11.1 Introduction ............................85 11.2 IP Context Overview Configuration Task List................
  • Page 7 Table of Contents 14.8 Configuring Layer 2 CoS to Service Class Mapping for an Ethernet Port ......108 14.9 Adding a Receive Mapping Table Entry..................109 14.10 Adding a Transmit Mapping Table Entry .................. 109 14.11 Closing an Ethernet Port ....................... 110 Link Scheduler Configuration....................
  • Page 8 Table of Contents 17.1 Introduction ............................ 147 17.2 Basic IP Routing Configuration Task List................... 148 17.3 Configuring Static IP Routes......................148 17.4 Deleting Static IP Routes ....................... 149 17.5 Displaying IP Route Information ....................149 17.6 Examples ............................150 17.6.1 Basic Static IP Routing Example...................
  • Page 9 Table of Contents 20.8 Configure ISDN Ports........................182 20.9 Configure an ISoIP VoIP Connection..................182 20.10 Configure a H.323 VoIP Connection ................... 182 20.11 Activate CS Context Configuration ..................... 183 20.12 Example............................185 20.12.1 Configure SmartNode in an Enterprise Network............185 CS Interface Configuration ......................
  • Page 10 Table of Contents 24.1 Introduction ............................ 230 24.1.1 ISDN Reference Points......................230 24.1.2 Possible SmartNode Port Configurations ................231 24.1.3 ISDN UNI signalling......................232 24.2 Warnings ............................233 24.3 ISDN Port Configuration Task List....................233 24.4 Shutdown and Enable ISDN Ports....................233 24.5 Configure Common BRI and PRI Parameters ................
  • Page 11 Table of Contents 28.1 Simple Network Management Protocol (SNMP) ..............275 28.1.1 Background..........................275 28.1.2 SNMP Basic Components ..................... 275 28.1.3 SNMP Basic Commands ....................... 276 28.1.4 SNMP Management Information Base (MIB) ..............276 28.1.5 Network Management Framework ..................276 28.2 Identification of the SmartNode 1000 and 2000 series via SNMP ...........

  • Page 12: About This Guide

    About This Guide ABOUT THIS GUIDE Objectives The objective of SmartWare Software Configuration Guide is to provide information concerning the software configuration and setting into service of SmartNode devices and their interface cards. The aim is to enable you to install such devices, alone or under supervision. For detailed descriptions of the commands in the SmartWare Revision 2.00 command set, see the SmartWare Command ReferenceGuide.

  • Page 13: How To Read This Guide

    Chapter 11, “IP Context Overview” and • Chapter 20, “CS Context Overview” We at Inalp Networks AG, hope you find this guide useful, whether you are a novice or professional working with SmartNode devices and SmartWare responsible for convergent telephony and networking solutions.

  • Page 14: Terms And Definitions

    Terms and Definitions 1 TERMS AND DEFINITIONS This chapter contains the terms and their definitions that are used throughout the Software Configuration Guide for SmartWare, Release 2.00. This chapter includes the following sections: • Introduction • SmartWare Architecture Terms and Definitions 1.1 Introduction The Software Configuration Guide for SmartWare, Release 2.00 contains many terms that are relate to specific networking technologies areas such as LAN protocols, WAN technologies, routing, Ethernet,...
  • Page 15 Terms and Definitions Term or Definiton Meaning Bootstrap The starting-up of a SmartNode, which involves checking the Reset button, loading and starting the application image, and starting other software modules, or—if no valid application image is available—the bootloader. Build The released software is organized as builds. Each build has its unique identification.
  • Page 16 Terms and Definitions Term or Definiton Meaning Context A SmartWare context represents one specific networking technology or protocol, e.g. IP or circuit switching. Data Port Physical port connected to a network element or used for data transfer. Dejitter Buffer To compensate variable network delays, SmartWare includes a dejitter buffer.
  • Page 17 ISDN network, such as calling line identification presentation (CLIP) or call waiting (CW). See also Q.SIG ISoIP ISDN over IP is patent pending solution of Inalp Networks to carry ISDN services over IP networks. Software Configuration Guide, Revision 1.03...
  • Page 18 Terms and Definitions Term or Definiton Meaning Jitter Jitter is the variation on packets arriving on a SmartNode. See also dejitter buffer. Mode The SmartWare CLI is comprised of modes. There are two basic mode groups, the execution mode group and the configuration mode group.
  • Page 19 Terms and Definitions Term or Definiton Meaning Port In SmartWare a port represents a physical connector on the SmartNode. Port Address A port address can be assigned to a CS interface to realize a virtual voice tunnel between two nodes. Post Filter The voice decoder output is normally filtered using a perceptual post-filter to improve voice quality.
  • Page 20 Terms and Definitions Term or Definiton Meaning SmartNode The SmartNode is Inalp Networks networking product available in two series: • The SmartNode 1000 series are compact integrated access devices for applications in SOHO or branch office environments. They are available in a various interface configurations supporting up to 4 voice channels.

  • Page 21: Applications

    Applications 2 APPLICATIONS This chapter provides an overview of SmartNode applications and the main elements in a SmartNode network. The chapter includes the following sections: • Introduction • Carrier networks • Enterprise networks • LAN telephony 2.1 Introduction The Inalp SmartNode product family consists of highly flexible multi-service IP network devices, which fit a range of networking applications.

  • Page 22: Enterprise Networks

    Applications Figure 2-1: Typical Carrier Network Application Figure 2-1 shows the deployment of SmartNodes in carrier networks. Each subscriber site is equipped with a SmartNode that connects the subscriber CPE on one side with the provider network and services on the other. Typical services in these networks are softswitch based telephony, PSTN access through V5.2 gateways, PBX networking services, and LAN interconnection.

  • Page 23: Lan Telephony

    Applications Figure 2-2: Typical Enterprise Network Figure 2-2 shows the deployment of SmartNodes in enterprise networks. Each site (headquarter, branch or home office) is equipped with a SmartNode that connects the local LAN and telephony infrastructure with the IP WAN and the local PSTN carrier. 2.4 LAN Telephony With its Voice-over-IP gateway features the SmartNode can be used as a standalone gateway for H.323 LAN voice systems such as LAN based PBXs or call centers.
  • Page 24 Applications Figure 2-3: Typical LAN Telephony System Software Configuration Guide, Revision 1.03...

  • Page 25: System Overview

    The second, and in many aspects core element, is the embedded software running on the SmartNode hardware platforms. The software designed by Inalp Networks AG for the SmartNodes is termed SmartWare. This software is handled as a separate element because it is as far as possible platform-independent and so provides the same features and functionality throughout the complete SmartNode model range.

  • Page 26: Smartnode Hardware Platforms

    VoIP gateway and packet routing engine. • Gateway (GW), which converts 64k circuits into Internet protocol (IP) packet streams and vice versa. Voice over IP is supported according the H.323 standard and via Inalp Networks’ patented ISDN over IP (ISoIP) protocol. •...

  • Page 27: Smartware Embedded Software

    System Overview Figure 3-2: SmartNode System Model For more detailed hardware information refer to the SmartNode Hardware Installation Guide. 3.3 SmartWare Embedded Software SmartWare is the application software that runs on the SmartNode hardware platforms. SmartWare is available in several releases that support all available SmartNode models. Refer to the SmartWare release notes for detailed information about hardware support.

  • Page 28: Smartview Management Tools

    System Overview • PMC driver software performs the runtime tasks on PMC interface cards mounted in SmartNode 2000 series devices. The PMC drivers are interface card specific and also have build numbers. Refer to the SmartWare release notes for PMC driver software compatibility. The PMC drivers may be upgraded together with a SmartWare release or they can be downloaded individually onto the device flash memory file system.

  • Page 29: Configuration Concepts

    Configuration Concepts 4 CONFIGURATION CONCEPTS This chapter introduces the basic SmartWare configuration concepts. A good understanding of these concepts is vital for the configuration tasks explained in the remaining chapters of this guide. Even if you do not like to read manuals and user guides, nevertheless we strongly recommend that you read through this chapter because it introduces the fundamental ideas behind the structure of the command line interface.

  • Page 30: Contexts And Gateways

    Configuration Concepts The chapter sections that follow refer to Figure 4-1 and describe the concepts and elements in more detail. 4.2 Contexts and Gateways 4.2.1 Context A SmartWare context represents one specific networking technology or protocol, namely IP (Internet Protocol) or CS (circuit-switching). A context can be seen as ”virtual dedicated equipment” within the SmartNode.

  • Page 31: Ports And Circuits

    Configuration Concepts entities. In SmartWare however, an interface is a logical construct that provides higher-layer protocol and service information, such as layer 3 addressing. Interfaces are configured as part of a context, and are independent of physical ports and circuits. The decoupling of the interface from the physical layer entities enables many of the advanced features offered by SmartWare.

  • Page 32: Profiles And Use Commands

    Configuration Concepts 4.4 Profiles and Use commands 4.4.1 Profiles Profiles provide configuration shortcuts. They contain specific settings which can be used in multiple contexts, interfaces or gateways. This concept allows to avoid repetitions of groups of configuration commands that are the same for multiple elements in a configuration. Figure 4-1 shows profiles that are used in the IP and CS contexts.

  • Page 33: Command Line Interface

    Command Line Interface 5 COMMAND LINE INTERFACE The primary user interface to SmartWare is the command line interface (CLI). You can access the CLI either via the SmartNode console port or through a Telnet session. The CLI lets you configure the complete SmartWare functionality, in contrast to other management interfaces (SNMP, HTTP) which are limited to a subset of the functions.

  • Page 34: System Prompt

    Command Line Interface Figure 5-1: Command Line Modes 5.1.1 System Prompt For interactive (on-line) sessions the system prompt is of the form nodename> In the operator exec mode, Software Configuration Guide, Revision 1.03...

  • Page 35: Navigating The Cli

    Command Line Interface nodename# In the administrator exec mode and in the different configuration modes nodename(mode)# Where: • nodename is the currently configured name of the node (SmartNode), the IP address or the hardware type of the device that is being configured, and •...
  • Page 36 Command Line Interface Mode Name Commands Used to Access Command-Line Prompt operator exec (user log-on) node> administrator exec enable command from operator exec node# mode configure configure command from node(config)# administrator exec mode system system command from configure nod (sys)# mode ic-voice ic voice <slot>...

  • Page 37: Command Editing

    Command Line Interface from configure mode source source {class¦policy} <name> node(src) [<name>]# command from profile_service-policy mode profile_voip profile voip <name> command from node(pf-voip) [<name>]# configure mode profile_tone-set profile tone-set <name> command node(pf-tones) [<name>]# from configure mode profile_call-progress- profile call-progress-tone command node(pf-callp) [<name>]# tone from configure mode...
  • Page 38 Command Line Interface Esc f is handled differently; press and release the “Escape” key (often labeled Esc on many keyboards) and then press the f key. Software Configuration Guide, Revision 1.03...
  • Page 39 Command Line Interface Keyboard Description Ctrl-p and <up-arrow> Recall previous command in the command history. Ctrl-n and <down-arrow> Recall next command in the command history. Ctrl-f and <right-arrow> Move cursor forward one character. Ctrl-b and <left-arrow> Move cursor backward one character. Esc f Move cursor forward one word.

  • Page 40: Accessing The Smartware Command Line Interface

    Accessing the SmartWare Command Line Interface 6 ACCESSING THE SMARTWARE COMMAND LINE INTERFACE The Inalp SmartNode products are engineered for operator network deployment, which means an emphasis on remote management and volume deployment. SmartNode management and configuration is therefore based on IP network connectivity. Once a SmartNode is connected to, and addressable in, an IP network then all configuration, management and maintenance tasks can be performed remotely.

  • Page 41: Accessing Via The Console Port

    Accessing the SmartWare Command Line Interface • Checking Identity and Connected Users • Ending a Telnet or Console Port Session 6.4 Accessing via the Console Port To access a SmartNode via its console port the host computer must be connected directly to the console port (labelled CONSOLE) with a serial cable (see Figure 6-1).

  • Page 42: Accessing Via A Telnet Session

    Accessing the SmartWare Command Line Interface Step 5 Proceed with logging in 6.5 Accessing via a Telnet Session This is the most usual method to connect to a SmartNode. The Telnet host accesses the SmartNode via its network interface. A host can be connected directly to the ETH 1 port (LAN) with a crossover cable (see Figure 6-2 A) or through an Ethernet hub with two straight cables (see Figure 6-2 B).

  • Page 43: Telnet Procedure

    Accessing the SmartWare Command Line Interface 6.5.1 Telnet Procedure Before you begin to use the CLI to input configuration commands, carry out these six steps: Step 1 Set up the SmartNode as described in the Hardware Installation Guide. Step 2 Connect the host (PC) or hub to the ETH 1 (LAN) port of your SmartNode with crossover or straight cables, according to Appendix A of the Hardware Installation Guide.

  • Page 44: Warning

    Accessing the SmartWare Command Line Interface 6.6.1 Warning You are responsible for creating a new administrator account to maintain system security. Inalp Networks accepts no responsibility for losses or damage caused by loss or misuse of passwords. Please read the following sections to secure your network equipment properly. 6.7 Selecting a Secure Password It is not uncommon for someone to try to hack into a network device.

  • Page 45: Create An Operator Account

    Accessing the SmartWare Command Line Interface 6.10 Create an Operator Account Operators do not have privileges to run the enable command and therefore cannot modify the system configuration. Operators are able to view partial system information. Creating a new operator account needs the following procedure: Pr oc edu re Create an operator account.

  • Page 46: Displaying The Cli Version

    Accessing the SmartWare Command Line Interface Step 2 node#configure Enters configuration mode Step 3 node(cfg)# administrator name password Creates new administrator account password name and password password Step 4 node(cfg)#copy running-config startup- Permanently stores the new config administrator account parameters. Ex amp le: C reat e a n Ad min ist ra to r Acc ou nt The following example shows the commands used to add a new administrator account with a login name “super”...

  • Page 47: Switching To Another Account

    Accessing the SmartWare Command Line Interface operator accounts E x amp le: D is p la y A c c ou nt Inf or m at io n The following example shows how to display information about existing administrator and operator accounts.

  • Page 48: End A Telnet Or Console Port Session

    Accessing the SmartWare Command Line Interface M od e Administrator or operator execution Command Purpose Step 1 node#who Shows more detailed information about the users ID, name, state, idle time and location node>who Shows the user login identity E x amp le: C h ec k ing Id ent i t y a n d C on ne ct e d U s ers The following example shows how to report who is logged in or more detailed information about users and process states, depending on the execution mode working in.
  • Page 49 Accessing the SmartWare Command Line Interface After confirming the dialog with “yes” the Telnet session to the SmartNode is terminated and the Telnet application window on your host closes. Note: Using the command exit in the operator execution mode also terminates a Telnet or console port session, but without any confirmation dialog.

  • Page 50: Establishing Basic Ip Connectivity

    Establishing Basic IP Connectivity 7 ESTABLISHING BASIC IP CONNECTIVITY This chapter explains how to establish network-based connections to and from your SmartNode using IP interfaces and Ethernet ports. Configuring basic IP connectivity is carried out in both the context IP and the subsidiary interface command modes. For a complete description of the IP context and interface configuration related commands referred to in this chapter, see Chapter 11, “IP Context Overview”, and Chapter 12, “IP Context Overview”...

  • Page 51: Define Ip Ethernet Encapsulation And Bind Ip Interface To Physical Port

    Establishing Basic IP Connectivity Command Purpose Step 1 node(cfg)#context ip router Enters the predefined IP context configuration mode. Step 2 node(ctx-ip)[router]#interface Creates the new interface name, which represents an name IP interface. This command also places you in interface configuration mode for the interface name you have just created.

  • Page 52: Activating A Physical Port

    Establishing Basic IP Connectivity E x amp le: D e f ine I P E t h er net En ca psu l at io n a nd B in d I P Int erf ace t o Phys i c a l P o r t We assume you would like to set IP encapsulation for Ethernet port 0 on slot 0 and bind the already defined IP interface lan to the same physical port.

  • Page 53: Display Ip Interface Information

    Establishing Basic IP Connectivity At this point your SmartNode has a running IP interface on Ethernet port 0 on slot 0, which uses IP encapsulation. 7.6 Display IP Interface Information Information for all the configured IP interfaces can be displayed by the show command. The command lists relevant information for every IP interface.

  • Page 54: Examples

    Establishing Basic IP Connectivity M od e Context IP Command Purpose Step 1 node(ctx-ip)[router]#no Deletes the existing IP interfaces name interface name Ex amp le: De lete IP In te rfac es The illustrated procedure below assumes that you would like to delete the IP interface named external.
  • Page 55 Establishing Basic IP Connectivity Figure 7-1: Relation between IP Interface lan and Ethernet port 0 on slot 0 First the context IP mode is selected for the required IP interface configuration. SN>enable SN#configure SN(cfg)#context ip router After that a new interface lan is created, for which both the IP address and netmask are specified. SN(ctx-ip)[router]#interface lan SN(if-ip)[lan]#ipaddress 192.168.1.3 255.255.255.0 Next the Ethernet port 0 on slot 0 is selected, the medium is set to 10 Mbit/s in half-duplex mode, and...

  • Page 56: System Image Handling

    System Image Handling Task List 8.1 Introduction All Inalp Networks SmartNode devices are shipped with a default system image, which is stored in the persistent flash memory of the SmartNode at the Inalp Networks AG factory. The system image contains the application image and driver software images that together build SmartWare. In addition a factory configuration is loaded to the SmartNode at the Inalp Networks AG factory, which initially parameterizes SmartWare.
  • Page 57 System Image Handling • Configuration files have to be stored in the logical region nvram: of the flash memory. The factory default configuration is always loaded, and may be restored by pressing the SmartNode reset button; see the Hardware Configuration Guide. The startup, or user-specific configuration, is also stored in nvram.

  • Page 58: Boot Procedure And Bootloader

    System Image Handling Figure 8-1: SmartNode Memory Regions Logically Defined in SmartWare 8.3 Boot Procedure and Bootloader During a normal boot procedure of a SmartNode the bootstrap application checks the persistent memory in the logical region nvram: for an application image. Following that the application image is executed, that is SmartWare is started module by module.

  • Page 59: Factory Configuration

    System Image Handling Figure 8-2: Boot Procedure There are two situations during bootstrap during which the bootloader takes control. The bootstrap application checks the status of the Reset button on the back plane of the SmartNode, and if the system button has been pressed it launches the bootloader. The bootloader is also launched if a valid application image is not available.

  • Page 60: Warning

    The following example shows the information that is available for a SmartNode 2000 series device with an optional IC-4BRV interface card mounted in slot 2. SN#show version Product name : SN2300 Software Version : SmartWare R2.00 BUILD22031 Supplier Provider Subscriber Information for Slot 0:...

  • Page 61: Copy System Images From A Network Server To Flash Memory

    As mentioned above the system image file contains the application software that runs SmartWare; it is loaded in the flash memory at the Inalp Networks factory. Since most of the voice and data features of the SmartNode are defined and implemented within the application software, upgrading to a new release might be necessary if you want to have additional voice and data features available.

  • Page 62: Copy Driver Software From A Network Server To Flash Memory

    System Image Handling The script file is downloaded with the copy commands. The copy command source defines the TFTP path to the script file and the target is set use the script parser. After downloading the script file the system image file and command line syntax definition file download is started automatically. Note: When encountering problems due to memory exhaustion (message "Parsing batch file...% APP - OUT OF MEMORY.") shutdown the H.323 gateway prior to initiating the download command as follows (which will temporarily free the required memory):...
  • Page 63 The following example shows a script file used to download a driver software image file from a TFTP server for an IC-4BRV interface card. # script file for driver software image download # Inalp Networks, Inc. 2001-10-24 /IC-4BRVoIP_Vx_R2.00_BUILD24028 +/flash/bin/pmc000216a6 4¼—...

  • Page 64: Configuration File Handling

    Configuration File Handling Task List 9.1 Introduction All Inalp Networks SmartNode devices are shipped with a factory configuration file which is stored in the flash memory of the SmartNode. A configuration file is like a script file containing SmartWare commands that can be loaded into the system.

  • Page 65: Understanding Configuration Files

    Configuration File Handling 9.1.1 Understanding Configuration Files Configuration files contain SmartWare commands that are used to customize the functionality of your SmartNode device. During system startup the SmartWare command parser reads the factory or startup configuration file command-by-command, organizes the arguments and dispatches each command to the command shell for execution.

  • Page 66: Factory Configuration

    Configuration File Handling mtu 1500 # interface WAN used for connection to access network interface wan ipaddress 172.19.32.30 255.255.255.0 mtu 1500 # interface used to access the PSTN telecom operator interface pstn pstn-operator routing dest-interface h323 bind port 1 0 # interface used to access the VoIP telecom provider interface h323 voip-provider routing dest-table rtab...

  • Page 67: Warnings

    Avoid downloading any configuration file if you do not completely understand what you have to do! If a configuration file download fails or succeeds only partially your SmartNode device cannot start up without a support intervention at the Inalp Networks factory. 9.4 Configuration File Handling Task List This Section describes how to create, load, and maintain configuration files.
  • Page 68 Configuration File Handling Figure 9-2: Local Memory Regions in SmartWare As shown in Figure the local memory regions are identified by their unique names, like nvram: which is located in flash memory and system:, which is the system RAM, i.e. the volatile memory. As already mentioned, within the same memory region any configuration file needs a unique name so for example it is not possible to have two configurations files with the name running-config in the memory region nvram:.

  • Page 69: Replacing The Startup Configuration With A Configuration From Flash Memory

    Check the content of the persistent startup configuration by listing its command settings with the show command. SN#show startup-config Startup configuration: #----------------------------------------------------------------# # SmartWare R2.00 BUILD22031 # 2001-10-25T09:20:42 # Generated configuration file #----------------------------------------------------------------# cli version 2.00 Software Configuration Guide, Revision 1.03...

  • Page 70: Copy Configurations To And From A Remote Storage Location

    Configuration File Handling snmp community public rw … framerelay exit 9.7 Copy Configurations to and from a Remote Storage Location Configuration Files may be copied from local memory (persistent or volatile region) to a remote data store. Remember the different store locations; they are the local memory in your SmartNode and the remote data store on a server system.

  • Page 71: Replacing The Startup Configuration With A Configuration Downloaded From Tftp Server

    Configuration File Handling or cloning purposes. The latter procedure is very helpful when you have several SmartNode devices each using a configuration which does not greatly differ from the others, or which is the same for all devices. During the configuration of the first SmartNode according to your requirements, the running configuration of this device, named running-config and which is to be found in the volatile memory region system: is edited.

  • Page 72: Displaying Configuration File Information

    Check the content of the persistent startup configuration by listing its command settings with the show command. SN#show nvram:startup-config Startup configuration: #----------------------------------------------------------------# # SmartWare R2.00 BUILD22031 # 2001-10-25T09:20:42 # Generated configuration file #----------------------------------------------------------------# cli version 2.00 snmp community public rw …...

  • Page 73: Modifying The Running Configuration Offline

    Configuration File Handling Pr oc edu re To modify the running configuration at the CLI and store it as the startup configuration M od e Administrator execution Command Purpose Step 1 node#configure Enters administrator configuration mode Step 2 Enter all the necessary configuration commands.

  • Page 74: Deleting A Specified Configuration

    Configuration File Handling Command Purpose Step 1 node#copy running-config tftp://node-ip- Uploads the current running configuration adress/current-config as file current-config to the TFTP server at address node-ip-address. This progress is visualized with a counter, counting up from 0 to 100% according to the downloaded amount of the file size.
  • Page 75 Configuration File Handling Pr oc edu re To delete a specified configuration in flash memory M od e Administrator execution Command Purpose Step 1 node#show nvram: Lists the loaded configurations Step 2 node#erase name Deletes the configuration name from flash memory. E x amp le: D e l et in g a S p ec if ie d C o nf i gu rati o n The following example shows how to delete a specific configuration from among a set of three available configurations in Flash memory.

  • Page 76: Basic System Management

    Basic System Management 10 BASIC SYSTEM MANAGEMENT This chapter describes parameters that report basic system information to the operator or administrator, and their configuration. Refer to Chapter 5, “System Mode”, in the SmartWare Command Reference Guide for a complete description of the commands related to this chapter. This chapter includes the following sections: •...
  • Page 77 Basic System Management System contact information tells the user how to contact the information service, e.g. the help line of the service provider. The contact information may be any alphanumeric string, including spaces, that is no longer than one line. This entry corresponds to the MIB II system sysContact object. The system name, also called the hostname, is used to uniquely identify the SmartNode in your network.

  • Page 78: Setting The System Banner

    Basic System Management Note: If system information has to be formed out of more than one word the information is enclosed by double quotes Ex amp le: Set ting S ys te m Inf ormat ion The following example shows the commands used to configure the contact information for your device, if you start from the operator execution mode.

  • Page 79: Setting Time And Date

    Basic System Management SN(cfg)#banner "#\n# Inalp Networks, Inc.\n#\n# Security Information:\n#\n# The password of all operators has changed please contact the administrator.\n#" 10.5 Setting Time and Date All SmartNode devices provide time-of-day and date services. These services allow the products to accurately keep track of the current time and date.

  • Page 80: Display Time Since Last Restart

    SmartWare are possible using a browser instead of accessing the SmartWare CLI via Telnet or the serial console. Without a Java applet the value of the embedded web server is limited. Contact Inalp Networks for any questions about custom designed Java configuration tools for SmartWare.

  • Page 81: Determining And Defining The Active Cli Version

    Basic System Management 10.9 Determining and Defining the active CLI Version SmartWare allows having a number of CLI version installed together, whereas only one CLI version is activated. There are commands available to determine the currently running CLI version and if necessary switch to another CLI version.

  • Page 82: Displaying The System Event Log

    Basic System Management Press 'yes' to restart, 'no' to cancel : yes The system is going down 10.11 Displaying the System Event Log The system event log contains warnings and information from system components of SmartWare. In case of problems it is often useful to check the system log for any information about malfunctioning system components.

  • Page 83: Controlling Command Execution

    Basic System Management 2001-03-12T08:24:15 : First start 2002-03-12T08:38:37 : First start 2002-03-12T10:37:31 : First start 10.13 Controlling Command Execution The SmartWare command shell includes a basic set of commands that allow you to control the execution of other running commands. In SmartWare the commands jobs and fg are used for such purposes.

  • Page 84: Displaying The Checksum Of A Configuration

    Basic System Management … Show the currently running commands SN>jobs * [run ] jobs 0 [bg ] ping Bring job 0 to foreground SN>fg % Resumed [ping] Reply from 172.16.36.80: Time <10ms Reply from 172.16.36.80: Time <10ms Ctrl-C Terminate current command % Aborted (ping) 10.14 Displaying the Checksum of a Configuration In SmartWare configuration files, e.g.

  • Page 85: Ip Context Overview

    IP Context Overview 11 IP CONTEXT OVERVIEW This chapter outlines the SmartWare Internet protocol (IP) context, together with its related components. You will get the fundamental understanding on how to set up your SmartNode to make use of IP related services. In the following sections configuration steps necessary to put together certain IP services are illustrated, together with the references to the related chapters that explain the issue in more details.

  • Page 86: Ip Context Overview Configuration Task List

    IP Context Overview Figure 11-1: IP Context and Related Elements The IP context undertakes the task of doing all IP related transport of data and voice packets via the logical interfaces and available gateways. In addition using profiles, which together with the IP context pinpoint how packets have to be handled for specific services, enhances the possible field of application.

  • Page 87: Planning Your Ip Configuration

    IP Context Overview • Finally if your network shall provide better service to selected network traffic, Chapter 15, “Link Scheduler Configuration” will help you with getting in-depth knowledge about quality of service (QoS) management with SmartWare. The basic tasks involved in IP context configuration are described in the following sections. Many parameters have acceptable default values, which in most cases do not need to be explicitly configured.

  • Page 88: Qos Related Information

    IP Context Overview The most important difference between these types of devices is that the DCE device supplies the clock signal that paces the communications on the interface. Note: The SmartNode 2300 is working as a DTE per default. Before you connect a device to the synchronous serial port, labelled SERIAL 0/0 on SmartNode 2300, you need to check the following: •...

  • Page 89: Configuring Napt

    IP Context Overview port. Therefore it is in your interest to decouple a logical interface from a physical port, by giving names to interfaces that describe their usage and not the physical constitution. As for any IP interface several IP related configuration parameters are necessary to define the behaviour of such an interface.

  • Page 90: Configuring Access Control Lists

    IP Context Overview destination-network entry, the router adds one to the metric value indicated in the update and enters the network in the routing table. The IP address of the sender is used as the next hop. RIP prevents routing loops from continuing indefinitely by implementing a limit on the number of hops allowed in a path from the source to a destination.

  • Page 91: Ip Interface Configuration

    IP Interface Configuration 12 IP INTERFACE CONFIGURATION This chapter provides a general overview of SmartNode interfaces and describes the tasks involved in configuring them. For detailed information on command syntax and usage guidelines for the commands listed in section “IP Interface Configuration Task List”, refer to Chapter 15, “Interface Mode”...

  • Page 92: Deleting An Ip Interface

    IP Interface Configuration Command Purpose Step 1 node(ctx-ip)[router]#interface Creates the new interface name, which represents name an IP interface. This command also places you in interface configuration mode for the interface just created. Step 2 node(if-ip)[name]# You are now in the interface configuration mode, where specific configuration parameters for IP interface name can be entered Ex amp le: C reat e IP In te rfac es...

  • Page 93: Setting The Ip Address And Netmask

    IP Interface Configuration Now delete the interfaces named “eth3” with the no interface command: SN(ctx-ip)[router]#no interface external Finally list the interfaces again to check if the appropriate interface was deleted: SN(ctx-ip)[router]#interface <?> <interface> New interface Existing interface Existing interface internal Existing interface 12.5 Setting the IP Address and Netmask Each IP interface needs its explicit IP address and an appropriate network mask to be set.

  • Page 94: Icmp Redirect Messages

    IP Interface Configuration other routers when a problem is discovered with the Internet header. For detailed information on ICMP, see RFC 792. SmartWare supports following ICMP message processing features: • ICMP redirect messages • Router advertisement broadcast message 12.7 ICMP Redirect Messages Routes are sometimes less than optimal.

  • Page 95: Defining The Mtu Of The Interface

    IP Interface Configuration Pr oc edu re To enable sending router advertisement broadcast messages on interface name, if this feature was disabled M od e Interface Command Purpose Step 1 node(ctx-ip)[router]#interface Selects interface name for ICMP message name processing configuration Step 2 node(if-ip)[name]# icmp router- Enables sending of router advertisement...

  • Page 96: Configuring An Interface As A Point-To-Point Link

    IP Interface Configuration 12.10 Configuring an Interface as a Point-to-Point Link A point-to-point network joins a single pair of routers. It is in particular used for interfaces, which have a binding to a frame relay PVC. Pr oc edu re Configure the interface ifname as point-to-point link M od e Configure...

  • Page 97: Testing Connections With The Ping Command

    IP Interface Configuration ICMP router-discovery: enabled ICMP redirect: send only State: OPENED Binding: ethernet 0 0 0/ethernet/ip ------------------------------------------------------------ Context: router Name: IP Address: 172.17.100.210 255.255.255.0 MTU: 1500 ICMP router-discovery: enabled ICMP redirect: send only State: CLOSED Binding: ethernet 0 0 1/ethernet/ip …...

  • Page 98: Examples

    IP Interface Configuration 12.13 Examples 12.13.1 Deleting an IP Interface Example The following example shows how to delete an IP interface named wan, use the no command as following demonstrated in IP context configuration mode. List the existing interfaces in the IP context: SN(ctx-ip)[router]#interface <?>...

  • Page 99: Napt Configuration

    NAPT Configuration 13 NAPT CONFIGURATION 13.1 Overview This chapter provides a general overview of Network Address Port Translation and describes the tasks involved in configuring it. For detailed information on command syntax and usage guidelines for the commands listed in section “Configuring Network Address Port Translation Task List”, refer to Chapter 10, “Profile NAPT Mode”...

  • Page 100: Creating A Napt Profile

    NAPT Configuration 13.4 Creating a NAPT Profile A NAPT profile can be bound to the global interface. The profile defines which packets to ports destined to the global interface should be forwarded to which hosts on the local network. Furthermore a host can be specified to get all ICMP messages, namely the ICMP default server. This command creates and enters new profiles, enters existing profile or removes existing profile.

  • Page 101: Removing A Static Napt Entry

    NAPT Configuration E x amp le: A d d in g a N A PT E nt ry The following example shows how to add a static NAPT entry to profile access. All TCP packets, arriving at the global interface at port 80, are forwarded to the host with IP address 192.168.1.1 in the local network.

  • Page 102: Removing An Icmp Default Server

    NAPT Configuration Command Purpose Step 1 node(cfg)#profile napt name Selects the existing NAPT profile name for modification Step 2 node(pf-napt)[name]#icmp Defines a host in the local network at IP address default ip-address ip-address shall get all ICMP messages from the global network E x amp le: C o nf i gu r ing an IC M P D e f au l t S er ve r The following example shows how to configuring the ICMP defaults server.

  • Page 103: Display Napt Configuration Information

    NAPT Configuration M od e Configure Command Purpose Step 1 node(cfg)#context ip router Selects the IP router context Step 2 node(ctx-ip)[router]#interface The NAPT profile shall be used on the interface name name Step 3 node(if-ip)[name]#use profile Defines that the NAPT profile profile shall be used napt profile on the interface name E x amp le: C o nf i gu r ing N A P T Int e rfa ce...

  • Page 104: Ethernet Port Configuration

    Ethernet Port Configuration 14 ETHERNET PORT CONFIGURATION This chapter provides an overview of Ethernet ports and describes the tasks involved in configuring Ethernet ports through the Inalp SmartWare. For detailed information on syntax and usage guidelines for the commands listed under “Procedures”, see the Chapter 22, “Port Ethernet Mode” in the SmartWare Command Reference Guide.

  • Page 105: Configuring Medium For An Ethernet Port

    Ethernet Port Configuration the interface card fit for SmartNode 2000 series devices. All permanent on-board interfaces of a SmartNode are described as being on slot 0. See the following table for more details. Device Type Interface Type Slot Port Interface SmartNode 1x00 Ethernet ETH 0...

  • Page 106: Configuring Ethernet Encapsulation Type For An Ethernet Port

    Ethernet Port Configuration 14.5 Configuring Ethernet Encapsulation Type for an Ethernet Port Pr oc edu re To configure the encapsulation type to IP for the Ethernet port on slot and port M od e Configure Command Purpose Step 1 node(cfg)#port ethernet slot port Enters Ethernet port configuration mode for the interface on slot and port Step 2...

  • Page 107: Selecting The Frame Format For An Ethernet Port

    Ethernet Port Configuration Figure 14-1: Binding of an Ethernet Port to an IP Interface Pr oc edu re To bind the Ethernet port to an already existing IP interface M od e Configure Command Purpose Step 1 node(cfg)#port ethernet slot port Enters Ethernet port configuration mode for the interface on slot and port Step 2...

  • Page 108: Configuring Layer 2 Cos To Service Class Mapping For An Ethernet Port

    Ethernet Port Configuration Ethernet connection the frame format has to be specified. The command frame-format allows you to set the sending either of IEEE 802.3 or IEEE 802.1Q frames. Supported command options are: • dot1q Sends VLAN-tagged IEEE 802.1Q frames used for virtual LANs •...

  • Page 109: Adding A Receive Mapping Table Entry

    Ethernet Port Configuration Step 2 node(prt-eth)[slot/port]#cos Selects the layer 2 CoS to service class mapping {default | rx-map | tx-map } If the frame format is set to standard, the cos default command value defines which class of service has to be used for the data traffic. The command syntax is: The cos rx-map and cos tx-map commands above need service class mapping table entries, which has to be entered as additional command argument.

  • Page 110: Closing An Ethernet Port

    Ethernet Port Configuration Pr oc edu re To add a transmit mapping table entry M od e Configure Command Purpose Step 1 node(cfg)#port ethernet slot port Enters Ethernet port configuration mode for the interface on slot and port Step 2 node(prt-eth)[slot/port]#cos tx- Adds a transmit mapping table entry, which map service class value as layer 2...
  • Page 111 Ethernet Port Configuration SN(prt-eth)[0/0]#shutdown Checking the state of the Ethernet port on slot 0 and port 0 shows that the interface was closed. SN(prt-eth)[0/1]#show port ethernet 0 1 Ethernet Configuration ------------------------------------- Port : ethernet 0 0 1 State : CLOSED MAC Address : 00:30:2B:00:1D:D4 Speed...

  • Page 112: Link Scheduler Configuration

    Link Scheduler Configuration 15 LINK SCHEDULER CONFIGURATION This chapter describes how to use and configure the SmartWare, Release 2.00, Quality of Service (QoS) features. For a complete description of the QoS related commands in this chapter, see Chapter 8, "Profile Service Policy Mode", in the SmartWare Command Reference Guide. Moreover it is advisable to read Chapter 19, “Access Control List Configuration”, to fully understand the use of access control lists.

  • Page 113: Quick References

    Link Scheduler Configuration Figure 15-1: Service-Policy Profile devoted to an Interface The link arbiter controls outbound network traffic according to a service-policy profile devoted to a certain interface, as shown in Figure 15-1. Take into account, that such an interface normally represents the very bottleneck in the data transmission chain.

  • Page 114: Setting The Modem Rate

    Link Scheduler Configuration 15.2.1 Setting the Modem Rate If you are familiar with SmartWare Release 1.50 or 1.80, you might wonder where the command to set the modem rate is to be found In SmartWare Release 2.00. To match the voice and data multiplexing to the capacity of the access link is, with Release 2.00, just one of a variety of possible configurations that you can set.

  • Page 115: Link Scheduler Configuration Task List

    Link Scheduler Configuration Action IOS command SmartWare command bit rate to a source. For IOS specifies or modifies bandwidth {bandwidth-kbps | share percent-of-bandwidth the bandwidth allocated for a percent percent} class belonging to a policy map. Percent defines the percentage of available bandwidth to be assigned to the class.

  • Page 116: Creating An Access Control List

    Link Scheduler Configuration The packet classification has to be defined as a first step. In SmartWare the access control list are used to tag packets to a certain class. Note: Keep in mind that the class local-default comprises all other classes, which are not explicitly stated in a service policy profile.

  • Page 117: Assigning Bandwidth To Traffic Classes

    Link Scheduler Configuration Pr oc edu re Creating an access control list for tagging web traffic from the single source host at a certain IP address. M od e Configure Command Purpose Step 1 node(cfg)#profile acl name Creates a new access control list profile named name Step 2 node(pf-acl)[name]#permit ip host ip-...

  • Page 118: Burst Tolerance

    Link Scheduler Configuration Note: The SmartWare link scheduler before any other bandwidth sharing method always serves the priority scheme first. W e i ght ed F a ir Que u in g With other traffic sources you do not know as well, you would normally want to specify that for example class A gets three times the bandwidth of class B and that-no matter how many class A packets arrive-B packets will still be served.
  • Page 119 Link Scheduler Configuration • it is a clean way of combining different decision criteria and • it can also be a nice way to cope with groups of traffic classes In Figure 15-3 an example of hierarchical scheduling is illustrated. The 1 level arbiter Level_1 uses weighted fair queuing to share the bandwidth among source classes VPN, Web and incorporates the traffic from the 2...

  • Page 120: Creating A Top-Level Service Policy Profile

    Link Scheduler Configuration share 30 Figure 15-4: Service Policy for Level_1 Arbiter Parts of the configuration used for arbiter Low_Priority are listed below. . The arbitration uses shaping to share the bandwidth between the two classes Mail and Default. Therefore each class gets just as much bandwidth as assigned, but never more.
  • Page 121 Link Scheduler Configuration … source class name … source class name … source policy name Figure 15-7: Syntax of a Top-Level Service Policy Profile The first line specifies the name of the link arbiter profile to configure. On the second line the global bandwidth limit is set.

  • Page 122: Specifying Source Classes Or Lower Level Source Policy Profiles

    Link Scheduler Configuration Step 4 node(pf-srvpl)[name]#source {class | Enters source configuration mode for policy} src-name an ACL class or an hierarchical lower level service policy profile named src- name. Step 5 node (src)[src-name]… At this point the necessary commands used to specify the source classes or lower level source policy profiles have to be entered.

  • Page 123: Defining The Bit-Rate

    Link Scheduler Configuration recommended to split 100—which is interpreted as 100%—among all available source classes, e.g. with 20, 30 and 50 as value for the respective share commands, which represent 20%, 30% and 50%. Pr oc edu re Defining fair queuing weight M od e Source Command...

  • Page 124: Defining The Maximum Queue Length

    Link Scheduler Configuration 15.8.4 Defining the Maximum Queue Length The command queue-limit specifies the maximum number of packets queued for the class name. Excess packets are dropped. Used in “class” mode—queuing only happens at the leaf of the arbitration hierarchy tree. The no form of this command reverts the queue-limit to the internal default value, which depends on your configuration.

  • Page 125: Specifying The Precedence Field

    Link Scheduler Configuration Pr oc edu re Defining the type-of-service (TOS) field M od e Source Command Purpose node(src)[name]#set ip tos value Defines the type-of-service (TOS) value applied to packets of for the selected class or policy name. Valid values for value are 0, 1, 2, 4, and 8, as given in Table 15-2.
  • Page 126 Link Scheduler Configuration • conditioning the marked packets at network boundaries in accordance with the requirements or rules of each service. The requirements or rules of each service must be set through administrative policy mechanisms, which are outside the scope of this user guide. A differentiated services-compliant network node includes a classifier that selects packets based on the value of the DS field, along with buffer management and packet scheduling mechanisms capable of delivering the specific packet forwarding treatment indicated by the DS field value.

  • Page 127: Specifying Layer 2 Marking

    Link Scheduler Configuration Pool Codepoint Space Assignment Policy xxxxx0 Standards Action xxxx11 EXP/LU xxxx01 EXP/LU (*) Table 15-3: Codepoint Pools (*) may be utilized for future Standards Action allocations as necessary Service providers are not required to use the same node mechanisms or configurations to enable service differentiation within their networks, and are free to configure the node parameters in whatever way that is appropriate for their service offerings and traffic engineering objectives.

  • Page 128: Defining Random Early Detection

    Link Scheduler Configuration Tagged Frame Type Interpretation Always set to 8100h for Ethernet frames (802.3ac tag format) 3-Bit Priority Field (802.1p) Value from 0 to 7 representing user priority levels (7 is the highest) Canonical Always set to 0 12-Bit 802.1Q VLAN Identifier VLAN identification number Table 15-4: T...

  • Page 129: Devoting The Service Policy Profile To An Interface

    Link Scheduler Configuration argument kilobits-ahead defines the tolerated burst size in kBits/s ahead of schedule. Excess packets are dropped. Pr oc edu re Defining discard excess load M od e Source Command Purpose node(src)[name]#police average-kilobits burst- Defines how traffic arriving in a queue for for size kilobits-ahead the selected class or policy name has to be controlled.

  • Page 130: Displaying Link Arbitration Status

    Link Scheduler Configuration Therefore the use profile service-policy command allows attaching a certain service policy profile to an IP interface that is defined within the IP context. The command offers an optional argument allowing to define that the service policy profile is activated in receive or transmit direction. Note: Be aware that service policy profiles can only be activated on the transmit direction at the moment! Providers may use input shaping to improve downlink voice jitter in the absence of voice support.

  • Page 131: Displaying Link Scheduling Profile Information

    Link Scheduler Configuration E x amp le: D is p la yin g L i nk A rb it r at io n Statu s The following example shows how to display link arbitration status information. SN>show service-policy available queue statistics -------------------------- default - packets in queue: 10...
  • Page 132 Link Scheduler Configuration Table 15-5: Values Defining Verbosity of Command Output Note: The debug features offered by SmartWare require CPU resources of your SmartNode. Therefore do not enable statistic gathering or other debug features if it is not necessary. Disable any debug feature after use with the no form of the command.

  • Page 133: Serial Port Configuration

    Serial Port Configuration 16 SERIAL PORT CONFIGURATION This chapter provides an overview of the serial port and describes the tasks involved in configuring the serial port through the Inalp SmartWare. For detailed information on syntax and usage guidelines for the commands listed under Configuration Tasks, refer to the Chapter 23, "Port Serial Mode" of the SmartWare Command Reference Guide.

  • Page 134: Disabling An Interface

    Serial Port Configuration 16.3 Disabling an Interface Before you replace a compact serial cable, or attach your SmartNode to other serial equipment, use the shutdown command to disable the serial interfaces. This is to prevent anomalies and hardware faults. When you shut down an interface, it has the state CLOSED in the show port serial command display. Note: Use the no shutdown command to enable the serial interface after the configuration procedure.

  • Page 135: Configuring The Serial Encapsulation Type

    Serial Port Configuration M od e Administrator execution Command Purpose Step 1 node(cfg)#port serial slot port Selects the serial interface on slot and port Step 2 node(prt-ser)[slot/port]#no shutdown Enable the interface Step 3 node(prt-ser)[slot/port]#show port serial Displays the serial interface configuration.

  • Page 136: Configuring The Hardware Port Protocol

    Serial Port Configuration E x amp le: C o nf i gu r ing t he S er ia l E nca psu l at io n T yp e The following example enables frame relay encapsulation for the serial interface on slot 0 and port 0 of a SmartNode 2300 series device.

  • Page 137: Defining The Transmit Data Clock Edge

    Serial Port Configuration Port : serial 0 0 0 State : CLOSED Hardware Port : X.21 Port Type : DTE CRC Type : CRC-16 Max Frame Length: 2048 Recv Threshold Encapsulation : framerelay 16.7 Defining the Transmit Data Clock Edge SmartWare allows defining the received clock edge on which data shall be transmitted over the serial interface from a SmartNode to a peripheral device.

  • Page 138: Configuring The Lmi Type

    Serial Port Configuration Step 3 node(frm-rel)[slot/port]# Frame Relay configuration mode prompt is displayed Ex amp le: Ent er Fr ame R e la y Mod e The following example shows how to enter into the Frame Relay configuration mode for the serial interface on slot 0 and port 0 of a SmartNode 2300 series device.

  • Page 139: Enabling Fragmentation

    Serial Port Configuration Command Purpose Step 1 node(frm-rel)[slot/port]#keepalive number Sets the LMI keepalive interval To disable keepalives on networks that do not utilize LMI, use the no keepalive interface configuration command. E x amp le: C o nf i gu r ing t he K ee pa l i ve I n t erva l The following example sets the keepalive interval to 10 seconds for Frame Relay over the serial interface on slot 0 and port 0 of a SmartNode 2300 series device.

  • Page 140: Configuring The Pvc Encapsulation Type

    Serial Port Configuration The resulting set of interconnected devices forms a private Frame Relay group, which may be either fully interconnected with a complete "mesh" of virtual circuits, or only partially interconnected. In either case, each virtual circuit is uniquely identified at each Frame Relay interface by a Data Link Connection Identifier (DLCI).

  • Page 141: Binding The Frame Relay Pvc To Ip Interface

    Serial Port Configuration SN(prt-ser)[0/0]#framerelay SN(frm-rel)[0/0]#pvc 1 SN(pvc)[1]#encapsulation rfc1490 16.14 Binding the Frame Relay PVC to IP Interface A newly created permanent virtual circuit (PVC) for Frame Relay has to be bound to an IP interface for further use. The logical IP interface has to be defined already and should be named according to the use of the serial Frame Relay PVC.

  • Page 142: Disabling A Frame Relay Pvc

    Serial Port Configuration SN(cfg)#port serial 0 0 SN(prt-ser)[0/0]#framerelay SN(frm-rel)[0/0]#pvc 1 SN(pvc)[1]#bind interface wan router 16.15 Disabling a Frame Relay PVC Frame Relay PVCs can be disabled whenever it is necessary. Be aware that disabling a specific PVC also disables the related serial interface and vice versa. Pr oc edu re To disable the Frame Relay PVC dlci on the serial interface M od e...

  • Page 143: Examples

    Serial Port Configuration Command Purpose Step 1 node(prt-ser)[slot/port]#show framerelay Displays Frame Relay information E x amp le: D is p la yin g F ra m e R e la y I n f or mat i on The following example displays the Frame Relay configuration settings for the serial interface. SN(cfg)#port serial 0 0 SN(prt-ser)[0/0]# show framerelay Framerelay Configuration:...

  • Page 144: Integrated Service Access

    Serial Port Configuration serial 0 0 0 open rfc1490 wan@router 16.17.3 Integrated Service Access The example in Figure 16-2 shows a typical integrated service access scenario, where different service providers are accessed via permanent virtual circuits (PVCs) on Frame Relay over the serial interface of a SmartNode 2300 series device.
  • Page 145 Serial Port Configuration Between the leased line modem and the SmartNode 2300 series device ANSI T.617 type of LMI packets have to be exchanged. In addition the keepalive interval has to be set to 20 seconds. Long data frames shall be fragmented into smaller pieces therefore fragmentation on Frame Relay has to be enabled. Figure 16-3: I P Context with logical IP interfaces bound to Ethernet port, serial port PVC 1 and PVC 2...
  • Page 146 Serial Port Configuration S t e p 3 The serial interface settings are configured. SN(cfg)#port serial 0 0 SN(prt-ser)[0/0]#shutdown SN(prt-ser)[0/0]#encapsulation framerelay SN(prt-ser)[0/0]#hardware-port x21 SN(prt-ser)[0/0]#port-type dte S t e p 4 The Frame Relay configuration is done next. Therefore we have to change to the Frame Relay configuration mode.

  • Page 147: Basic Ip Routing Configuration

    Basic IP Routing Configuration 17 BASIC IP ROUTING CONFIGURATION This chapter provides an overview of IP routing and describes the tasks involved in configuring static IP routing in SmartWare. For a complete description of the IP routing configuration commands in this chapter, refer to Chapter 15, “Interface Mode”, in the SmartWare Command Reference Guide. This chapter includes the following sections: •...

  • Page 148: Basic Ip Routing Configuration Task List

    Basic IP Routing Configuration 17.2 Basic IP Routing Configuration Task List To configure IP routes, perform the tasks described in the following sections. The tasks in the first two sections are required; the task in the remaining section is optional, but might be required for your application.

  • Page 149: Deleting Static Ip Routes

    Basic IP Routing Configuration The route is added to the routing database with the default metric 0. The router will forward packets to the 20.0.0 network via interface wan to the router on 172.17.100.2. 17.4 Deleting Static IP Routes The no form of the route command deletes a static IP route from the routing table. Pr oc edu re To delete one or more static IP routes from the routing table M od e...

  • Page 150: Examples

    Basic IP Routing Configuration --------------------------------------------------------------------- * 127.0.0.1/32 local * 172.16.40.77/32 local * 172.17.100.210/32 local * 172.17.100.0/24 local * 20.0.0.0/24 172.17.100.2 static * 172.16.0.0/16 local 17.6 Examples 17.6.1 Basic Static IP Routing Example Figure 17-1 shows an Internetwork consisting of three routers, a SmartNode device in the middle, and the four autonomous networks, with network addresses 10.1.5.0/16, 172.16.40.0/24, 172.17.100.0/24, and 10.2.5.0/16.
  • Page 151 Basic IP Routing Configuration --------------------------------------------------------------------- * 127.0.0.1/32 local * 172.16.40.1/24 local * 172.17.100.1/24 local * 172.17.100.0/24 local * 172.16.40.0/16 local * 10.1.5.10/32 172.16.40.2 static * 10.2.0.0/16 172.17.100.2 static Software Configuration Guide, Revision 1.03...

  • Page 152: Routing Information Protocol (Rip) Configuration

    Routing Information Protocol (RIP) Configuration 18 ROUTING INFORMATION PROTOCOL (RIP) CONFIGURATION This chapter provides an overview of the Routing Information Protocol (RIP) and describes the tasks involved in configuring RIP features within SmartWare. For a complete description of the RIP related commands in this chapter, see Chapter 15, “Interface Mode”...

  • Page 153: Rip Configuration Task List

    Routing Information Protocol (RIP) Configuration Routing Information Protocol (RIP) 1 is the most widely used routing protocol on IP networks. All gateways and routers that support RIP 1 periodically broadcast routing information packets. These RIP 1 packets contain information concerning the networks that the routers and gateways can reach as well as the number of routers/gateways that a packet must travel through to reach the receiving address.

  • Page 154: Enabling An Interface To Receive Rip

    Routing Information Protocol (RIP) Configuration Command Purpose Step 1 node(if-ip)[name]#rip supply Enables send RIP on interface name Ex a mp le : En abl in g Se nd RI P The following example shows how to enable send RIP on IP interface wan on a SmartNode. SN(cfg)#context ip router SN(ctx-ip)[router]#interface wan SN(if-ip)[wan]#rip supply...

  • Page 155: Specifying The Receive Rip Version

    Routing Information Protocol (RIP) Configuration Command Purpose Step 1 node(if-ip)[name]# rip send Selects send RIP version for interface name version {1 | 1compatible | 2} Ex amp le: Sp ec if yin g t he Se nd R IP The following example shows how to select send RIP version 1compatible on IP interface wan on a SmartNode.

  • Page 156: Enabling An Interface To Receive Rip

    Routing Information Protocol (RIP) Configuration • host for RIP learn host and • default for RIP learn default See the following sections on how to configure those two RIP learning mechanisms. Pr oc edu re To enable accepting of IP host and default routes received on an interface for RIP learning M od e Interface Command...

  • Page 157: Enabling Rip Auto Summarization

    Routing Information Protocol (RIP) Configuration • default for RIP default routes, • host for IP host routes, • self-as-default for self as RIP default routes and • static for static IP routes. Depending on the RIP announcing method the last option for the command in step 3 must be explicitly selected.

  • Page 158: Specifying The Default Route Metric

    Routing Information Protocol (RIP) Configuration E x a m p le : E n a b l i n g R I P A u t o S u m ma r iza t i o n The following example shows how to enable auto-summarization on IP interface wan on a SmartNode.

  • Page 159: Enabling The Poison Reverse Algorithm

    Routing Information Protocol (RIP) Configuration which that information originated. This behavior usually optimizes communications among multiple routers, particularly when links are broken. However, with non-broadcast networks (such as Frame Relay), situations can arise for which this behavior is less than ideal. For these situations, you might want to disable split horizon for RIP.

  • Page 160: Enabling Holding Down Aged Routes

    Routing Information Protocol (RIP) Configuration 18.15 Enabling Holding Down Aged Routes Holding down or locking aged routes learned from RIP packets on the specified interface helps, if an aged route cannot be refreshed to a non-aged status but must be deleted and then relearned. Enabling this function enhances the stability of the RIP topology in the presence of transients.

  • Page 161: Displaying Global Rip Information

    Routing Information Protocol (RIP) Configuration announce static: disabled announce default: disabled announce self-as-default: disabled route-holddown: enabled poison-reverse: disabled auto-summary: disabled split-horizon: disabled default-route-value: 0 -------------------------------------------------- 18.17 Displaying Global RIP Information SmartWare also support displaying global RIP information for the IP router context. Pr oc edu re To display the global RIP information M od e...

  • Page 162: Access Control List Configuration

    Access Control List Configuration 19 ACCESS CONTROL LIST CONFIGURATION This chapter provides an overview of IP Access Control Lists and describes the tasks involved in configuring them through the Inalp SmartWare, Release 2.00. For a complete description of the IP Access Control List commands in this chapter, refer to Chapter 7, “Profile ACL Mode”, in the SmartWare Command Reference Guide.

  • Page 163: When To Configure Access Lists

    Access Control List Configuration Figure 19-1: Using Traffic Filters to Prevent Traffic From Being Routed to a Network You can also use access lists to decide which types of traffic are forwarded or blocked at the router interfaces. For example, you can permit e-mail traffic to be routed but at the same time block all Telnet traffic.

  • Page 164: Access Control List Configuration Task List

    Access Control List Configuration • All access control lists have an implicit “deny all” at the end. A packet that does not match the criteria of the first statement is subjected to the criteria of the second statement and so on until the end of the access control list is reached, at which point the packet is dropped.

  • Page 165: Create An Access Control List Profile And Enter Configuration Mode

    Access Control List Configuration list offline within a configuration file and downloading the configuration file later via TFTP to your SmartNode device. 19.4 Create an Access Control List Profile and Enter Configuration Mode Pr oc edu re To create an IP access control list and enter access control list configuration mode M od e Administrator execution Command...

  • Page 166: Add An Icmp Filter Rule To The Current Access Control List Profile

    Access Control List Configuration M od e Profile access control list Command Purpose Step 1 node(pf-acl)[name]#deny ip {src src-wildcard | Creates an IP access of control list any | host src} {dest dest-wildcard | any | host entry that denies access defined dest} [cos group] according to the command options Where the syntax is:...
  • Page 167 Access Control List Configuration Pr oc edu re To create an ICMP access control list entry that permits access M od e Profile access control list Command Purpose Step 1 node(pf-acl)[name]#permit icmp {src src- Creates an ICMP access of control wildcard | any | host src} {dest dest-wildcard | list entry that permits access any | host dest} [msg name | type type | type...

  • Page 168: Add A Tcp, Udp Or Sctp Filter Rule To The Current Access Control List Profile

    Access Control List Configuration msg name The ICMP message name. The following are valid message names: administratively-prohibited, alternate-address, conversion-error, dod-host- prohibited, dod-net-prohibited, echo, echo-reply, general-parameter-problem, host-isolated, host-precedence-unreachable, host-redirect, host-tos-redirect, host- tos-unreachable, host-unknown, host-unreachable, information-reply, information-request, mask-reply, mask-request, mobile-redirect, net-redirect, net- tos-redirect, net-tos-unreachable, net-unreachable, network-unknown, no-room- for-option, option-missing, packet-too-big, parameter-problem, port-unreachable, precedence-unreachable, protocol-unreachable, reassembly-timeout, redirect,...
  • Page 169 Access Control List Configuration Command Purpose Step 1 node(pf-acl)[name]#permit {tcp | udp | sctp} Creates a TCP, UDP or SCTP {src src-wildcard | any | host src} [{eq port | gt access of control list entry that port | lt port | range from to}] {dest dest-wildcard permits access defined according | any | host dest} [{eq port | gt port | lt port | to the command options...

  • Page 170: Bind And Unbind An Access Control List Profile To An Ip Interface

    Access Control List Configuration dest-wildcar A wildcard for the destination address. See src-wildcard. host dest The address of a single destination host. Optional. Specifies that packets matched by this rule belong to a certain Class of Service (CoS). For detailed description of CoS configuration refer to chapter “Quality of Service Configuration”...
  • Page 171 Access Control List Configuration name The name of an access control list profile that has already been created using the profile acl command. This argument must be omitted in the no form Specifies that the access control list profile applies to incoming packets on this interface.

  • Page 172: Display An Access Control List Profile

    Access Control List Configuration 19.9 Display an Access Control List Profile The show profile acl command displays the indicated access control list profile. If no specific profile is selected all installed access control list profiles are shown. If an access control list is linked to an IP interface the number of matches for each rule is displayed.

  • Page 173: Examples

    Access Control List Configuration Step 2 node(ctx-ip)[router]#interface if-name Selects IP interface if-name for which access control list profile shall be debugged Step 3 node(if-ip)[if-name]#debug acl {in | out} [level] Enables access control list debug monitor with a certain debug level for the selected interface if-name Where the syntax is: Keyword...
  • Page 174 Access Control List Configuration Figure 19-2: Deny a Specific Subnet on an Interface The commands that have to be entered are listed below. The commands access the SmartNode device via a Telnet session running on a host with IP address 172.16.2.13, which accesses the SmartNode via IP interface lan.

  • Page 175: Cs Context Overview

    CS Context Overview 20 CS CONTEXT OVERVIEW This chapter gives an overview of the SmartWare circuit-switching (CS) context and its associated components and describes the tasks involved in its configuration. If you want understand the CS entity configuration you should read this chapter. You will get a basic understanding of how to set up a SmartNode to support voice calls.

  • Page 176: Cs Context Configuration Task List

    CS Context Overview The job of the CS context and its associated components is to route and establish a voice call. For example the signaling for dial-up circuits is routed and the corresponding voice call circuits are switched between PSTN interfaces and via VoIP interfaces to the VoIP gateways and the IP Context. This is explained in more detail in the configuration task 'Configure Call Routing'.
  • Page 177 CS Context Overview packaging the ISDN voice frames is not synchronized with the remote ISDN clock, this may result in bit errors. In case of fax applications not one page could be transmitted. • We need two ISDN ports, the first one for the ISDN phone, the second one for the public ISDN network.

  • Page 178: Configure General Cs Settings

    CS Context Overview Figure 20-2: Remote Office in an Enterprise Network You must not start configure the CS context and its components until you have finished planning your voice environment. The following chapters explain how to realize the planned voice environment into the SmartWare CS configuration.
  • Page 179 CS Context Overview In most cases the default value is suitable, so that you do not need to perform this configuration tasks. • Configure clock source: The packaging of the ISDN voice frames needs a reference clock. It is possible to generate this reference clock internally or get it from an external device (e.g.

  • Page 180: Configure Call Routing

    CS Context Overview SN(sys)#ic voice 1 SN(ic-voice)[1]#pcm code E1 SN(ic-voice)[1]#pcm law-select aLaw SN(ic-voice)[1]#exit 20.5 Configure Call Routing Calls through a SmartNode can be routed according to a set of routing criteria. The entity that manages call routing is called Session Router. Calls are routed from one CS interface to another. The Session Router determines the destination interface for every incoming call.

  • Page 181: Specify Call Routing

    CS Context Overview Interface names can be any arbitrary string with a maximum of 25 characters. For ease of identification the interface type can be a part of the name. For examples and information on how to create CS interfaces please refer to Chapter 21, “CS Interface Configuration”. 20.5.2 Specify Call Routing As described above, for basic call routing you can omit creating Session Router tables.

  • Page 182: Configure Isdn Ports

    CS Context Overview • Filters • DTMF Relay • Echo Canceler • Silence Compression • Voice Volume • Dejitter Buffer Parameters which can be overwriten on a CS interface are: • DTMF Relay • Echo Canceler • Silence Compression • Voice Volume •...

  • Page 183: Activate Cs Context Configuration

    CS Context Overview interface, during a call setup the first codec listed in the H.323 gateway which matches with the remote SmartNode is taken. For information how to configure the codecs for a H.323 connection refer to Chapter 25, “Gateway Configuration”. In H.323 there are two call signaling methods, 'direct call signaling' and 'gatekeeper routed call signaling'.
  • Page 184 CS Context Overview Pr oc edu re Show the CS context configuration, enable the Session Router debug monitor and activate the CS context M od e Context CS Command Purpose Step 1 node(ctx-cs)[switch]#show context Show the CS context configuration. Level could cs config level be 0..5.

  • Page 185: Example

    CS Context Overview 20.12 Example 20.12.1 Configure SmartNode in an Enterprise Network S i t u at io n Figure 20-4 shows an enterprise network with a SmartNode 2300 series with a BRI interface card in slot 2. A PBX, a LAN, the PSTN and the company network are connected. The VoIP protocol used is H.323.
  • Page 186 CS Context Overview • We synchronize the time of the SmartNode to the ISDN time. (Refer to section 'Configure General Settings'). To get useful system event logs it is very recommended to set the system time! • We need four ISDN ports, two for the PSTN and another two for the PBX. (Refer to section 'Configure ISDN Ports') •...
  • Page 187 CS Context Overview SN(sys)#exit SN(cfg)# C o n f i g u r e C a l l R o u t in g Next we create the PSTN interfaces and configure call routing: SN(cfg)#context cs SN(ctx-cs)[switch]#interface pstn PBX SN(if-pstn)[PBX]#routing dest-table calledNumberRouting SN(if-pstn)[PBX]#fallback dest-interface PublicPSTN SN(if-pstn)[PBX]#exit SN(ctx-cs)[switch]#interface pstn PublicPSTN...

  • Page 188: Sn(Cfg)#Context Cs

    CS Context Overview SN(prt-isdn)[2/0]#down SN(prt-isdn)[2/0]#channel-range 0 1 SN(prt-isdn)[2/0]#l2proto pp SN(prt-isdn)[2/0]#l3proto pss1 SN(prt-isdn)[2/0]#max-channels 2 SN(prt-isdn)[2/0]#uni-side net SN(prt-isdn)[2/0]#up SN(prt-isdn)[2/0]#exit SN(cfg)# SN(cfg)# SN(cfg)#port isdn 2 1 SN(prt-isdn)[2/0]#down SN(prt-isdn)[2/0]#channel-range 0 1 SN(prt-isdn)[2/0]#l2proto pp SN(prt-isdn)[2/0]#l3proto pss1 SN(prt-isdn)[2/0]#max-channels 2 SN(prt-isdn)[2/0]#uni-side net SN(prt-isdn)[2/0]#up SN(prt-isdn)[2/0]#exit SN(cfg)# SN(cfg)# SN(cfg)#port isdn 2 2 SN(prt-isdn)[2/0]#down SN(prt-isdn)[2/0]#channel-range 0 1 SN(prt-isdn)[2/0]#l2proto pp...

  • Page 189: Sn(Cfg)#Show Context Cs Config

    CS Context Overview SN(if-h323)[Company~]#exit SN(ctx-cs)[switch]# SN(ctx-cs)[switch]#exit SN(cfg)# In addition we have to use the VoIP profile by the gateway: SN(cfg)#gateway h323 h323 SN(gw-h323)[h323]#use voip-profile H323VoIPProfile SN(gw-h323)[h323]#exit SN(cfg)# Act ivat e CS Context Conf iguration Prior to activating our configuration we use two 'show' commands to display part of our configuration: SN(cfg)#show context cs config Following session-router configuration sets are available:...

  • Page 190: Sn(Cfg)#Debug Session-Router 5

    CS Context Overview SN(cfg)#gateway h323 SN(gw-h323)[gw_name]#no shutdown SN(gw-h323)[gw_name]#exit SN(cfg)#debug session-router 5 SN(cfg)#context cs SN(ctx-cs)[switch]#no shutdown SN(ctx-cs)[switch]#02:47:59 > Loading interfaces... 02:47:59 > Resolving interface references interfaces... 02:47:59 > Classifier is resolving interface references... 02:47:59 > Loading session router tables... 02:47:59 > Resolving routing table references within routing tables...
  • Page 191 CS Context Overview use tone-set-profile default interface pstn PBX routing dest-table CalledNumberRouting fallback dest-interface PublicPSTN bind port 2 0 bind port 2 1 interface pstn PublicPSTN routing dest-table CalledNumberRouting bind port 0 1 interface h323 CompanyOfficeA routing dest-table CalledNumberRouting remoteip 146.86.130.11 codec g711alaw64k interface h323 CompanyOfficeB routing dest-table CalledNumberRouting...
  • Page 192 CS Context Overview down channel-range 0 1 l2proto pp l3proto pss1 max-channels 2 uni-side net port isdn 2 2 down channel-range 0 1 l2proto pp l3proto dss1 max-channels 2 uni-side usr port isdn 2 3 down channel-range 0 1 l2proto pp l3proto dss1 max-channels 2 uni-side usr...

  • Page 193: Cs Interface Configuration

    CS Interface Configuration 21 CS INTERFACE CONFIGURATION This chapter provides an overview of interfaces in the CS context and describes the tasks involved in configuring them. For detailed information on command syntax and usage guidelines for the commands listed in the configuration tasks refer to Chapter 16, " Context CS Mode", in the SmartWare Command Reference Guide.

  • Page 194: Cs Interface Configuration Task List

    CS Interface Configuration Figure 21-1: CS int erfaces on the CS context A PSTN interface is a CS interface type bound to a physical ISDN or POTS port. If more than one port is bound to a PSTN interface, a line hunt group is created automatically. H.323 and ISoIP interfaces are CS interface types that provides voice over IP settings in addition to the general CS interface parameters.

  • Page 195: Create And Configure Cs Interfaces

    CS Interface Configuration 21.3 Create and Configure CS interfaces To configure CS interfaces you have first to enter in the CS context mode. Once entered you can create and configure your required interface by entering the CS interface configuration mode and specify the parameters.

  • Page 196: Configure Call Routing

    CS Interface Configuration SN(if-pstn)[PublicA~]#no interface pstn PublicPSTN SN(ctx-cs)[switch]#interface pstn <?> <name> Interface name Existing interface PublicAccess Existing interface callapp Existing interface SN(ctx-cs)[switch]# 21.4 Configure Call Routing SmartWare offers two levels of call routing, 'basic interface routing' and 'advanced session routing'. Basic interface routing allows you to forward all incoming calls on a CS interface to a destination CS interface.

  • Page 197: Configure Digit Collection

    CS Interface Configuration SN(ctx-cs)[switch]# 21.5 Configure Digit Collection The SmartWare CS context supports overlap dialling on all interfaces. Some of the connected devices (PBX, ISDN network, remote gateways and gatekeepers) may however require bloc sending of the dialed number. SmartWare offers three options to collect overlap dialed digits and forward them in a single call setup message.

  • Page 198: Configure Direct Call Signaling On Voip Interfaces

    CS Interface Configuration E x amp le: C o nf i gu re D ig i t C o l lec t i on In the following example the SmartNode sends the bloc of numbers either when the asterisk character '*' is received or after 4 seconds have elapsed since the last dialed digit. SN(if-h323)[h323_0]#digit-collection timeout 4 SN(if-h323)[h323_0]#digit-collection terminating-char * 21.6 Configure Direct Call Signaling on VoIP Interfaces...

  • Page 199: Specify The Port Address On Voip Interfaces

    CS Interface Configuration 21.7 Specify the Port Address on VoIP interfaces ISoIP and the Q.931 tunneling in H.323 can support ISDN services which use D-channel broadcast messages, such as call back and call waiting services. These features are related to physical ports on the remote gateway and not to a specific called party number.

  • Page 200: Bind Pstn Interfaces To Pstn Ports And Create Line Hunt Groups

    CS Interface Configuration Step 1 node(if-type)[if-name]#portaddress Specify the port address for a H.323 or IsoIP address interface. E x amp le: S p ec if yin g a P ort A dd re ss The following example shows how to set the port address to value 5 for a H.323 interface and enable Q.931 tunneling to use this feature in an H.323 network.

  • Page 201: Examples

    CS Interface Configuration 21.9 Examples 21.9.1 V5 Carrier Access Figure 21-4 shows a V5 carrier access scenario. The association between the subscriber ISDN port and the switch port is achieved using a port address. This port address creates a virtual extension line which supports the complete ISDN services and supplementary services Figure 21-4:...
  • Page 202 CS Interface Configuration SN(if-isoip)[IpBackb~]#exit SN(ctx-cs)[switch]#interface pstn ISDNPhone101 SN(if-pstn)[ISDNPho~]#routing dest-interface IpBackbone101 SN(if-pstn)[ISDNPho~]#exit SN(ctx-cs)[switch]#interface isoip IpBackbone102 SN(if-isoip)[IpBackb~]#routing dest-interface ISDNPhone102 SN(if-isoip)[IpBackb~]#exit SN(ctx-cs)[switch]#interface pstn ISDNPhone102 SN(if-pstn)[ISDNPho~]#routing dest-interface IpBackbone102 SN(if-pstn)[ISDNPho~]#exit SN(ctx-cs)[switch]# Next we specify the remote IP address for direct call signaling and set the port address: SN(ctx-cs)[switch]#interface isoip IpBackbone101 SN(if-isoip)[IpBackb~]#remoteip 172.21.1.1 SN(if-isoip)[IpBackb~]#portaddress 101...

  • Page 203: Q.sig Pbx Networking

    CS Interface Configuration 02:47:59 > IpBackbone102 02:47:59 > ISDNPhone101 02:47:59 > ISDNPhone102 02:47:59 > Following routing tables have been loaded: 02:47:59 > Following functions have been loaded: 02:47:59 > Following number replacement tables have been loaded: SN(ctx-cs)[switch]# 21.9.2 Q.SIG PBX Networking The example in Figure 21-5 shows a Q.SIG PBX network scenario.
  • Page 204 CS Interface Configuration SN#configure SN(cfg)#context cs SN(ctx-cs)[switch]#interface h323 IPBackbone_1 SN(if-h323)[IPBackb~]#routing dest-interface PBX_1 SN(if-h323)[IPBackb~]#exit SN(ctx-cs)[switch]#interface h323 IPBackbone_2 SN(if-h323)[IPBackb~]#routing dest-interface PBX_2 SN(if-h323)[IPBackb~]#exit SN(ctx-cs)[switch]#interface pstn PBX_1 SN(if-pstn)[PBX_1]#routing dest-interface IPBackbone_1 SN(if-pstn)[PBX_1]#exit SN(ctx-cs)[switch]#interface pstn PBX_2 SN(if-pstn)[PBX_2]#routing dest-interface IPBackbone_2 SN(if-pstn)[PBX_2]#exit SN(ctx-cs)[switch]# Next we configure the remote IP address for direct call signaling and specify the port addresses: SN(ctx-cs)[switch]#interface h323 IPBackbone_1 SN(if-h323)[IPBackb~]#remoteip 172.21.16.1 SN(if-h323)[IPBackb~]#portaddress 1...
  • Page 205 CS Interface Configuration After you have finished the CS configuration you must enable the CS context. Prior to activating the CS context we enable the debug Session Router monitor to display the loading of the CS context. SN(ctx-cs)[switch]#debug session-router 5 SN(ctx-cs)[switch]#no shutdown SN(ctx-cs)[switch]# 02:47:59...

  • Page 206: Session Router Configuration

    Session Router Configuration 22 SESSION ROUTER CONFIGURATION This chapter provides an overview of Session Router tables and number manipulation functions and describes the tasks involved in configuring the Session Router in SmartWare. For detailed information on syntax and usage guidelines for the commands listed in the configuration tasks, refer to Chapter 16, “Context CS Mode”...

  • Page 207: Routing Table Structure

    Session Router Configuration Figure 22-1: Direct Call Routing vs. Advanced Session Routing Due to the tree search algorithm implemented in the Session Router very large routing tables can be scanned very quickly with minimal impact on the call setup delay. The SmartWare Session Router supports the following routing criteria: •...

  • Page 208: Warning

    Session Router Configuration dest-interface Specifies the CS interface (name) to be used as the outgoing interface. <function> Is the name of a number manipulation function to be executed before the call setup is forwarded to the next routing table or the destination interface Note: To support broadcast features the routing table needs a default entry ! 22.2 Warning The Session Router allows you to solve practically any call routing and number manipulation...

  • Page 209: Configure The Entry Table On Circuit Interfaces

    Session Router Configuration that you need multiple tables of the same type to achieve your goals. On the other hand an alternative sequence may help you to reduce the number of tables or the size of each table while still achieving the set goal.

  • Page 210: Create A Called Party Number Routing Table

    Session Router Configuration Type Format Description Example unknown as dialled with all leading zeros or other prefix numbers 0041 31 985xxxx national (area code) (local extension number) 31 985xxxx international (country code) (area code) (local extension number) 41 31 985xxxx Table 22-1: ISDN number types The missing prefix in the national and international number types can complicate the Session Router configuration.

  • Page 211: Create A Calling Party Number Routing Table

    Session Router Configuration Command Purpose Step 1 node(ctx-cs)[switch]#called-party tbl-name Create a CdPN routing table tbl-name key dest-interface if-name for destination interface if-name or destination table tbl-name by entering the first line. node(ctx-cs)[switch]#called-party tbl-name key dest-table tbl-name Step 2 Repeat step 1 to add lines for additional table entries.

  • Page 212: Create A Bearer Capability Routing Table

    Session Router Configuration SN(ctx-cs)[switch]#calling-party exts 523 dest-interface breakout SN(ctx-cs)[switch]#calling-party exts 525 dest-interface breakout SN(ctx-cs)[switch]#calling-party exts 572 dest-interface DefAcc 22.6.5 Create a Bearer Capability Routing Table The bearer capability table is used to route calls based on the bearer capability field in the ISDN setup message.

  • Page 213: Create A Time Of Day Routing Table

    Session Router Configuration 22.6.6 Create a Time of Day Routing Table The time table is used to route calls based upon the current system time during one day, i.e. an 24hr. period from midnight to midnight. Times are matched within the ranges defined in the time routing table.

  • Page 214: Create A Date Routing Table

    Session Router Configuration E x amp le: D a y o f W ee k R o ut ing Ta b le SN(ctx-cs)[switch]#weekday DayTable1 sat dest-table LeastCost SN(ctx-cs)[switch]#weekday DayTable1 sun dest-table LeastCost SN(ctx-cs)[switch]#weekday DayTable1 default dest-interface VoIPCarrierA 22.6.8 Create a Date Routing Table The Date table is used to route calls according to the current system date.

  • Page 215: Create A Number Replacement Table

    Session Router Configuration Command Purpose Step 1 node(ctx-cs)[switch]#number- Create a number manipulation manipulation name {cdpn|cnpn} function identified by a “speaking” {add|remove|replace|truncate} param name. Specify if the function acts on the CdPN or the CnPN. Specify the action: • add digits in front of number •...

  • Page 216: Create Complex Number Manipulation Functions

    Session Router Configuration Ex amp le: C reat e a Tr an s lat ion T ab le SN[switch]#translation-table PISNtoDDI 550 250 SN[switch]#translation-table PISNtoDDI 551 251 SN[switch]#translation-table PISNtoDDI 552 252 SN[switch]#translation-table PISNtoDDI 553 253 Corresponding number manipulation function: Input: 550 Result: 250 SN[switch]# number-manipulation SwapDDI cdpn replace PISNtoDDI 22.7.2 Create Complex Number Manipulation Functions Complex functions allow to combine number manipulation functions which need to be executed in...

  • Page 217: Activate The Session Router Configuration

    Session Router Configuration Command Purpose Step 1 node(ctx-cs)[switch]#delete routing-table Delete a specific routing table tablename Step 2 node(ctx-cs)[switch]#delete function Delete a specific number manipulation functionname function Step 3 node(ctx-cs)[switch]#delete all-routing- Delete all routing tables in the CS tables context configuration Step 4 node(ctx-cs)[switch]#delete all Delete all routing tables, functions and...

  • Page 218: Example

    Session Router Configuration 22.10 Example 22.10.1 Enterprise Network with Local Breakout and IP Carrier Access Consider the following Enterprise Network. Figure 22-2: Session Routing Example Network Note that the SmartNodes in this Network may be owned and operated by the Company or by a Service Provider.
  • Page 219 Session Router Configuration The requirements for the Session Router can be summarized as: • Route ISDN data calls to the local breakout • Route inter-site calls to the opposite SmartNode (Node A to Node B and vice versa) • Route international calls to Carrier “Melon” •...
  • Page 220 Session Router Configuration Figure 22-3: C S Context and Session Router elements We assume that the CS interfaces have already been created and configured. So we can start directly with the Session Router elements. Since the command sequence is quite long it is usefull to create the configuration offline and download it using TFTP.
  • Page 221 Session Router Configuration SN(ctx-cs)[switch]#interface pstn pbx_a SN(if-pstn)[pbx_a]#routing dest-table ISDNservice SN(if-pstn)[pbx_a]#fallback dest-interface local_ba SN(if-pstn)[pbx_a]#exit SN(ctx-cs)[switch]#interface h323 node_b SN(if-h323)[node_b]#routing dest-interface pbx_a SN(if-h323)[node_b]#exit SN(ctx-cs)[switch]#interface isoip node_c SN(if-isoip)[node_c]#routing dest-interface pbx_a SN(if-isoip)[node_c]#exit The configuration is now complete. Prior to activating the configuration enable the Session Router debug monitor to check the loading of the Session Router elements.

  • Page 222: Tone Configuration

    Tone Configuration 23 TONE CONFIGURATION This chapter gives an overview of SmartWare Release 2.00 call-progress-tone profiles and tone-set profiles and describes the tasks involved in their configuration. For detailed information on syntax and usage guidelines for the commands listed in the Configuration Tasks, refer to Chapter 12, “Profile Tone Set Mode”...

  • Page 223: Tone Configuration Task List

    Tone Configuration Figure 23-1: CS Context with Tone Profiles 23.2 Tone Configuration Task List To configure call progress tones, perform the tasks described in the following sections. • Configure Call-Progress-Tone Profiles • Configure Tone-Set profiles • Use Tone-Set Profiles • Generation of Local In-Band Tones •...
  • Page 224 Tone Configuration Figure 23-2: Tone Duration Parameters Pr oc edu re To configure a call-progress-tone profile M od e Configure Command Purpose Step 1 node(cfg)#profile call-progress-tone name Create the tone profile name and enters the tone profile configuration mode. Use speaking names such as “dial-US” or “busy-CH”.

  • Page 225: Configure Tone-Set Profiles

    Tone Configuration Step 9 node(pf-callp)[name]#off2 duration Specify duration off2 between 0 and 5000 [ms], set to zero for a continuous tone E x amp le: C o nf i gu r ing a C a l l Pro gr es s Ton e Pr of i le The following example shows how to configure the Swiss dial tone.

  • Page 226: Use Tone-Set Profiles

    Tone Configuration 23.5 Use Tone-Set Profiles There is a default tone set named 'default', which is used to generate call progress tones in the call set-up process. If you want to override this default configuration, configure the call-progress-tone and tone-set profiles as described above and “use” the tone-set profile in the CS context. The profile used in the CS context applies to all PSTN interfaces on the CS context.

  • Page 227: Show Call-Progress-Tone And Tone-Set Profiles

    Tone Configuration Command Purpose Step 1 node(sys)#local-inband-tones Force the SmartNode to generate local in-band tones (dial, alerting, busy) for all PSTN interfaces Ex amp le: Co nf igu re local in-band tones The following example shows how to configure local in-band tones SN(sys)#local-inband-tones 23.7 Show Call-Progress-Tone and Tone-Set Profiles Use the show command to display the call-progress-tone profiles as well as the tone-set profiles.

  • Page 228: Example

    Tone Configuration DTMF low frequency level: -4 dBm DTMF duration: 80 ms DTMF interspace: 80 ms ------------------------------------------------ Call progress Tone mapping: dialtone -> defaultDialtone alertingtone -> defaultAlertingtone busytone -> defaultBusytone SN(cfg)# 23.8 Example 23.8.1 Tone Configuration The following example shows the commands used to configure a tone-set profile for UK and apply it to the CS context.
  • Page 229 Tone Configuration SN(cfg)#context cs SN(ctx-cs)[switch]#use tone-set-profile UK Software Configuration Guide, Revision 1.03...

  • Page 230: Isdn Port Configuration

    ISDN Port Configuration 24 ISDN PORT CONFIGURATION This chapter provides an overview of SmartNode ISDN ports and describes the tasks involved in configuring ISDN ports in SmartWare. For detailed information on syntax and usage guidelines for the commands listed under Configuration Tasks refer to Chapter 19, “Interface ISoIP Mode”, in the SmartWare Command Reference Guide.

  • Page 231: Possible Smartnode Port Configurations

    ISDN Port Configuration Figure 24-1: ISDN Reference Points The S reference point is on the subscriber interface. This is the typical 4-wire connection between an ISDN phone and an ISDN PBX. Be aware that many ISDN PBX vendors use non-standard proprietary 2-wire interfaces to connect the Terminals to the PBX.

  • Page 232: Isdn Uni Signalling

    ISDN Port Configuration Figure 24-2: Intergration in IASDN Access Lines 24.1.3 ISDN UNI signalling ISDN is a User-Network Interface (UNI) signaling protocol with a user and a network side. The user side is implemented in ISDN terminals (phones, terminal adapters, etc.) while the network side is implemented in the exchange switches of the network operator.

  • Page 233: Warnings

    ISDN Port Configuration Figure 24-3: ISDN Signaling Side 24.2 Warnings Port activation deactivation ISDN ports can only be configured when in the down state. The first configuration task explains how to disable and enable ISDN ports for configuration. When the port is down all active calls on the port are dropped.

  • Page 234: Configure Common Bri And Pri Parameters

    ISDN Port Configuration Step 3 Configure settings according to the sections below Step 4 (prt-isdn) [slot/port]#up Activate the port. At the end of the configuration procedure re- enabling the port activates the configuration changes. Ex amp le: Sh utt ing Dow n and En ab ling a n ISDN p ort The following example shows how to enter the configuration mode for ISDN port 0/0, disable and activate the port.

  • Page 235: Configure Bri Port Parameters

    ISDN Port Configuration Step 1 (prt-isdn)#l3proto dss1 Specify the ISDN layer 3 protocol. The ISDN layer 3 is the network signalling protocol. SmartWare ISDN ports support Euro- (prt-isdn)#l3proto pss1 ISDN (E-DSS1) and Q.SIG (PSS1) signalling. The layer 3 signalling must correspond to the connected ISDN equipment or network.

  • Page 236: Configure Pri Port Parameters

    ISDN Port Configuration M od e Port ISDN Command Purpose Step 1 node(prt-isdn)[slot/port]#l2proto Specify the ISDN layer 2 protocol Make sure the connected ISDN device operates the same layer 2 protocol! node(prt-isdn)[slot/port]#l2proto 24.7 Configure PRI Port Parameters Of the 32 time slots in an ISDN PRI, slot 0 is reserved for synchronisation, slot 16 is used for signaling, and the remaining 30 slots can be used as B-channels for dial-up circuits.
  • Page 237 ISDN Port Configuration Step 4 node(prt-isdn)[slot/port]#channel- Specify channel hunting hunting down The hunting mode defines how the available time slots are filled. The cyclic modes use a ’round-robin’ implementation. The ’up’ and node(prt-isdn)[slot/port]#channel- ’down’ modes define whether the time slots are hunting down-cyclic filled at the lowest or highest available slot, i.e.

  • Page 238: Example

    ISDN Port Configuration 24.8 Example Assume the scenario as illustrated in Figure 24-4: Figure 24-4: PBX connected to ISDN port 1/1 Configure the ISDN port 1/1 to work as a Q-SIG master port but clock-slave and allow a maximum of eight parallel B-channel connections.

  • Page 239: Gateway Configuration

    Gateway Configuration 25 GATEWAY CONFIGURATION This chapter provides an overview of ISoIP and H.323 gateways and describes the tasks involved in configuring them. For detailed information on command syntax and usage guidelines for the commands listed in the configuration tasks refer to Chapter 20, “Gateway ISoIP Mode”, and Chapter 21, “Gateway H.323 Mode”...

  • Page 240: Gateway Configuration Task List

    Gateway Configuration Figure 25-1: Gateways between IP and CS contexts 25.2 Gateway Configuration Task List This chapter describes the configuration of the H.323 and IsoIP gateways. Some parameters could be configured in the gateway configuration mode and overwritten in another configuration mode. For example the default value for the voice codec for ISoIP connections is set in the gateway configuration mode and could be overwritten in the ISoIP interface.

  • Page 241: Configure Used Codec For An Isoip Connection

    Gateway Configuration accommodate different target compression rates such as 8, 6.4 and even 5.3 kbps. Note that this bit rate is for audio only. When transmitting packetized voice over the network, protocol overhead (such as RTP/UDP/IP/Ethernet) is added on top of this bit rate, resulting in a higher actual data rate.

  • Page 242: Configure Used Codec For An H.323 Connection And Enable Fast Connect

    Gateway Configuration Step 2 node(gw-isoip)[isoip]#codec codec Specify the default codec and the packet size of [packet-length] the transmitted voice packet for all calls over the ISoIP gateway. Step 3 node(gw-isoip)[isoip]#exit Optional: Only if necessary: Change to interface Step 4 node(cfg)#context cs configuration mode to overwrite the default Step 5 node(ctx-cs)[switch]#interface...
  • Page 243 Gateway Configuration (prefered or exclusive) are without effect. interface with no codec specified. 2. If no interface is present with no codec specified the call is rejected. Table 25-1: Codec Selection in H.323 Similarly for an H.323 connection it is possible to specify the packet size of the transmitted voice packets, and additionally announce length capability for received voice packets to the remote VoIP device.

  • Page 244: Configure Registration Authentication Service (Ras) In An H.323 Gateway

    Gateway Configuration SN(cfg)#gateway h323 h323 SN(gw-h323)[h323]#codec g711alaw64k 20 40 SN(gw-h323)[h323]#codec g723_6k3 20 40 SN(gw-h323)[h323]#codec g729 20 40 SN(gw-h323)[h323]#faststart SN(gw-h323)[h323]#exit SN(cfg)#context cs SN(ctx-cs)[switch]#interface h323 H323 SN(if-h323)[H323]#codec g711alaw64k SN(if-h323)[H323]# 25.4 Configure Registration Authentication Service (RAS) in an H.323 Gateway As mentioned in previous chapters a call setup can use direct call signaling and gatekeeper routed call signaling.

  • Page 245: Enable Q.931 Tunneling For An H.323 Connection

    Gateway Configuration Step 2 node(gw-h323)[h323]#alias h323-id Sets the identifier(s) for registration on the name gatekeeper with a string with a phone number node(gw-h323)[h323]#alias e164 number Step 3 Repeat step 2 to add more that one alias to the configuration. Step 4 node(gw-h323)[h323]#ras Enable the RAS protocol for gatekeeper registration and client resolution...

  • Page 246: Enable The Gateway Configuration

    Gateway Configuration 25.6 Enable the Gateway Configuration Finally, before enabling the gateway SmartWare must know which IP interface belongs to which gateway. In ISoIP this is detected automatically, in H.323 the gateway must be bound to the respective IP interface. In order to become active the ISoIP or H.323 gateway must be enabled.

  • Page 247: Examples

    Gateway Configuration 25.7 Examples 25.7.1 Branch Offices in an Enterprise Network Figure 25-2 shows a branch office in Linn and a branch office in Zurich connected to the main office in Berne over ISoIP. Zurich and Berne are linked over an 2 Mbit/s direct copper DSL wire and use the voice codec G.711 for this high-rate connection.
  • Page 248 Gateway Configuration SN>enable SN#configure SN(cfg)#context cs SN(ctx-cs)[switch]#interface pstn PBX SN(if-pstn)[PBX]#routing dest-table CdPnRouting SN(if-pstn)[PBX]#fallback dest-interface PublicAccess SN(if-pstn)[PBX]#exit SN(ctx-cs)[switch]#interface pstn PublicAccess SN(if-pstn)[PublicA~]#routing dest-table CdPnRouting SN(if-pstn)[PublicA~]#exit SN(ctx-cs)[switch]# SN(ctx-cs)[switch]#interface isoip BackboneLinn SN(if-isoip)[Backbon~]#remoteip 195.183.25.32 SN(if-isoip)[Backbon~]#routing dest-table CdPnRouting SN(if-isoip)[Backbon~]# SN(ctx-cs)[switch]#interface isoip BackboneZurich SN(if-isoip)[Backbon~]#remoteip 195.183.25.33 SN(if-isoip)[Backbon~]#routing dest-table CdPnRouting SN(if-isoip)[Backbon~]#exit SN(ctx-cs)[switch]# The configuration steps for the VoIP profile and the ISDN Ports are omitted.

  • Page 249: Gatekeeper In Lan Based Telephony

    Gateway Configuration 02:47:59 > Following functions have been loaded: 02:47:59 > Following number replacement tables have been loaded: SN(ctx-cs)[switch]#exit SN(cfg)#gateway isoip isoip SN(gw-isoip)[isoip]#no shutdown SN(gw-isoip)[isoip]#exit SN(cfg)# 25.7.2 Gatekeeper in LAN Based Telephony Figure 25-3 illustrates LAN based telephony with a gatekeeper. We configure the SmartNode for gatekeeper routed call signaling, and in addition we use fast connect to set up a call.
  • Page 250 Gateway Configuration The configuration steps for the VoIP profile and the ISDN Ports are omitted. Next we configure the SmartNode for 'gatekeeper routed call signaling'. Therfore we specify the alias, the gatekeeper discovery and enable the registration authentication service (RAS). Additionally we enable fast connect.

  • Page 251: Voip Profile Configuration

    VoIP Profile Configuration 26 VOIP PROFILE CONFIGURATION This chapter gives an overview of SmartWare VoIP profiles, how they are used and describes the tasks involved in VoIP profile configuration. For detailed information on syntax and usage guidelines for the commands listed in the configuration tasks refer to Chapter 13, “Profile VoIP Mode”...

  • Page 252: Voip Profile Configuration Task List

    VoIP Profile Configuration Figure 26-1: VoIP profile association 26.2 VoIP Profile Configuration Task List The various components can be configured in the VoIP profile mode and often in the CS interface mode also. Generally the configuration in the VoIP profile applies to all calls going through that gateway.

  • Page 253: Enable Dtmf Relay

    VoIP Profile Configuration Pr oc edu re To create a VoIP Profile and enter the VoIP profile configuration mode M od e Configure Command Purpose Step 1 node(cfg)#profile voip name Create a VoIP profile with name name and enter VoIP profile configuration mode Step 2 node(pf-voip)[name]#...

  • Page 254: Enable Echo Canceller

    VoIP Profile Configuration Command Purpose Step 1 node(pf-voip)[name]#dtmf-relay Enable DTMF relay Step 2 node(pf-voip)[name]#exit Optional: Change to CS interface configuration mode to Step 3 node(cfg)#context cs overwrite the settings in the VoIP profile in a Step 4 node(ctx-cs)[switch]#interface specific CS interface isoip name node (ctx-cs)[switch]#interface h323 name...

  • Page 255: Enable Silence Compression

    VoIP Profile Configuration M od e Profile VoIP Command Purpose Step 1 node(pf-voip)[name]#echo- Enable echo canceller canceller Step 2 node(pf-voip)[name]#exit Optional: Change to CS interface configuration mode to Step 3 node(cfg)#context cs overwrite the settings in the VoIP profile in a Step 4 node(ctx-cs)[switch]#interface specific CS interface...

  • Page 256: Configure Voice Volume

    VoIP Profile Configuration overwrite the settings in the VoIP profile in a Step 4 node(ctx-cs)[switch]#interface specific CS interface isoip name node(ctx-cs)[switch]#interface h323 name Step 5 node(if-type)[if-name]#no silence- Disable silence compression and comfort noise compression on a specific interface Ex amp le: En ab le Sile nc e Co mp re ss io n The following example shows how to enable the silence compression for the VoIP profile.

  • Page 257: Configure Dejitter Buffer (Advanced)

    VoIP Profile Configuration Pr oc edu re To configure voice volume M od e Profile VoIP Command Purpose Step 1 node(pf-voip)[name]#voice-volume Set the voice volume to value in dB value Step 2 node(pf-voip)[name]#exit Optional: Change to CS interface configuration mode to Step 3 node(cfg)#context cs overwrite the settings in the VoIP profile in a...
  • Page 258 VoIP Profile Configuration Figure 26-5: Jitter and Dejitter Buffer Since the receiving decompression algorithm (voice decoder) requires fixed spacing between the packets, the typical solution is to implement a dejitter buffer within the gateway. The dejitter buffer deliberately delays incoming packets in order to present them to the decompression algorithm at fixed spacing.
  • Page 259 VoIP Profile Configuration Figure 26-6: Adaptive versus Fixed Dejitter Buffer The adaptive buffer automatically adapts to the network delay variation characteristics and in general yields the best results. The manual fixed buffer is useful only if you have specific information about your network, such as jitter period, etc.

  • Page 260: Enable/Disable Filters (Advanced)

    VoIP Profile Configuration overwrite the settings in the VoIP profile in a Step 5 node(ctx-cs)[switch]#interface specific CS interface isoip name node(ctx-cs)[switch]#interface h323 name Step 6 node(if-type)[if-name]#dejitter- Specify the dejitter buffer for a specific H.323 or mode mode ISoIP interface Step 7 node(if-type)[if-name]#dejitter- Specify max delay for the dejitter buffer for the max-delay max-delay...

  • Page 261: Show Voip Profile Configuration And Assign It To A Voip Gateway

    VoIP Profile Configuration Note: Filtering occurs only with G.723 and G.729 CODECs and could only be configured for an VoIP profile and not for an H.323 or ISoIP interface. Pr oc edu re To disable post and high-pass filter M od e Profile VoIP Command Purpose...
  • Page 262 VoIP Profile Configuration E x amp le: S h ow Vo I P P r of i le C on f ig ura t ion an d A ss ig n it t o a V o I P gat ew a y This example shows how to show all defined VoIP profiles and how to use the VoIP profile ISoIPProfile by the ISoIP gateway.

  • Page 263: Example

    VoIP Profile Configuration max bit rate: 9600 bit/s hdlc: disabled DTMF settings: DTMF relay: enabled encoder mode: muted SN(pf-voip)[ISoIPPr~]#exit SN(cfg)#gateway isoip isoip SN(gw-isoip)[isoip]#use voip-profile ISoIPProfile SN(gw-isoip)[isoip]# 26.11 Example 26.11.1 Home Office in an Enterprise Network Figure 26-8 is an example of a home office in an enterprise network. The connection bandwith amounts to 128 kbit/s and is very low quality.
  • Page 264 VoIP Profile Configuration SN(cfg)#profile voip Wire128kbit SN(pf-voip)[Wire128~]#silence-compression SN(pf-voip)[Wire128~]#dtmf-relay SN(pf-voip)[Wire128~]#dejitter-mode adaptive SN(pf-voip)[Wire128~]#dejitter-max-delay 100 SN(pf-voip)[Wire128~]#voice-volume 20 SN(pf-voip)[Wire128~]#exit SN(cfg)# Afterwards we show the configuration and configure the ISoIP gateway to use the VoIP profile. As aformetioned fax and data settings may be ignored. SN(cfg)#show profile voip Wire128kbit Profile Wire128kbit ------------------------------------------------------------------...

  • Page 265: Voip Debugging

    VoIP Debugging 27 VOIP DEBUGGING This chapter helps you to localize a system component that is responsible for faults during operation of a SmartNode device. This chapter provides debugging strategies to help you locating the origin of an error, and describes the necessary debug and show commands. The emphasis is on VoIP debugging.

  • Page 266: Warning

    VoIP Debugging 27.3 Warning Enabling some or all debug monitors may degrade system performance (IP routing, call signaling). To avoid inadvertent permanent system performance degradation make sure all monitors are switched off once the configuration is debugged and running. 27.4 Debugging Task List Depending on problem that has occurred one or more of the following debugging tasks should be performed.

  • Page 267: Verify Circuit Switch Connectivity

    VoIP Debugging Reply from 172.16.40.122: Time <10ms Reply from 172.16.40.122: Time <10ms Ping statistics for 172.16.40.122: Packets: Sent 5, Received 5, Lost 0 (0% loss), RTT: Minimum <10ms, Maximum <10ms, Average <10ms 27.6 Verify Circuit Switch Connectivity The following commands makes possible to establish voice calls between two endpoints without additional voice devices such as voice phones.
  • Page 268 VoIP Debugging SmartNode 2: Route calls from ISoIP interface ISOIP_IF to interface callap and enable debug monitor. SN2>enable SN2#configure SN2(cfg)#context cs SN2(ctx-cs)[switch]#interface isoip ISOIP_IF SN2(if-isoip)[ISOIP_IF]#routing dest-interface callapp SN2(if-isoip)[ISOIP_IF]#exit SN2(ctx-cs)[switch]#no shutdown SN2(ctx-cs)[switch]#exit SN2(cfg)#exit SN2# SN2#debug call 5 SmartNode 1: Enable debug monitor and dial SN1#debug call 5 SN1# SN1#call 21 dial ISOIP_IF...
  • Page 269 VoIP Debugging SN2#call 8000 accept SN2#14:13:31 CALL > [8000] SENT [080007] CONNECT (Generic Q.931) 14:13:31 CALL > [8000] GOT [08000F] CONNECT ACKNOWLEDGEMENT (Generic Q.931) SN2# SmartNode 1: See debug monitor output and show call sessions 14:13:30 CALL > [0021] GOT [080007] CONNECT (Generic Q.931) 14:13:30...

  • Page 270: Debug Isdn Data

    VoIP Debugging SN2#14:14:50 CALL > [8000] GOT [080045] DISCONNECT (Generic Q.931) [0803038090] Cause : normal call clearing transit network - CCITT - Q.931 14:14:50 CALL > [8000] SENT [08004D] RELEASE (Generic Q.931) [0803038090] Cause : normal call clearing transit network - CCITT - Q.931 14:14:50 CALL >...

  • Page 271: Debug Isoip Data

    VoIP Debugging M od e Administrator execution Command Purpose Step 1 node#show gateway h323 config Show the actual H.323 configuration Step 2 node#show gateway h323 status Show the actual status of the H.323 stack. Step 2 node#debug gateway h323 signaling [detail- Enable the H.323 debug monitor to get level] information about the transposed...

  • Page 272: Debug Voice Over Ip Data

    VoIP Debugging M od e Administrator execution Command Purpose Step 1 node#show session-control subsystems Show registered subsystems [detail-level] Step 2 node#show session-control sessions [detail- Show open VoIP data sessions level] Step 3 node#debug session-control [detail-level] Enable the session-control debug monitor to show exchanged data between ISDN and VoIP protocols.

  • Page 273: How To Submit Trouble Reports To Inalp

    VoIP Debugging information from the system supervisor such as memory full, task failed etc. Every reason for an unexpected reboot of the system is stored in this log. Pr oc edu re To check system and supervisor event logs M od e Administrator execution Command Purpose...
  • Page 274 VoIP Debugging N.B.: In order to correlate the protocol monitors at the different levels in SmartWare (e.g. ISDN layer3 and Session-Router monitors) run the monitors concurrently. • Network Traffic Traces: In certain cases it may be helpful to have a trace of the traffic on the IP network in order to inspect packet contents.

  • Page 275: Snmp Configuration

    • SNMP Configuration Task List • Using the AdventNet SNMP Utilities • Standard SNMP Version 1 Traps • Inalp Networks enterprise specific Traps • Inalp Networks private MIBs • Examples 28.1 Simple Network Management Protocol (SNMP) 28.1.1 Background The Simple Network Management Protocol (SNMP) is an application-layer protocol that facilitates the exchange of management information between network devices.

  • Page 276: Snmp Basic Commands

    SNMP Configuration An NMS executes applications that monitor and control managed devices. NMSs provide the bulk of the processing and memory resources required for network management. One or more NMSs must exist on any managed network. 28.1.3 SNMP Basic Commands Managed devices are monitored and controlled using four basic SNMP commands: read, write, trap, and traversal operations.

  • Page 277: Identification Of The Smartnode 1000 And 2000 Series Via Snmp

    28.2 Identification of the SmartNode 1000 and 2000 series via SNMP All models of the Inalp Networks SmartNode 1000 and 2000 series devices have their unambiguous value assigned sysObjectID (.iso.org.dod.internet.mgmt.mib-2.system.sysObjectID) object. Table 28-1 lists the returned value when reading the sysObjectID object for each SmartNode model.

  • Page 278: Setting Basic System Information

    SNMP Configuration • Setting basic system information (Required) • Setting access community information (Required) • Setting allowed host information (Required) • Specifying the default SNMP trap target (Optional) • Displaying SNMP related information (Optional) 28.6 Setting Basic System Information The implementation of the MIB-II system group is mandatory for all systems. By default, an SNMP agent is configured to have a value for any of these variables and responds to get commands from a NMS.
  • Page 279 In the following example the system information is set for later access via SNMP. See Figure 28-1 for a typical MIB browser application accessing these MIB-II system group objects representing the system information. SN>enable SN#configure SN(cfg)#system contact "Lorenz Born, Phone 533" SN(cfg)#system location "Office, 3rd floor, Inalp Networks" SN(cfg)#system hostname "SN2300-01" SN2300-01(cfg)# Software Configuration Guide, Revision 1.03...

  • Page 280: Setting Access Community Information

    SNMP Configuration After entering a host name the prompt on the CLI no longer displays the IP address of the Ethernet port over which the Telnet session is running but shows the newly entered host name. 28.7 Setting Access Community Information SNMP makes use of one or more labels called community strings to delimit groups of objects (variables) that can be viewed or modified on a device.

  • Page 281: Setting Allowed Host Information

    SNMP Configuration Ex amp le: Set ting A cc ess C o mmu n it y In f o r mat ion In the following example the SNMP communities for the default community public with read-only access and the undisclosed community Not4evEryOne with read/write access are defined. Only these valid communities have access to the information from the SNMP agent running on the respective SmartNode 1000 or 2000 series device.

  • Page 282: Displaying Snmp Related Information

    E x amp le: D is p la yin g S N M P R e la t ed I nf o rmat i on This example shows how to display SNMP configuration information. SN2300-01(cfg)#show snmp SNMP Information: hostname : SN2300-01 location : Office, 3rd floor, Inalp Networks contact : Lorenz Born, Phone 533 Hosts: 172.16.224.44 security-name public...

  • Page 283: Using The Adventnet Snmp Utilities

    The MIB tree component enables us to traverse through the tree, view the loaded MIBs and learn the definition for each node. The AdventNet MibBrowser allows loading additional MIB files in the text format, e.g. the Inalp Networks enterprise specific MIBs used for SmartNode 1000 or 2000 series device management.

  • Page 284: Using The Trapviewer

    SNMP Configuration There are three ways in which the primary window of the MibBrowser can be viewed. It can be viewed with the result display, MIB description panel or multi-variable bind panel in the right frame. The view can be altered by three ways. •...
  • Page 285 SNMP Configuration The TrapViewer has a table that depicts the trap information, the common parameters text fields where necessary information has to be entered and other options such as Start, Stop, Trap Details, Delete Trap and ParserEditor. Follow these steps to work on the Trap Viewer and to know more about the available options: •...
  • Page 286 SNMP Configuration Figure 28-4: AdventNet Trap Details Window of TrapViewer The various details available in the Trap Details window are listed in Table 28-2 below: Trap Details Description The TimeStamp is a 32-bit unsigned value indicating the number of centiseconds that have elapsed since the (re)start of the SNMP agent and TimeStamp the sending of the trap.

  • Page 287: Standard Snmp Version 1 Traps

    SNMP Configuration Trap Details Description This field shows the Severity or the intensity of the trap. They could be 0- Severity All, 1-Critical, 2-Major, 3-Minor, 4-warning, 5-Clear and 6-info. Entity The source IP address from which the Trap was sent is depicted here. RemotePort This field reveals the port on which the Trap was sent by the originator.
  • Page 288 SNMP Configuration ::= 3 Note: The linkUp trap is not sent if any of the ISDN ports has come up. authenticationFailure TRAP-TYPE ENTERPRISE snmp DESCRIPTION "An authenticationFailure trap signifies that the sending protocol entity is the addressee of a protocol message that is not properly authenticated.

  • Page 289: Sntp Client Configuration

    SNTP Client Configuration 29 SNTP CLIENT CONFIGURATION This chapter describes how to configure Simple Network Time Protocol (SNTP) client. For a complete description of the SNTP related commands in this chapter, refer to Chapter 5, “System Mode” chapter of the SmartWare Command Reference Guide. This chapter includes the following sections: •...

  • Page 290: Defining Sntp Client Operating Mode

    SNTP Client Configuration Step 1 node(cfg)#sntp-client server primary ip- Enters the SNTP primary server IP address address Step 2 node(cfg)#sntp-client server secondary ip- Enters the SNTP secondary server IP address address E x amp le: S e l ect in g S N T P T ime S er ve r s In the following example an internal SNTP time server (172.16.1.10) is selected as primary and utcnist.colorado.edu (128.138.140.44) as secondary SNTP time server.

  • Page 291: Defining Sntp Local Udp Port

    SNTP Client Configuration SN(cfg)#sntp-client operating-mode multicast 29.5 Defining SNTP Local UDP Port The communication between an SNTP client and its the primary or secondary SNTP time server uses UDP. The UDP port number assigned to SNTP is 123, which should be used in both the source port (on the SmartNode) and destination port (on SNTP time server) fields in the UDP header.

  • Page 292: Defining Sntp Client Poll Interval

    SNTP Client Configuration E x amp le: D is ab l i ng t he SNT P C l ie nt O per at io n SN(cfg)#no sntp-client 29.7 Defining SNTP Client Poll Interval Specifies the seconds between each SNTP client request in unicast or anycast mode. This SNTP client poll interval can be defined to be within in the range from 1 to 4’294’967’295.

  • Page 293: Defining The Sntp Client Anycast Address

    SNTP Client Configuration SN#configure SN(cfg)#sntp-client gmt-offset + 02:00:00 There is a short form notation supported as shown in the following example. SN(cfg)#sntp-client gmt-offset + 2 29.9 Defining the SNTP Client Anycast Address Anycast mode is designed for use with a set of cooperating servers whose addresses are not known beforehand by the SmartNode.

  • Page 294: Enabling And Disabling Local Clock Offset Compensation

    SNTP Client Configuration 29.10 Enabling and Disabling Local Clock Offset Compensation The Simple Network Time Protocol (SNTP) Version 4 is an adaptation of the Network Time Protocol (NTP) that is used to synchronize computer clocks in the Internet. While not necessary in a conforming SNTP client, in unicast and anycast modes it is highly recommended that the transmit timestamp in the request is set to the time of day according to the client clock in NTP timestamp format.

  • Page 295: Showing Sntp Client Related Information

    SNTP Client Configuration Ex amp le: En ab ling th e SNT P Clie nt Ro ot De la y C o mp en sat ion SN(cfg)#sntp-client root-delay-compensation E x amp le: D is ab l i ng t he SNT P C l ie nt Ro ot D el a y C o mp ens at ion SN(cfg)#no sntp-client root-delay-compensation 29.12 Showing SNTP Client Related Information During set-up and operation of the SNTP client, displaying the information and status of the SNTP...

  • Page 296: Recommended Public Sntp Time Servers

    SNTP Client Configuration E x amp le: E n ab le t he S N T P D e bu g M on it or The following example shows how to enable the SNTP debug monitor and some typical debug information.

  • Page 297: Other Public Ntp Primary (Stratum 1) Time Servers

    SNTP Client Configuration nist1-sj.glassey.com 207.126.103.204 California time-a.nist.gov 129.6.15.28 Maryland time-b.nist.gov 129.6.15.29 Maryland time-a.timefreq.bldrdoc.gov 132.163.4.101 Colorado time-b.timefreq.bldrdoc.gov 132.163.4.102 Colorado time-c.timefreq.bldrdoc.gov 132.163.4.103 Colorado time-d.timefreq.bldrdoc.gov 132.163.4.104 Colorado time.nist.gov 192.43.244.18 Colorado time-nw.nist.gov 131.107.1.10 Washington Table 25-1: Time Servers operated by NIST L eg en d 1.

  • Page 298: Additional Information On Ntp And A List Of Other Ntp Servers

    SNTP Client Configuration Geographic Coordinates: 49.573N 11.028E (from Meinberg GPS 166) Synchronization: NTP V3 primary (DCF77 PZF receiver (<50us)), Sun E3000 SunOS 5.6 Service Area: Germany/Europe Access Policy: open access, pick one of ntp{0,1,2}.fau.de Contact: The Timekeepers (time@informatik.uni-erlangen.de) Note: IP addresses are subject to change; please use DNS DE ntps1-0.cs.tu-berlin.de (130.149.17.21) Location: Technische Universitaet Berlin, D-10587 Berlin, FRG Geographic Coordinates: 52.518N 13.326E...

  • Page 299: Appendix A

    Appendix A 30 APPENDIX A 30.1 Configuration Mode Overview Figure 30-1 illustrates the configuration modes hierarchy. Each box contains the mode name, the enter command and the prompt in a telnet console. Additionally all relationships between the instances of the components through bind and link commands are illustrated. For example an instance of 'port ethernet' must be bound to an 'IP interface' through the command '[no] bind interface <name>...

  • Page 300: Smartware 2.0 Command Summary

    Appendix A Figure 30-1: Configuration Modes and Bind and Link Commands Overview 30.2 SmartWare 2.0 Command Summary 30.2.1 Introduction The SmartWare 2.00 commands are collected in configuration modes as illustrated in Figure 30-1. Following all commands in the configuration modes are listed. The configuration modes are listed in order as shown in Figure 30-1.

  • Page 301: Command Summary

    Appendix A Figure 30-2: EBNF Syntax 30.2.2 Command Summary This command summary is valid for SmartWare, Release 2.00, Build 22037. Commands in future SmartWare releases or builds may be different. The information provided in this chapter is subject to change without notice. operator_exec [no] debug call [<detail>...
  • Page 302 Appendix A show dsp {<slot> | (statistics <slot> ) | (channel statistics <slot> ) | (sw-version <slot> ) | (test- result <slot> ) } show framerelay [pvc <print-dlci> ] show history show ip interface [<interface_name> ] [router ] show ip route show log show napt interface <ip_interface_name_show>...
  • Page 303 Appendix A [no] debug sntp client [no] debug voip-data [<detail> ] copy {{running-config|factory-config|startup-config|system:running-config} | {cli:|preferences:} | <src> | <src> } {{running-config|startup-config|system:running-config|flash:} | {cli:|preferences:} | <dest> | <dest> } erase {{startup-config} | {cli:|preferences:} | <config> } reload session-control close <session> show {nvram: | {running-config|factory-config|startup-config|system:running-config} | {cli:|preferences:} | <config>...
  • Page 304 Appendix A [no] snmp community <community> {ro|rw} [no] snmp host <ipAddress> security-name <community> [no] snmp target <ipAddress> security-name <community> [no] sntp-client [no] sntp-client local-clock-offset [no] webserver [port <port> ] [lang {en|de} ] cli version <version> clock set <time> sntp-client anycast-address <ip_anycast-address> [port <sntp_port> ] sntp-client gmt-offset {+|-} <time_gmtoffset>...
  • Page 305 Appendix A ic_voice ic voice <slot> pcm {(law-select {aLaw | uLaw } ) | (code {E1 | T1 } ) } exit profile_acl [no] profile acl <profile_name> {permit|deny} {(ip {any | (host <src_ip> ) | (<src_ip> <src_wildcard> ) } {any | (host <dst_ip> ) | (<dst_ip>...
  • Page 306 Appendix A [no] queue-limit <value> [no] rate-limit <value> [header-length <option-value> ] [no] set ip dscp <value> [no] set ip precedence <value> [no] set ip tos <value> [no] set layer2 cos <value> debug queue reset mode {shaper | burst-shaper | wfq | burst-wfq } exit source [no] source {(class <source-name>...
  • Page 307 Appendix A [no] profile napt <napt-profile_name> [no] icmp default <host> [no] static {udp|tcp} <port> <host> exit profile_call-progress-tone [no] profile call-progress-tone <name> high-frequency <high_frequency> high-frequency-level {mute | <high_frequency_level> } low-frequency <low_frequency> low-frequency-level {mute | <low_frequency_level> } off1 <off1> off2 <off2> on1 <on1> on2 <on2>...
  • Page 308 Appendix A [no] dejitter-shrink-speed <dejitter_shrink_speed> [no] dtmf-relay [no] echo-canceller [no] high-pass-filter [no] post-filter [no] silence-compression [no] voice-volume <voice_volume> exit context_ip context ip [router ] [no] route <destaddr> <destmask> {<gwaddr> | <interface> } [<metric> ] multicast-send default-interface <ip_interface> exit interface [no] interface <ip_interface_name> [no] cos <cos_group>...
  • Page 309 Appendix A [no] rip split-horizon [no] rip supply [no] use profile acl <acl_profile_name> {in|out} [no] use profile napt <napt-profile_name> [no] use profile service-policy <arbiter-name> {in | out } ipaddress {unnumbered | (<ip_address> <ip_mask> ) } mtu <mtu> rip default-route-value <default_route_value> rip receive version {1|2|1or2} rip send version {1|2|1compatible} exit...
  • Page 310 Appendix A interface_pstn [no] interface pstn <if-name> [no] bind port <slot> <port> [no] digit-collection {(timeout [<val> ] ) | (terminating-char <val> ) | (nr-length <val> ) } [no] fallback {(dest-table <name> ) | (dest-interface <name> ) } [no] routing {(dest-table <name> ) | (dest-interface <name> ) } [no] use tone-set-profile <name>...
  • Page 311 Appendix A exit interface_isoip [no] interface isoip <if-name> [no] bind gateway isoip [no] codec {transparent|g711alaw64k|g711ulaw64k|g723_5k3|g723_6k3|g729|g726_16k|g726_24k |g726_32k|g726_40k|g727_16k|g727_24k|g727_32k|netcoder_6k4|netcoder_9k6} [<tx_packet_length> ] [no] digit-collection {(timeout [<val> ] ) | (terminating-char <val> ) | (nr-length <val> ) } [no] dtmf-relay [no] echo-canceller [no] fallback {(dest-table <name> ) | (dest-interface <name> ) } [no] portaddress <portaddress>...
  • Page 312 Appendix A [no] codec {g711alaw64k | g711ulaw64k | g723_6k3 | g723_5k3 | g729 | transparent | g726_16k | g726_24k | g726_32k | g726_40k | g727_16k | g727_24k | g727_32k | netcoder_6k4 | netcoder_9k6 } [<txlen> ] [no] shutdown use voip-profile <profile_name> exit gateway_h323 gateway h323 [h323 ]...
  • Page 313 Appendix A port_serial port serial <slot> <port> [no] shutdown encapsulation {framerelay } hardware-port {v35 | x21 } exit framerelay framerelay [no] keepalive [<keepalive> ] lmi-type {ansi | gof | itu } exit [no] pvc <dlci> encapsulation {rfc1490 } [no] bind interface <ip_interface_name> [router ] [no] shutdown exit port_isdn...
  • Page 314 Appendix A [no] smart-disconnect {from-isdn-calls | to-isdn-calls } [no] up channel-hunting {up | down | up-cyclic | down-cyclic } channel-numbering {etsi | pss1-old } clock-mode {master | slave } l2proto {pp | pmp } l3proto {dss1 | pss1 } uni-side {net | usr } exit Software Configuration Guide, Revision 1.03...

  • Page 315: Appendix B

    Appendix B 31 APPENDIX B 31.1 Internetworking Terms and Acronyms Abreviation Meaning Numeric 10BaseT Ethernet Physical Medium ATM Adaptive Layer Available Bit Rate Alternating Current Advice of Charge Asynchronous Transfer Mode audio 3.1 ISDN Audio Service up to 3.1 kHz audio 7.2 ISDN Audio Service up to 7.2 kHz Basic Rate Access...
  • Page 316 Appendix B Abreviation Meaning DSLAM Digital Subscriber Line Access Multiplexer Digital Signal Processor DTMF Dual Tone Multifrequency Transmission Standard at 2.048 Mb/s E-DSS1 ETSI Euro ISDN Standard Embedded File System Exchange Termination Ethernet Frequently Asked Questions Federal Communication Commission Frame Relay G.711 ITU-T Voice encoding standard G.723...
  • Page 317 Appendix B Abreviation Meaning Information Transfer Bearer Capability L2TP Layer Two Tunneling Protocol Local Area Network Least Cost Routing LDAP Lightweight Directory Access Protocol Light Emitting Diode Local Exchange Line Termination MGCP Media Gateway Control Protocol MIB II Management Information Base II Modem Modulator –...
  • Page 318 Appendix B Abreviation Meaning Primary Rate Interface PSTN Public Switched Telephone Network pt-mpt point-to-multi point pt-pt point-to-point Permanent Virtual Circuit Password Power Quality of Service RIPv1 Routing Information Protocol Version 1 RIPv2 Routing Information Protocol Version 2 RJ-45 Western Connector Type Route Table Manager Real-time Protocol SN-connection for Trunk Line...
  • Page 319 Appendix B Abreviation Meaning TCP/IP Transport Control Protocol / Internet Protocol Terminal Equipment TFTP Trivial File Transfer Protocol Unspecified Bit Rate UD 64 Unrestricted Data 64 kb/s User Datagram Protocol Variable Bit Rate Virtual Channel Identifier VoIP Voice over Internet Protocol Virtual Path Identifier Wide Area Network Software Configuration Guide, Revision 1.03...

  • Page 320: Appendix C

    Appendix C 32 APPENDIX C 32.1 Used IP Ports in SmartWare 2.0 Component Port Description H.323 UDP 1719 RAS for gatekeeper connection TCP 1720 Call signaling port for H.323 (adjustable) ISoIP UDP 1106 Voice data UDP 1107 Voice statistics TCP 1106 Signaling control messages NAPT TCP 8000-15999...

  • Page 321: Available Voice Codecs In Smartware 2.00

    Appendix C 32.2 Available Voice Codecs in SmartWare 2.00 Protocol Codec Net Band- Min. Com- Used Band- Usage width per pression width per Call (kbps) Delay (ms) Call (kbps) ISoIP G.711 A- Uncompressed, best voice quality, Europan audio- digitizing G.711 u- Uncompressed, best voice quality, American audio- digitizing...

This manual is also suitable for:

Smartware release 2.00

Table of Contents