Catalyst 4224 Access Gateway Switch Software Configuration Guide March 2003 Corporate Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
C ON T E NT S Preface xvii Objectives xvii Audience xviii Organization xviii Related Documentation xix Conventions xx Obtaining Documentation xxi Cisco.com xxi Documentation CD-ROM xxi Ordering Documentation xxii Documentation Feedback xxii Obtaining Technical Assistance xxiii Cisco.
Contents VoIP Gateway 1-6 IP Routing and WAN Features 1-7 Quality of Service 1-9 VPN and Firewall Features 1-9 Application Notes 1-10 Architecture 1-10 DSP Allocation 1-11 InterVLAN Routing 1-14 Quality of Service 1-14 Layer 2 QoS 1-14 Separate Voice and Data VLANs 1-15 Single Voice and Data VLAN with dot1p 1-15 Layer 3 QoS 1-16 WAN QoS Queuing and Scheduling 1-16 Summary of the Layer 3 WAN QoS Features 1-16 Configuration Guidelines 1-18 Default Port Configuration 1-18 Separate VLAN for Voice and Data 1-19
Contents No Ring Back Tone Generated 1-25 MTP Required on Cisco CallManager 1-26 H323-Gateway VOIP Bind SRCADDR Command 1-27 Port Fast Not Enabled on Trunk Ports 1-28 Priority Queuing on Frame Relay 1-28 Maximum Number of VLAN and Multicast Groups 1-29 IP Multicast Support 1-29 CHAPTER 2 Configuring for the First Time 2-1 First-Time Configuration 2-1 Booting the Catalyst 4224 2-2 Downloading an Image to Boot Flash Memory 2-2 Connecting a Terminal 2-3 Connecting a Modem 2-3 Configuring the Management Por
Contents Configuring Ethernet Ports to Support IP Phones and a Daisy-Chained Workstation 3-3 Configuring Separate Voice and Data Subnets 3-4 Voice Traffic and VVID 3-5 Sample Configuration 1 3-6 Sample Configuration 2 3-6 Configuring a Single Subnet for Voice and Data 3-7 Sample Configuration 3-9 Configuring Ethernet Ports to Support IP Phones with Multiple Ports 3-9 IP Addressing 3-9 Sample Configuration 3-10 Managing the Catalyst 4224 Access Gateway Switch 3-10 Adding Trap Managers 3-11 Configuring IP In
Contents CHAPTER 4 Configuring the Data Interfaces 4-1 Configuring the Host Name and Password 4-2 Configuring the Fast Ethernet Interface 4-4 Configuring Asynchronous/Synchronous Serial Interfaces 4-6 Configuring ISDN BRI Interfaces 4-9 Configuring T1 and E1 Interfaces 4-12 Configuring T1 Interfaces 4-12 Configuring E1 Interfaces 4-16 Checking the Interface Configuration 4-18 Saving Configuration Changes 4-19 CHAPTER 5 Configuring the Voice Interfaces 5-1 Configuring Voice Interfaces 5-1 MGCP Configur
Contents ISDN BRI Configuration (H.323) 5-24 Configuring ISDN BRI Lines 5-26 ISDN BRI Provisioning by Switch Type 5-26 Defining ISDN Service Profile Identifiers 5-29 BRI Direct-Inward Dialing Configuration 5-29 Gateway 1 Configuration 5-30 Gateway 2 Configuration 5-31 T1/E1 Configuration (H.323) 5-31 Configuring T1 Interfaces 5-31 T1/PRI Configuration Example 5-33 Configuring E1 Interfaces 5-33 E1/PRI Configuration Example 5-34 E&M Trunk Line Configuration (H.
Contents Configure Real-Time Transport Protocol Header Compression 6-9 Enable RTP Header Compression on a Serial Interface 6-11 Change the Number of Header Compression Connections 6-11 RTP Header Compression Configuration Example 6-11 Configure Custom Queuing 6-11 Configure Weighted Fair Queuing 6-12 Configure Number Expansion 6-12 Create a Number Expansion Table 6-13 Configure Number Expansion 6-15 Configure Dial Peers 6-15 Inbound Versus Outbound Dial Peers 6-17 Create a Dial-Peer Configuration Table 6-1
Contents Additional VoIP Dial-Peer Configurations 6-33 Configure IP Precedence for Dial Peers 6-33 Configure RSVP for Dial Peers 6-34 Configure codec and VAD for Dial Peers 6-35 Configure codec for a VoIP Dial Peer 6-35 Configure VAD for a VoIP Dial Peer 6-36 Configure Frame Relay for VoIP 6-37 Frame Relay for VoIP Configuration Example 6-38 CHAPTER 7 Configuring the Eight-Port FXS RJ-21 Module 7-1 Eight-Port RJ-21 FXS Module User Interface Conventions 7-2 Configuring FXS Voice Ports 7-2 Changing Defaul
Contents Configuring Survivable Remote Site Telephony 8-7 Verifying Survivable Remote Site Telephony 8-9 Troubleshooting Survivable Remote Site Telephony 8-10 Monitoring and Maintaining Survivable Remote Site Telephony 8-11 SRST Configuration Example 8-12 CHAPTER 9 Implementing Fax over IP on Cisco Voice Gateways 9-1 Overview 9-2 Fax Pass-Through 9-2 Cisco Fax Relay 9-3 Supported Platforms and Features 9-4 CHAPTER 10 Traffic Shaping 10-1 About Traffic Shaping 10-2 Why Use Traffic Shaping? 10-2 Traffi
Contents Frame Relay Traffic Shaping 10-9 How It Works 10-10 Derived Rates 10-10 Configuration and Commands 10-11 Restrictions 10-12 Distributed Traffic Shaping 10-12 Prerequisites 10-12 How It Works 10-12 Configuration 10-13 Restrictions 10-14 Low-Latency Queueing 10-14 CHAPTER 11 Configuring Encryption Services 11-1 Configuring the Encryption Service Adapter 11-2 Step 1: Configure the T1 Channel Group 11-2 Step 2: Configure the Internet Key Exchange Security Protocol 11-3 Step 3: Configure IPSec Netwo
Contents CHAPTER 12 Configuring Other Routing Protocols 12-1 Novell IPX 12-1 The Cisco Implementation of Novell IPX 12-1 IPX MIB Support 12-2 IPX Enhanced IGRP Support 12-2 LAN Support 12-3 VLAN Support 12-3 Multilayer Switching Support 12-3 IPX Configuration 12-3 IBM SNA 12-4 The Cisco Four-Phase Model for SNA-to-IP Integration 12-4 Phase One: SNA Centric 12-6 Phase Two: IP Transport 12-7 Phase Three: IP Client 12-8 Phase Four: IP Centric 12-9 Summary of Four-Phase Model 12-9 Scenarios for SNA-to-IP Int
Contents interface vlan A-3 Syntax A-3 Syntax Description A-3 Defaults A-3 Command Modes A-3 Usage Guidelines A-3 Example A-4 monitor session A-4 Syntax A-4 Syntax Description A-4 Defaults A-4 Command Modes A-5 Usage Guidelines A-5 Examples A-5 spanning-tree A-6 Syntax A-6 Syntax Description A-6 Defaults A-6 Command Modes A-6 Usage Guidelines A-6 Example A-7 spanning-tree portfast A-7 Syntax A-7 Syntax Description A-7 Defaults A-8 Command Modes A-8 Usage Guidelines A-8 Example A-8 Catalyst 4224 Access Gat
Contents switchport access A-8 Syntax A-9 Syntax Description A-9 Defaults A-9 Command Modes A-9 Usage Guidelines A-9 Example A-9 switchport voice vlan A-10 Syntax A-10 Syntax Description A-10 Defaults A-11 Command Modes A-11 Usage Guidelines A-11 Example A-11 APPENDIX B Synopsis of Basic VoIP Concepts B-1 VoIP Overview B-1 A Voice Primer B-2 How VoIP Processes a Typical Telephone Call B-2 Numbering Scheme B-3 Analog Versus Digital B-3 codecs B-4 Mean Opinion Score B-4 Delay B-5 Jitter B-6 End-to-End Del
Contents APPENDIX C VoIP Configuration Examples C-1 FXS-to-FXS Connection Using RSVP C-1 Configuration for Catalyst 4224 RLB-1 C-3 Configuration for Catalyst 4224 RLB-w C-4 Configuration for Catalyst 4224 RLB-e C-5 Configuration for Catalyst 4224 RLB-2 C-6 Linking PBX Users with E&M Trunk Lines C-7 Router San Jose Configuration C-8 Router Salt Lake City Configuration C-9 FXO Gateway to PSTN C-10 Router San Jose Configuration C-11 Router Salt Lake City Configuration C-11 FXO Gateway to PSTN (PLAR Mode) C-
Preface This preface contains these sections: • Objectives, page xvii • Audience, page xviii • Organization, page xviii • Related Documentation, page xix • Conventions, page xx • Obtaining Documentation, page xxi • Obtaining Technical Assistance, page xxiii Objectives This guide explains how to configure basic commands and scenarios for Ethernet switching, IP WAN routing, Voice over IP (VoIP), and IP telephony on the Catalyst 4224 Access Gateway Switch.
Preface Audience Audience This guide is intended for network administrators, engineers, and managers who need to understand the Catalyst 4224 system or configure the software. It is also intended for Cisco customer service representatives and system engineers. Organization This guide contains the following chapters: Title Description Chapter 1 Product Overview Provides an overview of the Catalyst 4224 Access Gateway Switch software features.
Preface Related Documentation Title Description Chapter 10 Traffic Shaping Describes different types of traffic shaping and provides pointers to configuration and command information. Chapter 11 Configuring Encryption Services Describes how to configure encryption services. Chapter 12 Configuring Other Routing Protocols Describes how to configure the Novell Internetwork Packet Exchange (IPX) and IBM Systems Network Architecture (SNA) routing protocols.
Preface Conventions Conventions This guide uses the following conventions: Convention Description boldface font Commands and keywords are in boldface. italic font Arguments for which you supply values are in italics. [ ] Elements in square brackets are optional. {x|y|z} Alternative keywords are grouped in braces and separated by vertical bars. [x|y|z] Optional alternative keywords are grouped in brackets and separated by vertical bars. string A nonquoted set of characters.
Preface Obtaining Documentation Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data. Obtaining Documentation Cisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems. Cisco.com You can access the most current Cisco documentation on the World Wide Web at this URL: http://www.cisco.com/univercd/home/home.
Preface Obtaining Documentation Ordering Documentation You can find instructions for ordering documentation at this URL: http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm You can order Cisco documentation in these ways: • Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace: http://www.cisco.com/en/US/partner/ordering/index.shtml • Registered Cisco.
Preface Obtaining Technical Assistance Obtaining Technical Assistance Cisco provides Cisco.com, which includes the Cisco Technical Assistance Center (TAC) Website, as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from the Cisco TAC website. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC website, including TAC tools and utilities. Cisco.com Cisco.
Preface Obtaining Technical Assistance We categorize Cisco TAC inquiries according to urgency: • Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration. • Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
Preface Obtaining Additional Publications and Information Cisco TAC Escalation Center The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case. To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL: http://www.
Preface Obtaining Additional Publications and Information • Packet magazine is the Cisco monthly periodical that provides industry professionals with the latest information about the field of networking. You can access Packet magazine at this URL: http://www.cisco.com/en/US/about/ac123/ac114/about_cisco_packet_maga zine.html • iQ Magazine is the Cisco monthly periodical that provides business leaders and decision makers with the latest information about the networking industry.
C H A P T E R 1 Product Overview The Cisco Catalyst 4224 Access Gateway Switch (Catalyst 4224) is an integrated switch/router that provides Voice-over-IP (VoIP) gateway and IP telephony services to a small branch office. This section provides an overview of the Catalyst 4224.
Chapter 1 Product Overview Features Features The Catalyst 4224 supports the following features: • 24 10/100 Ethernet ports with inline power and quality of service (QoS) that connect IP telephony phones and PCs • An integrated eight-port Foreign Exchange Station (FXS) module that connects analog phones, fax machines, modems, key telephone systems (KTS) or voicemail systems for VoIP • Three modular slots that support up to six ports on a wide variety of cards and can provide connectivity to the publi
Chapter 1 Product Overview Solution Solution The Catalyst 4224 can be deployed as part of a centralized call processing network with a Cisco CallManager and Survivable Remote Site Telephony (SRST) software that provides Ethernet switching, IP routing, VoIP gateway, and IP telephony services for a small branch office. Centralized call processing allows network administrators to deploy and manage IP telephony applications at the corporate headquarters or the corporate data center.
Chapter 1 Product Overview Solution Figure 1-1 Centralized Call Processing Solution Catalyst 4224 IP A C VIC/WIC ISDN BU MFT-T1 IP IP Single T-1 access to each branch office IP V IP WAN 12 Channels voice/ 12 Channels data PSTN 55335 B In the diagram, a Cisco CallManager cluster at a central site uses Simple Client Control Protocol (SCCP) to control IP phones at two branch offices. In the branch VoIP network, a Catalyst 4224 acts as an H.
Chapter 1 Product Overview IP Telephony IP Telephony The term IP telephony identifies a networking solution that integrates a switched LAN, the Cisco CallManager, and IP phones. The Catalyst 4224 is designed to work as part of a centralized Cisco CallManager network that supports up to 24 remote users.
Chapter 1 Product Overview VoIP Gateway • Protocol Independent Multicast (PIM) and Internet Group Management Protocol (IGMP) snooping • Per-port broadcast, multicast, and unicast storm control that prevents faulty end stations from degrading overall system performance • Inline 48-volt DC power • MAC-based port-level security to prevent unauthorized stations from accessing the switch Survivable Remote Site Telephony As enterprises extend IP telephony from central sites to remote offices, it is imp
Chapter 1 Product Overview IP Routing and WAN Features Table 1-1 describes the voice interface cards supported by the Catalyst 4224.
Chapter 1 Product Overview IP Routing and WAN Features • Asynchronous start-stop on ASCII • Synchronous PPP The Catalyst 4224 supports the following IP routing features: • A high-performance MPC8260 processor running at 200 MHz provides the processing power required for delivering voice, streaming video, and data to the branch office • Packet-processing capabilities of 35,000 pps at 64-byte Layer 3 • Onboard hardware encryption provides up to 10 times the performance of software-only encryption
Chapter 1 Product Overview IP Routing and WAN Features Quality of Service The Catalyst 4224 provides the performance and intelligent services of Cisco IOS software for branch office applications. The Catalyst 4224 can identify user applications—such as voice or multicast video—and classify traffic with the appropriate priority levels. Quality of service (QoS) policies are enforced using Layer 2 and 3 information such as 802.1p and IP precedence.
Chapter 1 Product Overview Application Notes Note DES and 3DES software is controlled by U.S. export regulations on encryption products. For additional details visit the following URL: http://www.cisco.
Chapter 1 Product Overview Application Notes • DSP subsystem—Interfaces to the TDM subsystem and CPU subsystem for converting voice streams to IP packets • Power subsystem—Provides power to the Catalyst 4224 and inline power to the IP phones that connect to the 10/100 Ethernet ports From a logical view, the Catalyst 4224 looks like a router that connects an Ethernet switch and a TDM switch in one system. Figure 1-2 shows a logical view of the Catalyst 4224.
Chapter 1 Product Overview Application Notes The DSPs compress and decompress packets based on codecs. The Catalyst 4224 supports the following codecs: • G.711 a-law 64 Kbps • G.711 mu-law 64 Kbps • G.729 abr 8 Annex-A & B 8 Kbps • G.729 ar8 G729 Annex-A 8 Kbps • G 729 r8 G729 8 Kbps The number of DSP channels that you can use depends upon the VIC configuration.
Chapter 1 Product Overview Application Notes • The two-Port FXS and FXO VIC uses two of the available four DSO channels. The DSP is used when the VIC is plugged in, even if the ports are not configured. • The eight-Port FXS Module uses eight DS0 channels or two DSPs, even if it is not used (unless it is disabled using the CLI).
Chapter 1 Product Overview Application Notes InterVLAN Routing The forwarding performance for interVLAN routing on the Catalyst 4224 is 35 Kpps for 64-byte packets. Fast Switching is the default switching path. The Catalyst 4224 supports Cisco Express Forwarding (CEF). Quality of Service The Catalyst 4224 can function as a Layer 2 switch connected to a Layer 3 router.
Chapter 1 Product Overview Application Notes a CoS/ToS of 3 are placed into the highest priority Queues. If the queue has no packets to be serviced, it will be skipped. WRED is not supported on the Fast Ethernet ports. The WRR default values cannot be changed. There are currently no CLI commands to determine QoS information for WRR weights and queue mappings. You cannot configure port-based QoS on the Layer 2 switch ports.
Chapter 1 Product Overview Application Notes Similar to other voice-enabled Catalyst platforms, the Catalyst 4224 learns that an IP phone is attached to the port via the CDP message exchange. Layer 3 QoS You can configure QoS on the Layer 3 CPU from the CLI, which is very similar to the interface on the Cisco 1750, Cisco 2600 series, and Cisco 3600 series routers. WAN QoS Queuing and Scheduling The Catalyst 4224 supports WAN QoS queuing and scheduling.
Chapter 1 Product Overview Application Notes – Differentiated services code point (DSCP) marking – IP Precedence – L2 Marking – L2 Matching – Match RTP – Network-based Application Recognition (NBAR) – Policy-based Routing (PBR) – QoS Preclassification for tunnels • Congestion Avoidance: – Flow-based RED (FRED) – Weighted RED (WRED) – WRED with DSCP • Policing and Traffic Shaping: – Class-based policing – Class-based shaping – IP Precedence – Frame Relay Traffic Shaping (FRTS) – General Traffic Shaping
Chapter 1 Product Overview Configuration Guidelines Configuration Guidelines This section provides platform specific guidelines for configuring the Catalyst 4224.
Chapter 1 Product Overview Configuration Guidelines Separate VLAN for Voice and Data Unlike the Catalyst 3500, you do not need to preconfigure VLANs with a VLAN database command. To be consistent with Cisco IP Telephony QoS design guidelines, you should configure a separate VLAN for voice and data. The following example shows a recommended configuration.
Chapter 1 Product Overview Configuration Guidelines InterVLAN and WAN Routing Configuration Configuring interVLAN routing on the Catalyst 4224 is identical to configuring interVLAN routing on the Catalyst 6000 with an MSFC. Configuring an interface for WAN routing is consistent with other Cisco IOS platforms. The following sample shows a configuration for interVLAN routing. interface Vlan 160 description Voice VLAN ip address 10.6.1.1 255.255.255.0 interface Vlan 60 description Data VLAN ip address 10.
Chapter 1 Product Overview Configuration Guidelines DHCP pool configuration commands: client-identifier Client identifier client-name Client name default-router Default routers dns-server DNS servers domain-name Domain name hardware-address Client hardware address host Client IP address and mask option Raw DHCP options C4224_SF(dhcp-config)# option 150 ip ? Hostname or A.B.C.D Note Server's name or IP address DHCP option 150 is supported locally.
Chapter 1 Product Overview Recommended Configurations Interface Range Command Support You can use the range command. The following sample configuration shows how to configure the range command: C4224_SF(config)# int range fas5/2 - 5 switchport access vlan 60 switchport voice vlan 160 Switched Port Analyzer (SPAN) Switched Port Analyzer (SPAN), also known as port monitoring, is supported for up to two sessions. Spanning a VLAN is not supported. You can only span selected interfaces.
Chapter 1 Product Overview Recommended Configurations • Maximum Number of VLAN and Multicast Groups, page 1-29 • IP Multicast Support, page 1-29 No VTP or DTP Support Using the interface switchport access or switchport trunk VLAN commands automatically creates a voice VLAN and data VLAN. If you require an additional VLAN beyond the voice and data VLAN when connecting to another switch, you must add it manually using the VLAN database command from the EXEC prompt.
Chapter 1 Product Overview Recommended Configurations Trunking The Catalyst 4224 supports only dot1Q trunking. Dynamic Trunking Protocol (DTP) is not supported. A Catalyst switch that is trunked to the Catalyst 4224 must have the trunking mode set to either On or No negotiate and type dot1q. Fractional PRI Configuration The maximum of 16 channels are available for trunk voice ports. This can cause a problem when a PSTN or PBX uses an unavailable channel to send a call to the Catalyst 4224.
Chapter 1 Product Overview Recommended Configurations Step 4 Busy-out the time slots for which DSP resources could not be allocated. The following sample configuration shows how to busy-out the time slots: isdn service dsl 0 b_channel 17-24 state 2 Step 5 Use the show isdn service command to ensure that the channel is out-of-service.
Chapter 1 Product Overview Recommended Configurations progress_ind alert enable 8 port 3/1:23 forward-digits all Note alert enable 8 is a hidden command option, which you cannot find by using the ? at the CLI. The following sample configuration shows what happens when you try to find this command option: C4224-2(config-dial-peer)# progress_ind alert ? % Unrecognized command This ringback situation applies only to PRI. It does not apply to BRI. MTP Required on Cisco CallManager Prior to support for H.
Chapter 1 Product Overview Recommended Configurations With the MTP Required checkbox enabled: The Catalyst 4224 is 10.253.1.1 Transcoder is Catalyst 6000 at Central : 10.1.1.11 C4224_SF# sh ip sock Proto Remote OutputIF 17 10.1.1.11 Port Local Port 16541 10.253.1.1 18757 In Out Stat TTY 0 0 1 0 With the MTP Required checkbox not enabled: IP Phone is 10.6.1.4 C4224_SF# sh ip sock Proto Remote OutputIF 17 10.6.1.4 Port Local Port 26287 10.253.1.
Chapter 1 Product Overview Recommended Configurations Port Fast Not Enabled on Trunk Ports You should configure ports as switched access ports. However, there may be implementations where your requirements dictate configuring ports as trunks and you want to standardize this configuration across all 24 ports. This is not the recommended configuration. Because of DHCP request timeouts on Windows 95/NT, portfast may be a desirable feature. However, portfast is not supported on ports in trunking mode.
Chapter 1 Product Overview Recommended Configurations frame-relay fragment 320 frame-relay ip rtp priority 16384 16383 170 Step 2 Apply the map class to a frame relay sub interface. The following sample configuration shows how to apply the map class: interface Serial0/0.300 point-to-point ip address 1.1.1.1 frame-relay interface-dlci 300 frame-relay class VOIP_256 Step 3 Apply frame relay shaping at the main interface.
Chapter 1 Product Overview Recommended Configurations Catalyst 4224 Access Gateway Switch Software Configuration Guide 1-30 OL-2031-02
C H A P T E R 2 Configuring for the First Time This section describes the initial steps of configuring the Catalyst 4224 and outlines the features of the Cisco IOS command line interface (CLI). Use this tool when you configure Catalyst 4224 interfaces.
Chapter 2 Configuring for the First Time First-Time Configuration Booting the Catalyst 4224 The factory configures the Catalyst 4224 to automatically load a Cisco IOS image. The software configuration register in the Catalyst 4224 determines where to find the image. The factory sets this register to load the Cisco IOS image into boot flash memory from configuration register 0x0101. This register enables autoboot at register 0x0103. Table 2-1 shows the Catalyst 4224 default configuration.
Chapter 2 Configuring for the First Time First-Time Configuration Connecting a Terminal To connect a terminal to the console port using the cable and adapters provided with the Catalyst 4224, connect to the port using the RJ-45-to-RJ-45 cable and RJ-45-to-DB-25 DTE adapter or RJ-45-to-DB-9 DTE adapter (labeled Terminal). Check the documentation that came with your terminal to determine the baud rate. The baud rate of the terminal must match the default baud rate (9600 baud) of the console port.
Chapter 2 Configuring for the First Time First-Time Configuration If the selected network management IP address is removed or the interface or subinterface associated with this IP address is shut down, the Catalyst 4224 selects another IP address as a replacement. If all the interfaces are down or no IP address has been assigned to any interface or subinterface that is running, the IP address for network management is 0.0.0.0.
Chapter 2 Configuring for the First Time Using the Cisco IOS CLI Figure 2-1 Catalyst 4224 Front Panel 10/100 Ethernet (slot 5) CATALYST 4224 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 CONSOLE 0 1 2 3 4 5 6 7 VIC 3 VWIC 2 VWIC 1 HDA STATUS STATUS PS RPS ACCESS GATEWAY SWITCH Status LED Switch utilization VWIC (slots 1 and 2) 10/100 Mgt port 55803 WS-U4604-8FXS 8-Port RJ21 FXS (slot 4) VIC (slot 3) Using the Cisco IOS CLI Cisco voice gateways
Chapter 2 Configuring for the First Time Using the Cisco IOS CLI Getting Help Use the question mark (?) and arrow keys to help you enter commands, as follows: • For a list of available commands, enter a question mark, for example: Gateway> ? • To complete a command, enter a few known characters followed by a question mark (with no space), for example: Gateway> s? • For a list of command variables, enter the command followed by a space and a question mark, for example: Gateway> show ? • To redispla
Chapter 2 Configuring for the First Time Using the Cisco IOS CLI Table 2-2 Common Command Modes (continued) Command Mode Access Method Global configuration From the privileged EXEC mode, enter the configure terminal command. Gateway Prompt Displayed hostname (config)# The default is Exit Method To exit to privileged EXEC mode, use the exit or end command, or press Ctrl-Z.
Chapter 2 Configuring for the First Time Using the Cisco IOS CLI In the following example, which uses the default prompt (router>), notice how the prompt changes after each command to indicate a new command mode: router> enable Password: router# configure terminal router(config-if)# line 0 router(config-line)# controller t1 1/0 router(config-controller)# exit router(config)# exit router# %SYS-5-CONFIG_I: Configured from console by console The last message is normal and does not indicat
C H A P T E R 3 Configuring Ethernet Switching This section describes the Ethernet switching capabilities of the Catalyst 4224. These capabilities are designed to work as part of the Cisco IP Telephony solution. This section also outlines how to configure Ethernet ports on the Catalyst 4224 to support IP phones in a branch office on your network.
Chapter 3 Configuring Ethernet Switching Configuring the Catalyst 4224 for Cisco IP Telephony Default Switch Configuration By default, the Catalyst 4224 provides the following settings with respect to Cisco IP Telephony: • All switch ports are in access VLAN 1. • All switch ports are static access ports, not 802.1Q trunk ports. • Default voice VLAN is not configured on the switch. • Inline power is automatically supplied on the 10/100 ports.
Chapter 3 Configuring Ethernet Switching Configuring Ethernet Ports to Support IP Phones and a Daisy-Chained Workstation For more information about Option 3, which entails the Cisco IP SoftPhone application, see the Cisco IP SoftPhone documentation library. The Cisco IP SoftPhone application was developed to provide clients with a phone that runs on software. This application can be installed on any PC that connects to an IP telephony network.
Chapter 3 Configuring Ethernet Ports to Support IP Phones and a Daisy-Chained Workstation Note Configuring Ethernet Switching In the following configurations, the powerinline command is set to auto by default. Configuring Separate Voice and Data Subnets For ease of network administration and increased scalability, network managers can configure the Catalyst 4224 to support Cisco IP phones such that the voice and data traffic reside on separate subnets.
Chapter 3 Configuring Ethernet Switching Configuring Ethernet Ports to Support IP Phones and a Daisy-Chained Workstation Step 3 Task Command Enter the privileged EXEC mode. A preset password may be required to enter this mode. enable Enter global configuration mode. configure terminal Enter the interface configuration mode and the port to be configured (for example, interface fa5/1). interface interface Configure the port as access and assign a data VLAN.
Chapter 3 Configuring Ethernet Ports to Support IP Phones and a Daisy-Chained Workstation Configuring Ethernet Switching Sample Configuration 1 The following example shows how to configure separate subnets for voice and data on the Catalyst 4224: interface FastEthernet5/1 description DOT1Q port to IP Phone switchport access vlan 50 switchport voice vlan 150 spanning-tree portfast (See Note below) interface Vlan 150 description voice vlan ip address 10.150.1.1 255.255.255.0 ip helper-address 172.20.73.
Chapter 3 Configuring Ethernet Switching Configuring Ethernet Ports to Support IP Phones and a Daisy-Chained Workstation The following example provides a sample configuration: interface Vlan 160 description voice vlan ip address 10.6.1.1 255.255.255.0 interface Vlan 60 description data vlan ip address 10.60.1.1 255.255.255.0 interface Serial1/0 ip address 160.3.1.2 255.255.255.
Chapter 3 Configuring Ethernet Ports to Support IP Phones and a Daisy-Chained Workstation Configuring Ethernet Switching This configuration approach must address two key considerations: • Network managers should ensure that existing subnets have enough available IP addresses for the new Cisco IP phones, each of which requires a unique IP address. • Administering a network with a mix of IP phones and workstations on the same subnet might pose a challenge.
Chapter 3 Configuring Ethernet Switching Configuring Ethernet Ports to Support IP Phones with Multiple Ports Sample Configuration The Catalyst 4224 supports the use of an 802.1p-only option when configuring the voice VLAN. Use this option to allow the IP phone to tag VoIP packets with a CoS of 5 on the native VLAN, while all PC data traffic is sent untagged.
Chapter 3 Configuring Ethernet Switching Managing the Catalyst 4224 Access Gateway Switch Sample Configuration The following example illustrates the configuration on the IP phone: interface FastEthernetx/x switchport voice vlan x The following example illustrates the configuration on the PC: interface FastEthernetx/y switchport access vlan y Note Using a separate subnet, and possibly a separate IP address space, may not be an option for some small branch offices due to the IP routing configuration.
Chapter 3 Configuring Ethernet Switching Managing the Catalyst 4224 Access Gateway Switch Adding Trap Managers A trap manager is a management station that receives and processes traps. When you configure a trap manager, community strings for each member switch must be unique. If a member switch has an assigned IP address, the management station accesses the switch by using its assigned IP address. By default, no trap manager is defined, and no traps are issued.
Chapter 3 Configuring Ethernet Switching Managing the Catalyst 4224 Access Gateway Switch gateway addresses. In addition, the switch must be able to access the BOOTP server through one of its ports. At startup, a switch without an IP address requests the information from the BOOTP server; the requested information is saved in the switch running the configuration file.
Chapter 3 Configuring Ethernet Switching Managing the Catalyst 4224 Access Gateway Switch Removing an IP Address Use the following procedure to remove IP information from a switch. Note Using the no ip address command in configuration mode disables the IP protocol stack and removes the IP information. Cluster members without IP addresses rely on the IP protocol stack being enabled.
Chapter 3 Configuring Ethernet Switching Managing the Catalyst 4224 Access Gateway Switch IP defines a hierarchical naming scheme that allows a device to be identified by its location or domain. Domain names are pieced together with periods (.) as the delimiting characters. For example, Cisco Systems is a commercial organization that IP identifies by a com domain name, so its domain name is cisco.com. A specific device in this domain, such as the File Transfer Protocol (FTP) system, is identified as ftp.
Chapter 3 Configuring Ethernet Switching Managing the Catalyst 4224 Access Gateway Switch Because the sound quality of an IP telephone call can deteriorate if the data is unevenly transmitted, the current release of the Cisco IOS software supports Quality of Service (QoS) based on IEEE 802.1p Class of Service (CoS). QoS uses classification and scheduling to transmit network traffic from the switch in a predictable manner. The Cisco 7960 IP Phone contains an integrated three-port 10/100 switch.
Chapter 3 Configuring Ethernet Switching Managing the Catalyst 4224 Access Gateway Switch A detection mechanism on the Catalyst 4224 determines whether it is connected to a Cisco 7960 IP Phone. If the switch senses that there is no power on the circuit, the switch supplies the power. If there is power on the circuit, the switch does not supply it. You can configure the switch to never supply power to the Cisco 7960 IP Phone and to disable the detection mechanism.
Chapter 3 Configuring Ethernet Switching Managing the Catalyst 4224 Access Gateway Switch Enabling the Switch Port Analyzer Beginning in privileged EXEC mode, follow these steps to enable SPAN: Task Command Step 1 Enter global configuration mode. configure terminal Step 2 Enable port monitoring for a specific session (“number”). Optionally, supply a SPAN destination interface, and a source interface monitor session number destination source Step 3 Return to privileged EXEC mode.
Chapter 3 Configuring Ethernet Switching Managing the Catalyst 4224 Access Gateway Switch The Address Resolution Protocol (ARP) associates a host IP address with corresponding media or MAC addresses and VLAN ID. Taking an IP address as input, ARP determines the associated MAC address. Once a MAC address is determined, the IP-MAC address association is stored in an ARP cache for rapid retrieval. Then, the IP datagram is encapsulated in a link-layer frame and sent over the network.
Chapter 3 Configuring Ethernet Switching Managing the Catalyst 4224 Access Gateway Switch Figure 3-3 Contents of the Address Table MAC Addresses and VLANs All MAC addresses are associated with one or more VLANs. An address can exist in more than one VLAN and have different destinations in each. Multicast addresses, for example, could be forwarded to port 1 in VLAN 1 and ports 9, 10, and 11 in VLAN 5. Each VLAN maintains its own logical address table.
Chapter 3 Configuring Ethernet Switching Managing the Catalyst 4224 Access Gateway Switch Beginning in privileged EXEC mode, follow these steps to configure the dynamic address table aging time. Task Command Step 1 Enter global configuration mode. configure terminal Step 2 Enter the number of seconds that dynamic addresses are to be retained in the address table. You can enter a number from 10 to 1000000. mac-address-table aging-time seconds Step 3 Return to privileged EXEC mode.
Chapter 3 Configuring Ethernet Switching Managing the Catalyst 4224 Access Gateway Switch You can enter a secure port address even when the port does not yet belong to a VLAN. When the port is later assigned to a VLAN, packets destined for that address are forwarded to the port. Adding Secure Addresses Beginning in privileged EXEC mode, follow these steps to add a secure address: Task Command Step 1 Enter global configuration mode.
Chapter 3 Configuring Ethernet Switching Managing the Catalyst 4224 Access Gateway Switch Adding and Removing Static Addresses A static address has the following characteristics: • It is manually entered in the address table and must be manually removed. • It can be a unicast or multicast address. • It does not age and is retained when the switch restarts.
Chapter 3 Configuring Ethernet Switching Managing the Catalyst 4224 Access Gateway Switch Removing Static Addresses Beginning in privileged EXEC mode, follow these steps to remove a static address: Task Command Step 1 Enter global configuration mode. configure terminal Step 2 Enter the static MAC address, the interface, and the VLAN ID of the port to be removed no mac-address-table static hw-addr [interface] interface [vlan] vlan-id Step 3 Return to privileged EXEC mode.
Chapter 3 Configuring Ethernet Switching Managing the Catalyst 4224 Access Gateway Switch Catalyst 4224 Access Gateway Switch Software Configuration Guide 3-24 OL-2031-02
C H A P T E R 4 Configuring the Data Interfaces This section describes how to configure the data interfaces on the Catalyst 4224 To configure a data interface, you must use configuration mode. In this mode, you enter Cisco IOS command-line interface (CLI) commands at the gateway prompt.
Chapter 4 Configuring the Data Interfaces Configuring the Host Name and Password Configuring the Host Name and Password One of your first configuration tasks is to configure the host name and set an encrypted password. Configuring a host name allows you to distinguish multiple Catalyst 4224s. Setting an encrypted password allows you to prevent unauthorized configuration changes. To configure the host name and password, perform these tasks: Step 1 Task Command Enter enable mode.
Chapter 4 Configuring the Data Interfaces Configuring the Host Name and Password Task Command Step 6 Enter exec-timeout 0 0 to prevent the Catalyst 4224’s EXEC facility from timing out if you do not type any information on the console screen for an extended period. gwy1(config-line)# exec-timeout 0 0 Step 7 Exit to global configuration mode.
Chapter 4 Configuring the Data Interfaces Configuring the Fast Ethernet Interface Step 2 Exit global configuration mode and attempt to reenter it using the new enable password: gwy1# exit . . . gwy1 con0 is now available Press RETURN to get started. gwy1> enable Password: guessme gwy1# Tip If you are having trouble, ensure that the Caps Lock function is off; passwords are case sensitive.
Chapter 4 Configuring the Data Interfaces Configuring the Fast Ethernet Interface To configure the Fast Ethernet interface, follow these steps: Step 1 Task Command Enter enable mode. gateway> enable Enter the password. Password: You know you have entered enable mode when the prompt changes to gateway#. Step 2 Enter global configuration mode. You know you have entered global configuration mode when the prompt changes to gateway(config)#.
Chapter 4 Configuring the Data Interfaces Configuring Asynchronous/Synchronous Serial Interfaces Configuring Asynchronous/Synchronous Serial Interfaces This section describes how to configure the serial interfaces on your asynchronous/synchronous serial WIC. Note Timesaver The asynchronous/synchronous serial WIC supports synchronous mode only. At this time, asynchronous mode is not supported.
Chapter 4 Configuring the Data Interfaces Configuring Asynchronous/Synchronous Serial Interfaces Step 4 Task Command Enter the interface configuration mode. gateway(config)# interface serial 1/0 You know you have entered interface configuration mode when the prompt changes to gateway(config-if)#. Step 5 Assign the IP address and subnet mask to the interface. Note Step 6 Step 7 All serial ports are initially configured as synchronous. gateway(config-if)# gateway(config-if)# ip address 172.16.74.
Chapter 4 Configuring the Data Interfaces Configuring Asynchronous/Synchronous Serial Interfaces Step 10 Task Command Exit back to global configuration mode. gateway(config-if)# exit If your Catalyst 4224 has more that one serial interface that you need to configure, repeat Step 4 through Step 9. Step 11 When you finish configuring the interface, return to enable mode. gateway(config)# Ctrl-z gateway# Table 4-1 lists the half-duplex timer commands.
Chapter 4 Configuring the Data Interfaces Configuring ISDN BRI Interfaces • 14400 bps • 19200 bps • 28800 bps • 32000 bps • 38400 bps • 56000 bps • 57600 bps • 64000 bps • 72000 bps • 115200 bps • 125000 bps • 128000 bps Configuring ISDN BRI Interfaces This section describes how to configure the interfaces on the basic rate interface (BRI) card of your Catalyst 4224.
Chapter 4 Configuring the Data Interfaces Configuring ISDN BRI Interfaces To configure ISDN BRI interfaces, perform the following steps: Step 1 Step 2 Task Command Enter enable mode. gateway> enable Enter the password. Password: You know you have entered enable mode when the prompt changes to gateway#. gateway# Enter global configuration mode. gateway# configure terminal You know you have entered global configuration mode when the prompt changes to gateway(config)#.
Chapter 4 Configuring the Data Interfaces Configuring ISDN BRI Interfaces Task Command Step 9 By default, the Catalyst 4224 allocates 25 percent of DRAM to shared memory (used for data transmitted (or received) by WAN interface cards). Specifying memory-size iomem 40 increases shared memory from 25 percent to 40 percent. gateway(config)# memory-size iomem 40 Step 10 When you finish configuring the interface, return to enable mode.
Chapter 4 Configuring the Data Interfaces Configuring T1 and E1 Interfaces Configuring T1 and E1 Interfaces This section describes how to configure a T1/E1 multiflex trunk interface on your Catalyst 4224. It describes a basic configuration, including how to enable the interface and to specify IP routing. Depending on your own requirements and the protocols you plan to route, you might also need to enter other configuration commands.
Chapter 4 Configuring the Data Interfaces Configuring T1 and E1 Interfaces Step 5 Task Command Enter controller configuration mode for the CT1/PRI interface at the specified slot/port location. gateway(config)# controller t1 1/0 This example configures a T1 interface in slot 1 and unit 0. Step 6 Specify which end of the circuit provides clocking.
Chapter 4 Configuring the Data Interfaces Configuring T1 and E1 Interfaces Step 5 Task Command Enter controller configuration mode for the CT1/PRI interface at the specified slot/port location. gateway(config)# controller t1 1/0 This example configures a T1 interface in slot 1 and unit 0. Step 6 Specify which end of the circuit provides clocking.
Chapter 4 Configuring the Data Interfaces Configuring T1 and E1 Interfaces Step 9 Task Command Specify the channel group and time slots to be mapped. gateway(config-controller)# channel-group 0 timeslots 1,3-5,7 When configuring a T1 data line, channel-group numbers can be values from 0 to 23. Time slots are assigned to channels. One or more time slots or ranges of time slots belong to the channel group. The first time slot is numbered 1. For a T1 controller, the time slot range is from 1 to 24.
Chapter 4 Configuring the Data Interfaces Configuring T1 and E1 Interfaces Configuring E1 Interfaces To configure a new E1 interface (balanced or unbalanced) or to change the configuration of an existing interface, perform these steps: Step 1 Step 2 Task Command Enter enable mode. gateway> enable Enter the password. Password: You know you have entered enable mode when the prompt changes to gateway#. gateway# Enter global configuration mode.
Chapter 4 Configuring the Data Interfaces Configuring T1 and E1 Interfaces Step 8 Task Command Specify the channel group and time slots to be mapped. gateway(config-controller)# channel-group 0 timeslots 1,3-5,7 When configuring a E1 data line, channel-group numbers can be values from 0 to 30. Time slots are assigned to channels. One or more time slots or ranges of time slots belong to the channel group. The first time slot is numbered 1. For an E1 controller, the time slot range is from 1 to 31.
Chapter 4 Configuring the Data Interfaces Checking the Interface Configuration Checking the Interface Configuration After configuring the new interface, you can perform the following tests to verify that the new interface is operating correctly: • Display the Catalyst 4224 hardware configuration with the show version command. Check that the list includes the new interface.
Chapter 4 Configuring the Data Interfaces Saving Configuration Changes Saving Configuration Changes To prevent the loss of the Catalyst 4224 configuration, you need to save it to NVRAM. To save configuration changes, perform these steps: Task Command Step 1 Enter enable mode. gateway> enable Enter the password. Password: password You know you have entered enable mode when the prompt changes to gateway#.
Chapter 4 Configuring the Data Interfaces Saving Configuration Changes Catalyst 4224 Access Gateway Switch Software Configuration Guide 4-20 OL-2031-02
C H A P T E R 5 Configuring the Voice Interfaces This section explains how to configure Voice-over-IP (VoIP) routing on the supported interface cards of your Catalyst 4224 Access Gateway Switch. (You need to perform the software configuration only for the cards that you have installed.) To configure a voice interface, you must use configuration mode. In this mode, you enter Cisco IOS command-line interface (CLI) commands at the Gateway prompt.
Chapter 5 Configuring the Voice Interfaces Configuring Voice Interfaces When you start a Catalyst 4224, it automatically detects the voice network modules and VICs that have been installed. The first time you use a Catalyst 4224, you need to configure each voice port that you want to enable. If you replace a card after you configure each port, the gateway will recognize the new hardware component and use the previous configuration settings.
Chapter 5 Configuring the Voice Interfaces MGCP Configuration Step 7 To see the current operating configuration, including any changes you just made, enter the show running-config command: c4224# show running-config To see the configuration currently stored in non-volatile random access memory (NVRAM), enter the show startup-config command at the enable prompt: c4224# show startup-config Step 8 The results of the show running-config and show startup-config commands differ from each other if you have c
Chapter 5 Configuring the Voice Interfaces MGCP Configuration • Configuring T1-CAS E&M Emulation, page 5-8 • T1/E1 Configuration (H.323), page 5-31 • Where to Go Next, page 5-16 For more information on using MGCP with Cisco CallManager 3.0, refer to the Cisco CallManager 3.0 online help and to Configuring Cisco IP Telephony Gateways. Enabling MGCP To configure the Catalyst 4224 so that it can be controlled by Cisco CallManager Release 3.
Chapter 5 Configuring the Voice Interfaces MGCP Configuration Cisco CallManager controls dial-plan-related configuration elements, and they should not be configured in the Cisco voice gateway for MGCP-managed endpoints (those with application MGCPAPP in the dial-peer statement). You should not configure any of the following elements when using MGCP: Note • Destination pattern • Session target • Expansion numbers • Connection PLAR/tie-line/trunk (voice port) • codec H.
Chapter 5 Configuring the Voice Interfaces MGCP Configuration Table 5-1 Switchback Command Options Switchback Command Option Function graceful The default value. Completes all outstanding calls before returning the gateway to the control of the primary Cisco CallManager server. immediate Returns the gateway to the control of the primary Cisco CallManager server without delay, as soon as the network connection to the server is reestablished.
Chapter 5 Configuring the Voice Interfaces MGCP Configuration The switchover occurs immediately with a manual redirect. This command does not switch the gateway to the backup Cisco CallManager server if you have the switchback option set to immediate and the primary Cisco CallManager server is still running. To view the current configuration of a Cisco voice gateway, enter the show ccm-manager command from privileged EXEC mode.
Chapter 5 Configuring the Voice Interfaces MGCP Configuration Current state: Automatic Configuration Download feature is disabled Configuration Error History: FAX relay mode: cisco-fax-relay Configuring FXS and FXO Analog Ports You use the same commands to configure both Foreign Exchange Service (FXS) and Foreign Exchange Office (FXO) ports.
Chapter 5 Configuring the Voice Interfaces MGCP Configuration To configure T1-CAS E&M emulation with MGCP using Cisco CallManager Administrator, perform the following steps and configure the route pattern and dial plan: Step 1 Identify the port number and then enter the configuration information provided by your local carrier, as in the following example: Gateway(config)# controller Gateway(config-controller)# Gateway(config-controller)# Gateway(config-controller)# Step 2 T1 1/port# framing esf clock s
Chapter 5 Configuring the Voice Interfaces MGCP Configuration Step 3 Enable MGCP for the port by entering the following commands: Gateway(config)# dial-peer voice 1 pots Gateway(config-dial-peer)# application mgcpapp port portnumber:ds0group Replace portnumber with the port number on the voice gateway you are configuring and ds0group with the DS0 group number. Example 5-2 shows typical use of commands for configuring T-1 CAS E&M Emulation for MGCP.
Chapter 5 Configuring the Voice Interfaces MGCP Configuration b. Specify which end of the circuit provides clocking: Gateway(config-controller)# clock source line Set the clock source to use internal clocking only for testing the network. Set one end of the T1 line to internal. c. Specify the framing type: Gateway(config-controller)# framing esf d. Specify the line code format: Gateway(config-controller)# linecode b8zs Step 2 Configure parameters for the voice interface. a.
Chapter 5 Configuring the Voice Interfaces MGCP Configuration The ISDN lower layer information (Q.921 and below) is terminated and processed on the gateway. The Layer 3 information (Q.931 and above) is transported over TCP to the Cisco CallManager (MGCP call agent).
Chapter 5 Configuring the Voice Interfaces MGCP Configuration Sample Configuration The following example shows the overall configuration required to enable MGCP on a T1/PRI line: isdn switch-type primary-5ess controller T1 1/0 framing crc4 linecode hdb3 pri-group timeslots 1-24 service mgcp interface Serial1/0:23 no ip address no logging event link-status isdn switch-type primary-net5 isdn incoming-voice voice no cdp enable isdn bind-l3 ccm-manager dial-peer voice 1 pots application mgcpapp port 1/0:0 C
Chapter 5 Configuring the Voice Interfaces MGCP Configuration Step 2 Configure parameters for the voice interface. a. Specify the PRI group and time slots to be mapped: Gateway(config-controller)# pri-group timeslots 1-31 service mgcp b. Configure each PRI group as a virtual serial interface: Gateway(config-controller)# interface serial 1/0:15 c.
Chapter 5 Configuring the Voice Interfaces MGCP Configuration This command displays information about the status of the PRI backhaul link and the status of any PRI D channels in the gateway. The following example shows the type of information the system displays. Example 5-4 PRI Backhaul Status PRI Backhaul link info: Link Protocol: TCP Remote Port Number: 2428 Remote IP Address: 172.20.71.
Chapter 5 Configuring the Voice Interfaces H.323 Gateway Configuration Where to Go Next At this point, make sure that Cisco CallManager is properly configured to provision the voice gateway and to configure MGCP endpoints or H.323 route patterns as required. Refer to the documentation and online help provided with Cisco CallManager. Refer to the Cisco IOS software configuration guide and command reference publications for more advanced configuration topics.
Chapter 5 Configuring the Voice Interfaces H.323 Gateway Configuration Perform the following steps to complete H.323 configuration: Step 1 Identify the port number and enter line-specific information provided by your local carrier, as described in the following sections: • Configuring T1-CAS Analog Emulation (H.323), page 5-19 • ISDN BRI Configuration (H.323), page 5-24 • T1/E1 Configuration (H.323), page 5-31 • E&M Trunk Line Configuration (H.
Chapter 5 Configuring the Voice Interfaces H.323 Gateway Configuration Step 4 Configure H.323 endpoints connected to the Catalyst 4224 Ethernet port. To configure H.
Chapter 5 Configuring the Voice Interfaces Configuring T1-CAS Analog Emulation (H.323) The number of digits that you substitute for pattern plus the number of periods in the wildcard (...) must match the total number of digits configured for use by the Catalyst 4224 in Cisco CallManager Administration. Also, remember that the numbers that you substitute for pattern are removed by the Catalyst 4224.
Chapter 5 Configuring the Voice Interfaces Configuring T1-CAS Analog Emulation (H.323) Step 1 Identify the port number and then enter the configuration information provided by your telco, as in the following example: c4224(config)# controller c4224(config-controller)# c4224(config-controller)# c4224(config-controller)# Step 2 T1 1/port# framing esf clock source internal linecode b8zs Assign time slots to the DS-0 group and identify the emulation type.
Chapter 5 Configuring the Voice Interfaces Configuring T1-CAS Analog Emulation (H.323) You can configure DS-0 hunt groups by assigning a range of time slots to a DS-0 group, and then configuring multiple voice peers with the same destination pattern pointing to multiple voice ports.
Chapter 5 Configuring the Voice Interfaces Configuring T1-CAS Analog Emulation (H.323) endpoints on a Catalyst 4224. If you configure Cisco CallManager as an H.323 endpoint, you must use Cisco CallManager Administration to define the route patterns required to route calls to the Catalyst 4224. The following example illustrates how to configure a single DS-0 group. Repeat the relevant commands to configure additional groups.
Chapter 5 Configuring the Voice Interfaces Configuring T1-CAS Analog Emulation (H.323) FXO Emulation Example To use FXO emulation to connect the T1-CAS port to the PSTN, you must have Direct Inward Dialing (DID) enabled on incoming DS-0 groups. DID allows the gateway or Cisco CallManager to identify the extension to which each call on an incoming DS-0 group is directed. Because DID only works on incoming connections, you must have separate DS-0 groups allocated for incoming and outgoing calls.
Chapter 5 Configuring the Voice Interfaces ISDN BRI Configuration (H.323) calls to and from the PBX to which the gateway is connected. The commands required to make these changes are shown below (all the extensions on the PBX begin with the prefix 625): c4224(config-controller)# dso-group 0 timeslots 1 type e&m-immediate-start c4224(config)# dial-peer voice 1 pots c4224(config-dial-peer)# port 1/0:0 c4224(config-dial-peer)# destination-pattern 625.... ISDN BRI Configuration (H.
Chapter 5 Configuring the Voice Interfaces ISDN BRI Configuration (H.
Chapter 5 Configuring the Voice Interfaces ISDN BRI Configuration (H.323) Configuring ISDN BRI Lines Before using a Catalyst 4224 with an ISDN BRI interface, you must order a correctly configured ISDN BRI line from your local telecommunications service provider. The ordering process varies from provider to provider and from country to country; however, here are some general guidelines: • Ask for two channels to be called by one number.
Chapter 5 Configuring the Voice Interfaces ISDN BRI Configuration (H.323) Table 5-4 ISDN Provisioning by Switch Type Switch Type Provisioning 5ESS Custom BRI For voice only: • (Use these values only if you have an ISDN telephone connected.
Chapter 5 Configuring the Voice Interfaces ISDN BRI Configuration (H.
Chapter 5 Configuring the Voice Interfaces ISDN BRI Configuration (H.323) Defining ISDN Service Profile Identifiers Some service providers assign service profile identifiers (SPIDs) to define the services to which an ISDN device subscribes. If your service provider requires SPIDs, your ISDN device cannot place or receive calls until it sends a valid SPID to the service provider when initializing the connection.
Chapter 5 Configuring the Voice Interfaces ISDN BRI Configuration (H.323) In this example, a call comes in to Catalyst 4224 1 on the BRI port. The DID information allows the Catalyst 4224 to route the call based on the called number. If the called number is 2xxx, the call is routed to Catalyst 4224 2000; if the called number is 3xxx, the call is routed to Catalyst 4224 3000. Figure 5-1 illustrates the topology of this connection example. Figure 5-1 Configuring DID on a BRI Port Voice port 1/0/0 1.1.1.
Chapter 5 Configuring the Voice Interfaces T1/E1 Configuration (H.323) Gateway 2 Configuration dial-peer voice 1 pots port 1/0/0 destination-pattern 2000 T1/E1 Configuration (H.323) To configure an ISDN PRI interface or T1/E1 multiflex trunk interface on your Catalyst 4224, use configuration mode.
Chapter 5 Configuring the Voice Interfaces T1/E1 Configuration (H.323) b. Specify which end of the circuit provides clocking. c4224(config-controller)# clock source line The clock source should be set to use internal clocking only for testing the network or if the full T1 line is used as the channel group. Only one end of the T1 line should be set to internal. c. Specify the framing type. c4224(config-controller)# framing esf d. Specify the line code format.
Chapter 5 Configuring the Voice Interfaces T1/E1 Configuration (H.
Chapter 5 Configuring the Voice Interfaces T1/E1 Configuration (H.323) b. Configure each channel group as a virtual serial interface. c4224(config-controller)# interface serial 1/0:31 c.
Chapter 5 Configuring the Voice Interfaces E&M Trunk Line Configuration (H.323) E&M Trunk Line Configuration (H.323) The section illustrates how to configure VoIP to link PBX users with E&M trunk lines.
Chapter 5 Configuring the Voice Interfaces E&M Trunk Line Configuration (H.323) Linking PBX Users with E&M Trunk Lines 172.16.1.123 Dial peer 1 POTS Voice port 1/0/0 172.16.65.
Chapter 5 Configuring the Voice Interfaces E&M Trunk Line Configuration (H.323) Gateway San Jose Configuration hostname sanjose !Configure pots dial-peer 1 dial-peer voice 1 pots destination-pattern +527.... port 1/0/0 !Configure pots dial-peer 2 dial-peer voice 2 pots destination-pattern +527.... port 1/0/1 !Configure voip dial-peer 3 dial-peer voice 3 voip destination-pattern +569.... session target ipv4:172.16.65.
Chapter 5 Configuring the Voice Interfaces E&M Trunk Line Configuration (H.323) !Configure the E&M interface voice-port 1/0/0 signal immediate operation 4-wire type 2 voice-port 1/0/0 signal immediate operation 4-wire type 2 !Configure the serial interface interface serial 0/0 description serial interface type dte ip address 172.16.65.182 no shutdown Note The PBXs should be configured to pass all DTMF signals to the gateway. Cisco recommends that you do not configure “store-and-forward” tone.
C H A P T E R 6 Configuring VoIP The Catalyst 4224 Access Gateway Switch (Catalyst 4224) provides Voice-over-IP (VoIP) gateway applications for a micro branch office. This section provides comprehensive information on how to configure VoIP on your Catalyst 4224.
Chapter 6 Configuring VoIP Prerequisite Tasks Prerequisite Tasks Before you can configure your Catalyst 4224 to use VoIP, you need to perform the following tasks: • Establish a working IP network. For more information about configuring IP, refer to the “IP Overview,” “Configuring IP Addressing,” and “Configuring IP Services” sections in the Network Protocols Configuration Guide, Part 1 for Cisco IOS Release 12.0 T. • Install the voice interface cards (VICs) in your Catalyst 4224.
Chapter 6 Configuring VoIP Configuration Tasks Configuration Tasks To configure VoIP on your Catalyst 4224, perform the following steps: Step 1 Configure your IP network to support real-time voice traffic. See the “Configure IP Networks for Real-Time Voice Traffic” section on page 6-3 for information about selecting and configuring the appropriate quality of service (QoS) tool or tools to optimize voice traffic on your network.
Chapter 6 Configuring VoIP Configure IP Networks for Real-Time Voice Traffic weighted fair queuing), and IP precedence. To configure your IP network for real-time voice traffic, you need to consider the entire scope of your network and then select the appropriate QoS tool or tools. To improve voice network performance, QoS must be configured throughout your network, not just on your Catalyst 4224 running VoIP. Not all QoS techniques are appropriate for all network routers.
Chapter 6 Configuring VoIP Configure IP Networks for Real-Time Voice Traffic Configure RSVP for Voice Resource Reservation Protocol (RSVP) enables routers to reserve enough bandwidth on an interface to provide reliable, high-quality performance. RSVP allows end systems to request a particular QoS from the network. Real-time voice traffic requires network consistency. Without consistent QoS, real-time traffic can experience jitter, insufficient bandwidth, delay variations, or information loss.
Chapter 6 Configuring VoIP Configure IP Networks for Real-Time Voice Traffic This command starts RSVP and sets the bandwidth and single-flow limits. The default maximum bandwidth is up to 75 percent of the bandwidth available on the interface. By default, the amount reservable by a flow can be up to the entire reservable bandwidth. On subinterfaces, RSVP applies to the more restrictive of the available bandwidths of the physical interface and the subinterface.
Chapter 6 Configuring VoIP Configure IP Networks for Real-Time Voice Traffic Configure Multilink Point-to-Point Protocol with Interleaving Multiclass multilink Point-to-Point Protocol (PPP) interleaving allows large packets to be multilink-encapsulated and fragmented into smaller packets to satisfy the delay requirements of real-time voice traffic. Small real-time packets, which are not multilink-encapsulated, are transmitted between fragments of the large packets.
Chapter 6 Configuring VoIP Configure IP Networks for Real-Time Voice Traffic To configure multilink PPP and interleaving on a configured and operational interface or virtual interface template, use the following interface configuration commands: Note Task Command Step 1 Enable Multilink PPP. ppp multilink Step 2 Enable real-time packet interleaving. ppp multilink interleave Step 3 Optionally, configure a maximum fragment delay of up to 20 milliseconds.
Chapter 6 Configuring VoIP Configure IP Networks for Real-Time Voice Traffic Multilink PPP Configuration Example The following example defines a virtual interface template that enables multilink PPP with interleaving and a maximum real-time traffic delay of 20 milliseconds, and then applies that virtual template to the multilink PPP bundle: c4224(config)# interface virtual-template 1 c4224(config-if)# ppp multilink c4224(config-if)# encapsulated ppp c4224(config-if)# ppp multilink interleave c4224(config-
Chapter 6 Configuring VoIP Configure IP Networks for Real-Time Voice Traffic Figure 6-1 RTP Header Compression Before RTP header compression: 20 bytes IP 8 bytes 12 bytes UDP RTP Header Payload 20 to 160 bytes After RTP header compression: 2 to 4 bytes IP/UDP/RTP header 20 to 160 bytes 12076 Payload You should configure RTP header compression if the following conditions describe your network: Note • Links slower than two Mbps • Need to save bandwidth Do not use RTP header compression
Chapter 6 Configuring VoIP Configure IP Networks for Real-Time Voice Traffic Enable RTP Header Compression on a Serial Interface You need to enable compression on both ends of a serial connection. To enable RTP header compression, use the following interface configuration command: c4224(config-if)# ip rtp header-compression [ passive] If you include the passive keyword, the software compresses outgoing RTP packets only if incoming RTP packets on the same interface are compressed.
Chapter 6 Configuring VoIP Configure Number Expansion Custom queuing and other methods for identifying high-priority streams should be configured for these port ranges. For more information about custom queuing, refer to the “Managing System Performance” section in the Configuration Fundamentals Configuration Guide for Cisco IOS Release 12.0 T. Configure Weighted Fair Queuing Weighted fair queuing ensures that queues do not starve for bandwidth and that traffic gets predictable service.
Chapter 6 Configuring VoIP Configure Number Expansion Create a Number Expansion Table The example depicted in Figure 6-2 pertains to a small company that decides to use VoIP to integrate its telephony network with its existing IP network. The destination pattern (or expanded telephone number) associated with Catalyst 4224 1 (left of the IP cloud) is 408-555-xxxx, where xxxx identifies the individual dial peers by extension.
Chapter 6 Configuring VoIP Configure Number Expansion Table 6-1 Note Sample Number Expansion Table Extension Destination Pattern Num-Exp Command Entry 1... 14085551... num-exp 1... 14085551... Expands a four-digit extension beginning with the numeral 1 by prefixing 1408555 to the extension. 2... 17295552... num-exp 2... 17295552... Expands a four-digit extension beginning with the numeral 2 by prefixing 1408555 to the extension. 3... 17295553... num-exp 3... 17295553...
Chapter 6 Configuring VoIP Configure Dial Peers Configure Number Expansion To define how to expand an extension number into a particular destination pattern, use the following global configuration command: num-exp extension-number extension-string extension-number represents the digit(s) defining an extension number to be expanded, whereas extension-string represents the digit(s) defining an extension string to be expanded.
Chapter 6 Configuring VoIP Configure Dial Peers Dial Peer Call Legs, from the Perspective of the Source Catalyst 4224 Source Destination Call leg for POTS dial peer 1 Figure 6-4 IP cloud V 58508 V Call leg for VoIP dial peer 2 Dial Peer Call Legs, from the Perspective of the Destination Catalyst 4224 Call leg for VoIP dial peer 3 V IP cloud Destination Call leg for POTS dial peer 4 V Source 58509 Figure 6-3 There are two types of dial peers with each voice implementation: • POTS (plain
Chapter 6 Configuring VoIP Configure Dial Peers addition, you can use VoIP dial peers to define characteristics such as IP precedence, additional QoS parameters (when RSVP is configured), codec, and VAD. Inbound Versus Outbound Dial Peers Dial peers are used for both inbound and outbound call legs. The terms inbound and outbound are defined from the router perspective. An inbound call leg means that an incoming call comes to the router.
Chapter 6 Configuring VoIP Configure Dial Peers Figure 6-5 Outgoing Calls, from the Perspective of POTS Dial Peer 1 Source Destination Voice port 0/0 Catalyst 4224 Catalyst 4224 10.1.2.2 V 10.1.1.2 IP cloud V Voice port 0/0 (310) 555-1000 POTS call leg dial peer 1 VoIP call leg dial peer 2 58510 (408) 555-4000 To configure call connectivity between the source and the destination as illustrated in Figure 6-5, enter the following commands on Catalyst 4224 10.1.2.
Chapter 6 Configuring VoIP Configure Dial Peers To complete the end-to-end call between dial peer 1 and dial peer 4, as illustrated in Figure 6-6, enter the following commands on Catalyst 4224 10.1.1.2: c4224(config)# dial-peer voice 4 pots c4224(config-dial-peer)# destination-pattern 13105551000 c4224(config-dial-peer)# port 0/0 c4224(config)# dial-peer voice 3 voip c4224(config-dial-peer)# destination-pattern 14085554000 c4224(config-dial-peer)# session target ipv4:10.1.2.
Chapter 6 Configuring VoIP Configure Dial Peers Configure POTS Dial Peers POTS dial peers enable incoming calls to be received by a particular telephony device. To configure a POTS dial peer, you need to uniquely identify the dial peer (by assigning it a unique tag number), define its telephone number(s), and associate it with a voice port through which calls are established.
Chapter 6 Configuring VoIP Configure Dial Peers Configure VoIP Dial Peers VoIP dial peers enable outgoing calls to be made from a particular telephony device. To configure a VoIP dial peer, you need to identify the dial peer (by assigning it a unique tag number), define its destination telephone number, and define its destination IP address. The default values for the remaining dial peer configuration commands are usually adequate to establish connections.
Chapter 6 Configuring VoIP Configure Voice Ports Troubleshooting Tips If you are having trouble connecting a call and you suspect the problem is associated with the dial-peer configuration, you can try to resolve the problem by performing the following tasks: • Ping the associated IP address to confirm connectivity. If you cannot successfully ping your destination, refer to the “Configuring IP” section in the Network Protocols Configuration Guide, Part 1 for Cisco IOS Release 12.0 T.
Chapter 6 Configuring VoIP Configure Voice Ports • FXO—The foreign exchange office interface uses a RJ-11 modular telephone cable to connect local calls to a PSTN central office or to a PBX that does not support E&M signaling. This interface is used for off-premise extension applications. • E&M—The E&M interface uses an RJ-48 telephone cable to connect remote calls from an IP network to PBX trunk lines (tie lines) for local distribution.
Chapter 6 Configuring VoIP Configure Voice Ports Table 6-3 Commands to Configure FXS and FXO Voice Ports (continued) Task Required or Optional Command Step 7 (For FXO ports only) Specify the maximum number of rings before answering a call. Required ring number number Step 8 Specify the private line auto ringdown (PLAR) connection if this voice port is used for a PLAR connection. The string value specifies the destination telephone number.
Chapter 6 Configuring VoIP Configure Voice Ports Troubleshooting Tips If you are having trouble connecting a call and you suspect the problem is associated with the voice port configuration, you can try to resolve the problem by performing the following tasks: • Ping the associated IP address to confirm connectivity. If you cannot ping the destination, refer to the Network Protocols Configuration Guide, Part 1 for Cisco IOS Release 12.0T.
Chapter 6 Configuring VoIP Configure Voice Ports Table 6-4 Commands to Fine Tune FXS and FXO Voice Ports (continued) Valid Entries Default Value –6 to 14 dB 0 dB 0 to 14 dB 0 dB 8, 16, 24, and 32 ms 16 ms timeouts initial seconds 0 to 120 sec 10 sec Specify the number of seconds the system will wait (after the caller has input the initial digit) for the caller to input a subsequent digit.
Chapter 6 Configuring VoIP Configure Voice Ports Table 6-4 Commands to Fine Tune FXS and FXO Voice Ports (continued) Task Command Valid Entries Default Value Step 12 (FXO ports only) If the voice-port dial type is pulse, configure the pulse digit signal duration. timing pulse-digit milliseconds 10 to 20 ms 20 ms Step 13 (FXO ports only) If the voice-port dial type is pulse, configure the pulse inter-digit signal duration.
Chapter 6 Configuring VoIP Configure Voice Ports Table 6-5 Commands to Configure E&M Voice Ports (continued) Task Required or Optional Command Step 4 Select the appropriate signal type for this interface. Step 5 Select the appropriate voice call progress tone Required for this interface. cptone {australia | brazil | china | finland | france | germany | japan | northamerica | unitedkingdom} Step 6 Select the appropriate cabling scheme for this Required voice port.
Chapter 6 Configuring VoIP Configure Voice Ports Table 6-5 Commands to Configure E&M Voice Ports (continued) Required or Optional Command Task impedance {600c | 600r | 900c complex1 | complex2} Step 8 Specify a terminating impedance for an E&M Required voice port. The impedance value selected must match the specifications from the telephony system to which this voice port is connected. Step 9 Specify the private line auto ringdown (PLAR) connection if this voice port is used for a PLAR connection.
Chapter 6 Configuring VoIP Configure Voice Ports Troubleshooting Tips If you are having trouble connecting a call and you suspect the problem is associated with the voice port configuration, you can try to resolve the problem by performing the following tasks: • Ping the associated IP address to confirm connectivity. If you cannot ping the destination, refer to the Network Protocols Configuration Guide, Part 1 for Cisco IOS Release 12.0 T.
Chapter 6 Configuring VoIP Configure Voice Ports Table 6-6 Commands to Fine Tune E&M Voice Ports (continued) Task Command Step 3 Specify (in dB) the amount of gain to be inserted at the receiver side of the interface. input gain value Step 4 Specify (in dB) the amount of attenuation at the transmit side of the interface. output attenuation value Step 5 Enable echo-cancellation of voice that is sent out of the interface and received back on the same interface.
Chapter 6 Configuring VoIP Configure Voice Ports Table 6-6 Commands to Fine Tune E&M Voice Ports (continued) Task Command Valid Entries Default Values Step 9 Specify the number of seconds the system will wait (after the caller has input the initial digit) for the caller to input a subsequent digit. timeouts interdigit seconds 0 to 120 sec 10 sec Step 10 Specify the indicated timing parameters.
Chapter 6 Configuring VoIP Additional VoIP Dial-Peer Configurations Additional VoIP Dial-Peer Configurations Depending on how you have configured your network interfaces, you might need to configure additional VoIP dial-peer parameters.
Chapter 6 Configuring VoIP Additional VoIP Dial-Peer Configurations For example, to ensure that voice traffic associated with VoIP dial peer 103 is given a higher priority than other IP network traffic, enter the following: c4224(config)# dial-peer voice 103 voip c4224(config-dial-peer)# ip precedence 5 In this example, when an IP call leg is associated with VoIP dial peer 103, all packets transmitted to the IP network via this dial peer will have their precedence bits set to 5.
Chapter 6 Configuring VoIP Additional VoIP Dial-Peer Configurations To generate Simple Network Management Protocol (SNMP), use the following commands beginning in global configuration mode: Table 6-8 Configuration Commands to Generate SNMP Task Command Step 1 Enter the dial peer configuration mode to configure a VoIP dial peer. dial-peer voice number voip Step 2 Generate an SNMP event if the QoS for a dial peer drops below a specified level.
Chapter 6 Configuring VoIP Additional VoIP Dial-Peer Configurations The default for the codec command is g729r8, which is normally the most desirable setting. However, if you are operating on a high-bandwidth network and voice quality is of the highest importance, you should configure the codec command for g711alaw or ulaw. Using g711alaw results in better voice quality, but it also requires higher bandwidth usage for voice.
Chapter 6 Configuring VoIP Configure Frame Relay for VoIP For example, to enable VAD for VoIP dial peer 108, enter the following: c4224(config)# Dial-peer voice 108 voip c4224(config-dial-peer)# vad Configure Frame Relay for VoIP When you are configuring VoIP, you need to take certain factors into consideration so that it runs smoothly over Frame Relay. A public Frame Relay cloud provides no QoS guarantee.
Chapter 6 Configuring VoIP Configure Frame Relay for VoIP • Shape the traffic—Use adaptive traffic shaping to slow the output rate based on the backward explicit congestion notification (BECN). If the feedback from the switch is ignored, packets (both data and voice) might be discarded. Because the Frame Relay switch does not distinguish between voice and data packets, voice packets could be discarded, which would result in a deterioration of voice quality.
Chapter 6 Configuring VoIP Configure Frame Relay for VoIP traffic-shape rate 32000 4000 4000 frame-relay interface-dlci 16 frame-relay ip rtp header-compression In this configuration example, the main interface is configured as follows: • MTU size is 300 bytes. • No IP address is associated with this serial interface. The IP address must be assigned for the subinterface. • Encapsulation method is Frame Relay. • Fair-queuing is enabled. • IP RTP header compression is enabled.
Chapter 6 Configuring VoIP Configure Frame Relay for VoIP Catalyst 4224 Access Gateway Switch Software Configuration Guide 6-40 OL-2031-02
C H A P T E R 7 Configuring the Eight-Port FXS RJ-21 Module The Eight-port RJ-21 FXS Module is a high-density analog phone and fax relay interface. By providing service to analog phones and fax machines, the eight Foreign Exchange Station (FXS) ports emulate a Public Switched Telephone Network (PSTN) central office (CO) or private branch exchange (PBX). This section describes how to configure the eight-port FXS module on the Catalyst 4224.
Chapter 7 Configuring the Eight-Port FXS RJ-21 Module Eight-Port RJ-21 FXS Module User Interface Conventions Eight-Port RJ-21 FXS Module User Interface Conventions The eight-port Foreign Exchange Station (FXS) module is similar to the two-port FXS analog interface card (VIC-2FXS). Because the eight-port FXS module is located in slot 4, the eight ports are numbered 4/0 to 4/7. The front panel of this module has two rows of four LEDs each.
Chapter 7 Configuring the Eight-Port FXS RJ-21 Module Configuring FXS Voice Ports Command Purpose cptone country Selects the appropriate voice call progress tone for this interface. The default for this command is us. For a list of supported countries, refer to the Voice, Video, and Home Applications Command Reference. ring frequency {25 | 50} Selects the appropriate ring frequency (in Hertz) specific to the equipment attached to this voice port.
Chapter 7 Configuring the Eight-Port FXS RJ-21 Module Configuring FXS Voice Ports Validating the Configuration To validate your voice port configuration, perform one or both of the following tasks: • Pick up the handset of a telephony device attached to your IP network and check for a dial tone. The corresponding LED turns green to indicate “off-hook” and “call-in-progress” conditions. If the dial tone stops when you dial a digit, then the voice port is probably configured properly.
Chapter 7 Configuring the Eight-Port FXS RJ-21 Module Configuring FXS Voice Ports Ring Frequency is 50 Hz Hook Status is On Hook Ring Active Status is inactive Ring Ground Status is inactive Tip Ground Status is inactive Digit Duration Timing is set to 100 ms InterDigit Duration Timing is set to 100 ms Ring Cadence is defined by CPTone Selection Ring Cadence are [4 2] [4 20] * 100 msec Troubleshooting the Configuration If you are having trouble placing a call and you suspect the problem is associated wit
Chapter 7 Configuring the Eight-Port FXS RJ-21 Module Fine-Tuning FXS Voice Ports Fine-Tuning FXS Voice Ports Depending on the specifics of your particular network, you might need to fine-tune the FXS voice port settings. Under most circumstances, the default values will suffice; however, if you need to change them, use the following commands in privileged EXEC mode. Command Purpose configure terminal Enters global configuration mode.
Chapter 7 Configuring the Eight-Port FXS RJ-21 Module Fine-Tuning FXS Voice Ports Command Purpose timing digit milliseconds If the voice port dial type is dual tone multifrequency (DTMF), configures the duration (in milliseconds) of the DTMF digit signal. The range of the duration is from 50 to 100; the default is 100. timing inter-digit milliseconds If the voice port dial type is DTMF, configures the duration (in milliseconds) of the DTMF interdigit signal.
Chapter 7 Configuring the Eight-Port FXS RJ-21 Module Activating the Voice Port Activating the Voice Port By default, configured voice ports are active. However, if you need to activate a port because it has been shut down explicitly, use the no shutdown command, as follows: Gateway# conf t Enter configuration commands, one per line. End with CNTL/Z.
Chapter 7 Configuring the Eight-Port FXS RJ-21 Module Sample Configuration In the sample configuration illustrated in Figure 7-1, Fax1 is connected through an FXS port to the Cisco 2610 router. The router is connected through Fast Ethernet to the eight-port FXS module, which is connected through an FXS port to Fax2.
Chapter 7 Configuring the Eight-Port FXS RJ-21 Module Sample Configuration 3. Identifies the remote end of the VoIP call, which can be specified using an IP address (as shown in the configuration) or a DNS name. Cisco 2600 Sample Configuration Using the configuration template shown, you could configure the Cisco 2600 as follows: >[Configure the fast ethernet interface] >2600# conf t >Enter configuration commands, one per line. End with CNTL/Z.
Chapter 7 Configuring the Eight-Port FXS RJ-21 Module Sample Configuration >Gateway(config-dial-peer)# dial-peer voice 2 voip >Gateway(config-dial-peer)# destination-pattern 10 >Gateway(config-dial-peer)# session target ipv4:172.20.59.61 At this point, you should be able to send a fax or phone call from the Cisco 2600 to the FXS module, and vice versa.
Chapter 7 Configuring the Eight-Port FXS RJ-21 Module Sample Configuration >ip classless >ip route 8.1.1.0 255.255.255.0 30.1.1.1 >no ip http server >! >snmp-server packetsize 4096 >call rsvp-sync >! >voice-port 1/1/0 >! >voice-port 1/1/1 >! >dial-peer cor custom >! >dial-peer voice 1 pots > destination-pattern 10 > port 1/1/0 >! >dial-peer voice 2 voip > destination-pattern 20 > session target ipv4:172.20.59.
Chapter 7 Configuring the Eight-Port FXS RJ-21 Module Sample Configuration >no service password-encryption >! >hostname Gateway >! >no logging buffered >no logging buffered >logging rate-limit console 10 except errors >! >ip subnet-zero >no ip finger >! >ip audit notify log >ip audit po max-events 100 >! >voicecard mode toll-by-pass >! >interface FastEthernet0/0 > ip address 172.20.59.93 255.255.0.0 > duplex auto > speed auto >! >interface GigabitEthernet0/0 > ip address 1.1.1.1 255.255.255.
Chapter 7 Configuring the Eight-Port FXS RJ-21 Module Sample Configuration >! >voice-port 4/7 >! >dial-peer voice 1 pots > destination-pattern 20 > port 4/0 >! >dial-peer voice 2 voip > destination-pattern 10 > session target ipv4:172.20.59.
C H A P T E R 8 Configuring Survivable Remote Site Telephony Survivable Remote Site Telephony (SRST) provides Cisco CallManager with fallback support for Cisco IP Phones that are attached to the Catalyst 4224 Access Gateway Switch (Catalyst 4224) on your local Ethernet. SRST enables the Catalyst 4224 to provide call handling support for Cisco IP Phones when a Cisco IP Phones lose connection to the remote primary, secondary, or tertiary Cisco CallManager or when the WAN connection is down.
Chapter 8 Configuring Survivable Remote Site Telephony Overview of Survivable Remote Site Telephony Overview of Survivable Remote Site Telephony Cisco CallManager Releases 3.0 and later support Cisco IP Phones across the WAN that are attached to a branch office Catalyst 4224.
Chapter 8 Configuring Survivable Remote Site Telephony Overview of Survivable Remote Site Telephony Prerequisites Prerequisites for employing the SRST feature on the Catalyst 4224 are as follows: • IP routing must be enabled. • The SRST Catalyst 4224 must be configured as the default for the Cisco IP Phones. • Cisco IOS Release 12.1(5)YD or higher is required. • Cisco CallManager Release 3.0.5 or higher is required.
Chapter 8 Configuring Survivable Remote Site Telephony Overview of Survivable Remote Site Telephony Note • Calling party ID (Caller ID/ANI) display • Calling party name display • Last number redial • Maintaining local extension-to-extension calls when WAN link fails • Maintaining local extension to public switched telephone network (PSTN) calls when WAN link fails • Maintaining existing calls when failed WAN link is reestablished • Call transfer of local calls (blind transfer) • Multiple
Chapter 8 Configuring Survivable Remote Site Telephony Overview of Survivable Remote Site Telephony of three entries. When a secondary Cisco CallManager is not configured, the SRST Catalyst 4224 is listed as the stand-by Cisco CallManager during normal operation hosted by a single Cisco CallManager. When the WAN link fails, calls in progress are sustained if possible for the duration of the call. Calls in transition must be attempted again after the Cisco IP Phones re-home to the local SRST Catalyst 4224.
Chapter 8 Configuring Survivable Remote Site Telephony Overview of Survivable Remote Site Telephony Cisco IP Phones periodically attempt to reestablish connections with the remote Cisco CallManagers. When a connection is reestablished with a remote Cisco CallManager, the Cisco IP Phones unregister from the local Catalyst 4224 with the SRST feature and register with the remote Cisco CallManager.
Chapter 8 Configuring Survivable Remote Site Telephony Configuring Survivable Remote Site Telephony Figure 8-2 Branch Office Cisco IP Phones Operating in Survivable Remote Site Telephony (SRST) Mode Telephone Telephone Fax PCs PSTN V Catalyst 4224 IP V IP network WAN disconnected IP Cisco IP phones 58957 IP Central Cisco CallManager Configuring Survivable Remote Site Telephony When SRST is enabled, Cisco IP Phones do not need to be reconfigured individually during Cisco CallManager fallback m
Chapter 8 Configuring Survivable Remote Site Telephony Configuring Survivable Remote Site Telephony Step 3 Task Command Configure the allowable number of Cisco IP Phones that can be supported by the Catalyst 4224. C4224(config-cm-fallback)# max-ephone s max phone Note Step 4 You cannot reduce the allowable number of Cisco IP Phones once the maximum allowable number is configured, without rebooting the Catalyst 4224.
Chapter 8 Configuring Survivable Remote Site Telephony Verifying Survivable Remote Site Telephony Task Command Step 9 (Optional) Configure trunk access codes for each type of line—Basic Rate Interface (BRI), E&M, Foreign Exchange Office (FXO), and Primary Rate Interface (PRI)—so that the Cisco IP Phones can access the trunk lines during Cisco CallManager fallback mode when the SRST feature is enabled.
Chapter 8 Configuring Survivable Remote Site Telephony Troubleshooting Survivable Remote Site Telephony Step 4 Temporarily block the TCP port 2000 Skinny Client Protocol (SCCP) connection for one of the Cisco IP Phones. This forces the Cisco IP Phone to lose its connection to Cisco CallManager and register with the SRS Catalyst 4224. Perform the following: 1. Note Use the appropriate access-list command to temporarily disconnect a Cisco IP Phone from Cisco CallManager.
Chapter 8 Configuring Survivable Remote Site Telephony Monitoring and Maintaining Survivable Remote Site Telephony Command Purpose debug ephone pak Provides voice packet level debugging and prints the contents of one voice packet in every 1024 voice packets. debug ephone raw Provides raw low-level protocol debugging display for all Skinny Client Control Protocol messages.
Chapter 8 Configuring Survivable Remote Site Telephony SRST Configuration Example SRST Configuration Example This section provides a configuration example for the SRST feature: ! version 12.1 no service single-slot-reload-enable service timestamps debug uptime service timestamps log uptime no service password-encryption ! hostname Garfield ! logging rate-limit console 10 except errors ! ip subnet-zero ! no ip finger no ip domain-lookup ! ip dhcp pool PHONE1 host 10.1.0.2 255.255.0.
Chapter 8 Configuring Survivable Remote Site Telephony SRST Configuration Example no ip address ! interface TokenRing1/0 no ip address shutdown ! ip kerberos source-interface any ip classless no ip http server ! snmp-server packetsize 4096 snmp-server manager call rsvp-sync ! mgcp modem passthrough voip mode ca no mgcp timer receive-rtcp ! mgcp profile default ! dial-peer cor custom ! call-manager-fallback ip source-address 10.0.0.
Chapter 8 Configuring Survivable Remote Site Telephony SRST Configuration Example Catalyst 4224 Access Gateway Switch Software Configuration Guide 8-14 OL-2031-02
C H A P T E R 9 Implementing Fax over IP on Cisco Voice Gateways Fax over IP enables interoperability of traditional analog fax machines with IP telephony networks. The fax image is converted from an analog signal and is carried as digital data over the packet network.
Chapter 9 Implementing Fax over IP on Cisco Voice Gateways Overview Overview In its original form, fax data is digital. However, to transmit across a traditional PSTN, it is modulated and converted to analog. Fax over IP reverses this analog conversion, transmitting digital data over the packet network, and then reconverting the digital data to analog for the receiving fax machine.
Chapter 9 Implementing Fax over IP on Cisco Voice Gateways Overview Figure 9-1 Fax Pass-Through IP network Modulated data Modulated data Fax V Latency, Jitter, buffers, Packet loss Voice Gateway V PSTN Modulated data 63696 Fax Voice Gateway Cisco Fax Relay Cisco fax relay does not involve Cisco CallManager; it is a gateway-controlled fax mode.
Chapter 9 Implementing Fax over IP on Cisco Voice Gateways Supported Platforms and Features Figure 9-2 Cisco Fax Relay IP network Modulated data Fax Demodulated data V Latency, Jitter, buffers, Packet loss Voice Gateway with fax relay Fax Voice Gateway with fax relay V PSTN 63613 Modulated data Supported Platforms and Features Table 9-1 shows the supported fax protocol, modes, and required software version for the Catalyst 4224 Access Gateway Switch.
C H A P T E R 10 Traffic Shaping Cisco IOS Quality of Service (QoS) software includes four types of traffic shaping: • Generic Traffic Shaping (GTS) • Class-Based Traffic Shaping • Frame Relay Traffic Shaping (FRTS) • Distributed Traffic Shaping (DTS) All four traffic shaping methods are similar in implementation, though their command line interfaces (CLIs) differ somewhat and they use different types of queues to contain and shape traffic that is deferred.
Chapter 10 Traffic Shaping About Traffic Shaping About Traffic Shaping Traffic shaping allows you to control outgoing traffic on an interface to match the traffic speed of the remote target interface and to ensure that the traffic conforms to specific policies. Traffic that adheres to a particular profile can be shaped to meet downstream requirements, thereby eliminating bottlenecks in topologies caused by data-rate mismatches.
Chapter 10 Traffic Shaping About Traffic Shaping Traffic Shaping and Rate of Transfer Traffic shaping limits the rate of transmission of data. You can limit the data transfer to one of the following: • A specific configured rate • A derived rate based on the level of congestion The rate of transfer depends on three components that constitute the token bucket: burst size, mean rate, and measurement (time) interval. The mean rate is equal to the burst size divided by the interval.
Chapter 10 Traffic Shaping About Traffic Shaping Discard Eligible Bit You can specify which Frame Relay packets have low priority or low time sensitivity. These packets are the first to be dropped when a Frame Relay switch is congested. The Discard Eligible (DE) bit allows a Frame Relay switch to identify such packets.
Chapter 10 Traffic Shaping About Traffic Shaping Table 10-1 summarizes these differences.
Chapter 10 Traffic Shaping Generic Traffic Shaping Traffic Shaping and Queueing Traffic shaping smooths traffic by storing traffic above the configured rate in a queue. When a packet arrives at the interface for transmission, the following sequence occurs: 1. 2. If the queue is empty, the arriving packet is processed by the traffic shaper. • If possible, the traffic shaper sends the packet. • Otherwise, the packet is placed in the queue. If the queue is not empty, the packet is placed in the queue.
Chapter 10 Traffic Shaping Generic Traffic Shaping GTS is supported on most media and encapsulation types on the router. GTS can be applied to a specific access list on an interface. Figure 10-1 shows how GTS works.
Chapter 10 Traffic Shaping Class-Based Traffic Shaping Class-Based Traffic Shaping Class-Based Traffic Shaping can be enabled on any interface that supports GTS. How It Works Using Class-Based Traffic Shaping, you can perform the following tasks: • Configure GTS on a traffic class to provide greater flexibility for configuring traffic shaping. Previously, this ability was limited to the use of ACLs. • Specify average rate or peak rate traffic shaping.
Chapter 10 Traffic Shaping Frame Relay Traffic Shaping For information on traffic shaping commands, see the Cisco IOS Quality of Service Solutions Command Reference, Release 12.2 manual: http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fqos _r/index.htm Restrictions Peak and average traffic shaping is configured on a per-interface or per-class basis, and cannot be used in conjunction with commands used to configure GTS from previous versions of Cisco IOS.
Chapter 10 Traffic Shaping Frame Relay Traffic Shaping How It Works Using FRTS, you can configure rate enforcement to either the CIR or some other defined value such as the excess information rate on a per-VC basis. The ability to allow the transmission speed used by the router to be controlled by criteria other than line speed provides a mechanism for sharing media by multiple VCs. You can allocate bandwidth to each VC, creating a virtual time-division multiplexing (TDM) network.
Chapter 10 Traffic Shaping Frame Relay Traffic Shaping this data will get marked with a BECN on its way to the other DTE device. However, if the DTE device is not sending any data, the DTE device can send a Q.922 TEST RESPONSE message with the BECN bit set. When an interface configured with traffic shaping receives a BECN, it immediately decreases its maximum rate by a large amount.
Chapter 10 Traffic Shaping Distributed Traffic Shaping Restrictions FRTS applies only to Frame Relay PVCs and switched virtual circuits (SVCs). Distributed Traffic Shaping DTS provides a method of managing the bandwidth of an interface to avoid congestion, to meet remote site requirements, and to conform to a service rate that is provided on that interface. DTS uses queues to buffer traffic surges that can congest a network and send the data to the network at a regulated rate.
Chapter 10 Traffic Shaping Distributed Traffic Shaping DTS provides the following key benefits: • Offloads traffic shaping from the Route Switch Processor (RSP) to the VIP. • Supports up to 200 shape queues per VIP, supporting up to OC-3 rates when the average packet size is 250 bytes or greater and when using a VIP2-50 or better with eight MB of SRAM. Line rates below T3 are supported with a VIP2-40. • Configures DTS at the interface level or subinterface level.
Chapter 10 Traffic Shaping Low-Latency Queueing Restrictions DTS does not support the following: Note • Fast EtherChannel, Multilink PPP (MLP), Tunnel, VLANs, and dialer interface • Any VIP below a VIP2-40 A VIP2-50 is strongly recommended when the aggregate line rate of the port adapters on the VIP is greater than DS3. A VIP2-50 card is required for OC-3 rates. Low-Latency Queueing The LLQ feature brings strict PQ to CBWFQ.
Chapter 10 Traffic Shaping Low-Latency Queueing can give one or more classes priority status. When multiple classes within a single policy map are configured as priority classes, all traffic from these classes is enqueued to the same single, strict priority queue. One of the ways in which the strict PQ used within CBWFQ differs from its use outside CBWFQ is in the parameters it takes.
Chapter 10 Traffic Shaping Low-Latency Queueing Catalyst 4224 Access Gateway Switch Software Configuration Guide 10-16 OL-2031-02
C H A P T E R 11 Configuring Encryption Services The Encryption Service Adapter (ESA) is a high-performance data encryption module that offloads some of the encryption processing from the Catalyst 4224 main processor and improves performance. The ESA implements data encryption and authentication algorithms on the Catalyst 4224 through a software service called a crypto engine. The ESA includes a public key math processor and a hardware random number generator.
Chapter 11 Configuring Encryption Services Configuring the Encryption Service Adapter Configuring the Encryption Service Adapter Configuring the ESA requires four steps, as outlined below: • Step 1: Configure the T1 Channel Group, page 11-2 • Step 2: Configure the Internet Key Exchange Security Protocol, page 11-3 • Step 3: Configure IPSec Network Security, page 11-5 • Step 4: Configure Encryption on the T1 Channel Group Serial Interface, page 11-8 Step 1: Configure the T1 Channel Group The first
Chapter 11 Configuring Encryption Services Configuring the Encryption Service Adapter Step 4 Task Command Specify the framing type for the T1 or E1 data line. Gateway(config-controller)# framing {sf|esf} sf specifies Super Frame as the T1 frame type. esf specifies Extended Super Frame as the T1 frame type. Step 5 Specify the line code format. ami specifies alternate mark inversion (AMI) as the line-code type. Valid for T1 or E1 controllers; the default for T1 lines.
Chapter 11 Configuring Encryption Services Configuring the Encryption Service Adapter To configure an IKE Security Protocol, follow this procedure: Task Step 1 Command 1 Create an IKE policy with a unique priority number and enter Internet Security Association and Key Management Protocol (ISAKMP2) policy configuration mode. Note Gateway(config)# crypto isakmp policy priority You can configure multiple policies on each peer3.
Chapter 11 Configuring Encryption Services Configuring the Encryption Service Adapter Step 3: Configure IPSec Network Security The third step is to define how the T1 data will be handled. This requires that you use IPSec (IP Security Protocol) security. IPSec is a framework of open standards that provides data confidentiality, data integrity, and data authentication between participating peers. IPSec provides these security services at the IP layer.
Chapter 11 Configuring Encryption Services Configuring the Encryption Service Adapter Task Step 4 Command 3 Create a crypto map denoted by map-name. Enter crypto map configuration mode, unless you use the dynamic keyword. Gateway(config)# crypto map map_name seq_num ipsec-isakmp [dynamic dynamic_map_name] [discover] seq-num is the number you assign to the crypto map entry.
Chapter 11 Configuring Encryption Services Configuring the Encryption Service Adapter Task Command Step 8 Return to global configuration mode. Gateway(cfg-crypto-trans)# exit Step 9 Create an access list.4 Gateway(config)# access-list access_list_number {permit | deny} {type_code wild_mask | address mask} access_list_number denotes an IP list number from 1 through 99. permit or deny specifies permit or deny condition for this list.
Chapter 11 Configuring Encryption Services Configuring the Encryption Service Adapter Step 4: Configure Encryption on the T1 Channel Group Serial Interface The fourth step is to configure a T1 serial interface with an IP address and a crypto map. To configure encryption on the T1 channel group, follow this procedure: Task Command Step 1 Select the serial interface and enter interface configuration mode.
Chapter 11 Configuring Encryption Services Verifying the Configuration Verifying the Configuration After configuring the new interface, use the following commands to verify that it is operating correctly: Note • Use show version to display the router hardware configuration. Check that the list includes the new interface. • Use show controllers to display all network modules and their interfaces. • Use show interfaces [type slot/port] to display the details of a specified interface.
Chapter 11 Configuring Encryption Services Sample Configurations Encrypting Traffic Between Two Networks The sample configurations in this section show you how to encrypt traffic between a private network (10.103.1.x) and a public network (98.98.98.x) using IPSec. The 98.98.98.x network knows the 10.103.1.x network by the private addresses. The 10.103.1.x network knows the 98.98.98.x network by the public addresses.
Chapter 11 Configuring Encryption Services Sample Configurations no ip directed-broadcast no ip route-cache no ip mroute-cache crypto map rtp ! interface Ethernet0/2 no ip address no ip directed-broadcast shutdown ! interface Ethernet0/3 no ip address no ip directed-broadcast shutdown ! ip classless ip route 0.0.0.0 0.0.0.0 99.99.99.1 no ip http server ! access-list 115 permit ip 98.98.98.0 0.0.0.255 10.103.1.0 0.0.0.255 access-list 115 deny ip 98.98.98.0 0.0.0.
Chapter 11 Configuring Encryption Services Sample Configurations ! ip subnet-zero ! ip audit notify log ip audit PO max-events 100 isdn switch-type basic-5ess isdn voice-call-failure 0 ! crypto isakmp policy 1 hash md5 authentication pre-share crypto isakmp key cisco123 address 99.99.99.2 ! crypto ipsec transform-set rtpset esp-des esp-md5-hmac crypto map rtp 1 ipsec-isakmp set peer 99.99.99.
Chapter 11 Configuring Encryption Services Sample Configurations shutdown ! interface Serial1/0 no ip address no ip directed-broadcast shutdown ! interface TokenRing1/0 no ip address no ip directed-broadcast shutdown ring-speed 16 ! interface Ethernet3/0 ip address 95.95.95.2 255.255.255.0 no ip directed-broadcast ip nat outside no ip route-cache no ip mroute-cache crypto map rtp ! interface Ethernet3/1 no ip address no ip directed-broadcast shutdown ! interface Ethernet3/2 ip address 10.103.1.75 255.255.
Chapter 11 Configuring Encryption Services Sample Configurations dialer-list 1 protocol ipx permit route-map nonat permit 10 match ip address 110 ! tftp-server flash:cgateway-io3s56i-mz.120-7.
Chapter 11 Configuring Encryption Services Sample Configurations crypto ipsec transform-set transform-1 esp-des ! crypto map cmap 1 ipsec-isakmp set peer 6.6.6.2 set transform-set transform-1 match address 101 ! controller T1 1/0 framing esf linecode b8zs channel-group 0 timeslots 1-23 speed 64 channel-group 1 timeslots 24 speed 64 ! controller T1 1/1 channel-group 0 timeslots 1-23 speed 64 channel-group 1 timeslots 24 speed 64 ! process-max-time 200 ! interface FastEthernet0/0 ip address 111.0.0.2 255.0.
Chapter 11 Configuring Encryption Services Sample Configurations crypto map cmap ! interface Serial1/0:1 no ip address no ip directed-broadcast fair-queue 64 256 0 ! interface Serial1/1:0 no ip address no ip directed-broadcast ! interface Serial1/1:1 no ip address no ip directed-broadcast fair-queue 64 256 0 ! router rip network 4.0.0.0 network 6.0.0.0 ! ip classless ip route 0.0.0.0 0.0.0.0 111.0.0.
Chapter 11 Configuring Encryption Services Sample Configurations ! logging buffered 100000 debugging enable password lab ! ip subnet-zero no ip domain-lookup ! crypto isakmp policy 10 authentication pre-share crypto isakmp key pre-shared address 6.6.6.1 ! crypto ipsec security-association lifetime seconds 86400 ! crypto ipsec transform-set transform-1 esp-des ! crypto map cmap 1 ipsec-isakmp set peer 6.6.6.
Chapter 11 Configuring Encryption Services Sample Configurations interface Serial1/0:0 bandwidth 1472 ip address 6.6.6.2 255.0.0.0 no ip directed-broadcast encapsulation ppp no ip route-cache load-interval 30 no fair-queue crypto map cmap ! interface Serial1/0:1 no ip address no ip directed-broadcast fair-queue 64 256 0 ! interface Serial1/1:0 no ip address no ip directed-broadcast ! interface Serial1/1:1 no ip address no ip directed-broadcast fair-queue 64 256 0 ! router rip network 3.0.0.0 network 6.0.
C H A P T E R 12 Configuring Other Routing Protocols Cisco IOS software on the Catalyst 4224 Access Gateway Switch supports the following additional routing protocols: • Novell IPX, page 12-1 • IBM SNA, page 12-4 Novell IPX Novell Internetwork Packet Exchange (IPX) is derived from the Xerox Network Systems (XNS) Internet Datagram Protocol (IDP). IPX and XNS have the following differences: • IPX and XNS do not always use the same Ethernet encapsulation format.
Chapter 12 Configuring Other Routing Protocols Novell IPX IPX MIB Support Cisco supports the IPX MIB (currently, read-only access is supported). The IPX Accounting group represents one of the local Cisco-specific IPX variables Cisco supports. This group provides access to the active database that is created and maintained if IPX accounting is enabled on a router or access server.
Chapter 12 Configuring Other Routing Protocols Novell IPX LAN Support Cisco IOS software supports routing IPX between Ethernet-emulated LANs and Token Ring-emulated LANs. For more information on emulated LANs and routing IPX between them, refer to the “Configuring LAN Emulation” chapter of the Cisco IOS Switching Services Configuration Guide. VLAN Support Cisco IOS software supports routing IPX between VLANs.
Chapter 12 Configuring Other Routing Protocols IBM SNA IBM SNA Adopting a TCP/IP infrastructure is the first logical step to creating a multiservice network that seamlessly accommodates data, voice, and video. Enterprise organizations are heavily invested in mainframes and Systems Network Architecture (SNA) and mainframes are still a vital part of enterprise data centers. The goal for these enterprise organizations is to integrate the TCP/IP-based environment with the SNA-based environment.
Chapter 12 Configuring Other Routing Protocols IBM SNA Figure 12-1 The Cisco Four-Phase SNA-to-IP Integration Model Phase 1 Phase 2 SNA Network IP SNA/APPN SNA SNA centric lie nt IP transport Phase 4 C Phase 3 Appl SNA IP IP client IP centric 51880 IP The phases can be differentiated by the protocol that runs in each of three key elements in the network: the mainframe/midrange computer, the network backbone, and the desktop.
Chapter 12 Configuring Other Routing Protocols IBM SNA This section contains the following topics: • Phase One: SNA Centric, page 12-6 • Phase Two: IP Transport, page 12-7 • Phase Three: IP Client, page 12-8 • Phase Four: IP Centric, page 12-9 • Summary of Four-Phase Model, page 12-9 Phase One: SNA Centric An SNA-centric network has SNA, Advanced Peer-to-Peer Networking (APPN), or APPN/High Performance Routing (HPR), protocols running on one or more mainframe/midrange systems.
Chapter 12 Configuring Other Routing Protocols IBM SNA Phase Two: IP Transport Beginning in the 1980s, large organizations began building TCP/IP-based networks to support client/server applications and systems. UNIX, a dominant operating system for client/server applications, natively supports TCP/IP. As the growth of TCP/IP-based systems continued, organizations often found that they had built parallel networks, one running SNA and one running TCP/IP.
Chapter 12 Configuring Other Routing Protocols IBM SNA Phase Three: IP Client In the third phase of SNA-to-IP integration, organizations eliminated the dual protocol stacks at end-user PCs by implementing emulation software that supports TCP/IP. The same rich functionality that end users relied on in their emulation software remains the same, only it now runs over a TCP/IP stack.
Chapter 12 Configuring Other Routing Protocols IBM SNA Phase Four: IP Centric In the fourth and final stage of SNA-to-IP integration, the mainframe and midrange systems natively support TCP/IP. They share files with and transfer data to other, non-SNA systems. Corporate databases are securely accessed in a standard way from a variety of different end-user applications.
Chapter 12 Configuring Other Routing Protocols IBM SNA Scenarios for SNA-to-IP Integration There are common elements or scenarios for integrating TCP/IP with SNA networks. This section describes three elements or scenarios, the corresponding phase from the Cisco four-phase integration model, and the Cisco products and software features deployed in these scenarios.
Chapter 12 Configuring Other Routing Protocols IBM SNA The primary product in a FEP replacement project is a channel-attached router. This router contains the mainframe channel connection hardware supporting either a bus-and-tag or ESCON interface (or multiple interfaces). It also runs the necessary channel protocol software and, in some cases, special software designed to offload communication processing from the mainframe.
Chapter 12 Configuring Other Routing Protocols IBM SNA SNA Configuration For details on how to configure SNA protocol, refer to the following documentation: • Cisco IOS Bridging and IBM Networking Configuration Guide, Release 12.2 http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/ fibm_c/index.htm • Cisco IOS Bridging and IBM Networking Command Reference, Volume 1, Release 12.2 http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/ fibm_r1/index.
A P P E N D I X A Command Reference for Voice VLAN This section provides reference information for the following voice VLAN commands: • interface range, page A-1 • interface vlan, page A-3 • monitor session, page A-4 • spanning-tree, page A-6 • spanning-tree portfast, page A-7 • switchport access, page A-8 • switchport voice vlan, page A-10 interface range The interface range command allows you to configure multiple interfaces with the same configuration parameters.
Appendix A Command Reference for Voice VLAN interface range Syntax Description slot Slot number. interface Interface number. Defaults None. Command Modes Global configuration Usage Guidelines The space before the dash is required. You can enter up to five comma-separated ranges. You are not required to enter spaces before or after the comma. If you enter multiple configuration commands while you are in interface range mode, each command is executed as it is entered.
Appendix A Command Reference for Voice VLAN interface vlan interface vlan Use the interface vlan configuration command to configure an interface type, create a switch virtual interface to be used as the routed VLAN interface, and to enter interface configuration mode. Syntax interface vlan number no interface vlan number Syntax Description number Valid VLAN IDs are from 1 to 1005. Do not enter leading zeroes. Defaults The default management VLAN interface is VLAN 1. Command Modes Global configuration.
Appendix A Command Reference for Voice VLAN monitor session Example The following example shows how to enter configuration mode for vlan 3: Switch# configure terminal Switch(config)# interface vlan 3 Switch(config-if)# monitor session Use the monitor session configuration command to set a port session.
Appendix A Command Reference for Voice VLAN monitor session Command Modes Interface configuration. Usage Guidelines You can span only selected interfaces. You cannot span VLANs. Examples The following example shows how to set up a port monitor session. For this example, we configure two sessions in global configuration mode.
Appendix A Command Reference for Voice VLAN spanning-tree spanning-tree Use the spanning-tree global configuration command to enable Spanning Tree Protocol (STP) on a VLAN. Use the no form of the command to disable STP on a VLAN. Syntax spanning-tree [vlan stp-list] no spanning-tree [vlan stp-list] Syntax Description vlan stp-list (Optional) List of spanning-tree instances. Each spanning-tree instance is associated with a VLAN ID. Valid IDs are from 1 to 1005. Enter each VLAN ID separated by a space.
Appendix A Command Reference for Voice VLAN spanning-tree portfast You can disable STP on a VLAN that is not currently active, and verify the change by using the privileged EXEC show running-config or the show spanning-tree vlan stp-list command. The setting takes effect when the VLAN is activated. If the variable stp-list is omitted, the command applies to the STP instance associated with VLAN 1. You can enable STP on a VLAN that has no ports assigned to it.
Appendix A Command Reference for Voice VLAN switchport access Defaults The Port Fast feature is disabled; however, it is automatically enabled on dynamic-access ports. Command Modes Interface configuration. Usage Guidelines This feature should be used only on ports that connect to end stations. It affects all VLANs on the port. A port with the Port Fast feature enabled is moved directly to the spanning-tree forwarding state.
Appendix A Command Reference for Voice VLAN switchport access Syntax switchport access vlan vlan-id no switchport access vlan vlan-id Syntax Description vlan vlan-id ID of the VLAN. Valid IDs are from 1 to 1005. Do not enter leading zeroes. Defaults All ports are in static-access mode in VLAN 1. Command Modes Interface configuration. Usage Guidelines An access port can be assigned to only one VLAN. When the no switchport access vlan form is used, the access mode is reset to static access on VLAN 1.
Appendix A Command Reference for Voice VLAN switchport voice vlan You can verify the previous command by entering the show interface interface-id switchport command in privileged EXEC mode and examining information in the Administrative Mode and Operational Mode rows. switchport voice vlan Use the switchport voice vlan interface configuration command to configure the voice VLAN on the port. Use the no form of this command to return the setting to its default.
Appendix A Command Reference for Voice VLAN switchport voice vlan Defaults The switch default is not to configure the telephone automatically (none). The Cisco 7960 IP Phone default is to generate an 802.1Q/802.1P frame. Command Modes Interface configuration. Usage Guidelines Ports that are not configured as trunk ports but have a configured voice VLAN are access ports with a voice VLAN ID (VVID).
Appendix A Command Reference for Voice VLAN switchport voice vlan Catalyst 4224 Access Gateway Switch Software Configuration Guide A-12 OL-2031-02
A P P E N D I X B Synopsis of Basic VoIP Concepts The Catalyst 4224 Access Gateway Switch (Catalyst 4224) provides Voice over IP (VoIP) gateway applications for a micro branch office. This chapter introduces some basic VoIP concepts.
Appendix B Synopsis of Basic VoIP Concepts A Voice Primer A Voice Primer This section describes some basic telephony concepts that might help you understand VoIP: • How VoIP Processes a Typical Telephone Call, page B-2 • Numbering Scheme, page B-3 • Analog Versus Digital, page B-3 • codecs, page B-4 • Delay, page B-5 • Echo, page B-7 • Signaling, page B-7 How VoIP Processes a Typical Telephone Call The general flow of a two-party call follows this process: 1.
Appendix B Synopsis of Basic VoIP Concepts A Voice Primer 6. The coder-decoder compression schemes (codecs) are enabled for both ends of the connection using Real-Time Transport Protocol/User Datagram Protocol/Internet Protocol (RTP/UDP/IP) as the protocol stack. 7. Any call-progress indications (or other signals that can be carried inband) are cut through the voice path as soon as an end-to-end audio channel is established.
Appendix B Synopsis of Basic VoIP Concepts A Voice Primer In response to the limitations of analog transmission, the telephony industry migrated to digital transmission using pulse code modulation (PCM) or adaptive differential PCM (ADPCM). In both cases, analog sound is converted into digital form by sampling the analog sound 8000 times per second and converting each sample into a numeric code.
Appendix B Synopsis of Basic VoIP Concepts A Voice Primer Table B-1 Compression Methods and MOS Scores Compression Method Bit Rate (kbps) Framing Size (ms) MOS Score G.711 PCM 64 0.125 4.1 8 10 3.92 G.729 x 2 encodings2 8 10 3.27 G.729 x 3 encodings 8 10 2.68 G.729a3 8 10 3.7 G.729 CS-ACELP 1 CS-ACELP 1. Conjugate structure-algebraic code-excited linear prediction. 2. A G.729 voice signal is tandem-encoded two times. 3. G.729 Annex A.
Appendix B Synopsis of Basic VoIP Concepts A Voice Primer Handling delay (sometimes called serialization delay) is caused by the devices that handle voice information. Handling delays significantly degrade voice quality in a packet network. Delays caused by codecs are considered handling delays. Table B-2 shows the delay introduced by different codecs. Table B-2 codec-Induced Delays codec Bit Rate (kbps) Framing size (ms) Compression Delay (ms) G.711 PCM 64 0.125 5 G.729 CS-ACELP 8 10 15 G.
Appendix B Synopsis of Basic VoIP Concepts A Voice Primer Playout control is handled through RTP encapsulation, either by selecting adaptive or non-adaptive playout-delay mode. In either mode, the default value for nominal delay is sufficient. End-to-End Delay Figuring out the end-to-end delay is not difficult if you know the end-to-end signal paths/data paths, the codec, and the payload size of the packets.
Appendix B Synopsis of Basic VoIP Concepts A Voice Primer when a line has gone off-hook or on-hook. Foreign Exchange Station (FXS) and Foreign Exchange Office (FXO) are types of access signaling. There are two common methods of providing this basic signal: • Loop start is the most common technique for access signaling in a standard PSTN end-loop network.
A P P E N D I X C VoIP Configuration Examples This section uses four different scenarios to demonstrate how to configure Voice over IP (VoIP). The actual VoIP configuration procedure depends on the topology of your voice network. The following configuration examples should give you a starting point, but you will need to customize them to reflect your network topology.
Appendix C VoIP Configuration Examples Figure C-1 illustrates the topology of this FXS-to-FXS connection example.
Appendix C VoIP Configuration Examples Configuration for Catalyst 4224 RLB-1 hostname RLB-1 ! Create voip dial-peer 2 dial-peer voice 2 voip ! Define its associated telephone number and IP address destination-pattern 14155553001 sess-target ipv4:40.0.0.1 ! Request RSVP req-qos controlled-load ! Create pots dial-peer 1 dial-peer voice 1 pots ! Define its associated telephone number and voice port destination-pattern 14085554001 port 0/0 ! Configure serial interface 0 interface Serial0 ip address 10.0.0.
Appendix C VoIP Configuration Examples Configuration for Catalyst 4224 RLB-w hostname RLB-w ! Configure serial interface 0 interface Serial0 ip address 10.0.0.2 255.0.0.0 ! Configure RTP header compression ip rtp header-compression ip rtp compression-connections 25 ! Enable RSVP on this interface ip rsvp bandwidth 96 96 fair-queue 64 256 3 ! Configure serial interface 1 interface Serial1 ip address 20.0.0.1 255.0.0.
Appendix C VoIP Configuration Examples Configuration for Catalyst 4224 RLB-e hostname RLB-e ! Configure serial interface 0 interface Serial0 ip address 40.0.0.2 255.0.0.0 ! Configure RTP header compression ip rtp header-compression ip rtp compression-connections 25 ! Enable RSVP on this interface ip rsvp bandwidth 96 96 fair-queue 64 256 3 ! Configure serial interface 1 interface Serial1 ip address 20.0.0.2 255.0.0.
Appendix C VoIP Configuration Examples Configuration for Catalyst 4224 RLB-2 hostname RLB-2 ! Create pots dial-peer 2 dial-peer voice 2 pots ! Define its associated telephone number and voice-port destination-pattern 14155553001 port 0/0 ! Create voip dial-peer 1 dial-peer voice 1 voip !Define its associated telephone number and IP address destination-pattern 14085554001 sess-target ipv4:10.0.0.1 ! Configure serial interface 0 interface Serial0 ip address 40.0.0.1 255.0.0.
Appendix C VoIP Configuration Examples Linking PBX Users with E&M Trunk Lines The following example shows how to configure VoIP to link PBX users with E&M trunk lines. In this scenario, a company decides to connect two offices: one in San Jose, California, and the other in Salt Lake City, Utah. Each office has an internal telephone network using a PBX connected to the voice network by an E&M interface.
Appendix C VoIP Configuration Examples Router San Jose Configuration hostname router SJ !Configure pots dial-peer 1 dial-peer voice 1 pots destination-pattern 1408555.... port 0/0 !Configure pots dial-peer 2 dial-peer voice 2 pots destination-pattern 1408555.... port 0/1 !Configure voip dial-peer 3 dial-peer voice 3 voip destination-pattern 1801555.... session target ipv4:172.16.65.
Appendix C VoIP Configuration Examples Router Salt Lake City Configuration hostname router SLC !Configure pots dial-peer 3 dial-peer voice 3 pots destination-pattern 1801555.... port 0/0 !Configure pots dial-peer 4 dial-peer voice 4 pots destination-pattern 1801555.... port 0/1 !Configure voip dial-peer 1 dial-peer voice 1 voip destination-pattern 1408555.... session target ipv4:172.16.1.
Appendix C VoIP Configuration Examples FXO Gateway to PSTN Foreign Exchange Office (FXO) interfaces provide a gateway from the VoIP network to the analog public switched telephone network (PSTN) or to a PBX that does not support Ear and Mouth (E&M) signaling. In this scenario, users connected to Catalyst 4224 SJ in San Jose, California, can reach PSTN users in Salt Lake City, Utah, via Catalyst 4224 SLC. Router SLC in Salt Lake City is connected directly to the PSTN through an FXO interface.
Appendix C VoIP Configuration Examples Router San Jose Configuration hostname router SJ ! Configure pots dial-peer 1 dial-peer voice 1 pots destination-pattern 14085554000 port 0/0 ! Configure voip dial-peer 2 dial-peer voice 2 voip destination-pattern 1801....... session target ipv4:172.16.65.182 ip precedence 5 ! Configure serial interface 0 interface serial0 clock rate 2000000 ip address 172.16.1.
Appendix C VoIP Configuration Examples FXO Gateway to PSTN (PLAR Mode) The following scenario shows an FXO gateway to PSTN connection in PLAR mode. In this scenario, PSTN users in Salt Lake City, Utah, can dial a local number and establish a private line connection in a remote location. As in the previous scenario, Catalyst 4224 SLC in Salt Lake City is connected directly to the PSTN through an FXO interface. Figure C-4 illustrates the topology of this scenario.
Appendix C VoIP Configuration Examples Router San Jose Configuration hostname router SJ ! Configure pots dial-peer 1 dial-peer voice 1 pots destination-pattern 14085554000 port 0/0 ! Configure voip dial-peer 2 dial-peer voice 2 voip destination-pattern 1801....... session target ipv4:172.16.65.182 ip precedence 5 ! Configure the serial interface 0 interface serial0 clock rate 2000000 ip address 172.16.1.
Appendix C VoIP Configuration Examples Catalyst 4224 Access Gateway Switch Software Configuration Guide C-14 OL-2031-02
I N D EX static A adding 3-22 adding secure addresses 3-20, 3-21 static addresses 3-22 address resolution 3-17 see also addresses addresses dynamic described 3-18, 3-22 removing 3-23 Address Resolution Protocol (ARP) see ARP table address table aging time, configuring 3-19 dynamic addresses, removing 3-20 MAC 3-18 aging time 3-19 secure addresses described 3-18 adding 3-21 removing 3-20 removing 3-21 for IP phones 3-9 MAC static addresses removing 3-23 adding secure 3-20 ADPCM codec B-4 aging
Index asynchronous/synchronous serial interface configuring 4-6 audience xviii Cisco IOS command modes 2-6 enable mode 2-8 getting help 2-6 saving configuration changes 2-8 B undo command 2-8 backup Cisco CallManager 5-4 class-based shaping feature description 10-8 Bc 6-39 CMCC (Cisco Mainframe Channel Connection) adapter Be 6-39 BECN 6-38 BECN (backward explicit congestion notification) SNA-to-IP integration 12-11 codec FRTS 10-10 applied B-3 GTS 10-6 configuring 6-35 BOOTP 3-11 described B
Index show protocols 4-18 IP information 3-11 show running-config 4-18 IP networks for real-time voice traffic 6-3 show startup-config 5-3 IP Phone 3-15 show version 4-18 ISDN-BRI interface 4-9 switchback 5-5 ISDN PRI interface 4-12 switchover 5-6 E1 interface 4-16, 5-13, 5-33 undo 2-8 T1 interface 4-12, 5-10, 5-31 commands show running-config 5-3 multiflex trunk interface 4-12 configuration E1 interface 4-16, 5-13, 5-33 saving 4-19 T1 interface 4-12, 5-10, 5-31 saving changes 2-8 Mult
Index DNS D configuring 3-13 DE (discard eligible) lists, traffic shaping 10-4 described 3-14 debug cch323 h225 command 6-22 enabling 3-14 debug cch323 rtp command 6-22 document debug vpm spi command 6-22 conventions xx delay B-5 objectives xvii dial-peer command 5-8 organization xviii dial-peer configuration documentation optimizing 6-33 related xix POTS 6-20, 6-21 domain name table 6-19 described 3-14 troubleshooting tips 6-22 specifying 3-13, 3-14 verifying 6-21 Domain Name Syst
Index E&M voice port FEP (front-end processor) configuration example C-7 replacement 12-10 configuring 6-27 Frame Relay for VoIP fine-tuning commands 6-30 configuring 6-37 signaling type B-8 example 6-38 troubleshooting tips 6-30 FRTS (Frame Relay Traffic Shaping) 10-9 verifying 6-29 FXO E.
Index GTS (Generic Traffic Shaping) how it works (figure) 10-7 overview 10-6 IP address configuring for H.323 endpoints 5-18 IP addresses discovering 3-18 removing 3-13 H IP addressing 3-9 H.
Index routing M between emulated LANs 12-3 MAC addresses metrics 12-1 SAP 12-1 adding secure 3-20 VLAN support 12-3 aging time 3-19 ISDN BRI interface, configuring 4-9 discovering 3-18, 3-19 ISDN PRI interface MAC address tables, managing 3-18 configuring 4-12 manual redirection of call agent 5-6 E1 configuration 4-16, 5-13, 5-33 mean opinion score B-4 T1 configuration 4-12, 5-10, 5-31 metrics, routing ISDN switch types 5-25 IPX 12-1 ITU-T B-1 XNS 12-1 MIB IPX 12-2 J modem, connecting
Index power, inline 3-15 N power detection on the 3524-PWR 3-16 NANP B-3 primary Cisco CallManager 5-4 North American Numbering Plan B-3 privileged EXEC command mode 2-6 Novell IPX provisioning the gateway 5-16 See IPX PVC 6-37 number expansion command 6-12 configuring 6-15 described 6-12 Q QoS table 6-13 see Quality of Service numbering scheme B-3 Quality of Service backbone routers 6-4 described 6-3 P edge routers 6-4 packet loss prevention, traffic shaping 10-2 tools password custom
Index removing signaling types dynamic address entries 3-20 E&M 6-22, B-8 IP information 3-13 FXS/FXO 6-22, B-8 secure addresses 3-21 SNA (Systems Network Architecture) internetworking overview 12-11 static addresses 3-22, 3-23 RSVP SNA-to-IP integration applied B-2 description 12-4 configuring for voice 6-5 phases enabled 6-5 (figure) 12-5 FXS-to-FXS connection example C-1 IP centric 12-9 RTCP B-3 IP client 12-8 RTP 6-9, B-3 IP transport 12-7 RTP header compression 6-9 SNA centric 1
Index switchover 5-5 trap managers switchover command 5-6 adding 3-11 Switch Port Analyzer (SPAN) configuring 3-11 disabling 3-17 enabling 3-16 troubleshooting dial-peer configuration 6-22 E&M configuration 6-30 FXS/FXO configuration 6-25 T T1 channel bank 5-19 T1 interface configuring 4-12 U UDP 6-9, B-3 terminal, connecting to 2-3 undo command 2-8 timeout, disabling 4-3 user EXEC command mode 2-6 time slots, configuring 5-9 timeslots, configuring 5-20 traffic monitoring 3-16 traffic shaping
Index voice activity detection VoIP see VAD see Voice-over-IP voice interfaces VoIP dial peer configuring 5-1 configuring 6-21 Voice over IP described 6-16 configuring 3-14, 5-1, 6-1 Frame Relay, configuring for 6-37 port configuration 3-15 voice over IP weighted fair queuing 6-12 linking PBX users with E&M trunk lines 5-35 voice ports W Weighted Random Early Detection 6-3 wildcard destination patterns, configuring 5-18 WRED 6-3 configuring troubleshooting tips 7-5 E&M configuring 6-27 desc
Index Catalyst 4224 Access Gateway Switch Software Configuration Guide IN-12 OL-2031-01
