Table Of Contents
New Hardware Features Supported in Cisco IOS Release 12.2(15)T
1 Port Enhanced ATM Port Adapter with Support for 8K VCs
1 and 2-port T1/E1 Multiflex Voice/WAN Interface Card
1- and 2-Port V.90 Modem WICs for Cisco 1720, 1751 and 1760 Routers
Catalyst 4500 Access Gateway Module 16-port RJ21 FXS Module (WS-U4604-16FXS)
Catalyst 4500 AGM Voice/WAN Bundle (WS-X4604-VOICE)
Gigabit Ethernet Network Module
SDH/STM-1 Trunk Card for Cisco AS5850 Universal Gateway
New Software Features in Cisco IOS Release 12.2(15)T
Any Transport over MPLS (AToM)
Asynchronous Call Queueing by Role
BGP Increased Support of Numbered AS-Path Access Lists to 500
BGP Nonstop Forwarding (NSF) Awareness
BGP Restart Session After Max-Prefix Limit
BGP Route-Map Policy List Support
Certificate Security Attribute-Based Access Control
Cisco Easy VPN Remote Enhancements
Cisco IOS Firewall Stateful Inspection of ICMP
Cisco IOS Firewall Support for SIP
Cisco IOS Firewall Websense URL Filtering
Cisco IOS Software Feature Removal—Phase II
Cisco IOS Telephony Service Version 2.1
Cisco Mobile Networks—Priority Home Agent Assignment
Cisco Mobile Networks—Static Collocated Care-of Address
Cisco Mobile Networks—Tunnel Templates for Multicast
Cisco Survivable Remote Site Telephony Version 2.1
Class-Based Policer for the DiffServ AF PHB
Clear Channel T3/E3 with Integrated CSU/DSU
DHCP Secured IP Address Assignment
DHCP Server Import All Enhancement
DHCP Server—ODAP Support for Non-MPLS VPN Pools
EIGRP Nonstop Forwarding (NSF) Awareness
Enhanced Debug Capabilities for Cisco Voice Gateways
Expanded Scope for Cause-Code-Initiated Call Establishment Retries
Exporting and Importing RSA Keys
Fax and Modem Pass-Through over VoIP
Firewall Intrusion Detection System Signature Enhancements
Firewall Support of HTTPS Authentication Proxy
Frame Relay Voice-Adaptive Traffic Shaping
G.732 Support for the Integrated Signaling Link Terminal
Gatekeeper Management Statistics
GLBP: Gateway Load Balancing Protocol
H.323v4 Gateway Zone Prefix Registration Enhancements
Integrated IS-IS Multi-Topology Support for IPv6
Integrated IS-IS Nonstop Forwarding (NSF) Awareness
Integrated Voice and Data WAN on T1/E1 Interfaces Using the AIM-ATM-VOICE-30 Module
IP Access List Entry Sequence Numbering
IPv6 Provider Edge Router over MPLS
ISDN Generic Transparency Descriptor (GTD) for Setup Message
ISDN Progress Indicator Support for SIP Using 183 Session Progress
L2TP Dial-Out Load Balancing and Redundancy
L2TP Large-Scale Dial-Out per-User Attribute via AAA
Malicious Caller Identification (MCID) Invocation Support for Enterprise Networks
Measurement-Based Call Admission Control for SIP
MGCP 1.0 Including NCS 1.0 and TGCP 1.0 Profiles
MGCP Based Fax (T.38) and DTMF Relay
MGCP Basic CLASS and Operator Services
MGCP VoIP Call Admission Control
Mobile IP—Home Agent Accounting
MPLS VPN Support for EIGRP Between Provider Edge (PE) and Customer Edge (CE)
Multicast Subsecond Convergence
Multiple OPC Support for the Cisco Signaling Link Terminal
NAT Support for IPSec ESP—Phase II
Network-Based Application Recognition Protocol Discovery Management Information Base
OSPF Forwarding Address Suppression in Translated Type-5 LSAs
OSPF Inbound Filtering Using Route Maps with a Distribute List
OSPF Nonstop Forwarding (NSF) Awareness
OSPF Shortest Path First Throttling
OSPF Support for Fast Hello Packets
Per-User QoS via AAA Policy Name
RADIUS Support of 56-Bit Acct Session-Id
RADIUS Timeout Set During Pre-Authentication
RSVP Support for RTP Header Compression, Phase 1
SIP Call Transfer and Call Forwarding Supplementary Services
SIP—Configurable PSTN Cause Code Mapping
SIP Diversion Header Implementation for Redirecting Number
SIP—DNS SRV RFC2782 Compliance
SIP Gateway Support for Third Party Call Control
SIP Gateway Support of RSVP and TEL URL
SIP INVITE Request with Malformed Via Header
SIP: ISDN Suspend/Resume Support
SIP—Session Initiation Protocol for VoIP Enhancements
Source Interface Selection for Outgoing Traffic with Certificate Authority
Support for Bridged RFC 1483 Encapsulated Traffic over ATM SVCs
Support for IUA with SCTP for Cisco Access Servers
T1 Channel Associated Signaling (CAS)
Tunneled GR-303 for the Cisco Cable Modem
UDP Forwarding Support of IP Redundancy Virtual Router Group (VRG)
V.92 and V.44 Support for Digital Modems
XML Interface to Syslog Messages
New Hardware Features Supported in Cisco IOS Release 12.2(13)T
Catalyst 4224 Access Gateway Switch
Cisco 3631 Router Enhanced Functionality
Cisco 3725 Router, Cisco 3745 Router, Cisco 2691 Router Enhanced Functionality
Cisco 7401 ASR-BB and Cisco 7401 ASR-CP
Content Engine Network Module for Caching and Content Delivery
Unchannelized support for PA-MC-2T3+ port adapter
Update to the Enhancements for the Cisco Voice Gateway 200
New Software Features in Cisco IOS Release 12.2(13)T
Advanced Encryption Standard (AES)
Analog DID (Direct Inward Dial)
ATM Multilink PPP Support on Multiple VCs
ATM Policing by Service Category for SVC/SoftPVC
Automatic Protection Switching (APS)
BGP 4 MIB Support for per-Peer Received Routes
Bisync-to-IP Conversion for Automated Teller Machines
Call Admission Control for H.323 VoIP Gateways
Call Release Source Reporting in Gateway-Generated Call Accounting Records
CEF and Distributed CEF Switching for IPv6
Cisco Conferencing and Transcoding for Voice Gateway Routers
Cisco IOS Software Feature Removal
Cisco IOS Telephony Service (ITS) Version 2.02
Cisco Mobile Networks—Asymmetric Link
Cisco Mobile Networks—Dynamic Network Support
Cisco Survivable Remote Site Telephony Service V2.02
Class-Based RTP and TCP Header Compression
Connection-Oriented Media (Comedia) Enhancements for SIP
Dial-Peer Support for Data Calls
Distributed IPv6 for Cisco IOS software
DLR Enhancements: PGM RFC-3208 Compliance
Dual Serial Line Management to Interface Lucent 5ESS
Dynamic Multipoint VPN (DMVPN)
Dynamic Subscriber Bandwidth Selection
Enhanced Features for Local and Advanced Voice Busyout
Enhanced ITU-T G.168 Echo Cancellation
Enhancements for the Cisco Voice Gateway 200
Exterior Gateway Protocol (EGP)
File System Check and Repair for PCMCIA ATA Disks
Frame Relay PVC Bundles with IP and MPLS QoS Support
Frame Relay Queueing and Fragmentation at the Interface
H.323 Call Redirection Enhancements
H.323 Dual Tone Multifrequency Relay Using Named Telephone Events
H.323 Scalability and Interoperability Enhancements
H.323 Support for Virtual Interfaces
Interim Local Management Interface (ILMI)
Interim-Interswitch Signaling Protocol (IISP)
Interim Update at Call Connect
Interior Gateway Routing Protocol (IGRP)
IPv6 ADSL and Dial Deployment Support
IPv6 Extended Access Control Lists
Low Latency Queueing (LLQ) for IPSec
LZ Software with Hardware Encryption
Manual Certificate Enrollment (TFTP and Cut-and-Paste)
MGCP 1.0 and TGCP 1.0 Profiles
MGCP Gateway Support for the Bind Command
Mobile IP—Challenge/Response Extensions
Mobile IP—Fastswitching Support on Foreign Agent
Mobile IP—Generic NAI Support and Home Address Allocation
Mobile IP Home Agent Policy Routing
Mobile IP —IPsec for Home Agent to Foreign Agent Tunnel
Mobile IP—MIB Support for NAI and HA Redundancy
Mobile IP—Private Addressing Support
Mobile IP—Support for FA Reverse Tunneling
Modular QoS CLI (MQC)-Based Frame-Relay Traffic Shaping
Modular QoS CLI (MQC) Three-Level Hierarchical Policer
Modular QoS CLI (MQC) Unconditional Packet Discard
MPLS Label Distribution Protocol (LDP) MIB
MPLS VPN—Carrier Supporting Carrier—IPv4 BGP Label Distribution
MPLS VPN—Inter-AS—IPv4 BGP Label Distribution
Multicast-VPN—IP Multicast Support for MPLS VPNs
NAT Integration with MPLS VPNs
NAT Stateful Failover of Network Address Translation
NAT-Support of H.323 v2 Call Signaling
NetWare Link Services Protocol (NLSP)
Next Hop Resolution Protocol (NHRP) for IPX
OSPF Support for Multi-VRF on CE Routers
Packet Classification Based on Layer 3 Packet Length
Packet Classification Using the Frame Relay DLCI Number
Percentage-Based Policing and Shaping
RADIUS Attribute 52 and Attribute 53 Gigaword Support
RADIUS Centralized Filter Management
RSVP Refresh Reduction and Reliable Messaging
Show Command Output Redirection
Simple Multicast Routing Protocol (SMRP) for AppleTalk
SIP and H.323 Fax Enhancements
SIP—Call Transfer Enhancements Using the Refer Method
SIP Enhanced 180 Provisional Response Handling
SIP Extensions for Caller Identity and Privacy
SIP Gateway Compliance to RFC2543-bis-04
SIP Redirect Processing Enhancements
Subscriber Service Switch (SSS)
Support for IPsec ESP Through NAT
Terminal Line Security for PAD Connections
Update to the Interworking of Cisco MGCP Voice Gateways and Cisco CallManager Version 3.2 Feature
Update to the playout-delay Command
Virtual Router Redundancy Protocol (VRRP)
X.25 Suppression of Security Signaling Facilities
New Hardware Features Supported in Cisco IOS Release 12.2(11)T1
Hardware Platforms and Modules Newly Supported in Cisco IOS Release 12.2(11)T
16-Port Ethernet Switch Module for Cisco 2600 Series and Cisco 3600 Series
Cisco AS5350 Universal Gateway
Cisco AS5850 Universal Gateway
Cisco Signaling Link Terminal (SLT) Dual Ethernet
New Software Features in Cisco IOS Release 12.2(11)T
Accounting of VPDN Disconnect Cause
ACL Authentication of Incoming rsh and rcp Requests
Analog Centralized Automatic Message Accounting E911 Trunk
ATM Service Level Monitoring (SLM)
Barge-In and Busy Line Verify Operator Services
Basic Service Relationships (H.225 Annex G)
BGP Conditional Route Injection
BGP Hide Local-Autonomous System
BGP Multipath Load Sharing for Both eBGP and iBGP in an MPLS-VPN
BGP Prefix-Based Outbound Route Filtering
Call Admission Control Based on CPU Utilization
Call Admission Control for H.323 VoIP Gateways
Call Status Tracking Optimization
Call Tracker show Commands Extensions
Certificate Enrollment Enhancements
Circuit Interface Identification Persistence for SNMP
Cisco Gateway Management Agent
Cisco H.323 Multizone Enhancements
Cisco IOS Telephony Service Version 2.0
CISCO-BULK-FILE-MIB Enhancements
CISCO-SIP-UA-MIB Enhancements Providing Functional Parity to SIP related CLI
Configuring a Gatekeeper to Provide Nonavailability Information for Terminating Endpoints
Connect-Info RADIUS Attribute 77
Customer Profile Idle Timer Enhancements for Interesting Traffic
DF Bit Override Functionality with IPSec Tunnels
DHCP Client—Dynamic Subnet Allocation API
DHCP Relay Agent Support for Unnumbered Interfaces
DHCP Server—On-Demand Address Pool Manager
DHCP Server—Option to Ignore All BOOTP Requests
Distributed Management Event and Expression MIB Persistence
Distributed Management Event MIB Conformance to RFC 2981
DTMF Events Through SIP Signaling
DTMF Relay for SIP calls Using Named Telephone Events
Enable Multilink PPP via RADIUS for Preauthentication User
Encrypted Vendor-Specific Attributes
Enhanced Codec Support for SIP Using Dynamic Payloads
Enhanced Debug Capabilities for Cisco Voice Gateways
Enhancements for the Cisco VG200 Voice Gateway
Enhancing Raw Buffer Management: Audit and Prepopulation for Channel-Associated Signaling
Fax and Modem Pass-Through over VoIP
Fax Detection (Single-number Voice and Fax)
Fax Relay Packet Loss Concealment
G.Clear, GSMFR, and G.726 Codecs and Modem and Fax Pass-Through for Cisco Universal Gateways
Gatekeeper Endpoint Control Enhancements
Gatekeeper-to-Gatekeeper Authentication
Generic Routing Encapsulation (GRE) Tunnel Keepalive
Globalized Cadence and Tone for Cisco IOS Gateways
GTD for GKTMP using SS7 Interconnect version 2.0
H.323 Call Redirection Enhancements
H.323 Dual Tone Multifrequency (DTMF) Relay Using Named Telephone Events
IGMP MIB Support Enhancements for SNMP
Integrated Signaling Link Terminal
Integrated IS-IS Point-to-Point Adjacency Over Broadcast Media
Interactive Voice Response Version 2.0 on VoIP Gateways
Inter-Domain Gatekeeper Security Enhancement
Interface Alias Long Name Support
Internal Cause Code Consistency Between SIP and H.323
Interworking of Cisco MGCP Voice Gateways and Cisco CallManager Version 3.2
Interworking Signaling Enhancements for H.323 and SIP VoIP
ip dhcp-client default-router distance value Command
IPSec VPN High Availability Enhancements
ISDN and V.120 Support for NextPort DSPs
ISDN-NFAS with D Channel Backup
IVR: Configuring Dynamic Prompts
IVR: Customizing Accounting Templates
IVR: Enhanced Multilanguage Support
Location Confirmation (LCF) Enhancements for Alternate Endpoints
Low Latency Queueing with Priority Percentage Support
Media Gateway Control Protocol-Based Fax (T.38) and Dual Tone Multifrequency (IETF RFC 2833) Relay
MGCP 1.0 Including NCS 1.0 and TGCP 1.0 Profiles
MGCP Basic CLASS and Operator Services
MGCP Generic Configuration Support for Call Manager (IP-PBX)
MGCP Line Package Enhancements for Loop Current Feed Open (LCFO)
MGCP PRI Backhaul and T1-CAS Support for Call Manager (IP-PBX)
MGCP Voice on Cisco AS5850 Universal Gateway
MGCP VoIP Call Admission Control
Modem Relay Support on VoIP Platforms
Modem Script and System Script Support in Large-Scale Dial-Out
Monitoring Voice and Fax Services on the Cisco AS5350 and Cisco AS5400 Universal Gateways
MPLS Label Distribution Protocol (LDP)
Multicast Music on Hold Support for Call Manager (IP-PBX)
NetFlow Multiple Export Destinations
NetFlow ToS-Based Router Aggregation
Network Access Server (NAS) Package for MGCP
Network Side ISDN PRI Signaling, Trunking, and Switching
Nonblocking Gatekeeper AAA Interface
OSPF Sham-Link Support for MPLS VPN
OSPF Stub Router Advertisement
OSPF Update Packet-Pacing Configurable Timers
PIAFS Wireless Data Protocol Version 2.1 for Cisco MICA Modems
PIM MIB Extension for IP Multicast
Preauthentication with ISDN PRI and Channel-Associated Signalling Enhancements
PRI Backhaul Using the Stream Control Transmission Protocol and the ISDN Q.921 User Adaptation Layer
PRI/Q.931 Signaling Backhaul for Call Agent Applications
R2 and ISUP Transparency and R2-to-ISUP Interworking Enhancements
RADIUS Attribute 66 (Tunnel-Client-Endpoint) Enhancements
RADIUS Attribute 82: Tunnel Assignment ID
RADIUS Attribute Value Screening
RADIUS Number Translation VSAs for VoIP
RADIUS Packet Suppression for VoIP GW Rotary Dial-Peer Attempts
RADIUS Preauthentication for H.323 and SIP Voice Calls
RADIUS Tunnel Preference for Load Balancing and Fail-over
Reverse Path Forwarding - Source Exists Only
Route Switch Controller (RSC) Handover Redundancy
Router-Shelf Redundancy for the AS5800 Series
SGCP RSIP and AUEP Enhancement
Shell-Based Authentication of VPDN Users
SIP—Call Transfer Using Refer Method
SIP Carrier Identification Code
SIP—Configurable PSTN Cause Code Mapping
SIP—DNS SRV RFC2782 Compliance
SIP Diversion Header Implementation for Redirecting Number
SIP—Enhanced Billing Support for Gateways
SIP Gateway Support for the Bind Command
SIP Gateway Support for Third Party Call Control
SIP Gateway Support of RSVP and TEL URL
SIP INFO Method for DTMF Tone Generation
SIP INVITE Request with Malformed Via Header
SIP—Session Initiation Protocol for VoIP
SIP—Session Initiation Protocol for VoIP Enhancements
SIP T.37 Store and Forward Fax
Speech Recognition and Synthesis for Voice Applications
Static Cache Entry for IPv6 Neighbor Discovery
Survivable Remote Site Telephony Version 2.0
TCL IVR 2.0 Call Initiation and Callback
TCL IVR Disconnect Cause-Code Manipulation
TCL-Enabled Signaling Parameter Mapping
Timer and Retry Enhancements for L2TP and L2F
Universal Port Resource Pooling for Voice and Data Services
V.44 LZJH Compression for Cisco AS5300 and Cisco AS5800 Universal Access Servers
V.92 Modem on Hold for Cisco AS5300 and Cisco AS5800 Universal Access Servers
V.92 Quick Connect for Cisco AS5300 and Cisco AS5800 Universal Access Servers
VoAAL2 Profile 9 Support for Broadband Loop Emulation Services Specification Interoperability
Voice Application Access To SS7 Signaling
Voice DSP Control Message Logger
Voice over IP Q.SIG Network Transparency
VoiceXML SS7 ISUP Session Variables
VoiceXML Media Volume and Rate Controls
VoiceXML Transfer Enhancements
VoiceXML Voice Store and Forward
VoIP Call Admission Control using RSVP
VoIP Interoperability with Cisco Express Forwarding and Policy Based Routing
VoIP Gatekeeper Trunk and Carrier Based Routing Enhancements
VoIP Gateway Trunk and Carrier Based Routing Enhancements
VoIP Outgoing Trunk Group Identification and Carrier ID for Gateways
VPN Routing Forwarding (VRF) Framed Route (Pool) Assignment via PPP
WRED Enhancement—Explicit Congestion Notification (ECN)
X.25 Record Boundary Preservation for Data Communications Networks
Hardware Platforms and Modules Newly Supported in Cisco IOS Release 12.2(8)T1
36-Port Ethernet Switch Module for Cisco 2600 Series and Cisco 3600 Series
New Software Features in Cisco IOS Release 12.2(8)T1
MPLS Label Switch Controller and Enhancements
Hardware Platforms and Modules Newly Supported in Cisco IOS Release 12.2(8)T
1- and 2-Port V.90 Modem WICs for Cisco 2600 and 3600 Series
16-Port Ethernet Switch Module for Cisco 2600 Series and Cisco 3600 Series
AIM-ATM, AIM-VOICE-30, and AIM-ATM-VOICE-30 on the Cisco 2600 Series and Cisco 3660
Analog Station Interface (ASI) Cards
Cisco 806 Broadband Gateway Router
Cisco 3725 Application Service Router
Cisco 3745 Application Service Router
Cisco High-Density Analog Voice and Fax Network Module
Cisco IOS Voice Features on IGX 8400 Series Universal Router Module
Digital J1 Voice Interface Card
Multichannel STM-1 Port Adapter
NM-AIC-64, Contact Closure Network Module
New Software Features in Cisco IOS Release 12.2(8)T
ACL Authentication of Incoming rsh and rcp Requests
Asynchronous Serial Traffic Over User Datagram Protocol (UDP)
ATM PVC Bundle Enhancement—MPLS EXP-Based PVC Selection
ATM Software Segmentation and Reassembly (SAR)
ATM SVC Troubleshooting Enhancements
BGP Hide Local-Autonomous System
BIP—BSC to IP Conversion for Automated Teller Machines
Call Admission Control for H.323 VoIP Gateways
CDP and ODR Support for ATM PVCs
Cisco Discovery Protocol (CDP)— IPv6 Address Family Support for Neighbor Information
CEF-Switched Multipoint GRE Tunnels
Certificate Enrollment Enhancements
CISCO-BULK-FILE-MIB Enhancements
Cisco Gateway Management Agent (CGMA) Phase 2
Cisco IOS Firewall Performance Improvements
Cisco IOS Telephony Service Version 2.0
Cisco Service Assurance Agent Support for the Cisco 820 Series and SOHO 70 Series
Class-Based Weighted Fair Queueing (CBWFQ)
Configurable PSTN Cause Code to SIP Response Mapping
DHCP Client—Dynamic Subnet Allocation API
DHCP Server—On-Demand Address Pool Manager
DHCP Server—Option to Ignore All BOOTP Requests
DHCP Server Options Import and Autoconfiguration
Dialer Map VRF-Aware for an MPLS VPN
Diff-Serv-aware MPLS Traffic Engineering
DistributedDirector Boomerang Support
DistributedDirector Cache Auto Refresh
DistributedDirector Configurable Cache
DistributedDirector MIB Support
Distributed LFI/dQoS over Leased Lines
Distributed Multilink Point-to-Point Protocol
DNS Client AAAA Record Lookups over IPv6
Dual Tone Multifrequency (DTMF) Relay for SIP Calls Using Named Telephone Events
Enabling Fax Rate on POTS to POTS Fax Calls
Encrypted Vendor-Specific Attributes
Enhanced Billing Support for SIP Gateways
Fax Detection for Cisco 2600 Series and Cisco 3600 Series Routers
Gatekeeper Transaction Message Protocol Interface Resiliency Enhancement
Generic Routing Encapsulation (GRE) Tunnel Keepalive
GKTMP Security Token Enhancement
IGMP Version 3—Explicit Tracking of Hosts, Groups, and Channels
Integrated IS-IS Point-to-Point Adjacency Over Broadcast Media
Integrated IS-IS Support for IPv6
Interactive Voice Response Version 2.0 on VoIP Gateways
IPSec VPN High Availability Enhancements
Large-Scale Dial-Out (LSDO) VRF Aware
Media Gateway Control Protocol Based Fax (T.38) and Dual Tone Multifrequency (IETF RFC 2833) Relay
MGCP VoIP Call Admission Control
MPLS Label Distribution Protocol (LDP)
MPLS Over ATM: Virtual Circuit (VC) Merge
MPLS Traffic Engineering (TE) MIB
MPLS VPN Carrier Supporting Carrier
Multiprotocol BGP (MP-BGP) Support for CLNS
Network-Based Application Recognition RTP Payload Type Classification
Nonstop Forwarding Enhanced FIB Refresh
OSPF Sham-Link Support for MPLS VPN
Policer Enhancement—Multiple Actions
Secure Shell (SSH) Support over IPv6
Secure Shell (SSH) Version 1 Server Support
Session Initiation Protocol (SIP) for VoIP
Simple Network-Enabled Auto-Provisioning for Cisco IAD2420 Series IADs
SIP Gateway Support for the Bind Command
SIP Gateway Support of RSVP and TEL URL
SIP INVITE Request with Malformed Via Header
SIP T.37 Store and Forward Fax
SIP—Call Transfer Using Refer Method
SIP—DNS SRV RFC2782 Compliance
SNMP IF-MIB Support for VLAN (ISL, 802.1Q) Subinterfaces
Static Cache Entry for IPv6 Neighbor Discovery
Stream Control Transmission Protocol (SCTP) Release 2
Survivable Remote Site Telephony Version 1.0
Survivable Remote Site Telephony Version 2.0
T.37 Store-and-Forward Fax for Cisco 1751 Modular Access Routers
T.37 Store-and-Forward Fax for the Cisco 2600 Series and Cisco 3600 Series Routers
Unspecified Bit Rate Plus (uBR+) and ATM Enhancements for Service Provider Integrated Access
Update to the MGCP 1.0 Including NCS 1.0 and TGCP 1.0 Profiles
VoAAL2 Profile 9 Support for BLES Interoperability
Voice Support for Japan on Cisco 800 Series Routers, Phase 2
VPN Routing Forwarding (VRF) Framed Route (Pool) Assignment via PPP
WRED Enhancement—Explicit Congestion Notification (ECN)
X.25 Record Boundary Preservation for Data Communications Networks
Hardware Platforms and Modules Newly Supported in Cisco IOS Release 12.2(4)T
1-Port ADSL WAN Interface Card
1-Port T1/E1 Digital Voice Port Adapters for Cisco 7200 and Cisco 7500
8-Port Mix-Enabled T1/E1/PRI PA
Cisco uBR925 Cable Access Router
Cisco CVA122 Cable Voice Adapter
Cisco CVA122E Cable Voice Adapter
New Software Features in Cisco IOS Release 12.2(4)T
Ability to Disable Xauth for Static IPSec Peers
Accounting of VPDN Disconnect Cause
Adaptive Frame Relay Traffic Shaping for Interface Congestion
ATM SNMP Trap and OAM Enhancements
AutoInstall over Frame Relay-ATM Interworking Connections
Automatic Bandwidth Adjustment for MPLS Traffic Engineering Tunnels
BGP Conditional Route Injection
BGP Multipath Load Sharing for Both eBGP and iBGP in an MPLS-VPN
BGP Prefix-Based Outbound Route Filtering
Call Admission Control for H.323 VoIP Gateways
Circuit Interface Identification Persistence for SNMP
Cisco H.323 Scalability and Interoperability Enhancements
Crashinfo Support for Cisco 3600 Series
DFP Support in DistributedDirector
Diff-Serv-aware Traffic Engineering
Distinguished Name Based Crypto Maps
Distributed Link Fragmentation and Interleaving
DistributedDirector Enhancements
Distributed Management Event and Expression MIB Persistence
DNS Server Support for NS Records
Enhancements to H.323 Call Statistics
Four SS7 Link Support on the Cisco Signaling Link Terminal
ICMP ECHO-Based RTT Probing by DRP Agents
IGMP MIB Support Enhancements for SNMP
Inter-Domain Gatekeeper Security Enhancement
Interesting Traffic PPP and Customer Profile Idle Timer
IP to ATM Class of Service Mapping for SVC Bundles
IPSec MIB Support for VPN Management
ISIS: Allows BGP to Control the Configuration of the Overload Bit
Leased and Switched BRI Interfaces for ETSI NET3
Location Confirmation Enhancements for Alternate Endpoints
MGCP 1.0 Including NCS 1.0 and TGCP 1.0 Profiles
MGCP Voice Gateway Interoperability with Cisco CallManager
Mobile IP MIB Support for SNMP
MPLS Label Switch Controller and Enhancements
MPLS Traffic Engineering (TE)—Automatic Bandwidth Adjustment for TE Tunnels
MPLS Traffic Engineering (TE)—IP Explicit Address Exclusion
Multiservice Interchange (MIX) Support
NAT—Ability to Use Route Maps with Static Translations
NAT—Static Mapping Support with HSRP for High Availability
NAT—Translation of External IP Addresses Only
NetFlow Multiple Export Destinations
NetFlow ToS-Based Router Aggregation
Offload Server Accounting Enhancement
OSPF Stub Router Advertisement
OSPF Update Packet-Pacing Configurable Timers
PIM MIB Extension for IP Multicast
PPPoA/PPPoE Autosense for ATM PVCs
PRI Backhaul Using the Stream Control Transmission Protocol and the ISDN Q.921 User Adaptation Layer
PRI/Q.931 Signaling Backhaul for Call Agent Applications
PSTN Fallback for Cisco 7200 and 7500 Series Routers
RADIUS Attribute 82: Tunnel Assignment ID
RADIUS Tunnel Preference for Load Balancing and Fail-Over
RSVP Support for Low Latency Queueing
SS7 Four-Link Support for Cisco Signaling Link Terminal
Stream Control Transmission Protocol (SCTP), Release 1
T.38 Fax Services for Cisco 1750 Access Routers
Timer and Retry Enhancements for L2TP and L2F
Using 31-Bit Prefixes on IPv4 Point-to-Point Links
Hardware Platforms and Modules Newly Supported in Cisco IOS Release 12.2(2)T
1-Port ADSL WAN Interface Card
Cisco uBR905 Cable Access Router
Small Office, Home Office ADSL Router
WT-2750 Multipoint Broadband Wireless System
New Software Features in Cisco IOS Release 12.2(2)T
56K CSU Support for the Cisco Signaling Link Terminal
Analog DID for Cisco 2600 and Cisco 3600 Series Routers
ATM PVC Range and Routed Bridge Encapsulation Subinterface Grouping
Circuit Interface Identification Persistence for SNMP
Cisco High-Performance Gatekeeper
Cisco IOS Server Load Balancing
Cisco Signaling Link Terminal G.732 Support
Cisco Quality of Service Device Manager 2.0 Support for Cisco 1700 Series Routers
Classifying VoIP Signaling and Media with DSCP for QoS
DF Bit Override Functionality with IPSec Tunnels
DFP Support in DistributedDirector
DHCP Option 82 Support for Routed Bridge Encapsulation
Distributed Time-Based Access Lists
DNS Server Support for NS Records
Enhanced Multilingual Support for Cisco IOS Integrated Voice Response
Firewall Feature Set for Cisco 820 Series Routers
Frame Relay Discard Eligibility Bit Setting
Frame Relay Point-Multipoint Wireless
Functionality Changed for the tunnel mpls traffic-eng autoroute metric Command
FXO Answer and Disconnect Supervision
H.323 Call Redirection Enhancements
Interactive Voice Response Version 2.0 on Cisco VoIP Gateways
Interface Alias Long Name Support
IP Header Compression Enhancement—PPPoATM and PPPoFR Support
IPSec and 3DES Feature Set for Cisco 820 Series Routers
Low Latency Queueing with Priority Percentage Support
MGCP CAS PBX and PRI Backhaul on Cisco 7200 Series Routers
MGCP CAS PBX and AAL2 PVC with Basic CLASS and Operator Services
MGCP VoIP Signaling for 1750 Series
Mobile IP MIB Support for SNMP
Modem Script and System Script Support in Large-Scale Dial-Out
MPLS Label Distribution Protocol
MPLS Label Distribution Protocol MIB
MPLS Label Switching Router MIB
MPLS QoS Multi-VC Mode for PA-A3
NetFlow Multiple Export Destinations
Network-Based Application Recognition
Preauthentication with ISDN PRI and Channel-Associated Signaling Enhancements
Prefix Dial for 800 Series Routers
Quality of Service for Virtual Private Networks
RADIUS Attribute 66 (Tunnel-Client-Endpoint) Enhancements
SA Agent Support for Application Monitoring, Frame Relay, VoIP, and MPLS VPN
Secure Shell Terminal-Line Access
Shell-Based Authentication of VPDN Users
SIP Diversion Header Implementation for Redirecting Number
SIP Gateway Support for Third-Party Call Control
SNMP Trap Support for the Virtual Switch Interface Master MIB
Supplementary Telephone Services for the Euro-ISDN Switch
TCL IVR disconnect cause-code Manipulation
Trimble Palisade NTP Synchronization Driver for the Cisco 7200 Series Routers
Using 31-bit Prefixes on IPv4 Point-to-Point Links
Voice over ATM with AAL2 Trunking on Cisco 7200 Series Routers
X.25 Annex G Session Status Change Reporting
Deprecated and Replacement MIBs
SNMP Version 1 BGP4-MIB Limitations
Important Notes for Cisco IOS Release 12.2(15)T9
Cisco Images Deferred Because of Caveat CSCec46250
Cisco Images Deferred Because of Caveat CSCec46250
Important Notes for Cisco IOS Release 12.2(15)T8
Cisco Images Deferred Because of Caveats CSCec46250 and CSCin50865
Cisco Images Deferred Because of Caveat CSCec46250
Cisco Images Deferred Because of Caveat CSCec46250
Important Notes for Cisco IOS Release 12.2(15)T5
Cisco Images Deferred Because of Caveat CSCea91464
Important Notes for Cisco IOS Release 12.2(15)T4
Images Deferred Because of Caveats CSCea21186, CSCeb07534, CSCeb07595, and CSCeb10053
Important Notes for Cisco IOS Release 12.2(15)T3
Important Notes for Cisco IOS Release 12.2(15)T1
Images Deferred Because of Caveat CSCin40652
Important Notes for Cisco IOS Release 12.2(15)T
Cisco Images Deferred Because of Caveat CSCdy01600
Important Notes for Cisco IOS Release 12.2(13)T1
Cisco 1600 Series Router Images Deferred Because of Caveat CSCdz38371
Important Notes for Cisco IOS Release 12.2(13)T
Configuring MD5 Authentication for BGP Peering Sessions
Cisco 1600 Series Router Images Deferred Because of Caveat CSCdz38371
Cisco 3620 Series Router Images Deferred Because of Caveat CSCdz45923
Cisco AS5800 Images Deferred Because of Caveats CSCdz04856, CSCdz09639, CSCdz26779, and CSCdy87529
Cisco Catalyst 4000 Access Gateway Module Images Deferred Because of Caveat CSCdz27525
Cisco Images Deferred Because of Caveat CSCdy01600
Important Notes for Cisco IOS Release 12.2(11)T9
Cisco AS5850 Images Deferred Because of Caveat CSCec06547
Important Notes for Cisco IOS Release 12.2(11)T8
Cisco AS5850 Images Deferred Because of Caveat CSCec06547
Important Notes for Cisco IOS Release 12.2(11)T6
Cisco AS5850 Images Deferred Because of Caveat CSCec06547
Important Notes for Cisco IOS Release 12.2(11)T5
Cisco AS5850 Images Deferred Because of Caveat CSCec06547
Important Notes for Cisco IOS Release 12.2(11)T3
Cisco IAD2420 Images Deferred Because of Caveat CSCdz62759
Important Notes for Cisco IOS Release 12.2(11)T2
Update to the mgcp fax t38 Command
Important Notes for Cisco IOS Release 12.2(11)T
Cisco Catalyst 4000 Access Gateway Module Images Deferred Because of Caveat CSCdy17203
Cisco H.235 Accounting and Security Enhancements for Cisco Gateways
Cisco Images Deferred Because of Caveat CSCdy01600
Detecting Carrier Sense Errors on the Cisco uBR905 and Cisco uBR925 Cable Access Routers
Displaying Alarm Settings on the Cisco AS5800
Fine-Grain Address Segmentation in Dial Peers
Gatekeeper Alias Registration and Address Resolution Enhancements
MICA and NextPort Modem Tech-Support Commands for the AS5xxx Platforms
OSP Client Performance Improvement
SS7 Interconnect to Lucent 1AESS Switches
Important Notes for Cisco IOS Release 12.2(8)T2
Use 12.2(8)T1 Version of c7200-kboot-mz Image
Important Notes for Cisco IOS Release 12.2(8)T1
Cisco IGX 8400 Series URM Images Deferred Because of Caveat CSCdx41149
Cisco 7200 Series Router Limitation
Important Notes for Cisco IOS Release 12.2(8)T
Changes to Feature Support with Cisco IOS Release 12.2(8)T
Cisco IGX 8400 Series URM Images Deferred Because of Caveat CSCdx41149
Cisco Images Deferred Because of Caveat CSCdy01600
Enhanced Gigabit Ethernet Interface Processor Support on Cisco 7500/RSP Series
MPLS Defects in Cisco IOS Release 12.2(8)T
Important Notes for Cisco IOS Release 12.2(4)T
Cisco 7500 Series Images Deferred Because of Caveat CSCdu01272
Cisco 15104 Optical Networking System Image Deferred
Cisco Images Deferred Because of Caveat CSCdy01600
MPLS VPN with TE and MPLS InterAS Advisory on Cisco IOS Software
Important Notes for Cisco IOS Release 12.2(2)T
Addition of the squeeze Command for Cisco 2600 and Cisco 3600 Series Routers
Changes to the output attenuation Command
Cisco 820 and SOHO 70 Router Images Deferred Because of Caveat CSCds69577
Cisco Catalyst 4000 Gateway Images Deferred Because of Caveats CSCdu59093 and CSCdu63022
Cisco Images Deferred Because of Caveat CSCdy01600
Caveats for Cisco IOS Release 12.2T
New and Changed Information
The following is a list of the new features that are supported in Cisco IOS Release 12.2 T. For additional information regarding the features supported in Cisco IOS Release 12.2T, refer to the new feature documentation at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/index.htm
Determining Platform Support Through Cisco Feature Navigator
Cisco IOS software is packaged in feature sets that are supported on specific platforms. To get updated information regarding platform support for the new features listed in Cisco IOS Release 12.2 T, access Cisco Feature Navigator. Cisco Feature Navigator is regularly updated as new platform support is added for features.
Cisco Feature Navigator is a web-based tool that enables you to determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or release. Under the release section, you can compare releases side by side to display both the features unique to each software release and the features in common.
To access Cisco Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:
Note
MPLS Class of Service is now referred to as MPLS Quality of Service. This transition reflects the growth of MPLS to encompass a wider meaning and highlight the path toward Any Transport over MPLS.
New Hardware Features Supported in Cisco IOS Release 12.2(15)T
The following new hardware features are supported in Cisco IOS Release 12.2(15)T. Some of these features may have been introduced on other hardware platforms in earlier Cisco IOS software releases.
1 Port Enhanced ATM Port Adapter with Support for 8K VCs
The PA-A6 is a series of single-width, single-port, ATM port adapters for Cisco 7200 series and Cisco 7401ASR routers. With advanced ATM features, the PA-A6 supports broadband aggregation, WAN aggregation, and campus/MAN aggregation.
1 and 2-port T1/E1 Multiflex Voice/WAN Interface Card
1- and 2-port T1/E1 Multiflex Voice/WAN interface cards provide basic structured and unstructured service for T1 or E1 networks. The card provides fractional data service and channelized voice services and TDM drop and insert (voice/data integration) services.
1- and 2-Port V.90 Modem WICs for Cisco 1720, 1751 and 1760 Routers
The one- and two-port V.90 Modem WICs expand the extensive range of WICs currently available on these routers. The modem WIC cards provide cost-effective basic telephone service connectivity to allow remote router management, asynchronous Dial-on-Demand routing (DDR) and dial back-up, and low-density remote access server (RAS) services.
Catalyst 4500 Access Gateway Module 16-port RJ21 FXS Module (WS-U4604-16FXS)
The 16-Port RJ21 FXS module for the Catalyst 4500 Access Gateway Module is a high density analog phone and fax interface. By providing service to analog phones and fax machines, the sixteen Foreign Exchange Station (FXS) ports emulate a PSTN central office (CO) or PBX.
Catalyst 4500 AGM Voice/WAN Bundle (WS-X4604-VOICE)
The Cisco Catalyst 4500 AGM Voice/WAN bundle provides integrated telephony and routing services to the Cisco Catalyst 4000 series and Cisco Catalyst 4500 series switches. The Cisco Catalyst 4500 AGM Voice/WAN bundle consists of the following products:
•
•
•
Gigabit Ethernet Network Module
The Gigabit Ethernet (GE) network module provides gigabit connectivity. The throughput of the interface depends on the platform. The network module has one GBIC slot to carry any standard copper or optical Cisco GBIC, including CWDM. The GE network module optimizes the performance for branch office customers by offering a high-speed uplink to both existing and new LAN or WAN environments. The extended reach of the provided fiber connectivity allows customers the option of interconnecting branch offices with Gigabit Ethernet and avoids expensive leased serial lines. Metro area service providers now have additional options when connecting their customers in branch offices to MANs.
The Gigabit Ethernet network module is supported on the following platforms: Cisco 2691, Cisco 3660, Cisco 3725, and Cisco 3745.
MRP300
The Multiservice Route Processor 300 (MRP300) is a voice-and-data-capable router that can carry voice traffic over an IP network and that can link small-to-medium-size remote Ethernet LANs to central offices over WAN links. The MRP300 has a slot for expanding flash memory; two slots that support WICs, VWICs, and VICs; two PVDM slots for adding DSPs; and a DIMM slot for upgrading DRAM.
MRP3-8FXS
The MRP3-8FXS contains an 8-port Foreign Exchange Station (FXS) module and a slot for any VIC, WIC, or VWIC module that supports digital and analog voice trunks and WAN routing interfaces. The MRP3-8FXS is similar to the analog station interface 81 card (ASI81), with the exception that the ASI81 does not have onboard Flash memory.
MRP3-16FXS
The MRP3-16FXS contains a 16-port Foreign Exchange Station (FXS) module. The MRP3-16FXS is similar to the analog station interface 161 card (ASI160), except that the ASI160 does not have onboard Flash memory.
NPE-G1
The NPE-G1 is the first network processing engine for the Cisco 7200 VXR routers to provide the functionality of both a network processing engine and an I/O controller. If used without an I/O controller, an I/O blank panel must be in place.
Although its design provides I/O controller functionality, it can also work with any I/O controller supported in the Cisco 7200 VXR routers. The NPE-G1, when installed with an I/O controller, provides the primary input/out functionality; that is, the NPE-G1 input/out functionality enhances that of the existing I/O controller. However, when both the I/O controller and NPE-G1 are present, the functionality of the auxiliary port and console port are on the I/O controller.
The NPE-G1 maintains and executes the system management functions for the Cisco 7200 VXR routers and also holds the system memory and environmental monitoring functions.
The NPE-G1 consists of one board with multiple interfaces. It is keyed so that it can be used only in the Cisco 7200 VXR routers.
RPM-XF Card for the MGX 8850
The RPM-XF card is a next-generation, high-performance model of the RPM for the MGX 8850 platform, using PXM45 processor modules. It is a router module based on an RM7000A MIPS processing engine.
The RPM-XF hardware provides forwarding technology for packet switching capabilities in excess of 2-million pps. The forwarding engine is packet based and is interfaced to the midplane of the system through a combination of switch interface technologies.
SDH/STM-1 Trunk Card for Cisco AS5850 Universal Gateway
Channelized STM-1 provides a high speed remote access aggregation solution with 63 E1s and 1890 DSO channels. The SDH/STM-1 trunk card is a high density mux/demux card that takes in an STM-1 (SDH) pipe, used to transport up to 1890 DS0 channels. The SDH/STM-1 trunk card provides an ingress connection between the Cisco AS5850 universal gateway and external networks. The SDH/STM-1 trunk card has a 155-mbps channelized SDH physical interface in a standard dial feature card (DFC) format. The SDH interface supports channelization to 64 kbps and connects to single mode fiber optic supporting intermediate reach PPP applications.
New Software Features in Cisco IOS Release 12.2(15)T
The following new features are supported in Cisco IOS Release 12.2(15)T. Some of these features may have been introduced on other hardware platforms in earlier Cisco IOS software releases.
ADSL over ISDN
Cisco 826 routers connect corporate telecommuters and small offices via Internet service providers (ISPs) over asymmetric digital subscriber lines (ADSLs) to corporate LANs and the Internet. The router can provide bridging and multiprotocol routing between LAN and WAN ports. Cisco 826 routers provide connectivity to an ISDN network through an ADSL port.
Note
Any Transport over MPLS (AToM)
Any Transport over MPLS (AToM) transports Layer 2 packets over a Multiprotocol Label Switching (MPLS) backbone. AToM enables service providers to connect customer sites with existing data link layer (Layer 2) networks, by using a single, integrated, packet-based network infrastructure—a Cisco MPLS network. Instead of separate networks with network management environments, service providers can deliver Layer 2 connections over an MPLS backbone. AToM provides a common framework to encapsulate and transport supported Layer 2 traffic types over an MPLS network core. AToM supports the following transport types:
•
•
•
•
•
•
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/atomt/index.htm
ARP Optimization
The Address Resolution Protocol (ARP) is used to map a Layer 3 IP address to a Layer 2 MAC address. A Cisco router stores this mapped information in an ARP table. The ARP table provides MAC rewrite information when the router is forwarding a packet using Cisco Express Forwarding (CEF) or other IP switching technologies.
In previous versions of Cisco IOS software, the ARP table was organized for easy searching on an entry based on the IP address. However, there are cases such as interface flapping on the router and a topology change in the network in which all related ARP entries need to be refreshed for correct forwarding. This situation could consume a significant amount of CPU time in the ARP process to search and clean up all the entries. The ARP Optimization feature improves ARP performance by reducing the ARP searching time by using an improved data structure.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/arpoptim.htm
Asynchronous Call Queueing by Role
The Asynchronous Call Queueing by Role feature allows priority users who are making Telnet connection requests to busy asynchronous rotary groups to be placed at the head of the queue when asynchronous rotary line queueing is enabled. If a second priority user makes a Telnet connection request, this user will be placed behind the first priority user at the head of the queue. This feature allows a priority user to access the first available line. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftasyncq.htm
AutoQoS - VoIP
The AutoQoS - VoIP feature allows you to automate the delivery of quality of service (QoS) on your network, and provides a means for simplifying the implementation and provisioning of QoS for voice over IP (VoIP) traffic. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftautoq1.htm
BGP Hybrid CLI Support
The BGP Hybrid CLI Support feature allows the network operator to configure the Border Gateway Protocol (BGP) using the Network Layer Reachability Information (NLRI) format for IPv4 unicast commands and the address-family identifier (AFI) format for address family commands, such as IPv6, VPNv4, and Connectionless Network Service (CLNS) protocol commands. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftbhycli.htm
BGP Increased Support of Numbered AS-Path Access Lists to 500
The BGP Increased Support of Numbered AS-Path Access Lists to 500 feature is an enhancement for Border Gateway Protocol (BGP) autonomous system access lists. This enhancement increases the maximum number autonomous system access lists from 199 to 500. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftiaaspa.htm
BGP Nonstop Forwarding (NSF) Awareness
Nonstop Forwarding (NSF) awareness allows a router to assist NSF-capable neighbors to continue forwarding packets during a switchover operation or during a well-known failure condition. The BGP Nonstop Forwarding Awareness feature allows an NSF-aware router that is running BGP to forward packets along routes that are already known for a router that is performing a switchover operation or is in a well-known failure mode. This capability allows the BGP peers of the failing router to retain the routing information that is advertised by the failing router and continue to use this information until the failed router has returned to normal operating behavior and is able to exchange routing information. The peering session is maintained throughout the entire NSF operation.
Cisco Nonstop Forwarding (NSF) works with the Stateful Switchover (SSO) feature in Cisco IOS software. SSO is a prerequisite of Cisco NSF. NSF works with SSO to minimize the amount of time a network is unavailable to its users following a switchover. The main objective of Cisco NSF is to continue forwarding IP packets following a Route Processor (RP) switchover. NSF/SSO is configured in the core of your network, and NSF awareness is configured on iBGP peers in the core and the edge of the network.
BGP Restart Session After Max-Prefix Limit
The BGP Restart Session After Max-Prefix Limit feature enhances the capabilities of the neighbor maximum-prefix command with the introduction of the restart keyword. This enhancement allows the network operator to configure the time interval at which a peering session is reestablished by a router when the number of prefixes that have been received from a peer has exceeded the maximum prefix limit. The restart keyword has a configurable timer argument that is specified in minutes. The time range of the timer argument is from 1 to 65535. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftbrsamp.htm
BGP Route-Map Policy List Support
The BGP Route-Map Policy List Support feature introduces new functionality to Border Gateway Protocol (BGP) route maps. This feature adds the capability for a network operator to group route-map match clauses into a named list called a policy list. A policy list functions like a macro within a route map. When the policy list is referenced within a route map with the match policy-list command, all match statements in the policy list are executed. Policy lists can be used for all applications of a route map and for redistribution between routing protocols. Policy lists can coexist with configured match and set clauses within the same subblock. Policy lists, however, do not support set statements, and policy lists are not supported by IP routing policy. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftbgprpl.htm
BRI QSIG Protocol
BRI QSIG is the QSIG support over BRI interface. QSIG protocol support allows Cisco voice gateways to connect PBXs, key telephone systems (KTS), and central office switches that communicate by using the QSIG protocol.
Certificate Security Attribute-Based Access Control
Under the IP Security (IPSec) protocol, certification authority (CA) interoperability permits Cisco IOS devices and a CA to communicate so that the Cisco IOS device can obtain and use digital certificates from the CA. Certificates contain several fields that are used to determine whether a device or user is authorized to perform a specified action. The Certificate Security Attribute-Based Access Control feature adds fields to the certificate that allow specifying an access control list (ACL) to create a certificate-based ACL. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftcrtacl.htm
Cisco Easy VPN Remote Enhancements
The Cisco Easy VPN Remote Enhancements feature improve the capabilities of the Cisco Easy VPN Client feature first delivered in Cisco IOS Release 12.2(4)YA. Additional capabilities include the following:
•
•
•
•
•
•
•
•
•
•
These enhancement were introduced in Cisco IOS Release 12.2(8)YJ to support Cisco 806, Cisco 826, Cisco 827, and Cisco 828 routers; Cisco 1700 series routers; and Cisco uBR905 and Cisco uBR925 cable access routers. This release is adding support for Cisco 2600, Cisco 3600, and Cisco 3700 series routers. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftezvpnr.htm
Cisco IOS Firewall Stateful Inspection of ICMP
The Cisco IOS Firewall Stateful Inspection of ICMP feature addresses the limitation of qualifying Internet Control Management Protocol (ICMP) messages into either a malicious or benign category by allowing the Cisco IOS firewall to use stateful inspection to "trust" ICMP messages that are generated within a private network and to permit the associated ICMP replies. Thus, network administrators can debug network issues without needing to block ICMP messages from entering the network because of possible intruders.
Cisco IOS Firewall Support for SIP
The Cisco IOS Firewall Support for SIP feature integrates Cisco IOS firewalls, the Voice over IP (VoIP) protocol, and Session Initiation Protocol (SIP) within a Cisco IOS based platform, enabling better network convergence.
Cisco IOS Firewall Websense URL Filtering
The Cisco IOS Firewall Websense URL Filtering feature enables your Cisco IOS firewall (also known as Cisco Secure Integrated Software [CSIS]) to interact with the Websense URL filtering software, thereby allowing you to prevent users from accessing specified websites on the basis of some policy. The Cisco IOS Firewall feature works with the Websense server to know whether a particular URL should be allowed or denied (blocked). Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122y/122yu11/ftwebsen.htm
Cisco IOS Software Feature Removal—Phase II
The Cisco IOS Software Feature Removal feature is an engineering project to permanently remove selected legacy features (or components) from the Cisco IOS code. These features will not be available in future releases of Cisco IOS software. The legacy features that have been removed as of Cisco IOS Release 12.2(15)T are as follows:
•
•
•
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftjencrg.htm
Cisco IOS Telephony Service Version 2.1
Cisco IOS Telephony Service (ITS) offers an entry-level IP telephony solution integrated directly into Cisco IOS software. Customers can now deploy voice, data, and IP telephony on a single platform for their small offices. ITS offers a core set of phone features that customers commonly require for their everyday business needs, and leverages the wide array of voice capabilities that are available in Cisco IOS software to provide a very robust IP telephony offering for the small office environment.
Cisco ITS version 2.1 provides support for the following new features:
•
•
•
•
•
•
•
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/itsv21/index.htm
Cisco Mobile Networks—Priority Home Agent Assignment
The mobile router currently preconfigures home agents with different priorities, registering with only the highest priority home agent. However, there are situations in which the mobile router roams to an area where a closer home agent is more desirable to register with. The Cisco Mobile Networks—Priority Home Agent Assignment feature allows a mobile router to register with the closer home agent using the existing home agent priority configurations on the mobile router and care-of address access lists configured on the home agent. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftdynaha.htm
Cisco Mobile Networks—Static Collocated Care-of Address
The Cisco Mobile Networks—Static Collocated Care-of Address feature allows a mobile router to roam to foreign networks where foreign agents are not deployed. Before the introduction of this feature, the mobile router was required to use a foreign agent care-of address when roaming. Now a roaming interface with a static IP address configured on the mobile router itself works as the collocated care-of address (CCoA).
Cisco Mobile Networks—Tunnel Templates for Multicast
The Cisco Mobile Networks—Tunnel Templates for Multicast feature allows the configuration of multicast on statically created tunnels to be applied to dynamic tunnels brought up on the home agent and mobile router. A tunnel template is defined and applied to the tunnels between the home agent and the mobile router. The mobile router can now roam carrying multicast sessions to its mobile networks. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftmultic.htm
Cisco Survivable Remote Site Telephony Version 2.1
The Cisco Survivable Remote Site Telephony (SRST) feature offers enterprises a reliable mechanism for providing continuous IP telephony services to small branch offices in the event of an outage. SRST enables enterprises to build large IP telephony networks using centralized call processing resources.
SRST Version 2.1 provides support for the Cisco IP Phone Extension Module 7914, Unity Voice Mail integration, additional languages for Cisco IP Phone 7940 and Cisco IP Phone 7960 display, higher directory number (DN) maximums, and a new command for creating global prefixes. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/srst21/index.htm
Note
Class-Based Policer for the DiffServ AF PHB
The Class-Based Policer for the DiffServ AF PHB feature is based on RFC 2697 A Single Rate Three Color Marker. The packet stream is metered and packets are marked "conform," "exceed," or "violate." Marking is based on a Committed Information Rate (CIR) and two associated burst sizes, a Committed Burst Size (CBS) and an Excess Burst Size (EBS). A packet is marked "conform" if it does not exceed the CBS, "exceed" if it exceeds the CBS but not the EBS, and "violate" otherwise.
Note
Clear Channel T3/E3 with Integrated CSU/DSU
Nonchannelized (Clear Channel) T3/E3 service is delivered as a T3/E3 pipe with the bandwidth being 28x24x64k for T3 or 16x32x64k for E3. Clear Channel T3/E3 service is generally used in point-to-point applications (one customer sending data to one remote site). Any subdivision of bandwidth is performed at each customer site rather than at the central office. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122y/122yt/122yt11/ft_te3nm.htm
Clear IPC Statistics
This existing feature provides a way to clear and reset the interprocess communications (IPC) statistics. When debugging IPC problems, the ipc stat counters are clearable, making it easier to diagnose the problem.
DHCP Accounting
The DHCP Accounting feature introduces authentication, authorization, and accounting (AAA) and Remote Authentication Dial-In User Service (RADIUS) support for Dynamic Host Configuration Protocol (DHCP) configuration. The introduction of AAA and RADIUS support improves public wireless LAN (PWLAN) security by sending secure START and STOP accounting messages. The configuration of this feature adds a layer of security that allows DHCP lease assignment and termination to be triggered for the appropriate RADIUS START and STOP accounting records so that the session state is properly maintained by upstream devices, such as a Service Selection Gateway (SSG). The additional security provided by this feature can help to prevent unauthorized clients or hackers from gaining illegal entry to the network by spoofing authorized DHCP leases. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftdhcpac.htm
DHCP ODAP Server Support
The DHCP ODAP Server Support feature introduces the capability to configure an IOS Dynamic Host Configuration Protocol (DHCP) server (or router) as a subnet allocation server. This capability allows the IOS DHCP server to be configured with a pool of subnets for lease to On-Demand Address Pool (ODAP) clients. Subnet pools can be configured for global ODAP clients or Multiprotocol Label Switched (MPLS) Virtual Private Network (VPN) ODAP clients on a per-client basis. The DHCP subnet allocation server creates bindings for the subnet leases and stores these leases in the DHCP database. This feature also supports database agents for subnet lease recovery. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftodapss.htm
DHCP Secured IP Address Assignment
The DHCP Secure IP Address Assignment feature introduces the capability to secure ARP table entries to Dynamic Host Configuration Protocol (DHCP) leases in the DHCP database. This feature secures and synchronizes the MAC address of the client to the DHCP binding, preventing unauthorized clients or hackers from spoofing the DHCP server and taking over a DHCP lease of an authorized client. When this feature is enabled and the DHCP server assigns an IP address to the DHCP client, the DHCP server adds a secure ARP entry to the ARP table with the assigned IP address and the MAC address of the client. This ARP entry cannot be updated by any other dynamic ARP packets, and this ARP entry will exist in the ARP table for the configured lease time or as long as the lease is active. The secured ARP entry can be deleted only by an explicit termination message from the DHCP client or by the DHCP server when the DHCP binding expires. This feature can be configured for a new DHCP network or used to upgrade the security of an existing network. The configuration of this feature does not interrupt service and is not visible to the DHCP client. The configuration of this feature does not interrupt service and is not visible to the DHCP client. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftdsiaa.htm
DHCP Server Import All Enhancement
When the import all DHCP pool configuration command is used, the DHCP Server Import All Enhancement feature allows options imported by one subsystem to coexist with options imported from another subsystem. When the session is terminated or the lease is released, the imported options are cleared from the DHCP server database.
DHCP Server—ODAP Support for Non-MPLS VPN Pools
The DHCP Server—On-Demand Address Pool Manager is a feature in which pools of IP addresses can be dynamically increased or reduced in size depending on the address utilization level. On-demand address pools (ODAPs) support address assignment using the Dynamic Host Configuration Protocol (DHCP) for customers using private addresses. Each ODAP is configured and associated with a particular Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN).
The DHCP Server—ODAP Support for Non-MPLS VPN Pools feature enhances the existing feature to provide support for non-MPLS VPN pools. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/ftondhcp.htm
E1 R2 Signaling
R2 signaling is an international signaling standard that is common to channelized E1 networks. The E1 R2 Signaling feature was introduced in Cisco IOS Release 11.3(2)T and is now supported on Cisco 1751 and Cisco 1760 platforms in Cisco IOS Release 12.2(15)T
EIGRP Nonstop Forwarding (NSF) Awareness
Nonstop Forwarding (NSF) awareness allows a router to assist NSF-capable neighbors to continue forwarding packets during a switchover operation or during a well-known failure condition. The EIGRP Nonstop Forwarding Awareness feature allows an NSF-aware router that is running EIGRP to forward packets along routes that are already known for a router that is performing a switchover operation or is in a well-known failure mode. This capability allows the EIGRP peers of the failing router to retain the routing information that is advertised by the failing router and continue to use this information until the failed router has returned to normal operating behavior and is able to exchange routing information. The peering session is maintained throughout the entire NSF operation.
Enhanced Debug Capabilities for Cisco Voice Gateways
The enhanced debugging capability for Cisco voice gateways provides improvements to the debugging output in order to identify and track a specific call in a multiple-call environment. Before the implementation of this feature, it was difficult to correlate call information between gateways or to identify specific debug messages associated with a single call, when multiple voice calls were simultaneously active. The output was unstructured and presented in a free form.
This feature adds a standardized header to the debug outputs of multiple voice modules, such as voice telephony service provider (VTSP), call control application program interface (CCAPI), session application (SSAPP), and interactive voice response (IVR). Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ft_dbgs2.htm
Enhanced Object Tracking
Prior to the introduction of the Enhanced Object Tracking feature, the Hot Standby Router Protocol (HSRP) had a simple tracking mechanism that allowed you to track the interface line protocol state only. If the line protocol state of the interface went down, the HSRP priority of the router was reduced, allowing another HSRP router with a higher priority to become active. The Enhanced Object Tracking feature separates the tracking mechanism from HSRP and creates a separate standalone tracking process that can be used by any other process as well as by HSRP. This feature allows tracking of other objects in addition to the interface line protocol state.
A client process, such as HSRP, Virtual Router Redundancy Protocol (VRRP), or Gateway Load Balancing Protocol (GLBP), can now register with the tracking service, its interest in tracking a particular object, such as an interface or a route, and then be notified when the tracked object changes state. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/fthsrptk.htm
Expanded Scope for Cause-Code-Initiated Call Establishment Retries
The Expanded Scope for Cause-Code-Initiated Call Establishment Retries feature enables the gateway to reattempt calls when a disconnect message is received from the public switched telephone network (PSTN) without maintaining extra dial peers. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ft_ccu.htm
Exporting and Importing RSA Keys
The Exporting and Importing RSA Keys feature allows you to transfer security credentials between devices by exporting and importing RSA keys.
The Exporting and Importing RSA Keys feature allows you to share the private RSA key pair of a router with standby routers, therefore transferring the security credentials between networking devices. The key pair that is shared between two routers will allow one router to immediately and transparently take over the functionality of the other router. If the main router were to fail, the standby router could be dropped into the network to replace the failed router without the need to regenerate keys, reenroll in certification authority (CA), or manually redistribute keys.
You can also use the Exporting and Importing RSA Keys feature to place the same RSA key pair on multiple routers, so that all management stations that use SSH can be configured with a single public RSA key. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ft_key.htm
Fax and Modem Pass-Through over VoIP
Fax and modem pass-through are now supported on the Cisco 1750 and Cisco 1761 platforms beginning in Cisco IOS Release 12.2(15)T.
Note
On detection of the fax or modem tone on an established VoIP call, the gateways switch into modem fax or pass-through mode: the voice codec and configuration is suspended and the pass-through parameters are loaded for the duration of the fax or modem session. This changes the bandwidth needed for the call to the equivalent of G.711.
With pass-through, the fax or modem traffic is carried between the two gateways in RTP packets, using an uncompressed format resembling the G.711 codec. Packet redundancy may be used to mitigate the effects of packet loss in the IP network. Even so, fax and modem pass-through remain susceptible to packet loss, jitter and latency in the IP network. The two endpoints must be clocked synchronously for this type of transport to work predictably.
The Fax and Modem Pass-Through feature is also known as Voice Band Data (VBD) by the International Telecommunication Union (ITU). VBD refers to the transport of fax or modem signals over a voice channel through a packet network with an encoding appropriate for fax or modem signals. The minimum set of coders for VBD mode is G.711 ulaw and alaw with VAD disabled. For modem transport, Echo cancellation is also be disabled.
Firewall Intrusion Detection System Signature Enhancements
Before the Firewall Intrusion Detection System Signature Enhancements, the Cisco Intrusion Detection System (IDS) contained 59 signatures, which was only a small subset of the signatures supported by Cisco Secure IDS. Firewall Intrusion Detection System (IDS) Signature Enhancements introduces 42 additional IDS signatures to Cisco IOS IDS that are supported by other Cisco products, such as PIX; these newly added signatures are categorized as follows:
•
•
•
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122y/122yu11/ft_fwids.htm
Firewall N2H2 Support
The Cisco IOS Firewall N2H2 Support feature provides users with an additional option when choosing the URL filter vendor. Just like the Websense URL filtering server, N2H2 interacts with your Cisco IOS firewall (also known as Cisco Secure Integrated Software [CSIS]) to allow you to prevent users from accessing specified websites on the basis of some policy. The Cisco IOS firewall works with the N2H2 Internet Filtering Protocol (IFP) server to know whether a particular URL should be allowed or denied (blocked). Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122y/122yu11/ft_n2h2.htm
Firewall Support of HTTPS Authentication Proxy
The Firewall Support of HTTPS Authentication Proxy feature allows a user to encrypt the change of the username and password between the HTTP client and the Cisco IOS router via Secure Socket Layer (SSL) when authentication proxy is enabled on the Cisco IOS firewall, thereby ensuring confidentiality of the data that is passing between the HTTP client and the Cisco IOS router. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122y/122yu11/ftfwhttp.htm
Frame Relay Voice-Adaptive Traffic Shaping
The Frame Relay Voice-Adaptive Traffic Shaping feature enables a permanent virtual circuit (PVC) to adjust the rate of traffic on the basis of the presence of packets in the priority queue or H.323 call setup signaling packets. This feature also introduces voice-adaptive fragmentation. Frame Relay voice-adaptive fragmentation allows fragmentation to be turned on when packets are detected in the priority queue or H.323 signaling packets are present and to be turned off when priority queue traffic and signaling packets are not present. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ft_vats.htm
G.732 Support for the Integrated Signaling Link Terminal
The G.732 Support for the Integrated Signaling Link Terminal feature ports the existing International Telecommunication Union Telecommunication Standardization Sector (ITU-T) G.732 bit error rate (BER) detection and alarm processing functionality from the Cisco Signaling Link Terminal (SLT) onto the Cisco AS5350 and Cisco AS5400 network access server (NAS) platforms. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftg7325x.htm
Gatekeeper Management Statistics
The Gatekeeper Management Statistics feature adds support for gatekeeper performance management parameters that provide statistics that may be used to monitor and troubleshoot a network. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ft_gms.htm
GLBP: Gateway Load Balancing Protocol
The Gateway Load Balancing Protocol feature provides automatic router backup for IP hosts configured with a single default gateway on an IEEE 802.3 LAN. Multiple first-hop routers on the LAN combine to offer a single virtual first-hop IP router while sharing the IP packet forwarding load between them. Other routers on the LAN may act as redundant GLBP routers that will become active if any of the existing forwarding routers fail.
This feature was originally introduced in Cisco IOS Release 12.2(14)S. This release is porting the feature into the Cisco 1700 series, Cisco 2600 series, Cisco 3640, and Cisco 3660 platforms. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ft_glbp.htm
H.323v4 Gateway Zone Prefix Registration Enhancements
The H.323v4 Gateway Zone Prefix Registration Enhancements feature provides support for two capabilities included in H.323 version 4: additive registration and dynamic zone prefix registration. Additive registration allows a gateway to add to or modify a list of aliases contained in a previous registration without first unregistering from the gatekeeper. Dynamic zone prefix registration allows a gateway to register actual public switched telephone network (PSTN) destinations served by the gateway with its gatekeeper. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftgwzpre.htm
Hot Standby MAC Address
The Hot Standby MAC Address (HSMA) feature achieves redundancy and fault tolerance and avoids a single point of failure of Cisco Channel Interface Processors (CIPs) or Channel Port Adapters (CPAs). This feature also ensures that multiple devices on the Ethernet can have a common MAC address.
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123newft/123_1/ft_hsma.htm
HTTP 1.1 Client
This feature implements support for HTTP clients within Cisco IOS software compliant with the HTTP 1.1 standard (RFC 2616). The HTTP 1.1 Client allows the network device to contact a remote web server and obtain content or interact with remote applications. The HTTP 1.1 Client is enabled by default on supported platforms.
HTTP 1.1 Web Server
The HTTP 1.1 Web Server feature provides a consistent interface for users and applications by implementing the HTTP 1.1 standard (RFC 2616). Prior to this release, Cisco software supported only a partial implementation of HTTP 1.0. The integrated HTTP Server API supports server application interfaces. When combined with the HTTPS and HTTP 1.1 Client features, the HTTP 1.1 Web Server feature provides a complete, secure solution for HTTP services to and from Cisco devices. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/fthttp1s.htm
HTTPS-HTTP with SSL 3.0
The HTTPS-HTTP with SSL 3.0 feature provides integrated Secure Socket Layer (SSL) 3.0 support for the HTTP 1.1 Server and Client in Cisco IOS software. SSL provides encryption to allow secure HTTP communications. HTTP with SSL (HTTPS) allows for encrypted HTTP communications with Cisco devices.
IGMP State Limit
The IGMP State Limit feature provides protection against denial of service (DoS) attacks caused by Internet Group Management Protocol (IGMP) packets. The new command-line interface (CLI) introduced by this feature allows you to configure a limit on the number of IGMP states that results from IGMP, IGMP Version 3 lite (IGMP v3lite), and URL Rendezvous Directory (URD) membership reports on a per-interface or global basis. Membership reports in excess of the configured limits will not be entered in the IGMP cache, and traffic for those excess membership reports will not be forwarded. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ft_igmps.htm
Implementing OSPF for IPv6
The Open Shortest Path First (OSPF) Version 3 for IPv6 (RFC 2740) feature expands on OSPF to provide support for IPv6 routing prefixes. In OSPF for IPv6, the commands used to customize OSPF are in interface configuration mode rather than router configuration mode. When using a nonbroadcast multiaccess (NBMA) interface in OSPF for IPv6, users must manually configure the router in order to detect neighbors.
Integrated IS-IS Multi-Topology Support for IPv6
The Integrated IS-IS Multi-Topology Support for IPv6 feature provides support for routing IPv6 prefixes in Intermediate System-to-Intermediate System (IS-IS) using a multi-topology solution.
Integrated IS-IS Nonstop Forwarding (NSF) Awareness
The Integrated IS-IS Nonstop Forwarding (NSF) Awareness feature allows customer premises equipment (CPE) routers that are NSF-aware to help NSF-capable routers perform nonstop forwarding of packets. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/isnsfawa.htm
Integrated Voice and Data WAN on T1/E1 Interfaces Using the AIM-ATM-VOICE-30 Module
The Integrated Voice and Data WAN on T1/E1 Interfaces Using the AIM-ATM-VOICE-30 Module feature provides configuration enhancements for the AIM-ATM-VOICE-30 digital signaling processor (DSP) card on the Cisco 2600 series, Cisco 2600XM, Cisco 3660, Cisco 3725, and Cisco 3745. This feature provides a migration path to higher bandwidth without the need to change transport facilities and provides a voice processing (termination) solution with AIM-ATM-VOICE-30 without consuming a network module slot. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftbckaim.htm
IP Access List Entry Sequence Numbering
Users can apply sequence numbers to permit or deny statements and also reorder, add, or remove such statements from a named IP access list. This feature makes revising IP access lists much easier. Prior to this feature, users could add access list entries to the end of an access list only; therefore needing to add statements anywhere except the end required reconfiguring the entire access list.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122s/122snwft/release/122s14/fsaclseq.htm
IPMROUTE-STD-MIB
This feature introduces support for the IPMROUTE-STD-MIB in Cisco IOS software. IPMROUTE-STD-MIB, as defined in RFC 2932, is a module for management of IP multicast routing in a manner independent of the specific multicast routing protocol in use. Support for this MIB replaces the draft form of the IPMROUTE-MIB.
The IPMROUTE-STD-MIB supports all the MIB objects of the IPMROUTE-MIB and in addition supports the following four new MIB objects:
1.
2.
3.
4.
Note
IPSec VPN Accounting
The IPSec VPN Accounting feature allows for a session to be accounted for by indicating when the session starts and when it stops. Additionally, session identifying information and session usage information will be passed to the RADIUS server via RADIUS attributes and vendor-specific attributes (VSAs). Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ft_evpna.htm
IPv6 ISATAP Tunnel Support
The Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) is an automatic overlay tunneling mechanism that uses the underlying IPv4 network as a nonbroadcast multiaccess (NBMA) link layer for IPv6. The IPv4 address is encoded in the last 32 bits of the IPv6 address, enabling automatic IPv6-in-IPv4 tunneling within an IPv4 network. ISATAP tunnels allow individual IPv4/IPv6 dual-stack hosts within a site to connect to an IPv6 network using the IPv4 infrastructure. ISATAP uses a normal global IPv6 prefix (/64), that can be used with both local and global unicast IPv6 prefixes, enabling IPv6 routing on the Internet. For additional information, refer to the following document:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/ipv6_c/sa_tunv6.htm
IPv6 MIB Support
IPv6 MIBs are now available for managing IPv6 traffic. Supported MIBs include the CISCO-IETF-IP-MIB and CISCO-IETF-IP-FORWARDING-MIB.
IPv6 Provider Edge Router over MPLS
The IPv6 Provider Edge Router over MPLS (Cisco 6PE) feature allows service providers that are running an MPLS/IPv4 infrastructure to offer IPv6 services on an Multiprotocol Label Switching (MPLS) network. A Cisco 6PE-enabled backbone allows IPv6 domains to communicate with each other over an MPLS IPv4 core network. A Cisco 6PE implementation requires no backbone infrastructure upgrades and no reconfiguration of core routers, because forwarding is based on labels rather than on the IP header itself.
Additionally, the inherent Virtual Private Network (VPN) and Traffic Engineering (TE) services available within an MPLS environment allow IPv6 networks to be combined into VPNs or extranets over an infrastructure that supports IPv4 VPNs and MPLS-TE.
The provider edge (PE) routers at each end of the MPLS network must be IPv6-enabled. The PE routers apply an appropriate label for the address in the packet to reach the other side of the MPLS backbone. This is similar to tunneling because it allows IPv6 traffic to be transported over MPLS without the routers in the backbone being aware of the IPv6 traffic. An MPLS packet enters and exits the MPLS network on different routers, and each router must be IPv6- and 6PE-enabled.
For more information about the IPv6 Provider Edge Router over MPLS (Cisco 6PE) feature, refer to the following document:
http://www.cisco.com/application/pdf/en/us/guest/products/ps6553/c1161/cdccont_0900aecd80311df4.pdf
ISDN Generic Transparency Descriptor (GTD) for Setup Message
The ISDN Generic Transparency Descriptor for Setup Message feature provides support for mapping ISDN information elements (IEs) to corresponding GTD parameters. Supported IEs and GTD parameters include the following:
•
•
•
•
•
This feature allows networks to do the following:
•
•
Cisco implements this feature on Cisco IOS gateways by providing a mechanism to allow creating and passing the Q931 Setup message and its parameters in a GTD format. The Setup message, sent by the gateway to initiate call establishment, is mapped to the GTD Initial Address Message (IAM). Generic transparency descriptors represent parameters within signaling messages and enable transport of signaling data in a standard format across network components and applications. The GTD mechanism allows them to share signaling data and achieve interworking between different signaling types.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftgtdisd.htm
ISDN PRI-SLT
The ISDN PRI-SLT feature allows you to release the ISDN PRI signaling time slot for Redundant Link Manager (RLM) configurations and for Signaling System 7 (SS7) applications in integrated Signaling Link Terminal (SLT) configurations. This feature supports the use of DS0 time slots for SS7 links and allows the coexistence of SS7 links and PRI voice and data bearer channels on the same T1 or E1 controller span. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122b/122b_8/ftprislt.htm
ISDN Progress Indicator Support for SIP Using 183 Session Progress
The ISDN Progress Indicator Support for SIP Using 183 Session Progress feature adds the SIP 183 Session Progress and Ringing messages to better map to the ISDN/CAS messages.
The ISDN Progress Indicator Support for SIP Using 183 Session Progress feature was previously released in Cisco IOS Release 12.1(5)T. This feature has been added on the Cisco 1751 and the Cisco 1760 in Cisco IOS Release 12.2(15)T.
L2TP Dial-Out Load Balancing and Redundancy
The L2TP Dial-Out Load Balancing and Redundancy feature enables an L2TP network server (LNS) to dial out to multiple L2TP access concentrators (LACs). When the LAC with the highest priority goes down, it is possible for the LNS to failover to another lower priority LAC. The LNS can also load-balance the sessions between multiple LACs that have the same priority settings. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftl2tlbr.htm
L2TP Large-Scale Dial-Out per-User Attribute via AAA
The L2TP Large-Scale Dial-Out per-User Attribute via AAA feature enhances Layer 2 Tunneling Protocol (L2TP) to support per-user attributes using authentication, authorization, and accounting (AAA) for large-scale dial-out. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftl2taaa.htm
Malicious Caller Identification (MCID) Invocation Support for Enterprise Networks
The Malicious Caller Identification (MCID) Invocation Support for Enterprise Networks feature enables a called party inside an enterprise network to use a configurable sequence of digits to notify the local law enforcement agency of a malicious call. MCID uses Tool Command Language (TCL) and interactive voice response (IVR) to trigger the gateway to send calling number information to the authorities.
The feature is platform independent; uses dual tone multifrequency (DTMF) tones to generate the trigger; and operates in both H.323 and Session Initiation Protocol (SIP) voice gateways and on all phones. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftmcid.htm
Measurement-Based Call Admission Control for SIP
The Measurement-Based Call Admission Control for SIP feature implements support within Session Initiation Protocol (SIP) to monitor IP network capacity and check the availability of router and interface resources, and to decide if adequate resources are available to carry a successful Voice over IP (VoIP) session. This feature also implements a mechanism to prevent calls that arrive from the IP network from entering the gateway when required resources are not available to process the call. This feature also provides the ability to support measurement-based call admission control processes as well as check for resource availability. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftcacsip.htm
MGCP 1.0 Including NCS 1.0 and TGCP 1.0 Profiles
The MGCP 1.0 Including NCS 1.0 and TGCP 1.0 Profiles feature implements the following Media Gateway Control Protocol (MGCP) protocols on the supported Cisco media gateways:
•
•
•
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t4/ft_24mg1.htm
Note
MGCP Based Fax (T.38) and DTMF Relay
This feature adds support for T.38 fax relay and dual tone multifrequency (DTMF) relay with Media Gateway Control Protocols (MGCP). This feature provides two modes of implementation for each component: gateway (GW)-controlled mode and call agent (CA)-controlled mode. In GW-controlled mode, GWs negotiate DTMF and fax relay transmission by exchanging capability information in Session Description Protocol (SDP) messages. That transmission is transparent to the CA. GW-controlled mode allows use of the MGCP-Based Fax (T.38) and DTMF (IETF RFC 2833) Relay feature without upgrading the CA software to support the feature. In CA-controlled mode, CAs use MGCP messaging to instruct GWs to process fax and DTMF traffic. For MGCP T.38 Fax Relay, the CAs can also instruct GWs to revert to GW-controlled mode if the CA is unable to handle the fax control messaging traffic; for example, in overloaded or congested networks.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xb/122xb_2/ftmgcpfx.htm
The MGC Protocol Based Fax (T.38) and DTMF (IETF RFC 2833) Relay feature was previously released in Cisco IOS Release 12.2(8)T on the Cisco 3600 series and Cisco MC3810, and in Cisco IOS Release 12.2(11)T on the Cisco AS5300, Cisco AS5400, and Cisco AS5850. This feature has been added on the Cisco 1751 and the Cisco 1760 in Cisco IOS Release 12.2(15)T.
MGCP Basic CLASS and Operator Services
The Media Gateway Control Protocol (MGCP) Basic CLASS and Operator Services feature provides CLASS and 3-way calling functionality using the Simple Gateway Control Protocol (SGCP) and MGCP protocols.
MGCP VoIP Call Admission Control
The MGCP VoIP Call Admission Control (CAC) feature determines if calls can be accepted on the IP network on the basis of available network resources. Before this release, Media Gateway Control Protocol (MGCP) Voice over IP (VoIP) calls were established regardless of the available resources on the gateway or network. The gateway had no mechanism for gracefully refusing calls if resources were not available to process the call. New calls would fail with unexpected behavior and in-progress calls would experience quality-related problems.
The MGCP VoIP Call Admission Control feature provides three CAC mechanisms to address the need for improved quality and predictable gateway behavior. The first mechanism is local/system CAC, which provides the ability to gracefully refuse calls on the basis of the availability of local gateway call processing resources such as CPU utilization and memory. The second CAC mechanism provides synchronization with Resource Reservation Protocol (RSVP) and reports the reservation request to the call agent. The third mechanism provides network congestion detection to gracefully refuse calls on the basis of a measured level of congestion.
The MGCP VoIP Call Admission Control feature was previously released in Cisco IOS Release 12.2(8)T and is now supported on the Cisco 1751 and Cisco 1760 platforms.
Mobile IP—Home Agent Accounting
In Cisco IOS Mobile IP, the home agent keeps track of the location of the mobile node as it roams away from its home network and forwards all traffic destined to the mobile node to its new location on the Internet. The Mobile IP—Home Agent Accounting feature allows the home agent to generate the following three new accounting messages that are forwarded to the Service Selection Gateway (SSG):
•
•
•
The SSG acts as the proxy server for the authentication, authorization, and accounting (AAA) server and acknowledges the accounting messages sent by the home agent. The accounting records generated by the home agent can be stored on the AAA server and used by Internet service providers (ISPs) for billing, capacity planning, and operations. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/fthaacct.htm
MPLS VPN—MIB Support
The MPLS VPN—MIB Support feature provides Simple Network Management Protocol (SNMP) agent support in Cisco IOS software for Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) management, as implemented in the draft MPLS/BGP Virtual Private Network Management Information Base Using SMIv2 (draft-ietf-ppvpn-mpls-vpn-mib-03.txt). The Provider-Provisioned VPN (PPVPN)-MPLS-VPN MIB provides access to VPN routing/forwarding instance (VRF) information, interfaces included in the VRF, and other configuration and monitoring information.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftvnmb15.htm
The MPLS VPN—MIB Support feature was introduced in Cisco IOS Release 12.0(21)ST. The PPVPN-MPLS-VPN MIB notifications were supported in Cisco IOS Release 12.2(13)T. The PPVPN-MPLS-VPN MIB tables were integrated into Cisco IOS Release 12.2(15)T.
MPLS VPN Support for EIGRP Between Provider Edge (PE) and Customer Edge (CE)
The MPLS VPN Support for EIGRP Between Provider Edge (PE) and Customer Edge (CE) feature provides the Enhanced Interior Gateway Routing Protocol (EIGRP) with the capability to redistribute routes through a Border Gateway Protocol (BGP) Virtual Private Network (VPN) cloud. This feature is configured only on PE routers, requiring no upgrade or configuration changes to customer equipment. This feature also introduces EIGRP support for Multiprotocol Label Switching (MPLS) and BGP extended community attributes. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/fteipece.htm
Multicast Subsecond Convergence
The Multicast Subsecond Convergence feature comprises a comprehensive set of features and protocol enhancements that provide for improved scalability and convergence in multicast-based services. This feature set provides for the ability to scale to larger service levels and to recover multicast forwarding after service failure in subsecond time frames.
Multicast subsecond convergence allows you to send Protocol Independent Multicast (PIM) router-query messages (PIM hellos) every few milliseconds. In earlier releases, you could send the PIM hellos every few seconds. By enabling a router to send PIM hello messages more often, this feature allows the router to discover unresponsive neighbors more quickly. As a result, the router can implement failover or recovery procedures more efficiently.
The scalability enhancements improve on the efficiency of handling increases (or decreases) in service users (receivers) and service load (sources or content). Scalability enhancements in this release include the following:
•
•
The scalability enhancements provide the following benefits:
•
•
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122s/122snwft/release/122s14/fs_subcv.htm
Multiple OPC Support for the Cisco Signaling Link Terminal
Multiple OPC Support for the Cisco Signaling Link Terminal (SLT) feature allows Cisco SLTs to access multiple Signaling System 7 (SS7) point codes (PCs) on a media gateway controller (MGC).
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftsltopc.htm
NAT Support for IPSec ESP—Phase II
The NAT Support for IPSec ESP—Phase II feature allows multiple concurrent IP Security (IPSec) Encapsulating Security Payload (ESP) tunnels or connections through a Cisco IOS Network Address Translation (NAT) device configured in overload or Port Address Translation (PAT) mode. The IPSec ESP deployment does not need to use wrapper techniques that typically use the User Datagram Protocol (UDP) to pass through the NAT router. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftsecnat.htm
Network-Based Application Recognition Protocol Discovery Management Information Base
The existing Network-Based Application Recognition (NBAR) feature is used to identify protocols so that traffic can be classified appropriately for quality of service purposes. NBAR also contains a protocol discovery feature that displays for the user any NBAR-supported protocol traffic that is traversing an interface.
The NBAR Protocol Discovery MIB expands the capabilities of NBAR protocol discovery by providing the following new protocol discovery functionality through simple network management protocol (SNMP):
•
•
•
Configure thresholds based on traffic of particular NBAR-supported protocols or applications that report breaches and send notifications when these thresholds are crossed. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftpdmib.htm
No Service Password-Recovery
The No Service Password-Recovery feature disables password-recovery capability for better console security.
OSPF Forwarding Address Suppression in Translated Type-5 LSAs
The OSPF Forwarding Address Suppression in Translated Type-5 LSAs feature causes a not-so-stubby area (NSSA) area border router (ABR) to translate Type-7 link state advertisements (LSAs) to Type-5 LSAs, but use the address 0.0.0.0 for the forwarding address instead of that specified in the Type-7 LSA. This feature causes routers that are configured not to advertise forwarding addresses into the backbone to direct forwarded traffic to the translating NSSA ABRs. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftoadsup.htm
OSPF Inbound Filtering Using Route Maps with a Distribute List
Users can define a route map to prevent Open Shortest Path First (OSPF) routes from being added to the routing table. In the route map, the user can match on any attribute of the OSPF route.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s24/routmap.htm
OSPF Nonstop Forwarding (NSF) Awareness
The OSPF Nonstop Forwarding (NSF) Awareness feature allows customer premises equipment (CPE) routers that are NSF-aware to help NSF-capable routers perform nonstop forwarding of packets. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftosnsfa.htm
OSPF Shortest Path First Throttling
The OSPF Shortest Path First Throttling feature makes it possible to configure Shortest Path First (SPF) scheduling in millisecond intervals and to potentially delay SPF calculations during network instability. SPF is scheduled to calculate the Shortest Path Tree (SPT) when there is a change in topology. One SPF run may include multiple topology change events.
The interval at which the SPF calculations occur is chosen dynamically and is based on the frequency of topology changes in the network. The chosen interval is within the boundary of the user-specified value ranges. If network topology is unstable, SPF throttling calculates SPF scheduling intervals to be longer until the topology becomes stable. Refer to the following document for additional information:
OSPF Support for Fast Hello Packets
The OSPF Support for Fast Hello Packets feature provides a way to configure the sending of hello packets in intervals less than 1 second. Such a configuration would result in faster convergence in an Open Shortest Path First (OSPF) network. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s23/fasthelo.htm
Per-User QoS via AAA Policy Name
The Per-User QoS via AAA Policy Name feature provides the ability to download a policy name that describes quality of service (QoS) parameters for a user session from a RADIUS server and apply them for the particular session. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ft_puq.htm
Per VRF AAA
The Per VRF AAA feature allows authentication, authorization, and accounting (AAA) on the basis of Virtual Private Network (VPN) routing and forwarding (VRF) instances. For Cisco IOS Release 12.2(15)T or later releases, you can use a customer template which may be stored either locally or remotely, and AAA services can be performed on the information that is stored in the customer template. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftvrfaaa.htm
PPPoE Connection Throttling
This feature will throttle the PPP over Ethernet (PPPoE) connection requests to prevent any denial of service attacks. It will implement per-mac/per-vc initiated session rate throttling in the PPPoE server to limit the session initiate count during a specific period of time.
PPPoE Profiles
The PPPoE Profiles feature introduces PPP over Ethernet (PPPoE) profiles, which contain configuration information for a group of PPPoE sessions. Multiple PPPoE profiles can be defined on a device, allowing different virtual templates and other PPPoE configuration parameters to be assigned to different Ethernet interfaces, VLANs, and ATM permanent virtual circuits (PVCs). Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftpprfls.htm
PRI QSIG Protocol
QSIG is a standardized PBX signaling protocol used primarily in Europe over E1 and BRI trunks and occasionally in North America over T1 trunks. The PRI QSIG Protocol feature provides QSIG signalling over PRI trunks
RADIUS Support of 56-Bit Acct Session-Id
The Radius Support of 56-Bit Acct Session-Id feature introduces a new 32-bit authentication, authorization, and accounting (AAA) variable, acct-session-id-count. The first 8 bits of the acct-session-id-count variable are reserved for the unique-ident, a unique number assigned to the accounting session that is preserved between reloads. The acct-session-id-count variable is used in addition to the existing 32-bit acct-session-id variable, RADIUS Attribute 44. This provides 56 bits to represent the actual accounting session ID. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftradaid.htm
RADIUS Timeout Set During Pre-Authentication
The RADIUS Timeout Set During Pre-Authentication feature provides RADIUS timeout values during the pre-authentication phase of a session, and the values are not overwritten in later phases of the same session. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftattr27.htm
RSVP Message Authentication
RSVP Support for RTP Header Compression, Phase 1
SIP Call Transfer and Call Forwarding Supplementary Services
The SIP Call Transfer and Call Forwarding Supplementary Services feature introduces the ability of Session Initiation Protocol (SIP) gateways to initiate blind or attended call transfers. Release Link Trunking (RLT) functionality was also added with this feature. With RLT, SIP blind call transfers can now be triggered by channel-associated signaling (CAS) trunk signaling. Finally, the SIP Call Transfer and Call Forwarding Supplementary Services feature implements SIP support of call forwarding requests from a Cisco IOS gateway.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftsipcal.htm
SIP—Configurable PSTN Cause Code Mapping
For calls to be established between a session initiation protocol (SIP) network and a PSTN network, the two networks must be able to interoperate. One aspect of their interoperation is the mapping of PSTN cause codes, which indicate reasons for Public Switched Telephone Network (PSTN) call failure or completion, for SIP status codes or events. The opposite is also true: SIP status codes or events are mapped to PSTN cause codes. Event mapping tables found in this document show the standard or default mappings between SIP and PSTN.
However, you may want to customize the SIP user agent software to override the default mappings between the SIP and PSTN networks. The Configurable PSTN Cause Code to SIP Response Mapping feature allows you to configure specific map settings between the PSTN and SIP networks. Thus, any SIP status code can be mapped to any PSTN cause code, or vice versa. When set, these settings can be stored in the NVRAM and are restored automatically on bootup.
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xb/122xb_2/ftmap.htm
Note
SIP Diversion Header Implementation for Redirecting Number
Note
SIP—DNS SRV RFC2782 Compliance
Session Initiation Protocol (SIP) on Cisco Voice over IP (VoIP) gateways uses Domain Name System Server (DNS SRV) query to determine the IP address of the user endpoint. The query string has a prefix in the form of "protocol.transport." and is attached to the fully qualified domain name (FQDN) of the next hop SIP server. This prefix style, from RFC 2052, has always been available; however, with this release, a second style is also available. The second style complies with RFC 2782 and prepends the protocol label with an underscore "_"; as in "_protocol._transport." The addition of the underscore reduces the risk of the same name being used for unrelated purposes. The form compliant with RFC 2782 is the default style. Use the srv version command to configure the DNS SRV feature.
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xb/122xb_2/vvfresrv.htm
Note
SIP Gateway Support for Third Party Call Control
Note
SIP Gateway Support of RSVP and TEL URL
The SIP Gateway Support of RSVP and TEL URL feature also supports Telephone Uniform Resource Locators or TEL URLs. Currently Session Initiation Protocol (SIP) gateways support URLs in the SIP format. SIP URLs are used in SIP messages to indicate the originator, recipient, and destination of the SIP request. However, SIP gateways may also encounter URLs in other formats, such as TEL URLs. TEL URLs describe voice call connections. They also enable the gateway to accept TEL calls sent through the Internet and to generate TEL URLs in the request line of outgoing INVITE requests.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xb/122xb_2/vvfresrv.htm
Note
SIP Intra-gateway Hairpinning
SIP hairpinning is a call routing capability in which an incoming call on a specific gateway is signaled through the IP network and back out the same gateway. This call can be a public switched telephone network (PSTN) call routed into the IP network and back out to the PSTN over the same gateway.
Similarly, SIP hairpinning can be a call signaled from a line (for example, a telephone line) to the IP network and back out to a line on the same access gateway. With SIP hairpinning, unique gateways for ingress and egress are no longer necessary.
Note
SIP INVITE Request with Malformed Via Header
SIP INVITE requests that a user or service participate in a session. Each INVITE contains a Via header that indicates the transport path taken by the request so far and where to send a response. In the past, when an INVITE contained a malformed Via header, the gateway would print a debug message and discard the INVITE without incrementing a counter. However, the printed debug message was often inadequate, and it was difficult to detect that messages were being discarded.
The SIP INVITE Request with Malformed Via Header feature provides a response to the malformed request. A counter, Client Error: Bad Request, increments when a response is sent for a malformed Via field. Bad Request is a class 400 response and includes the explanation Malformed Via Field. The response is sent to the source IP address (the IP address where the SIP request originated) at User Datagram Protocol (UDP) port 5060.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xb/122xb_2/ftmalvia.htm
Note
SIP: ISDN Suspend/Resume Support
The SIP: ISDN Suspend/Resume Support feature adds Session Initiation Protocol (SIP) call-hold support to SIP gateways when an ISDN Suspend event is triggered. Because Suspend and Resume support already exists for H.323, the SIP implementation of Suspend and Resume provides feature parity. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftsusres.htm
SIP—Session Initiation Protocol for VoIP Enhancements
Voice over IP (VoIP) currently implements the International Telecommunication Union (ITU)'s H.323 specification within Internet Telephony Gateways (ITGs) to signal voice call setup. The Session Initiation Protocol (SIP) is a new protocol developed by the Internet Engineering Task Force (IETF) for multimedia conferencing over IP. SIP features are compliant with IETF RFC 2543, SIP: Session Initiation Protocol, published in March 1999.
The Cisco SIP functionality, introduced in Cisco IOS Release 12.1(1)T and enhanced in Cisco IOS Release 12.1(3)T, enables Cisco access platforms to signal the setup of voice and multimedia calls over IP networks. This release ports the feature into the Cisco 1751 and Cisco 1760 platforms. The SIP feature also provides nonproprietary advantages in the areas of
•
•
•
•
SIP Support for Media Forking
The SIP Support for Media Forking feature provides the ability for Session Initiation Protocol (SIP) networks to create midcall multiple streams (or branches) of audio. The multiple streams of audio are associated with a single call, but can be sent to several different destinations. The SIP Support for Media Forking feature allows service providers to use technologies such as speech recognition, voice authentication, and text-to-speech conversion to provide sophisticated services to their end-user customers. An example is a web-browsing application that uses voice recognition and text-to-speech (TTS) technology to make reservations, verify shipments, or order products. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftspfork.htm
SIP T.38 Fax Relay
The SIP T.38 Fax Relay feature adds standards-based fax support to session initiation protocol (SIP) and conforms to ITU-T T.38 Procedures for real-time Group 3 facsimile communication over IP networks. The ITU-T standard specifies real-time transmission of faxes between two regular fax terminals over an IP network. Much like a voice call, SIP T.38 Fax Relay requires call establishment, data transmission, and release signaling.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xb/122xb_2/ftsipfax.htm
Note
SIP User Agent MIB
The Session Initiation Protocol (SIP) User Agent Client (UAC) and User Agent Server (UAS) are manageable by an SNMP-based network management platform, such as the Cisco Voice Manager. This release ports the feature to the Cisco 1750 and Cisco 1761 platforms. The SIP MIB has been defined, will be submitted to the IETF, and will be implemented on those platforms.
To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB web site on Cisco.com at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
Source Interface Selection for Outgoing Traffic with Certificate Authority
The Source Interface Selection for Outgoing Traffic with Certificate Authority feature allows you to specify the address of an interface to be used as the source address for all outgoing TCP connections when a designated trustpoint has been configured. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ft_asish.htm
Support for Bridged RFC 1483 Encapsulated Traffic over ATM SVCs
The Support for Bridged RFC 1483 Encapsulated Traffic over ATM SVCs feature allows you to send bridged RFC 1483 encapsulated packets over ATM switched virtual circuits (SVCs). Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftbridge.htm
Support for IUA with SCTP for Cisco Access Servers
The Support for IUA with SCTP for Cisco Access Servers feature supports the IDSN User Adaptation (IUA) Layer with Stream Control Transmission Protocol (SCTP) for the Cisco AS5x00 network access servers (NASs) and the Cisco 2420, Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series. This feature is to be used as an alternative to the existing IP-based User Datagram Protocol-to-Reliable Link Manager (UDP-to-RLM) transport between the Cisco PGW2200 and Cisco gateways. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftgkrup.htm
T1 Channel Associated Signaling (CAS)
Channel Associated Signaling (CAS) is the transmission of signaling information within the voice channel. Support for CAS is now available on T1 interfaces.
T.37 for Cisco 7200
This feature adds T.37 standards-based store-and-forward fax protocol support for H.323 gateways and gatekeepers to the Cisco 7200 series. T.37 is an ITU-T recommended standard for store-and-forward fax that enables Cisco gateways and gatekeepers to interwork with other Cisco gateways and third-party H.323 devices that support the T.37 protocol.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t11/faxapp/index.htm
T.37 store-and-forward fax was originally supported in Cisco IOS Release 12.1(5)T on the Cisco AS5300 platform. In Cisco IOS Release 12.2(8)T, support was added on the Cisco 1751, Cisco 2600 series, Cisco 3600 series, Cisco 3725, and Cisco 3745. In Cisco IOS Release 12.2(13)T, support was added on the Cisco AS5350 and the Cisco AS5400. Cisco IOS Release 12.2(15)T adds support on the Cisco 7200 series.
Tokenless Call Authorization
The Tokenless Call Authorization feature provides a statically configured access list of authorized H.323 endpoints for the Cisco IOS gatekeeper. The gatekeeper accepts calls from endpoints on the list. This security feature is an alternative to Interzone ClearTokens (IZCTs) and Cisco Access Tokens (CATs), and can be used with Cisco CallManager. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ft_tklss.htm
Tunneled GR-303 for the Cisco Cable Modem
The Tunneled GR-303 Support feature enables the Cisco uBR925 cable access router to send and receive call control messages using GR-303 signaling, in addition to the Media Gateway Control Protocol (MGCP) signaling that was previously supported. This allows the Cisco uBR925 router to support advanced call features such as caller ID and call waiting, using both GR-303 and MGCP signaling. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/dtgrmgcp.htm
UDP Forwarding Support of IP Redundancy Virtual Router Group (VRG)
User Datagram Protocol (UDP) forwarding is used in Cisco IOS software to forward broadcast and multicast packets received for a specific IP address. Virtual Router Group (VRG) support is currently implemented with the Hot Standby Routing Protocol (HSRP), and it allows a set of routers to be grouped as a logical router that answers to a well known IP address. The UDP Forwarding Support of IP Redundancy Virtual Router Group (VRG) feature enables UDP forwarding to be VRG aware, resulting in forwarding only to the active router in the VRG. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftudpvrg.htm
V.92 and V.44 Support for Digital Modems
The V.92 and V.44 Support for Digital Modems feature supports the V.92 Modem on Hold and V.92 Quick Connect portions of the new V.92 modem standard, and the new V.44 LZJH compression standard based on Lempel-Ziv, on the Cisco 3600 and Cisco 3700 series router platforms. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122y/122yt/122yt11/ftv92_44.htm
VRF-Aware IPSec
The VRF-Aware IPSec feature introduces IP Security (IPSec) tunnel mapping to Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs). Using the VRF-Aware IPSec feature, you can map IPSec tunnels to virtual routing and forwarding (VRF) instances using single public-facing addresses.
A VRF instance is a per-VPN routing information repository that defines the VPN membership of a customer site attached to the provider edge (PE) router. A VRF comprises an IP routing table, a derived Cisco Express Forwarding (CEF) table, a set of interfaces that use the forwarding table, and a set of rules and routing protocol parameters that control the information that is included in the routing table. A separate set of routing and CEF tables is maintained for each VPN customer.
The MPLS distribution protocol is a high-performance packet-forwarding technology that integrates the performance and traffic management capabilities of data link layer switching with the scalability, flexibility, and performance of network-layer routing. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ft_vrfip.htm
XML Interface to Syslog Messages
The Cisco IOS system logging (Syslog) process allows the system to report and save important error messages, either locally or to a remote logging server. These Syslog messages include system error messages and debugging output sent during network operation to assist users and Cisco TAC engineers with identifying the type and severity of a problem. Syslog messages can be sent to the console, a monitor (TTY), a buffer, or a remote host.
The XML Interface to Syslog Messages features provides Command Line Interface (CLI) commands for enabling syslog messages to be sent in an XML format. XML (Extensible Markup Language), a derivative of SGML, provides a representation scheme to structuralize consistently formatted data such as that found in Syslog messages. This feature defines a closed set of meaningful XML tags for Syslog messages. Logs in a standardized XML format can be more readily used in external customized monitoring tools. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/ftxmlsys.htm
New Hardware Features Supported in Cisco IOS Release 12.2(13)T
The following new hardware features are supported in Cisco IOS Release 12.2(13)T. Some of these features may have been introduced on other hardware platforms in earlier Cisco IOS software releases.
Catalyst 4224 Access Gateway Switch
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. The Cisco Catalyst 4224 provides an integrated switch and WAN/voice gateway for enterprise satellite offices with up to 24 users. It is intended to work in conjunction with a Cisco Call Manager cluster from the central site with fail over capabilities to allow local calls and basic PBX features.
For information about Cisco Catalyst 4224 configuration, see the following:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat4224/index.htm
Cisco 3631 Router Enhanced Functionality
In Cisco IOS Release 12.2(13)T, the Cisco 3631 will support additional functionality. Beginning in this release, this router will support the following interfaces:
•
•
•
•
•
•
•
•
•
•
•
•
For more information about network module configuration, see the following:
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_mod/cis2600/hw_inst/nm_inst/nm-doc/index.htm
For more information about WAN interface card (WIC) configuration, see the following:
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_mod/cis2600/hw_inst/wic_inst/wic_doc/index.htm
Cisco 3725 Router, Cisco 3745 Router, Cisco 2691 Router Enhanced Functionality
In Cisco IOS Release 12.2(13)T, the Cisco 3725, Cisco 3745, and Cisco 2691 routers will support additional functionality. Beginning in this release, these routers will support the following interfaces:
•
•
•
•
•
•
•
For more information about network module configuration, see the following:
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_mod/cis2600/hw_inst/nm_inst/nm-doc/index.htm
For more information about WAN interface card (WIC) configuration, see the following:
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_mod/cis2600/hw_inst/wic_inst/wic_doc/index.htm
Cisco 7401 ASR-BB and Cisco 7401 ASR-CP
The Cisco 7401 ASR-BB and Cisco 7401 ASR-CP are now supported on Cisco IOS Release 12.2T.
Content Engine Network Module for Caching and Content Delivery
The Content Engine (CE) Network Module for Caching and Content Delivery offers the ability to integrate the features of Cisco Application and Content Networking System (ACNS) software into branch office platforms. The CE network module combines the Content Caching, Content Filtering and Content Delivery features of ACNS with robust branch office routing and is supported on Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series routers.
The CE network module can operate as a stand-alone cache or in an integrated enterprise content delivery network (E-CDN) environment. As one element of an E-CDN, the CE network module can be deployed with a combination of other content engines, content routers, content services switches, and content distribution managers to create a complete content delivery network system.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ft_1cenm.htm
PA-MC-8TE1+
The Cisco PA-MC-8TE1+ is a single-wide port adapter designed to provide a full eight-port PRI multichannel solution for the Cisco 7200 and Cisco 7400. The interfaces can be channelized, fractional or ISDN-PRI, or unframed (E1) with up to 256 independent HDLC channels definable for T1 and E1 applications.
SRP MIB for DPT-OC12 WAN Card
This feature provides the SRP MIB for PA-SRP-OC12xx and SRPIP-OC12xx cards for the Cisco 7200 and Cisco 7500 series routers.
Unchannelized support for PA-MC-2T3+ port adapter
The PA-MC-2T3+ is a single-width port adapter that provides two T3 interface connections. Each T3 interface can now be independently configured to be either channelized or unchannelized. A channelized T3 provides 28 T1 lines multiplexed into the T3. Each T1 line can be configured into one or more serial interface data channels.
Using the no channelized command, you can configure the T3 as a single, unchannelized serial interface data channel. You can configure this data channel to use all of the T3 bandwidth or a portion of it.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121limit/121e/121e5/5e_ct3.htm
Update to the Enhancements for the Cisco Voice Gateway 200
The Enhancements for the Cisco Voice Gateway 200 (Cisco VG200) feature provides the Cisco VG200 platform (also called CAG-VG200) with increased voice gateway feature parity to the Cisco 2600, Cisco 3600, and Cisco 3700 platforms. This update provides additional feature functionality on the Cisco VG200 platform.
The Cisco VG200 platforms provide the following default memory options: CAG-VG200—16 MB of Flash, 64 MB of DRAM
VPN Accelerator Module (VAM)
The VPN Acceleration Module (VAM) is a single-width acceleration module. It provides high-performance, hardware-assisted tunneling and encryption services suitable for virtual private network (VPN) remote access, site-to-site intranet, and extranet applications. It also provides platform scalability and security while working with all services necessary for successful VPN deployments — security, quality of service (QoS), firewall and intrusion detection, service-level validation, and management. The VAM off-loads IPSec processing from the main processor, thus freeing resources on the processor engines for other tasks.
The VAM provides hardware-accelerated support for multiple encryption functions:
•
•
•
•
•
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122y/122ye/1229ye/12ye_vam.htm
WIC-1-B-U-V2
Beginning in this release, the model number for the existing WIC-1-B-U interface card for the Cisco 1700 series, Cisco 2600 series, and Cisco 3600 series is changing to WIC-1-B-U-V2.
In addition, this interface card will now be supported on the Cisco 1760, Cisco 2691, Cisco 3725 and Cisco 3745 beginning with this release.
New Software Features in Cisco IOS Release 12.2(13)T
The following new features are supported in Cisco IOS Release 12.2(13)T. Some of these features may have been introduced on other hardware platforms in earlier Cisco IOS software releases.
Advanced Encryption Standard (AES)
The Advanced Encryption Standard (AES) feature adds support for the new encryption standard AES, with CBC (Cipher Block Chaining) Mode, to IP Security (IPSec).
The National Institute of Standards and Technology (NIST) has created AES, which is a new Federal Information Processing Standard (FIPS) publication that describes an encryption method. AES is a privacy transforms for IPSec and Internet Key Exchange (IKE) and has been developed to replace the Data Encryption Standard (DES). AES is designed to be more secure than DES: AES offers a larger key size, while ensuring that the only known approach for an intruder to decrypt a message is to try every possible key. AES has a variable key length—the algorithm can specify a 128-bit key (the default), a 192-bit key, or a 256-bit.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ft_aes.htm
Analog DID (Direct Inward Dial)
Analog Direct Inward Dial (DID) is now supported on Cisco 1700 series routers.
Apollo Domain
The Apollo Domain networking protocol will no longer be offered after Cisco IOS Release 12.2. Apollo Domain commands will not appear in future releases of the Cisco IOS software documentation set.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftjencrg.htm
AppleTalk EIGRP
The AppleTalk Enhanced Interior Gateway Routing Protocol (Enhanced IGRP) will no longer be offered after Cisco IOS Release 12.2(13)T. AppleTalk EIGRP commands will not appear in future releases of the Cisco IOS software documentation set.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftjencrg.htm
ATM Multilink PPP Support on Multiple VCs
The ATM Multilink PPP Support on Multiple VCs feature supports the transport of real-time (voice) and other (data) traffic on Frame Relay and ATM virtual circuits (VCs).
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftatmmlt.htm
ATM Policing by Service Category for SVC/SoftPVC
When configured, an ATM switch at the network side of a user-to-network (UNI) interface polices the flow of cells in the forward (into the network) direction of a virtual connection. These traffic policing mechanisms are known as usage parameter control (UPC). With UPC, the switch determines whether received cells comply with the negotiated traffic management values and takes one of the following actions on violating cells:
•
•
•
The ATM Policing by Service Category for SVC/SoftPVC feature enables you to specify which traffic to police, based on service category, on switched virtual circuits (SVCs) or terminating VCs on the destination end of a soft VC.
For more information on UPC, refer to the "Traffic and Resource Management" chapter in the Guide to ATM Technology.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122b/122b_4/svc_upc.htm
ATM Subinterface MIB/Traps
This feature adds support for the monitoring of ATM and Frame Relay (FR) subinterface status using SNMP. New CLI commands allow the enabling or disabling of ATM and Frame Relay notifications (traps and informs), and provide an option for limiting the rate of notifications sent ("trap throttling").
Automatic Protection Switching (APS)
This feature allows switchover of packet-over-SONET (POS) circuits in the event of circuit failure and is often required when connecting SONET equipment to telco equipment.
Banyan VINES
The Banyan Virtual Network System (VINES) protocol will no longer be offered after Cisco IOS Release 12.2(13)T. Banyan VINES commands will not appear in future releases of the Cisco IOS software documentation set.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftjencrg.htm
BGP 4 MIB Support for per-Peer Received Routes
BGP 4 MIB Support for per-Peer Received Routes introduces a new table in the CISCO-BGP4-MIB that provides the capability to query (by using Simple Network Management Protocol [SNMP] commands) for routes that are learned from individual Border Gateway Protocol (BGP) peers.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftbgpmib.htm
BGP Policy Accounting
Border Gateway Protocol (BGP) policy accounting measures and classifies IP traffic that is sent to, or received from, different peers. Policy accounting is enabled on an input interface, and counters based on parameters such as community list, autonomous system number, or autonomous system path are assigned to identify the IP traffic.
Using the BGP table-map command, prefixes added to the routing table are classified by BGP attribute, autonomous system number, or autonomous system path. Packet and byte counters are incremented per input interface. A Cisco IOS policy-based classifier maps the traffic into one of eight possible buckets, representing different traffic classes.
Using BGP policy accounting, you can account for traffic according to the route it traverses. Service providers (SPs) can identify and account for all traffic by customer and bill accordingly. Customers are billed appropriately for traffic that is routed from a domestic, international, or satellite source.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ft_bgppa.htm
Bisync-to-IP Conversion for Automated Teller Machines
The Bisync-to-IP Conversion for Automated Teller Machines feature enables customers to attach a binary synchronous communication (bisync) automated teller machine to a serial interface on a Cisco router running bisync-to-IP (BIP) protocol translation, and then to route the data over a TCP/IP network directly to an IP-based application host.
As of Cisco IOS Release 12.2(13)T you can use the bstun peer-map-poll command in global configuration mode to map the ATM state to polling. The default is to not map the peer state to polling. If you configure this command, BIP activates polling when the BIP tunnel becomes active and stops polling when the tunnel connection is terminated. When the peer state-to-polling is not mapped, BIP waits for the host to issue an "active" status message across the BIP tunnel before polling the ATM device and polling is stopped when an "inactive" status message is received across the tunnel or the tunnel connection is terminated.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t4/ftbipatm.htm
Call Admission Control for H.323 VoIP Gateways
Before the call admission control feature, gateways did not have a mechanism to gracefully prevent calls from entering when certain resources were not available to process the call. This causes the new call to fail with unreported behavior, and could potentially cause the calls that are in progress to have quality related problems.
This feature set provides the ability to support resource-based call admission control processes. These resources include system resources such as CPU, memory, and call volume, and interface resources such as call volume.
If system resources are not available to admit the call, two kinds of actions are provided: system denial (which busyouts all of T1 or E1) or per call denial (which disconnects, hairpins, or plays a message or tone). If the interface-based resource is not available to admit the call, the call is dropped from the session protocol (such as H.323).
This feature was previously released in Cisco IOS Release 12.2(4)T on the Cisco 2600 and Cisco 3600 routers, and Cisco MC3810 multiservice concentrators. This release is porting the feature into the IAD2420 platform.
Call Release Source Reporting in Gateway-Generated Call Accounting Records
The Call Release Source Reporting in Gateway-Generated Call Accounting Records feature enables you to track the source of call release in a Voice over IP (VoIP) network. This call release information defines whether a call was released by the calling or called party or by an internal or external source.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ft_crsr.htm
CEF and Distributed CEF Switching for IPv6
Cisco Express Forwarding for IPv6 (CEFv6) is advanced, Layer 3 IP switching technology for the forwarding of IPv6 packets. Distributed CEF for IPv6 (dCEFv6) performs the same functions as CEFv6 but for distributed architecture platforms such as the Cisco 12000 series Internet routers and the Cisco 7500 series routers. dCEFv6 and CEFv6 function the same and offer the same benefits as dCEFv4 and CEFv4—network entries that are added, removed, or modified in the IPv6 Routing Information Base (RIB), as dictated by the routing protocols in use, are reflected in the Forwarding Information Bases (FIBs), and the IPv6 adjacency tables maintain Layer 2 next-hop addresses for all entries in each FIB.
CEFv6 was introduced in Cisco IOS Release 12.2(13)T for nondistributed architecture platforms, such as the Cisco 7200 series routers. dCEFv6 was introduced in Cisco IOS Release 12.0(21)ST for the Cisco 12000 series Internet routers, and was then integrated into Cisco IOS Release 12.2(13)T and later releases for other distributed architecture platforms, such as the Cisco 7500 series routers.
In Cisco IOS Release 12.0(21)ST, dCEFv6 included support for IPv6 addresses and prefixes. In Cisco IOS Release 12.2(13)T or later releases, dCEFv6 and CEFv6 were enhanced to include support for separate FIBs for IPv6 global, site-local, and link-local addresses.
Cisco Conferencing and Transcoding for Voice Gateway Routers
The feature enables voice conferencing to take place among conferees at small, remote branch offices or distributed sites using local resources, without calls having to traverse the company WAN to the central site that supports such services.
The feature also provides transcoding at the remote site. Different IP telephony devices support different codecs and, for communications to be enabled between them, transcoding is required. The feature provides transcoding at the remote site, without having to access transcoding services at the central site.
To provide these services, the feature takes advantage of unused DSP resources on a network module in an already existing small or midsize Cisco router at the remote site. The collection of DSP resources so made available is called a DSP farm. The DSP farm is managed by Cisco CallManager, the software-based call-processing component of the Cisco IP telephony solution, at a central office or branch office.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftdsp.htm
Cisco IOS Software Feature Removal
This feature permanently removes selected legacy features (or components) from the Cisco IOS code. These features will not be available in future releases of Cisco IOS software.
The features that have been removed in the 12.2(13)T release are as follows:
•
•
•
•
•
•
•
•
•
•
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftjencrg.htm
Cisco IOS Telephony Service (ITS) Version 2.02
The new feature for Cisco IOS Telephony Service (ITS) Version 2.02 is an increase in directory numbers from 192 to 288 for the following platforms:
•
•
•
•
•
The Cisco IOS Telephony Service V2.02 Feature Guide is located at the following location:
http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_feature_guides_list.html
Cisco Mobile Networks—Asymmetric Link
An asymmetric link environment such as satellite communications, with a separate uplink and downlink, provides challenges for the mobile router and foreign agent.Because each unidirectional link provides only one way traffic, the inherent mapping in the foreign agent of the return path to the mobile router for incoming messages does not apply. The Cisco Mobile Networks—Asymmetric Link feature solves this problem by extending the use of mobile networks to networks where the mobile router has unidirectional links to the foreign agent. The foreign agent is able to transmit packets back to the mobile router over a different link than the one on which it receives packets from the mobile router.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/asymmetr.htm
Cisco Mobile Networks—Dynamic Network Support
The Cisco Mobile Networks feature enables a mobile router and its subnets to be mobile and maintain all IP connectivity, transparent to the IP hosts connecting through this mobile router. Previously, this feature was a static network implementation that supported stub routers only.
Cisco IOS Release 12.2(13)T introduces dynamic network support, which means that the mobile router dynamically registers its mobile networks to the home agent, which reduces the amount of configuration required at the home agent. For example, if a home agent supports 2000 mobile routers, the home agent does not need 2000 configurations but only a range of home IP addresses to use for the mobile routers.This registration results in minimal configuration on the home agent making administration and set up easier.
Cisco Survivable Remote Site Telephony Service V2.02
The new feature for Cisco Survivable Remote (SRS) Telephony V2.02 is Unity Voice Mail integration, which introduces six new commands:
•
•
•
•
•
•
For further information, see Cisco IOS Telephony Service V2.02 at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/access/ip_ph/srs/index.htm
Class-Based RTP and TCP Header Compression
Real-time Transport Protocol (RTP) or Transmission Control Protocol (TCP) IP header compression is typically configured at the interface level. However, this feature now allows you to configure RTP or TCP IP header compression on a per-class basis, when a class in configured within a policy map. Policy maps are created using the Modular Quality of Service Command-Line Interface (MQC).
Thus, this feature extends the functionality of the MQC and allows you to configure and fine-tune IP header compression at a more granular level.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/fthdrcmp.htm
Clearable SIP-UA Statistics
This feature provides the ability to clear all Session Initiation Protocol (SIP) statistics counters that are displayed by the show sip-ua statistics command, which includes response, traffic and retry statistics. Prior to the implementation of the new feature, SIP counters could be cleared only by reloading or resetting the router. The new feature enhances both trouble-shooting and statistical analysis efforts by clearing SIP counters without reloading or resetting the router.
The new feature includes the following functionality:
•
•
•
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftshadow.htm
Committed Access Rate (CAR)
Committed Access Rate (CAR) can rate limit traffic based on certain matching criteria, such as incoming interface, IP Precedence, or IP access list.
Connection-Oriented Media (Comedia) Enhancements for SIP
This feature provides the following functionality to symmetric Network Address Translation (NAT) traversal:
•
•
The new feature implements one of many possible SIP solutions to address problems with different NAT types and traversals.With the Connection-Oriented Media (Comedia) Enhancements for SIP feature, the gateway can open an RTP session with the remote end and then update or modify the existing RTP session's remote address and port (raddr:rport) with the source address and port of the actual media packet received after passing through NAT.
Dial-Peer Support for Data Calls
The Dial-Peer Support for Data Calls feature enables the configuration and order assignment of dial peers so that a gateway can identify incoming calls as voice or data. The feature provides a unified call processing model that is scalable for voice and data calls through dial-peer provisioning. The feature also enables the capability of assigning separate number ranges for voice or data calls so that the calls will have the same preference level of matching.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftconcrt.htm
Distributed IPv6 for Cisco IOS software
This feature provides distributed CEF switching support for IPv6 on the Cisco 7500 platforms.
DLR Enhancements: PGM RFC-3208 Compliance
In compliance with RFC 3208, the DLR Enhancements feature adds off-tree designated local repairer (DLR) support and redirecting poll response (POLR) capability for upstream DLRs to the Cisco implementation of Pragmatic General Multicast (PGM).
Dual Serial Line Management to Interface Lucent 5ESS
This feature is a part of the Cisco IOS Telco Feature Set, a bundle of applications specific to the data communications network (DCN) environment. Specifically, this feature supports X.25-to-TCP protocol translation, and provides dual serial interfaces to preserve the redundancy and monitoring capability available from SCC0 and SCC1 links on a Lucent 5ESS switch in the DCN network.
Dynamic Multipoint VPN (DMVPN)
The Dynamic Multipoint VPN (DMVPN) feature combines GRE tunnels, IPSec encryption, and NHRP routing to provide users an ease of configuration via crypto profiles, which override the requirement for defining static crypto maps, and dynamic discovery of tunnel endpoints.
This feature relies on the following two Cisco technologies—NHRP and mGRE Tunnel Interface.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftgreips.htm
Dynamic Subscriber Bandwidth Selection
The Dynamic Subscriber Bandwidth Selection (DBS) feature enables wholesale service providers to sell different classes of service to retail service providers by controlling bandwidth at the ATM Virtual Circuit (VC) level. ATM Quality of Service (QoS) parameters from the subscriber domain are applied to the ATM PVC on which a PPPoE or PPPoA session is established.
Using DBS you can set the ATM permanent virtual circuit (PVC) traffic shaping parameters to be dynamically changed based on the RADIUS profile of a PPP over Ethernet (PPPoE) or PPP over ATM (PPPoA) user logging in on the PVC. If the user is the first user on that PVC, then the RADIUS profile values override the default values of the PVC. If users already exist on the PVC, then the new value overrides the existing configuration only if it is higher than the existing value. If multiple PPPoE sessions are allowed on a subscriber VC, then the highest peak cell rate (PCR) and sustainable cell rate (SCR) of all the sessions is selected as the PCR and SCR of the VC.
You can apply DBS QoS parameters per user as well as per domain. If you apply DBS QoS parameters under a domain profile, all users in that profile are assigned the same DBS QoS parameters. These parameters are assigned to the RADIUS profile for that domain. You can also apply distinctive DBS QoS parameters via the RADIUS user profile.
Traffic shaping parameters can be locally configured by IOS CLI in VC-mode, VC-class, range mode, or PVC-in-range mode. These parameters have a lower priority and are overridden by the shaping parameters specified in the domain service profile. Traffic shaping parameters that are CLI configured at the VC class interface or subinterface level are treated as the default QoS parameters for the PVCs to which they apply. These parameters are overridden by the domain service profile QoS parameters of the domain the user is logged in to. If no VC class is configured, the default is the unspecified bit rate (UBR).
When a network access server (NAS) sends a domain authorization request and receives an affirmative response from the RADIUS server, this response may include a "QoS-management" string via vendor-specific attribute (VSA) 26 for QoS management in the NAS. The QoS management values are configured as part of the domain service profile attributes on the RADIUS server. These values contain PCR and SCR values for a particular user or domain. If the QoS specified for a domain or user cannot be applied on the PVC that the session belongs to, the session is not established.
Changing PVC traffic parameters because of new simultaneous PPPoE sessions on the PVC does not cause existing PPPoE sessions that are already established to disconnect. Changing domain service profile QoS parameters on the RADIUS server does not cause traffic parameters to automatically change for PVCs that have existing sessions.
When you enter the dbs enable or no dbs enable commands to configure or unconfigure DBS, existing sessions are not disconnected. If you have a session that has been configured for DBS and you configure the no dbs enable command on a VC, additional sessions that are configured will display DBS configured QoS values until the first new session is up. After the first session is brought up, the VC has default and locally configured values. If you configure the dbs enable command after multiple sessions are already up on the VC, all sessions on that VC have DBS QoS parameters.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftdbs.htm
Enhanced Features for Local and Advanced Voice Busyout
This feature introduces 2 new commands, busyout monitor gatekeeper and busyout action graceful. The busyout monitor gatekeeper command busies out the gatekeeper if the gateway loses connection to the primary gatekeeper and removes the busyout state when the gateway restores connection to the primary or backup gatekeeper. The busyout action graceful command controls the busyout behavior that is triggered by the busyout monitor command. This command busies out the voice port immediately if the busyout behavior is triggered but if there is an active call on this voice port it will wait until the call is over.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ft_lavbo.htm
Enhanced ITU-T G.168 Echo Cancellation
This feature provides an alternative to the default, Cisco proprietary 32-millisecond G.165 echo canceller (EC). The new extended echo canceller provides improved performance for trunking gateway applications and provides a configurable tail length that supports up to 64 milliseconds (ms) of echo cancellation. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftecho.htm
Enhanced Packet Marking
The Enhanced Packet Marking feature allows you to map and convert the marking of a packet from one value to another (for example, the Precedence value can be mapped to the equivalent Class of Service (CoS) value) by using a kind of conversion chart called a table map.
The table map establishes an equivalency from one value to another. For example, the table map can map the CoS value of a packet to the Precedence or differentiated services code point (DSCP) value of the packet. For networks using MPLS, the MPLS EXP value can be mapped to the QoS group value, which can then be mapped to the Precedence or DSCP value of the packet. This value mapping can be propagated for use on the network, as needed. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftenpkmk.htm
Enhancements for the Cisco Voice Gateway 200
The Enhancements for the Cisco Voice Gateway 200 (VG200) feature provides the Cisco VG200 platform with increased voice gateway feature parity to the Cisco 2600, Cisco 3600, and Cisco 3700 platforms. This update provides additional feature functionality on the Cisco VG200 platform. Refer to the following document for additional information:
Exterior Gateway Protocol (EGP)
The Exterior Gateway Protocol (EGP) will no longer be offered after Cisco IOS Release 12.2(13)T. EGP commands will not appear in future releases of the Cisco IOS software documentation set.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftjencrg.htm
File System Check and Repair for PCMCIA ATA Disks
This feature introduces a File-System-Check (fsck) utility in Cisco IOS software for FAT file systems on PCMCIA disks. The utility performs functions such as checking the boot sector and partition table, checking file and directory structure, reclaiming unused disk space, and updating the FAT file structure. Prior to the introduction of this utility, corrupt files could not be removed from ATA disks using the Cisco IOS CLI. This utility is run using the fsck privileged EXEC mode command.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ft_fsck.htm
Frame Relay PVC Bundles with IP and MPLS QoS Support
Frame Relay PVC bundles allow you to associate a group of Frame Relay permanent virtual circuits (PVCs) with a single next-hop address. When Frame Relay PVC bundles are used with IP, packets are mapped to specific PVCs in the bundle on the basis of the precedence value or differentiated services code point (DSCP) settings in the type of service (ToS) field of the IP header. Each packet is treated differently according to the QoS configured for each PVC.
Frame Relay PVC bundles with MPLS QoS support extends Frame Relay PVC bundle functionality to support the mapping of Multiprotocol Label Switching (MPLS) packets to specific PVCs in the bundle. MPLS packets are mapped to PVCs according to the settings of the experimental (EXP) bits in the MPLS packet header.Waiting for information.
Frame Relay Queueing and Fragmentation at the Interface
The Frame Relay Queueing and Fragmentation at the Interface feature introduces support for low-latency queueing (LLQ) and FRF.12 end-to-end fragmentation on a Frame Relay interface. This new feature simplifies the configuration of low-latency, low-jitter quality of service (QoS) by enabling the queueing policy and fragmentation configured on the main interface to apply to all permanent virtual circuits (PVCs) and subinterfaces under that interface. Before the introduction of this feature, queueing and fragmentation had to be configured on each individual PVC. Subrate shaping can also be configured on the interface.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/frfrintq.htm
H.323 Call Redirection Enhancements
The user-to-user information element (UUIE) of the Facility message is used primarily for call redirection. The UUIE contains a field, facilityReason, that indicates the nature of the redirection. The H.323 Call Redirection Enhancements feature adds support for two of the reasons: routeCallToGatekeeper and callForwarded. It also provides a non-standard method for using the Facility message to effect call transfer.
This feature was previously released in Cisco IOS Release 12.2(2)T on Cisco 1700, Cisco 2600 series, Cisco 3600 series, Cisco MC3810, Cisco AS5300, Cisco uBR924 platforms. This release is porting the feature into the IAD2420 platform.
H.323 Dual Tone Multifrequency Relay Using Named Telephone Events
The NTE method of DTMF relay was originally available on Cisco gateways only for Session Initiation Protocol (SIP) and Media Gateway Control Protocol (MGCP) gateways. The H.323 DTMF Relay Using Named Telephone Events (NTE) feature adds support for this method for H.323 gateways.
Cisco H.323 gateways advertise capabilities using the H.245 capabilities messages. By default, they advertise that they can receive all DTMF relay modes. If the capabilities of the remote gateway do not match, the Cisco H.323 gateway transmits DTMF tones as in-band voice. Configuring DTMF relay on the Cisco H.323 gateway sets preferences for how the gateway handles DTMF transmission. If multiple methods are configured, the priority is as follows:
•
•
•
•
In addition to support for NTE, the H.323 DTMF Relay Using NTE feature provides support for asymmetrical payload types. Payload types can differ between local and remote endpoints. Therefore, the Cisco gateway can transmit one payload type value and receive a different payload type value.
This feature was previously released in Cisco IOS Release 12.2(11)T on Cisco 2600 series, Cisco 3600 series, Cisco AS5300, Cisco AS5350, Cisco AS5400, Cisco AS5800, and Cisco AS5850 platforms. This release is porting the feature into the IAD2420 platform.
H.323 (Gateway) Support
Support for H.323 Version 2 Gateway functionality is added to the Cisco IAD2420 series of integrated access devices (IADs). This support provides the Cisco IAD2420 IAD with more market opportunities than when the IAD only supported MGCP and SGCP call control protocols.
The Cisco IAD2420 IAD with 16 FXS analog ports delivers local voice and data service using VoIP in an Ethernet To The Building (ETTx) application. It aggregates the voice traffic from multiple tenants and transports it to an Ethernet switch, such as the Cisco 2950, over the Ethernet link. The built-in WAN interface (either a T1, ADSL or SHDSL module) is not used when using the IAD2420-16FXS.
H.323 Redundant Zone Support
The Redundant H.323 Zone Support feature allows users to configure multiple gatekeepers to service the same zone or technology prefix. This feature can be used with the Gateway Support for Alternate Gatekeepers feature, which allows a user to configure a gateway to point to two gatekeepers (one as the primary and the other as the alternate). Together, these features allow a user to configure a Cisco gateway to send location requests (LRQs) to two or more Cisco gatekeepers---one as a primary and the others as back up gatekeepers.
This feature was previously released in Cisco IOS Release 12.1(1)T on Cisco 2600 series, Cisco 3600 series, Cisco MC3810, Cisco AS5200, Cisco AS5300, and Cisco AS5800 platforms. This release is porting the feature into the Cisco IAD2420 platform.
H.323 Scalability and Interoperability Enhancements
The Cisco H.323 Scalability and Interoperability Enhancements feature upgrades the Cisco H.323 Gatekeeper and Cisco H.323 Gateway to comply with H.323 Version 3. The enhancements in this release include support for mandatory H.323 Version 3 elements in the gateway, support for H.225 call signalling over UDP, and address resolution using border elements.
For gatekeeper support, this feature was previously released in Cisco IOS Release 12.2(4)T on Cisco 2500 series, Cisco 2600 series, Cisco 3600 series, Cisco MC3810, Cisco AS5850, and Cisco 7200 series platforms. For gateway support, this feature was previously released in Cisco IOS Release 12.2(4)T on Cisco 1700, Cisco 2600 series, Cisco 3600 series, Cisco 7200 series, Cisco AS5850, Cisco uBR900 series, and Cisco uBR924 platforms. This release is porting the feature into the IAD2420 platform.
H.323 Support for Virtual Interfaces
The H.323 Support for Virtual Interfaces feature allows users to configure the IP address of the gateway, so that the IP address include in the H.323 packet is deterministic and consistently indicates the same address for the source.
In previous releases of the Cisco IOS software, the source address included in the H.323 packet could vary depending on the protocol (RAS, H.225, H.245, or RTP). This makes it difficult to configure firewall applications to work with H.323 messages.
The H.323 Support for Virtual Interfaces feature addresses that difficulty by allowing the user to explicitly configure an IP address to be used for all protocols
This feature was previously released in Cisco IOS Release 12.1(2)T on Cisco 2500 series, Cisco 2600 series, Cisco 3600 series, Cisco AS5300, Cisco 7200 series, and Cisco uBR924 platforms. This release is porting the feature into the IAD2420 platform.
HP Probe
The HP Probe feature will no longer be offered after Cisco IOS Release 12.2(13)T. HP Probe commands will not appear in future releases of the Cisco IOS software documentation set.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftjencrg.htm
Interim Local Management Interface (ILMI)
The Interim Local Management Interface (ILMI) is a protocol defined by the ATM Forum for setting and capturing physical layer, ATM layer, virtual path, and virtual circuit parameters on ATM interfaces. ILMI uses simple network management protocol (SNMP) messages without User Datagram Protocol (UDP) and IP, and organizes managed objects into the following four management information bases (MIBs).
Interim-Interswitch Signaling Protocol (IISP)
The Interim-Interswitch Signalling Protocol (IISP) defines a static routing protocol (using manually configured prefix tables) for communication between ATM switches. IISP provides support for switched virtual circuits (SVCs) on ATM switches that do not support the Private Network-to-Network Interface (PNNI) protocol.
Interim Update at Call Connect
With this feature, Cisco IOS software generates and sends an additional updated interim accounting record to the accounting server when a call leg is connected. All attributes (for example, h323-connect-time and backward-call-indicators) available at the time of call connection are sent through this interim updated accounting record. Refer to the following document for additional information:
Interior Gateway Routing Protocol (IGRP)
The Interior Gateway Routing Protocol (IGRP) will no longer be offered after Cisco IOS Release 12.2(13)T. IGRP commands will not appear in future releases of the Cisco IOS software documentation set.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftjencrg.htm
IP Event Dampening
Interface state changes occur when interfaces are administratively brought up or down or if an interface changes state. When an interface changes state or flaps, routing protocols are notified of the status of the routes that are affected by the change in state. Every interface state change requires all affected devices in the network to recalculate best paths, install or remove routes from the routing tables, and then advertise valid routes to peer routers. An unstable interface that flaps excessively can cause other devices in the network to consume substantial amounts of system processing resources and cause routing protocols to lose synchronization with the state of the flapping interface.
The IP Event Dampening feature introduces a configurable exponential decay mechanism to suppress the effects of excessive interface flapping events on routing protocols and routing tables in the network. This feature allows the network operator to configure a router to automatically identify and selectively dampen a local interface that is flapping. Dampening an interface removes the interface from the network until the interface stops flapping and becomes stable. Configuring the IP Event Dampening feature improves convergence times and stability throughout the network by isolating failures so that disturbances are not propagated, which reduces the utilization of system processing resources by other devices in the network and improves overall network stability.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftipevdp.htm
IPSec NAT Transparency
Before the introduction of the IPSec NAT Transparency feature, a standard IPSec VPN tunnel would not work if there were one or more NAT or PAT points in the delivery path of the IPSec packet. This feature introduces support for IPSec traffic to travel through NAT or PAT points in the network by encapsulating IPSec packets in a User Datagram Protocol (UDP) wrapper, thereby, allowing remote access users to build IPSec tunnels to home gateways.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftipsnat.htm
IPSec Passive Mode
The IPSec Passive mode feature allows users to configure an intermediate mode—IPSec passive mode—that enables routers within an existing network to accept encrypted and unencrypted data. The routers will also attempt to negotiate an encrypted session when sending data, but they will send the data in unencrypted form as necessary.
IPSec passive mode is valuable for users who wish to migrate existing networks to IPSec because they no longer have wait for all routers to deploy IPSec; that is, all routers will continue to interact with routers that will encrypt data (that have been upgraded with IPSec) and routers that have yet to be upgraded.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftpasips.htm
Note
IPv6 ADSL and Dial Deployment Support
The IPv6 ADSL and Dial Deployment Support feature adds support for IPv6 prefix pools, and per-user IPv6 Radius attributes. It further enables deployment of IPv6 in DSL and dial access environments. This feature provides the extensions that make large scale IPv6 access possible for IPv6 environments, including IPv6 Radius attributes, stateless address configuration on PPP links, per-user static routes, and access lists (ACLs). Refer to the following document for more information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ipv6/index.htm
IPv6 Extended Access Control Lists
In Cisco IOS Release 12.2(2)T or later releases, 12.0(21)ST, and 12.0(22)S, standard IPv6 access control list (ACL) functionality is used for basic traffic filtering functions—traffic filtering is based on source and destination addresses, inbound and outbound to a specific interface, and with an implicit deny statement at the end of each access list (functionality similar to standard ACLs in IPv4). IPv6 ACLs are defined and their deny and permit conditions are set by using the ipv6 access-list command with the deny and permit keywords in global configuration mode.
In Cisco IOS Release 12.2(13)T or later releases, and 12.0(23)S, the standard IPv6 ACL functionality is extended to support—in addition to traffic filtering based on source and destination addresses—filtering of traffic based on IPv6 option headers and optional, upper-layer protocol type information for finer granularity of control (functionality similar to extended ACLs in IPv4). IPv6 ACLs are defined by using the ipv6 access-list command in global configuration mode and their permit and deny conditions are set by using the deny and permit commands in IPv6 access list configuration mode. (Configuring the ipv6 access-list command places the router in IPv6 access list configuration mode, from which permit and deny conditions can be set for the defined IPv6 ACL.)
IPv6 Quality of Service
This feature provides for the application of all the Differentiated Services (DiffServ) QoS features to IPv6 packets. Specific QoS features include packet classification, traffic shaping, traffic policing, packet marking, and Drop based on Weighted Random Early Detect (WRED) on all applicable interfaces.
IPv6 RIP Enhancements
The IPv6 RIP Enhancements feature adds support for a separate IPv6 RIP routing table, the ability to delete routes from the IPv6 RIP routing table, and the ability to set route tags. The holddown timer default is now set to zero, and a maximum number of parallel routes can be configured.
IS-IS HMAC-MD5 Authentication
The IS-IS HMAC-MD5 Authentication feature adds an HMAC-MD5 digest to each Intermediate System-to-Intermediate System (IS-IS) protocol data unit (PDU). HMAC is a mechanism for message authentication codes (MAC) using cryptographic hash functions. The digest allows authentication at the IS-IS routing protocol level, which prevents unauthorized routing messages from being injected into the network routing domain.
IS-IS has five packet types: link-state packet (LSP), LAN Hello, Serial Hello, complete sequence number PDU (CSNP), and partial sequence number PDU (PSNP). The IS-IS HMAC-MD5 authentication or the cleartext password authentication can be applied to all five types of PDU. The authentication can be enabled on different IS-IS levels independently. The interface-related PDUs (LAN Hello, Serial Hello, CSNP and PSNP) can be enabled with authentication on different interfaces, with different levels and different passwords.
The HMAC-MD5 mode cannot be mixed with the clear text mode on the same authentication scope (LSP or interface). However, administrators can use one mode for LSP and another mode for some interfaces, for example. If mixed modes are intended, different keys should be used for different modes in order not to compromise the encrypted password in the PDUs.
Refer to the following document for more information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftismd5.htm
L2TP Extended Failover
The L2TP Extended Failover feature extends Layer 2 Tunneling Protocol (L2TP) failover to occur if during tunnel establishment, a router receives a Stop-Control-Connection-Notification (StopCCN) message from its peer or during session establishment, a router receives a Call-Disconnect-Notify (CDN) message from its peer. In either case, the router selects an alternate peer to contact. This is in addition to the existing failover caused by excessive retransmission of Start-Control-Connection-Reply (SCCRQ) messages that indicate there is no response from the peer.
L2TP Extended Failover results in better load distribution and prevents congestion at a tunnel terminator by allowing the busy tunnel terminator to inform the tunnel initiator that it should try another tunnel terminator.
Refer to the following document for more information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftl2tpef.htm
L2TP Redirect
The L2TP Redirect feature allows an L2TP network server (LNS) participating in Stack Group Bidding Protocol (SGBP) to send a redirect message to the L2TP access concentrator (LAC) if another LNS wins the bid. The LAC will then reinitiate the call to the newly redirected LNS. The feature provides two purposes:
•
•
Refer to the following document for more information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftl2tpmr.htm
Low Latency Queueing (LLQ) for IPSec
Low Latency Queueing (LLQ) for IPSec encryption engines helps reduce packet latency by introducing the concept of queueing before crypto engines. Prior to this, the crypto processing engine gave data traffic and voice traffic equal status. Administrators now designate voice traffic as priority. Data packets arriving at a router interface are directed into a data packet inbound queue for crypto engine processing. This queue is called the best effort queue. Voice packets arriving on a router interface are directed into a priority packet inbound queue for crypto engine processing. This queue is called the priority queue. The crypto engine undertakes packet processing in a ratio favorable for voice packets. Voice packets are guaranteed a minimum processing bandwidth on the crypto engine.
Refer to the following document for more information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/llqfm.htm
LZ Software with Hardware Encryption
Before the LZ Software with Hardware Encryption feature was introduced, compression was not supported with the VPN encryption hardware advanced integration module (AIM) and network module (NM); that is, a user had to remove the VPN module from the router and run software encryption with software compression. This feature enables all VPN modules to support LZ compression in software when the VPN module is in Cisco 2600 and Cisco 3600 series routers, thereby, allowing users to configure and compress 2 128Kb/sec streams.
Manual Certificate Enrollment (TFTP and Cut-and-Paste)
The Manual Certificate Enrollment (TFTP and Cut-and-Paste) feature allows users to generate a certificate request and accept Certificate Authority (CA) certificates as well as the router's certificates; these tasks are accomplished via a TFTP server or manual cut-and-paste operations. Users may wish to utilize TFTP or manual cut-and-paste enrollment in the following situations:
•
•
Refer to the following document for more information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftmancrt.htm
Media Forking
Media Forking allows the gateway to create multiple streams (or forks) of media associated with a single call and send those streams to multiple destinations, which may include voice portals with speech recognition. Only the original media stream is bidirectional. Additional branches are unidirectional (transmit only), so additional participants are able to hear only the originating caller and not each other. Each media stream is independently configured and can be a variation of voice only, named telephone event (NTE) only, or voice plus NTE media stream.The content of the media stream is specified in the signaling when the media stream is established.
Although there can be more than one media destination, there is only one signaling destination, which might be the voice portal. The call leg that was originally signaled (for instance, from the originating gateway to the voice portal) is maintained for the life of the session. The media destinations are independent of the signaling destination, so media forks can be added and removed dynamically. The local telephony call leg must be maintained, and up to four media forks, including the destination of the original call, are supported. Fax calls are not supported on any media streams (including the original) when multiple forks are requested. No media forks can be created for a fax call session.
MGCP 1.0 and TGCP 1.0 Profiles
This feature implements the following MGCP protocols on the supported Cisco media gateways:
•
•
•
MGCP1.0 is a protocol for the control of Voice over IP (VoIP) calls by external call-control elements known as media gateway controllers (MGCs) or call agents (CAs). It is described in the informational RFC 2705, published by the Internet Society.
PacketCable is an industry-wide initiative for developing interoperability standards for multimedia services over cable facilities using packet technology. PacketCable developed the NCS and TGCP protocols, which contain extensions and modifications to MGCP while preserving basic MGCP architecture and constructs. NCS is designed for use with analog, single-line user equipment on residential gateways, while TGCP is intended for use in VoIP-to-PSTN trunking gateways in a cable environment. To meet European cable requirements and equipment characteristics, the EuroPacketCable working group has adapted PacketCable standards under the name IP Cablecom.
MGCP Model
MGCP bases its call control and intelligence in centralized call agents, also called media gateway controllers. The call agents issue commands to simple, low-cost endpoints, which are housed in media gateways (MGs), and the call agents also receive event reports from the gateways. MGCP messages between call agents and media gateways are sent with Internet Protocol over User Datagram Protocol (IP/UDP).
The MGCP 1.0 Including NCS 1.0 and TGCP 1.0 Profiles feature provides protocols for RGWs and TGWs, which sit at the border of the packet network to provide an interface between traditional, circuit-based voice services and the packet network. Residential gateways offer a small number of analog line interfaces, while trunking gateways generally manage a large number of digital trunk circuits.
Refer to the following document for more information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t4/ft_24mg1.htm
MGCP Gateway Support for the Bind Command
Previous Media Gateway Control Protocols (MGCP) implementation did not allow the assignment of particular IP addresses for sourcing MGCP commands and media packets, which could cause firewall and security problems. With this feature, you can configure interfaces on which control and media packets can be exchanged. This new functionality allows you to separate signaling from voice by binding control (MGCP signaling) and media (Real-Time Transport Protocol, or RTP voice, fax, and modem) to specific gateway interfaces. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftxbind.htm
Mobile IP—Challenge/Response Extensions
The Mobile IP—Challenge/Response Extensions feature enables a foreign agent to authenticate a mobile node by sending mobile foreign challenge extensions (MFCE) and mobile node-AAA authentication extensions (MNAE) to the home agent in registration requests. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ft_chext.htm
Mobile IP—Fastswitching Support on Foreign Agent
The Mobile IP—Fastswitching Support on Foreign Agent feature enables packets to be fast switched from the foreign agent both in the direction of the mobile node and through the reverse tunnel. In the direction of the mobile node, packets will be properly fast-switched for global IP addresses. However, this feature does not support fast-switching to mobile nodes using private home addresses.
Fast-switching packets through the reverse tunnel is achieved by intercepting packets before cache lookup and dynamically switching them through the correct tunnel interface.
Mobile IP—Generic NAI Support and Home Address Allocation
The Mobile IP—Generic NAI Support and Home Address Allocation feature allows a mobile node to be identified by using a network access identifier (NAI) instead of an IP address (home address). The NAI is a character string similar to an email address in that it is formatted as either user or user@realm but it need not be a valid e-mail address.
The original purpose of the NAI was to support roaming between dialup ISPs. With the NAI, each ISP need not have all the accounts for all of its roaming partners in a single RADIUS database. RADIUS servers can proxy requests to remote servers for each realm.
These services are also valuable for mobile nodes using Mobile IP when the nodes are attempting to connect to foreign domains with AAA servers. The mobile node can identify itself by including the NAI along with the Mobile IP registration request.
Additionally, this feature allows you to configure the home agent to allocate addresses to mobile nodes either statically (including multiple static addresses per NAI flow) or dynamically. Home address allocation can be from address pools configured locally, through either DHCP server access, or from the AAA server.
Refer to the following document for more information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftnaiadd.htm
Mobile IP Home Agent Policy Routing
The Mobile IP Home Agent Policy Routing feature supports route maps on Mobile IP tunnels created at the home agent. This feature allows an ISP to provide service to multiple customers. While reverse tunneling packets, the home agent looks up where the packet should go. For example, if an address corresponds to a configured network access identifier (NAI) realm name (such as cisco.com), the packet goes out interface 1, which has a connection to the Cisco network. If an address corresponds to another NAI realm name (such as nortel.com), the packet goes out interface 2, which has a connection to the Nortel network. This feature was designed to route traffics through VPNs back to an enterprise network.
Refer to the following document for more information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/fthapoli.htm
Mobile IP —IPsec for Home Agent to Foreign Agent Tunnel
The Mobile IP—IPsec for Home Agent to Foreign Agent Tunnel enables the use of IPSec on the home agent to foreign agent tunnel.
Crypto map configuration must be applied to both the tunnel and physical interfaces. For details refer to the "Configuring Cisco Encryption Technology" chapter in the Release 12.2 Cisco IOS Security Configuration Guide.
Mobile IP—MIB Support for NAI and HA Redundancy
The CISCO-MOBILE-IP-MIB is enhanced to add support for following features:
1.
The following tables are defined in the MIB to support NAI based mobile nodes (MN):
•
•
•
•
These tables are the same as the corresponding tables in the RFC2006-MIB (MIP MIB) in terms of the information they provide, but indices are changed so that entries for mobile nodes which are not identified by the IP address will also be included in the table.
The `cmiHaRegMobilityBindingTable' is augmented from `haMobilityBindingTable' of the RFC2006-MIB (MIP MIB) to provide the NAI information.
2.
Scalar objects have been added to MIB to monitor the message exchanges between peer home agents. These objects are under the `cmiHaRedun' subtree of the MIB.
3.
There are scalar objects under `cmiHaReg' subtree which gives statistics about the registration processing rate at home agent. Distinction is made between registration requests authenticated locally and those authenticated at the AAA server. There are scalar objects under the 'cmiMaReg' subtree which give statistics about the rate at which registration requests are received at the mobility agent (HA or FA).
Mobile IP—NAT Detect
The basic purpose of Network Address Translation (NAT) is to take traffic from the internal network and present it to the Internet as if it were coming from a single device having only one IP address. Traditional Mobile IP tunneling is incompatible with NAT. The Mobile IP—NAT Detect feature allows the home agent to tunnel traffic to Mobile IP clients with private IP addresses behind a NAT-enabled device. The home agent is capable of detecting a registration request traversing a NAT-enabled device and applying the appropriate tunnel to reach the Mobile IP client.
Refer to the following document for more information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftnatrav.htm
Mobile IP—Private Addressing Support
The Mobile IP—Private Addressing Support feature allows the use of private IP addresses for mobile nodes. Enhancements have been made to the foreign agent to allow it to distinguish between mobile nodes using the same private home address, but with different home agents.
When a mobile node successfully registers with a foreign agent, a tunnel is set up between the foreign agent and the home agent. When a packet is received by the foreign agent for the mobile node, the foreign agent will identify which mobile node to route the packet to based on the address of the mobile node, as well as the home agent from which the packet came.
Mobile IP—Support for FA Reverse Tunneling
The Mobile IP—Support for Foreign Agent Reverse Tunneling feature prevents packets sent by a mobile node from being discarded by routers configured with ingress filtering by creating a reverse tunnel between the foreign agent and the home agent.
Refer to the following document for more information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ft_farev.htm
Modular QoS CLI (MQC)-Based Frame-Relay Traffic Shaping
The Modular Quality of Service (QoS) Command Line Interface (CLI)-Based Frame-Relay Traffic Shaping feature provides users the ability to configure Frame Relay traffic shaping (FRTS) using Modular Quality of Service (QoS) Command Line Interface (CLI) commands. Modular QoS CLI is known as MQC.
Modular QoS CLI (MQC) Three-Level Hierarchical Policer
Earlier Cisco IOS traffic policing features allowed you to configure traffic policing at two levels of policy map hierarchies; the top level and a secondary level.
The Modular QoS CLI (MQC) Three-Level Hierarchical Policer extends the traffic policing functionality by allowing you to configure traffic policing at three levels of policy map hierarchies; a top level, a secondary level, and a third level. Traffic policing may be configured at any or all of these levels, depending on the needs of your network. The feature is configured using the Modular Quality of Service (QoS) Command-Line Interface (CLI) (MQC).
Configuring traffic policing in a three-level hierarchical structure provides a greater degree of granularity for traffic policing.
Refer to the following document for more information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ft3level.htm
Modular QoS CLI (MQC) Unconditional Packet Discard
This feature allows customers to classify traffic matching certain criteria and then configure the system to unconditionally discard any packets matching that criteria. This feature is configured using the Modular Quality of Service Command-Line Interface (MQC) feature.
Refer to the following document for more information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftcbdrp.htm
MPLS DiffServ Tunneling Modes
MPLS DiffServ Tunneling Modes allows service providers to manage the QoS that a router will provide to an MPLS packet in an MPLS network. MPLS DiffServ Tunneling Modes conforms to the IETF draft standard for Uniform, Short Pipe, and Pipe modes, and to Cisco-defined extensions for scalable CLI management of those modes at customer edge, provider edge, and core routers.
Refer to the following document for more information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftdtmode.htm
MPLS Label Distribution Protocol (LDP) MIB
Multiprotocol label switching (MPLS) is a packet forwarding technology that uses a short, fixed-length value called a label in packets to determine the next hop for packet transport through an MPLS network by means of label switching routers (LSRs).
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ldpmib13.htm
MPLS Virtual Private Networks
The Virtual Private Network (VPN) feature for Multiprotocol Label Switching (MPLS) allows a Cisco IOS network to deploy scalable IPv4 Layer 3 VPN backbone services.
This feature was originally introduced in 12.0(5)T. This release introduces the command.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftvpn13.htm
MPLS VPN—Carrier Supporting Carrier—IPv4 BGP Label Distribution
This feature enables you to configure your carrier supporting carrier network to enable Border Gateway Protocol (BGP) to transport routes and Multiprotocol Label Switching (MPLS) labels between the backbone carrier provider edge (PE) routers and the customer carrier customer edge (CE) routers. Previously you had to use Label Distribution Protocol (LDP) to carry the labels and an internal gateway protocol (IGP) to carry the routes between PE and CE routers to achieve the same goal.
This feature was originally introduced in Cisco IOS Release 12.0(21)ST. This release integrates the feature into Cisco IOS Release 12.2(13)T.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftcscl13.htm
MPLS VPN—Inter-AS—IPv4 BGP Label Distribution
This feature enables you to set up a VPN service provider network so that the autonomous system boundary routers (ASBRs) exchange IPv4 routes with MPLS labels of the provider edge (PE) routers. Route reflectors (RRs) exchange VPNv4 routes, using multihop, multiprotocol, External Border Gateway Protocol (EBGP). This configuration saves the ASBRs from having to store all the VPNv4 routes. Using the route reflectors to store the VPNv4 routes and forward them to the PE routers results in improved scalability.
This feature was originally introduced in Cisco IOS Release 12.0(21)ST. This release integrates the feature into Cisco IOS Release 12.2(13)T.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftiasl13.htm
MPLS VPN-MIB Notifications
The MPLS VPN technology allows service providers to offer intranet and extranet VPN services that directly connect their customers' remote offices to a public network with the same security and service levels that a private network offers. The Provider-Provisioned VPN (PPVPN)-MPLS-VPN MIB notifications provide SNMP notification for critical MPLS VPN events.
The MPLS VPN-MIB Notifications feature provides the following benefits:
•
•
•
•
This feature was originally introduced in Cisco IOS Release 12.0(21)ST. This release integrates the feature into Cisco IOS Release 12.2(13)T.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftvpnm13.htm
MS CHAP Version 2
The MS CHAP Version 2 feature in Cisco IOS Release 12.2(13)T introduces the ability of Cisco routers to utilize Microsoft Challenge Handshake Authentication Protocol Version 2 (MS CHAP V2) authentication for PPP connections between a computer using a Microsoft Windows operating system and a network access server (NAS). MS CHAP V2 authentication is an updated version of MS CHAP that is similar to, but incompatible with MS CHAP Version 1 (V1). MS CHAP V2 introduces mutual authentication between peers and a change password feature.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftmschap.htm
Multicast-VPN—IP Multicast Support for MPLS VPNs
The Multicast-VPN—IP Multicast Support for MPLS VPNs feature allows a service provider to configure and support multicast traffic in a Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) environment. Because MPLS VPNs support only unicast traffic connectivity, deploying the Multicast-VPN feature in conjunction with MPLS VPN allows service providers to offer both unicast and multicast connectivity to MPLS VPN customers.
This feature supports routing and forwarding of multicast packets for each individual VPN routing and forwarding (VRF) instance, and it also provides a mechanism to transport VPN multicast packets across the service provider backbone.
The Multicast-VPN feature in Cisco IOS software provides the ability to support the multicast feature over a Layer 3 VPN. As enterprises extend the reach of their multicast applications, service providers can accommodate these enterprises over their MPLS core network. IP multicast is used to stream video, voice, and data to an MPLS VPN network core.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftmltvpn.htm
Multiclass Multilink PPP
Previous implementations of Cisco IOS Multilink PPP (MLP) include support for Link Fragmentation Interleaving (LFI). This feature allows the delivery of delay-sensitive packets, such as the packets of a Voice call, to be expedited by omitting the PPP Multilink Protocol header and sending them as raw PPP packets in between the fragments of larger data packets. This feature works well on bundles consisting of a single link. However, when the bundle contains multiple links there is no way to keep the interleaved packets in sequence with respect to each other.
The Multiclass Multilink PPP (MCMP) feature in Cisco IOS Release 12.2(13)T addresses the limitations of MLP LFI on bundles containing multiple links by introducing multiple data classes. Normal data traffic and delay-sensitive data traffic are divided into Class 0 and Class 1, respectively. Class 0 data traffic is subject to fragmentation just as regular Multilink packets are. Class 1 data traffic can be interleaved but never fragmented. The next transmit sequence number, expected sequence number, unassigned fragment list, working packet, lost fragment timer, fastswitching mode, and all statistics are managed per-class, rather than for the bundle as a whole.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftmmlppp.htm
NAT Default Inside Server
The NAT Default Inside Server feature provides for the need to forward packets from the outside to a specified inside local address. Traffic is redirected that does not match any Network Address Translation (NAT) entries and the packets are not dropped.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftnatis.htm
NAT Integration with MPLS VPNs
Network Address Translation (NAT) and MPLS VPNs can now be configured on a single device to work together. NAT can differentiate which MPLS VPN it receives IP traffic from even if the MPLS VPNs are all using the same IP addressing scheme. This enhancement enables MPLS VPN customers the ability to provide common shared services across multiple MPLS VPN customers while ensuring that each MPLS VPN is completely separate from the other.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftnatvpn.htm
NAT MIB (Read-Only)
This feature introduces support for the Network Address Translation (NAT) MIB. NAT provides tables for translating internal network addresses external network addresses. The NAT MIB provides objects for the monitoring and management of NAT bindings and session using SNMP. In this release, access to the MIB is limited to the read-only level. No new or modified Cisco IOS commands are associated with this MIB.
For details on the management options provided by the MIB, see the CISCO-IETF-NAT-MIB.my file available in the "SNMP v2 MIBs" section of the Cisco.com MIB page at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml. Additional information on the MIB is available in the form of an internet draft (draft-ietf-nat-natmib), available through www.ietf.org.
NAT Protocol Translation
Network Address Translation - Protocol Translation (NAT PT) is an IPv6 translation mechanism allowing IPv6-only devices to communicate with IPv4-only devices, and vice versa. NAT PT was designed using RFC 2766 as a migration tool to help customers transition their IPv4 networks to IPv6 networks. Using existing IPv4 NAT capability and adding a protocol translator allows NAT PT to provide direct communication between hosts speaking a different network protocol.
NAT Stateful Failover of Network Address Translation
There is an increasing need to provide highly resilient IP networks where application connectivity continues unaffected by potential failure to links and routers at the Network Address Translation (NAT) border. The Stateful NAT feature allows two or more network address translators to function as a translation group. A backup router running NAT provides translation services in the event of failure of the active translator.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftsnat.htm
NAT Support of H.323 RAS
Cisco IOS NAT supports all H.225 and H.245 message types, including those sent in the RAS protocol. RAS provides a number of messages that are used by software clients and Voice over IP (VoIP) devices to register their location, request assistance in call setup, and control bandwidth. The RAS messages are directed toward an H.323 gatekeeper.
Some RAS messages include IP addressing information in the payload, typically meant to register a user with the gatekeeper or learn about another user already registered. If these messages are not known to NAT, they cannot be translated to an IP address that will be visible to the public.
Previously, NAT did not support H.323 v2 RAS messages. With this enhancement, embedded IP addresses can be inspected for potential address translation.
This feature was previously released in Cisco IOS Release 12.2(4)T on the Catalyst 2900, Catalyst 2900XL, Catalyst 4000 series, Catalyst 5000 family switches with an installed Route Switch Module, Catalyst 6000, Catalyst 8500 series, Cisco 800 series, Cisco 1000 series, Cisco1400 series, Cisco 1600 series, Cisco 1700, Cisco 2600 series, Cisco 3600 series, Cisco 4000 series, Cisco 6400 series, Cisco 7000 series, Cisco 8500 series, Cisco 12000 series, Cisco MC3810, Cisco uBR900 series, Cisco uBR7200, and LightStream 1010 series platforms. This release is porting the feature into the IAD2420 platform.
NAT-Support of H.323 v2 Call Signaling
Cisco IOS NAT supports all H.225 and H.245 message types, including FastConnect and Alerting, as part of the H.323 v2 specification.
Previously, NAT only supported H.323 version 1 and that was specific only to the Microsoft NetMeeting application. With this enhancement, any product that makes use of these message types will be able to pass through a Cisco IOS NAT configuration without any static configuration.
This feature was previously released in Cisco IOS Release 12.1(5)T on the Cisco Catalyst 2900, Cisco Catalyst 2900XL, Cisco Catalyst 4000 series, Cisco Catalyst 5000 family switches with an installed Route Switch Module, Cisco Catalyst 6000 series, Cisco Catalyst 8500 series, Cisco LightStream 1010 series, Cisco 800 series, Cisco 1000 series, Cisco 1400 series, Cisco 1600 series, Cisco 1700 series, Cisco 2500 series, Cisco 2600 series, Cisco 3600 series, Cisco 4000 series, Cisco AS5300, Cisco AS5400, Cisco AS5800, Cisco 6400 series, Cisco 7000 series, Cisco 8500 series, Cisco 12000 series, Cisco MC3810, Cisco uBR900, and Cisco uBR7200 platforms. This release is porting the feature into the Cisco IAD2420 platform.
NetWare Link Services Protocol (NLSP)
The NetWare Link Services Protocol (NLSP) will no longer be offered after Cisco IOS Release 12.2(13)T. NLSP commands will not appear in future releases of the Cisco IOS software documentation set.
Next Hop Resolution Protocol (NHRP) for IPX
The Next Hop Resolution Protocol (NHRP) for IPX will no longer be offered after Cisco IOS Release 12.2(13)T. NHRP for IPX commands will not appear in future releases of the Cisco IOS software documentation set.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftjencrg.htm
OSPF Support for Multi-VRF on CE Routers
The OSPF Support for Multi-VRF on CE Routers feature provides the capability of suppressing provider edge (PE) checks which are needed to prevent loops when the PE is performing a mutual redistribution of packets between the OSPF and BGP protocols. When VRF is used on a router that is not a PE (that is, one that is not running BGP), the checks can be turned off to allow for correct population of the VRF routing table with routes to IP prefixes.
OSPF multi-VRF allows you to split the router into multiple virtual routers, where each router contains its own set of interfaces, routing table, and forwarding table.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st21/ospfvrfl.htm
Packet Classification Based on Layer 3 Packet Length
This feature allows customers to match and classify traffic on the basis of the layer 3 length in the IP header of a packet. The layer 3 length is the IP datagram plus the IP header.
Traffic that matches a particular layer 3 length can be organized into specific classes that can, in turn, receive specific user-defined quality of service (QoS) treatment (for example, a certain amount of bandwidth or an IP Precedence value) when that class is included in a policy map.
This feature provides the added capability of matching and classifying traffic on the basis of the layer 3 length in the IP packet header. This new match criterion is in addition to the other match criteria, such as the IP precedence, differentiated services code point (DSCP) value, class of service (CoS), currently available.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftmchpkt.htm
Packet Classification Using the Frame Relay DLCI Number
The Packet Classification Using the Frame Relay DLCI Number feature allows customers to match and classify traffic based on the Frame Relay data-link connection identifier (DLCI) number associated with a packet. This new match criterion is in addition to the other match criteria, such as the IP Precedence, Differentiated Service Code Point (DSCP) value, Class of Service (CoS), currently available.
The Packet Classification Using the Frame Relay DLCI Number feature extends the functionality of the Modular Quality of Service (QoS) Command-Line Interface (CLI) (MQC).
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftpcdlci.htm
Per VRF AAA
Using the Per VRF AAA feature, Internet Service Providers (ISPs) can partition authentication, authorization, and accounting (AAA) services based on Virtual Route Forwarding (VRF). This feature permits the Virtual Home Gateway (VHG) to communicate directly with the customer's RADIUS server, which is associated with the customer's Virtual Private Network (VPN), without having to go through a RADIUS proxy. Thus, ISPs can scale their VPN offerings more efficiently because they no longer need to proxy AAA to provide their customers with the flexibility they demand.
This feature was originally introduced in Cisco IOS Release 12.2(1)DX. This release is porting the feature into the Cisco 7100 series, Cisco 7500 series, and Cisco 7700 series platforms.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftvrfaaa.htm
Percentage-Based Policing and Shaping
This feature provides the ability to configure traffic policing and traffic shaping based on a percentage of bandwidth available on the interface. Configuring traffic policing and traffic shaping in this manner enables customers to use the same policy map for multiple interfaces with differing amounts of bandwidth.
PPPoE Client DDR Idle-Timer
This feature supports the dial-on-demand routing (DDR) interesting traffic control list functionality of the dialer interface with a PPP over Ethernet (PPPoE) client, but also keeps original functionality (PPPoE connection up and always on after configuration) for those PPPoE clients that require it.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftppecls.htm
Privilege Command Enhancement
This feature simplifies the configuration of privilege levels for specific commands through the enhancement of the privilege level global configuration command. A privilege level can now be specified for all keyword options of a command with a single command-line interface (CLI) command. Previously, separate "privilege level" commands were required for each keyword combination of a command. This enhancement can significantly reduce the number of commands needed to configure user privilege levels and correspondingly reduce the size of configuration files.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftprienh.htm
RADIUS Attribute 52 and Attribute 53 Gigaword Support
The RADIUS Attribute 52 and Attribute 53 Gigaword Support feature introduces support for Attribute 52 (Acct-Input-Gigawords) and Attribute 53 (Acct-Output-Gigawords) in accordance with RFC 2869. Attribute 52 keeps track of the number of times the Acct-Input-Octets counter has rolled over the 32-bit integer throughout the course of the provided service; attribute 53 keeps track of the number of times the Acct-Output-Octets counter has rolled over the 32-bit integer throughout the delivery of service. Both attributes can be present only in Accounting-Request records where the Acct-Status-Type is set to "Stop" or "Interim-Update." These attributes can be used to keep accurate track of and bill for usage.
This feature was originally introduced in Cisco IOS Release 12.2(4)B. No additional platform support has been added.
RADIUS Attribute 77 for DSL
The RADIUS Attribute 77 for DSL feature introduces support for Attribute 77 (Connect-Info) to carry the textual name of the virtual circuit class associated with the given permanent virtual circuit (PVC). (Although attribute 77 does not carry the unspecified bit rate (UBR), the UBR can be inferred from the classname used if one UBR is set up on each class.) Attribute 77 is sent from the network access server (NAS) to the RADIUS server via Accounting-Request and Accounting-Response packets.
This feature was originally introduced in Cisco IOS Release 12.2(4)B. No additional platform support has been added.
RADIUS Centralized Filter Management
Before the RADIUS Centralized Filter Management feature, wholesale providers (who provide premium charges for customer services such as access control lists [ACLs]) were unable to prevent customers from applying exhaustive ACLs, which could impact router performance and other customers. This feature introduces a centralized administration point—a filter server—for ACL management. The filter server acts as a centralized RADIUS repository for ACL configuration.
Whether or not the RADIUS server that is used as the filter server is the same server that is used for access authentication, the network access server (NAS) will initiate a second access-request to the filter server. If configured, the NAS will use the filter-id name as the authentication username and the filter server password for the second access-request. The RADIUS server will attempt to authenticate the filter-id name, returning any required filtering configuration in the access-accept.
Because downloading ACLs is time consuming, a local cache is maintained on the NAS. If an ACL name exists on the local cache, that configuration will be used without consulting the filter server.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ft_ftrmn.htm
RADIUS EAP Support
The EAP RADIUS Support feature allows users to apply to the client authentication methods that may not be supported by the network access server; this is done via the Extensible Authentication Protocol (EAP). Before this feature was introduced, support for various authentication methods for PPP connections required custom vendor-specific work and changes to the client and NAS.
EAP is an authentication protocol for PPP that supports multiple authentication mechanisms that are negotiated during the authentication phase (instead of the link control protocol [LCP] phase). EAP allows a third-party authentication server to interact with a PPP implementation through a generic interface.
This feature was originally introduced in Cisco IOS Release 12.2(2)XB5. This release is porting the feature into the Catalyst 4000, Cisco AS5350, Cisco AS5800, Cisco AS5850, Cisco 05, Cisco 806, Cisco 820, Cisco 1400 series, Cisco 1600 series, Cisco 1600R, Cisco 2500 series, Cisco 2600 series, Cisco 3620, Cisco 7100 series, Cisco 7200 series, Cisco 7500 series, Cisco MC3810, Cisco SOHO 70 series, Cisco SOHO78, Cisco uBR7200, Cisco uBR920
RADIUS Logical Line ID
The RADIUS Logical Line ID feature enables users to track their customers on the basis of the physical lines in which the customers' calls originate. Thus, users can better maintain the profile database of their customers as the customers move from one physical line to another.
Logical Line Identification (LLID) is an alphanumeric string (which must be a minimum of one character and a maximum of 253 characters) that is a logical identification of a subscriber line. LLID is maintained in a RADIUS server customer profile database. This customer profile database is connected to a L2TP access concentrator (LAC) and is separate from the RADIUS server that the LAC and L2TP Network Server (LNS) use for the authentication and authorization of incoming users. When the customer profile database receives a preauthorization request from the LAC, the server sends the LLID to the LAC as the Calling-Station-ID attribute (attribute 31).
The LAC sends a preauthorization request to the customer profile database when the LAC is configured for preauthorization. Configure the LAC for preauthorization using the subscriber access pppoe pre-authorize command.
This feature was originally introduced in Cisco IOS Release 12.2(8)B. No additional platform support has been added.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftlineid.htm
RSVP Local Policy Support
The RSVP Local Policy Support feature allows network administrators to create default and access control list (ACL)-based policies. These policies, in turn, control how RSVP filters its signalling messages to allow or deny quality of service (QoS) to networking applications based on the IP addresses of the requesting hosts.
This feature is being introduced in Cisco IOS Release 12.2(13)T.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftrsvplp.htm
RSVP Refresh Reduction and Reliable Messaging
The RSVP Refresh Reduction and Reliable Messaging feature includes refresh reduction, which improves the scalability, latency, and reliability of RSVP signalling by introducing the following extensions:
•
•
•
This feature was originally introduced in Cisco IOS Release 12.2(11)S. This release integrates the feature into Cisco IOS Release 12.2(13)T.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftrsvpre.htm
Session Limit Per VRF
The Session Limit Per VPN Routing and Forwarding Instance (VRF) feature enables session limits to be applied on all VPDN groups associated with a common VPDN virtual template. Before the implementation of Session Limit Per VRF, a single default template carrying the configuration values of a subset of VPDN group commands were associated with all VPDN groups configured on the router. Session Limit Per VRF enables you to create, define and name multiple VPDN templates. You can then associate a specific template with a VPDN group. A session limit can be configured at the VPDN template level to specify a combined session limit for all VPDN groups associated with the configured VPDN template.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122b/122b_4/12b_vrf.htm
Show Command Output Redirection
This feature adds the capability to redirect output from Cisco IOS CLI show commands to a file. For each show command issued, a new file can be created, or the output can be appended to an existing file. Command output can optionally be displayed on-screen while being redirected to a file by using the tee keyword. Redirection is available using a pipe (|) character after any show command, combined with the redirect, append, or tee keywords.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftshowre.htm
Simple Multicast Routing Protocol (SMRP) for AppleTalk
The Simple Multicast Routing Protocol (SMRP) for AppleTalk will no longer be offered after Cisco IOS Release 12.2(13)T. NLSP commands will not appear in future releases of the Cisco IOS software documentation set.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftjencrg.htm
SIP and H.323 Fax Enhancements
The SIP and H.323 Fax Enhancements feature adds an assortment of fax transfer enhancements to the Cisco IOS gateway implementations of H.323 and Session Initiation Protocol (SIP) call control protocols. The enhanced areas include the use of:
•
•
•
•
•
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftsihfax.htm
SIP—Call Transfer Enhancements Using the Refer Method
The SIP—Call Transfer Enhancements Using the Refer Method feature provides blind and attended call transfer capabilities to supplement the Bye and Also methods already implemented on Cisco IOS Session Initiation Protocol (SIP) gateways. The SIP—Call Transfer Enhancements Using the Refer Method feature is compatible with the original forms of call transfer and with third-party call-control protocols. The SIP—Call Transfer Enhancements Using the Refer Method feature enables application service providers (ASPs) to provide attended transfer and blind transfer in accordance with emerging SIP standards.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftsipref.htm
SIP Enhanced 180 Provisional Response Handling
This feature provides the ability to enable or disable early media cut-through on Cisco IOS gateways for SIP 180 response messages. The new feature allows you to specify whether 180 messages with Session Description Protocol (SDP) are handled in the same way as 183 responses with SDP. The 180 Ringing message is a provisional or informational response used to indicate that the INVITE message has been received by the user agent and that alerting is taking place. Both 180 and 183 messages may contain SDP which allow an early media session to be established prior to the call being answered.
Prior to the implementation of the new feature, Cisco gateways handled a 180 Ringing response with SDP in the same manner as a 183 Session Progress response; that is, the SDP was assumed to be an indication that the far end was going to send early media. Cisco gateways handled a 180 response without SDP by providing local ringback, rather than early media cut-through. The new feature provides the capability to ignore the presence or absence of SDP in 180 messages, and as a result, treat all 180 messages in a uniform manner.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ft180sdp.htm
SIP Extensions for Caller Identity and Privacy
This feature provides support for privacy indication, as well as network verification and screening of a call participant's name and number. Cisco implements the new feature on Cisco SIP IOS trunking gateways by supporting a new header, Remote-Party-ID. In previous SIP implementations, the From header was used to indicate calling party identity, and once defined in the initial INVITE request, could not be modified for the duration of that session. Implementing the Remote-Party-ID header, which can be modified, added or removed as a call session is being established, overcomes previous limitations and enables call participant verification and screening
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftsipext.htm
SIP Gateway Compliance to RFC2543-bis-04
RFC2543-bis-04 contains several changes to Session Initiation Protocol (SIP) gateway code. The SIP Gateway Compliance to RFC2543-bis-04 feature updates Cisco SIP Voice over IP (VoIP) gateways with the latest RFC changes. All changes are compatible with older RFC versions. Some of the changes include:
•
•
•
•
•
•
•
•
•
•
•
•
SIP Redirect Processing Enhancements
The SIP Redirect Processing Enhancements feature allows flexibility in the handling of incoming redirect or 3xx class of responses so they can be enabled or disabled through the command-line interface (CLI). The default mode is enabled, in which Session Initiation Protocols (SIP) gateways handle incoming 3xx messages as per RFC 2543. RFC 2543 states that redirect response messages are used by SIP user agents (UA) to initiate a new Invite when a UA learns that a user has moved from a previously known location. If redirect handling is disabled through the CLI, the UA treats incoming 3xx responses as 4xx error class responses. The call is not redirected, and is instead released with the appropriate PSTN cause code.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftsipmaz.htm
SNMP Notification Logging
Systems that support Simple Network Management Protocol (SNMP) often need a mechanism for recording notification information as a hedge against lost notifications, whether those are traps or informs that exceed retransmission limits. The Notification Log MIB provides a common infrastructure for other MIBs in the form of a local logging function. The SNMP Notification Logging feature adds Cisco IOS command-line interface (CLI) commands to change the size of the notification log, to set the global ageout value for the log, and to display logging summaries at the command line.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/ftmiblog.htm
SSG Autologoff
The SSG Autologoff feature enables the Cisco Service Selection Gateway (SSG) to verify connectivity with each host at configured intervals. If SSG detects that the host is not reachable from SSG, then it automatically initiates the logoff for that host.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ssg/index.htm
SSG Port-Bundle Host Key
The SSG Port-Bundle Host Key feature enhances communication and functionality between the Service Selection Gateway (SSG) and the Cisco Subscriber Edge Services Manager (SESM) by introducing a mechanism that uses the host source IP address and source port to identify and monitor subscribers.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ssg/index.htm
SSG TCP Redirect for Services
The SSG TCP Redirect for Services feature redirects certain packets, which would otherwise be dropped, to captive portals that can handle the packets in a suitable manner. For example, packets sent upstream by unauthorized users are forwarded to a captive portal that can redirect the users to a logon page. Similarly, if users try to access a service to which they have not logged on, the packets are redirected to a captive portal that can provide a service logon screen.
The captive portal can be any server that is programmed to respond to the redirected packets. If the Cisco Subscriber Edge Services Manager (SESM) is used as a captive portal, unauthenticated subscribers can be sent automatically to the SESM logon page when they start a browser session. In SESM Release 3.1(3), captive portal applications can also redirect to service logon pages, advertising pages, and message pages. The SESM captive portal application can also capture a URL in a subscriber's request and redirect the browser to the originally requested URL after successful authentication. Redirected packets are always sent to a captive portal group that consists of one or more servers. SSG selects one server from the group in a round-robin fashion to receive the redirected packets.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ssg/index.htm
Subscriber Service Switch (SSS)
The Subscriber Service Switch (SSS) was developed in response to a need by Internet service providers for increased scalability and extensibility for remote access service selection and Layer 2 subscriber policy management. This Layer 2 subscriber policy is needed to manage tunneling of PPP, Ethernet, Frame Relay, and other link-level protocols in a policy-based bridging fashion
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ft_sss.htm
Support for IPsec ESP Through NAT
The ability to support multiple concurrent IPsec ESP tunnels or connections through a router configured with Network Address Translation (NAT) can now be utilized when the NAT router is configured in overload or Port Address Translation (PAT) mode.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftnatesp.htm
T.38 Fax Relay for VoIP H.323
T.38 Fax Relay for VoIP H.323 provides standards-based fax relay protocol support for H.323 gateways and gatekeepers. T.38 is an ITU-T recommended standard for fax relay. Since T.38 is a standards-based implementation for fax relay, Cisco gateways and gatekeepers are able to interwork with third-party H.323 devices that support T.38 protocol.
This feature was previously released in Cisco IOS Release 12.1(3)T on Cisco 2600 series, Cisco 3640, and Cisco MC3810 platforms. This release is porting the feature into the IAD2420 platform.
Terminal Line Security for PAD Connections
X.25 closed user group (CUG) service is a network service that allows subscribers to be segregated into private subnetworks with limited outgoing and incoming access. A data terminal equipment (DTE) device becomes a member of a CUG by subscription; the DTE must obtain membership from its network service for the set of CUGs to which it needs access.
The Terminal Line Security for PAD Connections feature allows CUG services to be configured on terminal lines, enabling terminal lines to participate in X.25 CUG security for packet assembler/disassembler (PAD) connections. CUG services can be applied to console lines, auxiliary lines, and tty and vty devices. Configuring CUG services on terminal lines allows you to specify CUG protection for lines that are part of the point of presence (POP). Before the introduction of this feature, CUG services could be configured only on X.25 synchronous data communications equipment (DCE) interfaces.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftcugpad.htm
Update to the Interworking of Cisco MGCP Voice Gateways and Cisco CallManager Version 3.2 Feature
This document describes updates to the Interworking of Cisco MGCP Voice Gateways and Cisco Call Manager Version 3.2 feature. This update introduces the mgcp validate domain-name command, which enables you to check if the domain name or host name and the IP address received as part of the endpoint names sent from the Call Agent (CA) or Cisco CallManager (CCM) match with the ones that have been configured on the gateway (GW). This check is valid for the MGCP messages received from the CA or CCM only.
Use the new mgcp validate domain-name command first before configuring MGCP in a Voice over IP (VoIP) network.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftvalid.fm
Update to the playout-delay Command
In environments with long network delays, T.38 fax relay can be unsuccessful. The fax keyword was added to the playout-delay command to allow users to decrease the playout delay value to compensate for long network delays when necessary.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ft_pdfax.htm
Virtual Router Redundancy Protocol (VRRP)
There are several ways a LAN client can determine which router should be the first hop to a particular remote destination. The client can use a dynamic process or static configuration. Examples of dynamic router discovery are as follows:
•
•
•
The drawback to dynamic discovery protocols is that they incur some configuration and processing overhead on the LAN client. Also, in the event of a router failure, the process of switching to another router can be slow.
An alternative to dynamic discovery protocols is to statically configure a default router on the client. This approach simplifies client configuration and processing, but creates a single point of failure. If the default gateway fails, the LAN client is limited to communicating only on the local IP network segment and is cut off from the rest of the network.
The Virtual Router Redundancy Protocol (VRRP) feature can solve the static configuration problem. VRRP enables a group of routers to form a single virtual router. The LAN clients can then be configured with the virtual router as their default gateway. The virtual router, representing a group of routers, is also known as a VRRP group.
VRRP is supported on Ethernet, Fast Ethernet, and Gigabit Ethernet interfaces, and on MPLS VPNs and VLANs.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st18/st_vrrpx.htm
VLAN Range
Using the VLAN Range feature, you can group VLAN subinterfaces together so that any command entered in a group applies to every subinterface within the group. This capability simplifies configurations and reduces command parsing.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122b/122b_4/12b_rang.htm
Voice and Quality of Service Features for ADSL and G.SHDSL on Cisco 1700, Cisco 2600, and Cisco 3600 Series Routers
Cisco 1700 series, Cisco 2600 series, and Cisco 3600 series routers with ADSL or G.SHDSL WAN interface cards support the integration of voice and data over the same ADSL or G.SHDSL circuit using Voice over IP (VoIP). Cisco 2600 series and Cisco 3600 series routers with ADSL or G.SHDSL WAN interface cards also support the integration of voice and data over the same ADSL or G.SHDSL circuit using Voice over ATM (VoATM).
This feature was originally introduced in Cisco IOS Release 12.2(4)XL. This release is porting the feature into the Cisco 1700 series platforms.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xl/122xl4/ft_qgdsl.htm
Voice Call Tuning
This feature provides tools for quickly taking spot performance measurements of voice call performance while the call is up. You also have the ability to change the echo canceller and jitter buffer parameters of a call while the call is in progress. Audible effects can be immediately noticed, aiding in problem determination and resolution. The feature provides real-time call monitor and manipulation on the interface between Cisco IOS software and the digital signalling processors (DSPs) by addressing the following two items:
•
•
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftvdsptn.htm
VPDN Multihop by DNIS
The Cisco VPDN Multihop by DNIS feature allows dialed number identification service (DNIS)-based multihop capability in a virtual private dial-up network (VPDN), which enables customers that dial in to a network using a standard telephone line to take advantage of the aggregation capability offered by multihop switching.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122b/122b_8/ftvmhopd.htm
VRRP Support
There are several ways a LAN client can determine which router should be the first hop to a particular remote destination. The client can use a dynamic process or static configuration. Examples of dynamic router discovery are as follows:
•
•
•
The drawback to dynamic discovery protocols is that they incur some configuration and processing overhead on the LAN client. Also, in the event of a router failure, the process of switching to another router can be slow.
An alternative to dynamic discovery protocols is to statically configure a default router on the client. This approach simplifies client configuration and processing, but creates a single point of failure. If the default gateway fails, the LAN client is limited to communicating only on the local IP network segment and is cut off from the rest of the network.
The Virtual Router Redundancy Protocol (VRRP) feature can solve the static configuration problem. VRRP enables a group of routers to form a single virtual router. The LAN clients can then be configured with the virtual router as their default gateway. The virtual router, representing a group of routers, is also known as a VRRP group.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st18/st_vrrpx.htm
X.25 Suppression of Security Signaling Facilities
This feature allows the X.25 Call Redirection/Call Deflection Notification (CRCDN) and Called Line Address Modified Notification (CLAMN) security signaling facilities to be disabled (suppressed) in packets that transit data communication equipment that uses a mix of International Telecommunication Union Telecommunication Standardization Sector T (ITU-T) 1980 and 1984 X.25 protocols.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftsupsgx.htm
Xerox Network Systems (XNS)
The Xerox Network Systems (XNS) feature will no longer be offered after Cisco IOS Release 12.2(13)T. XNS commands will not appear in future releases of the Cisco IOS software documentation set.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftjencrg.htm
New Hardware Features Supported in Cisco IOS Release 12.2(11)T1
The following new hardware features are supported in Cisco IOS Release 12.2(11)T1. Some of these features may have been introduced on other hardware platforms in earlier Cisco IOS software releases.
Cisco 3640A Router
The Cisco 3640A is identical to the Cisco 3640 router in terms of physical characteristics, interface support, performance and memory. The Cisco 3640A router will support the same Cisco IOS feature sets as the Cisco 3640 router, but requires a different minimum version of Cisco IOS software.
Hardware Platforms and Modules Newly Supported in Cisco IOS Release 12.2(11)T
The following hardware platforms and modules are now supported in Cisco IOS Release 12.2(11)T. These platforms and modules were first introduced in earlier Cisco IOS software releases.
16-Port Ethernet Switch Module for Cisco 2600 Series and Cisco 3600 Series
The 16-port Ethernet switch network module was originally introduced in Cisco IOS Release 12.2(8)T. Cisco IOS Release 12.2(11)T adds stacking and flow control features to the previously released feature.
See the "16-Port Ethernet Switch Module for Cisco 2600 Series and Cisco 3600 Series" section or refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t11/ft1636nm.htm.
Cisco 1760 Router
The Cisco 1760 router is a voice-and-data-capable router that provides Voice-over-IP (VoIP) functionality and can carry voice traffic (for example, telephone calls and faxes) over an IP network. Using one or two WAN connections, the router links small-to-medium-size remote Ethernet and Fast Ethernet LANs to central offices.
The Cisco 1760 router is available in two models. The Cisco 1760 runs data and data-plus-voice images, providing digital and analog voice support. The Cisco 1760-V includes all the features needed for immediate integration of data and voice services with support for multiple voice channels.
Refer to the documents at the following location for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/index.htm.
Cisco AS5350 Universal Gateway
The Cisco AS5350 Universal Gateway is the only one-rack-unit, two, four, or eight PRI gateway that provides universal services—data, voice, and fax services on any service, any port. The Cisco AS5350 offers high performance and high reliability in a compact, modular design. This cost-effective platform is ideally suited for Internet service providers (ISPs) and enterprises that require innovative universal services.
Refer to the documents at the following location for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5350/index.htm.
Cisco AS5850 Universal Gateway
The Cisco AS5850 Universal Gateway provides the highest concentration of port and Integrated Services Digital Network (ISDN) terminations available in a single remote access server product. The Cisco AS5850 is specifically designed to meet the demands of large service providers such as Post, Telephone, and Telegraphs (PTTs), regional bell operating companies (RBOCs), inter-exchange carriers (IXCs), and large Internet service providers (ISPs).
Refer to the documents at the following location for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5850/index.htm.
Cisco Signaling Link Terminal (SLT) Dual Ethernet
The Cisco Signaling Link Terminal (SLT) Dual Ethernet feature adds Cisco Cisco Signaling Link Terminal dual Ethernet support to the virtual switch controller (VSC). This enhanced Cisco SLT support provides two IP networks and two additional Session Manager sessions (for a total of four Session Manager sessions) for improved backhaul communication. These additions increase the resilience of Cisco SLT and VSC communications by supporting two Reliable User Datagram Protocol (RUDP) sessions from each Ethernet interface to each VSC. These VSC enhancements help to determine when to switch Ethernets and when to switch VSC activity.
The Cisco SLT, which is based on the Cisco 2611 router, is shipped with two Ethernet interfaces. Until this feature was released, the Cisco SLT and VSC solution supported only one of the two Ethernet interfaces. Both Session Manager sessions had to travel over this single Ethernet interface. The Cisco Signaling Link Terminal Dual Ethernet feature supports the second Ethernet, which improves the resilience of the backhaul IP communications.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t11/ftsltdua.htm.
New Software Features in Cisco IOS Release 12.2(11)T
The following new features are supported in Cisco IOS Release 12.2(11)T. Some of these features may have been introduced on other hardware platforms in earlier Cisco IOS software releases.
AAA-PPP-VPDN Non-Blocking
Previously, Cisco IOS created a statically configurable number of processes to authenticate calls. Each of these processes would handle a single call, but in some situations the limited number of processes could not keep up with the incoming call rate. This resulted in some calls timing out. The AAA-PPP-VPDN Non-Blocking feature changes the software architecture such that the number of processes will not limit the rate of call handling.
Note
Accounting of VPDN Disconnect Cause
In the past, whenever a Layer 2 Tunneling Protocol (L2TP) or Layer 2 Forwarding (L2F) session fails or disconnects, the network access server (NAS) and Home GateWay (HGW) report a very generic disconnect-cause code, such as "LOST CARRIER". These generic codes do not provide enough detailed information for accounting and debugging purposes, creating a need for disconnect-cause codes that provide more detailed information. The Accounting of VPDN Disconnect Cause feature adds eight new disconnect-cause codes. These eight disconnect-cause codes describe the status of Virtual Private Dialup Network (VPDN) failures and disconnects more specifically than existing generic disconnect-cause codes. These new disconnect-cause codes can be found in the Cisco IOS Security Configuration Guide, Release 12.2 located at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fsecur_c/fappendx/scgrdat3.htm.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t4/ftacldir.htm.
Note
ACL Authentication of Incoming rsh and rcp Requests
To enable the Cisco IOS software to receive incoming remote shell (rsh) protocol and remote copy (rcp) protocol requests, customers must configure an authentication database to control access to the router. This configuration is accomplished by using the ip rcmd remote-host command.
Currently, when using this command, customers must specify the local user, the remote host, and the remote user in the database authentication configuration. For users who can execute commands to the router from multiple hosts, multiple database authentication configuration entries must be used, one for each host.
This feature allows customers to specify an access list for a given user. The access list identifies the hosts to which the user has access. A new argument, access-list, has been added that can be used with this command to specify the access list.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/ftauth.htm.
Note
ACL Default Direction
The ACL Default Direction feature allows you to change the filter direction (where filter direction is not specified) to inbound packets only; that is, you can configure your server to filter packets that are coming toward the network.
This feature introduces the radius-server attribute 11 direction default command, which allows you to change the default direction of filters for your access control lists (ACL) via RADIUS. (RADIUS attribute 11 (Filter-Id) indicates the name of the filter list for the user.) Enabling this command allows you to change the filter direction to inbound—which stops traffic from entering a router, thereby reducing resource consumption—rather than the outbound default direction, which waits until the traffic is about to leave the network before filtering. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t4/ftacldir.htm.
Note
Advanced Voice Busyout
The local voice busyout feature provides a way to busy out a voice port or DS-0 group (time slot) if a state change is detected in a monitored network interface (or interfaces). When a monitored interface changes to a specified state—to out-of-service or in-service—the voice port presents a seized/busyout condition to the attached PBX or other customer premises equipment (CPE). The PBX or other CPE can then attempt to select an alternate route.
Advanced Voice Busyout adds the following functionality to the local voice busyout feature:
•
•
Using the Advanced Voice Busyout feature you can perform the following tasks:
•
•
•
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xa/122xa_2/ft_cacbo.htm.
Note
Analog Centralized Automatic Message Accounting E911 Trunk
Cisco IOS Release 12.2(11)T is the first Cisco IOS release that introduces the Analog Centralized Automatic Message Accounting (CAMA) E911 feature that adds E911 connectivity features to the Cisco 2600 series and Cisco 3600 series routers.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t11/acam_911.htm.
Asynchronous Line Monitoring
Before Cisco IOS Release 12.2(4)T, the Cisco IOS software did not provide a method for displaying asynchronous character mode traffic flowing out of an asynchronous line. Therefore, when a user tried to troubleshoot difficult asynchronous problems, the user had to use RS-232 datascopes to examine the data stream. This method is detailed and cumbersome. The Asynchronous Line Monitoring feature that is available in Cisco IOS Release 12.2(4)T allows the monitoring of inbound and outbound character mode asynchronous traffic on another terminal line. To monitor inbound or outbound asynchronous character mode traffic on the port to be monitored, enter the monitor traffic line command in privileged EXEC mode.
This feature increases the efficiency of the user who performs troubleshooting on asynchronous character mode traffic problems.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t11/ftasync.htm.
Note
ATM Service Level Monitoring (SLM)
The Cisco Service Assurance Agent (SA Agent) is an embedded performance monitoring utility in Cisco IOS software. The ATM Service Level Monitoring (SLM) feature expands the capabilities of the SA Agent to provide detailed monitoring statistics for your ATM network. Monitoring service levels for ATM connections allows service providers to ensure that their networks are meeting or exceeding the performance outlined in service level agreements (SLAs).
The ATM Service Level Monitoring feature can also be used with Cisco Networking Services (CNS). A device running CNS, such as the IE2100, can be used to retrieve the ATM performance statistics generated by the SA Agent. Additionally, these results can be passed to other devices running third-party monitoring software.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t11/ftatmslm.htm
Barge-In and Busy Line Verify Operator Services
The Barge-In and Busy Line Verify Operator Services feature enhances Simple Gateway Control Protocol (SGCP)/Media Gateway Control Protocol (MGCP) gateway conferencing capabilities to support the Busy Line Verification/Operator Interrupt (BLV/OI) feature. The Busy Line Verification feature permits an operator to establish a connection to a customer's line to verify a busy condition for a calling party. The Operator Interrupt feature allows the operator to speak to the customer and to connect the calling party and customer, if appropriate. These enhancements support other call flows such as call pickup with barge-in that require the ability to conference a second call into an existing two-party call without intervention by parties in the existing call. No explicit configuration is required to enable this feature.
The MGCP Basic CLASS and Operator Services feature introduced conferencing to support three-way calling on SGCP and MGCP gateways. It is described in MGCP Basic CLASS and Operator Services at
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ftmgcpgr.htm.
Basic Service Relationships (H.225 Annex G)
Cisco's H.225 Annex G implements the minimal set of Annex G features needed to allow Cisco border elements to interoperate with any ClearingHouse border element. This feature enhances Cisco's H.225.0 Annex G support to include basic Service Relationships and Usage Reporting. The feature provides enhanced interoperability with a ClearingHouse border element and third party border element as well as address resolution for interdomain call routing.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t11/ft_srang.htm.
BGP Conditional Route Injection
Cisco IOS software provides several methods in which you can originate a prefix into the Border Gateway Protocol (BGP). The existing methods include using the network or aggregate-address commands and redistribution. These methods assume the existence of more specific routing information (matching the route to be originated) in either the routing table or the BGP table.
The BGP Conditional Route Injection feature enables you to originate a prefix into BGP without the corresponding match. The routes are injected into the BGP table only if certain conditions are met. The most common condition is the existence of a less-specific prefix.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t11/ft11bpri.htm.
Note
BGP Hide Local-Autonomous System
The BGP Hide Local-Autonomous System feature introduces the no-prepend keyword to the neighbor local-as command. The use of the no-prepend keyword allows a network operator to configure a Border Gateway Protocol (BGP) speaker to not prepend the local autonomous system number to any routes that are received from external peers. This feature can be used to help transparently change the autonomous system number of a BGP network and ensure that routes can be propagated throughout the autonomous system, while the autonomous system number transition is incomplete. Because the local autonomous is not prepended to these routes, external routes will not be rejected by internal peers during the transition from one autonomous system number to another.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t11/ft11bhla.htm.
Note
BGP Link Bandwidth
The Border Gateway Protocol (BGP) Link Bandwidth feature is used to advertise the bandwidth of an autonomous system exit link as an extended community. The BGP Link Bandwidth feature is supported by the internal BGP (iBGP) and external BGP (eBGP) multipath features. The link bandwidth extended community indicates the preference of an autonomous system exit link in terms of bandwidth. The link bandwidth extended community attribute may be propagated to all iBGP peers and used with the BGP multipath features to configure unequal cost load balancing. When a router receives a route from a directly connected external neighbor and advertises this route to iBGP neighbors, the router may advertise the bandwidth of that link. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t11/ft11b_lb.htm.
Note
BGP Multipath Load Sharing for Both eBGP and iBGP in an MPLS-VPN
The BGP Multipath Load Sharing for eBGP and iBGP feature allows you to configure multipath load balancing with both external BGP (eBGP) and internal BGP (iBGP) paths in Border Gateway Protocol (BGP) networks that are configured to use Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs). This feature provides improved load balancing deployment and service offering capabilities and is useful for multi-homed autonomous systems and Provider Edge (PE) routers that import both eBGP and iBGP paths from multihomed and stub networks. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t11/ft11bmpl.htm.
Note
BGP Prefix-Based Outbound Route Filtering
The BGP Prefix-Based Outbound Route Filtering feature uses Border Gateway Protocol (BGP) outbound route filter (ORF) send and receive capabilities to minimize the number of BGP updates that are sent between peer routers. The configuration of this feature can help reduce the amount of resources required for generating and processing routing updates by filtering out unwanted routing updates at the source. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t11/ft11borf.htm.
Note
Call Admission Control Based on CPU Utilization
The Preauthentication with ISDN PRI feature permits the Cisco AS5300 and AS5800 universal access servers to deny incoming calls exceeding a preconfigured threshold, permitting the selection of a system CPU load level value. This feature helps ensure the quality of service (QoS) of existing calls and reliability of system processes by preventing system overload that is caused by excessive incoming calls. The feature rejects new digital calls (PRI, channel-associated signaling [CAS], and ISDN), with minor disruption to system users.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5800/sw_conf/ios_122/dt61294.htm.
Call Admission Control for H.323 VoIP Gateways
Before the call admission control feature was available, gateways did not have a mechanism to prevent calls from entering when certain resources were not available to process the call. This situation caused new calls to fail with unreported behavior and potentially caused the calls in progress to have quality-related problems.
This feature set provides the ability to support resource-based call admission control processes. These resources include system resources such as CPU, memory, and call volume and interface resources such as call volume.
If system resources are not available to admit the call, the following two kinds of actions are provided: system denial (which busy outs all of T1 or E1) or per-call denial (which disconnects, hairpins, or plays a message or tone). If the interface-based resource is not available to admit the call, the call is dropped from the session protocol (such as H.323).
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t11/ftcac58.htm.
Note
Call Status Tracking Optimization
In an H.323 Voice-over-IP (VoIP) network, gatekeepers use information request (IRQ) messages to obtain information about a certain call or all calls from an endpoint (for example, an originating gateway). The gatekeeper can send an IRQ to request information from the endpoint, which responds with an information request response (IRR). The gatekeeper can also use the IRR Frequency field in the initial admission confirm (ACF) message to instruct the endpoint to periodically report with IRR messages during call admission.
Currently, the Cisco gatekeeper maintains the call states of all calls it has admitted to track bandwidth usage. In addition, the gatekeeper must be able to reconstruct call structures for a newly transferred gateway from an alternate gatekeeper, if a gatekeeper switchover has occurred. In a gatekeeper switchover, the new gatekeeper sends an IRQ message with the call reference value (CRV) set to zero to the newly registered gateway to obtain information about existing calls before the switchover.
If a gateway supports a large volume of calls, the number of IRR messages as responses to an IRQ with the CRV set to zero could be CPU intensive and cause congestion. Additionally, if a gatekeeper serves many endpoints or high-capacity gateways, the IRQ requests and the resulting IRR messages received can flood the network, causing high CPU utilization and network congestion.
The Call Status Tracking Optimization feature provides the following methods to address this potential problem:
•
•
•
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t11/ft_csto2.htm.
Call Tracker show Commands Extensions
Before Cisco IOS Release 12.2(11)T, the show calltracker active EXEC command and the show calltracker history EXEC command provided a simple way to examine the Call Tracker active table and Call Tracker history table in chronological order. The extensions to these commands available in Cisco IOS Release 12.2(11)T allow the command output to be reverse collated (output from most recent to least recent) or to be filtered by call category or service type. Historical data for disconnected call sessions can be filtered by subsystem type.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t11/ftcall.htm.
CEF on Multipoint GRE Tunnels
The CEF on Multipoint GRE Tunnels feature enables Cisco Express Forwarding (CEF) switching of IP traffic to and from multipoint generic routing encapsulation (GRE) tunnels. Tunnel traffic can be forwarded to a prefix through a tunnel destination when both the prefix and the tunnel destination are specified by the application.
Note
Certificate Autoenrollment
The Certificate Autoenrollment feature allows you to configure your router to automatically request a certificate from the certification authority (CA) that is using the parameters in the configuration. Thus, operator convention is no longer required at the time the enrollment request is sent to the CA server.
Automatic enrollment will be performed on startup for any trustpoint CA that is configured and does not have a valid certificate. When the certificate—which is issued by a trustpoint CA that has been configured for autoenrollment—expires, a new certificate is requested. Although this feature does not provide seamless certificate renewal, it does provide unattended recovery from expiration.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/ftautoen.htm.
Note
Certificate Enrollment Enhancements
The Certificate Enrollment Enhancements feature introduces five new subcommands to the crypto ca trustpoint command—ip-address (ca-trustpoint), password (ca-trustpoint), serial-number, subject-name, and usage. These commands provide new options for certificate requests and allow users to specify fields in the configuration instead of having to go through prompts. (However, the prompting behavior remains the default if this feature is not enabled.) Thus, users can preload all necessary information into the configuration, allowing each router to obtain its certificate automatically when it is booted.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/ftenrol2.htm.
Note
Circuit Interface Identification Persistence for SNMP
The Circuit Interface MIB (CISCO-CIRCUIT-INTERFACE-MIB) provides a MIB object (cciDescr) which can be used to identify individual circuit-based interfaces for SNMP monitoring. The Circuit Interface Identification Persistence for SNMP feature maintains this user-defined name of the circuit across reboots, allowing the consistent identification of circuit interfaces. Circuit Interface Identification Persistence is enabled using the snmp mib persist circuit global configuration command.
Note
Cisco Gateway Management Agent
The Cisco Gateway Management Agent (CGMA) feature provides an eXtensible Markup Language (XML) interface to support real-time management of a Cisco IOS gateway (GW). Currently, GWs provide statistics using Simple Network Management Protocol (SNMP) and do not support real-time polling. The CGMA feature allows GWs to communicate with third-party management applications using XML over TCP/IP.
Note
Cisco H.323 Multizone Enhancements
The Cisco H.323 Multizone Enhancements feature enables the Cisco gateway to provide information to the gatekeeper with the use of additional fields in the RAS (registration, admission, and status) messages.
Previously, the source gateway attempted to set up a call to a destination IP address as provided by the gatekeeper in an Admission Confirm (ACF) message. If the gatekeeper was unable to resolve the destination E.164 phone number to an IP address, the incoming call was terminated.
This version of the H.323 software adds support to allow a gatekeeper to provide additional destination information and modify the destinationInfo field in the ACF. The gateway will include the canMapAlias associated destination information in setting up the call to the destination gateway.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5800/sw_conf/ios_122/pul0244x.htm.
Note
Cisco IOS Telephony Service Version 2.0
The Cisco IOS Telephony Service Version 2.0 feature was previously released in Cisco IOS Release 12.2(8)T. In Cisco IOS Release 12.2(11)T, there are minor enhancements to this feature, which is now referred to as Cisco IOS Telephony Service Version 2.01. Refer to the following document for information about the enhancements added to this release:
http://www.cisco.com/univercd/cc/td/doc/product/access/ip_ph/ip_ks/ipkey2.htm.
Cisco VCWare Version Checker
The Cisco VCWare Version Checker feature adds Cisco VCWare version checker warning output at bootup and when you use the show vfc version vcware and show vfc version dspware commands.
This new version checker feature detects possible mismatches between Cisco IOS software and Cisco VCWare and DSPWare. If a software mismatch is found, a compatibility mismatch warning is output at bootup and when the show vfc version commands are used. If no mismatch is found, there is no advisory output. Because the new information is advisory only, there is no action taken whether the software is compatible or incompatible.
This feature applies only to the Cisco AS5300. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t11/ftvdspck.htm
CISCO-BULK-FILE-MIB Enhancements
The Cisco Bulk File Creation MIB (CISCO-BULK-FILE-MIB.my) is a MIB module for creating and deleting bulk files of SNMP data for file transfer. The CISCO-BULK-FILE-MIB Enhancements feature enhances the Cisco Bulk File Creation MIB to support selective-row-transfer and notification-on-file-creation. Prior to this enhancement, when the MIB was used to dump large tables (for example, the ccHistoryTable), much of the data transfer consisted of duplicated data. This feature allows the SNMP manager to specify a starting row in the SNMP Get request.
This feature also introduces a notification that can be sent when file creation is complete or when there is an error during file creation. Specifically, this feature modifies the CISCO-BULK-FILE-MIB by introducing four new MIB objects (cbfDefineFileNotifyOnCompletion, cbfDefineObjectTableInstance, cbfDefineObjectNumEntries, cbfDefineObjectLastPolledInst) and a new notification object (cbfDefineFileCompletion). For details, refer to the CISCO-BULK-FILE-MIB.my file, available through Cisco.com MIB FTP site.
Note
CISCO-SIP-UA-MIB Enhancements Providing Functional Parity to SIP related CLI
The CISCO-SIP-UA-MIB Enhancements Providing Functional Parity to session initiation protocol (SIP) related CLI feature has Simple Network Management Protocol (SNMP)/command-line interface (CLI) MIB enhancements to maintain parity with SIP features released to date.
No documentation work is required. The MIB is "self-documenting."
CNS Agents SSL Security
CNS Agents SSL Security is a Cisco IOS software feature that allows for the configuration of a secure connection between the CNS Agent, running on the Cisco IOS software-based device, and a CNS Server. Secure Socket Layer (SSL) encryption for CNS connections is enabled on the Cisco IOS device (CNS Agent) side using the encrypt keyword with the cns config initial or cns config partial global configuration mode commands.
Note
CNS Configuration Agent
CNS is a foundation technology for linking users to network services. CNS SDK accomplishes this by making applications network-aware and increasing the intelligence of the network elements. CNS SDK provides building blocks to a range of customers in market segments such as Enterprise, service provider, independent software vendors, and system integrators.
The CNS Configuration Agent supports routing devices by providing:
•
•
•
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ftcns_ca.htm.
Note
CNS Event Agent
CNS is a foundation technology for linking users to network services. CNS SDK accomplishes this by making applications network-aware and increasing the intelligence of the network elements. CNS SDK provides building blocks to a range of customers in market segments such as Enterprise, service provider, independent software vendors, and system integrators.
The CNS Event Agent is part of the Cisco IOS infrastructure that allows Cisco IOS applications, for example CNS Configuration Agent, to publish and subscribe to events on a CNS Event Bus. CNS Event Agent works in conjunction with CNS Configuration Agent.
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ftcns_ea.htm.
Note
Configuring a Gatekeeper to Provide Nonavailability Information for Terminating Endpoints
An H.323 Location Request (LRQ) message is sent by a gatekeeper to another gatekeeper to request a terminating endpoint. The second gatekeeper determines the appropriate endpoint on the basis of the information contained in the LRQ message. However, sometimes all the terminating endpoints are busy servicing other calls and none are available. If you configure the lrq reject-resource-low command, the second gatekeeper will reject the LRQ request if no terminating endpoints are available. If the command is not configured, the second gatekeeper will allocate and return a terminating endpoint address to the sending gatekeeper even if all the terminating endpoints are busy.
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t11/ft_lrqrj.htm.
Connect-Info RADIUS Attribute 77
The Connect-Info RADIUS Attribute 77 feature enables the network access server (NAS) to report Connect-Info (attribute 77) in accounting "start" and "stop" records that are sent to the RADIUS client. The "start" and "stop" records allow you to compare transmit and receive speeds and have a realistic view of a user session. Comparing transmit and receive speeds is important because many modem speeds are often different at the end of the modem connection (after negotiation).
Refer to the following document for further information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t11/ftattr77.htm.
Customer Profile Idle Timer Enhancements for Interesting Traffic
The Customer Profile Idle Timer Enhancements for Interesting Traffic feature supports a PPP idle timer based on interesting traffic for dialer interfaces.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t11/ftprfidl.htm.
Note
Default VPDN Group Template
The Default VPDN Group Template feature introduces the ability to configure global default values for virtual private dialup network (VPDN) parameters in a VPDN template. These global default values are applied to all VPDN groups, unless specific values are configured for individual VPDN groups. Previously, the Cisco IOS software required that VPDN parameters be configured for each individual VPDN group if the system default values were not desired.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/ftdevpdn.htm.
Note
DF Bit Override Functionality with IPSec Tunnels
The DF Bit Override Functionality with IPSec Tunnels feature allows customers to configure the setting of the DF bit when encapsulating tunnel mode IPSec traffic on a global or per-interface level. Thus, if the DF bit is set to clear, routers can fragment packets regardless of the original DF bit setting. Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ftdfipsc.htm.
Note
DHCP Client—Dynamic Subnet Allocation API
The DHCP Client-Dynamic Subnet Allocation API feature is an application program interface (API) that is called by the DHCP Server-On-Demand Address Pool Manager feature for obtaining a subnet or releasing a subnet to the source server via DHCP. This feature allows automated configuration of layer 3 devices for simplified deployment.
Note
DHCP Client on WAN Interfaces
The DHCP Client on WAN Interfaces feature extends the Dynamic Host Configuration Protocol (DHCP) to allow PPP over ATM (PPPoA) and certain ATM interfaces to acquire an IP address through DHCP. By using DHCP rather than the IP Control Protocol (IPCP), a DHCP client can acquire other useful information such as DNS server addresses, the DNS default domain name, and default route.
Previously, the ip address dhcp interface configuration command could only be used on Ethernet interfaces. This feature allows the ip address dhcp command to be used on WAN interfaces.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/ftwandhp.htm.
Note
DHCP Relay—MPLS VPN Support
The DHCP relay agent information option (option 82) enables a Dynamic Host Configuration Protocol (DHCP) relay agent to include information about itself when forwarding client-originated DHCP packets to a DHCP server. The DHCP server can use this information to implement IP address or other parameter-assignment policies. The DHCP relay agent information option is organized as a single DHCP option that contains one or more suboptions that convey information known by the relay agent.
In some environments, a relay agent resides in a network element that also has access to one or more Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs). A DHCP server that wants to offer service to DHCP clients on those different VPNs needs to know the VPN in which each client resides. The network element that contains the relay agent typically knows about the VPN association of the DHCP client and includes this information in the relay agent information option.
The DHCP Relay-MPLS VPN Support feature allows the relay agent to forward this necessary VPN-related information to the DHCP server using the following three suboptions of the DHCP relay agent information option:
•
•
•
The DHCP Relay-MPLS VPN Support feature enables a network administrator to conserve address space by allowing overlapping addresses. The relay agent can now support multiple clients on different VPNs, and many of these clients from different VPNs can share the same IP address.
Refer to the following document for additional information:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/ftdhmpls.htm.
Note
DHCP Relay Agent Support for Unnumbered Interfaces
Relay agents are used to forward requests and replies between clients and servers when they are not on the same physical subnet. Relay agent forwarding is distinct from the normal forwarding of an IP router, where IP datagrams are switched between networks somewhat transparently. Relay Agents receive Dynamic Host Configuration Protocol (DHCP) messages and then generate a new DHCP message to send out on another interface.
The Cisco IOS DHCP relay agent supports IP unnumbered interfaces. The DHCP relay agent automatically adds a static host route specifying the unnumbered interface as the outbound interface.
DHCP Server—On-Demand Address Pool Manager
The DHCP Server-On-Demand Address Pool Manager is a feature in which pools of IP addresses can be dynamically increased or reduced in size depending on the address utilization level. This feature supports address assignment using the Dynamic Host Configuration Protocol (DHCP) for customers using private addresses. Each on-demand address pool (ODAP) is configured and associated with a particular Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN).
When configured, the ODAP is populated with one or more subnets leased from a source server and is ready to serve address requests from DHCP clients or from PPP sessions. The source server can be a remote DHCP server or a RADIUS server (via AAA). Currently, only the Cisco Access Registrar RADIUS server supports ODAPs. Subnets can be added to the pool when a certain utilization level (high utilization mark) is achieved. When the utilization level falls below a certain level (low utilization mark), a subnet can be returned to the server from which it was originally leased.
This feature allows customers to optimize their use of IP addresses, thus conserving address space.
Refer to the following document for additional information:
Guest
