SmartNode Series SmartWare Release 5.2 Software Configuration Guide Sales Office: +1 (301) 975-1000 Technical Support: +1 (301) 975-1007 E-mail: support@patton.com URL: www.patton.com Part Number: 07MSWR52_SCG, Rev.
Patton Electronics Company, Inc. 7622 Rickenbacker Drive, Gaithersburg, MD 20879 USA Tel: +1 (301) 975-1000 • Fax: +1 (301) 869-9293 • Support: +1 (301) 975-1007 Web: www.patton.com • E-mail: support@patton.com Copyright Statement Copyright © 2008, Patton Electronics Company. All rights reserved. Trademark Statement The terms SmartWare, SmartView, SmartLink, and SmartNode are trademarks of Patton Electronics Company.
Summary Table of Contents 1 System overview ............................................................................................................................................ 38 2 Configuration concepts ................................................................................................................................. 44 3 Command line interface (CLI) ......................................................................................................................
SmartWare Software Configuration Guide 32 VPN configuration ...................................................................................................................................... 362 33 CS interface configuration........................................................................................................................... 381 34 ISDN interface configuration......................................................................................................................
Table of Contents Summary Table of Contents ........................................................................................................................... 3 Table of Contents ........................................................................................................................................... 5 List of Figures ............................................................................................................................................... 27 List of Tables ....
SmartWare Software Configuration Guide Table of Contents 3 Command line interface (CLI) ...................................................................................................................... 49 Introduction ..........................................................................................................................................................50 Command modes ....................................................................................................................
SmartWare Software Configuration Guide Table of Contents Upgrading the software directly ......................................................................................................................71 Auto provisioning of firmware and configuration ..................................................................................................72 Boot procedure.........................................................................................................................................
SmartWare Software Configuration Guide Table of Contents General AAA Configuration ..........................................................................................................................104 RADIUS configuration........................................................................................................................................106 Configuring RADIUS clients ..................................................................................................................
SmartWare Software Configuration Guide Table of Contents Debug ARP ...................................................................................................................................................129 Traceroute ....................................................................................................................................................130 Configuring the IGMP Proxy.......................................................................................................
SmartWare Software Configuration Guide Table of Contents Quick references ..................................................................................................................................................155 Setting the modem rate .................................................................................................................................155 Command cross reference ..........................................................................................................
SmartWare Software Configuration Guide Table of Contents Enabling a Frame Relay PVC ........................................................................................................................184 Disabling a Frame Relay PVC .......................................................................................................................184 Debugging Frame Relay ................................................................................................................................
SmartWare Software Configuration Guide Table of Contents Configuring channel-group timeslots ............................................................................................................208 Configuring channel-group encapsulation .....................................................................................................208 Entering HDLC configuration mode ............................................................................................................
SmartWare Software Configuration Guide Table of Contents Using PVC channels with PPPoE .................................................................................................................233 Diagnostics ...................................................................................................................................................234 Troubleshooting DSL Connections ...............................................................................................................
SmartWare Software Configuration Guide Table of Contents Mapping out the goals of the access control list .............................................................................................256 Creating an access control list profile and enter configuration mode .............................................................257 Adding a filter rule to the current access control list profile ...........................................................................
SmartWare Software Configuration Guide Table of Contents Recommended public SNTP time servers............................................................................................................290 NIST Internet time service ............................................................................................................................290 Additional information on NTP and a list of other NTP servers ...................................................................
SmartWare Software Configuration Guide Table of Contents Configuring a PPPoE session ........................................................................................................................319 Configuring PPP over a HDLC Link ............................................................................................................321 Creating a PPP profile ...................................................................................................................................
SmartWare Software Configuration Guide Table of Contents Configuring an H.323 VoIP connection .............................................................................................................348 Configuring a SIP VoIP connection ....................................................................................................................348 Activating CS context configuration .................................................................................................................
SmartWare Software Configuration Guide Table of Contents SmartNode configuration ........................................................................................................................378 Cisco router configuration .......................................................................................................................378 IPsec tunnel, 3DES encryption at 192 bit key length, ESP authentication with HMAC-MD5-96 ................379 SmartNode configuration ......................
SmartWare Software Configuration Guide Table of Contents FXS supplementary services description...............................................................................................................410 Call hold .......................................................................................................................................................411 Call waiting ..........................................................................................................................
SmartWare Software Configuration Guide Table of Contents Enabling the early call connect (optional) .....................................................................................................436 Enabling the early call disconnect (optional) .................................................................................................437 Enabling the via address support (optional) ...................................................................................................
SmartWare Software Configuration Guide Table of Contents Regular Expressions .................................................................................................................................466 Digit Collection ......................................................................................................................................468 Digit Collection Variants .......................................................................................................................
SmartWare Software Configuration Guide Table of Contents Enable sending of “302 moved temporary” message on SIP. .............................................................522 Allow Push-Back .....................................................................................................................................522 Enable push-back – aaa service ..........................................................................................................522 Enable push-back – bridge service ....
SmartWare Software Configuration Guide Table of Contents 45 H.323 gateway configuration ...................................................................................................................... 546 Introduction ........................................................................................................................................................547 Gateway configuration task list ..................................................................................................
SmartWare Software Configuration Guide Table of Contents VoIP profile configuration task list ......................................................................................................................575 Creating a VoIP profile .................................................................................................................................575 Configure codecs ........................................................................................................................
SmartWare Software Configuration Guide Table of Contents Creating an Authentication Service ...............................................................................................................605 Configuring a Realm .....................................................................................................................................606 Configuring the authentication protocol .......................................................................................................
SmartWare Software Configuration Guide Table of Contents Verify an outgoing call ............................................................................................................................638 Using SmartWare’s internal call generator .....................................................................................................639 Debugging voice data .....................................................................................................................................
List of Figures 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 Basic system (abstract) model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Typical carrier network application with a SmartNode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Typical enterprise network with SmartNode . . . . . . . . . . . .
SmartWare Software Configuration Guide 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 Remote office in an Enterprise network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342 Direct call routing from one SmartNode to another . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 SmartNode in an Enterprise network . . . . .
List of Tables 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 General conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Mouse conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Command edit shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About this guide The objective of this SmartWare Software Configuration Guide is to provide information concerning the syntax and usage of the command set. For hardware specfic information, refer to the getting started guide that came with your unit.
SmartWare Software Configuration Guide About this guide Structure This guide contains the following chapters and appendices: • Chapter 1, "System overview" on page 38 provides an overview of the main elements of a SmartWare system. • Chapter 2, "Configuration concepts" on page 44 introduces basic SmartWare configuration concepts. • Chapter 3, "Command line interface (CLI)" on page 49 gives an overview of the CLI and the basic features that allow you to navigate the CLI and edit commands effectively.
SmartWare Software Configuration Guide About this guide • Chapter 19, "ISDN configuration" on page 217 describes the configuration of the Q.921 and Q.931 protocol and how to bind the ISDN protocol to an application. • Chapter 20, "RBS configuration" on page 225 describes the configuration of the Robbed Bit Signaling (RBS) protocol and how to bind it to the Call Control application.
SmartWare Software Configuration Guide About this guide • Chapter 36, "FXO interface configuration" on page 414 provides an overview of FXO interfaces and the tasks involved in configuring them. • Chapter 38, "H.323 interface configuration" on page 431 provides an overview of H.323 interfaces used by H.323 gateways and describes the specific tasks involved in their configuration.
SmartWare Software Configuration Guide About this guide • Appendix E, "Used IP ports & available voice codecs" on page 662 describes the used IP ports and available voice codecs in SmartWare. • Appendix F, "Notes for upgrading from R3.10 to R3.20" on page 618 describes how to upgrade a SmartNode device from Release 3.10 to 3.20. Precautions The following are used in this guide to help you become aware of potential problems: Note A note presents additional information or interesting sidelights.
SmartWare Software Configuration Guide About this guide Table 1. General conventions Convention # Meaning An hash sign at the beginning of a line indicates a comment line.
SmartWare Software Configuration Guide About this guide Mouse conventions The following conventions are used when describing mouse actions: Table 2. Mouse conventions Convention Meaning Left mouse button This button refers to the primary or leftmost mouse button (unless you have changed the default configuration). Right mouse button This button refers the secondary or rightmost mouse button (unless you have changed the default configuration).
SmartWare Software Configuration Guide About this guide Warranty Service and Returned Merchandise Authorizations (RMAs) Patton Electronics is an ISO-9001 certified manufacturer and our products are carefully tested before shipment. All of our products are backed by a comprehensive warranty program. Note If you purchased your equipment from a Patton Electronics reseller, ask your reseller how you should proceed with warranty service.
Chapter 1 System overview Chapter contents Introduction ..........................................................................................................................................................39 SmartWare embedded software .............................................................................................................................40 Applications.................................................................................................................................
SmartWare Software Configuration Guide 1 • System overview Introduction This chapter provides an overview of the main elements of a SmartNode system.
SmartWare Software Configuration Guide 1 • System overview Figure 1 depicts the basic system model of a Patton SmartNode. All SmartNode devices have the following main components: • 64k circuit switching between on-board ISDN ports and between ISDN and PSTN interface cards. The circuit switching engine uses dedicated hardware resources and therefore can bypass the VoIP gateway and packet routing engine.
SmartWare Software Configuration Guide 1 • System overview Applications The Patton SmartNode product family consists of highly flexible multi-service IP network devices, which fit a range of networking applications. This section provides an overview of the following SmartNode applications and the main elements in a SmartNode network. • Carrier networks—SmartNodes are used as customer gateways or integrated access devices at the customer premises.
SmartWare Software Configuration Guide 1 • System overview Typical services in these networks are softswitch-based telephony, PSTN access through V5.2 gateways, PBX networking services, and LAN interconnection. Typical access technologies for these networks include xDSL, WLL, PowerLine, cable and conventional leased lines. With the use of an external modem, the SmartNode can connect to leased lines or any bridged-Ethernet broadband access.
SmartWare Software Configuration Guide 1 • System overview PSTN IPPBX LAN Node IP Phones Figure 4. Typical LAN telephony system with a SmartNode gateway LAN telephony With its voice-over-IP gateway features, the SmartNode can be used as a standalone gateway for VoIP telephony (see figure 4). A standalone gateway has performance reliability and scalability advantages compared with PC-based gateway cards.
Chapter 2 Configuration concepts Chapter contents Introduction ..........................................................................................................................................................45 Contexts and Gateways..........................................................................................................................................46 Context ........................................................................................................................
SmartWare Software Configuration Guide 2 • Configuration concepts Introduction This chapter introduces basic SmartWare configuration concepts. A good understanding of these concepts is vital for the configuration tasks explained in the remaining chapters of this guide. Patton strongly recommends that you read through this chapter because it introduces the fundamental ideas behind the structure of the command line interface.
SmartWare Software Configuration Guide 2 • Configuration concepts lines) commands. For example, you need bind commands to bind a physical port to a logical interface, and use commands to assign profiles to contexts. The sections that follow refer to figure 5 on page 45 and describe the concepts and elements in more detail. Contexts and Gateways Context A context represents one specific networking technology or protocol, namely IP (Internet Protocol) or CS (circuit-switching).
SmartWare Software Configuration Guide 2 • Configuration concepts Interfaces, Ports, and Bindings Interfaces The concept of an interface in SmartWare differs from that in traditional networking devices. Traditionally, the term interface is often synonymous with port or circuit, which are physical entities. In SmartWare however, an interface is a logical construct that provides higher-layer protocol and service information, such as layer 3 addressing.
SmartWare Software Configuration Guide 2 • Configuration concepts Profiles and Use commands Profiles Profiles provide configuration shortcuts. They contain specific settings that can be used in multiple contexts, interfaces, or gateways. This concept allows to avoid repetitions of groups of configuration commands that are the same for multiple elements in a configuration. Profiles used in the IP and CS contexts are shown in figure 5 on page 45.
Chapter 3 Command line interface (CLI) Chapter contents Introduction ..........................................................................................................................................................50 Command modes ..................................................................................................................................................50 CLI prompt ..............................................................................................................
SmartWare Software Configuration Guide 3 • Command line interface (CLI) Introduction The primary user interface to SmartWare is the command line interface (CLI). You can access the CLI via the SmartNode console port or through a Telnet session. The CLI lets you configure the complete SmartWare functionality. You can enter CLI commands online or as a configuration script in the form of a text file. The CLI also includes monitoring and debugging commands.
SmartWare Software Configuration Guide 3 • Command line interface (CLI) Navigating the CLI Initial mode When you initiate a session, you can log in with operator or administrator privileges. Whichever login you use, the CLI is always set to operator exec (non-privileged exec) mode by default upon startup. This mode allows you to examine the state of the system using a subset of the available CLI commands.
SmartWare Software Configuration Guide 3 • Command line interface (CLI) CLI to complete the command at the prompt. If the number of characters is not sufficient to uniquely identify the command, the CLI will provide a list with all commands starting with the typed characters. For example, if you enter the string co in the configure mode and press , the selections configure, copy, and context are displayed.
Chapter 4 Accessing the CLI Chapter contents Introduction ..........................................................................................................................................................54 Accessing the SmartWare CLI task list...................................................................................................................54 Accessing via the console port .............................................................................................................
SmartWare Software Configuration Guide 4 • Accessing the CLI Introduction SmartNode products are designed for remote management and volume deployment. The management and configuration of SmartNodes is therefore based on IP network connectivity. Once a SmartNode is connected to, and addressable in, an IP network, you can remotely perform all configuration, management, and maintenance tasks.
SmartWare Software Configuration Guide 4 • Accessing the CLI • Ending a Telnet or console port session (see page 64) Accessing via the console port If a console port is available, the host computer can be connected directly to it with a serial cable (see figure 6). The host must use a terminal emulation application that supports serial interface communication. Serial interface Console Node Node Host Figure 6.
SmartWare Software Configuration Guide 4 • Accessing the CLI Accessing via a Telnet session This is the most commonly used and recommended method for connecting to a SmartNode. It is way faster than console access.The Telnet host accesses the SmartNode via its network interface. Note If the IP configuration of the Ethernet port (LAN port) is not known or is incorrectly configured, you will have to use the console interface.
SmartWare Software Configuration Guide 4 • Accessing the CLI Figure 7. Login display Upon logging in you are in operator execution mode, indicated by the “>” as command line prompt. Now you can enter system commands. Note Details on screen in figure 7, such as the IP address in the system prompt and window header bar, may be different on your unit. IMPORTANT You are responsible for creating a new administrator account to maintain system security.
SmartWare Software Configuration Guide 4 • Accessing the CLI Password encryption Unencrypted passwords can be stolen by hackers using protocol analyzers to scan packets or by examining the configuration file—to protect against that type of theft, SmartWare encrypts passwords by default. Encryption prevents the password from being readable in the configuration file.
SmartWare Software Configuration Guide 4 • Accessing the CLI node(cfg)#copy running-config startup-config Creating an administrator account Administrators can run the enable command and access additional information within the SmartWare configuration modes. Therefore administrators can modify the system configuration, as well as view all relevant system information.
SmartWare Software Configuration Guide 4 • Accessing the CLI Mode: Configure Step 1 Command Purpose [name](cfg)#terminal ssh use authentication used for user authentication. The AAA profile “default” is uses as when not specified otherwise. Mode: Enable Step 1 Command Purpose [name]#show ssh Displays status information of the SSH server. Mode: Enable Step 1 Command Purpose [name]#debug ssh Prints debug information of the SSH server.
SmartWare Software Configuration Guide 4 • Accessing the CLI Example: Display account information The following example shows how to display information about existing administrator and operator accounts. node#show accounts administrator accounts: super operator accounts: support Switching to another account A user can use the su command to switch from one user account to working in another. With this command, a user can change from his current account to another existing account ‘name’.
SmartWare Software Configuration Guide 4 • Accessing the CLI Example: Checking identity and connected users The following example shows how to report who is logged in or more detailed information about users and process states, depending on the execution mode in which you are working. Used in administrator execution mode: node#who ID User name * 0 administrator 1 support Note State exec exec Idle 00:00:00 00:01:56 Location 172.16.224.44:1160 172.16.224.
SmartWare Software Configuration Guide 4 • Accessing the CLI 192.168.1.1(pf-voip)[default]#codec 3 before 1 192.168.1.1(pf-voip)[default]#show running-config ... profile voip default codec 1 g723-6k3 rx-length 30 tx-length 30 codec 2 g711ulaw64k rx-length 20 tx-length 20 codec 3 g711alaw64k rx-length 20 tx-length 20 dejitter-max-delay 200 ... Note Succeeding indexes are automatically renumbered. Example 2: Moving the G.723 codec back position 3 This command moves the G.
SmartWare Software Configuration Guide 4 • Accessing the CLI Ending a Telnet or console port session Use the logout command in the operator or administration execution mode to end a Telnet or console port session. To confirm the logout command, you must enter yes on the dialog line as shown in the example below. Mode: Operator execution Step Command Purpose 1 node>logout Terminates the session after a confirmation by the user.
Chapter 5 System image handling Chapter contents Introduction ..........................................................................................................................................................66 Memory regions in SmartWare..............................................................................................................................67 System image handling task list .......................................................................................................
SmartWare Software Configuration Guide 5 • System image handling Introduction This chapter describes how to load, maintain, and update the various software images in the SmartNode. The SmartWare system software consists of the application image and the driver images. The images are stored in persistent (non-volatile) memory. The application image is the software which actually operates the SmartNode. Driver images are used to operate the various optional PMC interface cards.
SmartWare Software Configuration Guide 5 • System image handling Memory regions in SmartWare The SmartNode’s memory contains several logical regions and several physical regions as shown in figure 8 on page 68, each separate from the other. Note You will use a remote TFTP server for uploading and downloading the application image, the driver images, and the various configuration files to the SmartNode.
SmartWare Software Configuration Guide 5 • System image handling Operating configurations cannot be executed from the persistent memory, so the configuration used for operating the SmartNode is copied into the volatile memory of the SmartNode prior to normal operation. This procedure takes place after the system bootstrap, where the application image (i.e. SmartWare) is started and a configuration must be available.
SmartWare Software Configuration Guide 5 • System image handling Displaying system image information This procedure displays information about system images and driver software Mode: Administrator execution Step 1 Command show version Purpose Lists the system software release version, information about optional interface cards mounted in slots and other information that is the currently running system software.
SmartWare Software Configuration Guide 5 • System image handling Comment lines must have a hash character # in column one and can appear anywhere in the script file. Comment lines contain information for administrators or operators who maintain or use the script file. The following example shows a script file used to download a system image and command line syntax definition file from a TFTP server. # script file for system image download # Patton Electronics Co. 2001-10-24 image.bin 1369474 21; ver 2300.
SmartWare Software Configuration Guide 5 • System image handling After the successful download, either issue the reload command (in order to start the IPNode with the new software) or restart the H.323 gateway, thus enabling calls again (with the current software): node(gw-h323)[h323]#no shutdown Upgrading the software directly It is possible to upgrade the software directly by passing the name of the delivered zip-file to the CLI command “copy”. The SmartWare downloads the whole ZIP file.
SmartWare Software Configuration Guide 5 • System image handling Auto provisioning of firmware and configuration The new auto provisioning capability enables you to automatically distribute up-to-date configurations and firmware to a large number of units using TFTP. It works as follows: The unit downloads a specific file from a TFTP server. If this file has changed since the last download, it is stored and executed. If the file on the server did not change since the last download, no action is taken.
SmartWare Software Configuration Guide Step 5 • System image handling Command 2 [name] (pf-prov)[CONFIG]#location 1 tftp://tftp1.provider.net /configs/ $(system.mac).cfg 3 [name] (pf-prov)[CONFIG]#location 2 tftp://172.16.1.33/configs/$(system.mac).cfg 4 [name] (pf-prov)[CONFIG]#activation reload graceful Purpose Specifies the location of the file to check for changes. $(system.mac) is a placeholder for the unit’s MAC address of ETH 0/0.
SmartWare Software Configuration Guide 5 • System image handling Boot procedure During a normal boot procedure of a SmartNode, the bootstrap application checks for an application image in the persistent memory of the logical region nvram:. The application image is then executed, i.e. the SmartWare is started module by module. One of the last start-up tasks to finish in bringing up the entire system is handling the operating configuration.
SmartWare Software Configuration Guide 5 • System image handling The bootloader ensures that basic operations, network access, and downloads are possible in case of interrupted or corrupted application image downloads. After downloading an application image (that is, new system software/software upgrade), the bootloader ensures that basic operations, network access, and downloads are possible in case of interrupted or corrupted application image downloads.
Chapter 6 Configuration file handling Chapter contents Introduction ..........................................................................................................................................................77 Understanding configuration files ...................................................................................................................77 Factory configuration ...............................................................................................................
SmartWare Software Configuration Guide 6 • Configuration file handling Introduction This chapter describes how to upload and download configuration files from and to SmartWare. A configuration file is a batch file of SmartWare commands used in the software modules that perform specific functions of the SmartNode. This chapter also describes some aspects of configuration file management. Refer to chapter 5, “System image handling” on page 65 for more information.
SmartWare Software Configuration Guide 6 • Configuration file handling Figure 10, shows the characteristics of a configuration file. It is stored on a TFTP server in the file myconfig.cfg for later download. The command syntax used to enter commands with the CLI and add commands in configuration files is identical. For better comprehension, you can add comments in configuration files. To add a line with a comment to your configuration file, simply begin the line with the hash (#) character.
SmartWare Software Configuration Guide 6 • Configuration file handling bind gateway h323 # H.323 gateway primarily used gateway h323 faststart no ras gatekeeper-discovery auto bind interface lan router no shutdown port ethernet 0 0 medium auto encapsulation ip bind interface lan router no shutdown port ethernet 0 1 medium 10 half encapsulation ip bind interface wan router no shutdown Figure 10. Sample configuration file Each configuration file stored in the flash memory needs a unique name.
SmartWare Software Configuration Guide 6 • Configuration file handling • Copying configurations within the local memory (see page 80) • Replacing the startup configuration with a configuration from the Flash memory (see page 81) • Copying configurations to and from a remote storing location (see page 82) • Replacing the startup configuration with a configuration downloaded from the TFTP server (see page 83) • Displaying configuration file information (see page 83) • Modifying the running configuration at
SmartWare Software Configuration Guide 6 • Configuration file handling You can copy the current running configuration into the persistent memory region nvram: under a user-specified name, if you want to preserve that configuration. In addition, an already existing configuration is usually copied into the persistent memory region nvram: by using a user-specified name, for conservation or later activation.
SmartWare Software Configuration Guide 6 • Configuration file handling Copying configurations to and from a remote storage location Configuration files can be copied from local memory (persistent or volatile region) to a remote data store. From within SmartWare, the remote TFTP server is represented by the memory region tftp: in combination with the IP address of the TFTP server and the name and path of the configuration file.
SmartWare Software Configuration Guide 6 • Configuration file handling Replacing the startup configuration with a configuration downloaded from TFTP server From within the administration execution mode, you can replace the startup-configuration by downloading a configuration from the TFTP server into the flash memory area where to store the startup configuration.
SmartWare Software Configuration Guide IMPORTANT Note 6 • Configuration file handling It is recommended that you never save a configuration in startupconfig or a user-specific configuration with the cli config defaults command because the additional list of default commands consumes significant portions of the nvram: memory. Application files can be very long when displayed (by using the show command).
SmartWare Software Configuration Guide 6 • Configuration file handling Example: Modifying the running configuration at the CLI The following example shows how to modify the currently running configuration via the CLI and save it as the startup configuration.
SmartWare Software Configuration Guide 6 • Configuration file handling Example: Modifying the running configuration offline The following example shows how to upload the running configuration from the SmartNode to the file current-config on a TFTP server at IP address 172.16.36.80. The uploaded configuration file is written into the root directory specified by the TFTP server settings, and overwrites any existing file with the same name.
SmartWare Software Configuration Guide 6 • Configuration file handling startup-config factory-config Encrypted file download This section explains how configuration files can be transported encrypted over IP. TFTP as a configuration download mechanism has the advantage of being extremely simple (trivial) and applicable in any network without any requirements for specialized management servers or applications. It has the disadvantage of being completely insecure.
SmartWare Software Configuration Guide 6 • Configuration file handling enctool decrypt [] A log file lists the last up/downloads: show log file-transfer Use Cases Install a custom encryption key (optional) You can install a custom encryption key with the SmartNode. The encryption key is used to automatically decrypt an encrypted configuration file that is downloaded later. A default encryption key is already installed on the SmartNode.
SmartWare Software Configuration Guide 6 • Configuration file handling 123100000020002abc000cf187d909XYZ Then you have to download the created key file to the SmartNode. Open a telnet session and type in the following commands: >enable #copy tftp:/// key: where is the IP address of your TFTP server and is the path to the key file relative to the TFTP root. IMPORTANT The downloaded key also defines how the passwords are encrypted in your configuration files.
Chapter 7 Basic system management Chapter contents Introduction ..........................................................................................................................................................91 Basic system management configuration task list ...................................................................................................91 Managing feature license keys .............................................................................................................
SmartWare Software Configuration Guide 7 • Basic system management Introduction This chapter describes parameters that report basic system information to the operator or administrator, and their configuration.
SmartWare Software Configuration Guide 7 • Basic system management Managing feature license keys Several features of the firmware require a system specific license key to be installed to enable the feature. This section describes how to install the feature license keys on your equipment. Because license keys comprise very long strings of characters, the standard way of installing them is to download the file containing the license keys from a TFTP server to the equipment.
SmartWare Software Configuration Guide 7 • Basic system management node(cfg)#show licenses VPN [vpn] License serial number: 14343534 Status: Active node(cfg)# Setting system information The system information includes the following parameters: • Contact • Hostname • Location • Provider • Subscriber • Supplier By default there is no information specified for any of the above parameters. System contact information tells the user how to contact the information service, e.g.
SmartWare Software Configuration Guide 7 • Basic system management Mode: Configure Step 1 2 3 4 5 6 Command node(cfg)#system node(cfg)#system node(cfg)#system node(cfg)#system node(cfg)#system node(cfg)#system Note Purpose contact information hostname information location information provider information subscriber information supplier information Sets Sets Sets Sets Sets Sets the the the the the the contact information to information hostname to information location information to information provi
SmartWare Software Configuration Guide 7 • Basic system management Example: Setting the system banner The following example shows how to set a message for the system banner for your device, if you start from the configuration mode. node(cfg)#banner \n#\n# The password of all operators has changed\n# please contact the administrator\n#" Setting time and date All SmartNode devices provide time-of-day and date services. These services allow the products to accurately keep track of the current time and date.
SmartWare Software Configuration Guide 7 • Basic system management Display time since last restart This procedure describes how to display the time since last restart Mode: Operator execution Step 1 Command node>show uptime Purpose Display the time since last restart. Example: The following example shows how to display the uptime of your device, if you start from the configuration mode.
SmartWare Software Configuration Guide 7 • Basic system management Example: Defining the desired CLI version The following example shows how to determine the running CLI version and define CLI version 2.10 for your device, if you start from the configuration mode. node(cfg)#show version cli CLI version : 3.00 node(cfg)#cli version 2.10 Restarting the system In case the SmartNode has to be restarted, the reload command must be used.
SmartWare Software Configuration Guide 7 • Basic system management System resets may have a number of reasons, the most prominent being a manual reset issued on the Telnet/ console (‘reload’). Other reset reasons include power off failures and system failures. In order to pinpoint the problem, the reset log contains the reset cause. Mode: Administrator execution Step 1 2 Command Purpose node#show log [event] Show event log. node#show log supervisor Show log of the system supervisor.
SmartWare Software Configuration Guide 7 • Basic system management Mode: Administrator execution Step 1 2 3 4 5 6 Command node# node#jobs node#fg jobid node# Purpose Execute the first command Suspend the active command and get system prompt back Execute the second command Shows the currently running commands Brings job with jobid back to foreground Terminates the currently running command Example: Controlling Command Execution The following example shows how to suspend an active command
SmartWare Software Configuration Guide 7 • Basic system management Timed execution of CLI command The command timer allows the timed execution of CLI commands. The timer command is incremental; this means for each time it is entered, a new timer is created. All timers appear in the running-configuration, except if they have been created with the volatile option. It is possible to specify for each timer the start time and the reoccurrence.
SmartWare Software Configuration Guide Step Command 2 [name] (sys)#[no] terminal idle-timelogout 3 [name] (sys)#terminal more 4 [name] (sys)#terminal width 7 • Basic system management Purpose After 30 minutes without user input, a terminal session is automatically closed. If longer session periods are required (logging/debugging) this command allows to increase the session timeout, or to disable it completely.
Chapter 8 RADIUS Client Configuration Chapter contents Introduction ........................................................................................................................................................103 The AAA component ..........................................................................................................................................103 General AAA Configuration ....................................................................................................
SmartWare Software Configuration Guide 8 • RADIUS Client Configuration Introduction This chapter provides an overview of the authentication, authorization, and accounting (AAA) component and describes how to configure the RADIUS client, a subpart of the AAA component. It is important to understand how AAA works before configuring the RADIUS client. This chapter also describes the local database accounts configuration, which is another subpart of AAA.
SmartWare Software Configuration Guide 8 • RADIUS Client Configuration Figure 14 illustrates the authentication procedure for a user logging into a SmartNode that is configured to use RADIUS as authentication method. AAA Server (RADIUS) 3. Authentication accepted 4. Access granted IP 2. Authentication requested User 1. Login Request Node Figure 14. Authentication procedure with a RADIUS server General AAA Configuration The AAA component consists of AAA profiles and AAA methods. A service (e.g.
SmartWare Software Configuration Guide 8 • RADIUS Client Configuration 3. Query the local database (see “Configuring the local database accounts” on page 111 for information on how to configure the local database) If, e.g. radius_deepblue is not available, radius_extern will be queried after a timeout. But if radius_deepblue gives an answer that rejects the login request, the remaining methods are not used and the login is denied.
SmartWare Software Configuration Guide 8 • RADIUS Client Configuration node(pf-auth)[remote-~]#exit node(cfg)# node(cfg)#profile authentication local-only node(pf-auth)[local-o~]#method local node(pf-auth)[local-o~]#method none node(pf-auth)[local-o~]#exit node(cfg)#terminal Telnet use authentication remote-radius node(cfg)#terminal console use authentication local-only node(cfg)#show profile authentication Authentication Profile: default Server-Timeout: 10 Methods: local (Type=local) none (Type=none) Aut
SmartWare Software Configuration Guide 8 • RADIUS Client Configuration Transactions between the RADIUS client and server are authenticated through the use of a shared secret, which is never sent over the network—the same secret must thus be known to the server and the client by configuration. Using this secret as an encryption key, user passwords are sent encrypted between the client and RADIUS server.
SmartWare Software Configuration Guide 8 • RADIUS Client Configuration node(cfg)# Configuring RADIUS accounting The RADIUS accounting functionality can be added to a call-router configuration by inserting an AAA callcontrol service between two call-router elements. Any call that is then routed through the AAA service will cause call detail records (CDRs) to be sent to the radius server.
SmartWare Software Configuration Guide 8 • RADIUS Client Configuration The following procedure guides you through the steps necessary to enable RADIUS accounting in an existing configuration: Mode: Configure Step 1 2 Command Purpose node(cfg)# radius-client Create a new RADIUS client node(radius)[client-name]# Define the RADIUS server to be used. If the UDP port is omitradius-server
SmartWare Software Configuration Guide Step 8 • RADIUS Client Configuration Command Purpose 12 node(svc-aaa)[svc-name]# (Optional) accounting-start-trigger [setup | connect] Define, if accounting shall be started at call-setup or call-connect time. The default is at call-connect time. Note If setup is specified, an interim update will be sent at call-connect time.
SmartWare Software Configuration Guide 8 • RADIUS Client Configuration Attributes in the RADIUS accept message After the user and his credentials are approved by the authentication procedure on the RADIUS server, the SmartNode expects a RADIUS accept message with the following attributes: Attribute number 6 Attribute Type Service-Type 18 Reply-Message 27 Session-Timeout 28 Idle-Timeout Description If the value is set to 'administrative', the user has administrator rights on the SmartNode, otherwis
SmartWare Software Configuration Guide 8 • RADIUS Client Configuration servers are down or the network is not reachable, you can create an emergency user in the local database so that you can still access the SmartNode. Perform the following steps to configure the local accounts.
SmartWare Software Configuration Guide 8 • RADIUS Client Configuration Storing call logs with quality information It is possible to store call logs with quality information in the local aaa data sink. To do so, a service aaa is needed where the calls are routed through. Create a profile aaa with the method local. Then create a service aaa to route the calls through.
Chapter 9 IP context overview Chapter contents Introduction ........................................................................................................................................................115 IP context overview configuration task list...........................................................................................................116 Planning your IP configuration .............................................................................................................
SmartWare Software Configuration Guide 9 • IP context overview Introduction This chapter outlines the SmartWare Internet protocol (IP) context and its related components. You will get the fundamental understanding on how to set up your SmartNode to make use of IP related services. The following sections describe the configuration steps necessary to put together certain IP services and the references to the related chapters that explain the issue in more details.
SmartWare Software Configuration Guide 9 • IP context overview 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 to handle packets for specific services—enhances the possible field of application. Moreover, voice packets are transported via a voice gateway to the CS context for further processing and forwarding to the PSTN.
SmartWare Software Configuration Guide 9 • IP context overview Planning your IP configuration The following subsections provide network connection considerations for several types of physical ports types. Patton recommends that you draw a network overview diagram displaying all neighboring IP nodes and serial connected elements. Do not begin configuring the IP context until you have completed the planning of your IP environment.
SmartWare Software Configuration Guide 9 • IP context overview Configuring NAPT Network address port translation (NAPT), which is an extension to NAT, uses TCP/UDP ports in addition to network addresses (IP addresses) to map multiple private network addresses to a single outside address. NAPT enables small offices to save money by requiring only one official outside IP address to connect several hosts via a SmartNode to the access network.
SmartWare Software Configuration Guide 9 • IP context overview Configuring access control lists Packet filtering helps to control packet movement through the network. Such control can help to limit network traffic and to restrict network use by certain users or devices. An access control list is a sequential collection of permit and deny conditions that apply to packets on a certain interface.
Chapter 10 IP interface configuration Chapter contents Introduction ........................................................................................................................................................121 IP interface configuration task list........................................................................................................................121 Creating an IP interface .......................................................................................................
SmartWare Software Configuration Guide 10 • IP interface configuration Introduction This chapter provides a general overview of IP interfaces and describes the tasks involved in their configuration. 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 advanced features.
SmartWare Software Configuration Guide 10 • IP interface configuration Example: Create IP interfaces The procedure illustrated below assumes that you would like to create an IP interface named lan Use the following commands in administrator configuration mode. node>enable node#configure node(cfg)#context ip router node(ctx-ip)[router]#interface lan node(if-ip)[lan]# Deleting an IP interface Almost every configuration command has a no form. In general, use the no form to disable a feature or function.
SmartWare Software Configuration Guide 10 • IP interface configuration Setting the IP address and netmask Each IP interface needs its explicit IP address and an appropriate net mask to be set.
SmartWare Software Configuration Guide 10 • IP interface configuration ICMP message processing The IP suite offers a number of services that control and manage IP connections. The Internet Control Message Protocol (ICMP) provides many of these services. Routers send ICMP messages to hosts or other routers when a problem is discovered with the Internet header. For detailed information on ICMP, see RFC 792.
SmartWare Software Configuration Guide 10 • IP interface configuration Mode: Interface Step Command 1 node(ctx-ip)[router]#interface name 2 node(if-ip)[name]# icmp router-discovery Purpose Selects the interface name for ICMP message processing configuration Enables to send router advertisement broadcast messages Example: Router advertisement broadcast message The following example shows how to enable sending router advertisement broadcast messages on IP interface lan.
SmartWare Software Configuration Guide 10 • IP interface configuration The following example shows how to define the MTU of the IP interface lan to 1000 and to adjust the MSS in both directions to MTU-40. Use the following commands in IP context configuration mode.
SmartWare Software Configuration Guide 10 • IP interface configuration -----------------------------------------------------------Context: router Name: wan 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 … Displaying dynamic ARP entries The following command can be used to display the dynamically learned ARP entries on an IP interface or on the entire system.
SmartWare Software Configuration Guide 10 • IP interface configuration Mode: Either operator or administrator execution Step 1 Command node#ping
[ ] [timeout ] [packet-size ] [ttl ] [traffic-class ] Purpose Sends ICMP ECHO_REQUEST packets to network hosts at IP address Where the parameters are defined as follows: • [] optional parameter which indicates how many pings are sent • [timeout ] optional parameter whichSmartWare Software Configuration Guide 10 • IP interface configuration mal traffic and the IP router removes all routes pointing to that interface. Now, traffic previously flowing over that interface is routed through the interface with IP routes of a higher metric. However the interface continues to send ICMP echo requests. After a configurable number of ICMP replies the host is reachable again, and the interface will be opened for normal traffic.
SmartWare Software Configuration Guide 10 • IP interface configuration Mode: Either operator or administrator execution Step 1 2 Command node(cfg)# [no] debug arp node(cfg)# show arp Purpose Enables or disables the ARP debug monitor. Summarizes the ARP information for each of the Ethernet ports. Traceroute This procedure describes how to print the route (list of hops) packets take to the network host.
SmartWare Software Configuration Guide 10 • IP interface configuration Example: Display the ARP information. node(cfg)#show arp IP Interface eth0: ----------------------------------------------------------------------------Remote IP Remote MAC State TTL TxReq RxRep Usage ----------------------------------------------------------------------------69.138.216.
Chapter 11 NAT/NAPT configuration Chapter contents Introduction ........................................................................................................................................................133 Dynamic NAPT ...........................................................................................................................................133 Static NAPT ............................................................................................................................
SmartWare Software Configuration Guide 11 • NAT/NAPT configuration Introduction This chapter provides a general overview of Network Address (Port) Translation and describes the tasks involved in its configuration. For further information about the functionality of Network Address Translation (NAT) and Network Address Port Translation (NAPT), consult the RFCs 1631 and 3022. This chapter applies the terminology defined in RFC 2663.
SmartWare Software Configuration Guide 11 • NAT/NAPT configuration Global Network Local Network (Local Interface Address) 192.168.1.1 WAN LAN 131.1.1.1 (Global Interface Address) 131.1.1.10 - 131.1.1.15 (Global NAT Address Pool) Source Address modified 192.168.1.30 - 192.168.1.39 131.1.1.10 - 131.1.1.15 Destination Address modified Figure 17. Dynamic NAPT Static NAPT Dynamic NAPT does not permit hosts on the global network to access hosts on the local network.
SmartWare Software Configuration Guide 11 • NAT/NAPT configuration Dynamic NAT is particularly useful for protocols that do not build on UDP or TCP but directly on IP (e.g. GRE, ESP). See also section “NAPT traversal” on page 135. (Local Interface Address) 192.168.1.1 WAN LAN 131.1.1.1 (Global Interface Address) 131.1.1.20 (Global NAT Address) Source Address modified 192.168.1.40 131.1.1.20 Destination Address modified Figure 19.
SmartWare Software Configuration Guide 11 • NAT/NAPT configuration it should create and which IP addresses/ports it must modify (e.g. for voice connections in addition to signaling connections). It performs this task for the protocol FTP. Other protocols such as H.323 and SIP cannot traverse the SmartWare NAPT.
SmartWare Software Configuration Guide Step Command 11 • NAT/NAPT configuration Purpose 5 node(pf-napt)[name]#static local- Creates a Static NAT entry: local-ip is mapped to (optional) ip global-ip global-ip. (max. 20 entries) 6 node(pf-napt)[name]#static Creates a static NAT entry: traffic of the IP protocol (optional) { ah|esp|gre|ipv6 } local_ip AH, ESP, GRE, or IPv6 respectively directed to the [global_ip]. global_ip is forwarded to the local_ip.
SmartWare Software Configuration Guide 11 • NAT/NAPT configuration Mode: profile napt Step 1 2 Command Purpose [name] (pf-napt)[pf-name]# tcp-port- Define the TCP port range range [name] (pf-napt)[pf-name]# udpDefine the UDP port range port-range Preserving TCP/UDP port numbers in NAPT The NAPT can be configured to preserve the TCP/UDP port number of outbound packets sent from local hosts towards the glob
SmartWare Software Configuration Guide 11 • NAT/NAPT configuration Activate NAT/NAPT To activate a NAT/NAPT component, bind its NAPT profile to an IP interface. This binding identifies the global interface of the respective NAT/NAPT component. All other IP interfaces are local relative to this NAT/ NAPT. Note If both a NAPT profile and an ACL profile are bound to the same IP interface, the ACL (Access Control List) acts on the local side of the NAT/ NAPT component.
SmartWare Software Configuration Guide 11 • NAT/NAPT configuration Example: Display NAT/NAPT configuration information node(pf-napt)[access]#show profile napt access NAPT profile access: -------------------------STATIC NAPT MAPPINGS Protocol Local IP Local Port -------------------------------tcp 192.168.1.20 80 tcp 192.168.1.20 23 STATIC NAT Protocol -------ah Global IP --------------0.0.0.0 131.1.1.3 Global Port ----------80 23 PROTOCOL MAPPINGS Local IP Global IP --------------- --------------192.
Chapter 12 Ethernet port configuration Chapter contents Introduction ........................................................................................................................................................142 Ethernet port configuration task list ....................................................................................................................142 Entering the Ethernet port configuration mode ...................................................................................
SmartWare Software Configuration Guide 12 • Ethernet port configuration Introduction This chapter provides an overview of Ethernet ports and describes the tasks involved in configuring Ethernet ports through the SmartWare. Ethernet port configuration task list To configure Ethernet ports, perform the tasks described in the following sections. Most of the task are required to have an operable Ethernet port, some of the tasks are optional, but might be required for your application.
SmartWare Software Configuration Guide 12 • Ethernet port configuration Example: Configuring medium for an Ethernet port The following example shows how to configure medium auto-sense for the Ethernet port on slot 0 and port 0 of a SmartNode 4524 device. node(cfg)#port ethernet 0 0 node(prt-eth)[0/0]#medium auto Configuring Ethernet encapsulation type for an Ethernet port This procedure describes how to configure the encapsulation type to IP for the Ethernet port on slot and port.
SmartWare Software Configuration Guide 12 • Ethernet port configuration Figure 21 shows the logical binding of the Ethernet port at slot 0 on port 0 to the IP interface lan which is defined in the IP context router. Context IP “router” interface lan interface wan bind command bind command Port Ethernet 00 Port Ethernet 01 Figure 21.
SmartWare Software Configuration Guide 12 • Ethernet port configuration Mode: Configure Step 1 Command Purpose [name] (cfg)# context ip Enter the IP context configuration mode. 2 [name] (ctx-ip)[router]# interface Create the first IP interface. 3 [name] (if-ip)[ ]# ipaddress face 4 [name] (if-ip)[ ]# interface Create the second IP interface.
SmartWare Software Configuration Guide 12 • Ethernet port configuration Mode: Configure Step Command 1 node(config)#port ethernet slot port 2 3 node(prt-eth)[slot/port]#vlan id node(vlan)[id]#encapsulation {ip|pppoe|multi} 4 node(vlan)[id]#bind interface name [router] 5 node(vlan)[id]#map cos layer-2-CoS-value to traffic-class-name 6 7 node(vlan)[id]#no shutdown node(vlan)[id]#exit node(prt-eth)[slot/port]# no shutdown Purpose Enter Ethernet port configuration. Create new VLAN port.
SmartWare Software Configuration Guide 12 • Ethernet port configuration Mode: Configure Step 1 2 Command Purpose node(cfg)#port ethernet slot port Enters Ethernet port configuration mode for the interface on slot and port node(prt-eth)[slot/port]#map cos layer 2 class of service value Selects the layer 2 CoS to trafficto traffic class name class mapping. The traffic class name can be freely chosen.
SmartWare Software Configuration Guide 12 • Ethernet port configuration Adding a transmit mapping table entry The transmit mapping table defines the conversion of transmitting firmware-specific service class value into a Layer 2 CoS to service class value. Each conversion is stored as a mapping table entry, so the transmitting mapping table consists of several mapping table entries. This procedure describes how to add a transmit mapping table entry.
SmartWare Software Configuration Guide 12 • Ethernet port configuration Example: Disabling an Ethernet port The following example shows how to disable the Ethernet port on slot 0 and port 0. node(cfg)#port ethernet 0 0 node(prt-eth)[0/0]#shutdown Checking the state of the Ethernet port on slot 0 and port 0 shows that the interface was closed.
SmartWare Software Configuration Guide 12 • Ethernet port configuration The following is an example of how the sniffer is normally used: Step 1 2 3 Command Purpose [name] (cfg)# sniff ethernet 0 1 [wrap] Enable the sniffer on ethernet port 0 1. (Normally the sniffer stops capturing, if the capture buffer is full. However, if the ‘wrap’ option is specified, the sniffer starts discarding the oldest packets and retains the newest ones, if the capture buffer is full.
Chapter 13 Link scheduler configuration Chapter contents Introduction ........................................................................................................................................................152 Applying scheduling at the bottleneck ...........................................................................................................152 Using traffic classes ...................................................................................................................
SmartWare Software Configuration Guide 13 • Link scheduler configuration Introduction This chapter describes how to use and configure the Quality of Service (QoS) features. Refer to chapter 24, “Access control list configuration” on page 253 more information on the use of access control lists.
SmartWare Software Configuration Guide 13 • Link scheduler configuration Local applications (CLI, Web Server) Routing IPSec encryption/ decryption Access control list (ACL) Network address translation (NAT) Voice processing Voice mux/ demux Sequence of processing stages passed by a routed packet Link Scheduler To/from network port (Ethernet, PPPoE, Frame relay, etc.) Figure 22.
SmartWare Software Configuration Guide 13 • Link scheduler configuration service that is only available for a limited bandwidth e.g. low delay. When connecting the SmartNode to a DiffServ network shaping might be a required operation. Burst tolerant shaping or wfq For weighted fair queuing and shaping there is a variation of the scheduler that allows to specify if a traffic class may temporarily receive a higher rate as long as the average stays below the limit.
SmartWare Software Configuration Guide 13 • Link scheduler configuration Mode WFQ priority local voice min. 30% VPN min. 40% Level_1 Web min. 30% Mail Low_Priority Default Mode Shaper Define 2nd level arbiter Define 1st level arbiter Use arbiter on an interface Figure 23. Example of Hierarchical Scheduling Quick references The following sections provide a minimal “standard” link scheduler configuration for the case where voice and data share a (DSL/cable) modem link.
SmartWare Software Configuration Guide 13 • Link scheduler configuration • “rate-limit 512” allows no more than 512 kbit/sec to pass which avoids queueing in the modem. • “header-length 20” specifies how many framing bytes are added by the modem to “pack” the IP packet on the link. The framing is taken into account by the rate limiter. • “atm-modem” tells the rate limiter that the access link is ATM based. This option includes the ATM overhead into the rate limit calculation.
SmartWare Software Configuration Guide 13 • Link scheduler configuration • Enable statistics gathering (see page 168) Packet Classification ACL Profile Predefined Classes Different Types (Classes) of Traffic The service-policy profile defines the arbitration mode and order in which packets of different classes are served. Link Arbiter Service Policy Profile This interface is used as access link and normally represents the bottleneck of the system. IP Interface “wan” Figure 24.
SmartWare Software Configuration Guide 13 • Link scheduler configuration • local-default—All other packets that originate from the SmartNode itself. • default—All traffic that has not otherwise been labeled. Creating an access control list The procedure to create an access control list is described in detail in chapter 24, “Access control list configuration” on page 253. At this point a simple example is given, that shows the necessary steps to tag any outbound traffic from a Web server.
SmartWare Software Configuration Guide 13 • Link scheduler configuration Mode: Configure Step 1 2 3 Command Purpose node(cfg)#profile acl name Creates a new access control list profile named name node(pf-acl)[name]#permit ip host ip-address any traffic-class Creates an IP access conclass-name trol list entry that permits access for host at IP address ip-address, and specifies that packets matched by this rule belong to the traffic-class class-name.
SmartWare Software Configuration Guide 13 • Link scheduler configuration profile service-policy common settings link rate, arbitration common parameters source traffic-class settings for class x bandwidth, packet mark queue-size, etc. source traffic-class settings for class y source traffic-class default settings for all other traffic-classes not listed Figure 26.
SmartWare Software Configuration Guide 13 • Link scheduler configuration The following lines configure the source traffic-classes. When using weighted fair queuing (wfq) each userspecified source traffic-class needs a value specifying its share of the overall bandwidth. For this purpose the share command is used, which defines the relative weights of the source traffic-classes and policies. At a some point the source traffic-class default must be listed.
SmartWare Software Configuration Guide 13 • Link scheduler configuration Mode: Source Command Purpose node(src)[name]#share percentage Defines fair queuing weight (relative to other sources) to percentage for the selected class or policy name Defining the bit-rate The command rate is used with shaper link arbitration to assign the (average) bit-rate to the selected source.
SmartWare Software Configuration Guide 13 • Link scheduler configuration The type-of-service (TOS) byte in an IP header specifies precedence (priority) and type of service (RFC791, RFC1349). The precedence field is defined by the first three bits and supports eight levels of priority. The next four bits—which are set by the set ip tos command—determine the type-of-service (TOS). Table 5. TOS values and their meaning TOS Value SmartWare Value 1000 0100 0010 0001 0000 8 4 2 1 0 Meaning Minimize delay.
SmartWare Software Configuration Guide 13 • Link scheduler configuration “traffic-class” number called. With SmartWare you can inspect the DSCP value in the ACL rules and modify the DSCP value with the link scheduler set ip dscp command. Note When configuring service differentiation on the SmartNode, ensure that codepoint settings are arranged with the service provider. The command set ip dscp sets the DS field applied to packets of the class name.
SmartWare Software Configuration Guide 13 • Link scheduler configuration Defining random early detection The command random-detect is used to request random early detection (RED). When a queue carries lots of TCP transfers that last longer than simple web requests, there is a risk that TCP flow-control might be inefficient. 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.
SmartWare Software Configuration Guide 13 • Link scheduler configuration Mode: profile service-policy/profile Command Purpose [name] (pf-srvp)[]# [no] map packet-size Assigns IP packets of a predefined or speci{routed-voice | routed-voice-encrypted | [ fied range to a traffic-class. To name a spe] } traffic-class cific size, configure lower-range and upperrange with the same value.
SmartWare Software Configuration Guide 13 • Link scheduler configuration Devoting the service policy profile to an interface Any service policy profile needs to be bound to a certain IP interface to get activated. According the terminology of SmartWare a service policy profile is used on a certain IP interface, as shown in figure 27. Service Policy Profile Context IP “router” use command bind command PVC Serial Ethernet Figure 27.
SmartWare Software Configuration Guide 13 • Link scheduler configuration node(ctx-ip)[router]#interface wan node(if-ip)[wan]#use profile service-policy Voice_Prio out 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.
SmartWare Software Configuration Guide 13 • Link scheduler configuration The command has optional values (in the range of 1 to 4) that define the level of detail (see table 7). Table 7.
Chapter 14 Serial port configuration Chapter contents Introduction ........................................................................................................................................................171 Serial port configuration task list .........................................................................................................................171 Disabling an interface .........................................................................................................
SmartWare Software Configuration Guide 14 • Serial port configuration Introduction This chapter provides an overview of the serial port and describes the tasks involved in its configuration includes the following sections: • Serial port configuration task list • Configuration tasks • Examples The V.35 standard is recommended for speeds up to 48 kbps, although in practice it is used successfully at 4 Mbps. The X.
SmartWare Software Configuration Guide 14 • Serial port configuration Example: Disabling an interface The example shows how to disable the built-in serial interface on slot 0 and port 0 of a SmartNode. Check that State is set to CLOSED in the command output of show port serial.
SmartWare Software Configuration Guide Hardware Port : Transmit Edge : Port Type : CRC Type : Max Frame Length: Recv Threshold : Encapsulation : 14 • Serial port configuration V.35 normal DTE CRC-16 2048 1 Configuring the serial encapsulation type The synchronous serial interface supports the Frame Relay and PPP serial encapsulation method.
SmartWare Software Configuration Guide 14 • Serial port configuration Before using the serial interface the hardware port protocol has to be specified. There are two command options available to select the suitable hardware port protocol: • v35 for V.35 protocol to be used • x21 for X.
SmartWare Software Configuration Guide 14 • Serial port configuration Example: Configuring the active clock edge The following example enables to send data on the negative edge on slot 0 and port 0. Check that Transmit Clock is set to inverted in the command output of show port serial.
SmartWare Software Configuration Guide State: OPENED Configuration Hardware Port: Port Type: CRC: Transmit Edge: Max Frame Length: Baudrate: Recv Threshold: X.
Chapter 15 Frame Relay configuration Chapter contents Introduction ........................................................................................................................................................178 Frame Relay configuration task list ......................................................................................................................178 Configuring Frame Relay encapsulation .............................................................................................
SmartWare Software Configuration Guide 15 • Frame Relay configuration Introduction This chapter provides an overview of the Frame Relay protocol and describes the tasks involved in its configuration includes the following sections: • Frame Relay configuration task list • Configuration tasks • Examples Frame Relay is an example of a packet-switched technology. Packet-switched networks enable end stations to dynamically share the network medium and the available bandwidth.
SmartWare Software Configuration Guide 15 • Frame Relay configuration Configuring the LMI type For a Frame Relay network, the line protocol is the periodic exchange of local management interface (LMI) packets between the SmartNode and the Frame Relay provider equipment. If the SmartNode is attached to a public data network (PDN), the LMI type must match the type used on the public network. You can set one of the following three types of LMIs: • ansi for ANSI T1.
SmartWare Software Configuration Guide 15 • Frame Relay configuration Enabling fragmentation FRF.12 interface and end-to-end fragmentation of large IP packets is supported to reduce the delay imposed on voice packets on slow links (less than 512 kbps). As opposed to IP fragmentation, Frame Relay fragmentation is transparent to the IP layer. This leaves IP packets unchanged, which may be important for IP-based applications susceptible to IP fragmentation.
SmartWare Software Configuration Guide 15 • Frame Relay configuration End-to-end FRF.12 fragmentation is recommended for use on permanent virtual circuits (PVCs) that share links with other PVCs transporting voice and on PVCs transporting Voice over IP (VoIP). The fragmentation size depends on the available bandwidth, the chosen codec, and its packet length: • The less bandwidth available per call, the smaller the fragment size has to be configured.
SmartWare Software Configuration Guide 15 • Frame Relay configuration Example: Entering Frame Relay PVC configuration mode The following example enters the configuration mode for PVC with the assigned DLCI of 1 for Frame Relay over the serial interface on slot 0 and port 0.
SmartWare Software Configuration Guide 15 • Frame Relay configuration Frame Relay PVC. If serial Frame Relay PVC shall be used as WAN access, a suitable name for the logical IP interface could be wan as in figure 28 below. IP interface eth0 Context IP “router” IP interface wan IP interface eth1 PVC Port Ethernet 00 Port Ethernet 01 Port Serial 00 Figure 28.
SmartWare Software Configuration Guide 15 • Frame Relay configuration Enabling a Frame Relay PVC After binding Framerelay PVC to an ip interface it must be enabled for packet processing. This procedure activates the PVC by opening the bound ip interface.
SmartWare Software Configuration Guide 15 • Frame Relay configuration node(pvc)[1]#shutdown Check the PVC 1 status by using show running-config and verify that the entry shutdown occurs in the configuration part responsible for this PVC.
SmartWare Software Configuration Guide 15 • Frame Relay configuration 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. This procedure describes how to display the Frame Relay configuration settings for the serial interface. Mode: Port serial Step 1 Command Purpose node(prt-ser)[slot/port]#show framerelay Displays Frame Relay information.
SmartWare Software Configuration Guide 15 • Frame Relay configuration PSTN Internet GW GW Multi Multi Service Service Provider Provider PVC 1 Node Node 2300 X.21 Modem Modem PVC 2 Leased Line Network VPN VPN Provider Provider Figure 29.
SmartWare Software Configuration Guide 15 • Frame Relay configuration Figure 30. 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. 1. Enter the configuration mode. node>enable node#configure … 2. Set up the IP interface configuration first.
SmartWare Software Configuration Guide 15 • Frame Relay configuration 4. Configure the serial interface settings. node(cfg)#port serial 0 0 node(prt-ser)[0/0]#shutdown node(prt-ser)[0/0]#encapsulation framerelay node(prt-ser)[0/0]#hardware-port x21 node(prt-ser)[0/0]#port-type dte … 5. Configure the Frame Relay. You must thus change to the Frame Relay configuration mode. Use the service-policy profile defined above to give voice priority over data.
SmartWare Software Configuration Guide 15 • Frame Relay configuration hdlc encapsulation framerelay framerelay pvc 100 encapsulation rfc1490 bind interface pvc100 router no shutdown port e1t1 0 0 no shutdown Example 2: Frame Relay on e1t1 with a channel-group port e1t1 0 0 port-type e1 clock master framing crc4 encapsulation channelized channel-group myGroup timeslots 13-17 encapsulation hdlc hdlc encapsulation framerelay framerelay lmi-type gof keepalive 20 pvc 100 encapsulation rfc1490 bind interface p
Chapter 16 PRI port configuration Chapter contents Introduction ........................................................................................................................................................192 PRI port configuration task list............................................................................................................................192 Enable/Disable PRI port ............................................................................................................
SmartWare Software Configuration Guide 16 • PRI port configuration Introduction This chapter provides an overview of the PRI (Primary Rate Interface) ports, their characteristics and the tasks involved in the configuration. The SmartNode devices know three different kinds of PRI ports, E1, T1 and E1T1 whereas an E1T1 port can either work as E1 or T1. This chapter describes the superset of all commands are available on the different PRI ports.
SmartWare Software Configuration Guide 16 • PRI port configuration • PRI Debugging Enable/Disable PRI port By default, the PRI port is disabled. The following command is used for enabling or disabling it. Mode: port Step 1 Command [name] (hw-type)[slot/port]# [no] shutdown Purpose Enable/Disable the PRI port. Default: shutdown (which is disabled) Configuring PRI port-type An E1T1 Port can either work in T1 or in E1 (G.704) mode.
SmartWare Software Configuration Guide 16 • PRI port configuration Mode: port Step 1 Command [name] (prt-e1t1)[slot/port]# linecode {ami | b8zs | hdb3} Purpose Configures the line-code of the port. Default for e1: hdb3 Default for t1: b8zs Configuring PRI framing Four framing formats are available for selection on the E1T1 port. Unframed can only be used if the encapsulation is set for hdlc.
SmartWare Software Configuration Guide 16 • PRI port configuration Configuring PRI line-build-out (E1T1 in T1 mode only) The line build out configuration is used in long haul applications to prevent cross talk in the far end device. Mode: port e1t1 Step 1 Command [name] (prt-e1t1)[slot/port]# line-buildout {0 | -7.5 | -15 | -22.5} Purpose Specifies the pulse attenuation in dB on the line interface. Restriction: Only available for e1t1 ports in T1 mode.
SmartWare Software Configuration Guide 16 • PRI port configuration Configuring PRI LOS threshold (E1T1 only) This command takes effect only if the PRI port is configured for long-haul applications. It specifies the sensitivity for Loss Of Signal threshold. A signal suffers more attenuation over long distances than over short distances. Therefore the LOS-Threshold must be set higher for longer transmission distances.
SmartWare Software Configuration Guide 16 • PRI port configuration The command has three other options that allow you to manually switch on/off different loops. All these additional options are applicable in T1 and E1 mode. The ‘line-interface’ loop sends back the whole link bandwidth (2048kBit/s or 1544kBit/s). In ‘payload’ the entire user data bandwidth (1984 kbps or 1536 kbps) is looped back. For some tests it is helpful to loop back the system data.
SmartWare Software Configuration Guide 16 • PRI port configuration Create a Channel-Group If the desired encapsulated channel uses only selected time slots (not the entire PRI), then it is necessary to set up a channel-group. To create a channel-group, set the PRI port’s encapsulation to channelized. (See section “Configuring PRI encapsulation”.) On creating a new channel-group the channel-group configuration mode is immediately entered.
SmartWare Software Configuration Guide 16 • PRI port configuration RBS protocol. Enter the RBS configuration mode for RBS specific configurations (see Chapter 20, “RBS configuration” on page 225). Mode: channel-group group-name Step 1 Command Purpose [name] (ch-grp)[group-name]#[no] encap- Specifies the encapsulation type of the channelsulation {hdlc | q921 | rbs} group.
SmartWare Software Configuration Guide 16 • PRI port configuration Configuring HDLC Encapsulation The hdlc encapsulation command specifies what kinds of upper layer data are contained in the hdlc frames. Two encapsulation types are available, framerelay and ppp. For more details see Chapter 15, “Frame Relay configuration” on page 177 and Chapter 30, “PPP configuration” on page 313. Mode: hdlc Step 1 Command [name] (hdlc)#encapsulation {framerelay | ppp} Purpose Specifies the encapsulation type of hdlc.
SmartWare Software Configuration Guide 16 • PRI port configuration Mode: Operator execution Step 1 Command [name]#[no] debug hw-type [ ( [ | [] ] ) | [ [event] | [error] ] ] Purpose Enables/Disables the PRI event/error monitor for the device a slot or a port. Examples: 1)[no] debug e1t1 Enables/Disables the event and the error monitor for all e1t1 ports of the device. 2)[no] debug e1 event Enables/Disables the event monitor for all e1 ports of the device.
SmartWare Software Configuration Guide 16 • PRI port configuration • Example 4: Frame Relay without a channel-group • Example 5: Frame Relay with a channel-group • Example 6: PPP without a channel-group • Example 7: PPP with a channel-group Example 1: ISDN port e1t1 0 0 port-type t1 clock auto linecode b8zs framing esf encapsulation q921 q921 uni-side auto encapsulation q931 q931 protocol ni2 uni-side net bchan-number-order ascending encapsulation cc-isdn bind interface pri00 switch port e1t1 0 0 no shutd
SmartWare Software Configuration Guide 16 • PRI port configuration protocol eam-wink-start encapsulation cc-rbs bind interface pri00_1_8 switch channel-group group_9_16 timeslots 9-16 encapsulation rbs rbs protocol ground-start exchange encapsulation cc-rbs bind interface pri00_9_16 switch channel-group group_17_24 timeslots 17-24 encapsulation rbs rbs protocol eam-double-wink-start encapsulation cc-rbs bind interface pri00_17_24 switch port e1t1 0 0 no shutdown Example 4: Frame Relay without a channel-g
SmartWare Software Configuration Guide 16 • PRI port configuration Example 5: Framerelay with a channel-group port e1t1 0 0 port-type e1 framing crc4 encapsulation channelized channel-group myGroup timeslots 13-17 encapsulation hdlc hdlc encapsulation framerelay framerelay lmi-type itu pvc 100 encapsulation rfc1490 bind interface pvc100 router no shutdown port e1t1 0 0 no shutdown Example 6: PPP without a channel-group port e1t1 0 0 port-type e1 framing crc4 encapsulation hdlc hdlc encapsulation ppp bind
Chapter 17 BRI port configuration Chapter contents Introduction ........................................................................................................................................................206 BRI port configuration task list............................................................................................................................206 Enable/Disable BRI port ............................................................................................................
SmartWare Software Configuration Guide 17 • BRI port configuration Introduction This chapter provides an overview of the BRI (Basic Rate Interface) ports, their characteristics and the tasks involved in the configuration. A BRI port supports two 64kbit/s B-channels for switched voice or data connections, one 16kbit/s D-channel for signaling and always-on data transfer. This results a usable data bit rate of 144kBit/s.
SmartWare Software Configuration Guide 17 • BRI port configuration Configuring BRI Power-Feed Enables the application of power on the BRI port to provide power to ISDN terminals. This command applies only if the port is clock master (network side). It is only available on products with an internal, configurable ISDN power supply. Mode: port bri Step 1 Command [name] (prt-bri)[slot/port]#[no] powerfeed Purpose Enables/Disables power-feed on the selected port.
SmartWare Software Configuration Guide 17 • BRI port configuration Configuring channel-group timeslots The ‘timeslots’ command configures the timeslot for use in data transmission. On a BRI port, only the BChannels can be selected (0 or 1). Mode: channel-group Step 1 Command [name] (ch-grp)[group-name]#[no] timeslots Purpose Selects the timeslot to be used.
SmartWare Software Configuration Guide 17 • BRI port configuration BRI Debugging For the investigation of possible problems in link establishment, data transmission or synchronization, there exists a debug command with the options ‘event’ and ‘error’. The command has a hierarchical characteristic and can be applied to all ports on the whole device, or to all ports of slot or just to one specific port.
SmartWare Software Configuration Guide 17 • BRI port configuration BRI Configuration Examples • Example 1: ISDN with auto clock/uni-side settings • Example 2: ISDN with manual clock/uni-side settings • Example 3: Multi-Link PPP over two B-Channels Example 1: ISDN with auto clock/uni-side settings port bri 0 4 power-feed encapsulation q921 q921 uni-side auto encapsulation q931 q931 protocol dss1 uni-side net bchan-number-order ascending encapsulation cc-isdn bind interface bri04 switch port bri 0 4 no shut
SmartWare Software Configuration Guide 17 • BRI port configuration Example 3: Multi-Link PPP over two B-Channels context ip router interface wan-bri ipaddress 10.10.10.2 255.255.255.
Chapter 18 ISDN Overview Chapter contents Introduction ........................................................................................................................................................213 ISDN reference points ..................................................................................................................................213 Possible SmartNode port configurations .......................................................................................................
SmartWare Software Configuration Guide 18 • ISDN Overview Introduction This chapter provides an overview of ISDN ports and describes the tasks involved in configuring ISDN ports in SmartWare. ISDN ports are the physical ISDN connections on the SmartNode devices. There are two types of ISDN ports: • The ISDN basic rate interface (BRI), and • The ISDN primary rate interface (PRI).
SmartWare Software Configuration Guide 18 • ISDN Overview 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. The T reference point is on the trunk interface of a PBX. This is the standard 4-wire interface between the PBX and the network termination unit (NTU) also known as NT1 in standard terminology.
SmartWare Software Configuration Guide 18 • ISDN Overview Basic Rate Access Line point-to-point T S TE NT2 Phone PBX U T NT1 Node LT ET IP Network LE Basic Rate Access point-to-multipoint (S-bus) Local Exchange TE TE S/T Node Phones U S/T NT1 LT ET IP Network Primary Rate Access Line TE NT2 Phone PBX Legend: TE Terminal Equipment (Phone) NT1 Network Termination 1 (Modem) NT2 Network Termination 2 (PBX) V T S IP Network Node LE LT ET Node ET Local Exchange Line Termination
SmartWare Software Configuration Guide 18 • ISDN Overview Connector pin-out and short circuits—Some of the SmartNode ISDN BRI ports are configurable to operate as network or terminal ports. The pin-out of the sockets is switched according to IMPORTANT this configuration. Wrong port configurations, wrong cabling or wrong connections to neighboring equipment can lead to short circuits in the BRI line powering.
Chapter 19 ISDN configuration Chapter contents Introduction ........................................................................................................................................................218 ISDN configuration task list................................................................................................................................218 Enter Q.921 configuration mode .........................................................................................................
SmartWare Software Configuration Guide 19 • ISDN configuration Introduction This chapter describes the configuration of the Q.921 and Q.931 protocol and how to bind the ISDN protocol to an application like the Call Control. To get an overview of the ISDN protocol and the layered configuration model of SmartWare, please see Chapter 18, “ISDN Overview” on page 212. In this chapter it is supposed, the lower layer on which ISDN will be setup is correctly configured.
SmartWare Software Configuration Guide 19 • ISDN configuration Mode: q921 Step 1 Command node(q921)[slot/port]#protocol pp or node(q921)[slot/port]#protocol pmp 2 node(q921)[slot/port]#uni-side auto or node(q921)[slot/port]#uni-side net or node(q921)[slot/port]#uni-side user Purpose Specify Q.921 operating mode (Default: BRI: pmp, PRI: pp). The Q.921 protocol running on BRI ports can operate in point-to-point (pp) or point-to-multipoint (pmp) mode.
SmartWare Software Configuration Guide 19 • ISDN configuration command description below refers to the configuration mode in which Q.931 can be enabled by setting the encapsulation to ‘q931’. This configuration mode is called here ‘base-mode’ but it is only an alias for the real mode. Once encapsulation q931 has been configured, the Q.931 configuration mode can be entered. Mode: base-mode Step Command Purpose 1 [name](base-mode)]#[no] encapsulation q931 Enables/Disables Q.
SmartWare Software Configuration Guide Step 2 19 • ISDN configuration Command node(q931)[slot/port]#signalling-rule etsi Purpose Specify channel numbering (Default: etsi) Some older Q-SIG variants make use of a channel numbering scheme that differs from node(q931)[slot/port]#signalling-rule the standard ETSI method. In most cases the pss1old ETSI numbering applies.
SmartWare Software Configuration Guide Step 6 Command 19 • ISDN configuration Purpose node(q931)[slot/port]# bchan-numberorder ascending Specify B-channel allocation strategy (Default: ascending) or The numbering mode defines how the available time slots are filled. The cyclic modes use a “round-robin” implementation. The “up” and “down” modes define whether the time slots are filled at the lowest or highest available slot, i.e.
SmartWare Software Configuration Guide 19 • ISDN configuration Mode: Operator execution Step 1 Command Purpose node#show port isdn [slot port] [detail <- Show the status of one or more ISDN ports. level>] If the optional arguments slot/port are omitted the status of all ISDN ports is displayed. Level could be 1 to 5. Level 1 shows less, level 5 shows all available information. Default level is 3.
SmartWare Software Configuration Guide 19 • ISDN configuration Example: QSIG Assume the scenario as illustrated in figure 35: Node Node ISDN Port 1/0 Figure 35. PBX connected to ISDN port 1/0 Configure the ISDN port 1/0 to work as a Q-SIG master port but clock-slave and allow a maximum of eight parallel B-channel connections. 172.16.40.71(cfg)#port e1 1 0 172.16.40.71(prt-e1)[1/0]#clock slave 172.16.40.71(prt-e1)[1/0]#q921 172.16.40.71(q921)[1/0]#q931 172.16.40.71(q931)[1/0]#uni-side net 172.16.40.
Chapter 20 RBS configuration Chapter contents Introduction ........................................................................................................................................................226 RBS configuration task list ..................................................................................................................................226 Enter RBS configuration mode ..........................................................................................................
SmartWare Software Configuration Guide 20 • RBS configuration Introduction This chapter describes the configuration of the Robbed Bit Signaling (RBS) protocol and how to bind it to the Call Control application. RBS is used on T1 links to provide per-channel circuit signaling information. In this application no common signaling channel is used like in ISDN, each channel (Time Slot) is carrying its signaling information by itself.
SmartWare Software Configuration Guide 20 • RBS configuration • Ground Start: This protocol is commonly used for local loop PBX services. The protocol is asymmetric what means, the exchange and the subscriber side are different. Always an Exchange/Subscriber pair must be connected together. There is a provisioning for ring indication in this protocol. • E&M Wink Start: This protocol is used between exchanges, is symmetric and has NO provisioning for ring indication.
SmartWare Software Configuration Guide 20 • RBS configuration Mode: Operator execution Step 1 Command node#[no] debug cas {event | error} Purpose Enables/Disables CAS event/error monitor Mode: Operator execution Step 1 Command node#[no] debug rbs {event | error} Purpose Enables/Disables RBS event/error monitor RBS Configuration Examples Example: Configuring RBS Ground Start on a E1T1 port port e1t1 0 0 port-type t1 clock slave linecode b8zs framing esf encapsulation rbs rbs protocol ground-start sub
SmartWare Software Configuration Guide 20 • RBS configuration channel-group RBS_GROUP_17_24 timeslots 17-24 encapsulation rbs rbs protocol eam-double-wink-start encapsulation cc-rbs bind interface RBS00_17_24 switch port e1t1 0 0 no shutdown RBS configuration task list 229
Chapter 21 DSL Port Configuration Chapter contents Introduction ........................................................................................................................................................231 Line Setup ...........................................................................................................................................................231 Configuring PPPoE ........................................................................................................
SmartWare Software Configuration Guide 21 • DSL Port Configuration Introduction This chapter provides an overview of the DSL ports (ADSL and G.SHDSL), their characteristics and the tasks involved in the configuration. port dsl 0\ 0\ vpi 8 pvc vci 35 pppoe Profile napt WAN session MyISP use p bind subscriber MySubscriber Subscriber PPP MySubscriber face inter bind router WAN rofile n WAN apt WAN interface context ip Figure 36. Configuring the G.
SmartWare Software Configuration Guide 21 • DSL Port Configuration Next, you will need to create a WAN profile, create a WAN interface, and create a subscriber. Then, you can configure the DSL port (port dsl 0 0) for PPPoE.
SmartWare Software Configuration Guide 21 • DSL Port Configuration Setting up permanent virtual circuits (PVC) The modems currently available are using ATM to multiplex traffic over the DSL framing connection. ATM allows you to have separate logical connections running in parallel. Those connections are called permanent virtual circuits (PVC). All permanent virtual circuits use AAL5 framing. Table 8.
SmartWare Software Configuration Guide 21 • DSL Port Configuration Diagnostics Table 11. Diagnostics commans Command Step 1 node> show dsl type Step 2 node> show dsl line-state Step 3 node> show dsl version Step 4 node# debug dsl-setup Purpose Displays the type of modem installed. Displays information about the state of the DSL link. Display firmware version information for the modem. Lists the configuration interactions between the gateway and the modem module.
Chapter 22 Basic IP routing configuration Chapter contents Introduction ........................................................................................................................................................236 Routing tables ...............................................................................................................................................236 Static routing ...........................................................................................................
SmartWare Software Configuration Guide 22 • Basic IP routing configuration Introduction This chapter provides an overview of IP routing and describes the tasks involved in configuring static IP routing. IP routing moves information across an internetwork from a source to a destination, typically passing through one or more intermediate nodes along the way.
SmartWare Software Configuration Guide 22 • Basic IP routing configuration • Displaying IP route information (see page 238) 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. Once configured, a static route stays in the routing table indefinitely.
SmartWare Software Configuration Guide 22 • Basic IP routing configuration Deleting static IP routes The no form of the route command deletes a static IP route from the routing table.
SmartWare Software Configuration Guide 22 • Basic IP routing configuration Configuring policy routing Step Command Purpose 1 node(cfg)#context ip router 2 node(ctx-ip)[router]#[no] route destination netmask interface|gateway [metric ] [traffic-class ] Enters the IP router context Define a static routing table entry Where the syntax is: • destination—The IP address of the target network or subnet.
SmartWare Software Configuration Guide 22 • Basic IP routing configuration In this routing table two default routes (0.0.0.0/0) are defined. The first default route is valid for packets of the class local-voice only. The second default route is valid for all packets. Thus voice packets generated locally (traffic-class local-voice) will travel via the gateway (Nexthop) 172.16.32.1. All other packets will travel via the gateway (Nexthop) 172.16.32.2.
SmartWare Software Configuration Guide 22 • Basic IP routing configuration The necessary routing-table entries for the scenario described are listed below. node>enable node#configure node(cfg)#context ip router node(ctx-ip)[router]# route 10.1.5.10 255.255.255.255 172.16.40.2 node(ctx-ip)[router]# route 10.2.0.0 255.255.0.0 172.17.100.
Chapter 23 RIP configuration Chapter contents Introduction ........................................................................................................................................................243 Routing protocol .................................................................................................................................................243 RIP configuration task list .......................................................................................................
SmartWare Software Configuration Guide 23 • RIP configuration Introduction This chapter provides an overview of the Routing Information Protocol (RIP) and describes the tasks involved in configuring RIP features includes the following sections: • Routing protocol • RIP configuration task list (see page 244) RIP is a relatively old but still commonly used interior gateway protocol created for use in small, homogeneous networks. It is a classical distance-vector routing protocol.
SmartWare Software Configuration Guide 23 • RIP configuration RIP 2 is more useful in a variety of environments and allows the use of variable subnet masks on your network. It is also necessary for implementation of classless addressing as accomplished with CIDR (classless interdomain routing). It is recommended that RIP 2 be used on any segment where all routers can use the same IP routing protocol.
SmartWare Software Configuration Guide 23 • RIP configuration Example: Enabling send RIP The following example shows how to enable send RIP on IP interface wan. node(cfg)#context ip router node(ctx-ip)[router]#interface wan node(if-ip)[wan]#rip supply Enabling an interface to receive RIP By default an interface does not listen to routing information.
SmartWare Software Configuration Guide 23 • RIP configuration Specifying the receive RIP version By default, RIP version 1 and version 2 packets are received.
SmartWare Software Configuration Guide 23 • RIP configuration The following example shows how to enable RIP learn host and default on IP interface wan.
SmartWare Software Configuration Guide 23 • RIP configuration node(cfg)#context ip router node(ctx-ip)[router]#interface wan node(if-ip)[wan]#rip announce default node(if-ip)[wan]#rip announce host Enabling RIP auto summarization Summarizing routes in RIP Version 2 improves scalability and efficiency in large networks.
SmartWare Software Configuration Guide 23 • RIP configuration Mode: Interface Step 1 Command Purpose node(if-ip)[name]#rip default-route-value value Sets the routing metric to value indicating the distance to the destination on interface name Example: Specifying the default route metric The following example shows how to set the routing metric to 4 on IP interface wan.
SmartWare Software Configuration Guide 23 • RIP configuration Mode: Interface Step 1 Command Purpose node(if-ip)[name]#rip poison-reverse Enables the poison reverse algorithm on interface name Example: Enabling the poison reverse algorithm The following example shows how to enable the poison reverse algorithm on IP interface wan.
SmartWare Software Configuration Guide 23 • RIP configuration Displaying RIP configuration of an IP interface Displaying the RIP configuration of an IP interface is useful to list the settings.
SmartWare Software Configuration Guide 23 • RIP configuration rip enabled RIP configuration task list 252
Chapter 24 Access control list configuration Chapter contents Introduction ........................................................................................................................................................254 About access control lists .....................................................................................................................................254 What access lists do ................................................................................................
SmartWare Software Configuration Guide 24 • Access control list configuration Introduction This chapter provides an overview of IP Access Control Lists and describes the tasks involved in configuring them.
SmartWare Software Configuration Guide 24 • Access control list configuration For example, access lists can allow one host to access a part of your network, and prevent another host from accessing the same area. In figure 38 host A is allowed to access the Human Resources network and host B is prevented from accessing the Human Resources network. Host A Node Node Host B Human Resource Network Research & Development Network Figure 38.
SmartWare Software Configuration Guide 24 • Access control list configuration • All access control lists have an implicit deny ip any any at the end. A packet that does not match the criteria of the first statement is subjected to the criteria of the second statement and so on until the end of the access control list is reached, at which point the packet is dropped.
SmartWare Software Configuration Guide 24 • Access control list configuration Before you begin to enter the commands that create and configure the IP access control list, be sure that you are clear about what you want to achieve with the list. Consider whether it is better to deny specific accesses and permit all others or to permit specific accesses and deny all others.
SmartWare Software Configuration Guide 24 • Access control list configuration Mode: Profile access control list Step 1 Command Purpose node(pf-acl)[name]#deny ip {src src-wildcard | any | host Creates an IP access of control list src} {dest dest-wildcard | any | host dest} [cos group] entry that denies access defined according to the command options Where the syntax is: Keyword Meaning src The source address to be included in the rule. An IP address in dotted-decimal-format, e.g. 64.231.1.10.
SmartWare Software Configuration Guide 24 • Access control list configuration Adding an ICMP filter rule to the current access control list profile The command permit or deny are used to define an ICMP filter rule. Each ICMP filter rule represents an ICMP access of control list entry.
SmartWare Software Configuration Guide 24 • Access control list configuration Where the syntax is as following: Keyword Meaning src 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. An example for a valid wildcard is 0.0.0.
SmartWare Software Configuration Guide 24 • Access control list configuration The same effect can also be obtained by using the simpler message name option. See the following example. node(cfg)#profile acl WanRx node(pf-acl)[WanRX]#deny icmp any any msg echo node(pf-acl)[WanRX]#exit node(cfg)# Adding a TCP, UDP or SCTP filter rule to the current access control list profile The commands permit or deny are used to define a TCP, UDP or SCTP filter rule.
SmartWare Software Configuration Guide 24 • Access control list configuration Where the syntax is: Keyword Meaning src 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. An example for a valid wildcard is 0.0.0.
SmartWare Software Configuration Guide 24 • Access control list configuration Binding and unbinding 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.
SmartWare Software Configuration Guide 24 • Access control list configuration Unbind an access control list profile from an interface. node(cfg)#context ip router node(cfg-ip)[router]#interface wan node(cfg-if)[wan]#no use profile acl in Note When unbinding an access control list profile the name argument is not required, since only one incoming and outgoing access control list can be active at the same time on a certain IP interface.
SmartWare Software Configuration Guide 24 • Access control list configuration Mode: Interface Step Command Purpose 1 2 node(cfg)#context ip router node(ctx-ip)[router]#interface if-name 3 node(if-ip)[if-name]#debug acl {in | out} [level] Selects the IP router context Selects IP interface if-name for which access control list profile shall be debugged Enables access control list debug monitor with a certain debug level for the selected interface if-name Where the syntax is: Keyword if-name level in
SmartWare Software Configuration Guide 24 • Access control list configuration Examples Denying a specific subnet Figure 39 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. To prevent access, 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. 172.16.1.0 172.16.2.0 secure lan Node Node 172.16.1.1/24 172.16.2.
Chapter 25 SNMP configuration Chapter contents Introduction ........................................................................................................................................................268 Simple Network Management Protocol (SNMP) ................................................................................................268 SNMP basic components ..............................................................................................................................
SmartWare Software Configuration Guide 25 • SNMP configuration Introduction This chapter provides overview information about Simple Network Management Protocol (SNMP) and describes the tasks used to configure those of its features supported.
SmartWare Software Configuration Guide 25 • SNMP configuration • Traversal operations are used by the NMS to determine which variables a managed device supports and to sequentially gather information in variable tables, such as a routing table. SNMP management information base (MIB) A Management Information Base (MIB) is a collection of information that is organized hierarchically. MIBs are accessed using a network-management protocol such as SNMP.
SmartWare Software Configuration Guide IMPORTANT 25 • SNMP configuration The SNMP agent running in SmartWare is SNMP version 1 (SNMPv1) compliant. SNMP version 2 (SNMPv2) and SNMP version 3 (SNMPv3) are not currently supported. SNMP tools Patton recommends the AdventNet MibBrowser, TrapViewer and other SNMP tools. Check the AdventNet Web server at http://www.adventnet.com for latest releases.
SmartWare Software Configuration Guide 25 • SNMP configuration Mode: Administrator execution Step 1 2 3 Command Purpose node(cfg)#system contact name Sets the contact persons name node(cfg)#system location location Sets the system location node(cfg)#system hostname hostname Sets the system hostname and command line prompt If any of the command options name, location, or hostname has to be formed out of more than one word, the information is put in “double quotes”.
SmartWare Software Configuration Guide 25 • SNMP configuration Figure 40. AdventNet MibBrowser displaying some of the System Group objects Example: Setting the system group objects In the following example the system information is set for later access via SNMP. See figure 40 for a typical MIB browser application accessing these MIB-II system group objects representing the system information.
SmartWare Software Configuration Guide 25 • SNMP configuration Community strings also provide a weak form of access control in earlier versions of SNMP version 1 and 2. SNMP version 3 provides much improved access control using strong authentication and should be preferred over SNMP version 1 and 2 wherever it is supported. If a community string is defined, then it must be provided in any basic SNMP query if the requested operation is to be permitted by the device.
SmartWare Software Configuration Guide 25 • SNMP configuration 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. Therefore a host needs an entry, which allows accessing the device. The host is identified by its IP address and has to use a certain community string for security precautions.
SmartWare Software Configuration Guide 25 • SNMP configuration In the following example the NMS running on host with IP address 172.16.224.44 shall be defined as SNMP trap target. Since the NMS requires that SNMP message headers have a community of Not4evEryOne the security-name argument is set accordingly. node(cfg)#snmp target 172.16.224.
SmartWare Software Configuration Guide 25 • SNMP configuration The TrapViewer is a graphical tool to view the Traps received from one or more SNMP agents. The Trap viewer can listen to one or more port at a time and the traps can be sent from any host. Moreover the TrapViewer contains a Trap parser editor, which is a tool to create a trap parser file. The Trap viewer parses the file created using Trap parser editor to match each incoming traps with certain criteria.
SmartWare Software Configuration Guide 25 • SNMP configuration Using the TrapViewer TrapViewer is a graphical tool to view the traps received from one or more SNMP agents. The TrapViewer can listen to one or more port at a time and the traps can be sent from any host. Invoke the TrapViewer through the usage of the MibBrowser. To get to know more about the MibBrowser refer to section “Using the MibBrowser” on page 276. Figure 42 is a screen shot of the TrapViewer. Figure 42.
SmartWare Software Configuration Guide 25 • SNMP configuration - Message that by default has the object identifier format (sequence of numeric or textual labels on the SNs along a path from the root to the object) of the trap if any, or it is blank. • The details of the traps can be viewed by clicking the Trap Details button or right click the trap in the trap table and select the option View Trap Details. Figure 43 show the screen of such a trap details window. Figure 43.
SmartWare Software Configuration Guide 25 • SNMP configuration Table 12. Details available in the Trap Details window (Continued) Trap Details Description Entity RemotePort Community Node TimeReceived HelpURL The source IP address from which the Trap was sent is displayed here. This field reveals the port on which the Trap was sent by the originator. The Community string is displayed here. Source This displays the Date and Time when the trap was received.
SmartWare Software Configuration Guide 25 • SNMP configuration linkUp TRAP-TYPE ENTERPRISE snmp VARIABLES { ifIndex } DESCRIPTION "A linkUp trap signifies that the sending protocol entity recognizes that one of the communication links represented in the agent's configuration has come up." ::= 3 Note The linkUp trap is not sent if any of the ISDN ports has come up.
SmartWare Software Configuration Guide 2002-09-06T14:54:39 2002-09-06T14:54:39 2002-09-06T14:56:02 2002-09-10T14:21:20 ... SNMP interface traps : : : : LOGINFO LOGINFO LOGINFO LOGINFO 25 • SNMP configuration : : : : Link Link Link Link up on interface eth00. up on interface eth01.
Chapter 26 SNTP client configuration Chapter contents Introduction ........................................................................................................................................................283 SNTP client configuration task list ......................................................................................................................283 Selecting SNTP time servers .......................................................................................................
SmartWare Software Configuration Guide 26 • SNTP client configuration Introduction This chapter describes how to configure Simple Network Time Protocol (SNTP) client, it includes the following sections: • SNTP client configuration task list • Recommended Public SNTP Time Servers (see page 290) The Simple Network Time Protocol (SNTP) is an adaptation of the Network Time Protocol (NTP) that is used to synchronize computer clocks in the Internet.
SmartWare Software Configuration Guide 26 • SNTP client configuration Selecting SNTP time servers This procedure describes how to select a primary and secondary SNTP time server Mode: Configure Step Command Purpose 1 node(cfg)#sntp-client server primary host 2 node(cfg)#sntp-client server secondary host Enter the SNTP primary server IP address or hostname Enter the SNTP secondary server IP address or hostname Example: Selecting SNTP time servers In the following example an internal SNTP time serve
SmartWare Software Configuration Guide 26 • SNTP client configuration Example: Configuring SNTP client operating mode Configures the SNTP client operating mode to unicast operation node(cfg)#sntp-client operating-mode unicast Configures the SNTP client operating mode to anycast operation node(cfg)#sntp-client operating-mode anycast Configures the SNTP client operating mode to multicast operation node(cfg)#sntp-client operating-mode multicast Defining SNTP local UDP port The communication between an SNT
SmartWare Software Configuration Guide 26 • SNTP client configuration Enabling and disabling the SNTP client The SNTP client is disabled by default and has to be enabled if clock synchronization shall be used. This procedure describes how to enable or disable the SNTP client Mode: Configure Step 1 Command Purpose node(cfg)#[no] sntp-client Enables the SNTP client operation. Using the no command syntax disables this feature.
SmartWare Software Configuration Guide 26 • SNTP client configuration Defining SNTP client constant offset to GMT Setting the offset of the device local time zone from Greenwich Mean Time is required if the local time shall be used for time dependent routing decisions or other reasons. Greenwich Mean Time (GMT) is also known as Zulu Time and Universal Time Coordinated (UTC), refer to http://greenwichmeantime.com/ for more details and information about your time zone and offset to GMT.
SmartWare Software Configuration Guide 26 • SNTP client configuration Mode: Configure Step 1 Command Purpose node(cfg)#sntp-client anycast-address ip- Set the anycast-address to ip-address a designated address {port | port-number} local broadcast or multicast group address to which a request is sent. In addition an explicit SNTP server port-number in the range from 1 to 65535 can be defined or the argument port is selected, which sets the value for port to 123.
SmartWare Software Configuration Guide 26 • SNTP client configuration Example: Disabling the SNTP client root delay compensation node(cfg)#no sntp-client root-delay-compensation 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.
SmartWare Software Configuration Guide 26 • SNTP client configuration Example: Enable the SNTP debug monitor The following example shows how to enable the SNTP debug monitor and some typical debug information. node(cfg)#debug sntp client node(cfg)#14:44:21 SNTP > SNTP message sent with Timestamp: 2001-10-26T14:44:21 14:44:21 SNTP > SNTP message received: -----------------------------------------------Server: 172.16.1.
SmartWare Software Configuration Guide 26 • SNTP client configuration For more information about NIST Internet Time Service (ITS) check their web server at http://www.boulder.nist.gov/timefreq/service/its.htm Additional information on NTP and a list of other NTP servers The site http://ntp.isc.org contains a maintained list of available NTP/SNTP servers.
Chapter 27 DHCP configuration Chapter contents Introduction ........................................................................................................................................................293 DHCP-client configuration tasks.........................................................................................................................294 Enable DHCP-client on an IP interface ......................................................................................................
SmartWare Software Configuration Guide 27 • DHCP configuration Introduction This chapter provides an overview of the Dynamic Host Configuration Control Protocol (DHCP) and describes the tasks involved in their configuration. This chapter includes the following sections: • DHCP-client configuration tasks (see page 294) • DHCP-server configuration tasks (see page 297) The Dynamic Host Configuration Protocol (DHCP) automates the process of configuring new and existing devices on TCP/IP networks.
SmartWare Software Configuration Guide 27 • DHCP configuration DHCP-server and DHCP-client are illustrated in figure 44. LAN Node Node DHCP Server LAN Node Node DHCP Clients WAN DHCP Clients Node Node LAN DHCP Server Figure 44. DHCP-client and DHCP-server DHCP-client configuration tasks To configure the SmartNode as DHCP-client perform the steps mentioned below.
SmartWare Software Configuration Guide 27 • DHCP configuration interface, e.g. the default gateway, DNS server IP addresses, etc. To enable the DHCP-client on an IP interface perform the steps described below. Mode: context IP Step Command 1 node(ctx-ip)[router]#interface name 2 node(if-ip)[name]#ipaddress dhcp 3 node(if-ip)[name]#show dhcp-client Note Purpose Creates an IP interface with name name and enters ‘configure’ configuration mode Enables the DHCP-client on this IP interface.
SmartWare Software Configuration Guide 27 • DHCP configuration Release or renew a DHCP lease manually (advanced) After enabling the DHCP-client, the interface receives a DHCP lease from the DHCP-server. To manually release and/or renew this DHCP lease use the command described below. This procedure describes how to release and renew the DHCP lease Mode: interface Step 1 2 Command node(if-ip)[name]#dhcp-client release node(if-ip)[name]#dhcp-client renew Note Purpose Releases DHCP lease.
SmartWare Software Configuration Guide 2001-01-01T01:17:47 : LOGINFO 172.16.224.102 01:17:47 DHCPC > router/eth0 01:17:47 DHCPC > router/eth0 01:17:47 DHCPC > router/eth0 01:17:47 DHCPC > router/eth0 01:17:47 DHCPC > router/eth0 2001-01-01T01:17:48 : LOGINFO 2001-01-01T01:17:48 : LOGINFO 27 • DHCP configuration : router/eth0 (Rqst): Got DHCP lease for (Rqst): DHCP ACK received. (Rqst): Lease is valid for 28800 seconds (Rqst): (t1: 14400, t2: 25200) (Rqst): Got DHCP lease for 172.16.224.
SmartWare Software Configuration Guide 27 • DHCP configuration Mode: Configure Step 1 2 Command Purpose node(cfg)#profile dhcp-server name node(pf-dhcps)[name]#network ipaddress ip-mask Enter DHCP-server profile mode Defines the IP address range for which this profile is responsible IP address: basic DHCP information (‘your (client) IP address’) 3 node(pf-dhcps)[name]#[no] include ipaddress-from ip-address-to IP mask: DHCP Option 1 Defines up to 4 contiguous IP address ranges the server may use in
SmartWare Software Configuration Guide Step Command 27 • DHCP configuration Purpose 10 node(pf-dhcps)[name]#[no] bootfile boot- Defines the bootfile the client shall use when (optional) file-name starting. Usually this is used in conjunction with the next-server command. 11 node(pf-dhcps)[name]#[no] next-server (optional) next-server-ip-address Basic DHCP information (‘Boot file name’) Defines the address of the next server in the boot process.
SmartWare Software Configuration Guide 27 • DHCP configuration Define the bootfile (Option 67) for the DHCP-server The DHCP server can define bootfile (DHCP option 67). In contrast to the existing options bootfile and next-server, these options do not use BOOTP fields but DHCP options. Mode: profile dhcp-server Step 1 Command [name](pf-dhcps)[profile]#[no] bootfileopt67 Purpose Defines bootfile (option 67).
SmartWare Software Configuration Guide 27 • DHCP configuration Get debug output from the DHCP-server This procedure describes how to enable/disable the DHCP-server debug monitor Mode: Any Step 1 Command Purpose node(cfg) #[no] debug dhcp-server Enables/disables the debug monitor of the DHCP-server Example: Enable DHCP debug monitor This example shows how to enable the DHCP-server debug monitor.
SmartWare Software Configuration Guide 27 • DHCP configuration Configure DHCP-relay SmartNodes support the DHCP-Relay functionality. To avoid having a DHCP-Server in every subnet, SmartNodes now can forward DHCP-Requests either directly to a DHCP-Server or to another DHCP-Relay. To configure the relay, there is a profile type dhcp-relay. The minimum configuration of such a profile only needs one IP where DHCP-Requests are sent to.
SmartWare Software Configuration Guide 27 • DHCP configuration Enable/Disable DHCP-Relay Agent Mode: Context IP Step 1 Command Purpose [name] (ctx-ip)[name]# dhcp-relay Enable or disable DHCP-Relay. DHCP-Relay cannot be use enabled if a DHCP-Server is running.
Chapter 28 DNS configuration Chapter contents Introduction ........................................................................................................................................................305 DNS configuration task list .................................................................................................................................305 Enabling the DNS resolver ..............................................................................................................
SmartWare Software Configuration Guide 28 • DNS configuration Introduction The domain name system (DNS) enables users to contact a remote host by using easily remembered text labels (www.patton.com, for example) instead of having to use the host’s numeric address (209.45.110.15, for example).
SmartWare Software Configuration Guide 28 • DNS configuration You can test the DNS server configuration using the dns-lookup command as follows: Example: Testing DNS server configuration node(cfg)#dns-lookup www.patton.com Name: www.patton.com Address: 209.49.110.5 Note The DNS resolver automatically learns domain name servers if it receives them through PPP or DHCP protocols.
SmartWare Software Configuration Guide 28 • DNS configuration address. DNS Relay agents maintain a cache of host names and IP addresses, much smaller than a DNS Server.
Chapter 29 DynDNS configuration Chapter contents Introduction ........................................................................................................................................................309 DynDNS configuration task list ..........................................................................................................................309 Creating a DynDNS account ...............................................................................................................
SmartWare Software Configuration Guide 29 • DynDNS configuration Introduction SmartNodes are often used in applications where the addresses of their IP interfaces are not assigned statically (i.e. permanently) but instead are configured dynamically. In these applications, the IP address is assigned dynamically using protocols like DHCP or PPP.
SmartWare Software Configuration Guide 29 • DynDNS configuration Configuring basic DynDNS settings The following procedure describes the steps necessary to enable the DynDNS feature.
SmartWare Software Configuration Guide 29 • DynDNS configuration Configuring advanced DynDNS settings (optional) Defining a mail exchanger for your hostname If required, you can define a mail exchanger or a backup mail exchanger for your hostname on the DynDNS server. Mode: DynDNS Step 1 Command node(dyndns)# mail-exchanger hostname [backup-mx] Purpose Defines the host, which is the mail exchanger for your hostname.
SmartWare Software Configuration Guide 29 • DynDNS configuration Example: Displaying DynDNS status information The following example shows how to enable the debug monitor and the output of the monitor when the IP address on the DynDNS server can be updated successfully.
Chapter 30 PPP configuration Chapter contents Introduction ........................................................................................................................................................314 PPP configuration task list...................................................................................................................................315 Creating an IP interface for PPP ......................................................................................................
SmartWare Software Configuration Guide 30 • PPP configuration Introduction This chapter describes how to configure the point-to-point protocol over different link layers. The point-to-point protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links as defined by the RFC1661 etc. SmartWare offers PPP over the following link layers: • PPP over Ethernet (PPPoE) • PPP over HDLC Figure 46 shows the elements involved in the configuration of PPP.
SmartWare Software Configuration Guide 30 • PPP configuration its own IP interface. In addition to these PPPoE sessions, pure IP traffic can run concurrently over the same Ethernet port. This is achieved by binding the Ethernet port directly to an IP interface.
SmartWare Software Configuration Guide Step 3 Command node(if-ip)[name]#ipaddress unnumbered 30 • PPP configuration Purpose The PPP remote peer offers an IP address for the IP interface. The IP interface adopts this IP address or node(if-ip)[name]#ipaddress dhcp or node(if-ip)[name]# ipaddress ip-address netmask 4 node(if-ip)[name]# [no] tcp adjust-mss { (optional) rx | tx } { mtu | mss } Once PPP has established an IP connection, the IP interface can use DHCP to acquire an IP address.
SmartWare Software Configuration Guide Step 30 • PPP configuration Command Purpose 5 node(if-ip)[name]#use profile napt name Assigns the NAPT profile name to applied to (optional) this IP interface. See 11, “NAT/NAPT configuration” on page 132 to learn how to create a NAPT profile. Example: Create an IP interface for PPP The following procedure creates an IP interface that can be used for all three types of link layers. The command lines tcp adjust-mss only apply to Ethernet link layers.
SmartWare Software Configuration Guide Step 2 30 • PPP configuration Command Purpose node(subscr)[name]# dial {in|out} Defines the direction of the connection establishment with PPP over ISDN. This information allows to use different subscribers for incoming and outgoing calls.
SmartWare Software Configuration Guide 30 • PPP configuration Trigger forced reconnect of PPP sessions using a timer In some situations, it is useful to disconnect and reconnect a PPP session at a clearly defined time. The following procedure shows how PPP can be configured to reconnect the connection every time a timer expires. A common application for this feature: some ISPs disconnect the PPP session after a fixed period of time, for example, 16 hours.
SmartWare Software Configuration Guide 30 • PPP configuration Mode: Configure Step 1 2 Command Purpose node(cfg) #port ethernet slot port Enters Ethernet port configuration mode for the interface on slot and port node (prt-eth)[slot/port]# encapsulation Defines the payload type(s) to be used on the {ip|pppoe|multi} Ethernet: • ‘ip’: IP traffic only (not used for PPP) • ‘pppoe’: PPPoE sessions only • ‘multi’: both IP traffic and PPPoE sessions 3 4 5 6 7 node (prt-eth)[slot/port]# [no] bind inter- Bi
SmartWare Software Configuration Guide 30 • PPP configuration Example: Configure a PPPoE session The procedure below configures a PPPoE session for the connection to a DSL provider using the credentials specified in the subscriber profile above.
SmartWare Software Configuration Guide 30 • PPP configuration Mode: Configure Step 1 Command node(cfg) #[no] profile ppp { name | default } 2 node(pf-ppp)[name]#mtu min min max (optional) max Purpose Creates the new PPP profile name and enters the PPP profile configuration. The profile ‘default’ already exists. Defines the minimum and maximum size of IP packets (in Bytes) allowed on the outbound PPP connection. Outbound packets larger than the maximum size are fragmented into smaller ones if allowed.
SmartWare Software Configuration Guide 30 • PPP configuration Configuring the local and remote PPP MRRU The PPP Maximum Receive Reconstructed Unit (MRRU) denotes the maximum reassembled MRU we are able to receive above the multi-link PPP protocol, i.e. this is the MRU after reassembling frames from individual links inside a multi-link bundle. The valid range and default value of MRRU can be configured in the PPP profile.
SmartWare Software Configuration Guide 30 • PPP configuration Displaying PPP configuration information This section shows how to display and verify the PPP configuration information. Mode: Configure Step 1 Command Purpose node(cfg) #show running-config Gives the best overview of all PPP related configuration information.
SmartWare Software Configuration Guide 30 • PPP configuration Example: Display a PPP profile node(pf-ppp)[PPPoE]#show profile ppp PPPoE Profiles: --------Name: default 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 - 1920 MRU: 68 - 1920 Callback: both CHAP: allowed PAP: allowed Authentication: interval 3000 ms, max 3 IPCP Configure-Request: interval 3000 ms, max 10 IPCP Configure-Nak
SmartWare Software Configuration Guide 30 • PPP configuration Mode: Configure Step 1 2 Command node(cfg) #show ppp links [ level ] node(cfg) #show ppp networks [ level ] Purpose Displays status and configuration information of the Link Control Protocol (LCP) and the authentication protocol(s) (PAP and/or CHAP). Check whether the states of the two protocols are ‘Opened’. level specifies to level of details displayed (1..4, default is 1).
SmartWare Software Configuration Guide 30 • PPP configuration Example: Display PPP link information node(cfg)#show ppp links 4 PPP Link Information: ===================== Link: ID: 0 Name: ethernet 0 0 Protocols: LCP, PAP LCP: ID: 0 Name: ethernet 0 0 State: Opened Conf-Req send rate: 3000ms Max. Conf-Req: 10 Term-Req send rate: 3000ms Max. Term-Req: 2 Echo-Req send rate: 10000ms Max.
SmartWare Software Configuration Guide 30 • PPP configuration Example: Display PPP network protocol information node(session)[green]#show ppp networks 4 PPP Network Information: ======================== Network: ID: 0 Name: ethernet 0 0 0/pppoe/ppp_green/net State: up IPCP: ID: 0 Name: ethernet 0 0 0/pppoe/ppp_green/net State: Opened Conf-Req send rate: 3000ms Max. unanswered Conf-Req: 10 Local configured options: IP Address = 172.16.40.
SmartWare Software Configuration Guide Service: Access-Concentrator: State: Sent Initiations: Sent Requests: Peer Session-ID: Peer MAC-Address: 30 • PPP configuration Opened 1 1 3786 00:01:02:B8:4E:E4 Sample configurations PPP over Ethernet (PPPoE) Without authentication, encapsulation multi, with NAPT profile napt WAN context ip router interface normal_ip_interface ipaddress 172.16.1.1 255.255.0.
SmartWare Software Configuration Guide 30 • PPP configuration identification outbound password bind interface ppp_interface router port ethernet 0 0 encapsulation pppoe no shutdown pppoe session green bind subscriber joe_example no shutdown PPP over a HDLC Link (Serial Port) Without authentication, numbered interface context ip router interface ppp_interface ipaddress 172.17.1.1 255.255.255.
SmartWare Software Configuration Guide 30 • PPP configuration port e1t1 0 0 port-type e1 framing crc4 encapsulation hdlc hdlc encapsulation ppp bind interface myPPP router port e1t1 0 0 no shutdown PPP Dial-up over ISDN The following modules in this section must be configured in order to use the PPP dial-up over ISDN feature: • PPP Dialer (see page 331) • Dial-up (see page 337) • IP Link Supervision (see page 338) PPP Dialer The PPP Dialer is one of the modules you have to configure in order to use the P
SmartWare Software Configuration Guide 30 • PPP configuration • Retry List: A list of up to 8 retry timeouts that define if and when a retry is started for the same destination after a failed dial attempt. • Binding: By binding a dialer destination to a PPP subscriber configuration entity, you define the PPP protocol parameters (e.g. multi-link) and credentials that are applied to the dial-up connection.
SmartWare Software Configuration Guide Step 30 • PPP configuration Command Purpose 5 [name] (outbound)[provider]#[no] retry [ [timeout3>...]] 6 [name] (outbound)[provider]#encapsulation ppp 7 [name] (outbound)[provider]#bind subscriber Specifies how many times and after which timeouts the dialer shall redial the same provider if the previous dial-attempt failed. Up to 8 retry timeouts can be specified. The specified timeouts are relative to the previous try.
SmartWare Software Configuration Guide 30 • PPP configuration • If an additional link (when using multi-link PPP) was up and is accidentally disconnected, we retry to establish it after 5 seconds. • If an additional link (when using multi-link PPP) could not be established because of call-signaling problems (e.g. no ISDN CONNECT received), the dialer retries the same destination again after 10 seconds. • If an additional link (when using multi-link PPP) could be established (e.g.
SmartWare Software Configuration Guide 30 • PPP configuration The local and remote E.164 number configuration on inbound destinations have different meanings than for outbound destinations. On inbound destinations these numbers are used to dispatch incoming calls to one of the configured inbound destinations. Follow the steps below to create an inbound destination instance. Each destination contains all information needed to accept an incoming call and identify towards the remote party.
SmartWare Software Configuration Guide 30 • PPP configuration Debug dialer functionality The following commands show how to display information and events of a PPP dialer. Mode: enable Step 1 Command Purpose [name] #show call-control provider detail Shows configuration and state information about a certain dialer instance. Mode: enable Step Command Purpose 1 [name] #debug dialer detail 2 [name] #debug ppp Enables logging of dialer events and state changes.
SmartWare Software Configuration Guide 30 • PPP configuration interface dialer IF_DIALUP outbound 1 PROVIDER1 local-e164 100 remote-e164 0312345678 route call dest-interface BRI0 retry 5 10 10 encapsulation ppp bind subscriber SUB_PROVIDER1 use profile ppp default outbound 2 PROVIDER2 local-e164 100 remote-e164 0998887766 route call dest-interface BRI0 retry 5 encapsulation ppp bind subscriber SUB_PROVIDER2 use profile ppp default Dial-up Dial-up is one of the modules you have to configure in order to us
SmartWare Software Configuration Guide 30 • PPP configuration Dial-up on monitor Dial when a monitored interface is reported down and drop when that interface is reported up again. A delay time prevents to dial or drop if the monitored interface changes the state only for a short time.
Chapter 31 CS context overview Chapter contents Introduction ........................................................................................................................................................340 CS context configuration task list ........................................................................................................................341 Planning the CS configuration ..........................................................................................................
SmartWare Software Configuration Guide 31 • CS context overview Introduction This chapter gives an overview of the circuit-switching (CS) context and associated components, and describes the tasks involved in its configuration. It describes the steps needed configure voice connectivity, and refers to other chapters where a configuration topic is explained in more detail.
SmartWare Software Configuration Guide 31 • CS context overview The CS context and its associated components route and establish voice calls. For example, the signaling for dial-up circuits is routed and the corresponding voice call circuits are switched between PSTN interfaces and via VoIP interfaces to the VoIP gateways and the IP context (see section “Configuring call routing” on page 345 for more details).
SmartWare Software Configuration Guide 31 • CS context overview Figure 48 shows a typical application with a remote office in an enterprise network. The example focuses on the SmartNode in the remote office. There is an ISDN phone, a personal computer, a connection to the public ISDN network, and a connection to the IP backbone. The VoIP protocol used is H.323 with a codec G.711. A call can be routed to the IP backbone and the public ISDN network depending on its prefix and number length.
SmartWare Software Configuration Guide Note 31 • CS context overview Be careful when choosing where you get your clock source, if the clock used for packaging the ISDN voice frames is not synchronized with the remote ISDN clock, bit errors may result (such synchronization problems would probably cause a fax transmission to fail). • Two BRI ports will be needed, the first port for the ISDN phone and the second for the public ISDN network (see section “Configuring ISDN ports” on page 348).
SmartWare Software Configuration Guide 31 • CS context overview Mode: System Step 1 Command Purpose node(sys)#clock-source hw-type slot port Add an entry to the end of the list node(sys)#clock-source index hw-type slot port Overwrite and entry at position ‘index’ node(sys)#clock-source before index hw-type slot port Insert an entry before position ‘index’ node(sys)#clock-source after index hw-type slot port Insert an entry after position ‘index’ node(sys)#clock-source index up positions Move e
SmartWare Software Configuration Guide 31 • CS context overview Selecting PCM law compression The PCM law-select specifies the voice characteristic compression curve. Two values are possible: a-Law (used in Europe) and µ-Law (used in the USA).
SmartWare Software Configuration Guide 31 • CS context overview SIP GW SIP GW H.323 GW H.323 GW A party B party Context CS switch H.323 Interface ISDN Interface Context IP router Context IP router Context CS switch IP Interface IP Interface Ethernet Port BRI Port H.323 Interface Ethernet Port ISDN Interface ISDN Port IP Network Figure 49. Direct call routing from one SmartNode to another Figure 49 shows a call set up from the A-party on the left to the B-party on the right.
SmartWare Software Configuration Guide 31 • CS context overview Basic interface routing allows you to forward all incoming calls on a CS interface directly to a destination CS interface. The call router allows you to route calls to all available CS interfaces, based on a call property such as calling number, destination number and ISDN bearer capability and many more.
SmartWare Software Configuration Guide 31 • CS context overview Configuring ISDN ports BRI and E1/T1 ports represent physical ports on the SmartNode. The configuration of the ISDN ports depends on the port type (BRI, E1 or T1), and on the connected voice device. To configure the ISDN ports, refer to chapter 34, “ISDN interface configuration” on page 390. Configuring FXS ports FXS ports represents physical ports on the SmartNode.
SmartWare Software Configuration Guide 31 • CS context overview Activating CS context configuration After configuring the CS context and its components, the configuration must be activated. This includes binding the physical ports to the CS interfaces and enabling the gateways, ports, and the CS context. In order to become functional, each interface must be bound from one port from which it receives incoming calls, and to which it forwards outgoing calls.
SmartWare Software Configuration Guide 31 • CS context overview Mode: Context CS Step 1 2 3 4 Command Purpose node(ctx-cs)[switch]#show call-router config detail Show the CS context configuration. level Level could be 1..5. Level 1 shows less, level 5 shows all information. node (ctx-cs)[switch]#debug call-router detail level Enable the call-router debug monitor. Level could be 1..5. Level 1 only logs errors, level 5 shows all relevant information to track calls through routing tables.
SmartWare Software Configuration Guide 02:14:30 CR > Updating 02:14:33 CR > [switch] 02:14:33 CR > [switch] 02:14:33 CR > [switch] 02:14:33 CR > [switch] 02:14:33 CR > [switch] 02:14:33 CR > [switch] 02:14:33 CR > [switch] 02:14:33 CR > [switch] 02:14:33 CR > [switch] 02:14:33 CR > [switch] 02:14:33 CR > [switch] 02:14:33 CR > [switch] 02:14:33 CR > [switch] 02:14:33 CR > [switch] node(ctx-cs)[switch]# 31 • CS context overview tables in 3 seconds...
SmartWare Software Configuration Guide 31 • CS context overview • Calls from office A or B with number 5xx to office C • All other calls from office A or B to the PSTN (local breakout) Gateway H.323 H.323 interface: IF-COMPOFF-A H.323 interface: IF-COMPOFF-B Session Router Context CS switch PSTN interfaces: IF-PBX1 and IF-PBX2 PSTN interfaces IF-PUBLIC-PSTN1 and IF-PUBLIC-PSTN2 PSTN Port ISDN 2/3 Port ISDN 2/2 Port ISDN 2/1 Port ISDN 2/0 PBX Figure 51.
SmartWare Software Configuration Guide 31 • CS context overview • We enable DTMF relay and specify codec G.723. (Refer to section “Configuring voice over IP parameters” on page 347). • We define H.323 direct call signaling. (Refer to section “Configuring an H.323 VoIP connection” on page 348). Configuring general CS settings First we set clock-source to ISDN port 2/3.
SmartWare Software Configuration Guide 31 • CS context overview Finally, we configure the call router. Here we create a routing table that examines the called party number of a call and routes numbers starting with a 1 and containing at least 3 digits to the hunt group that tries to reach company office A over VoIP and falls back to the PSTN. We route numbers starting with 2 and containing at least 3 digits to the hunt group that tries to reach company office B over VoIP and falls back to the PSTN.
SmartWare Software Configuration Guide 31 • CS context overview node(rt-tab)[HUNT-PU~]#cyclic node(rt-tab)[HUNT-PU~]#route call 1 dest-interface IF-PUBLIC-PSTN1 node(rt-tab)[HUNT-PU~]#route call 2 dest-interface IF-PUBLIC-PSTN2 node(rt-tab)[HUNT-PU~]#exit node(ctx-cs)[switch]#exit node(cfg)# Configuring VoIP settings Because we need G.
SmartWare Software Configuration Guide 31 • CS context overview node(q931)[2/2]#uni-side user node(q931)[2/2]#encapsulation cc-isdn node(q931)[2/2]#bind interface IF-PBX1 node(q931)[2/2]#exit node(q921)[2/2]#exit node(prt-bri)[2/2]#no shutdown node(cfg)#port bri 2 1 node(prt-bri)[2/3]#q921 node(q921)[2/3]#q931 node(q921)[2/3]#protocol pp node(q931)[2/3]#uni-side user node(q931)[2/3]#encapsulation cc-isdn node(q931)[2/3]#bind interface IF-PBX1 node(q931)[2/3]#exit node(q921)[2/3]#exit node(prt-bri)[2/3]#no
SmartWare Software Configuration Guide 31 • CS context overview Table switch/IF-COMPOFF-A-precall-service: Key Value Function Dest-Type Dest-Name ------------------------------------------------------------------------------dest-table TAB-CALLED-NUMBER Table switch/IF-COMPOFF-B-precall-service: Key Value Function Dest-Type Dest-Name ------------------------------------------------------------------------------dest-table TAB-CALLED-NUMBER Table switch/TAB-CALLED-NUMBER: Key Value Function Dest-Type Dest-Na
SmartWare Software Configuration Guide 02:30:28 CR > [switch] 02:30:28 CR > [switch] 02:30:28 CR > [switch] 02:30:28 CR > [switch] node(ctx-cs)[switch]# Loading Loading Loading Loading 31 • CS context overview table table table table 'IF-PUBLIC-PSTN2-precall-service' 'IF-COMPOFF-A-precall-service' 'IF-COMPOFF-B-precall-service' 'TAB-CALLED-NUMBER' Showing the running configuration The configuration script for our application looks as follows: cli version 3.
SmartWare Software Configuration Guide 31 • CS context overview interface isdn IF-PUBLIC-PSTN1 route call dest-table TAB-CALLED-NUMBER interface isdn IF-PUBLIC-PSTN2 route call dest-table TAB-CALLED-NUMBER service hunt-group HUNT-COMPOFF-A timeout 5 drop-cause normal-unspecified drop-cause no-circuit-channel-available drop-cause network-out-of-order drop-cause temporary-failure drop-cause switching-equipment-congestion drop-cause access-info-discarded drop-cause circuit-channel-not-available drop-cause re
SmartWare Software Configuration Guide 31 • CS context overview route call 1 dest-interface IF-PUBLIC-PSTN1 route call 2 dest-interface IF-PUBLIC-PSTN2 context cs switch no shutdown gateway h323 h323 faststart bind interface eth0 router no shutdown port ethernet 0 0 medium 10 half encapsulation ip bind interface eth0 router no shutdown port ethernet 0 1 medium 10 half encapsulation ip bind interface eth1 router shutdown port bri 2 0 clock auto encapsulation q921 q921 protocol pp uni-side auto encapsulatio
SmartWare Software Configuration Guide 31 • CS context overview port bri 2 1 no shutdown port bri 2 2 clock auto encapsulation q921 q921 protocol pp uni-side auto encapsulation q931 q931 protocol dss1 uni-side user encapsulation cc-isdn bind interface IF-PUBLIC-PSTN1 port bri 2 2 no shutdown port bri 2 3 clock auto encapsulation q921 q921 protocol pp uni-side auto encapsulation q931 q931 protocol dss1 uni-side user encapsulation cc-isdn bind interface IF-PUBLIC-PSTN2 port bri 2 3 no shutdown Activating C
Chapter 32 VPN configuration Chapter contents Introduction ........................................................................................................................................................363 Authentication ..............................................................................................................................................363 Encryption .............................................................................................................................
SmartWare Software Configuration Guide 32 • VPN configuration Introduction This chapter describes how to configure the VPN connections between two SmartNodes or between a SmartNode and a third-party device. A virtual private network (VPN) is a private data network that uses the public telecommunications infrastructure, maintaining privacy through the use of a tunneling protocol and security procedures. There are different technologies to implement a VPN.
SmartWare Software Configuration Guide 32 • VPN configuration Transport and tunnel modes The mode determines the payload of the ESP packet and hence the application: • Transport mode: Encapsulates only the payload of the original IP packet, but not its header, so the IPsec peers must be at the endpoints of the communications link. • A secure connection between two hosts is the application of the transport mode. • Tunnel mode: Encapsulates the payload and the header of the original IP packet.
SmartWare Software Configuration Guide 32 • VPN configuration VPN configuration task list To configure a VPN connection, perform the following tasks: • Creating an IPsec transformation profile • Creating an IPsec policy profile • Creating/modifying an outgoing ACL profile for IPsec • Configuration of an IP Interface and the IP router for IPsec • Displaying IPsec configuration information • Debugging IPsec Creating an IPsec transformation profile The IPsec transformation profile defines which authenticatio
SmartWare Software Configuration Guide 32 • VPN configuration Procedure: To create an IPsec policy profile Mode: Configure Step 1 2 Command node(cfg)#profile ipsec-policy-manual name node(pf-ipstr)[name]#use profile ipsec-transform name node(pf-ipstr)[name]#session-key 3 optional { inbound | outbound } { ah-aauthentication | espauthentication | esp-encryption } key Purpose Creates the IPsec policy profile name Selects the IPsec transformation profile to be applied Sets a key for encryption or an authe
SmartWare Software Configuration Guide 32 • VPN configuration Use no in front of the above commands to delete a profile or a configuration entry. Example: Create an IPsec policy profile The following example defines a profile for AES-encryption at a key length of 128.
SmartWare Software Configuration Guide 32 • VPN configuration Configuration of an IP interface and the IP router for IPsec The IP interface that provides connectivity to the IPsec peer, must now activate the outgoing ACL profile configured in the previous section. Furthermore, the IP router must have a route for the remote network that points to the respective IP interface.
SmartWare Software Configuration Guide 32 • VPN configuration Example: Display IPsec transformation profiles node(cfg)#show profile ipsec-transform IPSEC transform profiles: Name: AES_128 ESP Encryption: AES-CBC, Key length: 128 Example: Display IPsec policy profiles node(cfg)#show profile ipsec-policy-manual Manually keyed IPsec policy profiles: Name: ToBerne, Peer: 200.200.200.
SmartWare Software Configuration Guide 32 • VPN configuration IN MANUAL 200.200.200.1 3622/unlimited ToBerne - Tunnel no 1111 19047/unlimited - AES-CBC 128 OUT MANUAL 200.200.200.
SmartWare Software Configuration Guide 32 • VPN configuration can optionally also specify a security association lifetime for IKE security associations. If the lifetime of the security association expires, IKE will automatically negotiate a new security association. The default lifetime for ISPEC security associations is one hour without any limit on the transmitted data volume. The parameters defined in this profile are used for the negotiation of IPSEC security associations in quick mode.
SmartWare Software Configuration Guide 32 • VPN configuration Creating an ISAKMP IPSEC policy profile To define all the settings and profiles needed to establish an IPSEC security association, you need to create an ISAKMP IPSEC policy profile There you can specify the ISAKMP and IPSEC transforms you created above, which should be used and other necessary parameters. You can later specify using an ACL, what traffic should be treated by a specify ISAKMP IPSEC policy.
SmartWare Software Configuration Guide Step Command 8 node(pf- ipsik)[]# protected(optional) network {host }|{subnet }|{range } {host }|{subnet }|{range } 9 node(pf- ipsik)[]# protection(optional) group 32 • VPN configuration Purpose Optionally if the remote system requires protected networks to
SmartWare Software Configuration Guide 32 • VPN configuration permit 4 ip any 10.0.0.0 0.255.255.255 ipsec-policy VPN permit 5 ip any any profile ipsec-transform IPSEC_3DES_192 esp-encryption 3des-cbc 192 profile isakmp-transform ISAKMP_3DES_192 encryption 3des-cbc 192 authentication-algorithm sha1 profile ipsec-policy-isakmp VPN authentication-method pre-shared-key sdfkl@hgdslkfs/iuçkfld$gus+ghf mode tunnel peer 1.2.3.
SmartWare Software Configuration Guide 32 • VPN configuration In addition to the monitors there are also show commands, which display current information about IKE and IPSEC. show ike policy • Displays information about the configuration options of specific policy as well as an indication, if the policy is valid or not. A policy might be invalid, if one or more configuration option is missing. show ike status • Displays information about the state of current IKE main and quick modes.
SmartWare Software Configuration Guide 32 • VPN configuration Mode: Context ip /interface Step 1 Command Purpose node(if-ip)[if-name]# [no] rtp-encryp- Enable or disable RTP encryption support on an tion IP interface. Using an alternate source IP address for specific destinations Normally, locally originated IP packets use the IP address of the outbound IP interface as their source address.
SmartWare Software Configuration Guide 32 • VPN configuration Sample configurations The following sample configurations establish IPsec connections between a SmartNode and a Cisco router.
SmartWare Software Configuration Guide 32 • VPN configuration Cisco router configuration crypto ipsec transform-set DES esp-des ! crypto map VPN_DES local-address FastEthernet0/1 crypto map VPN_DES 10 ipsec-manual set peer 200.200.200.2 set session-key inbound esp 2222 cipher FEDCBA0987654321 set session-key outbound esp 1111 cipher 1234567890ABCDEF set transform-set DES match address 110 ! access-list 110 permit ip 172.16.0.0 0.0.255.255 192.168.1.0 0.0.0.255 ! interface FastEthernet0/0 ip address 172.
SmartWare Software Configuration Guide 32 • VPN configuration set session-key inbound esp 6666 cipher FEDCBA0987654321FEDCBA0987654321FEDCBA0987654321FEDCBA0987654321 set session-key outbound esp 5555 cipher 1234567890ABCDEF1234567890ABCDEF1234567890ABCDEF1234567890ABCDEF set session-key inbound ah 4444 FEDCBA0987654321FEDCBA0987654321FEDCBA09 set session-key outbound ah 3333 1234567890ABCDEF1234567890ABCDEF12345678 set transform-set AES_SHA1 match address 110 ! ...
SmartWare Software Configuration Guide 32 • VPN configuration ... For the remainder of the configuration (see above), just change the name of the IPsec policy profile in the ACL profile VPN_Out.
Chapter 33 CS interface configuration Chapter contents Introduction ........................................................................................................................................................382 CS interface configuration task list ......................................................................................................................382 Creating and configuring CS interfaces...........................................................................................
SmartWare Software Configuration Guide 33 • CS interface configuration Introduction This chapter provides an overview of interfaces in the CS context and describes the tasks involved in their configuration. Within the CS context, an interface is a logical entity providing call signaling for incoming and outgoing calls to and from telephony ports and voice over IP gateways. It represents logical connections to other equipment or networks.
SmartWare Software Configuration Guide 33 • CS interface configuration page 529 and chapter 47, “VoIP profile configuration” on page 573. To create and configure CS interfaces you have to perform the configuration tasks listed below.
SmartWare Software Configuration Guide 33 • CS interface configuration The following example shows how to create and configure an interface, how to display it, and how to delete another.
SmartWare Software Configuration Guide 33 • CS interface configuration In the environment of the CS interfaces, it is necessary to specify whether the call will be routed directly to another CS interface (basic interface routing) or to a first lookup table from the call router (advanced call routing). In this chapter. only the configuration task on a CS interface is described.
SmartWare Software Configuration Guide 33 • CS interface configuration to another user agent having a different URI than the called one. This new URI as well as the derived E.164 number cannot be manipulated using the call router before presenting it to the other party. To circumvent this limitation, you can use mapping tables directly on an interface. In that case the mapping tables can be thought as input or output filters, which manipulate call properties at any stage of a call.
SmartWare Software Configuration Guide 33 • CS interface configuration use (input) interface isdn IF-PHONES Incoming Call #1 Calling E.164 20 Called E.164 21 Mapping-Table: PRIV-TO-GLOB input property output property Context E.164 CS switch E.164 (..) 00419988825\1 Incoming Call #1 Calling E.164 0041998882520 Called E.164 0041998882521 Routing-Table: TAB-CALLED-NUMBER Incoming Call #2 Calling E.164 20 Called E.164 0041778881111 Incoming Call #2 Calling E.164 0041998882520 Called E.
SmartWare Software Configuration Guide 33 • CS interface configuration use (input) interface isdn IF-PHONES Incoming Call Calling E.164 20 Called E.164 21 Mapping-Table: PRIV-TO-GLOB input property output property Context E.164CS switch E.164 (..) 00419988825\1 Incoming Call Calling E.164 0041998882520 Called E.164 0041998882521 Routing-Table: TAB-CALLED-NUMBER Outgoing Call Calling E.164 0041998882520 Called E.164 0041998882521 Outgoing Call Calling E.164 20 Called E.
SmartWare Software Configuration Guide 33 • CS interface configuration • interrogate-cw—Detects whether or not the call-waiting supplementary service is active on the interface that uses the precall service table. Note Currently you can only use precall service tables on FXS interfaces.
Chapter 34 ISDN interface configuration Chapter contents Introduction ........................................................................................................................................................391 ISDN interface configuration task list..................................................................................................................391 Configuring DTMF dialing (optional) ..............................................................................................
SmartWare Software Configuration Guide 34 • ISDN interface configuration Introduction This chapter provides an overview of ISDN interfaces, and the tasks involved in their configuration. This chapter does not explain the basic configuration steps equal to all CS interfaces.
SmartWare Software Configuration Guide 34 • ISDN interface configuration Configuring DTMF dialing (optional) Most ISDN terminals support two modes of call setup: En-bloc dialing and overlap dialing. En-bloc dialing transports the full called party information in the first SETUP message from the terminal. This means that the user must dial the number before going off-hook.
SmartWare Software Configuration Guide 34 • ISDN interface configuration Example: Configure an alternate PSTN profile The following example shows how to replace the PSTN profile default of the ISDN interface with the PSTN profile myprofile.
SmartWare Software Configuration Guide 34 • ISDN interface configuration Configuring Call-Hold on ISDN interfaces Normally, the call-hold feature is disabled on ISDN point-to-point links and enabled on ISDN point-to-multipoint links. However, you can manually enable or disable the Call-Hold feature using the following command: The default setting can be achieved using the ‘auto’ configuration option.
SmartWare Software Configuration Guide 34 • ISDN interface configuration Sending the connected party number (COLP) (optional) Sending the connected party number (COLP) can be suppressed by the command send-connected- party-number. Mode: context cs/interface isdn Step 1 Command node(if-isdn)[if-name]#[no] send-connected-party-number Purpose Enables/Disables sending the connected-partynumber. Default: enabled.
SmartWare Software Configuration Guide 34 • ISDN interface configuration Central Office Home Office y tewa Ga vice dia Me ss De IP Vo Acce SIP 0/ 6 0/ 5 0/ 4 0/ 0/ ns Co 0/ 3 0 0/ 1 3 0/ 2 0/ ice Po rts Po IP 0M et Ac tiv ity 10 En 0 w er R un Vo Li nk 1 0 Li nk 1 0/ 0 ity 0/ tiv 0M Ac 10 nk ity Li tiv 0M Ac nk 10 nk Li Li IP et En Vo rts Po w er R un Po Vo et En ice Vo ole 7 18 ToIP e 41 od tN ar Sm 2 (a) ole ns Co 0/ er ut y Ro ce v
SmartWare Software Configuration Guide 34 • ISDN interface configuration The push-back mechanism can be configured on each interface separately. Per default push-back is enabled for ISDN and SIP interfaces. You only have to change the configuration if you don’t want internally looped calls to be pushed back to the network. The configuration command [no] call-transfer accept configures if an incoming call-transfer request (e.g. ECT or REFER) shall be accepted.
SmartWare Software Configuration Guide 34 • ISDN interface configuration The following procedure disables the reception of AOC messages from the network on an ISDN user interface.
SmartWare Software Configuration Guide 34 • ISDN interface configuration there is no AOC information from the network. In that case a message containing the value noChargeAvailable is sent.
SmartWare Software Configuration Guide 34 • ISDN interface configuration The following table shows an overview of the AOC variants: no aoc-x aoc-x transparent aoc-x automatic aoc-x explicit Default option no yes ISDN User Interface (connected to a PBX switch etc.
SmartWare Software Configuration Guide 34 • ISDN interface configuration ISDN DivertingLegInformation2 Facility SmartWare is now able to extract the redirecting information from the DiverstingLegInformation2 Facility and to provide them to the call control. In the other direction, the redirecting information can be sent as DiverstingLegInformation2 Facility in addition to the Redirecting Number Information Element.
SmartWare Software Configuration Guide 34 • ISDN interface configuration • caller-name early-alerting : This configuration command specifies the behaviour for incoming ISDN calls. Some networks only deliver the name after an alerting indication. These networks simulate the mid-ring name delivery feature of analog lines. If early alerting is enabled, we send back a faked ALERTING message after a configurable timeout when we receive a NameInformationFollowing indication.
SmartWare Software Configuration Guide Step 3 Command node(if-isdn)#caller-name ignoreabsence 1000 34 • ISDN interface configuration Purpose (optional) If no name is present in an incoming ISDN call and if the incoming SETUP message contains the NameInformationFollowing indication, we forward the call to the routing destination anyway after 1000ms (500ms after faking the ALERTING message in this example). This step is optional. When not configured, the call is forwarded after 4s by default.
Chapter 35 FXS interface configuration Chapter contents Introduction ........................................................................................................................................................405 FXS interface configuration task list ....................................................................................................................405 Configuring a subscriber number (recommended) ...................................................................................
SmartWare Software Configuration Guide 35 • FXS interface configuration Introduction This chapter provides an overview of FXS interfaces, and the tasks involved in their configuration. This chapter does not explain the basic configuration steps equal to all CS interfaces. Information about basic interface configuration can be found in the general chapter about CS interface configuration (see chapter 33, “CS interface configuration” on page 381).
SmartWare Software Configuration Guide 35 • FXS interface configuration Mode: Interface FXS Step 1 Command [name](if-fxs)[name]#[no] subscribernumber Purpose Applies a subscriber number for the fxs interface. The no form of the command clears an existing one. Default: none Configuring an alternate PSTN profile (optional) The PSTN profile contains the configuration for data/voice transmission on circuit-switched channels (See chapter 48, “PSTN profile configuration” on page 597).
SmartWare Software Configuration Guide 35 • FXS interface configuration Configuring ringing-cadence (optional) The ringing-cadence on FXS Ringing-cadence profiles can be used on FXS interfaces. Each profile consists of a sequence of different rings and ring pauses. Arbitrary ring cadences of up to 10 elements can be configured. The sequence in which the commands are entered (or appear in the config file) defines the sequence in which the corresponding elements are played.
SmartWare Software Configuration Guide 35 • FXS interface configuration Configuring the Message Waiting Indication feature for FXS Note Message Waiting Indication is programmed in two sections of SmartWare, the FXS interface and the SIP Location service. The information below refers to information for configuring the Message Waiting Indication feature for FXS.
SmartWare Software Configuration Guide 35 • FXS interface configuration Frequency-shift keying Frequency-shift keying signaling can be specified in FXS port configuration mode, in one of the following formats: 1. Multiple Data Message Format (MDMF) (etsi standard) (default). 2. Single Data Message Format (SDMF) (bell standard). To enable frequency-shift keying by MDMF standard, use the existing caller-id format command.
SmartWare Software Configuration Guide 35 • FXS interface configuration FXS supplementary services description FXS interfaces offer a set of supplementary services. Some of these services are locally terminated. Others, like conferencing, push the involved subscribers to an external service.
SmartWare Software Configuration Guide 35 • FXS interface configuration The command to change the key patterns is available in the interface fxs configuration mode. If the patterns start with the same key sequence, they should also have the same length. The key parser is of type best matching so it executes the service of the first pattern that represents a full match. Mode: Interface FXS Step 1 Command Purpose [name](if-fxs)[name]#[no] {drop-passive Defines a new key pattern for the selected service.
SmartWare Software Configuration Guide 35 • FXS interface configuration Call waiting reminder ring If a remote subscriber disconnects the call, the local subscriber will hear the release tone and go on-hook. But, if there is still a pending remote subscriber that has been previously set on hold, the phone rings right after onhook. If the local subscriber goes off-hook, the user will be connected again with the previously held remote subscriber. It is possible to navigate to the pending held subscriber.
SmartWare Software Configuration Guide 35 • FXS interface configuration Conferencing When executing a conference, all involved calls will be handed to a given call-router conference service. It is then the responsibility of this service to initiate the conference. Conference services are configured in the Context CS and are protocol specific. The sip-conference service can be used to address a SIP Media Server for conferencing according to RFC4240 (see section, “SIP conference-service” on page 525).
Chapter 36 FXO interface configuration Chapter contents Introduction ........................................................................................................................................................415 FXO services description .....................................................................................................................................416 Creating an FXO interface....................................................................................................
SmartWare Software Configuration Guide 36 • FXO interface configuration Introduction This chapter provides an overview of FXO interfaces and the tasks involved in configuring them. This chapter does not explain the basic configuration steps common to all Context Switch (CS) interfaces. Information about basic interface configuration can be found in chapter 33, “CS interface configuration” on page 381. An FXO, Foreign eXchange Office, interface connects to an FXS, Foreign eXchange Subscriber, interface.
SmartWare Software Configuration Guide 36 • FXO interface configuration FXO services description The wide variety of applications and services are supported through a rich feature set.
SmartWare Software Configuration Guide 36 • FXO interface configuration Once you are in the Context CS mode, you can enter the FXO configuration mode with the next steps. Step 5 6 Prompt & command Purpose node(ctx-cs)[switch]#interface fxo name The “interface fxo” command creates the new interface name, which represents an FXO interface. This command also places you in the FXO interface configuration mode for the created interface.
SmartWare Software Configuration Guide 36 • FXO interface configuration FXO interface configuration task list There are numerous configurable parameters that apply to the FXO interface. The basic commands are listed with a short description of their function. • ring-number on-caller-id—Determines if the FXO interface will go off-hook upon reception of a specified caller-ID.
SmartWare Software Configuration Guide 36 • FXO interface configuration Mode: Interface FXO Step 1 2 3 4 5 Prompt, command & response Purpose node> node>enable node# Basic prompt in Operator Exec mode Enters Administration execution mode Response: The prompt in administration execution mode is the # node#configure Enters the Configure configuration mode node(cfg)# Response: The prompt in the Configure configuration mode is (cfg)# node(cfg)#context cs Enters the Context CS configure mode node(ctx-cs
SmartWare Software Configuration Guide 36 • FXO interface configuration Mode: Interface FXO Step 1 2 3 4 5 6 Prompt, command & response Purpose node> Basic prompt in Operator Exec mode node>enable Enters Administration execution mode node# Response: The prompt in administration execution mode is the # node#configure Enters the Configure configuration mode node(cfg)# Response: The prompt in the Configure configuration mode is (cfg)# node(cfg)#context cs Enters the Context CS configure mode node(ctx
SmartWare Software Configuration Guide Note 36 • FXO interface configuration Verify that you have configured the dial-tone for the country in which the SmartNode is installed. (see chapter 42, “Tone configuration” on page 529). If the dial-tone is not configured for the proper country, the FXO interface will not detect when the remote FXS switch is sending dial-tone.
SmartWare Software Configuration Guide 36 • FXO interface configuration Configuring how to detect a call has disconnected (optional) When a call has disconnected, the FXO interface may detect and verify the termination of the phone call by three different methods.
SmartWare Software Configuration Guide Note 36 • FXO interface configuration Use the battery-reversal disconnect signal with caution, and use only if the battery-reversal connect signal is also enabled.
SmartWare Software Configuration Guide 36 • FXO interface configuration Configuring the destination of the call The last command in configuring the FXO Interface is the route command. This command configures the call router. You can configure the routing-destination for call setup and for service activation. For complete details, see chapter 40, “Call router configuration” on page 456.
SmartWare Software Configuration Guide 36 • FXO interface configuration FXO interface examples Example 1: Configuring an FXO interface which is to be connected to a PSTN network for analog line extension over IP. The FXS switch provides caller-id between the first and second ring and uses battery reversal to indicate a connected call. The FXO interface is named pstn-local. The incoming call is routed directly to the interface named pstn-1-voip.
Chapter 37 RBS interface configuration Chapter contents Introduction ........................................................................................................................................................427 RBS interface configuration task list ....................................................................................................................427 Creating/Deleting a RBS interface ...............................................................................................
SmartWare Software Configuration Guide 37 • RBS interface configuration Introduction This chapter provides an overview of RBS interfaces, and the tasks involved in their configuration. This chapter does not explain the basic configuration steps equal to all CS interfaces. Information about basic interface configuration can be found in the general chapter about CS interface configuration (see Chapter 33, “CS interface configuration” on page 381).
SmartWare Software Configuration Guide 37 • RBS interface configuration Mode: Interface RBS Step 1 Command Purpose node(if-rbs)[if-name]#use profile pstn pro- Defines an alternate PSTN profile to be used for file-name this RBS interface/Reverts the setting to its default (use profile PSTN default) Configuring an alternate Tone-Set profile The Tone-Set profile contains the mapping of the different Call Progress Tones like Dial-Tone, Ringback-Tone or Release-Tone to programmed tone sequences.
SmartWare Software Configuration Guide 37 • RBS interface configuration Mode: Interface RBS Step 1 Command Purpose node(if-rbs)[if-name]#[no] disconnect-sig- Enables/Disables the busy/release-tone as addinal {busy-tone} tional disconnect signal. Default: Enabled Configuring number of Rings before Off-Hook The Loop Start and the Ground Start protocol on the subscriber side identifying an incoming call by detecting the Ring-Signal sent by the exchange side.
SmartWare Software Configuration Guide 37 • RBS interface configuration Mode: Operator execution Step 1 Command Purpose node#show ccrbs call if-name [detail level] Prints information about ongoing calls on the selected interface. node#show ccrbs interface if-name [detail Prints information about the configuration of the level] selected interface and about the states of the belonging protocol endpoints.
Chapter 38 H.323 interface configuration Chapter contents Introduction ........................................................................................................................................................432 H.323 interface configuration task list .................................................................................................................432 Binding the interface to an H.323 gateway ......................................................................................
SmartWare Software Configuration Guide 38 • H.323 interface configuration Introduction This chapter provides an overview of H.323 interfaces used by H.323 gateways and describes the specific tasks involved in their configuration. This chapter does not explain the basic configuration steps required for all CS interfaces. Information about basic interface configuration can be found in the general chapter about CS interface configuration. Within the CS context of SmartWare, an H.
SmartWare Software Configuration Guide 38 • H.323 interface configuration • Configuring information transfer capability handling (optional) • Configuring CLIP/CLIR support (optional) • Enabling the early-proceeding feature for call setup • Enabling the early call disconnect (optional) • Enabling the via address support (optional) • Overriding the default destination call-signaling port (optional) • Configuring status inquiry settings (optional) Binding the interface to an H.323 gateway Every H.
SmartWare Software Configuration Guide 38 • H.323 interface configuration The following example shows how to associate an H.323 interface named MyH323If with a remote H.323 entity, which has the IP address 1.2.3.4 node>enable node#configure node(cfg)#context cs node(ctx-cs)[switch]#interface h323 MyH323If node(if-h323)[myh323if]#remoteip 1.2.3.4 Configuring an alternate VoIP profile (optional) Normally, the VoIP profile defined in the H.323 gateway is used for all the calls over that gateway.
SmartWare Software Configuration Guide 38 • H.323 interface configuration Mode: Interface H.323 Step Command Purpose 1 node(if- h323)[if-name]#itc rx {3k1audio | 7k-audio | restricted-digital | unrestricted-digital | speech | video | transparent } Specifies the information transfer capability to be used for calls from the H.323 gateway to another gateway of the system (incoming calls).
SmartWare Software Configuration Guide 38 • H.323 interface configuration Mode: Interface H.323 Step 1 Command Purpose node(if- h323)[if-name]#clip-clir-support Enables CLIP/CLIR support on the H.323 interface Example: Enable CLIP/CLIR support The following example shows how to enable CLIP/CLIR support on the H.323 interface MyH323If. node>enable node#configure node(cfg)#context cs node(ctx-cs)[switch]#interface h323 MyH323If node(if-h323)[MyH323If]#clip-clir-support Enabling ‘early-proceeding’ on H.
SmartWare Software Configuration Guide 38 • H.323 interface configuration Enabling the early call disconnect (optional) Early call disconnect suppresses busy tones (e.g. disturbing a telephone conference) and post-call announcements by sending an H.323 Release message to the remote peer when the connected terminal hangs up (ISDN: when Disconnect message is received; analog line: when busy tone is detected, loop current is interrupted, or battery voltage is reversed).
SmartWare Software Configuration Guide Note 38 • H.323 interface configuration The call-signaling port specified here has no effect, if a gatekeeper is used. In that case the gatekeeper will provide the portnumber to use for establishing the call signaling connection Procedure: To configure an alternate destination TCP call-signaling port Mode: Interface H.
SmartWare Software Configuration Guide 38 • H.323 interface configuration node(cfg)#context cs node(ctx-cs)[switch]#interface h323 MyH323If node(if-h323)[MyH323If]#no status-inquiry Procedure: To change the default status inquiry interval Mode: Interface H.
SmartWare Software Configuration Guide 38 • H.323 interface configuration Mode: context cs/interfce h.323
Chapter 39 SIP interface configuration Chapter contents Introduction ........................................................................................................................................................442 SIP interface configuration task list......................................................................................................................442 Binding the interface to a SIP gateway .........................................................................................
SmartWare Software Configuration Guide 39 • SIP interface configuration Introduction This chapter provides an overview of SIP interfaces used by context SIP gateways and describes the specific tasks involved in their configuration. This chapter does not explain the basic configuration steps required for all CS interfaces. See Chapter 33, “CS interface configuration” on page 381 for information about configuring basic CS interfaces.
SmartWare Software Configuration Guide 39 • SIP interface configuration • Binding the interface to a context SIP gateway (see page 443) • Configure a remote host (see page 443) • Configure a local host (Optional) (see page 444) • Using an alternate VoIP profile (Optional) (see page 444) • Using an alternate SIP profile (Optional) (see page 445) • Using an alternate Tone-Set profile (Optional) (see page 445) • Configuring early call connect /disconnect (Optional) (see page 446) • Configuring address transl
SmartWare Software Configuration Guide 39 • SIP interface configuration Mode: Interface SIP Step 1 Command Purpose [node](if-sip)[if-name]# [no] remote [port] no form of the command removes a configured host name. Default Hostname: none Default Port: 5060 Configuring a local host (Optional) The local host parameter is used to build the host part of the From-Header-URI. Optionally, a port can be entered.
SmartWare Software Configuration Guide 39 • SIP interface configuration Mode: Interface SIP Step 1 Command [node](if-sip)[if-name]#use profile voip profile-name Purpose Defines an alternate VoIP profile to be used for this SIP interface. Default: default Using an alternate SIP profile (Optional) The SIP profile contains a cause and reason mapping from SIP notation to the call control notation and vice versa.
SmartWare Software Configuration Guide 39 • SIP interface configuration Mode: Interface SIP Step 1 Command [node](if-sip)[if-name]#use profile toneset profile-name Purpose Defines an alternate Tone-Set profile to be used for this SIP interface. Default: default Configuring early call connect / disconnect (Optional) Normally, SIP calls are fully connected by sending a 200 OK response to the INVITE request, if the called party answers the call.
SmartWare Software Configuration Guide 39 • SIP interface configuration Mapping SIP headers to call-control properties This functionality specifies rules that describe which SIP header should take place as a specific call-control property like the called-e164 or the calling-e164 number. Mode: Interface SIP Step Command 1 [node](if-sip)[if-name]#[no] addresstranslation incoming-call {property} {header} Purpose Specifies an incoming address translation rule.
SmartWare Software Configuration Guide 39 • SIP interface configuration Mode: Interface SIP Step Command Purpose 1 [node](if-sip)[if-name]# address-translation outgoing-call request-uri targetparam call redir Enables Redirecting Party Number Tunneling ISDN ‡ SIP: Enables transmission of the target and cause parameters in the Request-URI for outgoing SIP calls.
SmartWare Software Configuration Guide 39 • SIP interface configuration It is possible to configure the sip interface to wait for the caller-name, caller-number or both parameters before routing the call. If the caller-address parameters are sent with sip update and the call will be forwarded to a network where these parameters must be present at call setup time (ISDN), this wait-service must be enabled.
SmartWare Software Configuration Guide 39 • SIP interface configuration Transmit Direction. For enabling sending of the Diversion Header, an outgoing address translation expression must be configured on the sip interface. This expression specifies how to create the Diversion URI of the header. As the User Part of the URI, the Calling Redirecting number will always be taken. The user must configure the Host Part that is set per default to none.
SmartWare Software Configuration Guide 39 • SIP interface configuration SIP REFER Transmission (& ISDN Explicit Call Transfer support) Additional call transfer support, a push-back mechanism, is enabled by default for SIP interfaces by sending REFER messages. SmartWare detects calls that are looped internally, i.e. calls that leave the device over the same SIP interface over which they enter the device.
SmartWare Software Configuration Guide 39 • SIP interface configuration Central Office Home Office y tewa Ga vice dia Me ss De IP Vo Acce SIP 0/ 6 0/ 5 0/ 4 0/ 0/ ns Co 0/ 3 0 0/ 1 3 0/ 2 0/ ice Po rts Po IP 0M et Ac tiv ity 10 En 0 w er R un Vo Li nk 1 0 Li nk 1 0/ 0 ity 0/ tiv 0M Ac 10 nk ity Li tiv 0M Ac nk 10 nk Li Li IP et En Vo rts Po w er R un Po Vo et En ice Vo ole 7 18 ToIP e 41 od tN ar Sm 2 (a) ole ns Co 0/ er ut y Ro ce vi
SmartWare Software Configuration Guide 39 • SIP interface configuration The push-back mechanism can be configured on each interface separately. Per default push-back is enabled for ISDN and SIP interfaces. You only have to change the configuration if you don't want internally looped calls to be pushed back to the network. The configuration command [no] call-transfer accept configures if an incoming call-transfer request (e.g. ECT or REFER) shall be accepted.
SmartWare Software Configuration Guide 39 • SIP interface configuration Enabling the session timer (Optional) The gateway implements the SIP session timer feature, which is currently only defined in SIP draft standards. The session timer feature allows a gateway to check periodically during a call, if the remote gateway is still alive and if the call is still connected on the remote gateway. You can enable this feature using the command shown below.
SmartWare Software Configuration Guide 39 • SIP interface configuration Configure the SIP hold method (Optional) There are different ways to set a remote SIP subscriber On Hold. This command specifies which method the SmartNode uses to indicate this call state. In receive direction, all of them will be accepted.
Chapter 40 Call router configuration Chapter contents Introduction ........................................................................................................................................................458 Call router configuration task list.........................................................................................................................460 Map out the goals for the call router ...........................................................................................
SmartWare Software Configuration Guide 40 • Call router configuration Egress Interface .......................................................................................................................................495 Creating call services .....................................................................................................................................497 Creating a hunt group service ..............................................................................................
SmartWare Software Configuration Guide 40 • Call router configuration Introduction This chapter provides an overview of call router tables, mapping tables and call services and describes the tasks involved in configuring the call router in SmartWare.
SmartWare Software Configuration Guide 40 • Call router configuration service is an example for a call service. Figure 62 illustrates direct call and advanced call routing. In this chapter, advanced call routing is explained. For configuring direct call routing refer to chapter 40, “Call router configuration” on page 456.
SmartWare Software Configuration Guide 40 • Call router configuration • Time of day; hour:minute:second • Date; day.month.year The call router allows you to solve practically any call routing and call property manipulation requirement that you may have. The call router is very flexible in allowing the construction of IMPORTANT decision trees based on linked routing tables. However you should take care not to use too many tables and an over-elaborate structure.
SmartWare Software Configuration Guide 40 • Call router configuration The call router is able to accommodate almost every combination of these requirements through a customized configuration. In order to keep this configuration compact we recommend that you first define the routing requirements and restrictions that apply to your installation. Then define the routing and mapping tables and the call services that you need to fulfill these requirements. Finally define the decision tree (i.e.
SmartWare Software Configuration Guide 40 • Call router configuration Mode: Context CS Step 1 Command node(ctx-cs)[switch]# address-completion timeout timeout Purpose Configures the address completion timeout by specifying the timeout in seconds. If not configured, the default address completion timeout is 12 seconds. Example: Configure address completion timeout node[switch]#address-completion timeout 20 Configures the address completion timeout to 20s.
SmartWare Software Configuration Guide 40 • Call router configuration Example: Configure address completion timeout node[switch]#digit-collection timeout 3 node[switch]#digit-collection terminating-char * Configures the digit collection timeout to 3s. The digit-collection timeout can be stopped by the user entering the asterisk (*) character.
SmartWare Software Configuration Guide 40 • Call router configuration Configure call routing tables Routing tables are identified by names that can be any arbitrary string. For ease of identification the table type is typically used as part of the name. Call router tables are created by entering the routing-table command, which also brings you into the routing table configuration mode. There you can add, modify or delete entries of the routing tables.
SmartWare Software Configuration Guide 40 • Call router configuration Table 17. Routing table types (Continued) Type Description calling-e164 Route calls based on the calling party E.164 number. Entries of calling-e164 tables can use wildcards to summarize routes. called-type-of-number Route calls based on the called party number type. ISDN distinguishes different type of numbers. calling-type-of-number Route calls based on the calling party number type. ISDN distinguishes different type of numbers.
SmartWare Software Configuration Guide 40 • Call router configuration Mode: Context CS Step Command Purpose 1 node(ctx-cs)[switch]#routing-table table-type table-name Create a routing table table-name of the specified table-type. This enters the table mode where entries can be added or removed. To enter a previously created table from the context CS mode, you may leave away the table-type.
SmartWare Software Configuration Guide 40 • Call router configuration The following table shows the wildcard characters that are supported: Table 18. Wildcard symbols used as keys in E.164 tables (calling-e164, called-e164) Symbol Description . Indicates a single-digit placeholder. For example, 888 . . . . matches any dialed number beginning with 888, plus at least four additional digits. Note that the key only specifies the prefix. Thus the number may be longer, but also matches.
SmartWare Software Configuration Guide 40 • Call router configuration The next table shows some examples of how these wildcard symbols are applied to the key of a table entry: Table 19. Wildcard symbols used as keys in E.164 tables (calling-e164, called-e164) Expression Description 88825.+ 88825, followed by one or more wildcard digits. This expression implies that the number must contain at least 6 digits starting with 88825; for example, 888251, 8882512 or 888251234567890 88825.
SmartWare Software Configuration Guide 40 • Call router configuration The default value for the interdigit timeout is 5 seconds and can be configured using the digit-collection timeout command in the context CS configuration mode. You may want to override this default timeout for a specific entry. Just place the timeout in seconds after the T-indicator; e.g. T3 to set the inter digit timeout to 3 seconds for that entry.
SmartWare Software Configuration Guide 40 • Call router configuration digits, the address completion timeout elapses and the call is dropped. The digit collection timeout is active when a route is complete but a T-indicator is specified on the selected route, e.g. when the dialed number of 0991 is tried to match the entry 099T. In this case the call router waits for some period of time for the user to enter additional optional digits.
SmartWare Software Configuration Guide 40 • Call router configuration route default dest-interface IF5entry #5 Note The numbers that are normally dialed are longer than the prefixes listed in the table test. For example, if the numbering plan is defined using five digits, a user normally dials a number like 12345 to reach a destination. Anyway the lookup result must be the same for en-bloc and for overlap dialing.
SmartWare Software Configuration Guide Dialed Number Selected Entry 121 #2 191 #1 1111 #4 1111# #4 40 • Call router configuration Description Entry #1 and #2 match the dialed number of 121, but entry #2 matches better. The call is immediately placed to IF2. Only entry #1 matches the dialed number of 191. Thus the call is routed immediately to interface IF1. The lookup procedure is the same as for dialled number 111.
SmartWare Software Configuration Guide 40 • Call router configuration Note When you specified a national or international prefix using the commands national-prefix or international-prefix respectively. in the context CS configuration mode, the calling or called party number is extended with the specified prefix and the type-of-number is set to unknown in the incoming interface. Thus an international number can enter the call-router as unknown number.
SmartWare Software Configuration Guide 40 • Call router configuration The call router can route calls according to the following numbering plans. These values beside default can be used for the key parameter to create a routing table entry: • unknown—Unknown numbering plan. This is the default value for calls that arrive through an interface that does not support the numbering plan property. • isdn-telephony—ISDN/Telephony numbering plan according to CCITT Recommendation E.164/E.163).
SmartWare Software Configuration Guide 40 • Call router configuration You may specify a whole subnet with the key parameter of the routing table entry. The format of the key parameter is ipaddress[/mask-size]; the mask size may be omitted. Note Incoming SIP and H.323 calls use the calling party IP address property to store the IP address of the remote SIP user agent or H.323 terminal, respectively. Other interfaces like ISDN or FXS set the IP address to 0.0.0.0.
SmartWare Software Configuration Guide Note 40 • Call router configuration Incoming ISDN calls set the presentation indicator according to the received ISDN Setup message. Incoming H.323 calls only set the presentation indicator transparently when Octet3a handling is enabled. Other interfaces set the presentation indicator to allowed. The call router can route calls according to the following presentation indicators.
SmartWare Software Configuration Guide 40 • Call router configuration The call router can route calls according to the following screening indicators. These values beside default can be used for the key parameter to create a routing table entry: • user-not-screened—The calling party number is provided by the user but not screened by the network. Thus the calling party possibly send a number that is not owned by the calling party.
SmartWare Software Configuration Guide 40 • Call router configuration The call router can route calls according to the following information transfer capabilities. These values beside default can be used for the key parameter to create a routing table entry: • speech—Voice terminals (Telephones) • unrestricted-digital—Unrestricted digital information (64kBit/s) • restricted-digital—Restricted digital information (64kBit/s) • 3k1-audio—Transparent 3.1kHz audio channel.
SmartWare Software Configuration Guide 40 • Call router configuration • default: Any other unhandled case Mode: context cs Step 1 Command [name] (ctx-cs)[router]# routing-table calling-redir-reason Purpose Creates a redirect reason routing table. Both the redirecting-number and the redirect-reason can also be used in any call-router mapping tables. Time of day routing table The time table is used to route calls based upon the current system time during one day, i.e. an 24hr.
SmartWare Software Configuration Guide 40 • Call router configuration node(rt-tab)[HOLIDAY~]#route default dest-interface IF-VOIP Deleting routing tables To remove individual routing tables you can use the no form of the routing table command. Alternatively you can remove specific entries of a routing table by entering the routing table configuration mode and use the no form of the route command.
SmartWare Software Configuration Guide 40 • Call router configuration Mode: Context CS Step 1 Command Purpose node(ctx-cs)[switch]#no routing-table Delete the routing table table-name. table-name Note: You do not have to enter the type of the table when just deleting it. The type must only be specified when creating a table.
SmartWare Software Configuration Guide 40 • Call router configuration You can create a mapping table that examines and modifies a specific kind of property, e.g. the called party number. In this case you have to specify an input-type of called-e164 and an output-type of called-164. If you want to replace both, the called and the calling party property with the same mapping table, you can create a mapping table with input-type e164 and output-type e164, i.e.
SmartWare Software Configuration Guide 40 • Call router configuration Table 20. Mapping table types (Continued) Type called-name calling-name name called-ip calling-ip ip calling-pi calling-si itc time date day-of-week Description Input-Type Description Output-Type Selects an entry based on the display name of the called party. Selects an entry based on the display name of the calling party.
SmartWare Software Configuration Guide 40 • Call router configuration Let’s examine the mechanism of mapping tables in more detail. Figure 65 shows three mapping tables and a call that is routed through this mapping table. The call contains various call properties that are examined and modified by the mapping tables: Example #1 Incoming Call Calling E.164 200 URI Called E.164 201 URI Example #2 Incoming Call Calling E.164 200 PI restricted Called E.164 201 Example #3 Incoming Call Calling E.
SmartWare Software Configuration Guide 40 • Call router configuration Example #4: This example shows the same input call properties as in example #3. The mapping table is also almost the same, but unlike in the previous example, here we don’t look for a specific number type (e.g. called party number, calling party number), but for any E.164 number property of the call. The output property is also a generic number. In this case the mapping table replaces both, the calling and the called party number.
SmartWare Software Configuration Guide 40 • Call router configuration Detailed Example: You have an internal dial plan that uses three digit numbers starting with a 2 (e.g. 200, 201, etc.). So when an internal subscriber makes a call, its calling party number contains three digits. 1. You want to route calls to the public switched telephone network (PSTN), that is reachable over and ISDN interface. From the PSTN provider you have an assigned number range from 099-8882500 to 0998882599. 2.
SmartWare Software Configuration Guide 40 • Call router configuration The input *50998882525 matches the expression *5(.%) – the prefix *5 followed by any character repeated zero or more times. The first bracket encloses the number after the prefix: *5(.%) == *5(0998882525) -> \1 = 0998882525 The output is built from the first bracket \1. The called party number is set to 0998882525.
SmartWare Software Configuration Guide 40 • Call router configuration The input called party number 0778881111 matches the expression (.%) – any character repeated zero or more times. The first bracket encloses the last whole called party number: (.%) == (0778881111) -> \1 = 0778881111 The output (calling party number) is built from the first bracket \1. The calling party number is set to 0778881111.
SmartWare Software Configuration Guide 40 • Call router configuration node(cfg)#context cs node(ctx-cs)[switch]#mapping-table called-type-of-number to called-type-of-number SET-INT node(rt-tab)[SET-INT]#map default to international Any called party number type matches the default entry. Note that the input-type of the table does not matter when the mapping table contains only the default entry. Anyway an input-type must be specified when creating the mapping table.
SmartWare Software Configuration Guide 40 • Call router configuration Example: Remove entries from a mapping table The running-config shows the following table: mapping-table called-e164 to called-e164 MY-TABLE map 10 to 20 map 11 to 21 map 12 to 22 map 13 to 23 To remove the first two entries from the table enter the following commands: node(cfg)#context cs node(ctx-cs)[switch]#mapping-table MY-TABLE node(map-tab)[MY-TABLE]#no map 10 node(map-tab)[MY-TABLE]#no map 11 The resulting running-config is: ma
SmartWare Software Configuration Guide 40 • Call router configuration Mode: Context CS Step Command node(ctx-cs)[switch]#complexfunction function-name node(func)[function-name]#execute function 1 2 or node(func)[function-name]#execute index function 3 Purpose Create a complex function function-name. Add or inserts an entry to the complex function. function can be another complex function or a mapping table that shall be executed.
SmartWare Software Configuration Guide 40 • Call router configuration To remove the first two entries from the complex function enter the following commands. Pay attention on the index. When removing the first entry, the MAP2 function becomes entry with index 1.
SmartWare Software Configuration Guide 40 • Call router configuration The possible values for the type argument are: • transparent: Transparently passes an address-complete indication (e.g. ISDN Sending Complete Information Element) to the call-control. • set: Always sets the address-complete indication flag towards the call-control even when no such indication is received from the calling party. This configuration can be used to disable overlap-sending on an interface.
SmartWare Software Configuration Guide 40 • Call router configuration The following table shows the different digit-collection timeout configurations and their effect on a T-terminated route when the digit-collection timeout elapses. Important settings are marked bold.
SmartWare Software Configuration Guide 40 • Call router configuration not the egress interface propagates the address-complete indication depends on the interface configuration (see below). The next table shows the different digit-collection terminating-character configurations and their effect on a Tterminated route when the terminating-character is received.
SmartWare Software Configuration Guide 40 • Call router configuration The possible values for the type argument are: • transparent: Transparently passes an address-complete indication to the signaling-protocol (e.g. ISDN by sending a Sending Complete Information Element). • set: Always sends a Sending Complete Information Element with the SETUP message. This configuration can be used to disable overlap-sending on an interface. • clear: Never sends a Sending Complete Information Element.
SmartWare Software Configuration Guide Step Command 3 node(rt-tab)[tab-name]#exit 4 node(cts-cs)[ctx-name]#digit-collection timeout 5 set-addresscomplete-indication 5 node(cts-cs)[ctx-name]#digit-collection terminating-char # setaddress-complete-indication 40 • Call router configuration Purpose Leaves the routing table configuration mode and returns to the context cs configuration mode Configures the digit-collection timeout to 5 seconds and sets the address-complete indication if the timeout elap
SmartWare Software Configuration Guide 40 • Call router configuration interfaces IF-BRI0 up to IF-BRI3. All four ISDN interfaces lead to the same provider. Since the call router does not know the load on the BRIs, it has to be able to try BRI0 and, if BRI0 already serves two calls, use BRI1, and so on.
SmartWare Software Configuration Guide Note 40 • Call router configuration Unlike previous versions of SmartWare, now you can hunt a call over different interface types, not only over ISDN interfaces. You can, e.g. create a hunt group to try to call over a H.323 interface and, if this call fails, do a fallback to an ISDN interface.
SmartWare Software Configuration Guide 40 • Call router configuration The following table lists all drop causes and specifies whether the cause is used for hunting the next destination or dropping the original call. The behavior can be configured for each hunt group individually for each cause using the drop-cause command in the hunt group service mode. Table 21.
SmartWare Software Configuration Guide 40 • Call router configuration Table 21. Hunt group drop causes (Continued) Class Normal Event (Cont.
SmartWare Software Configuration Guide 40 • Call router configuration Table 21. Hunt group drop causes (Continued) Class Normal Event (Cont.
SmartWare Software Configuration Guide 40 • Call router configuration Table 21. Hunt group drop causes (Continued) Class Service or Option Not Available (Cont.
SmartWare Software Configuration Guide 40 • Call router configuration Table 21. Hunt group drop causes (Continued) Class Cause Default Behavior of the Hunt Group Service Invalid Message call-identity-in-use (Cont.
SmartWare Software Configuration Guide 40 • Call router configuration Table 21. Hunt group drop causes (Continued) Class Protocol Error (Cont.) Interworking Cause Default Behavior of the Hunt Group Service Description ie-does-not-exist Drop original call The remote equipment receives a message that includes information elements or call properties that are not recognized. The remote equipment receives a message that includes invalid information in the information element or call property.
SmartWare Software Configuration Guide 40 • Call router configuration Creating a distribution group service A distribution group service distributes a call to multiple destinations interfaces. Figure 67 shows an example scenario where a call from a SIP interface is first processed by several tables. The second table decides that the call must be forwarded to phones that are connected to various FXS interfaces. The distribution now lets ring all the four phones at the same time.
SmartWare Software Configuration Guide 40 • Call router configuration - 4 call destinations - No max. concurrent 4 picks up - 4 call destinations - max. concurrent = 2 - timeout = 5 after 5s after 10s 4 picks up Figure 68.
SmartWare Software Configuration Guide Note 40 • Call router configuration It does not make sense to configure the maximum number of concurrent destinations but no timeout, though the software does not prevent this configuration. Distribution-Group Min-Concurrent setting A new command in the call-control’s distribution-group service lets the user specify how many of the configured call destinations should be tried first: min-concurrent .
SmartWare Software Configuration Guide 40 • Call router configuration Figure 69. ‘Limiter’ service diagram context cs switch interface isdn localexchange route call dest-service mylimiter.inbound interface isdn voicemail interface sip sip bind gateway sip route call dest-service mylimiter.
SmartWare Software Configuration Guide 40 • Call router configuration service hunt-group services priority (prio) routing table route 911 dest-service prio.high route default dest-service prio.low1 high low1 priority: 2 priority: 0 priority: 0 SIP FXO If1 FXO If2 low2 Figure 70. Priority service diagram By default, the service drops any lower priority calls if a higher priority call fails.
SmartWare Software Configuration Guide 40 • Call router configuration CS Bridge service—‘VoIP Leased Line’ The circuit switch (CS) bridge service provides the functional ability to create a leased line between two FXS ports, with the FXS ports on different SmartNodes. The call is point-to-point in an always connected state, also known as nailed up. This Call Control service is called Bridge services.
SmartWare Software Configuration Guide 40 • Call router configuration port (see figure 72). Each of these interfaces is responsible for one of the two independent calls. The listener port terminates the “FXS call” and the dialer port terminates the “RTP call.” Listener Port – This port listens for a call from the FXO device and connects immediately upon detecting loop current. This is the “Listener Connection.
SmartWare Software Configuration Guide 40 • Call router configuration Mode: Context CS Step Command Purpose 1 [name] (ctx-cs)[switch]#[no] service bridge BRIDGE1 2 [name] (svc-bridg)[BRIDGE1]#port Creates a port on the service that can accept or spawn calls DIALER (the max number of ports is currently limited to two) [name] (port)[DIALER]# dial persis- Configures the port to actively dial the called-party “123” to tent 123 dest-interface REMOTE the destination REMOTE.
SmartWare Software Configuration Guide 40 • Call router configuration Caveat: For calls from the IP side, the service only works if the G711.alaw codec is chosen. On the SmartNode 4960 the service is available for all configurable codecs.
SmartWare Software Configuration Guide 40 • Call router configuration Procedure: To show and activate the call router configuration Mode: Context CS Step Command Purpose node(ctx-cs)[switch]#show call-router Show the actual call router configuration. This displays all config routing and mapping tables in the current context CS. When you are inside a routing or mapping table configuration mode, only the current table is displayed.
SmartWare Software Configuration Guide 40 • Call router configuration node(rt-tab)[TEST]#route default dest-interface IF5 node(rt-tab)[TEST]#exit node(ctx-cs)[switch]#no shutdown node(ctx-cs)[switch]#debug call-router detail 5 node(ctx-cs)[switch]#test call-router TEST called-e164 123 Parameters ========== Time: Result: Destination: Timeout: 2004-03-02T16:55:33<-- Time of the lookup route-found-place-call<-- Lookup result IF2<-- Dest. Interface 0<-- Digit-Coll.
SmartWare Software Configuration Guide 40 • Call router configuration Example: Enterprise network with local breakout and IP carrier access Consider the following Enterprise Network. Carrier Apple Site A Carrier Orange Site B TA ISDN PBX PBX Node A IP WAN Node B LAN LAN Node C Carrier Melon Figure 73. Call routing example network Note The SmartNodes in this Network may be owned and operated by the Company or by a Service Provider.
SmartWare Software Configuration Guide 40 • Call router configuration • When calling through carrier Melon the CLI (calling party number) must not use the public number blocks of Site A and B • Carrier Orange is to be used for national calls • Carrier Apple is to be used for calls to mobile The requirements for the call router can be summarized as: 1. Route ISDN data calls to the local breakout. 2. Route inter-site calls to the opposite SmartNode (node A to node B and vice versa). 3.
SmartWare Software Configuration Guide 40 • Call router configuration Figure 74 shows the corresponding CS Context and call router elements in node A: Context interface isdn IF-PBX-A interface isdn IF-LOCAL-BREAKOUT Call Router MAPCACAPPLE MAPCACORANGE SVCFALL BACK TABISDNSERVICE interface h323 IF-NODE-B TABDESTA MAPCACMELON interface sip IF-NODE-C Figure 74. CS context and call router elements We assume that the CS interfaces have already been created and configured.
SmartWare Software Configuration Guide 40 • Call router configuration # # Bearer capability routing table “TAB-ISDN-SERVICE” # routing-table itc TAB-ISDN-SERVICE route unrestricted-digital dest-interface IF-LOCAL-BREAKOUT route default dest-table TAB-DEST-A # # Called party number routing table “TAB-DEST-A” # routing-table called-e164 TAB-DEST-A route 0 dest-interface IF-LOCAL-BREAKOUT MAP-CAC-ORANGE route 00 dest-interface IF-NODE-C MAP-CLI-MELON route 07[4-6] dest-interface IF-LOCAL-BREAKOUT MAP-CAC-APP
SmartWare Software Configuration Guide 40 • Call router configuration node(if-isdn)[IF-LOCA~]#exit node(ctx-cs)[switch]#interface h323 IF-NODE-B node(if-h323)[IF-NODE-B]#route dest-interface IF-PBX-A node(if-h323)[IF-NODE-B]#exit node(ctx-cs)[switch]#interface sip IF-NODE-C node(IF-NODE-C)[IF-NODE-C]#route dest-interface IF-PBX-A node(IF-NODE-C)[IF-NODE-C]#exit The configuration is now complete.
SmartWare Software Configuration Guide 40 • Call router configuration Call reroute The call-reroute commands enable acceptation and emission of rerouting requests. Enable acceptation of rerouting requests on ISDN. If a reroute is accepted, the participant who sends the reroute request is disconnected and the call is established from the SmartNode to the new destination.
SmartWare Software Configuration Guide 40 • Call router configuration Enable push-back – bridge service. Mode: context cs/service bridge Step 1 Command [name](svc-brdg)[service]#[no] allows-push-back Purpose Enables push-back of a call of this service. Default is disabled. Enable push-back – distribution-group service. Mode: context cs/service distribution-group Step 1 Command [name](svc-dist)[service]#[no] allows-push-back Purpose Enables push-back of a call of this service. Default is disabled.
Chapter 41 SIP call-router services Chapter contents Introduction ........................................................................................................................................................525 SIP conference-service .........................................................................................................................................525 SIP conference-service configuration task list ...............................................................................
SmartWare Software Configuration Guide 41 • SIP call-router services Introduction This chapter contains the description of all SIP specific call router services, which are only available if the software includes the SIP component. SIP conference-service RFC4240 describes how to address different services on a media server without additional SIP headers or header parameters. This mechanism makes use of the fact media servers do not manage users, they manage media services.
SmartWare Software Configuration Guide 41 • SIP call-router services Mode: Service SIP conference Step 1 Command [name] (svc-sip-conf)[name]#[no] route call dest-interface or dest-table or dest-service Purpose Specifies the next call routing destination for an incoming call. The no form of the command deletes the current routing entry.
SmartWare Software Configuration Guide 41 • SIP call-router services Lookup Domain: biloxy.com Identity: john.doe Contact: 192.168.10.1:5060 Context CS Service Location - Service sip2 Location Service Domain: biloxy.com Create address binding: Identity: john.doe Contact: 192.168.10.1:5060 Interface: sip1 sip1 INVITE sip:john.doe@biloxy.com REGISTER biloxy.com From: john.doe@biloxy.com To: john.doe@biloxy.com Contact: 192.168.10.1:5060 INVITE sip:john.doe@192.168.10.1:5060 Figure 75.
SmartWare Software Configuration Guide 41 • SIP call-router services Binding a location service If a call is route to the location-service it performs a lookup with the requested URI to the bound location service to find the address bindings. This command is optional because if no location service is bound, all existing location services will be considered to find the right contact information.
Chapter 42 Tone configuration Chapter contents Introduction ........................................................................................................................................................530 Tone-set profiles..................................................................................................................................................530 Tone configuration task list ....................................................................................................
SmartWare Software Configuration Guide 42 • Tone configuration Introduction This chapter gives an overview of call-progress-tone profiles and tone-set profiles, and describes the tasks involved in their configuration. In-band tones keep the user informed about the state of his call or additional services such as call-waiting, hold etc. Other tones can be assigned to any event that occurs during a call, a call waiting tone, for example. The inband tones are referred to as call-progress-tones.
SmartWare Software Configuration Guide 42 • Tone configuration call-progress-tone profiles Dial-A Ring-A Call Setup A Busy-A tone-set Profile A Tone Play-Out Ring -A ISDN ISDN Interface 10 Call Setup A Context CS Switch SIP Interface MySIP H323 Interface MyH323 Call Setup B ISDN Interface 11 call-progress-tone profiles tone-set Profile B ISDN Tone Play-Out Ring -B Dial-B Ring-B Busy-B Call Setup B Figure 76.
SmartWare Software Configuration Guide 42 • Tone configuration Procedure: To configure a tone-set profile Mode: Configure Step Command Purpose Creates a call-progress-tone profile with name name and enters call-progress-tone configuration mode. Defines a tone with duration duration, frequency frequency1 and volume level1.
SmartWare Software Configuration Guide Step 42 • Tone configuration Command Purpose Map a call-progress-tone profile to an internal tone. An internal tone represents the call event for which a tone indication can be provided. Use the CLI help to get a list of all available events.
SmartWare Software Configuration Guide 42 • Tone configuration Mode: Interface Step Command Purpose Enter interface configuration mode. 1 node(ctx-cs)[switch]#interface if-type ifname 2 node(if-type)[if-name]#use profile tone- Assign a user defined tone-set profile to an interface. set name Example: Assign tone-set profiles to an ISDN interface The example shows how to use the SWISS tone-set for the CS context, and use the USA tone-set for an individual interface.
SmartWare Software Configuration Guide 42 • Tone configuration The following example shows how to display the tone-set profile.
SmartWare Software Configuration Guide 42 • Tone configuration node(ctx-cs)[switch]#interface isdn bri0 node(if-isdn)[bri0]#use profile tone-set UK Tone configuration task list 536
Chapter 43 FXS port configuration Chapter contents Introduction ........................................................................................................................................................538 Shutdown and enable FXS ports..........................................................................................................................538 Bind FXS ports to higher layer applications .............................................................................................
SmartWare Software Configuration Guide 43 • FXS port configuration Introduction This chapter provides an overview of POTS signaling and SmartNode FXS ports and describes the tasks involved in configuring FXS ports in SmartWare.
SmartWare Software Configuration Guide 43 • FXS port configuration Bind FXS ports to higher layer applications An FXS port needs to be associated to an fxs interface in a CS context. The same mechanism of encapsulation and binding is used as known for e.g. Ethernet ports (see “Interfaces, Ports, and Bindings” on page 47).
SmartWare Software Configuration Guide 43 • FXS port configuration Other FXS port parameters This section describes the commands available for the configuration of an FXS port. Procedure: Configure the FXS port parameters Mode: Configure Step Command Purpose 1 node(config)#port fxs slot port 2 node(prt-fxs) [slot/port]#[no] batteryoptional reversal Enter FXS port configuration mode Reverses the line polarity at connect/disconnect of the call. This might be required by certain PBX to work correctly.
SmartWare Software Configuration Guide 43 • FXS port configuration Example The following example shows how to enter the configuration mode for FXS port 0/0, configure it with typical US settings, and bind it to an interface named fxs00 in context CS switch. 172.16.40.71>enable 172.16.40.71#configure 172.16.40.71(cfg)#port fxs 0 0 172.16.40.71(prt-fxs)[0/0]#use profile fxs us 172.16.40.71(prt-fxs)[0/0]#caller-id format bell 172.16.40.71(prt-fxs)[0/0]#flash-hook-duration 350 172.16.40.
Chapter 44 FXO port configuration Chapter contents Introduction ........................................................................................................................................................543 Shutdown and enable FXO ports.........................................................................................................................543 Bind FXO ports to higher layer applications...............................................................................................
SmartWare Software Configuration Guide 44 • FXO port configuration Introduction This chapter provides an overview of POTS signaling and SmartNode FXO ports and describes the tasks involved in configuring FXO ports in SmartWare.
SmartWare Software Configuration Guide 44 • FXO port configuration Configure country specific FXO port parameters Unlike ISDN, POTS is heavily country specific even though there is a good chance that a setting for one country works reasonably good in another country. Country specific settings are contained in a so-called fxo profile which is integrated in the firmware of the SmartNode. It can be updated independently from the firmware by means of tftp download.
SmartWare Software Configuration Guide 44 • FXO port configuration Mode: Configure Step Command 1 node(config)#port fxo slot port 2 node(prt-fxo)[slot/port]#caller-id foroptional mat { bell | etsi } 3 node(prt-fxo) [slot/port]#flash-hook optional duration duration Other FXO port parameters Purpose Enter FXO port configuration mode Specifies which line protocol is used for caller-id transmission. Use bell for US / Canada, etsi for Europe.
Chapter 45 H.323 gateway configuration Chapter contents \Introduction.......................................................................................................................................................547 Gateway configuration task list ............................................................................................................................548 Binding the gateway to an IP interface .........................................................................................
SmartWare Software Configuration Guide 45 • H.323 gateway configuration Introduction This chapter provides an overview of the H.323 gateway and describes the tasks involved in its configuration. A gateway is always needed when communication is required between different networks. A gateway provides: • Data format translation, e.g. audio and video CODEC translation • Control signaling translation, e.g. call setup and tear-down functionality on both sides of a network.
SmartWare Software Configuration Guide 45 • H.323 gateway configuration Gateway configuration task list This chapter describes the configuration of the H.323 gateway. Some parameters can be configured in the gateway configuration mode and may be overwritten in another configuration mode, For example, in the H.323 CS interface. For example, the default VoIP profile to be used with the gateway is configured in the gateway configuration mode.
SmartWare Software Configuration Guide 45 • H.323 gateway configuration The following example shows how to enable an already defined H.323 Gateway. node(cfg)#gateway h323 h323 node(gw-h323)[h323]#no shutdown Configure registration authentication service (RAS) (Optional) The H.323 gateway can either work in combination with a gatekeeper, which uses the RAS protocol for communication with the gateways or it can be used for direct calls between gateways without a gatekeeper.
SmartWare Software Configuration Guide 45 • H.323 gateway configuration Mode: Gateway H.323 Step 1 2 Command Purpose node(gw-h323)[h323]#gatekeeper-discovery auto [gkid] Specify that gatekeeper discovery has to be done automatically or or node(gw-h323)[h323]#gatekeeper-discovery manual ip-address ip-port [gkid] Specify the gatekeeper explicitly. You can repeat this command to add multiple gatekeepers. Add an H.323_ID or E.164 alias for registration.
SmartWare Software Configuration Guide 45 • H.323 gateway configuration H.235v2 Annex D provides H.323 RAS and H.225 message authentication and integrity check thus thwarting any replay and spoofing attacks on H.323 calls. If H.235 is switched on, the following security attacks are thwarted: • Denial of Service attacks • Man-in-the-middle attacks • Replay attacks (replay of recorded messages) • Spoofing • Connection hijacking Among other information such as time stamp, sender and general ID, the H.
SmartWare Software Configuration Guide 45 • H.323 gateway configuration Mode: Gateway H.323 Step 1 2 3 Command Purpose node(gw-h323)[h323]#h235security master- Sets the master password (32 hex digits, 0–9, password master-password A–F) with which the H.235 password is decrypted. Note Configure the master password only over secure links (e.g. in LAN environments only or with serial connection), which cannot be wiretapped. C:\getcryptopassword h235-password mas- Generates H.
SmartWare Software Configuration Guide Step 7 45 • H.323 gateway configuration Command node(gw-h323)[h323]#h235-security rasauth-int-tx [] Purpose Enables or disables H.235 security for transmitted RAS packets. msg is the message type. or 8 node(gw-h323)[h323]#no h235-security ras-auth-int-tx [] node(gw-h323)[h323]#h235-security q931- Enables or disables H.235 security for callauth-int signaling.
SmartWare Software Configuration Guide 45 • H.323 gateway configuration Example: Switch on H.235 security The following example shows how to use the password encryption tool and how to enable H.235 security. Additionally the H.235 security debug monitor is enabled. Generate the encrypted H.235 password from ‘myh235pwd’: C:\>getcryptopassword myh235pwd 12d3f4e76a83c6dd1067a6d34fe5cb21 H.235 Password : Encrypted H.
SmartWare Software Configuration Guide 45 • H.323 gateway configuration Mode: Gateway H.323 Step 1 Command node(gw-h323)[h323]#h245-tunneling Purpose Enables H.245 tunneling. Example: Enabling H.245 tunneling The following example shows how to enable H.245 tunneling on an already defined H.323 Gateway. node(cfg)#gateway h323 h323 node(gw-h323)[h323]#h245-tunneling] Enabling the fastconnect procedure If the fastconnect procedure is enabled, no separate H.
SmartWare Software Configuration Guide 45 • H.323 gateway configuration Changing the TCP port for inbound call-signaling connections The default TCP listening port for inbound call-signaling connections is per default 1720 as defined in the H.323 standard. The following procedure describes how to change the port number. Mode: Gateway H.
SmartWare Software Configuration Guide 45 • H.323 gateway configuration Setting the connect timeout Per default the H.323 gateway waits for 60s when the call is in the alerting phase for the call to be answered. If the call is not answered within that time, the call is dropped. The value of this timer can be changed using the following procedure: Mode: Gateway H.323 Step 1 Command Purpose node(gw-h323)[h323]# timeout connect sec- Defines the connect timeout in seconds.
SmartWare Software Configuration Guide 45 • H.323 gateway configuration Troubleshooting You can display basic status information of the H.323 gateway using the following command: Mode: Configure Step 1 Command Purpose node(gw-h323)[h323]# show gateway h323 status [detail level] Displays H.323 gateway status information. The detail level parameter is a number in the range 0 to 5 and indicates how much detail should be displayed. Example: Display H.
Chapter 46 Context SIP gateway overview Chapter contents Introduction ........................................................................................................................................................560 Context SIP Gateway configuration task list........................................................................................................561 Creating a context SIP gateway ........................................................................................................
SmartWare Software Configuration Guide 46 • Context SIP gateway overview Introduction This chapter provides an overview of the context SIP gateway. The main purpose of a context SIP gateway is forwarding and reception of SIP packets according to a RFC 3261 User Agent. In SmartWare, the context SIP gateway represents the interface between the Call-Router (Context CS) and the IP Router (Context IP).
SmartWare Software Configuration Guide 46 • Context SIP gateway overview 1. From-URI-Host equal Remote and Request-URI-Host equal Local 2. From-URI-Host equal Remote 3. Request-URI-Host equal Local 4. No match, the first configured will be taken For detailed information about call control SIP interface configuration, see Chapter 39, “SIP interface configuration” on page 441.
SmartWare Software Configuration Guide 46 • Context SIP gateway overview Creating a transport interface The interface command enters the configuration mode of a transport interface. If the requested interface does not exist, a new one will be created. The no form of the command removes an existing transport interface. Mode: Context SIP Gateway Step 1 Command [node](sip-gw)[name]# [no] interface Purpose Creates/Destroy sa transport interface or enter configuration mode.
SmartWare Software Configuration Guide 46 • Context SIP gateway overview Configuring a spoofed contact address If the device is located behind a NAT, this command can be used to provide the Contact (SIP/SDP) and VIA headers of outgoing requests with the public ip address. Mode: Transport Interface Step 1 Command [node](sip-if)[name]# [no] spoofed-contact
Purpose Applies a spoofed contact address to the transport interface.SmartWare Software Configuration Guide 46 • Context SIP gateway overview Troubleshooting Show status information Mode: Administrator Execution Step 1 Command [node]#show context sip-gateway [gwname] [detail ] Purpose Displays status and configuration information about a context sip-gateway and its bound resources like the call-control sip interfaces.
SmartWare Software Configuration Guide 46 • Context SIP gateway overview Configuration Examples Example 1 This is the minimal configuration of a working context sip-gateway. It has one transport interface that is bound to the ip address 0.0.0.0 and to the port 5060. With this configuration, the context sip-gateway processes all SIP requests addressed to port 5060 independent on which ip interface they arrive.
SmartWare Software Configuration Guide 46 • Context SIP gateway overview Applications Outbound Authentication The back-to-back user agent can provide credentials for authentication on another sip user agent or proxy. The username and password used for authentication must be configured in an authentication-service. If one or more realms are configured in the authentication-service, the credentials are only provided to challenges containing one of these realms.
SmartWare Software Configuration Guide 46 • Context SIP gateway overview 2. Determine the identity which provides credentials. The name or the alias of the identity must match the user part of the from-uri. If there is no identity that matches and an identity-group with the name “default” is configured, the identity-group “default” is taken. 3. Determine the authentication-service which provides credentials.
SmartWare Software Configuration Guide 46 • Context SIP gateway overview authenticate 1 authentication-service AUTH_PATTON username boss If the gateway receives an incoming request without credentials, the following procedure takes place: 1. Determine the location-service which challenges credentials. The domain of the location service must match the host part of the request-uri and the location-service is bound to the context sip-gateway which handles the request. 2.
SmartWare Software Configuration Guide 46 • Context SIP gateway overview location-service INALP domain inalp.com identity-group register registration outbound register auto identity 400 registration outbound registrar sip.inalp.
SmartWare Software Configuration Guide 46 • Context SIP gateway overview Inbound Registration With the according license, the back-to-back user agent can allow registrations from other user agents. Therefore, identities must be configured with a registration inbound face. Contacts to forward requests for this identity can be configured or added dynamically with REGISTER requests.
SmartWare Software Configuration Guide 46 • Context SIP gateway overview 9. Return 200 OK with all contacts registered or configured from the requested identity If one of these steps fails the registration fails and an according message is sent. A registered contact is removed out of the location-service after the expiration time has passed and the registration was not refreshed. The “SIP location-service” (on page 526) in the context cs is able to forward calls to the registered contacts.
SmartWare Software Configuration Guide 46 • Context SIP gateway overview If the sip-location-service receives a call, the following procedure takes place: 1. Determine the requested domain. If none of these three possibilities matches the call is dropped. a. If the call has a destination-uri set the host part of that uri is taken as requested domain. b. If there is no destination-uri set, but a destination-ip-address, this is taken as requested domain. c.
Chapter 47 VoIP profile configuration Chapter contents Introduction ........................................................................................................................................................574 VoIP profile configuration task list ......................................................................................................................575 Creating a VoIP profile .........................................................................................................
SmartWare Software Configuration Guide 47 • VoIP profile configuration Introduction This chapter gives an overview of VoIP profiles, and describes how they are used and the tasks involved in VoIP profile configuration. A VoIP profile is a container for all datapath-related settings on VoIP connections. The profile settings apply to all calls going through the interface. A VoIP profile can be assigned to VoIP gateways and VoIP interfaces in context CS.
SmartWare Software Configuration Guide 47 • VoIP profile configuration VoIP profile configuration task list The following tasks describe components that can be configured through the VoIP profile: • Creating a VoIP profile • Configuring codecs • Enabling DTMF relay (see page 576) • Configuring RTP payload types (see page 579) • Configuring the dejitter buffer (advanced) (see page 579) • Enabling/disabling filters (advanced) (see page 583) • Configuring fax transmission (see page 584) • Configuring modem t
SmartWare Software Configuration Guide 47 • VoIP profile configuration Configure codecs The VoIP profile contains a list of codecs the forms the set of allowed codecs that can be used to set up a VoIP connection. The list is assembled in order of priority (i.e. the first entered codec is the most preferred one). For each codec in the list, a set of parameters can be configured.
SmartWare Software Configuration Guide 47 • VoIP profile configuration Mode: Profile VoIP Step 1 Command node(pf-voip)[name]#codec g729 txlength 30 rx-length 30 silencesuppression Purpose Appends codec g729 to the list of codecs. Specifies the payload duration for transmitted RTP packets of this codec, and the maximum supported payload duration for received RTP packets of this codec. Allows silence suppression to be used with this codec.
SmartWare Software Configuration Guide 47 • VoIP profile configuration Mode: Profile VoIP Step 1 Command node(pf-voip)[name]#codec 1 g729 txlength 30 rx-length 30 silencesuppression Purpose Inserts codec g729 at the first position of the list (most preferred codec). The parameters are the same previously described. If the codec g729 had yet existed in the list, it is moved to the first position of the list, adopting the entered parameter values.
SmartWare Software Configuration Guide 47 • VoIP profile configuration Configuring DTMF relay Dual tone multi-frequency (DTMF) tones are usually transported accurately in band when using high bit-rate voice codecs such as G.711. Low bit-rate codecs such as G.729 and G.723.1 are highly optimized for voice patterns and tend to distort DTMF tones. The dtmf relay command solves the problem of DTMF distortion by transporting DTMF tones out-of-band or separate from the encoded voice stream as shown in figure 2.
SmartWare Software Configuration Guide 47 • VoIP profile configuration Configuring RTP payload type for transparent-clearmode The following command configures the RTP payload type used for the transparent-clearmode codec. Mode: configure/profile voip Step Command 1 Purpose [name](pf-voip)[profile]#[no] crtp payloadtype transparent-clearmode Specifies the rtp payload type used for transparent clearmode. Value must be between 97 and 127. Default value is 97.
SmartWare Software Configuration Guide 47 • VoIP profile configuration ‘v150-vbd’ is selected, a re-invite will be sent even if the current voice coder is configured the same as the modem bypass coder. Furthermore the re-invite contains a gpmd-attribute line with the value ‘vbd=yes;ecan=off ’ in the media description part. This attribute signals the remote device of the new media transmission. If the command option ‘default’ is selected, the system behavior is the same as before.
SmartWare Software Configuration Guide 47 • VoIP profile configuration The operating modes for the dejitter buffer are illustrated in figure 4: • Adaptive—The adaptive buffer automatically adapts to variations in the network’s delay characteristics and in general yields the best results for voice conversations. IMPORTANT In the adaptive dejitter buffer there are parameters that can be configured (such as shrink-speed, grow-step, etc.) that should not be changed unless it is necessary to do so.
SmartWare Software Configuration Guide 47 • VoIP profile configuration Mode: Profile VoIP Step 1 Command Purpose node(pf-voip)[name]#dejitter-mode mode Specify the dejitter buffer as adaptive, static or static-data. node(pf-voip)[name]#dejitter-max-delay Specify the maximum delay in milliseconds that the max-delay dejitter buffer is allowed to introduce. This setting is valid for all modes.
SmartWare Software Configuration Guide 47 • VoIP profile configuration Configuring Fax transmission Fax is a protocol for electronically transmitting written material in-band over a voice channel. In public switched telephone networks (PSTN), a fax is handled the same way as a voice conversation. A G3 Fax device transforms (modulates) a scanned page into audible tones that are transmitted in-band. The receiving device converts the tones (demodulates) and reconstructs the page.
SmartWare Software Configuration Guide FAX Bypass 47 • VoIP profile configuration generated tones transported in RTP payload Node Node Node Node RTP Stream Modulated data Modulated data FAX Relay Modulated data reference data transported over T.38 Terminate fax protocol Terminate fax protocol Node Node Modulated data Node Node reference data Modulated data Figure 6.
SmartWare Software Configuration Guide 47 • VoIP profile configuration Mode: Profile VoIP Step 1 Command Purpose node(pf-voip)[name]#fax transmis- Adds fax bypass transmission with codec G.711 sion bypass g711alaw64k to the list of fax transmission modes.Alternative codecs available are: • G.711uLaw • G.726 32kbps • G.726 24kbps. 2 node(pf-voip)[name]#fax dejitteroptional max-delay buffer-size Sets the size of the dejitter buffer during fax transmissions.
SmartWare Software Configuration Guide Step 47 • VoIP profile configuration Command Purpose 4 node(pf-voip)[name]#fax volume (optional) volume Adjusts the volume of the fax signals re-generated on the receiver side. The volume is in dB, in the range -18.5 ... -3.5 (Default: -9.5dB). 5 node(pf-voip)[name]# fax max-bit- Sets maximum allowed bit-rate for fax relay (optional) rate { 2400 | 4800 | 7200 | 9600 | (Default 14400 Bit/sec).
SmartWare Software Configuration Guide 47 • VoIP profile configuration T.38 No-Signal Retransmission Some SIP gateways change their port number when switching from audio to T.38. This behavior causes problems if the SmartNode is located on the A-Side behind a NAT. Due to T.30 is a unidirectional. protocol and the B-Side is normally the initiator of the T.30 handshaking, the SmartNode never receives the initial packets of the B-Side because the NAT ports are not yet opened.
SmartWare Software Configuration Guide Step 2 47 • VoIP profile configuration Command [name] (pf-voip)[pf-name]# fax transmission 2 bypass g711alaw64k Note Purpose Define G.711 A-Law as the second fax transmission method to try, if T.38 is not supported by the remote gateway. The first codec must always be T.38, while the second one must be a highrate codec such as G.711, which supports fax transmission.
SmartWare Software Configuration Guide 47 • VoIP profile configuration Configuring the traffic class for Voice and Fax data The traffic class for voice data and fax data is configurable. The configured traffic class is used as additional routing criterion in the IP routing table. Mode: Profile VoIP Step 1 Command Purpose [ name] (pf-voip)[profile]# rtp trafficclass Sets traffic class for voice data and fax data packets. The traffic class may be new or may already exist.
SmartWare Software Configuration Guide 47 • VoIP profile configuration Examples Different applications require different VoIP profiles. This section includes a variety of applications and show how the VoIP profile for these applications would be configured. Home office in an enterprise network Figure 7 is an example of a home office in an enterprise network. The connection bandwidth is 128 kbps and is of very low quality, so the low bit-rate G.723_6k3 codec is used.
SmartWare Software Configuration Guide G.723 6k3: 47 • VoIP profile configuration rxlen=30;txlen=30;ss Fax Transmission Modem Transmission Dejitter -------Mode: Max. Delay: Max. Packet Loss: Shrink Speed: Grow Step: Grow Attenuation: High Pass Filter: Post Filter: Adaptive 100ms 4/1000 1 1 1 enabled enabled Fax --Detection: T.38 High Speed Redundant Packets: T.38 Low Speed Redundant Packets: Max. Bit Rate: Volume: Error Correction: HDLC: Dejitter Max Delay: CED Tone 0 0 14400bps -9.
SmartWare Software Configuration Guide 47 • VoIP profile configuration 8. Show the configured profile. Home office with fax Preconditions are those used in section “Home office in an enterprise network” on page 591: low bandwidth and high jitter. In this example, bandwidth is 256 kbps, what enables us to use the G.729 codec.
SmartWare Software Configuration Guide Error Correction: HDLC: Dejitter Max Delay: 47 • VoIP profile configuration enabled enabled 200ms Modem ----Max. Bit Rate: Volume: HDLC: 14400 -9.500dB enabled DTMF ---Relay: Mute Encoder: enabled enabled RTP --Payload Type NTE: 101 Description: 3. Create VoIP profile and give it a name. All settings have default values 4., 5. Remove the default codecs G.711alaw and G.711uLaw 6. Add codec g729 with silence-suppression enabled 7.
SmartWare Software Configuration Guide G.711 u-law: G.723 6k3: 47 • VoIP profile configuration rxlen=20;txlen=20 rxlen=30;txlen=30 Fax Transmission Modem Transmission Dejitter -------Mode: Max. Delay: Max. Packet Loss: Shrink Speed: Grow Step: Grow Attenuation: High Pass Filter: Post Filter: Adaptive 60ms 4/1000 1 1 1 enabled enabled Fax --Detection: T.38 High Speed Redundant Packets: T.38 Low Speed Redundant Packets: Max.
SmartWare Software Configuration Guide 47 • VoIP profile configuration 6. Disable DTMF relay. 7. Show the configured profile.
Chapter 48 PSTN profile configuration Chapter contents Introduction ........................................................................................................................................................598 PSTN profile configuration task list ....................................................................................................................598 Creating a PSTN profile ...........................................................................................................
SmartWare Software Configuration Guide 48 • PSTN profile configuration Introduction This chapter gives an overview of PSTN profiles, and describes how they are used and the tasks involved in PSTN profile configuration. A PSTN profile is a container for all datapath-related settings on PSTN connections. It can be assigned to PSTN interfaces in context CS. If no profile is specified in a particular interface, the profile default is used. The settings apply to all calls crossing the interface.
SmartWare Software Configuration Guide 48 • PSTN profile configuration Procedure: Create a PSTN Profile and enter the PSTN profile configuration mode Mode: Configure Step 1 2 Command Purpose node(cfg)#profile pstn name Create a PSTN profile with name name and enter PSTN profile configuration mode. The newly created profile contains default values for all parameters. If a profile with name name already exists, only the PSTN profile configuration mode is entered.
SmartWare Software Configuration Guide 48 • PSTN profile configuration Mode: Profile PSTN Step 1 Command node(pf-pstn)[name]#output-gain gain PSTN profile configuration task list Purpose Set the output gain to value in dB 600
Chapter 49 SIP profile configuration Chapter contents Introduction ........................................................................................................................................................602 SIP profile configuration task list.........................................................................................................................602 Entering the configuration mode for a SIP profile ...............................................................................
SmartWare Software Configuration Guide 49 • SIP profile configuration Introduction The SIP profile specifies disconnect cause mappings from SIP codes to Q.931 causes, and vice versa. As for all profiles, there is a default profile at system startup that can be modified. Only those causes that differ from the default mapping have to be configured. If a new profile is created, all mappings are set to their default and are only overwritten if configured.
SmartWare Software Configuration Guide 49 • SIP profile configuration Mapping to a SIP cause The map cause to-sip command can be used to map a call control Q.931 cause to a SIP cause. All causes are pre-defined in the system and are provided by the command. Mode: Profile SIP Step 1 Command [name](pf-sip)[name]#map cause to-sip q931-cause to sip-cause Purpose Maps a specific Q.931 disconnect cause to a SIP cause code.
Chapter 50 Authentication Service Chapter contents Introduction ........................................................................................................................................................605 Authentication Service configuration task list ......................................................................................................605 Creating an Authentication Service ........................................................................................................
SmartWare Software Configuration Guide 50 • Authentication Service Introduction This chapter describes how to configure authentication services in SmartWare. The Authentication Service is a data base that manages Authentication Credentials of one or more Realm. A Realm is an Authentication Zone or Authentication Domain that defines the authentication responsibility in a network.
SmartWare Software Configuration Guide 50 • Authentication Service Configuring a Realm The following commands add a new Realm to the authentication service. If more than one Realm has to be entered, the order of the list can be modified by using the index and/or before and after keywords. The no form of the command removes an existing Realm from the list.
Chapter 51 Location Service Chapter contents Introduction ........................................................................................................................................................608 Location Service configuration task list ................................................................................................................608 Creating a Location Service .................................................................................................................
SmartWare Software Configuration Guide 51 • Location Service Introduction This chapter describes how to configure location services in SmartWare. Location Service configuration task list The following section describes how to create a new location service and how to enter the configuration mode of an existing service. Additionally, it describes all commands and sub commands of the location service configuration mode.
SmartWare Software Configuration Guide 51 • Location Service and the Context SIP Gateway has more than one transport binding, it is recommended to add the local host addresses as Domain to the appropriated location services. Mode: Location Service Step 1 Command [node](ls)[name]# [no] domain or [node](ls)[name]#domain or [node](ls)[name]#domain before or [node](ls)[name]#domain after Purpose Adds a new domain to the location service.
SmartWare Software Configuration Guide 51 • Location Service An alias is an alternative way to express the user-part of an identity. An alias is never used to build a sip-uri and will never be used in communication with another device. The alias is used for comparing or matching the identity with a sip-uri received from an external device. Mode: Identity Step 1 Command [node](identity)[name]# [no] alias name Purpose Adds a new alias to the identity.
SmartWare Software Configuration Guide 51 • Location Service Mode: Authentication outbound Step Command Purpose 1 [node](authout)#authenticate authentication-service [username ] or [node](authout)#authenticate authentication-service [username ] or [node](authout)#authenticate before authentication-service [username ] or [node](authout)#authenticate after authentication-servi
SmartWare Software Configuration Guide 51 • Location Service Mode: Authentication inbound Step Command Purpose 1 [node](authin)#authenticate authentication-service [username ] or [node](authin)#authenticate authentication-service [username ] or [node](authin)#authenticate before authentication-service [username ] or [node](authin)#authenticate after authentication-service
SmartWare Software Configuration Guide 51 • Location Service Registration outbound face The registration outbound face is used to register an identity on an external registrar. Then, the registrar forwards calls from the registered identity to your identity. Mode: Identity Step 1 Command [node](identity)[name]# [no] registration outbound Purpose Adds a new face to the identity. The no form of the command removes an existing face with all content in it.
SmartWare Software Configuration Guide 51 • Location Service Mode: Registration outbound Step Command Purpose 1 [node](regout)#proxy [] [strict-route] or [node](regout)#proxy [] [strict-route] or [node](regout)#proxy before [] [strict-route] or [node](regout)#proxy after [] [strict-route] Adds a new proxy entry to the registration outbound face. For each proxy configured there is a route-header added.
SmartWare Software Configuration Guide 51 • Location Service Registration inbound face The registration inbound face is used when you want to allow external user agents to register, so that you can route calls to the registered contacts. Mode: Identity Step 1 Command [node](identity)[name]# [no] registration inbound Purpose Adds a new face to the identity. The no form of the command removes an existing face with all content in it.
SmartWare Software Configuration Guide 51 • Location Service Call outbound face The call outbound face is used to configure call properties for outgoing calls. Mode: Identity Step 1 Command [node](identity)[name]# [no] call outbound Purpose Adds a new face to the identity. The no form of the command removes an existing face with all content in it.
SmartWare Software Configuration Guide 51 • Location Service Mode: Call outbound Step 1 Command Purpose [node](callout)#proxy down index can be moved in the proxy list up or down or the number of positions given in the command.
SmartWare Software Configuration Guide 51 • Location Service Creating an identity group Multiple identities with the same properties can be grouped in an identity-group. The identity-group can be configured exactly in the same way and with the same parameters as an identity. An identity-group can only inherit configurations to identities, but they never play an active role. The special identity-group “default” inherits parameters to identities which are unknown or not configured.
SmartWare Software Configuration Guide 51 • Location Service Configuring the Message Waiting Indication feature for SIP Note Message Waiting Indication is programmed in two sections of SmartWare, the FXS interface, and the SIP Location service. The information below refers to information for configuring the Message Waiting Indication feature for SIP. For information on configuring the Message Waiting Indication feature for FXS, see “Configuring the Message Waiting Indication feature for FXS” on page 408.
SmartWare Software Configuration Guide 51 • Location Service Notification If the gateway receives an incoming NOTIFY request, the following procedure takes place: 1. Determine to which sip interface in the context cs the request should be forwarded. This happens according the same rules as an incoming INVITE is forwarded. 2. Get Identity. All location services bound to the context sip-gateway are searched for the identity: a. the identity matching the to-uri b. the identity matching request-uri c.
SmartWare Software Configuration Guide 51 • Location Service Mode: Message inbound Step 1 Command Purpose [node](msgin)#[no] message server Configures the address of the message server to [] send your subscription requests for explicit subscription. When no message-server is configured, the subscription requests are sent to the first domain entry in the location-service.
SmartWare Software Configuration Guide 51 • Location Service Message Waiting Indication through Call-Control The message waiting indication received on the SIP side is transported through the call control to the destination FXS interface. Currently, the SIP interface is the only source of message waiting indication information and the FXS interface is the only possible destination of this information. The information is routed like a call through the call-control.
SmartWare Software Configuration Guide 51 • Location Service Configuration Examples In this configuration example, inheritance is used. Example: location-service INALP domain inalp.com identity-group REGISTER authentication outbound authenticate 1 authentication-service AUTH_INALP username john registration outbound registrar sip.inalp.com lifetime 600 register auto identity 300 inherits REGISTER identity identity 400 inherits REGISTER Exactly the same can be configured without inheritance.
Chapter 52 VoIP debugging Chapter contents Introduction ........................................................................................................................................................625 Debugging strategy..............................................................................................................................................625 Filtering debug monitor output .........................................................................................................
SmartWare Software Configuration Guide 52 • VoIP debugging Introduction This chapter describes how to debug VoIP sessions, including the signaling part and the voice data path part (speech, fax, and modem connectivity). It provides debugging strategies to help locate the source of a problem, and describes the show and debug commands used to verify correct system operation and to troubleshoot problems.
SmartWare Software Configuration Guide 52 • VoIP debugging Filtering debug monitor output The output of the debug monitors can be filtered using the following command to let the terminal only print important information. The specified expression is a regular expression, which is used by the filter to select important lines. Mode: Configure Step 1 Command [name](cfg)# [no] terminal monitor-filter Purpose Enables the monitor filter using the specified expression.
SmartWare Software Configuration Guide 52 • VoIP debugging route to host” response) and a successful connection to host 172.16.40.122 (which received and sent packets with no loss). node#ping 192.195.23.1 10 timeout 5 Sending 10 ICMP echo requests to 192.195.23.10, timeout is 5 seconds: % No route to host node# node#ping 172.16.40.122 Sending 5 ICMP echo requests to 172.16.40.122, timeout is 1 seconds: Reply from 172.16.40.122: Time <10ms Reply from 172.16.40.122: Time <10ms Reply from 172.16.40.
SmartWare Software Configuration Guide Command unit#debug ccisdn error unit#debug ccisdn datapath unit#debug isdn error unit#debug isdn event slot port {all | layer2 | layer3} unit#show port isdn slot port status unit#show call-control provider name [detail detail] 52 • VoIP debugging Purpose Prints all errors occurring in ISDN call control and ISDN datapath control. Always switch this monitor on when debugging ISDN. Prints operations on the ISDN part of the voice data path.
SmartWare Software Configuration Guide 18:34:10 ICC 52 • VoIP debugging > [TERMINAL-00b73348] >> SETUP ACKNOWLEDGEMENT (DSS1 Ntwk) 18:34:10 ICC > [TERMINAL-00b73348] State: OVERLAP SENDING, Event: PEER TRYING 18:34:10 ICC > [TERMINAL-00b73348] State: OVERLAP SENDING, Event: PEER ALERTING 18:34:10 ICC > [TERMINAL-00b73348] Set state to CALL DELIVERED 18:34:10 ICC > [TERMINAL-00b73348] >> ALERTING (DSS1 Ntwk) Progress indicator : inband information available private network serving local user - CCITT 18:
SmartWare Software Configuration Guide 52 • VoIP debugging 22:03:06 ICC > [PSTN] NEW CALL. Allocated Endpoint PSTN-00b70a20 22:03:06 ICC > [PSTN-00b70a20] >> SETUP (DSS1 User) Bearer capability : speech - CCITT circuit mode - 64kBit/s - G.
SmartWare Software Configuration Guide 52 • VoIP debugging ISDN port status using the show port isdn command, and the debug isdn events commands (see below).
SmartWare Software Configuration Guide 52 • VoIP debugging Debugging FXS Signaling Overview: FXS debug monitors Command unit#debug ccfxs unit#debug fxs unit#debug media-gateway control unit#show call-control provider name [detail detail] Purpose Prints all operations on the FXS interfaces (highlevel). Prints all operations on the FXS ports (low-level). Prints the dialed digits. Shows the status of an FXS interface in context CS (call control part of FXS signaling).
SmartWare Software Configuration Guide 52 • VoIP debugging • 09:00:43 CFXS > [EP PHONE] Play tone: ringback-tone: The called-party is ringing, alerting-tone is played to the phone. This means that the call arrived correctly in context CS, and has reached its destination. • If the above line does not appear, the call has arrived in context CS, but has not reached its destination. Continue debugging call-router and the outgoing call to the destination signaling protocol.
SmartWare Software Configuration Guide 52 • VoIP debugging • 09:14:02 CFXS > [EP PHONE] Change state to CONNECTED.: The phone went off-hook and thus accepted the call. The state of the CS interface goes to CONNECTED. The call is now established. Debugging H.323 Signaling Overview: H.
SmartWare Software Configuration Guide 52 • VoIP debugging ---------State: Gatekeeper: REGISTERED 172.16.32.
SmartWare Software Configuration Guide 52 • VoIP debugging Explanation: • First the state of the gateway is checked. The state is “UP”, and the RAS engine is “REGISTERED”, which is OK. • The line 00:29:03 H323 > [EP h323-00c13dc0] Stack: Allocated new call: 0x00be56b tells that there is a new call incoming from H.323. This means that transport layer is OK. If there is no debug output at all, try to use debug gateway h323 tpktchan, which monitors all H.323 socket TCP traffic.
SmartWare Software Configuration Guide 52 • VoIP debugging 01:00:10 H323 > [EP h323-00c07230] Display: 50 01:00:10 H323 > [EP h323-00c07230] User-User: 01:00:10 H323 > [EP h323-00c07230] Set state to TERMINAL TRYING 01:00:10 H323 > [EP h323-00c07230] State: TERMINAL TRYING, Call Event: PEER CONNECTED 01:00:10 H323 > [EP h323-00c07230] State: TERMINAL TRYING, Call Event: PROGRESS 01:00:10 HRAS > Stack: Received Admission Confirm 01:00:10 H323 > [EP h323-00c07230] Stack: State: DIALTONE 01:00:10 H323 > [EP
SmartWare Software Configuration Guide 52 • VoIP debugging Debugging SIP signaling Mode: Administrator Execution Step 1 Command Purpose [node]#debug context sip-gateway data- Logs information related to the media chanpath [detail ] nels. [node]#debug context sip-gateway error Logs all errors detected within the Context SIP [detail ] Gateway. [node]#debug context sip-gateway regis- Logs information about user registration activtration [detail ] ities.
SmartWare Software Configuration Guide 52 • VoIP debugging Explanation: • The line 18:59:07 SIP_TR> Sent INVITE sip:60@172.16.32.33 SIP/2.0 indicates that the INVITE was sent. Thus, call routing worked in context CS and the message left to the SIP network. • 18:59:07 SIP_TR > Received SIP/2.0 100 Trying indicate that responses are received from the SIP network. This means that IP connectivity is OK and the remote gateway can be reached.
SmartWare Software Configuration Guide 52 • VoIP debugging presentation allowed - user provided not screened 19:17:44 ICC > [TERMINAL-00df2760] State: CALL RECEIVED, Event: TERMINAL CONNECT IND 19:17:44 ICC > [TERMINAL-00df2760] Set state to ACTIVE 19:17:44 ICC > [TERMINAL-00df2760] >> CONNECT ACKNOWLEDGEMENT (DSS1 Ntwk) unit(cfg)# unit(cfg)#call 55 drop unit(cfg)#19:19:29 ICC > [TERMINAL-00df2760] State: ACTIVE, Event: PEER RELEASED 19:19:29 ICC > [TERMINAL-00df2760] Set state to DISCONNECT INDICATION 19
SmartWare Software Configuration Guide 52 • VoIP debugging [no] debug media-gate- Displays RTP related call parameters at call setup: local/remote IP way rtp address and port, SSRC. During operation, displays periodically updated statistics containing the number of sent and received packets, the number of lost packets. Usage: To verify that RTP packets are sent/received, and to debug network quality issues (lost packets). [no] debug media-gate- Displays control activities on the TDM part of the Data Path.
SmartWare Software Configuration Guide 52 • VoIP debugging Prerequisite: Fax transmission is configured for T.38 relay in the voip profile. The call is established from a signaling point of view (see section “Debugging voice data” on page 640). Attention: Special signaling procedures are used for the transition between voice and fax data transmission. It may be that the initial call setup is correct, but that the signaling to T.38 over H.323 is faulty. The session-control and H.
SmartWare Software Configuration Guide 52 • VoIP debugging can do this either in the same Telnet session, or using different Telnet sessions. • Network traffic traces—In certain cases it may be helpful to have a trace of the traffic on the IP network in order to inspect packet contents. Please use one of the following tools (supporting trace file formats which our tools can read): - Network Associates Sniffer—Details are available at www.sniffer.com - TTC Firebird—Details are available at www.ttc.
Appendix A Terms and definitions Chapter contents Introduction ........................................................................................................................................................645 SmartWare architecture terms and definitions .....................................................................................................
SmartWare Software Configuration Guide A • Terms and definitions Introduction This chapter contains the terms and their definitions that are used throughout this SmartWare Software Configuration Guide. This guide contains many terms that are related to specific networking technologies areas such as LAN protocols, WAN technologies, routing, Ethernet, and Frame Relay. Moreover various terms are related to telecommunication areas.
SmartWare Software Configuration Guide Term or Definition Comfort Noise Command Line Interface Configuration Download Configuration File Configuration Server Configuration Upload Context Data Port Dejitter Buffer Digit Collection Driver Software Download Driver Software Image DTMF Relay Echo Canceller Factory Configuration Fast Connect Flash Memory A • Terms and definitions Meaning Comfort noise is generated at the remote end of the silent direction to avoid the impression that the connection is
SmartWare Software Configuration Guide Term or Definition flash: Gatekeeper Gateway H.323 H.323 RAS High-Pass Filter Host Hostname Hunt Group Interface Interface Card ISDN ISDN Services Jitter Mode A • Terms and definitions Meaning A region in the persistent memory of a SmartNode. See also flash memory. Gatekeepers manage H.323 zones, which are logical collections of devices such as all H.323 devices within an IP subnet.
SmartWare Software Configuration Guide Term or Definition Network Management System Node Nodename nvram: Operator PCI Local Bus PCM Highway Port Port Address Post Filter POTS Profile PSTN Q.931 Tunneling Q.SIG Release Routing Engine Running Configuration Session Router Session Initiation Protocol (SIP) Silence Compression A • Terms and definitions Meaning System responsible for managing at least part of a network.
SmartWare Software Configuration Guide Term or Definition Startup Configuration Switching Engine System Image System Memory system: TFTP Server tftp: A • Terms and definitions Meaning 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. Part of the SmartNode hardware which allows software controlled circuit switching of circuit ports.
Appendix B Mode summary Chapter contents Introduction ........................................................................................................................................................
SmartWare Software Configuration Guide B • Mode summary Introduction Figure 1 on page 651, figure 2 on page 652, and figure 3 on page 653 show the configuration mode hierarchy. Each box contains the mode name, the command to enter in this mode and the mode prompt printed in a Telnet or console session. The commands are defined in appendix C, “Command summary” on page 654.
SmartWare Software Configuration Guide B • Mode summary Gateways Gateway H323 gateway h323 (gw-h323)[]# (gw-h323)[]# Gateway SIP gateway sip (gw-sip)[]# Ports Port Ethernet port ethernet (prt-eth)[/]# PPPoE (pppoe)[/]# PPPoE Session session (session)[]# Port Gateway E1T1 H323 or BRI gateway port bri h323 (prt-bri)[/]# Gateway Q.
SmartWare Software Configuration Guide B • Mode summary Profiles Profile ACL port ethernet profile acl Profile Gateway Authentication H323 profile gateway authentication h323 (pf-auth)[]# ProfileGateway Call-Progress-Tone H323 profilegateway call-progress-tone h323 (pf-callp)[]# Profile Gateway DHCPH323 Server profile gateway dhcp-server h323 (pf-dhcps)[]# ProfileGateway IPSEC Manual H323Policy profi
Appendix C Command summary Chapter contents Introduction ........................................................................................................................................................655 New Configuration Commands ..........................................................................................................................656 Other.............................................................................................................................................
SmartWare Software Configuration Guide C • Command summary Introduction This chapter provides an overview of all CLI commands and modes available. It is organized as follows: Mode Name Enter Command Command 1 … Exit Mode Name … Several commands contain a lot of parameters and arguments. The command syntax is described as follows: • Arguments where you must supply the value are surrounded by .
SmartWare Software Configuration Guide C • Command summary New Configuration Commands The commands documented in the Release Note only cover new additions which are not yet included in the current revision of the Software Configuration Guide. You may download the release notes at www.patton.com/support. Current Revision: Document Number: 13211U8-001 Rev. D Part Number: 07MSWR320_SCG Revised: July 17, 2006 Other Show help Step 1 Command help [topic] Purpose Shows command help.
Appendix D Internetworking terms & acronyms Chapter contents Abbreviations.......................................................................................................................................................
SmartWare Software Configuration Guide D • Internetworking terms & acronyms Abbreviations Abbreviation Numeric 10BaseT A AAL ABR AC AOC ATM audio 3.1 audio 7.2 B BRA BRI C CAC CBR CD ROM CDR CFP CLEC CLI CLIP CO CPE CPU CRC32 D DC DDI DHCP DLCI DSL DSLAM DSP DTMF E E1 Abbreviations Meaning Ethernet Physical Medium ATM Adaptive Layer Available Bit Rate Alternating Current Advice of Charge Asynchronous Transfer Mode ISDN Audio Service up to 3.1 kHz ISDN Audio Service up to 7.
SmartWare Software Configuration Guide Abbreviation E-DSS1 EFS ET ETH F FAQ FCC FR G G.711 G.723 GUI GW H H.
SmartWare Software Configuration Guide D • Internetworking terms & acronyms Abbreviation Modem MSN N NAPT NAT NIC NT NT1 NT2 NT2ab O OEM OSF OSPF P PBR PBX PC PMC POP POTS PRA PRI PSTN pt-mpt pt-pt PVC pwd PWR Q QoS R RIPv1 RIPv2 RJ-45 RTM RTP S S1 Abbreviations Meaning Modulator – Demodulator Multiple Subscriber Number Network Network Network Network Network Network Network Address Port Translation Address Translation Interface Card Termination Termination 1 Termination 2 Termination with 2a/b Connect
SmartWare Software Configuration Guide Abbreviation S2 SAR S-Bus SCN SCTP SDSL SGCP SIP SME SNMP SOHO SONET SS7 STM SVC SW T TCP/IP TE TFTP U UBR UD 64 UDP V VBR VCI VoIP VPI W WAN Abbreviations D • Internetworking terms & acronyms Meaning node-connection for Subscriber Line Segmentation and Reassembly Subscriber Line (Connection) Bus Switched Circuit Network Stream Control Transmission Protocol Symmetric Digital Subscriber Line Simple Gateway Control Protocol Session Initiation Protocol.
Appendix E Used IP ports & available voice codecs Chapter contents Used IP ports ......................................................................................................................................................663 Available voice codecs .........................................................................................................................................
SmartWare Software Configuration Guide E • Used IP ports & available voice codecs Used IP ports Component H.323 SIP NAPT Telnet Webserver DHCP TFTP Used IP ports Port Description UDP 1719 TCP 1720 UDP 4864…5118 (even numbers) UDP 4865…5119 (odd numbers) UDP 5060 TCP 5060 UDP 4864…5118 (even numbers) UDP 4865…5119 (odd numbers) RAS for gatekeeper connection Call signaling port for H.
SmartWare Software Configuration Guide E • Used IP ports & available voice codecs Available voice codecs Protocol H.323 & SIP Codec Net Bandwidth per Call (kbps) Min. Compression Delay (ms) Used Bandwidth per Call (kbps, incl. IP header) G.711 A-law 64 10 96 G.711 U-law 64 10 96 G.723.1 6.3 30 17 G.729/ G.729a 8 10 40 Transparent 64 10 G.726 16, 24, 32, 40 20 G.727 16, 24, 32 20 T.
