1. Manuals
  2. Brands
  3. Inalp Networks Manuals
  4. Software
  5. SmartWare Release 2.10
  6. Software configuration manual

Inalp Networks SmartWare Release 2.10 Software Configuration Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Software
Configuration
Guide
SmartWare Release 2.10
Customer Deliverable Documentation
Part Number 80-0151
English
Revision 1.00, October 31, 2002

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the SmartWare Release 2.10 and is the answer not in the manual?

Questions and answers

Related Manuals for Inalp Networks SmartWare Release 2.10

Summary of Contents for Inalp Networks SmartWare Release 2.10

  • Page 1 Software Configuration Guide SmartWare Release 2.10 Customer Deliverable Documentation Part Number 80-0151 English Revision 1.00, October 31, 2002...
  • Page 2 Legal Notice Software Configuration Guide Release 2.10, Revision 1.00...

  • 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 ....................16 Introduction............................16 SmartWare Architecture Terms and Definitions................16 Applications ........................23 Introduction............................23 Carrier Networks..........................23 Enterprise Networks ........................24 LAN Telephony ..........................25 System Overview ......................27 Introduction............................27 SmartNode Hardware Platforms....................28 SmartWare Embedded Software ....................29 SmartView Management Center Tools..................30 Configuration Concepts....................

  • Page 5: Table Of Contents

    Table of Contents 6.13 Display Account Information ......................47 6.14 Switching to Another Account ....................... 47 6.15 Checking Identity and Connected Users..................48 6.16 End a Telnet or Console Port Session .................... 49 Establishing Basic IP Connectivity................50 Introduction ............................50 IP Context Selection and Basic Interface Configuration Tasks...........
  • Page 6 Table of Contents 11.3 Planning your IP Configuration .....................86 11.3.1 IP Interface Related Information ....................86 11.3.2 Serial Interface Related Information ..................86 11.3.3 QoS Related Information ......................87 11.4 Configuring Ethernet and Serial Ports...................87 11.5 Creating and Configuring IP Interfaces..................87 11.6 Configuring NAPT ...........................87 11.7 Configuring Static IP Routing......................88 11.8...
  • Page 7 Table of Contents 15.4 Link Scheduler Configuration Task List ..................113 15.5 Defining the Access Control List Profile ..................113 15.5.1 Packet Classification....................... 113 15.5.2 Creating an Access Control List ................... 114 15.6 Assigning Bandwidth to Traffic Classes ..................115 15.7 Creating a Top-Level Service Policy Profile ................
  • Page 8 Table of Contents 18.5 Enabling an Interface to Receive RIP ...................152 18.6 Specifying the Send RIP Version ....................152 18.7 Specifying the Receive RIP Version .....................153 18.8 Enabling RIP Learning ........................153 18.9 Enabling an Interface to Receive RIP ...................154 18.10 Enabling RIP Announcing......................154 18.11 Enabling RIP Auto Summarization..................155 18.12...
  • Page 9 Table of Contents 21.4 Defining SNTP Client Operating Mode ..................187 21.5 Defining SNTP Local UDP Port....................188 21.6 Enabling and Disabling the SNTP Client ..................188 21.7 Defining SNTP Client Poll Interval....................189 21.8 Defining SNTP Client Constant Offset To GMT ................ 189 21.9 Defining the SNTP Client Anycast Address................
  • Page 10 Table of Contents CS Interface Configuration................... 236 25.1 Introduction.............................236 25.2 CS Interface Configuration Task List ...................237 25.3 Create and Configure CS interfaces .....................237 25.4 Configure Call Routing........................238 25.5 Configure Digit Collection ......................239 25.6 Configure Direct Call Signaling on VoIP Interfaces ..............240 25.7 Specify the Port Address on VoIP interfaces ................241 25.8...
  • Page 11 Table of Contents 28.7 Configure PRI Port Parameters ....................279 28.8 Example ............................280 POTS Port Configuration..................282 29.1 Introduction ............................ 282 29.1.1 POTS Signaling ........................282 29.2 Warnings ............................282 29.3 Shutdown and Enable POTS Ports....................283 29.4 Configure Common POTS Port Parameters ................283 29.5 POTS Port Configuration Task List....................
  • Page 12 Debug Session Control Data .....................333 33.11 Debug Voice Over IP Data ......................334 33.12 Check System Logs........................334 33.13 How to Submit Trouble Reports to Inalp Networks AG............334 Appendix A......................336 34.1 Configuration Mode Overview ....................336 34.2 SmartWare 2.10 Command Summary ..................337 34.2.1...

  • Page 13: About This Guide

    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 Release 2.10 command set, see the SmartWare Command Reference Guide.

  • Page 14: How To Read This Guide

    Chapter 11, “IP Context Overview” and • Chapter 24, “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 15 Terms and Definitions Software Configuration Guide Release 2.10, Revision 1.00...

  • Page 16: 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.10. This chapter includes the following sections: • Introduction • SmartWare Architecture Terms and Definitions 1.1 Introduction The Software Configuration Guide for SmartWare, Release 2.10 contains many terms that are relate to specific networking technologies areas such as LAN protocols, WAN technologies, routing, Ethernet,...
  • Page 17 Terms and Definitions Term or Definition Meaning Build The released software is organized as builds. Each build has its unique identification. A build is part of a release and has software bug fixes. See also release. Call Routing Calls through SmartNode can be routed based on a set of routing criteria.
  • Page 18 Terms and Definitions Term or Definition Meaning Dejitter Buffer To compensate variable network delays, SmartWare includes a dejitter buffer. Storing packets in a dejitter buffer before they are transferred to the local ISDN equipment, e.g. telephone, SmartWare converts a variable delay into a fixed delay, giving voice a better quality.
  • Page 19 (CLIP) or call waiting (CW). See also Q.SIG ISoIP ISDN over IP is patent pending solution of Inalp Networks AG to carry ISDN services over IP networks. Jitter Jitter is the variation on packets arriving on a SmartNode.
  • Page 20 Terms and Definitions Term or Definition Meaning Network Management System System responsible for managing at least part of a network. An NMS is generally a reasonably powerful and well- equipped computer, such as an engineering workstation. NMSs communicate with agents to help keep track of network statistics and resources.
  • Page 21 Terms and Definitions Term or Definition Meaning Profile A profile provides configuration shortcutting. A profile contains specific settings which can be used on multiple contexts, interfaces or gateways. PSTN Public Switched Telephone Network. Contains ISDN and POTS Q.931 Tunneling Q.931 tunneling is able to support ISDN services and Q.SIG over an IP network.
  • Page 22 Terms and Definitions Term or Definition Meaning Startup Configuration The startup configuration is stored in the persistent memory (nvram:) and is always copied for execution to the running configuration in the volatile memory (system:) after a system start-up. Switching Engine Part of the SmartNode hardware which allows software controlled circuit switching of circuit ports.

  • Page 23: Applications

    LAN telephony 2.1 Introduction The Inalp Networks AG SmartNode product family consists of highly flexible multi-service IP network devices, which fit a range of networking applications. To simplify the description of these applications they have grouped into three application scenarios: 1.

  • Page 24: Enterprise Networks

    Applications Figure 2-1: Typical Carrier Network Application with a SmartNode 2300 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.

  • Page 25: Lan Telephony

    Applications Figure 2-2: Typical Enterprise Network with a SmartNode 1400 and 2300 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.
  • Page 26 Applications Figure 2-3: Typical LAN Telephony System with a SmartNode 1400 GW Software Configuration Guide Release 2.10, Revision 1.00...

  • Page 27: 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 28: Smartnode Hardware Platforms

    The SmartNode 2000 series with on-board ports plus expansion slots for individual interface configurations using a range of optional interface cards (IC). The basic system model of a Inalp Networks AG SmartNode is depicted in Figure 3-2. Both the SmartNode 1000 and the 2000 series have three main components: •...

  • Page 29: 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 30: Smartview Management Center Tools

    System Overview 3.4 SmartView Management Center Tools SmartWare provides two standard element management interfaces: • The Command Line Interface (CLI), which supports full online configuration and monitoring access for the operator • The SNMP agent and MIB, with an emphasis on inventory and alarm management for integration in a 3 party Network Management System (NMS) With the aid of configuration files and TFTP up and downloads, the SmartNodes can also be...

  • Page 31: Configuration Concepts

    Profiles and use commands 4.1 Introduction and Overview The Inalp Networks AG SmartNodes are multi-service network devices that offer high flexibility for the inter-working of circuit switched and packet routed networks and services. In order to consistently support a growing set of functions, protocols and applications, SmartWare configuration is based on a number of abstract concepts that represent the various SmartWare components.

  • Page 32: Contexts And Gateways

    Configuration Concepts 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. For example: • A CS context contains the circuit-switching functions of the SmartNode.

  • Page 33: Ports And Circuits

    Configuration Concepts In order for the higher-layer protocols to become active, you must associate an interface with a physical port or circuit. This association is referred to as a binding in SmartWare. Refer to the “Bindings” section later in this chapter for more information. In Figure 4-1, the IP context shows three interfaces and the CS context shows four interfaces.

  • Page 34: Use Commands

    Configuration Concepts 4.4.2 Use Commands Use commands form the association between profiles and contexts, gateways or interfaces. For example when a profile is used in a context all the configuration settings in that profile become active within the context. Software Configuration Guide Release 2.10, Revision 1.00...

  • Page 35: 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 36: 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> Software Configuration Guide Release 2.10, Revision 1.00...

  • Page 37: Navigating The Cli

    Command Line Interface In the operator exec mode, 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 38 Command Line Interface Mode Name Commands Used to Access Command-Line Prompt mode ic-voice ic voice <slot> command from system node(ic-voice) [<slot>]# mode context_ip context ip [router] command from node(ctx-ip) [router]# configure mode interface interface <name> command from node(if-ip) [<name>]# context_ip mode context_cs context cs [switch] command from node(ctx-cs) [switch]#...

  • Page 39: Command Editing

    Command Line Interface Mode Name Commands Used to Access Command-Line Prompt tone from configure mode Table 5-1: Command Mode Entry and Prompts 5.2 Command Editing 5.2.1 Command Help To see a list of all CLI commands available within a mode, type a question mark “?” at the system prompt in the mode of interest.
  • Page 40 Command Line Interface Esc f Move cursor forward one word. Esc b Move cursor backward one word. Ctrl-a Move cursor to beginning of line. Ctrl-e Move cursor to end of line. Ctrl-k Delete to end of line. Ctrl-u Delete to beginning of line. Ctrl-d Delete character.

  • Page 41: Accessing The Command Line Interface

    6 ACCESSING THE COMMAND LINE INTERFACE The Inalp Networks AG 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 42: Accessing Via The Console Port

    Accessing the 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 (labeled CONSOLE) with a serial cable (see Figure 6-1).

  • Page 43: Telnet Procedure

    Accessing the Command Line Interface Figure 6-2: Setup For Initial Configuration via an Ethernet Port The host must have a valid IP address configured in the same subnet as the SmartNode. Table 6-1 shows the default IP address and net mask of the Ethernet ports of the SmartNode. Port IP Address Network Mask...

  • Page 44: Log On To Smartware

    Accessing the Command Line Interface 6.6 Log On to SmartWare Accessing your SmartNode via the local console port or via a Telnet session will open a login screen. The following description of the login process is based on a Telnet session scenario but is identical when accessing via the local console port.

  • Page 45: Configure Operators And Administrators

    Accessing the Command Line Interface Right now you are probably asking yourself, “How am I going to remember that?” It’s easy, the password above is an acronym taken from: “3 blind mice see how they run”. Making a good password is that easy! But please, don’t use the above example password for your SmartNode device.

  • Page 46: Create An Administrator Account

    Accessing the Command Line Interface Ex amp le: C reat e a n O pe rat or Ac co unt The following example shows the commands used to add a new operator account with a login name “support” and a matching password of “s4DF&qw”. The changed configuration is then saved. SN>enable SN#configure SN(cfg)#operator support password s4DF&qw...

  • Page 47: Display Account Information

    Accessing the Command Line Interface Command Purpose Step 1 node>show version cli Displays CLI version E x amp le: D is p la yin g t he C L I Ve rs i on The following example shows how to display the version of the current running SmartWare CLI on your device, if you start from the operator execution mode.

  • Page 48: Checking Identity And Connected Users

    Accessing the Command Line Interface Command Purpose Step 1 node>su account-name Change to the user user account account-name Ex amp le: Sw itch ing t o An oth er Ac co unt The following example shows how to change from your current user account to an administrator account, starting from operator execution mode.

  • Page 49: End A Telnet Or Console Port Session

    Accessing the Command Line Interface Note: The “*” character identifies the identity of the user executing the who command. ID represents the ID of the account. State represents the actual running condition of the user, which can be logout, login, exec and config. Used in operator execution mode: SN>who You are operator support...

  • 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 Interface Configuration”...

  • 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 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. The IP interfaces are identified by the name. Pr oc edu re To displays IP interface information M od e...

  • Page 54: Examples

    Establishing Basic IP Connectivity 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 net mask 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,...

  • Page 56: System Image Handling

    System Image Handling Task List 8.1 Introduction All Inalp Networks AG 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 SmartNode reset button; see the Hardware Configuration Guide. The startup, or user-specific configuration, is also stored in nvram. The factory configuration is read-only, and is contained in the persistent memory in the logical region nvram: of the SmartNode. It can be used if no user-specific configuration is available to start- up SmartWare with a minimal functionality.

  • Page 58: Boot Procedure And Bootloader

    System Image Handling 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. Shortly before SmartWare is fully started up the configuration “startup-config”...

  • Page 59: Factory Configuration

    System Image Handling 8.4 Factory Configuration Inalp Networks AG SmartNodes are delivered with a factory configuration stored in the logical region nvram: of the memory. It is used to initially parameterize the network and component settings of SmartWare, which make sense at the very beginning. Moreover if a SmartWare is malfunctioning resetting to the initial state is done by reloading the factory configuration.

  • Page 60: 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 AG 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 61: Copy Driver Software From A Network Server To Flash Memory

    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 AG 2001-10-24 /IC-4BRVoIP_Vx_R2.00_BUILD24028 Software Configuration Guide Release 2.10, Revision 1.00...
  • Page 62 System Image Handling +/flash/bin/pmc000216a6 4¼— This script file defines how the driver software image file is to be handled and where it is to be stored. Note: You cannot download any driver software image file without an appropriate script file. Pr oc edu re To download a driver software image file M od e...

  • Page 63: Configuration File Handling

    Configuration File Handling Task List 9.1 Introduction All Inalp Networks AG 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 64 Configuration File Handling command to the command shell for execution. If, during operation of a SmartNode, you enter a command using the CLI of SmartWare, you alter the running configuration accordingly. In other words you are modifying a live, in-service system configuration. Figure 9-1 below shows the characteristics of a configuration file.

  • Page 65: Factory Configuration

    Refer back to Chapter 1, “Terms and Definitions”, to learn more about configuration file types. 9.2 Factory Configuration Inalp Networks AG SmartNodes are delivered with a factory configuration in the logical region nvram: of the SmartNode that is used to initially parameterize the network and component settings of SmartWare that are most useful when starting initially.

  • Page 66: 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 AG factory. 9.4 Configuration File Handling Task List This Section describes how to create, load, and maintain configuration files.
  • Page 67 Configuration File Handling Figure 9-2: Local Memory Regions in SmartWare As shown in Figure 9-2 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 68: Replacing The Startup Configuration With A Configuration From Flash Memory

    Configuration File Handling SN#copy startup-config nvram:backup 9.6 Replacing the Startup Configuration with a Configuration from Flash Memory The startup configuration is replaced by a configuration that is already present in the flash memory, by copying it to that area of the flash memory where the startup configuration is to be stored. Pr oc edu re To replace the startup configuration with another present in flash memory M od e...

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

    Configuration File Handling 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 70: Replacing The Startup Configuration With A Configuration Downloaded From Tftp Server

    Configuration File Handling memory region nvram: of the target device. After this the startup configuration is transferred to the TFTP server from where it can be distributed to other SmartNode devices, which therefore get clones of the starting system if the configuration does not need any modifications. 9.8 Replacing the Startup Configuration with a Configuration downloaded from TFTP Server From within the administration execution mode, the startup-configuration is replaced by...

  • Page 71: Displaying Configuration File Information

    Configuration File Handling #----------------------------------------------------------------# cli version 2.00 snmp community public rw … … framerelay exit 9.9 Displaying Configuration File Information Pr oc edu re To display information about configuration files M od e Administrator execution Command Purpose show nvram: List of all persistent configurations show running-config Displays the contents of the running configuration file show startup-config...

  • Page 72: Modifying The Running Configuration Offline

    Configuration File Handling Command Purpose Step 1 node#configure Enters administrator configuration mode Step 2 Enter all the necessary configuration commands. Step 3 node(cfg)#copy running-config startup- Saves the running configuration file as config upcoming startup configuration Step 4 node(cfg)#reload Restarts the system E x amp le: M od i f yi n g t he R u nn in g C o nf igu ra t i on at t he C L I The following example shows how to modify the currently running configuration via the CLI and save it as the startup configuration.

  • Page 73: Deleting A Specified Configuration

    Configuration File Handling Command Purpose Step 1 node#copy running-config tftp://node-ip- Uploads the current running configuration address/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 74 Configuration File Handling 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. Ex amp le: De let in g a Sp ec if ie d Co nf igu ratio n The following example shows how to delete a specific configuration from among a set of three available configurations in Flash memory.

  • Page 75: 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 76 The provider is a company making services available to subscribers. The provider information may be any alphanumeric string, including spaces, that is no longer than one line. This entry corresponds to the Inalp Networks AG enterprise specific MIB provider object.

  • Page 77: 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 78: Setting Time And Date

    Sets the system clock to yyyy-mm-ddThh:mm:ss ddThh:mm:ss Note: SmartWare Release 2.10 includes an integrated SNTP client, which allows synchronization of time-of-day and date to a reference time server. Refer to Chapter 21, “SNTP Client Configuration”, for more details.

  • Page 79: Configuring And Starting The Web Server

    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 AG for any questions about custom designed Java configuration tools for SmartWare.

  • Page 80: Restarting The System

    Basic System Management Pr oc edu re To determine the running CLI version and define another CLI version M od e Configure Command Purpose Step 1 node(cfg)#show version cli Displays the currently running CLI version Step 2 node(cfg)#cli version Selects the active CLI version in the form version.revision version.revision E x amp le: D e f in in g t h e d es ir ed C L I V ers io n...

  • Page 81: Displaying The System Logs

    Basic System Management 10.11 Displaying the System Logs The system logs contain warnings and information from the system components of SmartWare. In case of problems it is often useful to check the event or the supervisor logs for information about malfunctioning system components.
  • Page 82 Basic System Management Command Purpose Step 1 Execute the first command Step 2 node#<Ctrl-Z> Suspend the active command and get system prompt back Step 3 Execute the second command Step 4 node#jobs Shows the currently running commands Step 5 node#fg jobid Brings job with jobid back to foreground Step 6 node#<Ctrl-C>...

  • Page 83: Displaying The Checksum Of A Configuration

    Basic System Management 10.13 Displaying the Checksum of a Configuration In SmartWare configuration files, e.g. startup configuration, running configuration, and user-specific configuration, contain a checksum entry. This checksum informs the user about the validity and helps distinguish configuration files on the basis of the checksum. Pr oc edu re To display the checksum of a configuration M od e...

  • Page 84: 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 85: 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 86: Planning Your Ip Configuration

    IP Context Overview application scenario, some tasks are mandatory or might be optional. The following tasks set up on a bottom-up approach, starting from the ports, followed by the interfaces up to the services running on the SmartNode, as shown in Figure 11-1.

  • Page 87: Qos Related Information

    IP Context Overview • Type of connector, male or female, required connecting at the device • Signaling protocol required by the device must be X.21 or V.35 11.3.3 QoS Related Information Check with your access service provider if there are any QoS related requirements, which you need to know prior to configuring SmartWare QoS management.

  • Page 88: Configuring Static Ip Routing

    IP Context Overview outside IP address to connect several hosts via a SmartNode to the access network. Moreover NAPT provides additional security, because the IP addresses of hosts attached via the SmartNode are made invisible to the outside world. Configuring NAPT is done by creating a profile that is afterwards used on an explicit IP interface.

  • Page 89: Configuring Quality Of Service

    IP Context Overview ICMP, TCP, UDP, and SCTP) to filter the packets of those protocols as the packets pass through a SmartNode. SmartWare tests packets against the conditions in an access list one by one. The first match determines whether SmartWare accepts or rejects the packet. Because SmartWare stops testing conditions after the first match, the order of the conditions is critical.

  • Page 90: Ip Interface Configuration

    Examples 12.1 Introduction Within the Inalp Networks AG SmartWare, an interface is a logical entity 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 separation of the interface from the physical layer allows for many of the advanced features offered by the SmartWare.

  • Page 91: 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 92: Setting The Ip Address And Netmask

    IP Interface Configuration 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 net mask to be set. Pr oc edu re To set the IP address to ip-address and the network mask to netmask or enable IP processing for IP interface name without assigning an explicit IP address, use the ipaddress interface configuration...

  • Page 93: 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 94: 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 95: 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 96: Testing Connections With The Ping Command

    IP Interface Configuration 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 … 12.12 Testing Connections with the ping Command As an aid to diagnosing basic network connectivity, many network protocols support an echo protocol.

  • Page 97: Traceroute

    IP Interface Configuration 12.13 Traceroute Pr oc edu re To print the route (list of hops) packets take to network host. M od e Either operator or administrator execution Command Purpose Step 1 node>traceroute ip-address prints the route (list of hops) packets take to network host.

  • Page 98: 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 99: Adding A Static Napt Entry

    NAPT Configuration This command creates and enters new profiles, enters existing profile or removes existing profile. After entering the profile, the commands static and icmp default are available to configure the profile. Pr oc edu re To create the new NAPT profile M od e Configure Command...

  • Page 100: Removing A Static Napt Entry

    NAPT Configuration 13.6 Removing a Static NAPT Entry A static NAPT entry can be deleted, entering the inverted version of the command, e.g. no static protocol port. Pr oc edu re To remove a static NAPT entry M od e Configure Command Purpose...

  • Page 101: Removing An Icmp Default Server

    NAPT Configuration 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 102: Display Napt Configuration Information

    NAPT Configuration 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 The following example shows how to define that the NAPT profile access shall be used on the interface lan.

  • Page 103: Ethernet Port Configuration

    This chapter provides an overview of Ethernet ports and describes the tasks involved in configuring Ethernet ports through the Inalp Networks AG SmartWare. For detailed information on syntax and usage guidelines for the commands listed under “Procedures”, see the Chapter 22, “Port Ethernet Mode”...

  • Page 104: Configuring Medium For An Ethernet Port

    Ethernet Port Configuration Device Type Interface Type Slot Port Interface SmartNode 1x00 Ethernet ETH 0 ETH 1 ISDN BRI 0 BRI 1 SmartNode 2x00 Ethernet ETH 0/0 ETH 0/1 Serial SERIAL 0/0 Table 11-1: Permanent built-in Interface Slot and Port Mapping for SmartNode 1x00 and 2x00 Series 14.4 Configuring Medium for an Ethernet Port All Ethernet ports are configured by default to auto-sense both the port speed and the duplex mode.

  • Page 105: 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 106: Selecting The Frame Format For An Ethernet Port

    Ethernet Port Configuration 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 node(prt-eth)[slot/port]#bind Binds the Ethernet port to the already existing IP...

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

    Ethernet Port Configuration 14.8 Configuring Layer 2 CoS to Service Class Mapping for an Ethernet Port To enable real-time and delay sensitive services such as VoIP traffic to be transported across the network, the SmartWare application software supports the delivery of Quality of Service (QoS) information in the ToS (Type of Service) field.

  • Page 108: Adding A Transmit Mapping Table Entry

    Ethernet Port Configuration 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 rx- Adds a receive mapping table entry, which map layer 2 class of service value converts a layer 2 class of service into a service class as service class value value...
  • Page 109 Ethernet Port Configuration Pr oc edu re To disable 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 node(prt- Disables Ethernet port on slot and port...

  • Page 110: Link Scheduler Configuration

    When a SmartNode acts as an access router and voice gateway, the access link is the point at which intelligent use of the scarce resources really makes a difference in preventing a bottleneck. This chapter shows you how to configure the SmartWare Release 2.10 to make best use of the access link. The procedures include: •...

  • Page 111: Quick References

    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.10. To match the voice and data Software Configuration Guide Release 2.10, Revision 1.00...

  • Page 112: Command Cross Reference

    Comparing the SmartWare Release 2.10 with the Cisco IOS QoS software command syntax often helps administrators to straightforwardly configure SmartNode devices. In Table 15-1 below the Cisco IOS Release 12.2 QoS commands are in contrast with the respective SmartWare Release 2.10 commands.

  • Page 113: Link Scheduler Configuration Task List

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

  • Page 114: Creating An Access Control List

    Link Scheduler Configuration Note: Keep in mind that the class local-default comprises all other classes, which are not explicitly stated in a service policy profile. 15.5.2 Creating an Access Control List The procedure to create an access control list is described in detail in Chapter 19, “Access Control List Configuration”, later in this guide.

  • Page 115: Assigning Bandwidth To Traffic Classes

    Link Scheduler Configuration 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- Creates an IP access control list entry address any cos cos-name that permits access for host at IP address ip-address, and specifies that packets matched by this rule belong to...

  • Page 116: Burst Tolerance

    Link Scheduler Configuration assigned a relative weight, which determines how much more A bytes will be carried than B bytes. It would be possible to assign A the weight 3 and B the weight 1, but it is better using values that can be read as percentage, e.g.
  • Page 117 Link Scheduler Configuration Figure 15-3: Example of Hierarchical Scheduling Parts of the configuration used for arbiter Level_1 are listed below. Take account of the line rate-limit on the top which is responsible for limiting the overall output o 512 kBit/s. The arbitration uses weighted fair queuing to share the bandwidth among the two classes VPN and Web and the policy Low_Priority.

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

    Link Scheduler Configuration rate 40 … source class default rate 60 Figure 15-5: Service Policy for Low_Priority Arbiter At last the Level_1 service policy profile has to be used on the outbound IP interface. As shown in the example in Figure 15-1 a possible related IP interface could be named as “wan”. Therefore the interface section in the IP context configuration is as shown in Figure 15-6.
  • Page 119 Link Scheduler Configuration How the bandwidth on an IP interface is shared among the source classes is defined on the third line. The mode command allows selecting between the weighted fair queuing and shaping arbitration mode. On lines 4 to 9 the source classes are defined. When using weighted fair queuing (wfq) each user- specified source class needs a value specifying its contribute to the overall bandwidth.

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

    Link Scheduler Configuration Step 7 node(pf-srvpl)[name]#… Repeat steps 4 to 6 for all necessary source classes or lower level service policy profiles. Step 8 node(pf-srvpl)[name]#exit Leaves the service policy profile mode Ex amp le: C reat ing a T op -Le ve l Se r vic e Po lic y Pr o f ile The following example shows how to create a top-level service policy profile named Sample.

  • Page 121: Defining The Bit-Rate

    Link Scheduler Configuration 15.8.2 Defining the Bit-Rate The command rate is used with shaper link arbitration to assign the (average) bit-rate to the selected source. When enough bandwidth is available each source will exactly receive this bandwidth (but never more), when overloaded the shaper will behave like a wfq arbiter. Bit-rate specification for shaper (kilobits) Pr oc edu re Defining the bit-rate...

  • Page 122: Specifying The Type-Of-Service (Tos) Field

    Link Scheduler Configuration 15.8.5 Specifying the Type-Of-Service (TOS) Field The set ip tos command specifies the type-of-service (TOS) field value applied to packets of the class name. TOS and DSCP markings cannot be used at the same time. The no form of this command disables TOS marking.

  • Page 123: Specifying Differentiated Services Codepoint Marking

    Link Scheduler Configuration reserved for network control packets. Therefore, with the set ip precedence command the values 0 through 5 can be set for priority based on IP networks or applications. The no form of this command disables precedence marking. Pr oc edu re Defining the precedence field M od e...
  • Page 124 Link Scheduler Configuration Figure 15-8: DS Field Structure In a DSCP value notation 'xxxxxx' (where 'x' may equal '0' or '1') used in this user guide, the left-most bit signifies bit 0 of the DS field (as shown above), and the right-most bit signifies bit 5. The DSCP field within the DS field is capable of conveying 64 distinct codepoints.

  • Page 125: Specifying Layer 2 Marking

    Link Scheduler Configuration Command Purpose node(src)[name]#set ip dscp value Defines the Differentiated Services Codepoint value applied to packets of for the selected class or policy name. The range for value is from 0 to 63. 15.8.8 Specifying Layer 2 Marking The IEEE ratified the 802.1p standard for traffic prioritization in response to the realization that different traffic classes have different priority needs.

  • Page 126: Discarding Excess Load

    Link Scheduler Configuration queue has grown over half the “queue-limit”. This improves the performance of TCP flow-control. A burst-tolerance index between 1 and 10 may optionally be specified (exponential filter weight). The no form of this command reverts the queue to default “tail-drop” behavior. Pr oc edu re Defining random early detection M od e...
  • Page 127 Link Scheduler Configuration Figure 15-9: Using a Service Policy Profile on an IP Interface 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.

  • Page 128: Displaying Link Arbitration Status

    Link Scheduler Configuration SN(ctx-ip)[router]#interface wan SN(if-ip)[wan]#use profile service-policy Voice_Prio out 15.10 Displaying Link Arbitration Status The show service-policy command displays link arbitration status. This command supports the optional argument interface that select a certain IP interface. This command is available in the operator mode.

  • Page 129: Enable Statistics Gathering

    Link Scheduler Configuration 15.12 Enable Statistics Gathering Using the debug queue statistics commands enables statistic gathering of link scheduler operations. The command has optional value, which defines the level of detail. The value is in the range from 1 to 6. In Table 15-5 below the values and their implications are compiled. Optional Implication on Command Output Value...

  • Page 130: 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 Networks AG SmartWare. For detailed information on syntax and usage guidelines for the commands listed under Configuration Tasks, refer to the Chapter 23, "Port Serial Mode"...

  • Page 131: 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.

  • Page 132: Configuring The Serial Encapsulation Type

    Serial Port Configuration Pr oc edu re To enable a serial interface 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...

  • Page 133: Configuring The Hardware Port Protocol

    Serial Port Configuration Step 3 node(prt-ser)[slot/port]#show port serial Displays the serial interface 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 134: Configuring The Active Clock Edge

    Serial Port Configuration SN(prt-ser)[0/0]#hardware-port x21 SN(prt-ser)[0/0]#show port serial Serial Interface Configuration ------------------------------ Port : serial 0 0 0 State : CLOSED Hardware Port : X.21 Transmit Edge : normal Port Type : DTE CRC Type : CRC-16 Max Frame Length: 2048 Recv Threshold Encapsulation : framerelay...

  • Page 135: Enter Frame Relay Mode

    Serial Port Configuration 16.8 Enter Frame Relay Mode This Section describes the tasks for configuring Frame Relay for the serial interface on a SmartNode series 2000 device, after setting the basic serial interface parameters according to the chapters above. Pr oc edu re To enter the Frame Relay configuration mode M od e Administrator execution...

  • Page 136: Configuring The Keepalive Interval

    Serial Port Configuration E x amp le: C o nf i gu r ing t he LM I T yp e The following example sets the LMI type to ANSI T1.617 Annex D for Frame Relay over the serial interface on slot 0 and port 0 of a SmartNode 2300 series device. SN(cfg)#port serial 0 0 SN(prt-ser)[0/0]#framerelay SN(frm-rel)[0/0]#lmi-type ansi...
  • Page 137 Serial Port Configuration Step 3 node(frm-rel)[0/0]#use profile service-policy Use the previously defined service policy name out profile on Frame Relay layer (and not on IP interface level) in outward direction. For other profile settings refer to the software configuration guide. Step 4 node(frm-rel)[0/0]#fragment size Define the maximum size (in Bytes) of...

  • Page 138: Entering Frame Relay Pvc Configuration Mode

    Serial Port Configuration G.729 G.723 G.723 G.723 G.711 G.711 G.711 16.12 Entering Frame Relay PVC Configuration Mode The permanent virtual circuit (PVC) is a virtual circuit that is permanently established. PVCs save bandwidth associated with circuit establishment and tear down in situations where certain virtual circuits must exist all the time.

  • Page 139: Configuring The Pvc Encapsulation Type

    Serial Port Configuration 16.13 Configuring the PVC Encapsulation Type To set the encapsulation type to comply with the Internet Engineering Task Force (IETF) standard (RFC 1490) the PVC configuration command encapsulation rfc1490 has to be used. Use this keyword when connecting to another vendor's equipment across a Frame Relay network. Pr oc edu re To set the encapsulation type to comply with RFC 1490 M od e...

  • Page 140: Disabling A Frame Relay Pvc

    Serial Port Configuration Pr oc edu re To bind the Frame Relay PVC dlci on the serial interface to the logical IP interface name, which is related to the IP context router M od e Command Purpose Step 1 node(pvc)[dlci]#bind interface name router Binds Frame Relay PVC dlci to the IP interface name of IP context router E x amp le: B in d in g t he Fr a me R e l a y P V C t o I P I nt e rfa ce...

  • Page 141: Displaying Frame Relay Information

    Serial Port Configuration bind interface wan router shutdown exit … 16.16 Displaying Frame Relay Information Since Frame Relay configuration for the serial interface is complex and requires many commands, it is helpful to list the frame relay configuration on screen. Pr oc edu re To display the Frame Relay configuration settings for the serial interface M od e...

  • Page 142: Displaying Frame Relay Information

    Serial Port Configuration 16.17.2 Displaying Frame Relay Information The following example shows the commands used to display Frame Relay configuration settings for a SmartNode 2300 series device. Moreover a typical command output is listed below. SN>enable SN#configure SN(cfg)#show framerelay Framerelay Configuration: Port LMI-Type Keepalive...
  • Page 143 Serial Port Configuration Figure 16-2: Typical Integrated Service Access Scenario with dedicated PVCs Devices accessing the MSP and VPN services are attached to the 100 MBit/s Ethernet port 0/0 on the SmartNode 2300 series device. For that reason an IP context with three logical IP interfaces bound to Ethernet port 0/0, PVC 1 and PVC 2 on serial port 0/0 as shown in Figure 16-2 h as to be configured...
  • Page 144 Serial Port Configuration Figure 16-3: IP Context with logical IP interfaces bound to Ethernet port, serial port PVC 1 and PVC 2 The related IP, serial interface and Frame Relay configuration procedure is listed below. Where necessary comments are added to the configuration for better understanding. S t e p 1 Enter the configuration mode.
  • Page 145 Serial Port Configuration SN(src)[local-d~]#source class default … S t e p 4 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 5 The Frame Relay configuration is done next. Therefore we have to change to the Frame Relay configuration mode.

  • Page 146: 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 147: Configuring Static Ip Routes

    Basic IP Routing Configuration • Configuring static IP routes • Deleting static IP routes • Displaying IP route information 17.3 Configuring Static IP Routes Rather than dynamically selecting the best route to a destination, you can configure one or more static routes to that destination.

  • Page 148: Displaying Ip Route Information

    Basic IP Routing Configuration Pr oc edu re To delete one or more static IP routes from the routing table M od e Administrator execution Command Purpose Step 1 node(cfg)#context ip router Enters the IP router context Step 2 node(ctx-ip)[router]#no route network mask Deletes a static route {address | interface} For the syntax description see Chapter...

  • Page 149: Examples

    Basic IP Routing Configuration 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. The SmartNode shall be configured for the following IP routing scenario: All packets for the Workstation with IP address 10.1.5.10 shall be forwarded to the next-hop router Calvin.

  • Page 150: Rip Configuration

    RIP Configuration 18 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” in the SmartWare Command Reference Guide.

  • Page 151: Rip Configuration Task List

    RIP Configuration as well as the number of routers/gateways that a packet must travel through to reach the receiving address. RIP 2 is an enhancement of RIP 1 which allows IP subnet information to be shared among routers, and provides for authentication of routing updates. When this protocol is chosen, the router will use the multicast address 224.0.0.9 to send and/or receive RIP 2 packets for this network interface.

  • Page 152: Enabling An Interface To Receive Rip

    RIP Configuration SN(cfg)#context ip router SN(ctx-ip)[router]#interface wan SN(if-ip)[wan]#rip supply 18.5 Enabling an Interface to Receive RIP By default an interface does not listen to routing information. Pr oc edu re To enable interface to receive RIP information M od e Interface Command Purpose...

  • Page 153: Specifying The Receive Rip Version

    RIP Configuration 18.7 Specifying the Receive RIP Version By default, the SmartWare application software receives RIP version 1 and version 2 packets. The SmartWare application software allows receiving RIP version 1, version 2 or both version 1 and version 2 packets. Alternatively, you can explicitly configure the RIP version to be received with the last command argument as following: •...

  • Page 154: Enabling An Interface To Receive Rip

    RIP Configuration Command Purpose Step 1 node(if-ip)[name]# rip learn Enables accepting of IP host routes received on host interface name Step 2 node(if-ip)[name]#rip learn Enables learning using a default route advertised default by an RIP neighbor on interface name Ex amp le: En ab ling R IP L ear n Ho st a nd De fau lt The following example shows how to enable RIP learn host and default on IP interface wan on a SmartNode.

  • Page 155: Enabling Rip Auto Summarization

    RIP Configuration M od e Interface Command Purpose Step 1 node(if-ip)[name]#rip Selects the RIP announcing method on interface announce {default | host | self- name as-default | static} E x amp le: E n ab l i ng R I P A n no un c in g The following example shows how to enable the RIP default routes and IP host routes RIP announcing method on IP interface wan on a SmartNode.

  • Page 156: Enabling Rip Split-Horizon Processing

    RIP Configuration destination-network entry, the SmartNode 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 157: Enabling The Poison Reverse Algorithm

    RIP Configuration Command Purpose Step 1 node(if-ip)[name]#rip split- Enables RIP split-horizon processing on interface horizon name E x amp le: E n ab l i ng R I P Sp l it - H o r izo n Pro ce ss in g The following example shows how to enable split horizon on IP interface wan on a SmartNode.

  • Page 158: Displaying Rip Configuration Of An Ip Interface

    RIP Configuration Command Purpose Step 1 node(if-ip)[name]#rip route- Enables holding down aged routes on interface holddown name E x amp le: E n ab l i ng H o l d in g D ow n A ge d R o ute s The following example shows how to enable holding down of aged routes on IP interface wan on a SmartNode.
  • Page 159 RIP Configuration Pr oc edu re To display the global RIP information M od e Configure Command Purpose Step 1 node(cfg)#show rip Displays the RIP information E x amp le: D is p la yin g G l ob a l R IP I nf or m ati o n The following example shows how to display the global RIP information on a SmartNode.

  • Page 160: 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 Networks AG SmartWare, Release 2.10. 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 161: 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 162: Software Configuration Guide Release 2.10 Task List

    Access Control List Configuration • An empty access control list is treated as an implicit “deny ip any any” list. Note: Two or more administrators should not simultaneously edit the configuration file. This is especially the case with access lists. Doing this can have unpredictable results. Once in access control list configuration mode, each command creates a statement in the access control list.

  • Page 163: Add A Filter Rule To The Current Access Control List Profile

    Access Control List Configuration M od e Administrator execution Command Purpose Step 1 node(cfg)#profile acl name Creates the access control list profile name and enters the configuration mode for this list name is the name by which the access list will be known. Entering this command puts you into access control list configuration mode where you can enter the individual statements that will make up the access control list.

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

    Access Control List Configuration Keyword Meaning The source address to be included in the rule. An IP address in dotted-decimal- format, e.g. 64.231.1.10. src-wildcard A wildcard for the source address. Expressed in dotted-decimal format this value specifies which bits are significant for matching. One-bits in the wildcard indicate that the corresponding bits are ignored.
  • Page 165 Access Control List Configuration Pr oc edu re To create an ICMP access control list entry that denies access M od e Profile access control list Command Purpose Step 1 node(pf-acl)[name]#deny icmp {src src-wildcard Creates an ICMP access of control | any | host src} {dest dest-wildcard | any | host list entry that denies access dest} [msg name | type type | type type code...

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

    Access Control List Configuration Ex amp le: C reat e ICMP A cce ss C ont ro l L ist Ent r ies Select the access-list profile named WanRx and create the rules to filter all ICMP echo requests (as used by the ping command).
  • Page 167 Access Control List Configuration Keyword Meaning The source address to be included in the rule. An IP address in dotted-decimal- format, e.g. 64.231.1.10. src-wildcard A wildcard for the source address. Expressed in dotted-decimal format this value specifies which bits are significant for matching. One-bits in the wildcard indicate that the corresponding bits are ignored.

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

    Access Control List Configuration SN(cfg)# 19.8 Bind and Unbind an Access Control List Profile to an IP Interface The command use is used to bind an access control list profile to an IP interface. Pr oc edu re To bind an access control list profile to incoming packets on an IP interface M od e Profile access control list Command...

  • Page 169: Display An Access Control List Profile

    Access Control List Configuration Keyword Meaning Specifies that the access control list applies to outgoing packets on this interface. Thus for each IP interface only one incoming and outgoing access control list can be active at the same time. E x amp le: B in d a nd U n b in d a n A c ces s C o nt ro l List E nt r ie s t o a n I P I nt er f ac e Bind an access control list profile to incoming packets on the interface wan in the IP router context.
  • Page 170 Access Control List Configuration Pr oc edu re To debug the access control list profiles M od e Administrator execution or any other mode, except the operator execution Command Purpose Step 1 node#debug acl Enables access control list debug monitor Pr oc edu re To activate the debug level of an access control list profiles for a specific interface.

  • Page 171: Examples

    Access Control List Configuration 19.11 Examples 19.11.1 Deny a Specific Subnet Figure 19-2 shows an example in which a server attached to network 172.16.1.0 shall not be accessible from outside networks connected to IP interface lan of the SmartNode device. Therefore an incoming filter rule named Jamming is defined, which blocks any IP traffic from network 172.16.2.0 and has to be bound to IP interface lan.

  • Page 172: Snmp Configuration

    20 SNMP CONFIGURATION This chapter provides overview information about Simple Network Management Protocol (SNMP) and describes the tasks used to configure those of its features supported by the Inalp Networks AG SmartWare, Release 2.10. For a complete description of the SNMP commands in this chapter, refer to Chapter 27, “SNMP Mode”, in the SmartWare Command Reference Guide.

  • Page 173: 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. 20.1.3 SNMP Basic Commands Managed devices are monitored and controlled using four basic SNMP commands: read, write, trap, and traversal operations.

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

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

  • Page 175: Setting Basic System Information

    SNMP Configuration 20.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 176: Setting Access Community Information

    SN>enable SN#configure SN(cfg)#system contact "Lorenz Born, Phone 533" SN(cfg)#system location "Office, 3rd floor, Inalp Networks AG" SN(cfg)#system hostname "SN2300-01" SN2300-01(cfg)# 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.
  • Page 177 SNMP Configuration example of a read-only variable might be a counter showing the total number of octets sent or received through an interface. An example of a read-write variable might be the speed of an interface, or the hostname of a device. Community strings also provide a weak form of access control in earlier versions of SNMP version 1 and 2.

  • Page 178: Setting Allowed Host Information

    SNMP Configuration 20.8 Setting Allowed Host Information If a host has to access SNMP MIB objects on a certain node it explicitly needs the right to access the SNMP agent on the respective SmartNode 1000 or 2000 series device. Therefore a host needs an entry on a SmartNode 1000 or 2000 series device, which allows accessing the device.

  • Page 179: 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 AG contact : Lorenz Born, Phone 533 Hosts: 172.16.224.44 security-name public Targets: 172.16.224.44 security-name Not4evEryOne...

  • Page 180: 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 AG enterprise specific MIBs used for SmartNode 1000 or 2000 series device management.

  • Page 181: Using The Trapviewer

    SNMP Configuration Figure 20-2: AdventNet MibBrowser Settings Button on the Toolbar By default the MIB description display and the result display are visible in the MibBrowser. 20.11.2 Using the TrapViewer TrapViewer is a graphical tool to view the traps received from one or more SNMP agents running on a SmartNode 1000 or 2000 series device.
  • Page 182 SNMP Configuration • Click on Add button to add the port and community list on which the trap has to listen to. This is visible in the TrapList combo box. • The port and community list can be deleted by clicking on the Del button. •...

  • Page 183: Standard Snmp Version 1 Traps

    SNMP Configuration Trap Details Description sysUpTime variable converted into hours, minutes and seconds. This field shows the OID of the management enterprise that defines the Enterprise trap message. The value is represented as an OBJECT IDENTIFIER value and has a variable length. The Generic type value is categorized and numbered 0 to 6.

  • Page 184: Snmp Interface Traps

    SNMP Configuration linkDown TRAP-TYPE ENTERPRISE snmp VARIABLES { ifIndex } DESCRIPTION "A linkDown trap signifies that the sending protocol entity recognizes a failure in one of the communication links represented in the agent's configuration." ::= 2 Note: The linkDown trap is not sent if any of the ISDN ports is gone down. linkUp TRAP-TYPE ENTERPRISE snmp VARIABLES...
  • Page 185 SNMP Configuration SN(cfg)#show snmp-if-alias-mapping ifIndex : Interface Name (Interface Type) Interface Status --------------------------------------------------------------------- h323_60 (H323) h323_30 (H323) isdn20 (PSTN) ETH00 (ethernet-csmacd) ETH01 (ethernet-csmacd) eth00 (IP) eth01 (IP) ISDN20 (pstn) down Interface names in capital letters denote physical interfaces and in small letters logical interfaces. The SmartNode adds an entry to event log for each Interface Traps it sends: SN(cfg)#show log 2002-09-06T14:54:35 : LOGINFO...

  • Page 186: Sntp Client Configuration

    SNTP Client Configuration 21 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 187: Defining Sntp Client Operating Mode

    SNTP Client Configuration Command Purpose 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 188: Defining Sntp Local Udp Port

    SNTP Client Configuration SN(cfg)#sntp-client operating-mode multicast 21.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 189: Defining Sntp Client Poll Interval

    SNTP Client Configuration 21.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. The default value is 60 seconds.

  • Page 190: Defining The Sntp Client Anycast Address

    SNTP Client Configuration SN(cfg)#sntp-client gmt-offset + 2 21.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. An anycast client (SmartNode) sends a request to the designated local broadcast or multicast group address as described below.

  • Page 191: Enabling And Disabling Root Delay Compensation

    SNTP Client Configuration timestamp in the request is set to the time of day according to the client clock in NTP timestamp format. This allows a simple calculation to determine the propagation delay between the server and client and to align the local clock generally within a few tens of milliseconds relative to the server. In addition, this provides a simple method to verify that the server reply is in fact a legitimate response to the specific client request and to avoid replays.

  • Page 192: Showing Sntp Client Related Information

    SNTP Client Configuration 21.12 Showing SNTP Client Related Information During set-up and operation of the SNTP client, displaying the information and status of the SNTP client is very useful. Pr oc edu re To display information and status of the SNTP client M od e Configure Command...

  • Page 193: Recommended Public Sntp Time Servers

    SNTP Client Configuration Server: 172.16.1.10:123 v4 Stratum: Time: 2001-10-26T12:44:21 InternetTime: 20010926@530 ------------------------------------------------ 14:44:21 SNTP > Set the system time to 2001-10-26T14:44:21 14:44:51 SNTP > SNTP message sent with Timestamp: 2001-10- 26T14:44:51 14:45:21 SNTP > SNTP message sent with Timestamp: 2001-10- 26T14:45:21 14:45:51 SNTP...

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

    SNTP Client Configuration 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. Heavily loaded and not recommended for new users. 2. Recommended for new users. 3.

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

    SNTP Client Configuration Access Policy: open access Contact: Gerard Gschwind (gg@cs.tu-berlin.de) 21.14.3 Additional Information on NTP and a List of other NTP servers The University of Delaware hosts a World Wide Web site that provides additional information on NTP and a list of other NTP servers that are publicly available around the world. In many cases, Internet service providers, universities, and other institutions also provide NTP servers for their own communities.

  • Page 196: Dhcp Configuration

    DHCP Configuration 22 DHCP CONFIGURATION This chapter provides an overview of the Dynamic Host Configuration Control Protocol (DHCP) 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 14 ???, "Context IP Mode", Chapter 15 ???, "Interface Mode", or Chapter XX, "Profile DHCP-Server Mode"...

  • Page 197: Dhcp-Client Configuration Tasks

    DHCP Configuration Figure 22-1: DHCP-Client and DHCP-Server on the SmartNode 22.2 DHCP-Client Configuration Tasks To configure the SmartNode as DHCP-Client perform the steps mentioned below. • Enable DHCP-Client on an IP interface • Release or renew a DHCP lease manually (Advanced) •...

  • Page 198: Release Or Renew A Dhcp Lease Manually (Advanced)

    DHCP Configuration Step 2 node(if-ip)[name]#ipaddress dhcp Enables the DHCP-Client on this IP interface. (See note) Step 3 node(if-ip)[name]#show dhcp- Displays status information about the DHCP- client Client. E.g. default gateway, lease expire time, etc. Note: Please be aware, that if you are connected to the SmartNode by telnet over the IP interface on which you enable the DHCP-Client, the connection has lost after entering the command ‘ipaddress dhcp’.

  • Page 199: Get Debug Output From Dhcp-Client

    DHCP Configuration client release’. You need an other way (e.g. a serial connection) to connect to the SmartNode again and to enter the command “dhcp-client renew’ ! 22.5 Get Debug Output from DHCP-Client Pr oc edu re To enable/disable DHCP-Client debug monitor M od e Command Purpose...

  • Page 200: Dhcp-Server Configuration Tasks

    DHCP Configuration 22.6 DHCP-Server Configuration Tasks To configure the SmartNode as DHCP-Server perform the steps mentioned below. • Configure DHCP-Server profiles • Use DHCP-Server profiles and enable the DHCP-Server (and to clear lease database) • Check DHCP-Server configuration and status •...

  • Page 201: Use Dhcp-Server Profiles And Enable The Dhcp-Server

    DHCP Configuration Step 7 node(pf-dhcps)[name]#[no] domain-name- Defines up to 2 domain name servers server domain-name-server-ip-address (DNS) to be used by the client (optional) (incremental command) DHCP Option 6 Step 8 node(pf-dhcps)[name]#[no] netbios-name- Defines IP addresses of up to 2 NetBIOS server netbios-name-server-ip-address Name Servers, better known as ‘WINS (optional)

  • Page 202: Check Dhcp-Server Configuration And Status

    DHCP Configuration M od e Context IP Command Purpose Step 1 node(ctx-ip)[router]#[no] dhcp-server use Tell the DHCP-Server (not) to use name DHCP-Server profile name Step 2 node(ctx-ip)[router]#[no] dhcp-server Enables / disables DHCP-Server Step 3 node(ctx-ip)[router]#dhcp-server clear-lease Removes all or a specific lease from the { all | ip-address } server’s database, which in turn marks the IP address(es) as available again.

  • Page 203: Get Debug Output From The Dhcp-Server

    DHCP Configuration 22.10 Get Debug Output from the DHCP-Server Pr oc edu re To enable/disable the DHCP-Server debug monitor M od e Command Purpose Step 1 node(cfg) #[no] debug dhcp-server Enables / disables the debug monitor of the DHCP-Server E x amp le: E n ab le D H C P d eb ug m o n it o r This example shows how to enable the DHCP-Server debug monitor.

  • Page 204: Ppp Configuration

    PPP Configuration 23 PPP CONFIGURATION This chapter describes how to configure the Point-to-Point Protocol over different link layers. For detailed information on command syntax and usage guidelines for the commands listed in section “PPP Configuration Task List”, refer to Chapter ???, “???” of the SmartWare Command Reference Guide.

  • Page 205: Ppp Configuration Task List

    PPP Configuration Since the purpose of PPP is providing IP connectivity over different types of link layers, all PPP configuration elements connect to the IP context through an IP interface. This connection is relayed via a subscriber profile if either PPP peer requires authentication. For PPP over Ethernet, a PPPoE Session must be configured on the respective Ethernet port.
  • Page 206 PPP Configuration Step 3 node(if-ip)[name]#ipaddress The PPP remote peer offers an IP address for the unnumbered IP interface. The IP interface adopts this IP address. node(if-ip)[name]#ipaddress Once PPP has established an IP connection, the IP dhcp interface can use DHCP to acquire an IP address. It sends a DHCP Discover message (which is an IP broadcast) to the IP network to which PPP has established connection.

  • Page 207: Creating A Ppp Subscriber

    PPP Configuration SN(if-ip)[ppp_int~]#point-to-point SN(if-ip)[ppp_int~]#ipaddress unnumbered SN(if-ip)[ppp_int~]#tcp adjust-mss rx mtu SN(if-ip)[ppp_int~]#tcp adjust-mss tx mtu 23.4 Creating a PPP Subscriber One or more PPP subscriber shall be configured if either PPP peer requires authentication. Pr oc edu re To create a PPP subscriber M od e Configure Command...

  • Page 208: Configuring A Pppoe Session

    PPP Configuration Ex amp le: C reat e a PPP Sub sc rib er The procedure below creates a PPP subscriber for a PAP authentication with some Internet Service Provider. SN(cfg)#subscriber ppp joe_example SN(subscr)[joe_exa~]#dial out SN(subscr)[joe_exa~]#authentication pap SN(subscr)[joe_exa~]#identification outbound joeexample@isp.com password blue4you SN(subscr)[joe_exa~]#bind interface ppp_interface router 23.5 Configuring a PPPoE Session...

  • Page 209: Configuring A Serial Port For Ppp

    PPP Configuration Step 8 node (pppoe)[slot/port]# [no] Assigns a PPP profile other than the default (optional) use profile ppp name profile to this PPPoE Session Step 9 node (session)[name]#service Defines the tag ‘Service-Name’ to be supplied (optional) Service-Name with Active Discovery in order to identify the desired remote peer (check whether the remote peer supports this feature) Step 10...

  • Page 210: Creating A Ppp Profile

    PPP Configuration Step 3 node (prt-ser)[slot/port]# [no] Binds the serial port directly to the IP interface bind interface name [router] name in case no authentication is required node (prt-ser)[slot/port]# [no] Binds the serial port to the PPP subscriber name in bind subscriber name case authentication is required node (prt-ser)[slot/port]# [no]...

  • Page 211: Displaying Ppp Configuration Information

    PPP Configuration Step 2 node(pf-ppp)[name]#mtu min Defines the minimum and maximum size of IP (optional) min max max packets (in Bytes) allowed on the outbound PPP connection. Outbound packets larger than the maximum size are fragmented into smaller ones if allowed.
  • Page 212 PPP Configuration Command Purpose Step 1 node(cfg) #show running- Gives the best overview of all PPP related config configuration information. The following parts are of interest: - profile ppp default - profile ppp name - interface name - subscriber ppp name - port ethernet slot port - session name Step 2...

  • Page 213: Debugging Ppp

    PPP Configuration IPCP Terminate-Request: interval 3000 ms, max 2 Van-Jacobson Compression: allowed, max-slots 31 Van-Jacobson Decompression:allowed, max-slots 31 Name: PPPoE LCP Configure-Request: interval 3000 ms, max 10 LCP Configure-Nak: max 5 LCP Terminate-Request: interval 3000 ms, max 2 LCP Echo-Request: interval 10000 ms, max 3 MTU: 68 - 1492...
  • Page 214 PPP Configuration Step 3 node(cfg) #show pppoe [ name ] Displays status, configuration information, and statistics of PPPoE in general and of the PPPoE Session(s). Check whether state of the respective session is ‘Opened’. level specifies to level of details displayed (1..4, default is 1).
  • Page 215 PPP Configuration Magic Number = 0xb89d9e6b MRU = 1492 [68,1492] ACCM = 0xffffffff Authentication Protocol = { PAP } Remote acknowledged options: MRU = 1492 [68,1492] Magic Number = 0xb89d9e6b Authentication Protocol = { PAP } Remote denied options: Remote rejected options: PAP: Name: ethernet 0 0 0/pppoe/ppp_green...

  • Page 216: Sample Configurations

    PPP Configuration PPPoE Information: ================== Instance: Name: ethernet 0 0 0/pppoe Initiation Send Interval 3000 ms Request Send Interval 1000 ms Max. Initiations Max. Requests Received Octets 7247 Received Packets Received Discards Received Errors Received Unknown Protos Transmitted Octets 2952 Transmitted Packets Transmitted Discards Transmitted Errors...

  • Page 217: Ppp Over Serial Link

    PPP Configuration session green bind interface ppp_interface no shutdown W it h Aut he nt ic at io n , E n cap su la tion P P Po E context ip router interface ppp_interface ipaddress unnumbered point-to-point tcp adjust-mss rx mtu tcp adjust-mss tx mtu subscriber ppp joe_example dial out...
  • Page 218 PPP Configuration no shutdown Software Configuration Guide Release 2.10, Revision 1.00...

  • Page 219: Cs Context Overview

    CS Context Overview 24 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 220: Cs Context Configuration Task List

    CS Context Overview 24.2 CS Context Configuration Task List The information that is needed for the CS entity configuration is distributed among several configuration tasks, depending on its logical content. For example, all related information that pertains to call routing is described in configuration task 'Configure Call Routing'.
  • Page 221 CS Context Overview • To use ISoIP we need an ISoIP interface. (This is described in section 'Configure Call Routing') • To support call routing we have to configure Session Router routing tables and the ISoIP and PSTN interfaces. (This is described in section 'Configure Call Routing'). Calls are routed: •...

  • Page 222: Configure General Cs Settings

    CS Context Overview 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. The IP configuration is not a topic in this example.

  • Page 223: Configure Call Routing

    CS Context Overview Co nf igu re G ene ra l CS s ett in gs The following example configures the general CS parameters SN>enable SN#configure SN(cfg)#system SN(sys)#no bypass-mode SN(sys)#clock-source 1 0 SN(sys)#synchronize-to-isdn-time 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 24.5 Configure Call Routing Calls through a SmartNode can be routed according to a set of routing criteria.

  • Page 224: Create And Configure Cs Interfaces

    IP connection. SmartWare supports two different protocols that transmit voice packets over IP, the Inalp Networks AG developed protocol ISoIP and the generally defined H.323 protocol. The voice over IP (VoIP) parameters are configured in the VoIP profile. A VoIP profile is used by a ISoIP or H.323 gateway.

  • Page 225: Configure Isdn Ports

    CS Context Overview made in the VoIP profile, so that a call through this specific interface uses other settings. Parameters which are configured in the VoIP profile are: • Filters • DTMF Relay • Echo Canceller • Silence Compression • Voice Volume •...

  • Page 226: Activate Cs Context Configuration

    CS Context Overview H.323 interface one of these listed codecs we have to specified. If no codec is specified in the H.323 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 22, “DHCP Configuration”.
  • Page 227 CS Context Overview 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. Level 0 shows less, level 5 shows all information. Step 2 node (ctx-cs)[switch]#debug Enable the session-router debug monitor session-router Step 3 node (ctx-cs)[switch]#no shutdown...

  • Page 228: Example

    CS Context Overview 24.12 Example 24.12.1 Configure SmartNode in an Enterprise Network S i t u at io n Figure 24-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 229 CS Context Overview • We need four ISDN ports, two for the PSTN and another two for the PBX. (Refer to section 'Configure ISDN Ports') • Furthermore we need two PSTN interfaces. On each we bind two ISDN ports, which means, that we create a line hunt group on every PSTN interface.
  • Page 230 CS Context Overview 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 231 CS Context Overview 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 SN(prt-isdn)[2/0]#l3proto dss1 SN(prt-isdn)[2/0]#max-channels 2 SN(prt-isdn)[2/0]#uni-side usr SN(prt-isdn)[2/0]#up...
  • Page 232 CS Context Overview 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 233 CS Context Overview 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... 02:47:59 >...

  • Page 234: Context Cs Switch

    CS Context Overview 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 remoteip 146.86.130.24 codec g711alaw64k...
  • Page 235 CS Context Overview 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 236: Cs Interface Configuration

    CS Interface Configuration 25 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 237: Cs Interface Configuration Task List

    CS Interface Configuration H.323 and ISoIP interfaces are CS interface types that provides voice over IP settings in addition to the general CS interface parameters. All H.323 and ISoIP interface on the CS context are implicitly bound to the H.323 or ISoIP gateway through SmartWare. 25.2 CS Interface Configuration Task List Some parameters depend upon the interface type.

  • Page 238: Configure Call Routing

    CS Interface Configuration Step 7 node(ctx-cs)[switch]#no interface if- Delete an already defined interface. type if-name Ex amp le s: C reat e a n C S int erf ac es a nd de lete ano th er The following example shows how to create and configure an interface, how to display it and how to delete another.

  • Page 239: Configure Digit Collection

    CS Interface Configuration Step 3 node(if- type)[if-name]#fallback Specify a fallback interface for incoming calls dest-interface name Step 4 node(if- type)[if-name ]#exit Go back to the CS context configuration mode Step 5 Repeat steps 1-3 for all the required CS interfaces Ex amp le: Co nf igu r e C a l l R o u t in g The following example shows how to configure basic interface routing including fallback.

  • Page 240: Configure Direct Call Signaling On Voip Interfaces

    CS Interface Configuration M od e Interface below Context CS Command Purpose Step 1 node(if- type)[if-name]#digit- Specify the timeout to wait for the first dialed or collection timeout seconds between two dialed digits before all previous digits are sent. Step 2 node(if- type) [if-name]#digit- Specify a character that indicates the end of the collection terminating-char...

  • Page 241: Specify The Port Address On Voip Interfaces

    CS Interface Configuration E x amp le: C o nf i gu re D i rect C a l l S i g na l in g o n I So I P in t e rfac e The following example shows how to configure 'direct call signaling' in an ISoIP interface by specifying the remote IP address SN>enable SN#configure...

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

    CS Interface Configuration M od e Interface below Context CS Command Purpose 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 243: Examples

    CS Interface Configuration SN(if-pstn)[PublicP~]#bind port 2 1 SN(if-pstn)[PublicP~]# 25.9 Examples 25.9.1 V5 Carrier Access Figure 25-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 25-4: V5 Carrier Access Scenario First we configure the CS interfaces and the call routing.

  • Page 244: Sn(Ctx-Cs)[Switch]#No Shutdown

    CS Interface Configuration SN(if-isoip)[IpBackb~]#routing dest-interface ISDNPhone101 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 245: Q.sig Pbx Networking

    CS Interface Configuration 02:47:59 > IpBackbone101 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]# 25.9.2 Q.SIG PBX Networking The example in Figure 25-5 shows a Q.SIG PBX network scenario.

  • Page 246: Sn(Ctx-Cs)[Switch]

    CS Interface Configuration 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 247: Sn(Ctx-Cs)[Switch]#02:47:59

    CS Interface Configuration 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... 02:47:59 > Resolving interface references within routing tables...

  • Page 248: Session Router Configuration

    Session Router Configuration 26 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 249: Routing Table Structure

    Session Router Configuration Figure 26-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 250: 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 ! 26.2 Warning The Session Router allows you to solve practically any call routing and number manipulation...

  • Page 251: Configure The Entry Table On Circuit Interfaces

    Session Router Configuration achieving the set goal. Only when you are happy with the planned tables, functions and sequence should you start configuration. 26.5 Configure the Entry Table on Circuit Interfaces To activate the advanced Session routing the first lookup table in the CS interface has to be specified as you can see in Figure 26-1.

  • Page 252: Create A Called Party Number Routing Table

    Session Router Configuration Type Format Description Example unknown as dialed 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 19-26-1: ISDN number types The missing prefix in the national and international number types can complicate the Session Router configuration.

  • Page 253: 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 254: Create A Bearer Capability Routing Table

    Session Router Configuration 26.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. This can be used to differentiate between ISDN data services and ISDN speech connections.

  • Page 255: Create A Day Of Week Routing Table

    Session Router Configuration Pr oc edu re To create a time of day routing table M od e Context CS Command Purpose Step 1 node(ctx-cs)[switch]#time tbl-name key dest- Create a time routing table by adding interface if-name the first line. node(ctx-cs)[switch]#time tbl-name key dest- table tbl-name Step 2...

  • Page 256: Create A Date Routing Table

    Session Router Configuration 26.6.8 Create a Date Routing Table The Date table is used to route calls according to the current system date. It can be used for example to represent holidays in the routing decision tree. The table matches exact dates or date ranges. Pr oc edu re To create a date routing table M od e...
  • Page 257 Session Router Configuration Command Purpose Step 1 node(ctx-cs)[switch]# [no] number- Create a number manipulation function manipulation {cdpn | cnpn } {(add ) | identified by a “speaking” name. Specify if the function acts on the called or calling (remove ) | party number.

  • Page 258: Create A Number Replacement Table

    Session Router Configuration SN[switch]#number-manipulation CnPNToSpecific cnpn convert-to- specific Convert calling party number of type 'unknown' to type 'international': Input: number (0041319852525) of type 'unknown' and international prefix 00 Result: number of type 'international' and with international prefix '00' stripped away (41319852525) Calling party numbers of type 'international' will be left untouched SN[switch]#number-prefix international 00 SN[switch]#number-manipulation CnPNToSpecific cnpn convert-to-...

  • Page 259: Create Complex Number Manipulation Functions

    Session Router Configuration SN[switch]# number-manipulation SwapDDI cdpn replace PISNtoDDI 26.7.2 Create Complex Number Manipulation Functions Complex functions allow to combine number manipulation functions which need to be executed in sequence. This is useful if for example the calling and the called party number have to be modified in the same step.

  • Page 260: Activate The Session Router Configuration

    Session Router Configuration Step 4 node(ctx-cs)[switch]#delete all Delete all routing tables, functions and interfaces in the CS context configuration 26.9 Activate the Session Router Configuration Prior to activate the Session Router Configuration you can show the whole context CS configuration and the entire session routing tables.
  • Page 261 Session Router Configuration Figure 26-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. Two sites A and B are connected to a broadband IP provider. The IP network is used to exchange data and voice calls between the two sites.
  • Page 262 Session Router Configuration • Route mobile calls to carrier “Apple” • Calls from “local_ba”, “node_b” and “node_c” are forwarded directly to “pbx_a” The remainder of this example will focus on the configuration for Node A. The configuration for Node B can be built accordingly. Node C has an even simple configuration. It is a good idea to specify the required Session Router elements and names before starting the configuration.
  • Page 263 Session Router Configuration # Session Router Config File #------------------------------------------------------------- context cs switch # Bearer capability routing table “ISDNservice” bearer-capability ISDNservice ud dest-interface local_ba bearer-capability ISDNservice default dest-table dest_a # Called party number routing table “dest_a” called-party dest_a 0 dest-interface local_ba CACorange called-party dest_a 00 dest-interface node_c CLImelon called-party dest_a 074 dest-interface local_ba CACapple called-party dest_a 075 dest-interface local_ba CACapple...
  • Page 264 Session Router Configuration 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. SN(ctx-cs)[switch]#debug session-router SN(ctx-cs)[switch]##context cs SN(ctx-cs)[switch]#no shutdown SN(ctx-cs)[switch]#17:48:54 > Loading interfaces... 17:48:54 > Resolving interface references interfaces... 17:48:54 >...

  • Page 265: Tone Configuration

    Tone Configuration 27 TONE CONFIGURATION This chapter gives an overview of SmartWare 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 266: Mgcp-Events

    Tone Configuration Figure 27-1: Assign Tone-Sets to CS Context and CS Interfaces Note: There is a default tone-set named 'default', which maps the three Swiss standard in-band tones. Create a tone-set profile only if this default profile corresponds not with your country. 27.1.2 MGCP-Events MGCP uses events to request tone playback on the gateway.
  • Page 267 The duration parameter is ignored in this case. Note: The play command is new since SmartWare Release 2.10. All your currently used configuration, be it in config files on TFTP servers or stored in the startup-config of the SmartNode, are automatically converted into the new format.

  • Page 268: Configure Tone-Set Profiles

    Tone Configuration 27.4 Configure Tone-Set Profiles A tone-set profile maps one call-progress-tone profile to each internal call-progress-tone. A tone-set profile typically includes all the call-progress-tones for one country. Pr oc edu re To configure a tone-set profile M od e configure Command Purpose...

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

    Tone Configuration Pr oc edu re To assign a tone-set profile to the CS context and to a CS interface M od e Context cs Command Purpose Step 1 node(ctx-cs)[switch]#use tone-set-profile Assign the tone-set profile to the CS name context. Step 2 node(ctx-cs)[switch]#interface if-type if- Enter CS interface configuration mode.

  • Page 270: Example

    Tone Configuration Profiles: --------- defaultDialtone: Play 5000ms (425Hz at 0dB) defaultAlertingtone: Play 1000ms (425Hz at -7dB) Pause 4000ms defaultBusytone: Play 500ms (425Hz at -7dB) Pause 500ms myprofile: Play 5000ms (425Hz at 0dB and 3000Hz at 0B) Pr oc edu re To show tone-set profiles M od e administrator exec...
  • Page 271 Tone Configuration Figure 27-2: Assign a tone-set profile to the CS context Create the call-progress-tone profiles: SN(cfg)#profile call-progress-tone dial-UK SN(pf-callp)[dial-UK]#play 5000 350 0 440 0 SN(pf-callp)[dial-UK]#profile call-progress-tone alerting-UK SN(pf-callp)[alertin~]#play 400 400 0 450 0 SN(pf-callp)[alertin~]#no play 200 SN(pf-callp)[alertin~]#play 400 400 0 450 0 SN(pf-callp)[alertin~]#no play 2000 SN(pf-callp)[alertin~]#profile call-progress-tone busy-UK SN(pf-callp)[busy-UK]#play 400 400 0...
  • Page 272 Tone Configuration Software Configuration Guide Release 2.10, Revision 1.00...

  • Page 273: Isdn Port Configuration

    ISDN Port Configuration 28 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 274: Possible Smartnode Port Configurations

    ISDN Port Configuration Figure 28-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 275: Isdn Uni Signaling

    ISDN Port Configuration Figure 28-2: Integration in IASDN Access Lines 28.1.3 ISDN UNI signaling 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 276: Warnings

    ISDN Port Configuration 28.2 Warnings Po rt a ct iva tion de act iva t io n 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 277: Configure Common Bri And Pri Parameters

    ISDN Port Configuration 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 278: Configure Bri Port Parameters

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

  • Page 279: 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 28.7 Configure PRI Port Parameters Of the 32 time slots in an ISDN PRI, slot 0 is reserved for synchronization, slot 16 is used for signaling, and the remaining 30 slots can be used as B-channels for dial-up circuits.

  • Page 280: Example

    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 281 ISDN Port Configuration 172.16.40.71(cfg)#port isdn 1 1 172.16.40.71(prt-isdn)[1/0]#down 172.16.40.71(prt-isdn)[1/0]#uni-side net 172.16.40.71(prt-isdn)[1/0]#clock-mode slave 172.16.40.71(prt-isdn)[1/0]#channel-numbering etsi 172.16.40.71(prt-isdn)[1/0]#max-channels 8 172.16.40.71(prt-isdn)[1/0]#up Software Configuration Guide Release 2.10, Revision 1.00...

  • Page 282: Pots Port Configuration

    POTS Port Configuration 29 POTS PORT CONFIGURATION This chapter provides an overview of SmartNode POTS ports and describes the tasks involved in configuring POTS ports in SmartWare. For detailed information on syntax and usage guidelines for the commands listed under Configuration Tasks refer to Chapter ???, “???”, in the SmartWare Command Reference Guide. This chapter includes the following sections: •...

  • Page 283: Shutdown And Enable Pots Ports

    POTS Port Configuration A va i l ab l e c od ecs f or I C - 4 ab Currently (R2.10) only G.711 and G.723 or G.729 are supported on the IC-4ab, that is it is not possible to use G.723 on one port of the IC-4ab and G.729 at the same time on another port. 29.3 Shutdown and Enable POTS Ports Prior to changing any configuration settings on a POTS port, the port must be shut down.

  • Page 284: Pots Port Configuration Task List

    POTS Port Configuration M od e Port PSTN Command Purpose Step 1 (config)#port pstn slot all Enter configuration mode for all POTS ports Step 2 (prt-pstn)[slot/port]#use profile Select a profile containing the country specific pots profile settings of the port attributes (ring voltage etc.). The country settings are stored in a file which comes together with the software for the IC-4ab.

  • Page 285: Gateway Configuration

    Gateway Configuration 30 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 286: Gateway Configuration Task List

    Gateway Configuration Figure 30-1: Gateways between IP and CS contexts 30.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 287: 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 288: 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 289 Gateway Configuration specified the call is rejected. Table 30-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 290: Enable T.38 Fax Over Ip Relay

    Gateway Configuration 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]# Note: There is more than one possibility to establish a H.323 connection faster. Faststart is one of them. Another is to exchange H.245 messages soon (before the CONNECT message of the H.323 call signaling).

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

    Gateway Configuration Command Purpose Step 1 node(gw-h323)[h323]# [no] isoip-sp-mapping Outgoing calls (to H.323): mapping table <e164> <portaddress> [g711alaw64k 'calling-party-number' to codec; g711ulaw64k g723_6k3 g729 transparent ] Incoming calls (from H.323): mapping table 'called-party-number' to codec; A . O utg o ing ca lls (to H .3 23): For outgoing calls the calling party number is matched against the entries in the table defined with the command isoip-sp-mapping.
  • Page 292 Gateway Configuration To use the gatekeeper the SmartNode has to register by the gatekeeper, therefore the Registration Authentication Service (RAS) has to be enabled. The SmartNode has to register by a name or names, therefore some aliases have to be specified. Furthermore the gatekeeper discovery could be specify on automatically or manually.

  • Page 293: Ras Gatekeeper Registration Type

    Gateway Configuration SN(gw-h323)[h323]#gatekeeper-discovery auto SN(gw-h323)[h323]#alias h323-id Berne1 SN(gw-h323)[h323]#alias e164 007 SN(gw-h323)[h323]#alias e164 *5 SN(gw-h323)[h323]#alias e164 19421 SN(gw-h323)[h323]#ras 30.5 H.323 RAS Gatekeeper Registration Type H.323 gatekeepers usually allow configuring the registration type (terminal or gateway) of the registrant (RAS). For administrative purposes it may be desirable to change the registration type on the gatekeeper.

  • Page 294: Configure H.235 Security For H.323

    Gateway Configuration M od e Gateway H.323 Command Purpose Step 1 node(gw-h323)[h323]# [no] q931-tunneling Select the appropriate Q.931 tunneling [isoip-2 | isoip-sp | isoip-ig ] protocol. E x amp le: C o nf i gu r ing Q .93 1 T un ne l i ng a nd Tu nn e l ing Opt i on The following example shows how to enable Q.931 tunneling and tunneling option isoip-2 on the H.323 gateway.
  • Page 295 Gateway Configuration calculation is a mathematical one-way function (virtually impossible to derive the password from the hash value). To enable H.235 security on H.323 perform the steps described below. Pr oc edu re To enable H.235 Security on H.323 gateway M od e Gateway H.323 Command...
  • Page 296 Gateway Configuration Step 7 node(gw-h323)[h323]#h235security general- Sets the ID of the entity to which the id general-id message is sent, e.g. a gatekeeper. Must be a string containing 2, 4, 6, ... characters. Step 8 node(gw-h323)[h323]#h235security If all parameters are set, enables H.235 security.

  • Page 297: Show And Enable The Gateway Configuration

    Gateway Configuration 172.16.224.102(gw-h323)[h323]#h235security 172.16.224.102(gw-h323)[h323]#14:27:35 H235 > Info: H.235 was started successfully 30.8 Show and 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.

  • Page 298: Examples

    Gateway Configuration 30.9 Examples 30.9.1 Branch Offices in an Enterprise Network Figure 30-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 299: 02:47:59 Sr

    Gateway Configuration 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. Instead we show the configuration steps to configure the codec.

  • Page 300: Gatekeeper In Lan Based Telephony

    Gateway Configuration SN(gw-isoip)[isoip]#exit SN(cfg)# 30.9.2 Gatekeeper in LAN Based Telephony Figure 30-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. Figure 30-3: Gatekeeper in LAN Based Telephony First we configure the CS interfaces and the call routing.
  • Page 301 Gateway Configuration Finally we enable the CS configuration by enabling the ISoIP gateway and the CS context. Note that we have omitted the binding of the CS interfaces to the ISDN ports. We also display the CS configurations with the show commands. SN(cfg)#show gateway h323 config CURRENT H.323 GATEWAY CONFIGURATION State : enabled...

  • Page 302: Mgcp/Sctp/Iua Configuration

    MGCP/SCTP/IUA Configuration 31 MGCP/SCTP/IUA CONFIGURATION This chapter provides an overview of MGCP, SCTP and IUA 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 XX, “Gateway MGCP Mode”, and Chapter XX, "Gateway IUA Mode"...

  • Page 303: Mgcp/Sctp/Iua Configuration Task List

    MGCP/SCTP/IUA Configuration Figure 31-1: MGCP and IUA Gateways between IP and CS contexts The setup is akin to the concept of H.323 or ISoIP gateways and interfaces (see software configuration guide page XX). Again a gateway entity builds the bridge between the circuit oriented world (ISDN, POTS) and the packet based world (IP).

  • Page 304: Set Up The Mgcp Gateway

    MGCP/SCTP/IUA Configuration • Set up the MGCP Gateway • Set up the IUA Gateway • Enable the ISDN port for use with SCTP/IUA • Map MGCP events to call-progress-tones • Change RSIP settings (Advanced) • Change UDP port numbers (Advanced) •...
  • Page 305 MGCP/SCTP/IUA Configuration Step 8 node(gw-mgcp)[mgcp]#use voip- Assigns a VoIP-profile to the MGCP gateway profile name Step 9 node(gw-mgcp)[mgcp]#no Enables the MGCP gateway. For debug shutdown information on startup refer to section “Debug MGCP/SCTP/IUA” in this chapter. Step 10 node(gw-mgcp)[mgcp]#show Displays the MGCP gateway configuration or gateway mgcp [mgcp] information about the MGC endpoints {configuration | {endpoint name}}...

  • Page 306: Set Up The Iua Gateway

    MGCP/SCTP/IUA Configuration >> IALN/BA02/B2: << ISDN slot 0, port 1, b-channel 1 No connections. Normally the MGC’s are in other subnets than the gateway. Therefore the SmartNode needs a route to send IP packets to the MGC. Let us assume that the IP address 172.16.1.10 is our IP router. SN(cfg)#context ip router SN(ctx-ip)[router]#route 172.25.0.0 255.255.0.0 172.16.1.10 31.4 Set up the IUA gateway...

  • Page 307: Enable The Isdn Port For Use With Sctp / Iua

    MGCP/SCTP/IUA Configuration Max Path Retrans: Max Initial Retrans: Receive Window: 2000 Delay: Max Send Queue: Max Receive Queue: Max Messages in Flight: Incoming Streams: Outgoing Streams: Max Associations: Number of Addresses: Host Address 0: 172.16.40.124 Note: No special configuration is required for SCTP since by default IUA is transported over this transport protocol.

  • Page 308: Change Rsip Settings (Advanced)

    MGCP/SCTP/IUA Configuration Ex amp le: Map MGC P Eve n t ‘pt9 ’ of t he ‘X’ p ack age t o t one 's pe c ia lInfo The following example shows how to use the call-progress-tone profile to define a new tone called specialInfo, and the MGCP event mapping to map this tone to the MGCP “pt9”...

  • Page 309: Debug Mgcp/Sctp/Iua

    MGCP/SCTP/IUA Configuration Step 1 node(gw-mgcp)[mgcp]#udp- Sets the UDP port on which the gateway listens listening-port port for incoming MGCP commands. Step 2 node(gw-mgcp)[mgcp]#mgc-udp- Sets the UDP port number on which the MGC port port listens for incoming MGCP commands. 31.9 Debug MGCP/SCTP/IUA In case of an error or system malfunction there exist some debug monitors to display detailed information about the MGCP processing.

  • Page 310: Example

    MGCP/SCTP/IUA Configuration Pr oc edu re To Enable IUA gateway debug monitors M od e administrator exec Command Purpose Step 1 node(cfg)#debug gateway iua [iua] Displays information about status changes of detail-level the IUA gateway and about IUA messages itself. The parameter detail-level defines verbosity and can range from 1 through 6 The detail level ranges from 0 to 4.
  • Page 311 MGCP/SCTP/IUA Configuration Figure 31-2: Configuration of a SmartNode in an MGCP environment. Create route to the subnet of the MGC’s: SN>enable SN#configure SN(cfg)#context ip SN(ctx-ip)[router]#route 172.25.0.0 255.255.0.0 172.33.1.1 Configure and enable MGCP gateway: SN(ctx-ip)[router]#gateway mgcp mgcp SN(gw-mgcp)[mgcp]#bind interface eth0 SN(gw-mgcp)[mgcp]#primary-mgc-ip 172.25.1.10 SN(gw-mgcp)[mgcp]#secondary-mgc-ip 172.25.1.100 SN(gw-mgcp)[mgcp]#map L_dl to defaultDialtone SN(gw-mgcp)[mgcp]#map L_bz to defaultBusytone...

  • Page 312: Voip Profile Configuration

    VoIP Profile Configuration 32 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 313: Voip Profile Configuration Task List

    VoIP Profile Configuration Figure 32-1: VoIP profile association 32.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 314: Enable Dtmf Relay

    VoIP Profile Configuration 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]#... Configuration Steps as described in the chapters below Ex amp le: C reat ing a Vo IP pro f ile This example shows how to create a VoIP profile named ISoIPProfile and enter VoIP profile configuration mode.

  • Page 315: Enable Echo Canceller

    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 dtmf- Disable DTMF relay on a specific interface relay Ex amp le: En ab ling DT MF R e lay The following example shows how to enable DTMF relay for the VoIP profile and disable it for the ISoIP interface.

  • Page 316: Enable Silence Compression

    VoIP Profile Configuration 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 Step 5 node(if-type)[if-name]#no echo- Disable echo canceller on a specific interface canceller Ex amp le: En ab le Ech o Ca nce lle r The following example shows how to enable the echo cancellation for the VoIP profile.

  • Page 317: Configure Voice Volume

    VoIP Profile Configuration SN#configure SN(cfg)#profile voip ISoIPProfile SN(pf-voip)[ISoIPPr~]#silence-compression 32.7 Configure Voice Volume The voice volume determines the voice output volume gain towards CS context as illustrated in Figure 32-4. Figure 32-4: Applying voice volume Pr oc edu re To configure voice volume M od e Profile VoIP Command...

  • Page 318: Configure Dejitter Buffer (Advanced)

    VoIP Profile Configuration Example: Configure Voice Vo lume The following example shows how to set the voice volume for the VoIP profile to 10 dB and specify an other value 20 dB for a specific H.323 interface SN>enable SN#configure SN(cfg)#profile voip ISoIPProfile SN(pf-voip)[ISoIPPr~]#voice-volume 10 SN(pf-voip)[ISoIPPr~]#exit SN(cfg)#context cs...
  • Page 319 VoIP Profile Configuration SmartWare offers two operation modes for the dejitter buffer, adaptive and fixed, as illustrated in Figure 32-6. Figure 32-6: Adaptive versus Fixed Dejitter Buffer The adaptive buffer automatically adapts to the network delay variation characteristics and in general yields the best results.

  • Page 320: 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 321: Configure Fax Handling

    VoIP Profile Configuration Pr oc edu re To disable post and high-pass filter M od e Profile VoIP Command Purpose Step 1 node(pf-voip)[name]#no post-filter Disable decoder output filter Step 2 node(pf-voip)[name]#no high- Disable decoder input high pass filter pass-filter E x amp le: D is ab le F i lt ers The following example shows how to disable the decoder output post-filter and the input high-pass filter of the VoIP profile.
  • Page 322 VoIP Profile Configuration Figure 32-8: Fax relay and fax bypass The commands described below offer more functionality than fax only. Modem connections could be configured in the same manner as fax. Use one of the protocolls V.34, V.32 etc. for configuring a modem connection.

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

    VoIP Profile Configuration Step 2 node(pf-voip)[name]#fax- Packet loss can be catered for by means of redundancy ls-redundancy level transmitting the fax data packets redundantly n times. This can be configured for both the low- speed and the high-speed traffic separately. The default for both parameters is 0 (no redundant transmission).
  • Page 324 VoIP Profile Configuration Step 3 node(cfg)#gateway gw-type gw- Change to gateway configuration mode. name Step 4 node(gw-type)[gw-name]#use The VoIP profile with name name is used by the voip-profile name VoIP gateway. 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 325: Example

    VoIP Profile Configuration volume: -9.5 dBm jitter periond: 0 ms bypass coder: g711 error correction: disabled fax settings: protocol: T.38-TCP max bit rate: 9600 bit/s data settings: modulation type: single-frequency max bit rate: 9600 bit/s hdlc: disabled DTMF settings: DTMF relay: enabled encoder mode: muted...
  • Page 326 VoIP Profile Configuration 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 aforementioned fax and data settings may be ignored. SN(cfg)#show profile voip Wire128kbit Profile Wire128kbit ------------------------------------------------------------------ dejitter settings: mode:...

  • Page 327: Voip Debugging

    VoIP Debugging 33 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 328: Warning

    VoIP Debugging 33.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. 33.4 Debugging Task List Depending on problem that has occurred one or more of the following debugging tasks should be performed.

  • Page 329: Verify Circuit Switch Connectivity

    VoIP Debugging RTT: Minimum <10ms, Maximum <10ms, Average <10ms 33.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. Additionally the set up and shut down of voice calls can be traced by the debug monitor and established calls can be displayed by the show command.
  • Page 330 VoIP Debugging 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 SN1#14:12:55 CALL > [0021] SENT [080005] SETUP (Generic Q.931) [04039090A3]...
  • Page 331 VoIP Debugging 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 CALL > [0021] SENT [08000F] CONNECT ACKNOWLEDGEMENT (Generic Q.931) 14:13:30 CALL >...

  • Page 332: Debug Isdn Data

    VoIP Debugging [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 > [8000] DROPPED SN2# 33.7 Debug ISDN Data To obtain actual information about the ISDN layers you can use the ISDN debug commands.

  • Page 333: Debug Isoip Data

    VoIP Debugging 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 Enable the H.323 debug monitor to get [detail-level] information about the transposed H.323 data.

  • Page 334: Debug Voice Over Ip Data

    33.13 How to Submit Trouble Reports to Inalp Networks Due the wealth of functionality and complexity of the products there remains a certain number of problems, either pertaining to the Inalp Networks AG product or the interoperability with other vendor's products.
  • Page 335 VoIP Debugging • Problem Description: Add a description of the problem, if possible together with applicable augmented information with a diagram of the network setup (with Microsoft tools). • Running Configuration and Software and Hardware Version Information: With the Command Line Interface commands 'show running-config' and 'show version' you can display the currently active configuration of the system (in a Telnet and/or console session).

  • Page 336: Appendix A

    Appendix A 34 APPENDIX A 34.1 Configuration Mode Overview Figure 34-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 337: Smartware 2.10 Command Summary

    Appendix A Figure 34-1: Configuration Modes and Bind and Link Commands Overview 34.2 SmartWare 2.10 Command Summary 34.2.1 Introduction The SmartWare 2.10 comm ands are collected in configuration modes as illustrated Figure 34- Following all commands in the configuration modes are listed. The configuration modes are listed in order as shown in Figure 34-1.

  • Page 338: Command Summary

    Appendix A • Arguments where you must supply the value are surrounded by <angle brackets>. • Optional arguments within commands are shown in square brackets ([ ]) • Alternative parameters within commands are separated by vertical bars ( | ). •...
  • Page 339 Appendix A show clock show uptime show ip route show dsp {<slot> | (statistics <slot> ) | (channel statistics <slot> ) | (sw-version <slot> ) | (test- result <slot> ) } show profile voip [<show_name> ] show profile tone-set [<show_name> ] show profile call-progress-tone [<show_name>...
  • Page 340 Appendix A pdlfnerr pdlprint pdlprnerr pdlprnwrn pdlsm pdlsrc pdlmisc pdlmtask pdllist pdltimer per pererr q931 ra rasctrl rasindb seli timer tpktchan tunnctrl udpchan unreg vt ] [<detail> ] [no] debug session-control [switch ] [<detail> ] dsp {(up [<slot> ] ) | (down [<slot> ] ) | (reconfigure [<slot> ] ) | (test [<slot> ] ) | (channel {(restart [<slot>...

  • Page 341: Cli Version

    Appendix A ecm state <ecm> {initial|prepared|linked|started} show ecm show db [<table> ] snake show command stack show bootloader info show image info show board-descriptor show test test {all | (<test> [<param> ] ) } show memory-usage configure configure cli version <version> [no] administrator <account>...
  • Page 342 Appendix A ic voice <slot> pcm {(law-select {aLaw | uLaw } ) } status-request-timeout {<timeout> | none } exit exit profile_acl [no] profile acl <profile_name> {permit|deny} {(ip {any | (host <src_ip> ) | (<src_ip> <src_wildcard> ) } {any | (host <dst_ip>...
  • Page 343 Appendix A [no] queue-limit <value> [no] set ip dscp <value> [no] set ip precedence <value> [no] set ip tos <value> [no] set layer2 cos <value> [no] debug queue statistics [<value> ] exit exit profile_napt [no] profile napt <napt-profile_name> [no] icmp default <host> [no] static {udp|tcp} <port>...
  • Page 344 Appendix A dtmf-high-frequency-level {mute | <dtmf_high_frequency_level> } dtmf-low-frequency-level {mute | <dtmf_low_frequency_level> } dtmf-duration <dtmf_duration> dtmf-interspace <dtmf_interspace> dtmf-signal-level {mute | <dtmf_signal_level> } [no] map {(call_progress_tone <internal_tone_name> <call_progress_tone_name> ) } exit profile_voip [no] profile voip <name> hybrid-loss {0|3|6|9} non-linear-processor-mode {adaptive|disabled|silence} [no] high-pass-filter [no] post-filter [no] dtmf-relay [no] dtmf-mute-encoder...

  • Page 345: Context Ip Router

    Appendix A [no] netbios-name-server <address> [no] netbios-node-type {{b-node|p-node|m-node|h-node} } [no] bootfile <bootfile> [no] next-server <address> exit context_ip context ip [router ] [no] dhcp-server dhcp-server clear-lease {all | <address> } [no] dhcp-server use <name> [no] route <destaddr> <destmask> {<gwaddr> | <interface> } [<metric> ] multicast-send default-interface <ip_interface>...

  • Page 346: No Number-Prefix National

    Appendix A [no] authentication {(chap pap ) | {chap|pap} } [no] identification {outbound|inbound} <id> [password <password> ] [no] timeout {absolute|idle} <timeout> [no] max-sessions <max-sessions> [no] ipaddress <address> [no] callback [mandatory ] [destination {any|some|fix} ] [no] callback dial-string <dial-string> [no] bind interface <interface> [router ] exit context_cs context cs [switch ]...
  • Page 347 Appendix A [no] digit-collection {(timeout [<val> ] ) | (terminating-char <val> ) | (nr-length <val> ) } [no] remoteip <remote_ip> [no] portaddress <portaddress> [no] codec {g711alaw64k|g711ulaw64k|g723_6k3|g729|transparent|t38_udp} [exclusive ] dejitter-mode {adaptive|static} dejitter-max-delay <dejitter_max_delay> dejitter-max-packet-loss <dejitter_max_packet_loss> dejitter-shrink-speed <dejitter_shrink_speed> dejitter-grow-step <dejitter_grow_step> dejitter-grow-attenuation <dejitter_grow_attenuation> [no] dtmf-relay [no] echo-canceller [no] silence-compression...
  • Page 348 Appendix A gateway_h323 gateway h323 [h323 ] [no] alias {h323-id | e164 } <alias> [no] codec {g711alaw64k | g711ulaw64k | g723_6k3 | g729 | transparent | t38_udp } [<txlen> <rxlen> ] [no] faststart [no] early-h245 terminal-type {terminal | gateway } [no] ras call-signaling-port <ip_port>...
  • Page 349 Appendix A port serial <slot> <port> [no] encapsulation {framerelay|ppp} hardware-port {v35 | x21 } transmit-data-on-edge {positive | negative } crc-type {crc16 | crc32 } length <length> threshold <threshold> mask <mask> address {address-1 | address-2 | address-3 | address-4 } <address> [no] use profile ppp <profile>...
  • Page 350 Appendix A port {pstn | isdn } <slot> <port> [no] down [no] <key_action-type> <low> <high> <key_action-type> {up | down | up-cyclic | down-cyclic } <key_action-type> {pp | pmp } <key_action-type> {dss1 | pss1 } <key_action-type> {etsi | pss1-old } [no] <key_action-type> <channel> [no] <key_action-type>...

  • Page 351: Appendix B

    Appendix B 35 APPENDIX B 35.1 Internetworking Terms and Acronyms Abbreviation 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 352 Appendix B Abbreviation Meaning Digital Signal Processor DTMF Dual Tone Multi-frequency 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 SmartWare Frame Relay G.711 ITU-T Voice encoding standard G.723 ITU-T Voice compression standard Graphic User Interface...
  • Page 353 Appendix B Abbreviation Meaning L2TP Layer Two Tunneling Protocol Local Area Network Least Cost Routing LDAP Lightweight Directory Access Protocol Local Exchange Light Emitting Diode Line Termination MGCP Media Gateway Control Protocol MIB II Management Information Base II Modem Modulator – Demodulator Multiple Subscriber Number NAPT Network Address Port Translation...
  • Page 354 Appendix B Abbreviation Meaning 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 SN-connection for Subscriber Line Segmentation and Reassembly S-Bus Subscriber Line (Connection) Bus...
  • Page 355 Appendix B Abbreviation Meaning Variable Bit Rate Virtual Channel Identifier VoIP Voice over Internet Protocol Virtual Path Identifier Wide Area Network Software Configuration Guide Release 2.10, Revision 1.00...

  • Page 356: Appendix C

    Appendix C 36 APPENDIX C 36.1 Used IP Ports in SmartWare 2.10 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 357: Available Voice Codecs In Smartware 2.10

    Appendix C 36.2 Available Voice Codecs in SmartWare 2.10 Protocol Codec Net Band- Min. Com- Used Band- Usage width per pression width per Call (kbps) Delay Call (kbps, (ms) incl. IP header) ISoIP G.711 A- Uncompressed, best voice quality, European audio- digitizing G.711 u- Uncompressed, best voice...

Table of Contents