Etx10 BK

Cisco Broadband Local Integrated Services
Solution-ETTX 1.0 Overview and Planning

Guide
December 2002
Corporate Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 526-4100
Text Part Number: OL-3348-01

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public
domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
CCIP, the Cisco Arrow logo, the Cisco Powered Network mark, the Cisco Systems Verified logo, Cisco Unity, Follow Me Browsing, FormShare, Internet Quotient, iQ
Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, Networking Academy, ScriptShare, SMARTnet, TransPath, and Voice LAN are trademarks
of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That’s Possible, The Fastest Way to Increase Your Internet Quotient, and iQuick Study are
service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS,
the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel,
EtherSwitch, Fast Step, GigaStack, IOS, IP/TV, LightStream, MGX, MICA, the Networkers logo, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX,
Registrar, SlideCast, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other
countries.
All other trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship
between Cisco and any other company. (0206R)
Cisco Broadband Local Integrated Services Solution-ETTX 1.0 Overview and Planning Guide
Copyright © 2002, Cisco Systems, Inc.
All rights reserved.
C ON T E N T S
Preface vii
Document Objectives vii
Audience vii
Scope vii
Document Organization vii
Document Conventions viii
Obtaining Documentation ix
World Wide Web ix
Documentation CD-ROM ix
Ordering Documentation ix
Documentation Feedback x
Obtaining Technical Assistance x
Cisco.com x
Technical Assistance Center xi
CHAPTER 1 Introduction 1-1
How the Solution Works 1-1
CHAPTER 2 Solution Components 2-1
Solution Component Summary 2-1

The Call Agent: Cisco BTS 10200 Softswitch 2-3
Cisco BTS 10200 Softswitch Call Agent 2-4
Cisco BTS 10200 Softswitch Feature Server 2-6
Cisco BTS 10200 Softswitch Element Management Systems 2-6
Cisco BTS 10200 Softswitch Bulk Data Management System 2-6
Customer Premises Equipment 2-7
Cisco ATA 186 and ATA 188 Analog Telephone Adaptors 2-7
Cisco IAD 2421 Integrated Access Device 2-9
Cisco 2611XM or Cisco 2621XM Router 2-9
Ethernet/IP Infrastructure 2-11
Access Layer Switch 2-11
Media Servers 2-11
Cognitronics CX500 (Third Party) Announcement Server 2-11
Voice-mail Servers 2-12
OL-3348-01 iii
Contents
H.323 Gatekeepers 2-12
PSTN Interface 2-13

Trunking Gateway 2-13
Cisco PGW 2200 Signaling Controller (Optional) 2-14
CHAPTER 3 CPE Deployment Options 3-1
Option 1: Voice Only, Cisco ATA 186 or Cisco IAD 2421 3-1
Option 2: Voice and Data, Small-Scale Residential or SOHO Users, Cisco ATA 188 3-2
Option 3: Voice and Data, Larger-Scale Residential or SOHO Users, Cisco IAD 2421 3-3
Wiring Plan When Using the Cisco IAD 2421 with Voice and Data Customers 3-4
Option 4: Voice and Data, Small Business, Cisco IAD 2421 3-7
Option 5: Voice and Data, Small Business with PBX or KTS, Cisco 26x1XM 3-8
Design of the VLAN 3-8
CHAPTER 4 Solution Features 4-1
H.323 Features Supported by the Cisco BTS 10200 Softswitch 4-1

Fast Connect 4-1
H.323 Tandeming 4-2
Tech Prefix-Based Routing 4-2
RAS Signaling 4-2
H.225.0 Signaling 4-3
H.245 Signaling 4-3
DTMF Relay 4-3
Supplementary Services 4-3
Bearer Features 4-4

Codec Support 4-4
Call Progress Tones 4-5
Fax Pass-Through 4-6
Announcement Server Features 4-6
Voice-Mail Features 4-7

SIP Support 4-8
Codec Support 4-8
DTMF Relay Support 4-8
Data Features 4-8
Voice VLAN Support on the Cisco ATA 188 4-9
Packet Marking and Port-Based Queuing on the Cisco ATA 188 4-9
iv OL-3348-01
Contents
CHAPTER 5 Redundancy and Fault Tolerance 5-1
Redundant Deployment of the Cisco BTS 10200 Softswitch 5-1
Service Provider POP Redundant Network Design 5-2
CHAPTER 6 Sample Network and Configurations 6-1
Cisco BTS 10200 Softswitch Sample Configuration 6-2
CPE Sample Configurations 6-15

Cisco ATA 18x Sample Configuration 6-15
Cisco IAD 2421 Sample Configuration 6-17
Cisco 26x1XM Router Sample Configuration 6-21
Announcement Server Sample Configuration 6-23
Gatekeeper Sample Configurations 6-25

Cisco 2601 Router Sample Configuration (Local Voice Network) 6-25
Cisco 2601 Router Sample Configuration (H.323 Network) 6-26
Cisco 2602 Router Sample Configuration (H.323 Network) 6-27
Trunking Gateway Sample Configuration 6-28
CHAPTER 7 Design Limitations 7-1
Feature Limitations 7-1
Subscriber Features Requiring ANI 7-2
NAT/PAT Translation 7-2
Firewalls 7-2
Failover Limitations 7-2
CHAPTER 8 Solution Network Management 8-1
Fault Management 8-1
Configuration and Provisioning 8-2
Accounting 8-4
APPENDIX A Glossary A-1
OL-3348-01 v
Contents
vi OL-3348-01
Preface
Document Objectives
This guide provides the information you need to understand the Cisco Broadband Local Integrated
Services Solution-ETTX and begin planning your solution implementation. It also contains reference
information that might be needed by administrators, service technicians, and users.
Audience
This document is designed for service provider staff responsible for planning, implementing, and
operating the solution.
Scope
This document focuses on the end-to-end Cisco Broadband Local Integrated Services Solution-ETTX as
a whole. In-depth information about solution components is beyond the scope of this document.
References to component documentation are provided.
Document Organization
This document contains the following chapters listed in Table 1:
Table 1 Document Contents
Chapters Title Content

Chapter 1 Introduction An overview of the solution, including a simple
description of how it works and the two main
implementation options
Chapter 2 Solution Components A descriptive list of solution components with
links to component documentation
Chapter 3 CPE Deployment Options An explanation of your choices in customer
premises equipment (CPE), based on the services
you want to provide
OL-3348-01 vii
Preface
Document Conventions
Table 1 Document Contents (continued)
Chapters Title Content

Chapter 4 Solution Features Details on the features supported by the solution
Chapter 5 Redundancy and Fault Tolerance Information about the fault tolerance of solution
components and an example of a redundant
network design
Chapter 6 Sample Network and An example of a Cisco Broadband Local
Configurations Integrated Services Solution-ETTX
implementation, with sample configurations for
its components
Chapter 7 Solution Network Management Descriptions of the network management
components that may be used with the solution
Chapter 8 Design Limitations Details about design limitations for the solution.
Appendix A Glossary Definitions of acronyms used in this guide
Document Conventions
Command descriptions use the following conventions:
boldface font Commands and keywords are in boldface.

italic font Arguments for which you supply values are in italics.
[ ] Elements in square brackets are optional.
{x|y|z} Alternative keywords are grouped in braces and separated by vertical bars.
[x|y|z] Optional alternative keywords are grouped in brackets and separated by vertical
bars.
string A nonquoted set of characters. Do not use quotation marks around the string or
the string will include the quotation marks.
Screen examples use the following conventions:
screen font Terminal sessions and information the system displays are in screen font.
boldface screen font Information you enter is in boldface screen font.
italic screen font Arguments for which you supply values are in italic screen font.
Highlights an important line of text in an example.
^ Represents the key labeled Control or Ctrl. For example, the key
combination ^D in a screen display means hold down the Control key while
you press the D key.
< > Nonprinting characters, such as passwords, are in angle brackets.
[ ] Default responses to system prompts are in square brackets.
!, # An exclamation point (!) or a pound sign (#) at the beginning of a line of code
indicates a comment line.
viii OL-3348-01
Preface
Obtaining Documentation
Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the
publication.
Timesaver Means the described action saves time. You can save time by performing the action described in the
paragraph.
Tip Means the following information might help you solve a problem. The tips information might not be
troubleshooting or even an action, but could be useful information, similar to a Timesaver.
Caution Means reader be careful. In this situation, you might do something that could result in equipment
damage or loss of data.
Obtaining Documentation
These sections explain how to obtain documentation from Cisco Systems.
World Wide Web

You can access the most current Cisco documentation on the World Wide Web at this URL:
Translated documentation is available at this URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM
package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may
be more current than printed documentation. The CD-ROM package is available as a single unit or
through an annual subscription.
Ordering Documentation
You can order Cisco documentation in these ways:
• Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from
the Networking Products MarketPlace:
http://www.cisco.com/cgi-bin/order/order_root.pl
• Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription
Store:
OL-3348-01 ix
Preface
Obtaining Technical Assistance
http://www.cisco.com/go/subscription
• Nonregistered Cisco.com users can order documentation through a local account representative by
calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere
in North America, by calling 800 553-NETS (6387).
Documentation Feedback
You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click
the Fax or Email option in the “Leave Feedback” section at the bottom of the page.
You can e-mail your comments to bug-doc@cisco.com.
You can submit your comments by mail by using the response card behind the front cover of your
document or by writing to the following address:
Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can
obtain online documentation, troubleshooting tips, and sample configurations from online tools by using
the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access
to the technical support resources on the Cisco TAC Web Site.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open
access to Cisco information, networking solutions, services, programs, and resources at any time, from
anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a
broad range of features and services to help you with these tasks:
• Streamline business processes and improve productivity
• Resolve technical issues with online support
• Download and test software packages
• Order Cisco learning materials and merchandise
• Register for online skill assessment, training, and certification programs
If you want to obtain customized information and service, you can self-register on Cisco.com. To access
Cisco.com, go to this URL:
x OL-3348-01
Preface
Technical Assistance Center

The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance
with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC
Web Site and the Cisco TAC Escalation Center.
Cisco TAC inquiries are categorized according to the urgency of the issue:
• Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities,
product installation, or basic product configuration.
• Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably
impaired, but most business operations continue.
• Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects
of business operations. No workaround is available.
• Priority level 1 (P1)—Your production network is down, and a critical impact to business operations
will occur if service is not restored quickly. No workaround is available.
The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of
service contracts, when applicable.
Cisco TAC Web Site

You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time.
The site provides around-the-clock access to online tools, knowledge bases, and software. To access the
Cisco TAC Web Site, go to this URL:
http://www.cisco.com/tac
All customers, partners, and resellers who have a valid Cisco service contract have complete access to
the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a
Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or
password, go to this URL to register:
http://www.cisco.com/register/
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco
TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC
Web Site.
Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These
classifications are assigned when severe network degradation significantly impacts business operations.
When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer
automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
OL-3348-01 xi
Preface
Before calling, please check with your network operations center to determine the level of Cisco support
services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network
Supported Accounts (NSA). When you call the center, please have available your service agreement
number and your product serial number.
xii OL-3348-01
C H A P T E R 1
Introduction
Cisco Broadband Local Integrated Services Solution–ETTX 1.0 is a Cisco Ethernet-to-home or business
solution to offer integrated local voice and data services for residential units and small- to medium-sized
businesses in multiple dwelling unit (MDU) and multiple tenant unit (MTU) environments in the
Asia-Pacific market.
Key features of the solution include:
• Supplementary services to line subscribers (residential or small business)
• PBX or key telephone service (KTS) interconnect for business customers
• Local public switched telephone network (PSTN) termination and long distance through the H.323
long-distance network
• Announcement and voice-mail servers
• FAX pass-through
• Dual-tone multifrequency (DTMF) relay
• Hong Kong and China dial plans
• Hong Kong and China tone generation
Feature details are described in Chapter 4, “Solution Features.”
How the Solution Works

In this solution, subscriber units are prewired for Ethernet. The phone line (or small PBX or key system)
and optionally the data line in the residential or business-line subscriber’s unit is connected to a media
gateway that may be one of the following:
• An analog telephone adaptor (ATA), a Cisco ATA 186 (for voice only) or Cisco ATA 188 (for voice
and data)
• An integrated access device, such as a Cisco IAD 2421
• A Cisco 2611XM or 2621XM router, for connection to a PBX or key system and optionally the
customer’s LAN
A standard RJ-11 connector coming in from the telephone, PBX, or key system connects into the media
gateway Foreign Exchange Station (FXS) port. All supported media gateways provide at least two FXS
ports. The Cisco ATA 188 and the Cisco 2611XM or 2621XM router also provide a data port.
In turn, the media gateways connect out through an Ethernet port to a Fast Ethernet switch, such as the
Cisco Catalyst 2950, typically located in the building basement.
OL-3348-01 1-1
Chapter 1 Introduction
The Fast Ethernet switch connects to an Ethernet and IP infrastructure that supports a local Voice over
IP (VoIP) network. This infrastructure provides the connection between the end subscribers and the
service provider’s point-of-presence (POP) local VoIP network.
In this local VoIP network, the Cisco BTS 10200 Softswitch is the call agent. The call agent provides
MGCP-based call control and signaling support, subscriber features, and interfaces to network resources
such as announcement servers and voice-mail servers.
For calls to H.323 long distance or the PSTN (we will refer to these calls outside the local network as
off-net calls), the Cisco BTS 10200 Softswitch uses H.323 signaling. A service provider with an existing
H.323 infrastructure can leverage that network to provide long-distance VoIP services to their MGCP
subscribers.
The solution architecture comprises these layers:
• The residential or small-business access layer, containing the customer premises equipment (CPE)
and uplink technology.
• The call control layer, which provides call control and signaling support, feature server interfaces,
and support for network resource interfaces such as announcement servers and voice-mail servers.
• The aggregation and core switching layer, which provides traffic aggregation from all CPE uplinks
and interfaces to the packet network backbone.
• The H.323 based call control layer, which provides call control signaling for the H.323
long-distance network. This layer also includes trunking gateways and their associated signaling for
the PSTN interface.
• The network management layer, which provides the element management systems (EMSs) and
network management system (NMS) components.
Note The solution scope, and the scope of solution documentation, includes access transport, but does not
extend to core transport, which is assumed to be in place.
Two variations of the solution are illustrated:

• In Figure 1-1, the service provider leverages an existing H.323 network to provide long distance
services and PSTN access. Because the local voice network infrastructure supports both MGCP and
H.323 gateways, the H.323 network can be directly connected. There are two H.323 networks.
• In Figure 1-2, the service provider builds the network from the ground up. The service provider
H.323 network integrates PSTN access.
1-2 OL-3348-01
Figure 1-1 Solution with Direct Connect to the H.323 Long-Distance Network
Cisco ATA18x
Internet Cisco
V BTS 10200
Softswitch Cisco PGW 2200
Data
82753
router GK
Cisco Catalyst 2950/3500XL GK GK
Cisco H.323 Cisco SLT

IAD2421 Local Voice Transit
8/16 FXS Network Network
IAD Q.931+/IP F-link

AS5xx0 V
IMT
V
Cisco Catalyst 2950/3500XL Voice mail
server AS5xx0
Announcement R2/PRI PSTN
PBX or KTS server
V Cisco
26x1 XM
router TDM TDM
switch switch
FXS
OL-3348-01 1-3
Figure 1-2 Solution Connecting Indirectly to PSTN
Cisco ATA18x
Cisco
Internet BTS 10200
V Softswitch
H.323 GK
Data
router GK
Cisco SLT
Cisco Catalyst 2950/3500XL
Cisco PGW 2200
Cisco
IAD2421 Local Voice
Q.931+/IP F-link
8/16 FXS Network
IMT
IAD VV
PRI/R2
Cisco Catalyst 2950/3500XL Voice mail
server
Announcement
PBX or KTS server
Cisco PSTN network
V
82752
26x1 XM
router
FXS
1-4 OL-3348-01
C H A P T E R 2
Solution Components
This chapter includes a summary chart of the Cisco Broadband Local Integrated Services
Solution-ETTX components followed by descriptions and references for each component.
Solution Component Summary

Table 2-1 summarizes the components that comprise the solution, including the required software
release and the hardware platform, if different from the component itself.
Table 2-1 Solution Components
Type of Component Function Supported Component Hardware Platform

Call Agent Control media gateways and provide Cisco BTS 10200 Softswitch Sun Netra 140x
them supplementary services with
MGCP
CPE Devices
Media gateway Voice access and (Cisco ATA 188) Cisco ATA 188/186 Cisco ATA 18x
data access 186: CPE with 2 FXS analog1
Location: Subscriber unit voice ports and 1 Ethernet uplink

port (voice only)
188: CPE with 2 FXS voice ports,
1 Ethernet uplink port, and 1 data
port
Media gateway Voice access for residential and small Cisco IAD 2421 Cisco IAD 2421
business customers Integrated access device for Class
Location: Wiring closet on building 5 Switch Bypass with an Ethernet
floor or, where a large number of port uplink and 16 voice ports.
POTS lines are required, in
subscriber unit
Note T1 WAN port is not used in
this solution.
OL-3348-01 2-1
Chapter 2 Solution Components
Solution Component Summary
Table 2-1 Solution Components (continued)

Media gateway Voice and data access for business Cisco 2611XM or 2621XM router Cisco 2611XM,
customers with PBX or key systems Multipurpose router and VoIP 2621XM
Location: Wiring closet gateway. Provides FXS interfaces
(up to 4) to a small PBX or key
systems. Supports 2 Ethernet or
Fast Ethernet links (one uplink,
one data port). ISDN, R2, or T1
links are not supported.
EPOM Network management Cisco BTS 10200 Softswitch GUI. Sun Netra 140x
BAC Used for provisioning and Cisco 2421, Cisco 2600. Sun Netra 140x, 1125
configuring CPE and aggregation
devices
CIC Fault management functionality Cisco IAD 2421, Cisco 2611XM or • A Sun Ultra 10 for
2621XM router, Cisco 7200, and the Information
Cisco BTS 10200 Softswitch. Server.
• An UltraSPARC II
for the Information
Mediator
• A Sun workstation
for the Information
Administration
Desk
All platforms run on
Solaris 2.7
C-NOTE Fault management functionality Cisco IAD 2421, Cisco 2611XM or A standard Sun Netra 20
2621XM router, Cisco 7200, and platform which runs on
Cisco BTS 10200 Softswitch. Solaris 2.7 or higher OS
CNR Network management — Sun Netra 140x, 1125
PSTN Interconnect Components

Announcement server Handle announcements Cognitronics CX500. UltraSPARC
Announcement server Handle announcements Cisco AS5300 Announcement Cisco AS5300
Server or Cisco AS5350 Announcement Server
Announcement Server. or Cisco AS5350
Announcement Server.
Voice-mail server Handle voice mail IP Unity Harmony 6000 server. Sun workstation
H.323 Gatekeepers
Gatekeeper — Cisco 7200 router (recommended), —
Cisco 3660 router.
2-2 OL-3348-01
The Call Agent: Cisco BTS 10200 Softswitch
Table 2-1 Solution Components (continued)

H.323 interconnect Interconnection to a long-distance — —
voice network.
This may require firewall or
NAT/PAT functions
Cisco IOS NAT/PAT — Cisco 7200 with NSE. Cisco 7200 with
device NPE-400
Other Components
Ethernet/IP Connect the building with the service Customer-specific.
Infrastructure provider POP. Requirement: Example: —
Guarantee end-to-end quality of
service (QoS) Subscriber side aggregation: Cisco
Catalyst 2950 or Cisco 3550
switch.
POP side: Cisco 6500 switch.
Related Components (not part of the solution)
This version of Cisco Broadband Local Integrated Services Solution–ETTX 1.0 has SS7 Interconnect Gateways. For more
information, refer to
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/soln/voip20/index.htm.
H.323 Gateways
H.323 Gateway Cisco AS5350 Cisco AS5350
1. Foreign exchange station (telephone line)

As the solution's call agent, the Cisco BTS 10200 Softswitch provides the central intelligence and call
control for the network. It establishes and tears down telephony calls, provides the service logic required
to deliver services, manages dialing plans, and provides the appropriate interfaces to the operational
support systems.
A Cisco BTS 10200 Softswitch comprises four main components:
• The call agent
• The feature server
• The element management system (EMS)
• The bulk data management system (BDMS)
Physically, the components reside on four Sun Netra servers running Solaris 8, in the following
configuration:
• One server for the active call agent and feature server and one server for the backup call agent and
feature server
OL-3348-01 2-3
• One server for the active EMS and one server for the backup EMS
These are described in more detail in the following sections, as are the Cisco BTS 10200 Softswitch
Release 3.2 Local Subscriber Features.
Note The Cisco BTS 10200 Softswitch documentation is password-protected. To access the documentation,
contact your Cisco representative.
Once you have the correct username and password, you can access the Cisco BTS 10200 Softswitch
documentation at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/bts10200/bts3_2/index.htm.
For more information on the Cisco BTS 10200 Softswitch Release 3.2 Local Subscriber Features, refer
to the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/bts10200/bts3_2/btschina.htm.
Cisco BTS 10200 Softswitch Call Agent

The call agent server is responsible for the call management system and the media gateway controller.
It handles establishment, processing, and teardown of telephony calls. Figure 2-1 shows a functional
overview of the Cisco BTS 10200 Softswitch.
Figure 2-1 Functional Overview of Cisco BTS Softswitch
Physical office environment

sco BTS 10200 Softswitch H.323 to gatekeeper (Power/ground
feature server and H.323 endpoints dry alarm contacts)
Element Manager SIP-T

SNMP, TCP, UMS BTS 10200 call agent (not used in this solution)
network management SIP to voice mail server
MGCP 1.0
82740
Media gateways
The Cisco BTS 10200 Softswitch is deployed in a fully redundant primary and secondary configuration
where the secondary call agent takes over when the primary call agent fails. The Cisco BTS 10200
Softswitch is designed for high availability, with no single point of failure.
A single call agent consists of an active and standby half, located on the Sun UNIX platform. Call-state
information is copied from the active to the standby call agent, which ensures that no established calls
are lost in a switchover from active to standby mode. (H.323 calls are an exception, because of their TCP
nature.) The active Cisco BTS 10200 Softswitch processes all calls.
2-4 OL-3348-01
Each access device performs DNS lookup to locate the IP address of both the primary Cisco BTS 10200
Softswitch and the standby; default DNS lookup points to the active Cisco BTS 10200 Softswitch.
During normal conditions, all access devices communicate with the active BTS. If the active Cisco BTS
10200 Softswitch fails, the standby becomes active.
The active and standby call agents exchange periodic keepalive timers called KAM/RDM to detect any
failure scenarios. If a failure scenario is detected, the standby call agent takes over and becomes active.
Other Cisco BTS 10200 Softswitch elements, feature servers, and EMS are also deployed in
active/standby configurations, with real-time synchronization of data between the active and the standby
elements.
Note No traffic load sharing between the active and the standby call agents is done. The active Cisco BTS
10200 Softswitch performs all call processing and the standby is idle.
Voice over IP Signaling Protocols

Three types of voice signaling or control protocols are used in this solution: Media Gateway Control
Protocol (MGCP), H.323, and Session Initiation Protocol (SIP). The Voice over IP (VoIP) protocols used
by various solution components are as follows:
• MGCP is used in the Cisco BTS 10200 Softswitch, the media gateways (the Cisco ATA 18x,
Cisco IAD 2421, Cisco 2611XM and Cisco 2621XM routers), and the announcement servers.
• H.323 is used in the Cisco BTS 10200 Softswitch, the H.323 Gateway, the H.323 Gatekeeper, and
the NAT device.
• SIP is used for communication (over IP) between the Cisco BTS 10200 Softswitch and the
voice-mail server.
MGCP Support
The solution uses Media Gateway Control Protocol (MGCP) 1.0 to communicate between the
Cisco BTS 10200 Softswitch and the media gateways, such as the Cisco ATA 18x, Cisco IAD 2421, and
analog Cisco 2611XM or Cisco 2621XM routers. The Cisco BTS 10200 Softswitch is responsible for
providing interworking between these MGCP CPEs and H.323 gateways for PSTN hop-off (MGCP to
and from H.323) and between MGCP CPEs and the IP Unity voice-mail server (MGCP-SIP) for access
to voice mail recording and retrieval.
SIP Support
The solution uses Session Initiation Protocol (SIP) to communicate between the Cisco BTS 10200
Softswitch and the voice-mail server. The Cisco BTS 10200 Softswitch is responsible for providing SIP
interworking with MGCP CPEs (SIP-MGCP) and H.323 gateways (SIP-H.323) to provide access to
voice mail recording and retrieval.
The SIP protocol is defined in RFC 2543.
H.323 Support
H.323 Signaling support on the Cisco BTS 10200 Softswitch is based on H.323 protocol stack ported
from Cisco IOS gateways. To the H.323 network, the Cisco BTS 10200 Softswitch looks like a gateway
controlled by an H.323 gatekeeper. The Cisco BTS 10200 Softswitch H.323 stack is designed to allow
OL-3348-01 2-5
the creation of up to four separate H.323 gateway interfaces. Each interface has the ability to register
with different gatekeepers or the same one. This architecture allows for the ability to load balance
between the H.323 gateways to provide better scalability and resiliency.
Cisco BTS 10200 Softswitch Feature Server

The feature server component provides features support for the call agent’s controlled calls through
well-defined interfaces. The Feature Control Protocol (FCP) is used between feature servers, which
provide feature control, and the call agent, which provides call control. This independent architecture
allows the Cisco BTS 10200 Softswitch to support multiple features such as POTS, AIN, Centrex and
800 services from multiple feature servers. These feature servers can be implemented either internally
on the same machine or externally on a separate machine. FCP ensures the proper communication
through its well-defined interfaces between the call agent and feature servers.
In this solution, only internal feature servers physically residing within the Cisco BTS 10200 Softswitch
are used.
Cisco BTS 10200 Softswitch Element Management Systems

The EMS acts as a mediation device between a Network Management System (NMS) and one or more
call agents. It also provides the interface for the provisioning and administration features to the call agent
and provides a flexible mechanism to transport information over any protocol to any external device. The
EMS manages the Cisco BTS 10200 Softswitch components and provides operation, administration,
maintenance, and provisioning interfaces for monitoring control. The Cisco BTS 10200 Softswitch EMS
design takes into account that each carrier has its own unique set of Operations Support Systems (OSS).
The EMS provides a decoupling layer between the external protocols used within the service provider's
network and the internal protocols of the feature server and call agent. The core Call Agent/Feature
Server system does not need to interpret the specific data formats used by the carrier's other network
elements. Local Operators use a workstation or PC with a command line interface (CLI) or graphical
user interface (GUI) to communicate with the EMS. Sessions can be either interactive (using Telnet) or
batch mode (using FTP).
The EMS supports an XML over Corba interface for full nodal provisioning, and a packetcable
compliant CMS interface over HTTP for subscriber/MTA/services provisioning.
In this solution, the XML over Corba interface is used by Cisco Extensible Provisioning and Operations
Manager (EPOM) for real-time provisioning of the Cisco BTS 10200 Softswitch through EPOM's
web-based interface.
Cisco BTS 10200 Softswitch Bulk Data Management System

The Bulk Data Management System (BDMS) manages the billing functions of the
Cisco BTS 10200 Softswitch. BDMS gathers all billing-related call events from call processing,
formatting them into a standard format, and transmitting them to an external billing collection and
mediation device. The BDMS transmits billing records via FTP to a remote server that is part of the
service provider billing system. The FTP transfer occurs automatically in a pre-configured timer ranging
from 1 to 60 minutes configured by the service provider. The default in the Cisco BTS 10200 Softswitch
is 15 minutes.
2-6 OL-3348-01
Customer Premises Equipment

Customer premises equipment comprises these devices:
• A media gateway—either an analog telephone adaptor, the Cisco ATA 186 or 188, or a Cisco IAD
2421 integrated access device, or, for small businesses with a PBX or key system, the Cisco 2611XM
or 2621XM router
• For aggregation and connection to the Ethernet/IP infrastructure, a Fast Ethernet switch such as the
Cisco Catalyst 2950
Cisco ATA 186 and ATA 188 Analog Telephone Adaptors

The Cisco ATA 186 or Cisco ATA 188 analog telephone adaptor connects a subscriber's analog telephone
to an IP telephony network. In this solution, the Cisco ATA 186 or 188 serves as a CPE media gateway
for the subscriber, and is located in the subscriber's residential unit.
• The Cisco ATA 186 provides two foreign exchange station (FXS) analog voice ports and one
Ethernet uplink port. In this solution, it is suitable for subscribers desiring voice service only.
• The Cisco ATA 188 provides two FXS voice ports, one Ethernet uplink port for direct connection to
a 10/100BASE-T Ethernet network, and one data port. It is appropriate for customers requiring both
voice and data.
For more information on the Cisco ATA 186 analog telephone adaptor, refer to the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/ata/index.htm
Cisco ATA 186 Details

Use the Cisco ATA 186 for customers requiring voice services only.
Cisco ATA 186 Interfaces
• One RJ-45 10BASE-T Ethernet WAN Port

• Two RJ-11 Foreign Exchange Station (FXS) ports
• One Ethernet status LED
• 5V DC power supply
Cisco ATA 186 Voice Features
• Codecs supported: G711A-law (also supports G.711 µ-law and G.723.1 that are not required for
Release 1.0)
• DTMF Relay: DTMF relay is based on either out of band via MGCP or RFC 2833
• Fax support is based on Cisco NSE G.711 pass-through method
• Comfort noise generation (CNG) and voice activity detection (VAD) support
• Cisco ATA 186 Signaling/Control
• MGCP 1.0
• FXS
OL-3348-01 2-7
Cisco ATA 186 QoS Features
• Software-based QoS marking for Layer 3 Type of Service.
Cisco ATA 188 Details

Use the Cisco ATA 188 for customers requiring both voice and data services.
Cisco ATA 188 Interfaces
• Built-in three-port switch

• One RJ-45 10/100BASE-T Ethernet WAN port
• One RJ-45 10/100BASE-T Ethernet data port
• Two RJ-11 Foreign Exchange Station (FXS) ports
• Two Ethernet status LED
• 5V DC power supply
• Low-cost 81 MHz Komodo VoIP processor
• One MB DRAM
Cisco ATA 188 Voice Features
• Codecs supported: G711 A-law (also supports G.711 µ-law and G.723.1 that are not required for
Release 1.0)
• DTMF Relay: DTMF relay is based on either out of band via MGCP or RFC 2833
• Fax support is based on Cisco NSE G.711 pass-through method
• Comfort noise generation (CNG) and voice activity detection (VAD) support
• Cisco ATA 188 Signaling/Control
• MGCP 1.0
• FXS
Cisco ATA 188 QoS Features
• 802.1Q and CDPv2 for voice VLAN

• Software-based QoS marking for Layer 3 Type of Service (ToS) and Layer 2 Class of Service
(802.1p) for voice traffic
• Prioritize voice traffic over data traffic
• Data traffic is forwarded transparently (on the native VLAN if untagged, on the specified VLAN if
tagged). If the PC is sending tagged frames with specific CoS and ToS values, the Cisco ATA 188
does not zero out this value before sending the frames to the switch. The Cisco ATA 188 does not
tag data frames or zero out CoS values but it queues voice as high priority.
2-8 OL-3348-01
Cisco IAD 2421 Integrated Access Device

The Cisco IAD 2421 integrated access device (IAD) is a Class 5 Switch Bypass with 16 analog FXS
(voice) ports. It aggregates multiple channels of data and voice/fax user-side traffic for transport over a
single wide-area network (WAN) uplink. Voice/fax traffic is transported by Voice over IP (VoIP) or by
Voice over ATM (VoATM).
In this solution, the Cisco IAD 2421 serves as a CPE media gateway, providing analog voice interfaces
and a WAN uplink, and is typically located in a wiring closet on each floor or in the building basement.
Although the Cisco IAD 2421 provides voice services only, customers also requiring data services can
connect their LAN directly to the basement LAN switch.
Cisco IAD 2421 Interfaces

• One RJ-45 Ethernet port (straight or cross) which will be used as WAN uplink
• One RJ-45 console port and one auxiliary port
• 8/16 FXS ports with RJ-21 Telco connector
• Serial port and T1 port (not used in this solution)
• Cisco IAD 2421 Voice Features
• Fax/modem pass-through support based Cisco Name Signaling Event (NSE) method
• Codec supported: G711 A-law and G.711 µ-law
• Echo Cancellation, VAD
Cisco IAD 2421 Signaling/Control

• MGCP 1.0
• FXS
Cisco IAD 2421 QoS Features

• IEEE 802.1Q VLAN tagging
• Policy maps for traffic routing
• Class of service (CoS) and type of service (ToS) marking both for signaling and bearer traffic
For more information on the Cisco IAD 2400 series integrated access devices, refer to the following
URL:
http://www.cisco.com/univercd/cc/td/doc/product/access/iad/iad2420/index.htm.
Cisco 2611XM or Cisco 2621XM Router

The Cisco 26x1 router is a multipurpose, modular router and VoIP gateway that provides up to 12 FXS
interfaces to a small PBX or key system. It supports two Ethernet or Fast Ethernet links (one uplink, one
data port). ISDN, R2, or T1 links are not supported.
OL-3348-01 2-9
In this solution, the Cisco 2611XM or 2621XM router serves as the CPE media gateway connecting
small-business PBX or key systems through an analog FXS interface to the local voice network. All
voice supplementary services are locally provided by the PBX or key system and require no involvement
from the router or the BTS.
The Cisco 2611XM or 2621XM router supports all standard router functions, such as DHCP services for
customer's terminal and routing services to the network. The interfaces and features specific to this
solution are described below.
Cisco 26x1 Router Interfaces

• Two RJ-45 Fast Ethernet ports, one dedicated for the WAN uplink and the other for LAN data
• One RJ-45 console port and I auxiliary port
• One two-port FXS voice/fax interface card
• One-slot or two-slot voice/fax network module
• Optionally, a High-Density Analog (HDA) network module with up to 12 FXS ports
Cisco 26x1 Router Voice Features

• Fax/Modem pass-through support based Cisco Name Signaling Event (NSE) method
• Codec supported: G.711 A-law and G.711 µ-law
• Echo Cancellation, VAD
The following configurations are supported for FXS:
• NM-1V + VIC-2FXS = 2 ports
• NM-2V + VIC-2FXS + VIC-2FXS = 4 ports
• NM-HDA-4FXS = 4 ports
• NM-HDA-4FXS + EM-HDA-8FXS = 12 ports
Cisco 26x1 Signaling

• MGCP 1.0
• FXS
Cisco 26x1 QoS Features

• IEEE 802.1p tagging and IEEE 802.1q VLAN tagging
• Policy Maps for traffic routing
• Class of service (CoS) and type of service (ToS) marking both for signaling and bearer traffic
For more information on the Cisco 2600 router series, refer to the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_mod/cis2600/index.htm
2-10 OL-3348-01
Ethernet/IP Infrastructure
Ethernet/IP Infrastructure
The Ethernet/IP infrastructure connects the subscriber, through an access layer switch aggregating CPE
devices, with the VoIP network in the service provider POP (through an aggregating router). Specific
components in this infrastructure depend on your requirements.
Access Layer Switch

At the subscriber location, Regular Ethernet or Fast Ethernet is used to aggregate floors or to connect
directly to basement devices. The primary access layer LAN switch is the Cisco Catalyst 2950 switch.
Note Other switches such as the Cisco 3500 may be used.
The access layer switch provides such functions as:

• DHCP relay
• 802.1q and 802.1p
• CDP for VLAN ID discovery (on the switch to which ATA 188 analog telephone adaptors are
connected
• Traffic classification
• Prioritization at Layer 2
Media Servers
The solution supports an announcement server, the Cognitronics CX500, and a voice-mail server such
as the IP Unity server.
Cognitronics CX500 (Third Party) Announcement Server
Note The Cognitronics CX500 announcement server is a third-party server, and is not sold or supported by
Cisco.
The Cognitronics CX500 announcement server provides the following key features:
• NEBS compliant
• Two rack units high (3.5 x 17 x 12 inch)
• Single power supply
• UltraSPARC single board design running Solaris 2.6
• Supports N+1 redundancy
• Supports vacant code (changed number) announcement
• CLI based user interface for management and provisioning
• Supports MGCP 1.0
OL-3348-01 2-11
H.323 Gatekeepers
• Dynamic announcements
• 200 message function types per vocabulary, 10,000 voice files, and up to 8 vocabularies
The announcements are stored as Wave (.WAV) files. G.711 A law compression is supported.
The CX500 can be located at a SuperPOP or at a remote POP. The MGCP call control interactions are
via MGCP 1.0. The server is connected to the network via a Fast Ethernet connection.
For load sharing and redundancy, two CX500 servers are deployed in load-sharing mode. If one platform
fails, the Cisco BTS 10200 Softswitch uses the other platform.
The announcement server recognizes a primary and secondary BTS call agent. The server gets a list of
BTS call agents from the DNS lookup, and uses the secondary call agent if the primary one goes down.
For more information on the Cognitronics CX500 announcement server, refer to the following URL:
http://www.cognitronics.com/products/cx500.html
Cognitronics vendor information is at http://www.cognitronics.com/.
Voice-mail Servers
The solution includes one or more voice-mail servers, such as an IP Unity server, to provide voice mail
capabilities. The voice-mail servers are located in the service provider POP, with an IP connection to the
Cisco BTS 10200 Softswitch. The number of servers required depends on the number of voice mail
subscribers you expect to serve and the voice mail characteristics they require.
The solution supports the following voice-mail protocols:
• Ethernet interface, used for all signaling and bearer traffic
• SIP, the protocol used (over IP) between the call agent and the voice-mail server to set up and tear
down calls
• Codec support for G.711 for message recording and playout
H.323 Gatekeepers
The H.323 gatekeepers provide registration services and load-balancing functions for the H.323 gateway
endpoints of the Cisco BTS 10200 Softswitch. The gatekeeper handles call processing requests from
H.323 gateways by identifying and routing the call to the appropriate destination. The gatekeeper is
scalable to handle registration services for up to 1000 gateways and is capable of handling up to 50 calls
per second.
Before an H.323 gateway on the Cisco BTS 10200 Softswitch can originate or terminate calls through
an H.323 gatekeeper, it must first discover and register with a gatekeeper. When an H.323 gateway
wishes to discover H.323 gatekeepers in the network, a GRQ message is sent out over the IP network. If
a gatekeeper receives a GRQ, it replies with a GCF for a confirmation or a GRJ for a rejection to the
GRQ. The H.323 gateway chooses the gatekeeper with the highest priority, H323_GW2GK.PRIORITY,
as its primary gatekeeper and the others (can have up to two total configured) will be designated as
alternates. If the gatekeeper sends back a list of alternate gatekeepers, these will be added to the list. This
allows for dynamic introduction and configuration of primary and alternate gatekeepers in the network
that H.323 gateways can communicate with.
Alternatively, the H.323 gateway can be statically configured with the IP addresses of the secondary or
alternate gatekeepers it can communicate with. Gatekeeper discovery can be accomplished either
through multicast or unicast mode. In multicast mode, the GRQ message from the H.323 gateway is
2-12 OL-3348-01
PSTN Interface
multicast out on the well-known transport address (addr: 224.0.1.41 port: 1718) and the gatekeeper ID
is not specified, then any gatekeeper may respond to the request with a GCF if all the authorization and
admission checks pass. In unicast mode, the gatekeeper ID, address and port number will be specified in
the GRO message.
Once the H.323 gateway discovers the gatekeeper, it needs to register with it and uses an RRQ message
to request permission to register with a gatekeeper. The gatekeeper in turn will respond with an RCF for
confirmation of the registration request or it will send back an RRJ for a rejection. There are two flavors
of RRQ messages, heavyweight and lightweight. Heavyweight registration will be used on the initial
registration with the gatekeeper. Lightweight registration is used to report to the gatekeeper so that the
gatekeeper will not deregister the endpoint. In this solution, all the Cisco BTS 10200 Softswitch gateway
interfaces register to dedicated gatekeepers to ensure proper scalability and capacity.
For most implementations, we recommend using a cluster of gatekeepers. For small deployments, two
gatekeepers can be used, a primary and an alternate. The alternate can be statically configured on the
gateway. During the gateway's full registration with the primary gatekeeper, a Time-to-Live (TTL) timer
value (default is 60 seconds) is returned to the gateways. The gateways use the TTL minus 15 seconds
as the lightweight registration interval. If the gatekeeper does not respond to the gateway's lightweight
registration during this interval, the gateway will retry three times. If there is still no response, the
gateway will register to the alternate gatekeeper.
To enhance system availability, the gatekeeper can optimally be configured to use the Sequential Unicast
LRQ feature. With Sequential LRQs, each LRQ is sent staggered by a user-defined time interval between
0.1 to 1 second. The first LRQ is given a chance to succeed. If the gatekeeper receives an LRJ or the
defined timer interval expires, the second LRQ is sent.
In this solution, the recommended gatekeeper is the Cisco 7200 router running the gatekeeper image.
The Cisco 2611 router or, in small deployments, the Cisco 3660 router, may also be used.
PSTN Interface
Connection to the public switched telephone network (PSTN) is through an H.323 trunking gateway that
may be part of your network or part of another vendor's network (the Wholesale VoIP provider).
Trunking Gateway
The H.323 trunking gateway is an optional component used as an interface to the PSTN at the signaling
level, through SS7 ISUP, ISDN PRI or R2, and at the bearer level, by converting IP packets into TDM
digital signals.
The H.323 gateway registers with a gatekeeper. The gateways may be part of the network or they may
be part of another vendor network under a wholesale relationship. H.323 gateways are part of the Cisco
Voice Infrastructure and Applications (VIA) transport solution. For more information on Cisco VIA and
its gateways, please refer to the following URL:
http://www.cisco.com/en/US/netsol/ns110/ns163/ns166/ns68/networking_solutions_package.html
For more information on SS7, refer to the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/soln/voip20/index.htm.
In this solution, the Cisco AS5xxx series (Cisco AS5350, AS5400, AS5850) universal access servers may
be used as H.323 trunking gateways.
OL-3348-01 2-13
PSTN Interface
Cisco PGW 2200 Signaling Controller (Optional)

The Cisco PGW 2200 signaling controller is used in conjunction with the Cisco AS5xxx H.323 gateways
to provide SS7/C7 support. The PGW 2200 is a software application that runs on industry-standard Sun
UNIX platforms and supports ISUP, NUP, or TUP China variants. In addition to SS7 protocol functions,
the signaling controller provides system resource management (including keeping track of circuit IDs
for ports on the AS5xxx for assigning calls), call control (including originating and terminating call
processing/signaling), managing resource availability, usage measurements for accounting and
management purposes, and alarms.
The PSTN SS7 network routes SS7 messages to the Cisco PGW 2200 signaling controller, which in turn
converts the SS7 messages to an extended Q.931 protocol over IP and relays it to the AS5xxx H.323
gateways. This allows the PGW 2200 signaling controller to provide call control for multiple AS5xxx
gateways, which can be located in the same or different geographical sites.
2-14 OL-3348-01
C H A P T E R 3
CPE Deployment Options
This chapter describes the options for deploying the customer premises equipment (CPE):
• Option 1: Voice only
• Option 2: Voice and data, small-scale residential or SOHO users
• Option 3: Voice and data, larger-scale residential or SOHO users
• Option 4: Voice and data, small business
• Option 5: Voice and optionally data, small business with PBX or KTS
For voice and data connectivity, subscribers are assumed to have single Ethernet Category 3 (up to 10
Mbps) or Category 5 (up to 100 Mbps) cables prewired into their residential units. For future upgrades
or evolution, Cisco recommends using Category 5 cables.
Note Long Reach Ethernet (LRE) is not supported in this release.
These options are described in more detail in the following sections.
Option 1: Voice Only, Cisco ATA 186 or Cisco IAD 2421

If a customer wants voice services only, use the Cisco ATA 186 or the Cisco IAD 2421 as the media
gateway (see Figure 3-1 and Figure 3-2). Either one then connects with prewired Ethernet Category 3 or
Category 5 cables to the Ethernet/IP infrastructure though a LAN switch such as the Cisco Catalyst 2950
switch.
In the building basement, another switch is typically used to aggregate VLAN trunks from wiring-closet
switches on the higher floors.
Note The Cisco ATA 186 lacks a data port and thus is suitable only for subscribers who require voice-only
services without data. If integrated voice and data are required, use the Cisco ATA 188.
OL-3348-01 3-1
Chapter 3 CPE Deployment Options
Option 2: Voice and Data, Small-Scale Residential or SOHO Users, Cisco ATA 188
Figure 3-1 Voice Only, Cisco ATA 186
Cisco ATA186
82743
Cisco LAN switch
Figure 3-2 Voice Only, Cisco IAD 2421
Cisco IAD 2421

8/16 FXS
IAD
82744
Cisco LAN switch
Caution It is technically possible for the subscriber to install an Ethernet hub between the Cisco ATA 186 and the
uplink cable to allow both voice and data to run on the same VLAN, but this should not be done. Using
a hub places voice and data traffic in the same collision domain and risks degrading voice quality when
large data packets are transmitted or received.
Option 2: Voice and Data, Small-Scale Residential or SOHO

Users, Cisco ATA 188
If a residential or SOHO customer wants both voice and data services, use the Cisco ATA 188, which
includes a data port as well as voice ports. As in Option 1, the Cisco ATA 188 connects with prewired
Ethernet Category 3 or Category 5 cables to the Ethernet/IP infrastructure through a LAN switch such
as the Cisco Catalyst 2950 switch, but in this case, the Cisco ATA provides both the voice and data
connections. In the building basement, another switch is typically used to aggregate VLAN trunks from
wiring-closet switches on the higher floors.
With a Fast Ethernet data port, the Cisco ATA 188 can connect to the subscriber's PC or Ethernet hub
and up to two POTS lines (see Figure 3-3). The Ethernet hub should not be placed between the Cisco
ATA and the uplink cable; as with the Cisco ATA 186, this places voice and data traffic in the same
collision domain and risks degrading voice quality when large data packets are transmitted or received.
3-2 OL-3348-01
Option 3: Voice and Data, Larger-Scale Residential or SOHO Users, Cisco IAD 2421
Because the Cisco ATA 188 provides a 10/100 Mbps uplink, it supports auto speed and simplex/duplex
negotiation not supported by the standard Ethernet uplink on the Cisco ATA 186. It is desirable for the
floor aggregation switch to also support Fast Ethernet.
Figure 3-3 Voice and Data, Cisco ATA 188
Cisco ATA188
82745
Cisco LAN switch
Option 3: Voice and Data, Larger-Scale Residential or SOHO

Users, Cisco IAD 2421
For a building with many residential users requiring both voice and data services, use the Cisco IAD
2421 as the media gateway (see Figure 3-4). In this case, because the Cisco IAD 2421 has voice ports
only, customers' data connections (as well as the voice connections from the Cisco IAD 2421) go directly
to the Cisco Catalyst 2950 switch. Wiring to support this option is described in the following “Wiring
Plan” section.
Figure 3-4 Voice and Data, Cisco IAD 2421 and LAN Connections to Cisco Catalyst 2950
Cisco IAD 2421

8/16 FXS
IAD
82746
LAN switch
OL-3348-01 3-3
Wiring Plan When Using the Cisco IAD 2421 with Voice and Data Customers
If you use the Cisco IAD 2421 as the media gateway for customers requiring voice and data, the customer
LAN can be connected directly to the Cisco Catalyst 2950 switch. The following sections describe the
wiring necessary for this configuration.
• Wiring for One or Two POTS Lines per Unit
• Wiring for More POTS Lines per Unit
Place the Cisco IAD 2421 in a secure wiring closet, either on the building floor or in the customer unit,
depending on the number of Plain Old Telephone Service (POTS) lines the customer unit requires.
Wiring for One or Two POTS Lines per Unit

If the number of POTS lines per unit is fixed at one or two, the Cisco IAD 2421 is installed in the floor
wiring closet (see Figure 3-5). Each residential unit is prewired with a Category 3 or Category 5 cable.
To allow voice and data to run on the same cable, the cable is connected to a custom-made splitter in the
unit. The splitter includes a single RJ-45 jack for data and up to two RJ-11 jacks for POTS. Typically,
residential subscribers require only one RJ-11 jack for a single phone line; business subscribers may
require two.
The wiring of the eight copper wires inside the cable to the splitter is as follows (Figure 3-7):
• Wires 1, 2, 3, and 6 go to the RJ-45 jack for data (a single PC or a hub)
• Wires 3 and 4 go to the first RJ-11 jack for POTS
• Wires 7 and 8 go to the second RJ-11 jack for POTS (optional)
To ensure no signal interference between the copper pairs for the POTS and Ethernet, they must remain
twisted in pairs between the copper conductors on the splitter and the place where the wires are wrapped
with plastic shielding.
3-4 OL-3348-01
Figure 3-5 Wiring Example for One or Two POTS Lines
Telco cable
IAD
Cisco
IAD2421-FXS
IAD
Cisco
IAD2421-FXS Cisco
BTS 10200
IAD Softswitch
Cisco
Catalyst 2950 Metro/
82747
Backbone
Punch-down Cisco Catalyst 2950/3500XL

block
In the wiring closet on each floor, all Category 3 or 5 cables from the units are connected to standard
110 punch-down blocks with RJ-45 connectors. The data wires (1, 2, 3, 6) are separated from the POTS
wires (4, 5, 7, 8) in this configuration:
• For packet voice, the POTS wires are crosswired to an RJ-21 connector attached to the 110
punch-down block, which in turn is connected with a standard 50-wire TELCO cable to the Cisco
IAD 2421.
• For data connectivity, the Ethernet wires of the cable are crosswired to another RJ-45 jack on the
same punch-down block, which in turn is connected with another Category 5 cable to a Fast Ethernet
switch.
Because of the size of the standard 110 punch-down block and the Cisco IAD 2421 16-POTS line
capacity, each block can connect up to:
• Four RJ-45 jacks for incoming cables from dwelling/tenant units
• Four outgoing RJ-45 jacks for cables to a Fast Ethernet switch
• One RJ-21 connector for a single 50-wire TELCO cable to a Cisco IAD 2421
See Figure 3-6.
OL-3348-01 3-5
Figure 3-6 110 Punch Down Block Wiring
(Conductors 4 and 5)
4 CAT5 cables
from residences
1 RJ-21 cable
to the Cisco IAD
(Conductors 1, 2, 3 and 6)
4 RJ-45 cables
to the Ethernet Switch
Each punch down block has enough lines

to serve 4 residences with 1 Ethernet and
88106
1 POTS at each residence
Assuming that the Cisco IAD 2421 with 16 Foreign Exchange Stations (FXS) is used and each unit
requires only a single POTS line, 16 POTS lines from the Cisco IAD 2421 can support up to four 110
punch-down blocks, one of which terminates the RJ-21 TELCO cable from the Cisco IAD 2421. The
POTS lines on the other three 110 punch-down blocks are crosswired to the 110 punch-down block with
the RJ-21 connector.
For the uplink in the wiring closet on each floor, the Cisco IAD 2421 is connected to the Fast Ethernet
switch through its Ethernet port. If the service provider requires voice and data to run on separate
VLANs, configure the data ports connected to the 110 punch-down blocks and the voice port connected
to the Cisco IAD 2421 with separate VLAN IDs. Traffic of both types is sent uplink via a VLAN trunk.
Finally, a separate Fast Ethernet switch is installed in the basement to aggregate VLAN trunks from Fast
Ethernet switches.
Wiring for More POTS Lines per Unit

If the number of POTS lines per unit is near the number of supported lines on the Cisco IAD 2421 (8 or
16 FXS) or its multiples, install one or more Cisco IAD 2421 devices in a secure closet in the customer
unit itself (see Figure 3-7). This option is suitable for small and medium businesses, and avoids the need
to run multiple cables between a Cisco IAD 2421 in a floor wiring closet and the dwelling unit.
3-6 OL-3348-01
Option 4: Voice and Data, Small Business, Cisco IAD 2421
Figure 3-7 Wiring Example, Multiple POTS Lines
Cisco
IAD2421-FXS
IAD
Switch
w/Voice CoS
Cisco
IAD2421-FXS
Cisco
BTS 10200
IAD Softswitch
Switch
w/Voice CoS Metro/
82742
Backbone
Cisco Catalyst 2950/3500XL
For LAN and Internet connectivity, the customer unit requires a separate Category 5 cable (the
Cisco IAD 2421 single Ethernet interface is used for VoIP).
In the wiring closet on each floor, separate voice and data cables are connected to a LAN switch, which
provides an uplink to the next-hop Fast Ethernet switch in the basement.
This option saves the cost of splitters and 110 punch-down blocks. The customer should ensure that their
wiring closet is locked and secure.
Note It is technically possible for the customer to install an Ethernet hub between the Cisco IAD 2421 and the
uplink cable to allow both voice and data to run on the same VLAN, but this should not be done. Using
a hub places voice and data traffic in the same collision domain and risks degrading voice quality when
large data packets are transmitted or received.
Option 4: Voice and Data, Small Business, Cisco IAD 2421

For small businesses that have their own LANs, use a dedicated Cisco IAD 2421 to provide voice lines
for each customer, connecting to the Cisco Catalyst 2950 switch. The customer LAN connects directly
to the Cisco Catalyst 2950 Ethernet port.
This option has the same basic components as does Option 3; the difference is that the Cisco IAD 2421
is dedicated to a single customer.
OL-3348-01 3-7
Option 5: Voice and Data, Small Business with PBX or KTS, Cisco 26x1XM
Option 5: Voice and Data, Small Business with PBX or KTS,

Cisco 26x1XM
For businesses that have a PBX or KTS, use a Cisco 2611XM or Cisco 2621XM router. The router
provides voice ports for the PBX or KTS and an Ethernet port for the customer LAN.
The Cisco 2611XM or Cisco 2621XM router is typically deployed in a secure, locked wiring closet on
the customer's premises. Deployment is similar to deployment of the Cisco IAD 2421, but because the
Cisco 26xx has a local data port and routing capabilities, separate voice and data wiring between it and
the Fast Ethernet switch is not needed.
In high-traffic settings, the Cisco 26xx router may be set up to bypass the local Cisco 2950 Fast Ethernet
switch and connect directly to the Metro network through Ethernet or Fast Ethernet.
Design of the VLAN

Follow these practices in setting up VLANs in this solution:
• For security and manageability, all voice customer premises equipment should reside in different IP
subnets or VLANs from data elements, such as user PCs.
• Ensure that VLANs do not cross wiring-closet switches. When VLANs extend beyond a single
access switch, the Spanning Tree Protocol (STP) domain must also extend beyond a single access
switch. Because STP requires between 30 to 50 seconds to converge, if the STP domain increases
in diameter, the time it takes the network to be restored when a link goes down is significantly
increased.
For additional information on designing the VLAN, see Chapter 5, “Redundancy and Fault Tolerance.”
3-8 OL-3348-01
C H A P T E R 4
Solution Features
This chapter describes the major features of the solution.
H.323 Features Supported by the Cisco BTS 10200 Softswitch

The solution uses H.323 v.3 to communicate between the Cisco BTS 10200 Softswitch and an H.323
long-distance network. The Cisco BTS 10200 Softswitch is responsible for providing interworking
between:
• H.323 gateways and MGCP CPEs (H.323-MGCP) for PSTN access
• H.323 gateways and the IP Unity voice-mail server for access to voice-mail recording and retrieval
(H.323-SIP)
In addition, H.323-H.323 calls can be tandemed through the Cisco BTS 10200 Softswitch.
The H.323 stack within Cisco BTS 10200 Softswitch Release 3.2 is based on the Cisco IOS H.323
portable stack and supports all mandatory and some optional elements in H.323 v.3 and 4. When the
Cisco BTS 10200 Softswitch runs H.323 in full capacity, it runs four stacks concurrently. Virtually, the
Cisco BTS 10200 Softswitch appears to be four individual high-density gateways. To distinguish
themselves, these virtual gateways share the same Cisco BTS 10200 Softswitch IP addresses with their
unique H.225.0 TCP source ports. All Real Time Protocol (RTP) and RTCP packets on these virtual
gateways are originated from and terminated to the Cisco ATA 18x, Cisco IAD 2421, and Cisco 2600,
controlled by the Cisco BTS 10200 Softswitch using MGCP.
Cisco BTS 10200 Softswitch Release 3.2 supports the portable Cisco IOS H.323 stack, but provides only
a subset of the H.323 features currently supported by Cisco IOS software. The supported features are
described in the sections that follow.
Fast Connect
The Cisco BTS 10200 Softswitch always sends an H.225.0 Setup message with the Fast Connect element
to the terminating H.323 endpoint. One of the following two scenarios can occur:
• If the terminating endpoint replies with the Fast Connect element, the call is set up using the Fast
Connect procedure.
• If the terminating endpoint does not reply with the Fast Connect element up to and including the
H.225.0 Connect message, the Cisco BTS 10200 Softswitch falls back to using H.245 procedures
for media capability exchange.
OL-3348-01 4-1
Chapter 4 Solution Features
H.323 Features Supported by the Cisco BTS 10200 Softswitch
When the Cisco BTS 10200 Softswitch acts as the terminating H.323 endpoint by receiving an H.225.0
Setup message, it decides whether to use the Fast Connect or Slow Connect procedures depending on
whether there is a Fast Start element in the incoming Setup. One of the following two scenarios can
occur:
• If the Fast Start element exists, the Cisco BTS 10200 Softswitch returns it in the Alerting message,
which contains its media capabilities based on the session description protocol (SDP) from the
MGCP media gateway. Note that the Cisco BTS 10200 Softswitch never sends any Call Proceeding
message.
• If there is no Fast Start element in the incoming Setup message, the Cisco BTS 10200 Softswitch
assumes that the media capability exchange between the two endpoints is done using H.245
procedures.
H.323 Tandeming
The Cisco BTS 10200 Softswitch supports an incoming H.323 call routed to an outgoing H.323 trunk
group. This mechanism is also known as H.323 hairpin. This could happen with call forwarding, for
instance, such as an H.323 off-net call to an on-net subscriber who has forwarded calls back to the H.323
network.
Tech Prefix-Based Routing

Like a Cisco IOS gateway, the Cisco BTS 10200 Softswitch supports Tech Prefix for registration and
routing H.323 calls using the gatekeeper.
RAS Signaling
The Cisco BTS 10200 Softswitch supports Registration, Admission, and Status Protocol (RAS)
messages:
• GRQ/GCF/GRJ for gatekeeper discovery. The Cisco BTS 10200 Softswitch supports both unicast
and multicast addresses in GRQ.
• RRQ/RCF/RRJ for gatekeeper registration. The Cisco BTS 10200 Softswitch supports both static
gatekeeper lists provisioned by the CLI and a dynamic alternate gatekeeper list received in RCF and
RRJ, which overrides the static dynamic gatekeeper list.
• Information Request Response (IRR) for Cisco BTS 10200 Softswitch gateway status reporting to
the gatekeeper.
• Resource Availability Indicator (RAI) for resource availability to the gatekeeper. A static
Cisco BTS 10200 Softswitch CLI, MAX_VOIP, defined in table Trunk Group is used to define the
watermark.
• Bandwidth Request (BRQ) for bandwidth reporting to the gatekeeper.
• Restart In Progress (RIP) for the gatekeeper to inform the Cisco BTS 10200 Softswitch gateway
about address translation being in progress.
4-2 OL-3348-01
Supplementary Services
H.225.0 Signaling
The Cisco BTS 10200 Softswitch supports the following H.225.0 functions in addition to the basic
signaling:
• Call Redirection based on the canMapAlias field parameter in the ARQ
• Proprietary Octet 3a for calling number delivery
• Configurable proprietary TCP Connection Timer for outgoing H.225.0 connections
• Call signaling channel multiplexing
• Interworking of MGCP and H.225.0 messages
H.245 Signaling
The Cisco BTS 10200 Softswitch supports the following H.245 functions, in addition to the basic
signaling:
• Send and receive Empty Capability Set for Call Forwarding and H.323 IP IVR applications
• Interworking of MGCP SDP and H.245 Logical Channel Information
DTMF Relay
In dual-tone multifrequency (DTMF) relay, a local VoIP gateway listens for DTMF digits (during a call)
and then sends them uncompressed as either RTP or H.245 packets to the remote VoIP gateway, which
regenerates DTMF digits and prevents digit loss due to compression.
In MGCP-H.323 calls, the Cisco BTS 10200 Softswitch supports the following DTMF relay
interworking options:
• Out-of-band with NTFY/RQNT in MGCP and H.245 Alphanumeric
• RFC 2833 in MGCP and H.323 (requires 12.2(11) T for H.323)
In MGCP-H.323 calls, the Cisco BTS 10200 Softswitch supports the following DTMF relay
interworking options:
• Out-of-band with NTFY/RQNT in MGCP and H.245 Alphanumeric
• RFC 2833 in MGCP and H.323 (requires 12.2(11) T for H.323)
In MGCP-SIP calls (subscriber to VM), the Cisco BTS 10200 Softswitch supports the RFC 2833 DTMF
relay interworking options in MGCP and SIP.
Supplementary Services
The solution supports the most commonly used supplementary services. All features can be activated
and deactivated with predefined access codes or vertical service codes (VSCs). Some can also be
interrogated with a VSC to identify whether a service has been activated or not.
These supplementary services are supported:
• Anonymous call rejection (ACR)
• Call forwarding busy (CFB)
OL-3348-01 4-3
Bearer Features
• Call forwarding no answer (CFNA)

• Call forwarding unconditional (CFU)
• Call waiting (CW)
• Calling line identification presentation (CLIP)
• Calling line identification restriction (CLIR)
• Three way calling (TWC)
• Do not disturb (DND)
• Calling number presentation - number only (CND)
• Calling number display blocking (CNDB)
• Multiple directory number (MDN)
• Call waiting deluxe (CWD)
• Outgoing call barring (OCB)
• Centrex feature set
– Extension dialing
– Call Hold
– Call Retrieve
– Do not disturb
– Distinctive ringing for DID versus internal calls
• Message waiting indicator
• Interaction between services
Bearer Features
The solution supports the following bearer features:
• Codec support
• Call progress tones
• Fax pass-through
These features are explained in further detail in the following sections.
Codec Support
In this solution, the Cisco ATA 18x and Cisco IAD 2421 support G.711 A-law and µ-law, which is also
supported by existing gateways in the H.323 long-distance network. The Cognitronics announcement
server and IP Unity voice-mail server also support these codec types to exchange RTP with an H.323 or
MGCP gateway. To reach an agreement on what codec type is to be used in a given call, the gateways
perform codec negotiation during call setup.
In an MGCP-MGCP call, codec negotiation involves these procedures:
1. The Cisco BTS 10200 Softswitch can be preconfigured with preferred codec types for given
customer premise equipment (CPE).
4-4 OL-3348-01
Bearer Features
2. When a call is actually being set up, the Cisco BTS 10200 Softswitch indicates its preferences in the
LCO parameter when sending MGCP CRCX to the first CPE.
3. The first CPE builds the intersection list of the Cisco BTS 10200 Softswitch preferred codec types
and supported codec types in the order of highest preference to lowest. The list is returned in the
media description parameter within the SDP of MGCP response to CRCX.
4. The Cisco BTS 10200 Softswitch copies the whole SDP field, without modification, into the MGCP
CRCX that is destined to the terminating CPE. The Cisco BTS 10200 Softswitch may also indicate
its own preferences in the LCO.
5. The second CPE builds the intersection list of the received preferred codec types and supported
codec types in the order of highest preference to lowest. As a result, the terminating gateway chooses
the common codec with the highest preference.
RTP packetization period and voice activity detection (VAD) negotiation can be selected at call setup.
Both MGCP and H.323 gateways do not explicitly advertise support of packetization and VAD. RTP
packetization and VAD may be implicit with some codecs, and then are included as part of the codec
negotiation, but it is also possible to have different VAD or packetization settings on each side of the
connection.
In the Cisco BTS 10200 Softswitch, VAD support for a MGCP gateway is configurable.
In an MGCP-H.323 call, Cisco BTS 10200 Softswitch Release 3.2 does not propagate supported codec
capability of an MGCP endpoint to an H.323 endpoint and vice versa. Instead, the Cisco BTS 10200
Softswitch must have the supported codec type of the MGCP endpoint provisioned in its QoS table, and
use it for codec negotiation with the remote H.323 gateway on behalf of the MGCP endpoint. For this
reason, the Cisco BTS 10200 Softswitch codec configuration must match codec configuration at the
MGCP endpoints.
Call Progress Tones

The Cisco 26x1XM router and Cisco IAD 2421 support the following call progress tones:
• Dial tone
• Busy tone
• Ringback tone
• Call waiting tone
• Special dial tone
• Congestion tone
The Cisco ATA 18x supports the following call progress tones:
• Dial tone
• Busy tone
• Ringback tone
• Call waiting tone
• Special dial tone
• Reorder tone (also known as congestion tone)
• Confirm tone
OL-3348-01 4-5
Announcement Server Features
Fax Pass-Through
To transmit fax reliably across a data network, this solution supports Cisco proprietary fax pass-through.
Fax pass-through sends a fax transmission using high-quality voice codecs such as G.711 across the VoIP
network (see Figure 4-1). The switching method from a voice call to fax pass-through is Cisco
proprietary. There is no negotiation for fax pass-through in H.323 voice protocol. To use this feature,
therefore, all gateways in both H.323 and MGCP must support fax pass-through.
Figure 4-1 Call Flow of Switchover from Voice to Fax Pass-through
Sending Fax Receiving Fax
VoIP
V V
T.30 VoIP Established T.30 Upon establishment of the VoIP call,

both fax machines attempt to set up
a fax call with T.30
2100 Hz/V.21 Upon receiving a 2100Hz tone or a v.21

Preamble preamble from the receiving fax
machine, the egress GW up speeds to
NSE 192 G.711 and turns off VAD> It notifies with
NSE 192 to tell the ingress GW to the
same things
Fax Passthru
Established
82741
Once the voice path is established between both the originating and terminating fax machines, a fax tone
is sent (2100 Hz tone), generally by the terminating fax machine. When the terminating gateway detects
this tone, its DSP sends a Cisco Named Signaling Event (NSE) 192 to the DSP of the originating
gateway. The NSE is notification for upspeeding from the original negotiated audio codec, if not G.711
already, to G.711. NSEs are RTP packets with payload type value equal to 100 (configurable). In
addition, NSE 192 will cause VAD, Echo Cancellation and high pass filters turned off on the DSPs (and
even an increase in the dejitter buffers on some gateways to increase the tolerance to transport jitter).
Echo Cancellation is turned back on—if it was enabled previously—if a V.21 fax preamble is detected.
Then, both gateways can begin to exchange standard T.4 and T.30 fax signals for fax transmission. Upon
completion of the fax call, both gateways will stay at G.711 codec and will not down speed to the original
negotiated audio codec. Regardless of H.323 or MGCP, fax pass-through does not require any capability
negotiation during the call setup stage. The call control of both gateways is not involved in fax
pass-through because all the steps are done at the DSP level (MGCP gateways may report an mt or ft
event if instructed to do so).
Announcement Server Features

Cognitronics is an Announcement Server vendor, which has a large market share in the TDM-based
announcement servers. Cognitronics has traditionally sold their platforms to the legacy TDM operators,
and are now positioning their product for packet networks. They currently have two platforms for the
packet networks, the CX4000 and CX500. This release of the solution supports the CX500 platform.
4-6 OL-3348-01
Voice-Mail Features
CX500 Platform Key Features

• NEBS compliant
• 2 RU high (3.5"h x 12"d x 17")
• Single power supply
• UltraSparc single board design running Solaris 2.6
• N+1 redundancy support
• Supports vacant code (changed number) announcement
• CLI-based user interface for management and provisioning
• Supports MGCP 1.0
• Dynamic announcements
• 200 message function types per vocabulary, 10,000 voice files, and up to 8 vocabularies
The Cognitronics CX500 is physically located at the SuperPOP or at remote POP. Two CX500 platforms
are deployed in load sharing and redundant configuration. The MGCP call control interactions are via
MGCP 1.0. They are connected to the IP cloud via a Fast Ethernet connection.
The platform can support 200 message function types per vocabulary, 10,000 voice files, and up to 8
vocabularies. The announcements are stored as wave files. G.711 compression is required for this
solution.
The redundancy is achieved by deploying two platforms in load sharing mode. In the event of one
platform failure, the BTS uses the other platform. The announcement server gets a list of BTS CAs from
the DNS lookup. The secondary CA is used if the primary one goes down.
For information on the announcement server, please see the “Cognitronics CX500 (Third Party)
Announcement Server” section on page 2-11.
Voice-Mail Features
Note The IP Unity Unified Messaging Server is not sold or supported by Cisco.
The voice-mail server used in the solution is the IP Unity Unified Messaging Server. This section
describes features provided by the IP Unity voice-mail server.
• Answering Service
The answering service allows users to record and retrieve voice messages, as well as use different
options when leaving messages. Other answering service features include:
– Sending faxes directly to the mailbox
– Automatically insert sender’s mailbox number
– A built-in Find me/forward feature
– Support for call screening
• Message Alerts
There are many message alert features to notify users of waiting messages, including a message
waiting indication alert, a message waiting notification by pager or phoneand offsite pager
notification.
OL-3348-01 4-7
Data Features
• Accessibility
The IP Unity voice-mail server provides accessiblity by allowing them to read email using
text-to-speech technology, and by using speech recognition.
• Web Interface
The voice-mail server also provides Web interface feautres, including Web-based configuration,
Web-based personalization, and Web-based access for messages.
For more information about the IP Unity Unified Messaging Server, refer to
http://ipunity.com/products/media.html.
SIP Support
The solution uses the Session Initiation Protocol (SIP) to communicate between the Cisco BTS 10200
Softswitch and the voice-mail server. The Cisco BTS 10200 Softswitch is responsible for providing SIP
interworking with MGCP CPEs (SIP-MGCP) and H.323 gateways (SIP-H.323) to provide access to
voice-mail recording and retrieval.
Codec Support
The voice-mail server provides codec support for G.711 for both message recording and playout. The
Cisco BTS 10200 Softswitch facilitates codec negotiation between MGCP and SIP for calls originating
from MGCP and between H.323 and SIP for calls originating from H.323.
DTMF Relay Support

• To support RFC 2833 DTMF relay, the Cisco BTS 10200 Softswitch performs capability exchange
during call setup between the MGCP/H.323 originator and the voice-mail server.
• Cisco ATA 18x and voice-mail: DTMF relay RFC 2833
• Cisco IAD 2421 or Cisco Analog 2600 router and voice-mail: DTMF relay RFC 2833
• H.323 Gateway and voice-mail: DTMF RFC2833 is supported in H.323 gateways running Cisco IOS
12.2(11)T or above
Alternatively, in-band G.711 can be used. This requires DSP on the voice-mail platform.
Data Features
The solution supports the following data features:
• Voice VLAN Support on the Cisco ATA 188
• Packet Marking and Port-Based Queuing on the Cisco ATA 188
These features are explained in further detail in the following sections.
4-8 OL-3348-01
Data Features
Voice VLAN Support on the Cisco ATA 188

A VLAN (Layer 2) maps to a subnet (Layer 3) as a broadcast domain in such a way that the VLAN is
equivalent to a subnet. The Cisco Catalyst software currently supports the Voice VLAN ID (VVID), the
voice VLAN that the switch assigns to the IP phone inside the enhanced Cisco Discovery Protocol (CDP)
message, referred to as CDP v.2. It allows the Cisco ATA 188 to get its VLAN ID automatically when it
is plugged into the switch if a VVID is configured for the Cisco ATA 188. If no VVID is configured, the
Cisco ATA 188 resides in the native VLAN (data subnet) of the Cisco Catalyst switch.
The trigger field is used by a newly connected Cisco ATA 188 to force a response from the remote switch.
Under normal circumstances, the Catalyst switch sends CDP update messages at a configured interval
(default is one minute). If the Cisco ATA 188 is connected between CDP messages, it cannot receive its
VVID. In this case, it issues a trigger in the CDP message that it sends to the switch, forcing the switch
to respond with a VVID.
Packet Marking and Port-Based Queuing on the Cisco ATA 188

In the Cisco ATA 188, there is both data traffic from PCs and voice traffic from the box itself transmitted
to the core network. To ensure minimal latency and jitters on the voice traffic, the Cisco ATA provides
CoS and ToS marking for RTP and MGCP packets and port-based queuing on the uplink Ethernet
interface.
Data traffic is forwarded transparently (on the native VLAN if untagged, on the specified VLAN if
tagged). If the PC is sending tagged frames with a specific CoS and ToS values, the Cisco ATA 188 does
not zero out this value before sending the frames to the switch. The Cisco ATA 188 does not tag data
frames or zero out CoS values but it queues voice as high priority.
OL-3348-01 4-9
Data Features
4-10 OL-3348-01
C H A P T E R 5
Redundancy and Fault Tolerance
This chapter describes how to design your network for redundancy and fault tolerance, and discusses the
constraints on a redundant, fault-tolerant design. Table 5-1 summarizes the fault tolerance of the various
solution components.
Table 5-1 Fault Tolerance of Solution Components
Solution Component Fault Tolerance

Cisco BTS 10200 Softswitch CA/FS and EMS with 1:1 redundancy
Cisco ATA 18x analog telephone adaptor No specific fault tolerance
Cisco IAD 2421 Integrated Access Device No specific fault tolerance
Cisco 26xx router None (trunk groups can be split between routers)
H.323 Gatekeeper for the Cisco BTS 10200 Gatekeeper cluster or alternate gatekeeper
Softswitch
Cognitronics Announcement Server 1:n redundancy
voice-mail system IP Unity
Redundant Deployment of the Cisco BTS 10200 Softswitch

The Cisco BTS 10200 Softswitch is deployed in a fully redundant primary and secondary configuration
where the secondary call agent takes over when the primary call agent fails. The Cisco BTS 10200
Softswitch is designed for high availability, with no single point of failure.
A single call agent consists of an active and standby half, located on the Sun UNIX platform. Call-state
information is copied from the active to the standby call agent, which ensures that no established calls
are lost in a switchover from active to standby mode. (H.323 calls are an exception, because of their TCP
nature.) The active Cisco BTS 10200 Softswitch processes all calls.
Each access device performs DNS lookup to locate the IP address of both the primary Cisco BTS 10200
Softswitch and the standby; default DNS lookup points to the active Cisco BTS 10200 Softswitch.
During normal conditions, all access devices communicate with the active BTS. If the active Cisco BTS
10200 Softswitch fails, the standby becomes active.
The active and standby call agents exchange periodic keepalive timers called KAM/RDM to detect any
failure scenarios. If a failure scenario is detected, the standby call agent takes over and becomes active.
OL-3348-01 5-1
Chapter 5 Redundancy and Fault Tolerance
Service Provider POP Redundant Network Design
Other Cisco BTS 10200 Softswitch elements, feature servers and Element Management System (EMS)
are also deployed in active/standby configurations, with real-time synchronization of data between the
active and the standby elements.
No traffic load sharing between the active, and the standby call agents is done. The active Cisco BTS
10200 Softswitch performs all call processing and the standby is idle.

In the service provider point of presence (POP) shown in Figure 5-1, there are four main clusters of
network elements:
• The Cisco BTS 10200 Softswitch call agent, feature server, and EMS, as described in the previous
section
• The gatekeeper cluster for the Cisco BTS 10200 Softswitch
• The announcement server farm
• The voice-mail server farm
Figure 5-1 Service Provider POP Network Design
Cisco BTS 10200 softswitch
CA-A CA-B EMS-A EMS-B H.323 GK cluster Announcement

servers
Voice mail
GK servers
GK
GK
VLAN 4 VLAN 5
VLAN 2 VLAN 7
VLAN 1 VLAN 6 VLAN 9
VLAN 3 VLAN 8
VLAN 10
FE
Cisco Catalyst 6509

ISL
GE
Border
router
82750
MGCP and H.323

networks
5-2 OL-3348-01
The objective of this design is to provide continuous network connectivity if there is a single failure
caused by a network element in the POP. Each network element is equipped with two Fast Ethernet
interfaces connected to the POP. As a result, each cluster connects to a redundant pair of Cisco Catalyst
6509 switches over two redundant VLANs, one being active and the other being standby, to transport
voice signaling traffic (H.323, MGCP, and EG323) or RTP traffic.
Note The Cisco BTS 10200 Softswitch has a third VLAN for Telnet traffic and multiple internal VLANs
within its cluster for intra-CA/FS/EMS traffic, which is not connected to the Catalyst 6509.
The virtual H.323 gateways of the Cisco BTS 10200 Softswitch are still registered at the gatekeeper
cluster. This is to ensure that if a physical interface on one of the gatekeepers fails, the gateways are still
registered to the IP addresses of the loopback interfaces on the gatekeepers instead of those of the
physical interfaces. Using an advanced routing protocol in the POP, such as OSPF or EIGRP, is a
requirement for fast failure recovery.
The Cisco Catalyst 6509 switches connect to each other with ISL for redundancy. The switched also
connect to a pair of border routers such as a Cisco 7500 or GSR 12000, with a redundant pair of Gigabit
Ethernet links for communication with the MGCP CPEs and H.323 network.
OL-3348-01 5-3
5-4 OL-3348-01
C H A P T E R 6
Sample Network and Configurations
The sample configurations provided in this chapter are for a network similar to that shown in Figure 6-1.
Each supported type of customer premise equipment (CPE) configuration is illustrated, including:
• A building where Cisco ATA 188 analog telephone adaptors are used as the media gateway,
connecting to a basement Cisco LAN switch into the Metro Ethernet infrastructure to the local voice
network.
The illustration shows the Cisco ATA 188 used only for voice, but it can also be used for data by
connecting the subscriber's PC or LAN to the second Ethernet port of the Cisco ATA 188.
• A building where Cisco IAD 2421 integrated access devices are used as the media gateway, also
connecting to a basement Cisco LAN switch.
In this case, because the Cisco IAD 2421 has voice ports only, subscribers' PC data connections are
routed directly to the Ethernet port on the basement LAN switch.
• A building where a key telephone system (KTS) or PBX connects to a Cisco 2611XM analog router,
serving as the media gateway and connecting directly to the Metro Ethernet infrastructure and the
local voice network.
The illustration shows the Cisco 2611XM router used only for voice, but it also may be used for data
by connecting the subscriber’s LAN to the second Fast Ethernet port of the router.
In the local voice network are the call agent, the Cisco BTS 10200 Softswitch, an announcement server
(in this example, a Cisco AS5300 universal access server), and a gatekeeper (a Cisco 2611XM router)
connecting to the H.323 network, which can be used for local PSTN termination or as a voice distance
network. This gatekeeper is dedicated to the Cisco BTS 10200 Softswitch for registration and call
admission.
There are two additional gatekeepers in the H.323 network:
• A Cisco 2601 router provides registration and call admission for the H.323 gateway (a Cisco
AS5xx0) to the PSTN.
• A Cisco 2602 router serves as a directory gatekeeper exchanging call routing information via
Location Request (LRQ) and Location Confirm (LCF) messages of H.225.0 registration, admission
and status (RAS) signaling between the first gatekeeper and the gatekeeper dedicated to the
Cisco BTS 10200 Softswitch.
Note In your implementation, for best performance we recommend using the Cisco 7200 router or the Cisco
3660 router as gatekeepers.
OL-3348-01 6-1
Chapter 6 Sample Network and Configurations
Cisco BTS 10200 Softswitch Sample Configuration
Figure 6-1 Sample Network
Cisco ATA188
V
Cisco
BTS 10200 Gatekeeper
Softswitch
DGK
dgk-2601 Gatekeeper
Cisco LAN switch Gatekeeper H.323

Long Distance GK
Local Voice Network gk-2602
Network GK
gk-2601
Cisco IAD 2421 Trunking
8/16 FXS gateway
IAD
V
PSTN-5350
PRI
LAN switch
Announcement
server
TDM switch
V
82749
Cisco
2611 XM
PBX or KTS
router
FXS

Example 6-1 shows how to configure the Cisco BTS 10200 Softswitch for use with the devices shown
in Figure 6-1.
Example 6-1 Cisco BTS 10200 Softswitch Configuration Example
############################################
# Add call agents
############################################
add call-agent id=CA146; TSAP-ADDR-SIDEA=bts-ca; ems-primary-tsap=bts-ems;

mgw-monitoring-enabled=Y
############################################
# Add feature servers
############################################
add feature-server id=FSPTC235; TSAP-ADDR-SIDEA=bts-ca:11235; type=POTS;

ems-primary-tsap=bts-ems;
add feature-server id=FSAIN205; TSAP-ADDR-SIDEA=bts-ca:11205; type=AIN;
ems-primary-tsap=bts-ems;
6-2 OL-3348-01
add ca_config datatype=INTEGER; type=CPRK-ANN; value=0;

add ca_config datatype=INTEGER; type=CPRK-CLEAR; value=0;
add ca_config datatype=INTEGER; type=CPRK-HC-T1; value=48;
add ca_config datatype=INTEGER; type=CPRK-TIMER; value=60;
add ca_config datatype=STRING; type=AC-ACTIVATION-LEVEL; value=ONE;
add ca_config datatype=BOOLEAN; type=ARAC-ACTIVATIION-TO-COIN; value=N;
add ca_config datatype=BOOLEAN; type=ARAC-ACTIVATION-TO-ANONYMOUS-DN; value=N;
add ca_config datatype=BOOLEAN; type=ARAC-ACTIVATION-TO-MLHG; value=Y;
add ca_config datatype=BOOLEAN; type=ARAC-ACTIVATION-TO-NON-UNIQUE-DN; value=N;
add ca_config datatype=INTEGER; type=ARAC-INITIAL-QUERY-RESPONSE-TIMER-T5; value=3;
add ca_config datatype=INTEGER; type=ARAC-MAX-6SEC-RINGING-CYCLES; value=4;
add ca_config datatype=INTEGER; type=ARAC-MAX-CONCURRENT-ATTEMPTS; value=30;
add ca_config datatype=INTEGER; type=ARAC-MAX-QUEUE-SIZE; value=15;
add ca_config datatype=INTEGER; type=ARAC-MAX-UNANSWERED-RING-APPLICATIONS; value=2;
add ca_config datatype=INTEGER; type=ARAC-MONITORING-TIMER-T6; value=30;
add ca_config datatype=INTEGER; type=ARAC-ORIGINATING-SCAN-RATE; value=60;
add ca_config datatype=INTEGER; type=ARAC-OSPCS-OVERALL-MONITOR-TIMER-T10; value=3;
add ca_config datatype=INTEGER; type=ARAC-OUTSTANDING-NOTIFICATION-TIMER-T8; value=35;
add ca_config datatype=INTEGER; type=ARAC-PERIODIC-SCAN-RATE; value=30;
add ca_config datatype=BOOLEAN; type=ARAC-QUEUING-SUPPORTED; value=Y;
add ca_config datatype=INTEGER; type=ARAC-RESUME-SCANNING-THRESHOLD-TIME; value=5;
add ca_config datatype=INTEGER; type=ARAC-RESUME-SCANNING-TIMER-T2; value=5;
add ca_config datatype=INTEGER; type=ARAC-SUB-QUERY-RESPONSE-TIMER-T9; value=3;
add ca_config datatype=INTEGER; type=ARAC-TERMINATING-SCANNING-MONITOR-TIMER-T7; value=30;
add ca_config datatype=BOOLEAN; type=ARAC-TERMINATING-SPCS-SCAN-ALLOW; value=Y;
add ca_config datatype=STRING; type=AR-ACTIVATION-LEVEL; value=ONE;
add ca_config datatype=INTEGER; type=ARAC-TSPCS-OVERALL-MONITOR-TIMER-T10; value=3;
add ca_config datatype=STRING; type=COT-ACTIVATION-LEVEL; value=ONE;
add ca_config datatype=BOOLEAN; type=CODEC-MOD-DURING-CALL; value=N;
add ca_config datatype=INTEGER; type=COLLECT-TMR; value=50;
add ca_config datatype=INTEGER; type=CONN-ACK-TMR; value=2;
add ca_config datatype=STRING; type=DEFAULT-INTL-DIAL-PLAN-ID; value=DEFAULT;
add ca_config datatype=STRING; type=DEFAULT-ODR; value=DEFAULT;
add ca_config datatype=INTEGER; type=DEFAULT-OFFICE-SERVICE-ID; value=999;
add ca_config datatype=INTEGER; type=DEFAULT-OLI; value=255;
add ca_config datatype=INTEGER; type=DEFAULT-POP; value=255;
add ca_config datatype=STRING; type=DEFAULT-QOS-ID; value=DEFAULT;
add ca_config datatype=STRING; type=DEFAULT-REGION; value=DEFAULT;
add ca_config datatype=BOOLEAN; type=E911-CALLED-PARTY-HOLD; value=Y;
add ca_config datatype=INTEGER; type=NO-RESP-TMR; value=20;
add ca_config datatype=INTEGER; type=OSI-GUARD-TMR; value=2;
add ca_config datatype=BOOLEAN; type=PST-AFTER-TIMED-RELEASE; value=Y;
add ca_config datatype=INTEGER; type=RECONNECT-TMR; value=65;
add ca_config datatype=INTEGER; type=SSF-TMR; value=5;
add ca_config datatype=INTEGER; type=SUSP-TMR; value=10;
add ca_config datatype=INTEGER; type=TIME-RELEASE-INTERVAL; value=10;
add ca_config datatype=INTEGER; type=TONE-TIMER; value=5;
add ca_config datatype=BOOLEAN; type=FSPTC-SIG-TOS-LOWDELAY; value=Y;
add ca_config datatype=INTEGER; type=FSPTC-SIG-TOS-PRECEDENCE; value=2;
add ca_config datatype=BOOLEAN; type=FSPTC-SIG-TOS-RELIABILITY; value=N;
add ca_config datatype=BOOLEAN; type=FSPTC-SIG-TOS-THROUGHPUT; value=N;
add ca_config datatype=BOOLEAN; type=H323-SUPPORTED; value=N;
add ca_config datatype=INTEGER; type=MGCP-ICMP-PING-RETRANSMIT-DURATION; value=2;
add ca_config datatype=INTEGER; type=MGCP-ICMP-PING-RETRY-COUNT; value=2;
add ca_config datatype=INTEGER; type=MGCP-INIT-DURATION; value=1;
add ca_config datatype=INTEGER; type=MGCP-INIT-TERMS; value=1000;
add ca_config datatype=INTEGER; type=MGCP-MAX-RETRANSMIT-COUNT; value=3;
add ca_config datatype=INTEGER; type=MGCP-MAX-UNREACH-COUNT; value=5;
add ca_config datatype=INTEGER; type=MGCP-MIN-RETRANSMIT-COUNT; value=2;
add ca_config datatype=INTEGER; type=MGCP-PING-ATTEMPTS; value=2;
add ca_config datatype=INTEGER; type=MGCP-PING-DURATION; value=60;
add ca_config datatype=INTEGER; type=MGCP-TIMER-VAL; value=400;
add ca_config datatype=INTEGER; type=MGCP-MAX-FAULT-COUNT; value=5;
add ca_config datatype=INTEGER; type=MGCP-RECOVERY-DURATION; value=2;
OL-3348-01 6-3
add ca_config datatype=BOOLEAN; type=MGCP-SIG-TOS-LOWDELAY; value=Y;

add ca_config datatype=INTEGER; type=MGCP-SIG-TOS-PRECEDENCE; value=2;
add ca_config datatype=BOOLEAN; type=MGCP-SIG-TOS-RELIABILITY; value=N;
add ca_config datatype=BOOLEAN; type=MGCP-SIG-TOS-THROUGHPUT; value=N;
add ca_config datatype=BOOLEAN; type=CLASS5-SUPPORTED; value=N;
add ca_config datatype=BOOLEAN; type=SPLIT-NPA-ACTIVE; value=N;
add ca_config datatype=BOOLEAN; type=TANDEM-SUPPORTED; value=N;
add ca_config datatype=BOOLEAN; type=SIA-SIG-TOS-LOWDELAY; value=Y;
add ca_config datatype=INTEGER; type=SIA-SIG-TOS-PRECEDENCE; value=2;
add ca_config datatype=BOOLEAN; type=SIA-SIG-TOS-RELIABILITY; value=N;
add ca_config datatype=BOOLEAN; type=SIA-SIG-TOS-THROUGHPUT; value=N;
add ca_config datatype=BOOLEAN; type=SIM-SIG-TOS-LOWDELAY; value=Y;
add ca_config datatype=INTEGER; type=SIM-SIG-TOS-PRECEDENCE; value=2;
add ca_config datatype=BOOLEAN; type=SIM-SIG-TOS-RELIABILITY; value=N;
add ca_config datatype=BOOLEAN; type=SIM-SIG-TOS-THROUGHPUT; value=N;
add ca_config datatype=STRING; type=ENCRYPTION-KEY; value=0000000000000000;
add ca_config datatype=INTEGER; type=MAX-SUBSCRIPTION-LEVEL; value=3600;
add ca_config datatype=BOOLEAN; type=RADIUS-AUTHORIZATION-ALLOWED; value=N;
add ca_config datatype=INTEGER; type=RADIUS-CLIENT-PORT; value=1813;
add ca_config datatype=BOOLEAN; type=REFER-NOTIFY-FULL; value=N;
add ca_config datatype=INTEGER; type=WHISPER-TONE-TIMER; value=30;
add ca_config datatype=INTEGER; type=SLE-DE-THRESHOLD; value=3;
add ca_config datatype=INTEGER; type=SLE-LIST-SIZE; value=31;
add ca_config datatype=INTEGER; type=SLE-TIMER-T1; value=4;
add ca_config datatype=INTEGER; type=SLE-TO-THRESHOLD; value=3;
add ca_config datatype=INTEGER; type=CAR-800-TTYPE; value=254;
add ca_config datatype=INTEGER; type=CNAM-TTYPE; value=254;
add ca_config datatype=INTEGER; type=LNP-TTYPE; value=11;
add ca_config datatype=INTEGER; type=NAT-800-TTYPE; value=254;
#######################################################
# Define gateway profiles
#######################################################
add mgw_profile id=ata_MGCP1_0; vendor=cisco; silent-suppress-supp=y; rbk-on-conn-supp=n;
packet-type=ip; aal1=n; aal2=n; aal5=n; pvc=n; svc=n;spvc=n; ec=y; mparty-conference=n;
mparty-3way=n; num-per-mparty=1; num-of-mparty=1; lptime=10; hptime=20; isdn=n; dtmf=n;
mf=n; fxo=n; fxs=n; fgd=n; backhaul-type=rudp; sdp-origfield-unsupp=y;
sdp-sessname-unsupp=y; sdp-email-unsupp=y; sdp-phone-unsupp=y; sdp-uri-unsupp=y;
sdp-bandwidth-unsupp=y; sdp-info-unsupp=y; sdp-time-unsupp=y;
sdp-attrib-unsupp=y;mgcp-erqnt-unsupp=y; mgcp-hairpin-unsupp=y; mgcp-qloop-unsupp=y;
mgcp-3way-hshake-unsupp=n; mgcp-conn-id-at-gw-unsupp=y; mgcp-cmd-seq-unsupp=y;
termination-prefix=aaln/; port-start=0; description=ciscoubr;mgcp_version=MGCP_1_0
add mgw-profile id=2420_MGCP1_0; vendor=cisco; mgcp_version=MGCP_1_0; packet-type=ip;
aal1=n; aal2=n; aal5=n; pvc=n; svc=n; spvc=n; ec=n; mparty-3way=n;
mparty-conference=n; lptime=20; hptime=20; silent-suppress-supp=y; rbk-on-conn-supp=y;
isdn=n; dtmf=n; mf=n; fxo=n; fgd=n; mgcp-erqnt-unsupp=y; mgcp-hairpin-unsupp=y;
mgcp-cmd-seq-unsupp=y; mgcp-vmwi-unsupp=y;
add mgw-profile id=2600_MGCP1_0; vendor=cisco; mgcp_version=MGCP_1_0; packet-type=ip;
aal1=n; aal2=n; aal5=n; pvc=n; svc=n; spvc=n; ec=n; mparty-3way=n;
mparty-conference=n; lptime=20; hptime=20; silent-suppress-supp=y; rbk-on-conn-supp=y;
isdn=n; dtmf=n; mf=n; fxo=n; fgd=n; mgcp-erqnt-unsupp=y; mgcp-hairpin-unsupp=y;
mgcp-cmd-seq-unsupp=y; mgcp-vmwi-unsupp=y;
add mgw_profile id=as5300_MGCP1_0; silent_suppress_supp=y; packet_type=ip; aal1=n; aal2=n;
aal5=n; pvc=n; svc=n; spvc=n; ec=n; mparty_conference=n; mparty_3way=n; num_per_mparty=1;
num_of_mparty=1; lptime=20; hptime=20; isdn=y; dtmf=y; mf=y; fxo=n; fxs=n; fgd=n;
backhaul_type=rudp; sdp_origfield_unsupp=y; sdp_sessname_unsupp=y;
sdp_email_unsupp=y;sdp_phone_unsupp=y;sdp_bandwidth_unsupp=y;sdp_info_unsupp=y;sdp_time_un
6-4 OL-3348-01
supp=y;sdp_attrib_unsupp=y;mgcp_erqnt_unsupp=y;mgcp_hairpin_unsupp=y; mgcp_qloop_unsupp=y;
mgcp_3way_hshake_unsupp=n; mgcp_conn_id_at_gw_unsupp=y; termination_prefix=null;
port_start=1; vendor=cisco; mgcp_cmd_seq_unsupp=y; mgcp_version=MGCP_1_0;
############################################
# Add announcement trunk group profile
############################################
add annc-tg-profile
id=1;annc=y;ivr=n;annc-sig-type=TCL-CISCO;auto-answer=n;local-trunk-selection=y;descriptio
n=UsedForCisco5300
############################################
# Add subscriber profile
############################################
##################################################
# Add dial plan profiles
##################################################
add dial-plan-profile id=na; NANP_DIAL_PLAN=Y; description=North America Dial Plan
Profile;
############################################
# Add POP table
############################################
add pop id=1; state=tx; country=usa; timezone=pst; zero-minus=lec; block-eawopic=n;
pic2-reqd=n; cnam_option=ext_lidb; digit-map-id=na
############################################
# Add digit map
############################################
add digit-map id=na;
digit-pattern=0T|00|[2-9]11|[2-9]xx[2-9]xxxxxx|1[2-9]xx[2-9]xxxxxx|0[2-9]xx[2-9]xxxxxx|011
xxxxxx.T|01xxxxxx.T|101xxxx|#|*xx |11xx|xxxxxxxxxxxxxxxxxx; description=North America
Pattern;
###################################
# Add features for services
###################################
add feature fname=CFU; tdp1=TERMINATION_ATTEMPT_AUTHORIZED;
tid1=TERMINATION_ATTEMPT_AUTHORIZED; ttype1=R; fname1=CFUA; fname2=CFUD; type1=MCF;
value1=Y; type2=RR; value2=Y; description=CFU MCF=multiple call forwarding allowed,
RR=ring reminder; feature_server_id=FSPTC235;
add feature fname=CFUA; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;
ttype1=R; type1=INTL; value1=N; description=CFU Activation, INTL=CF to international DN
allowed; feature_server_id=FSPTC235;
add feature fname=CFUD; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;
ttype1=R; description=Call Forwarding Uncoditional Deactivation;
feature_server_id=FSPTC235;
add feature fname=CFB; tdp1=T_BUSY; tid1=T_BUSY; ttype1=R; fname1=CFBVA; fname2=CFBVD;
description=Call Forwarding Busy; feature_server_id=FSPTC235;
add feature fname=CFBVA; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;
ttype1=R; type1=INTL; value1=N; description=Call Forwarding Busy Activation;
add feature fname=CFBVD; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;
ttype1=R; description=Call Forwarding Busy Deactivation; feature_server_id=FSPTC235;
add feature fname=CFNA; tdp1=CALL_ACCEPTED; tid1=CALL_ACCEPTED; ttype1=R;
fname1=CFNAVA; fname2=CFNAVD; type1=TO; value1=30; description=Call Forwarding No
Answer TO=Timeout ; feature_server_id=FSPTC235;
add feature fname=CFNAVA; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;
ttype1=R; type1=INTL; value1=N; description=CFNA Variable Activation;
OL-3348-01 6-5
add feature fname=CFNAVD; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;

ttype1=R; description=Call Forwarding No Answer Variable Deactivation;
add feature fname=TWC; tdp1=O_MID_CALL; tdp2=T_MID_CALL;
tid1=O_SWITCH_HOOK_FLASH_IMMEDIATE; tid2=T_SWITCH_HOOK_FLASH_IMMEDIATE; ttype1=R;
ttype2=R; description=Three way call; feature_server_id=FSPTC235;
add feature fname=CW; tdp1=T_BUSY; tid1=T_BUSY; ttype1=R; description=Call Waiting;
add feature fname=CCW; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;
ttype1=R; description=Cancel Call Waiting; feature_server_id=FSPTC235;
add feature fname=CND; tdp1=FACILITY_SELECTED_AND_AVAILABLE;
tid1=TERMINATION_RESOURCE_AVAILABLE; ttype1=R; description=Calling number delivery;
add feature fname=CNDB; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;
ttype1=R; description=Calling Number Delivery Blocking(toggles the privacy indicator);
add feature fname=ACR; tdp1=TERMINATION_ATTEMPT_AUTHORIZED;
tid1=TERMINATION_ATTEMPT_AUTHORIZED; ttype1=R; description=Anonymous Call Rejection;
add feature fname=ACR_ACT; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;
ttype1=R; description=ACR Activation; feature_server_id=FSPTC235;
add feature fname=ACR_DEACT; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;
ttype1=R; description=ACR Deactivation; feature_server_id=FSPTC235;
add feature fname=MDN; tdp1=TERMINATION_ATTEMPT_AUTHORIZED;
tid1=TERMINATION_ATTEMPT_AUTHORIZED; ttype1=R; description=Multiple Directory Numbers;
add feature fname=DND; tdp1=TERMINATION_ATTEMPT_AUTHORIZED;
tid1=TERMINATION_ATTEMPT_AUTHORIZED; ttype1=R;description=Do Not Disturb;
add feature fname=DND_ACT; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;
ttype1=R; description=DND Activation; feature_server_id=FSPTC235;
add feature fname=DND_DEACT; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;
ttype1=R; description=DND Deactivation ; feature_server_id=FSPTC235;
add feature fname=CIDSD; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;
ttype1=R; description=Calling Identity Delivery; feature_server_id=FSPTC235;
add feature fname=CIDSS; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;
ttype1=R; description=Calling Identity Delivery Supression; feature_server_id=FSPTC235;
add feature fname=CWD; tdp1=T_BUSY; tid1=T_BUSY; ttype1=R; description=Call Waiting
Deluxe; feature_server_id=FSPTC235;
add feature fname=CWDA; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;
ttype1=R; description=Call Waiting Deluxe Activation; feature_server_id=FSPTC235;
add feature fname=CWDD; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;
ttype1=R; description=Call Waiting Deluxe Deactivation; feature_server_id=FSPTC235;
add feature fname=CWDI; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;
ttype1=R; description=Call Waiting Deluxe Interrogation; feature_server_id=FSPTC235;
add feature fname=TWCD; tdp1=O_MID_CALL; tdp2=T_MID_CALL;
tid1=O_SWITCH_HOOK_FLASH_IMMEDIATE; tid2=T_SWITCH_HOOK_FLASH_IMMEDIATE; ttype1=R;
ttype2=R; description=Three way call Deluxe; feature_server_id=FSPTC235;
add feature fname=CFUI; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;
ttype1=R; description=Call Forwarding Uncoditional Interrogation;
add feature fname=CFBI; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;
ttype1=R; description=Call Forward on Busy Interrogation; feature_server_id=FSPTC235;
add feature fname=CFNAI; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;
ttype1=R; description=Call Forward on No Answer Interrogation;
add feature fname=HOTV; tdp1=O_ATTEMPT_AUTHORIZED; tid1=O_ATTEMPT_AUTHD; ttype1=R;
type1=TO; value1=4; description=Hotline-Variable; feature_server_id=FSPTC235;
add feature fname=HOTVA; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;
ttype1=R; description==Hotline-Variable Activation; feature_server_id=FSPTC235;
add feature fname=HOTVD; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;
ttype1=R; description==Hotline-Variable Deactivation; feature_server_id=FSPTC235;
add feature fname=HOTVI; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;
ttype1=R; description==Hotline-Variable Interrogation; feature_server_id=FSPTC235;
6-6 OL-3348-01
add feature fname=OCB; tdp1=COLLECTED_INFORMATION; tid1=COS_TRIGGER; ttype1=R;

description=Outgoing Call Barring; feature_server_id=FSPTC235;
add feature fname=OCBA; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;
ttype1=R; description=Outgoing Call Barring Activation; feature_server_id=FSPTC235;
add feature fname=OCBD; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;
ttype1=R; description=Outgoing Call Barring Deactivation; feature_server_id=FSPTC235;
add feature fname=OCBI; tdp1=COLLECTED_INFORMATION; tid1=VERTICAL_SERVICE_CODE;
ttype1=R; description=Outgoing Call Barring Interrogation; feature_server_id=FSPTC235;
#
# Optional Umbrella features.
#
add feature fname=CLIP; fname1=CND; fname2=CNAM; feature_server_id=FSPTC235;
add feature fname=CLIR; fname1=CNDB; fname2=CNAB; feature_server_id=FSPTC235;
add feature fname=CIDS; fname1=CIDSD; fname2=CIDSS; feature_server_id=FSPTC235;
############################################
# Define the star-codes for features.
############################################
add vsc digit_string=*57; fname=COT;
add vsc digit_string=*60; fname=SCR_ACT;
add vsc digit_string=*61; fname=DRCW_ACT;
add vsc digit_string=*63; fname=SCF_ACT;
add vsc digit_string=*64; fname=SCA_ACT;
add vsc digit_string=*66; fname=AC_ACT;
add vsc digit_string=*67; fname=CNDB;
add vsc digit_string=*69; fname=AR_ACT;
add vsc digit_string=*70; fname=CCW;
add vsc digit-string=*72;fname=CFUA
add vsc digit-string=*73;fname=CFUD
add vsc digit_string=*74; fname=SC1D_ACT;
add vsc digit_string=*75; fname=SC2D_ACT;
add vsc digit_string=*77; fname=ACR_ACT;
add vsc digit_string=*78; fname=DND_ACT;
add vsc digit_string=*79; fname=DND_DEACT;
add vsc digit_string=*80; fname=SCR_ACT;
add vsc digit_string=*81; fname=DRCW_ACT;
add vsc digit_string=*82*; fname=CIDSD;
add vsc digit_string=*83; fname=SCF_ACT;
add vsc digit_string=*84; fname=SCA_ACT;
add vsc digit_string=*86; fname=AC_DEACT;
add vsc digit_string=*87; fname=ACR_DEACT;
add vsc digit_string=*89; fname=AR_DEACT;
add vsc digit-string=*90;fname=CFBVA
add vsc digit-string=*91;fname=CFBVD
add vsc digit-string=*92;fname=CFNAVA
add vsc digit-string=*93;fname=CFNAVD
add vsc digit_string=*95; fname=CNAB;
add vsc digit_string=*96*; fname=CIDSS;
add vsc digit_string=*97; fname=CBLK;
add vsc digit_string=*52*; fname=HOTVA;

add vsc digit_string=#52#; fname=HOTVD;
add vsc digit_string=*#52*; fname=HOTVI;
add vsc digit_string=*54*; fname=OCBA;
add vsc digit_string=#54*; fname=OCBD;
add vsc digit_string=*#54#; fname=OCBI;
add vsc digit_string=*57*; fname=CFUA;
add vsc digit_string=#57#; fname=CFUD;
add vsc digit_string=*#57*; fname=CFUI;
add vsc digit_string=*40*; fname=CFBVA;
add vsc digit_string=#40#; fname=CFBVD;
add vsc digit_string=*#40*; fname=CFBI;
add vsc digit_string=*41*; fname=CFNAVA;
OL-3348-01 6-7
add vsc digit_string=#41#; fname=CFNAVD;

add vsc digit_string=*#41*; fname=CFNAI;
add vsc digit_string=*58#; fname=CWDA;
add vsc digit_string=#58#; fname=CWDD;
add vsc digit_string=*#58#; fname=CWDI;
############################################
# Define services for collections of features
############################################
add service id=301; fname1=CND; fname2=CNDB; description=Caller Number Delivery & Blocking
Package
add service id=302; fname1=CW; fname2=CCW; description=Call Waiting Package
add service id=303; fname1=TWC; description=3 Way Call Package
add service id=304; fname1=CFU; fname2=CFB; fname3=CFNA; description=Call Forward Package
add service id=305; fname1=ACR; description=Anonymous Call Reject
add service id=306; fname1=DND; description=Do Not Disturb Package
add service id=307; fname1=MDN; description=Multiple Directory Number Package
add service id=308; fname1=OCB; fname2=OCBA; fname3=OCBD; fname4=OCBI;
description=Outgoing Call Barring Package
add service id=309; fname1=CT; description=Call Transfer Package
################################
# Add destination
################################
add destination dest-id=local_call; call-type=LOCAL; route-type=SUB;
###########################################################################
# Add dial plan for sj_tme_iad-1, sj_tme_ata-1, sj_tme_2600-1
###########################################################################
add ndc digit-string=972;
add exchange-code ndc=972; ec=578100; office-code-index=11;

add office-code ndc=972; ec=578100; dn-group=x; call-agent-id=CA146;
add dial-plan id=na; digit-string=972578100; dest-id=local_call; reqd-digits=10;
min-digits=10; max-digits=10


###########################################################################
# Add mgw for sj_tme_ata188-1
###########################################################################
add mgw id=sj_tme_ata188-1; tsap-addr=10.0.1.111; call-agent-id=CA146;
mgw-profile-id=ata_MGCP1_0; rgw=y; tgw=n; nas=n; pbx=n; ans=n; ivr=n;
call-agent-control-port=0;
###########################################################################
# Add termination for sj_tme_ata188-1
###########################################################################
add termination prefix=a00; port-start=1; port-end=2; type=LINE;
mgcp-pkg-type=LINE_MGCP; mgw-id=sj_tme_ata188-1
###########################################################################
# Add subscriber-profile for sj_tme_ata188-1
###########################################################################
add subscriber-profile id=ata188_prof1; dial-plan-id=na; digit-map-id=na; pop-id=1;
6-8 OL-3348-01
###########################################################################
# Add subscribers for sj_tme_ata188-1
###########################################################################
add subscriber id=9725781001; category=INDIVIDUAL; name=9725781001; status=ACTIVE;
billing-dn=972-578-1001; dn1=972-578-1001; ring-type-dn1=1; term-id=a001;
sub-profile-id=ata188_prof1; mgw-id=sj_tme_ata188-1;
add subscriber id=9725781002; category=INDIVIDUAL; name=9725781002; status=ACTIVE;
billing-dn=972-578-1001; dn1=972-578-1002; ring-type-dn1=1; term-id=a002;
sub-profile-id=ata188_prof1; mgw-id=sj_tme_ata188-1;
add subscriber-service-profile sub-id=9725781001; service-id=301; priority=1;


###########################################################################
# Turn up sj_tme_ata188-1
###########################################################################
control mgw id=sj_tme_ata188-1; target-state=oos; mode=forced;
control mgw id=sj_tme_ata188-1; target-state=ins; mode=forced;
equip subscriber-termination id=9725781001

control subscriber-termination id=9725781001; target-state=OOS; mode=FORCED;
control subscriber-termination id=9725781001; target-state=INS; mode=FORCED;

###########################################################################
# Add mgw id for sj_tme_iad-1
###########################################################################
add mgw id=sj_tme_iad-1; tsap-addr=10.0.1.116; call-agent-id=CA146;
mgw-profile-id=2420_MGCP1_0; rgw=y; tgw=n; nas=n; pbx=n; ans=n;
call-agent-control-port=0; ivr=n;
###########################################################################
# Add termination for sj_tme_iad-1
###########################################################################
add termination prefix=aaln/S1/; port-start=1; port-end=8; type=LINE;
mgcp-pkg-type=LINE_MGCP; mgw-id=sj_tme_iad-1;
###########################################################################
# Add subscriber profiles and subscribers for sj_tme_iad-1
###########################################################################
add subscriber-profile id=iad_prof1; dial-plan-id=na; digit-map-id=na; pop-id=1;
add subscriber id=9725783001; category=INDIVIDUAL; name=sub1; status=ACTIVE;
billing-dn=972-578-3001; dn1=972-578-3001; ring-type-dn1=1; term-id=aaln/S1/1;
sub-profile-id=iad_prof1; mgw-id=sj_tme_iad-1;
OL-3348-01 6-9

###########################################################################
# Add subscribers for sj_tme_iad-1
###########################################################################
###########################################################################
# Turn up sj_tme_iad-1 and its subscribers
###########################################################################
control mgw id=sj_tme_iad-1; target-state=oos; mode=forced;
control mgw id=sj_tme_iad-1; target-state=ins; mode=forced;



###########################################################################
# Add mgw id for sj_tme_2600-1
###########################################################################
add mgw id=sj_tme_2600-1; tsap-addr=10.0.1.99; call-agent-id=CA146;
mgw-profile-id=2600_MGCP1_0; rgw=y; tgw=n; nas=n; pbx=n; ans=n;
call-agent-control-port=0; ivr=n;
###########################################################################
# Add termination for sj_tme_2600-1
###########################################################################
add termination prefix=aaln/S1/SU0/; port-start=0; port-end=1; type=LINE;
mgcp-pkg-type=LINE_MGCP; mgw-id=sj_tme_2600-1;
###########################################################################
# Add subscriber profiles and subscribers for sj_tme_2600-1
###########################################################################
add subscriber-profile id=2600_prof1; dial-plan-id=na; digit-map-id=na; pop-id=1;
billing-dn=972-267-1001; dn1=972-267-1001; ring-type-dn1=1; term-id=aaln/S1/SU0/0;
sub-profile-id=2600_prof1; mgw-id=sj_tme_2600-1;
billing-dn=972-267-1002; dn1=972-267-1002; ring-type-dn1=1; term-id=aaln/S1/SU0/1;
sub-profile-id=2600_prof1; mgw-id=sj_tme_2600-1;
6-10 OL-3348-01
###########################################################################
# Turn up sj_tme_2600-1 and its subscribers
###########################################################################
control mgw id=sj_tme_2600-1; target-state=oos; mode=forced;
control mgw id=sj_tme_2600-1; target-state=ins; mode=forced;


###########################################################################
# Add mgw id for as5300_as
###########################################################################
add mgw id=as5300_as; tsap-addr=10.0.1.106; call-agent-id=CA146;
mgw-profile-id=as5300_MGCP1_0; rgw=n; tgw=y; ans=y; CALL-AGENT-CONTROL-PORT=0;
add termination prefix=S0/DS1-0/; port-start=1; port-end=24; type=trunk;

mgcp-pkg-type=ANNC; mgw-id=as5300_as;
add termination prefix=S0/DS1-1/; port-start=1; port-end=24; type=trunk;
mgcp-pkg-type=ANNC; mgw-id=as5300_as;
add trunk-grp id=901; call-agent-id=CA146; tg_type=ANNC; cost=1; status=oos;
tg-profile-id=1;
add trunk-grp id=902; call-agent-id=CA146; tg_type=ANNC; cost=1; status=oos;
tg-profile-id=1;
add route id=rt_annc1; lcr=y; tgn1-id=901;
add route id=rt_annc2; lcr=y; tgn1-id=902;
add route-guide id=rg_annc1; policy-type=ROUTE; policy-id=rt_annc1;
add route-guide id=rg_annc2; policy-type=ROUTE; policy-id=rt_annc2;
add trunk termination-prefix=S0/DS1-0/; termination-port_start=1; termination-port_end=24;

cic_start=1; cic_end=24; tgn-id=901; mgw-id=as5300_as;
add trunk termination-prefix=S0/DS1-1/; termination-port_start=1; termination-port_end=24;
cic_start=1; cic_end=24; tgn-id=902; mgw-id=as5300_as;
add annc-trunk tgn-id=901; term-id=S0/DS1-0/1; mgw-id=as5300_as;

remote-term-id=S0/DS1-0/1; remote-mgw-id=as5300_as;
OL-3348-01 6-11

6-12 OL-3348-01

###########################################################################
# Add announcements
###########################################################################
add announcement id=0010; type=SYSTEM; route-guide-id=rg_annc1;
announcement-file=ann_id_10.au;
###########################################################################
# Add announcements cause
###########################################################################
add release-cause id=0034; annc-id=0011;
OL-3348-01 6-13
###########################################################################
# Bring up the mgw and trunks
###########################################################################
control mgw id=as5300_as;target-state=oos;mode=forced
control mgw id=as5300_as;target-state=ins;mode=forced
control trunk-grp id=901;call-agent-id=CA146;target-state=oos;mode=forced

control trunk-grp id=901;call-agent-id=CA146;target-state=ins;mode=forced

equip trunk-termination tgn-id=901;cic=all

control trunk-termination;mode=forced;target-state=oos;cic=all;tgn-id=901
control trunk-termination;mode=forced;target-state=ins;cic=all;tgn-id=901
equip trunk-termination tgn-id=902;cic=all

control trunk-termination;mode=forced;target-state=oos;cic=all;tgn-id=902
control trunk-termination;mode=forced;target-state=ins;cic=all;tgn-id=902
###########################################################################
# Add H.323 configuration
###########################################################################
add h323_tg_profile; id=h323_ras; RAS=Y; DTMF_CISCO_RTP_SUPP=N;

DTMF_H245_ALPHA_SUPP=Y; DTMF_H245_SIGNAL_SUPP=N; DTMF_RFC2833=N
add service_provider id=tme;

add tech_prefix_grp_profile; id=tp_tme1;
add tech_prefix_grp id=tp_tme1; tech_prefix=1#; sp_id=tme;
add trunk_grp id=611; call_agent_id=CA146; tg_type=H323; SOFTSW_TSAP_ADDR=10.0.1.75;

tg_profile_id=h323_ras; dial_plan_id=na
add route id=rt_wsv; tgn1_id=611;
add destination dest_id=dest_wsv; call_type=LOCAL; route_type=RID; route_id=rt_wsv;
add dial-plan id=na; digit-string=408; dest-id=dest_wsv; reqd-digits=10; min-digits=10;

max-digits=10
max-digits=10
max-digits=10
max-digits=10
add h323_gw id=bts_gw1; gw_h225_port=1740; tgn_id=611; security=N;

tech_prefix_grp_id=tp_tme1; SECURITY_LEVEL=ENDPOINT; password=cisco;
change trunk_grp id=611; h323_gw_id=bts_gw1;
add h323_gw2gk h323_gw_id=bts_gw1; gk_id=bts-gk1; priority=1; gk_ip_addr=10.0.1.86;

multicast=N; gk_ras_port=1719;
control h323_gw id=bts_gw1;target-state=oos

control h323_gw id=bts_gw1;target-state=ins

6-14 OL-3348-01
CPE Sample Configurations

This section provides configuration examples for these types of CPE devices:
• Cisco ATA 18x analog telephone adaptor
• Cisco IAD 2421 integrated access device
• Cisco 26x1XM router
Cisco ATA 18x Sample Configuration

The sample configuration shown in Figure 6-2 (a Cisco ATA 188 configuration screen) is for the
Cisco ATA 186 or Cisco ATA 188 shown in Figure 6-1.
OL-3348-01 6-15
Figure 6-2 Sample Cisco ATA 188 Configuration
6-16 OL-3348-01
Cisco IAD 2421 Sample Configuration

Example 6-2 shows a sample configuration for the Cisco IAD 2421 shown in Figure 6-1.
Note If the Cisco IAD 2421 is installed in an environment where voice and data are on different VLANs, the
Catalyst switch port which the Cisco IAD 2421 is connected to must be configured on the voice VLAN.
Example 6-2 Cisco IAD 2421 Configuration Example
Current configuration : 3834 bytes

!
! No configuration change since last restart
!
version 12.2
no service pad
service timestamps debug datetime localtime
service timestamps log uptime
no service password-encryption
!
hostname 2421-city3
!
logging buffered 2000000 debugging
enable password cisco
!
username cisco password 0 cisco
network-clock base-rate 56k
ip subnet-zero
!
!
ip domain name nsitelab.com
ip name-server 192.168.100.150
!
ip audit notify log
ip audit po max-events 100
!
!
voice call carrier capacity active
!
!
!
!
!
!
!
no voice confirmation-tone
!
!
voice-card 0
!
!
controller T1 0
framing sf
linecode ami
!
!
!
!
interface Ethernet0
ip address 192.168.102.41 255.255.255.0
ntp broadcast client
OL-3348-01 6-17
!
interface Serial0
no ip address
shutdown
!
ip classless
ip route 0.0.0.0 0.0.0.0 192.168.102.254
no ip http server
ip pim bidir-enable
!
!
logging 192.168.100.118
snmp-server enable traps snmp authentication linkdown linkup coldstart warmstart
no snmp-server enable traps tty
snmp-server enable traps config
snmp-server enable traps entity
snmp-server enable traps voice poor-qov
snmp-server enable traps xgcp
snmp-server enable traps dnis
snmp-server host 192.168.100.113 public
call rsvp-sync
!
voice-port 1/1
cptone HK
caller-id enable
idle-voltage high
!
voice-port 1/2
cptone HK
caller-id enable
idle-voltage high
!
voice-port 1/3
cptone HK
codec g729r8
!
voice-port 1/4
cptone HK
caller-id enable
idle-voltage high
!
voice-port 1/5
cptone HK
caller-id enable
idle-voltage high
!
voice-port 1/6
cptone HK
caller-id enable
idle-voltage high
!
voice-port 1/7
cptone HK
caller-id enable
idle-voltage high
!
voice-port 1/8
cptone HK
caller-id enable
idle-voltage high
!
voice-port 1/9
cptone HK
caller-id enable
6-18 OL-3348-01
idle-voltage high
!
voice-port 1/10
cptone HK
caller-id enable
idle-voltage high
!
voice-port 1/11
cptone HK
caller-id enable
idle-voltage high
!
voice-port 1/12
cptone HK
caller-id enable
idle-voltage high
!
voice-port 1/13
cptone HK
caller-id enable
idle-voltage high
!
voice-port 1/14
cptone HK
caller-id enable
idle-voltage high
!
voice-port 1/15
cptone HK
caller-id enable
idle-voltage high
!
voice-port 1/16
cptone HK
caller-id enable
idle-voltage high
!
mgcp
mgcp call-agent mgcp-SYS11CA.nsitelab.com service-type mgcp version 1.0
mgcp dtmf-relay voip codec all mode nte-gw
mgcp modem passthrough voip mode nse
mgcp modem passthrough voip codec g711alaw
mgcp codec g711alaw packetization-period 10
mgcp ip qos dscp cs5 media
mgcp ip qos dscp cs3 signaling
mgcp tse payload 105
no mgcp timer receive-rtcp
mgcp sdp simple
mgcp fax t38 ecm
mgcp rtp payload cisco-pcm-switch-over-ulaw 126
mgcp rtp payload cisco-pcm-switch-over-alaw 127
!
mgcp profile default
!
dial-peer cor custom
!
!
!
dial-peer voice 1 pots
application mgcpapp
port 1/1
!
application mgcpapp
OL-3348-01 6-19
port 1/2
!
application mgcpapp
port 1/3
!
application mgcpapp
port 1/4
!
application mgcpapp
port 1/5
!
application mgcpapp
port 1/6
!
application mgcpapp
port 1/7
!
application mgcpapp
port 1/8
!
application mgcpapp
port 1/9
!
application mgcpapp
port 1/10
!
application mgcpapp
port 1/11
!
application mgcpapp
port 1/12
!
application mgcpapp
port 1/13
!
application mgcpapp
port 1/14
!
application mgcpapp
port 1/15
!
application mgcpapp
port 1/16
!
banner motd ^C
FT1.0 test bed, contact nsite-ft@cisco.com
^C
!
line con 0
6-20 OL-3348-01
line aux 0
line 2 3
line vty 0 4
exec-timeout 0 0
password cisco
login
!
ntp clock-period 17207321
end
Cisco 26x1XM Router Sample Configuration

Both the Cisco 2611XM router and Cisco 2621XM router are supported as media gateways. Example 6-3
shows a sample configuration for the Cisco 2611XM analog router shown in Figure 6-1.
Example 6-3 Cisco 26x1XM Configuration Example
!
version 12.2
no parser cache
service timestamps debug uptime
!
hostname 10.0.1.99
!
ip subnet-zero
!
no ip domain lookup
ip host bts-ca 10.0.1.123
!
!
!
!
fax interface-type fax-mail
mta receive maximum-recipients 0
!
interface FastEthernet0/0
ip address 10.0.1.99 255.255.255.224
half-duplex
!
no ip address
shutdown
half-duplex
!
ip classless
ip route 0.0.0.0 0.0.0.0 10.0.1.97
no ip http server
ip pim bidir-enable
!
snmp-server manager
call rsvp-sync
!
voice-port 1/0/0
!
voice-port 1/0/1
!
voice-port 1/1/0
pre-dial-delay 3
OL-3348-01 6-21
!
voice-port 1/1/1
!
mgcp
mgcp call-agent bts-ca 2427 service-type mgcp version 1.0
!
!
!
application mgcpapp
port 1/0/0
!
application mgcpapp
port 1/0/1
!
line con 0
exec-timeout 0 0
line aux 0
line vty 0 4
exec-timeout 0 0
no login
!
end
!
version 12.2
no parser cache
!
hostname 10.0.1.99
!
ip subnet-zero
!
no ip domain lookup
!
!
!
!
!
ip address 10.0.1.99 255.255.255.224
half-duplex
!
no ip address
shutdown
half-duplex
!
ip classless
ip route 0.0.0.0 0.0.0.0 10.0.1.97
no ip http server
ip pim bidir-enable
!
snmp-server manager
6-22 OL-3348-01
Announcement Server Sample Configuration
call rsvp-sync
!
voice-port 1/0/0
!
voice-port 1/0/1
!
voice-port 1/1/0
pre-dial-delay 3
!
voice-port 1/1/1
!
mgcp
mgcp call-agent bts-ca 2427 service-type mgcp version 1.0
!
!
!
application mgcpapp
port 1/0/0
!
application mgcpapp
port 1/0/1
!
line con 0
exec-timeout 0 0
line aux 0
line vty 0 4
exec-timeout 0 0
no login
!
end

Example 6-4 shows a sample configuration for a Cisco AS5300 access server serving as an
announcement server, as shown in Figure 6-1.
Note Cisco recommends using a Cognitronics CX500 for the announcement server. However, this example is
provided to show the steps for configuration, and the required parameters for setting up MGCP.
Example 6-4 Announcement Server Configuration Example
!
version 12.2
service timestamps debug datetime msec localtime
service timestamps log datetime msec localtime
!
hostname 10.0.1.106
!
resource-pool disable
!
ip subnet-zero
OL-3348-01 6-23
!
isdn switch-type primary-ni
isdn voice-call-failure 0
!
voice service voip
modem passthrough nse codec g711ulaw redundancy
!
!
fax interface-type modem
!
controller T1 0
framing esf
clock source line primary
linecode b8zs
ds0-group 0 timeslots 1-24 type none service mgcp
!
controller T1 1
framing esf
clock source line secondary 1
linecode b8zs
ds0-group 0 timeslots 1-24 type none service mgcp
!
controller T1 2
framing esf
linecode b8zs
!
controller T1 3
framing esf
linecode b8zs
!
interface Ethernet0
no ip address
shutdown
!
interface FastEthernet0
ip address 10.0.1.106 255.255.255.128
duplex auto
speed auto
!
ip classless
ip route 0.0.0.0 0.0.0.0 10.0.1.97
no ip http server
!
call rsvp-sync
!
voice-port 0:0
!
voice-port 1:0
!
mgcp
mgcp call-agent bts-ca service-type mgcp version 1.0
mgcp package-capability dtmf-package
mgcp package-capability rtp-package
mgcp package-capability as-package
mgcp package-capability script-package
mgcp fax t38 inhibit
!
!
line con 0
exec-timeout 0 0
transport preferred none
line aux 0
6-24 OL-3348-01
Gatekeeper Sample Configurations
line vty 0 4
exec-timeout 0 0
no login
transport preferred none
!
end

Configurations are shown for three gatekeepers:
• A Cisco 2601 router in the local voice network POP (gk-2601). This gatekeeper is dedicated to the
Cisco BTS 10200 Softswitch for registration and call admission.
• A Cisco 2601 router in the H.323 long-distance network (dgk-2601). This serves as a directory
gatekeeper exchanging call routing information via Location Request (LRQ) and Location Confirm
(LCF) messages of H.225.0 registration, admission, and status (RAS) signaling between the first
gatekeeper and the gatekeeper dedicated to the Cisco BTS 10200 Softswitch.
• A Cisco 2602 router in the H.323 long-distance network (gk-2602). This provides registration and
call admission for the H.323 gateway (a Cisco AS5xx0 access server) to the PSTN.
Note In your implementation, for best performance we recommend using the Cisco 7200 router or the
Cisco 3660 router as gatekeepers.
Cisco 2601 Router Sample Configuration (Local Voice Network)

Example 6-5 shows a sample configuration for a Cisco 2611XM router in the local voice network POP,
whose hostname is gk-2601, as shown in Figure 6-1.
Example 6-5 Cisco 2611XM Configuration Example
!
version 12.2
no service single-slot-reload-enable
!
hostname gk-2601
!
logging rate-limit console 10 except errors
!
ip subnet-zero
!
no ip domain-lookup
!
no ip dhcp-client network-discovery
!
!
!
!
interface Ethernet0/0
ip address 10.0.1.86 255.255.255.128
half-duplex
!
OL-3348-01 6-25
no ip address
shutdown
half-duplex
!
ip classless
ip route 0.0.0.0 0.0.0.0 10.0.1.1
no ip http server
!
!
!
gatekeeper
zone local bts-gk1 cisco.com 10.0.1.86
zone remote dgk-2601 cisco.com 10.0.1.70 1719
zone prefix bts-gk1 972*
zone prefix dgk-2601 *
gw-type-prefix 1#* default-technology
load-balance endpoints 1
no shutdown
!
line con 0
exec-timeout 0 0
line aux 0
line vty 0 4
exec-timeout 0 0
password cisco
login
line vty 5 15
login
!
no scheduler allocate
!
end
Cisco 2601 Router Sample Configuration (H.323 Network)

Example 6-6 shows a sample configuration is for the Cisco 2601 router functioning as a directory
gatekeeper in the H.323 long-distance network, whose hostname is dgk-2601, as shown in Figure 6-1.
Example 6-6 Cisco 2601 Router Directory Gatekeeper Configuration Example
!
version 12.2
!
hostname dgk-2601
!
!
ip subnet-zero
!
no ip domain-lookup
!
!
!
6-26 OL-3348-01
ip address 10.0.1.70 255.255.255.128
half-duplex
!
ip address 10.1.100.10 255.255.255.0
half-duplex
!
router igrp 100
network 10.0.0.0
!
ip classless
ip route 0.0.0.0 0.0.0.0 10.0.1.1
no ip http server
!
tftp-server flash:c2600-ix-mz
tftp-server flash:c2600-ix-mz.122-0.21.T
!
!
gatekeeper
zone local dgk-2611 cisco.com 10.0.1.70
zone remote bts-gk1 cisco.com 10.0.1.86 1719
zone remote pstn-gk cisco.com 10.0.1.88 1719
zone prefix bts-gk1 214*
zone prefix pstn-gk 408*
gw-type-prefix 1#*
lrq forward-queries
no shutdown
!
line con 0
line aux 0
line vty 0 4
exec-timeout 0 0
password cisco
login
line vty 5 15
login
!
end
Cisco 2602 Router Sample Configuration (H.323 Network)

Example 6-7 shows a sample configuration for the Cisco 2602 router in the H.323 long-distance
network, whose hostname is gk-2602, as shown in Figure 6-1.
Example 6-7 Cisco 2621XM Router Configuration Example
!
version 12.2
!
hostname gk-2602
!
OL-3348-01 6-27

!
ip subnet-zero
!
!
!
ip address 10.0.1.88 255.255.255.128
half-duplex
!
no ip address
shutdown
half-duplex
!
ip classless
ip route 0.0.0.0 0.0.0.0 10.0.1.1
no ip http server
!
tftp-server flash:
!
!
gatekeeper
zone local pstn-gk cisco.com 10.0.1.88
zone remote dgk-2611 cisco.com 10.0.1.70 1719
zone prefix dgk-2611 *
gw-type-prefix 1#* default-technology
no shutdown
!
line con 0
line aux 0
line vty 0 4
exec-timeout 0 0
password cisco
login
line vty 5 15
login
!
no scheduler allocate
!
end
Trunking Gateway Sample Configuration

The trunking gateway sample in Figure 6-1 provides the connection to the PSTN from the H.323
network. Example 6-8 shows a configuration for a Cisco AS5xx0 access server, hostname pstn-5350.
Example 6-8 Trunking Gateway Configuration Example
!
version 12.2
no parser cache
service timestamps debug datetime msec localtime
service timestamps log datetime msec localtime
6-28 OL-3348-01
!
hostname pstn-5xx0
!
no logging buffered
!
username all
!
resource-pool disable
clock timezone PST -8
clock summer-time PDT recurring
!
ip subnet-zero
no ip domain lookup
!
isdn switch-type primary-5ess
!
!
voice service voip
h323
modem passthrough nse codec g711ulaw
!
voice class codec 1
codec preference 1 g711alaw
codec preference 2 g711ulaw
codec preference 3 g729r8
!
!
!
!
controller T1 0
framing esf
clock source line primary
linecode b8zs
pri-group timeslots 1-24
!
controller T1 1
shutdown
framing esf
clock source line secondary 1
linecode b8zs
!
controller T1 2
shutdown
framing esf
linecode b8zs
!
controller T1 3
shutdown
framing sf
linecode ami
!
interface Ethernet0
no ip address
shutdown
!
interface Serial0:23
no ip address
isdn switch-type primary-ni
isdn incoming-voice modem
no cdp enable
OL-3348-01 6-29
!
interface FastEthernet0
ip address 10.0.1.75 255.255.255.224
duplex full
speed auto
h323-gateway voip interface
h323-gateway voip id pstn-gk ipaddr 10.0.1.88 1718
h323-gateway voip h323-id pstn-5350
h323-gateway voip tech-prefix 1#
!
ip classless
ip route 0.0.0.0 0.0.0.0 10.0.1.65
no ip http server
!
call rsvp-sync
!
voice-port 0:D
translate called 1
!
!
!
destination-pattern ^[2-9].........
no digit-strip
direct-inward-dial
port 0:D
prefix 1
!
dial-peer voice 11 voip
destination-pattern 972.......
modem passthrough nse codec g711ulaw
voice-class codec 1
session target ras
dtmf-relay h245-alphanumeric
no vad
!
gateway
!
line con 0
exec-timeout 0 0
logging synchronous
line aux 0
line vty 0 4
exec-timeout 0 0
password cisco
login
!
scheduler interval 1000
end
6-30 OL-3348-01
C H A P T E R 7
Design Limitations
This chapter describes the design limitations for the Cisco Broadband Local Integrated Services
Solution-ETTX solution.
Feature Limitations
The solution has the following feature limitations:
• T.38 fax relay
T.38 fax relay is only available between two Cisco IOS Media Gateway Control Protocol (MGCP)
endpoints (for example, a Cisco IAD 2421 and an analog Cisco 2600). Fax over IP in other endpoint
combinations is completed by using pass-through.
• Billing interoperability
The call agent produces a different format of call detail records (CDRs) than those common in Cisco
H.323 transit solutions. As a result, you may need special arrangements to interconnect with IP
transit networks and ensure billing interoperability.
• Voice mail, MGCP and H.323
Voice mail is only accessible from MGCP endpoints in this release, not from H.323 endpoints.
Supported Features
• G.711 A-law and U-law codecs
In this release, only G.711 A-law and U-law codecs are supported.
• Modem over IP
Modem over IP is supported only in pass-through mode for all the Cisco IOS H.323 and MGCP
platforms.
Note The Cisco ATA 18x does not support modem pass-through.
Features Not Supported

• Cascading Cisco ATA 188 devices
Cascading (daisy chaining) Cisco ATA 188 devices is not supported.
OL-3348-01 7-1
Chapter 7 Design Limitations
Subscriber Features Requiring ANI
• SIP
SIP is not supported in this release for any use beyond interfacing to the voice messaging system.
• E1 and DSL links
E1 and DSL links are not supported on the Cisco IAD 2421 in this release—only Ethernet uplinks
are supported.
Subscriber Features Requiring ANI

If the call agent provides subscriber-specific features such as called number restriction, the Private
Branch Exchanges (PBXs) connected via Foreign Exchange Station (FXS) cannot transmit individual
subscriber extensions.
For PBXs, the Cisco BTS 10200 Softswitch determines the automatic number identification (ANI) for
the trunk based on its database, and not based on the digits sent from the PBX. The Cisco BTS 10200
Softswitch is provisioned with a number block (such as 408-525-xxxx) for the particular PBX. The
Cisco BTS 10200 Softswitch does not know from which extension of the PBX a call originates because
there is no ANI reported in the incoming MGCP NTFY message. In this case, the call restriction can be
done on a per PBX basis, not on a per line basis.
NAT/PAT Translation
To use private IP space in the network, consider the simultaneous calls that must be supported in
interfaces to other networks. For capacities, refer to the latest information on Cisco NAT/PAT translation
boxes like the Cisco 7200 with the NPE-400 Network Processor Engine.
Also consider which voice protocols can successfully pass through existing NAT boxes. At the time the
Release 1.0 documentation was written, NAT was only supported in H.323, but not in MGCP.
Firewalls
Scaling is an issue for firewalls. You must carefully calculate how much traffic will pass through a given
firewall, because scalability is more limited in this area.
Also be aware of which voice protocols can successfully pass through existing firewall boxes. For
example, a Cisco voice-aware firewall supports some H.323 transparency, but not MGCP.
Failover Limitations
If the call agent experiences a failover from active to standby, there is no call preservation on active calls
in which H.323 is at least one of the call legs. Only calls with MGCP on both call legs are preserved.
Any call not in a stable state (that is, a call in progress and not yet “connected”) also fails during a
failover.
7-2 OL-3348-01
C H A P T E R 8
Solution Network Management
Table 8-1 summarizes the solution network management fault, configuration, accounting, performance,
and security (FCAPS) components that are described in more detail in the following sections.
Table 8-1 Solution Component Network Management Summary
Component Fault Configuration Accounting Performance Security

Cisco BTS 10200 BTS 10200-EMS BTS 10200-EMS Third-party billing Not in scope Cisco BTS 10200
Softswitch R3.2 R3.2 system EMS R3.2
EPOM v1.1
CIC R3.4.1 (with
patches)
Cisco ATA 186 or The current release CNR R5.5.2 — Not in scope Native device
188 does not generate security
alarms.
Cisco IAD 2421 C-NOTE R2.0 BAC v2.5 — Not in scope Native device
CIC R3.4.1 CNR R5.5.2 security
Cisco 26xx/FXS C-NOTE R2.0 BAC v2.5 — Not in scope Native device
CIC R3.4.1 CNR R5.5.2 security
Cisco 7200 C-NOTE R2.0 CLI — Not in scope Native device

(gatekeeper) CIC R3.4.1 security
Cisco Network CIC R3.4.1 CNR R5.5.2 GUI — Not in scope CNR R5.5.2
Registrar
Fault Management
Cisco BTS 10200 Softswitch Release 3.2—The Cisco BTS 10200 Softswitch is a distributed switch
controller designed to provide the major functions performed by traditional class 4 and class 5 switching
systems. The Cisco BTS 10200 Softswitch includes an integrated element management system (EMS)
for FCAPS management.
Cisco BTS 10200 Softswitch EMS provides an SNMP agent to forward its events and alarms to an
external Fault Management System, such as Cisco Information Center (CIC).
Cisco Networking Services (CNS) Notification Engine (C-NOTE) Release 2.0—C-NOTE processes
event entries in IOS SYSLOG file and converts selected entries to alarms, which are reported to a Fault
Management System such as the CIC or Hewlett-Packard OpenView. Delivery of events and alarms to
external system may be SNMP traps, or over CNS bus.
OL-3348-01 8-1
Chapter 8 Solution Network Management
Configuration and Provisioning
C-NOTE collects SYSLOG files from the Cisco IAD 2421, 26xx, and 7200, and then:
• Parses all IOS SYSLOG messages, alleviating the need for the operator to understand complicated
and inconsistent message structure
• Converts the parsed data from SYSLOG messages into structured, detailed SNMP traps, which
reduces reaction time
• Delivers traps in a reliable manner
• Preprocesses and filters SYSLOG messages prior to trap generation
• Reduces number of traps generated by ~ 90%
• Categorizes SYSLOG messages and traps
• Provides consistent handling of SYSLOG messages and consistent northbound interface across
Cisco IOS
For more information on C-NOTE, refer to the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cns_note/rel_2_0/index.htm
Cisco Information Center Release 3.4.1—CIC is a service-level alarm monitoring and diagnostics tool
that provides network fault and performance monitoring, network trouble isolation, and real-time,
service-level management for large networks. CIC is designed to help operators focus on important
network events, offering a combination of alarm processing rules, filtering, customizable alarm viewing,
and partitioning. CIC provides a highly configurable client/server application that can consolidate,
de-duplicate, filter, and correlate fault information from multitechnology, multivendor network and
management platforms.
Because this solution is a voice network that overlays an existing core and access network, operational
procedures for management of this network are limited. Fault management is limited to fault detection
only. Operational procedures for troubleshooting are dependent on customer network and operation
processes and organization. Use of CIC applications to automate procedures will be evaluated after
operational procedures are defined and tested in specific customer environments.
CIC supports both SNMP and CNS bus interface for receiving events and alarms from managed
elements.

The scope of subscriber provisioning to support this solution is limited to updating of the
Cisco BTS 10200 Softswitch, and setting up customer premise equipment (CPE) for new subscribers.
Network provisioning of the Cisco BTS 10200 Softswitch, the core and access network, and data
services is outside the scope of the solution.
For information on provisioning the Cisco BTS 10200 Softswitch, refer to the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/bts10200/bts3_2/index.htm
The system for managing provisioning in the solution includes:
• CNR to manage DHCP and DNS services and ATA configuration files
• The Cisco BTS 10200 Softswitch EMS
• EPOM 1.1 for BTS provisioning
• BAC for provisioning Cisco IOS-based CPE
Cisco Network Registrar Management Tools—A set of tools including a GUI interface is provided to
manage DHCP, DNS, and TOD (time of day) services.
8-2 OL-3348-01
CNR also offers multithreaded, high-performance TFTP, which can be used to store ATA configuration
files.
For more information, refer to the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/ciscoasu/nr/nr55/index.htm.
Cisco BTS 10200 Softswitch Release 3.2—The Cisco BTS 10200 Softswitch includes an integrated
EMS for managing FCAPS, and a published API interface. External management systems can obtain
programmable access to the Cisco BTS 10200 Softswitch through its defined CORBA interface to
deliver provisioning data or query against the Cisco BTS 10200 Softswitch for configuration or
subscriber data. XML over CORBA is also supported by the Cisco BTS 10200 Softswitch.
For more information on the Cisco BTS 10200 Softswitch, refer to the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/bts10200/bts3_2/index.htm
Extensible Provisioning and Operations Manager (EPOM) Release 1.1—The Extensible
Provisioning and Operations Manager (EPOM) is a web-based application for real-time provisioning of
the Cisco BTS 10200 Softswitch. EPOM allows authorized users to carry out the following provisioning
tasks:
• Show, add, modify, and delete subscriber services
• Show the status of components and place them in or out of service
Provisioning tasks in EPOM generally match tasks done using the Cisco BTS 10200 Softswitch CLI or
MAC interface, but are accomplished through a web-browser interface. Common multistep procedures
are simplified by being grouped together into tasks executed with task wizards.
Authorized EPOM administrators set up and manage the EPOM server software and perform EPOM user
administration and network setup tasks:
• Set up the network initially
• Show, add, modify, and delete Cisco BTS 10200 Softswitch devices
• Show, add, modify, and delete media gateways such as the Cisco IAD 2421 and Cisco 2611XM or
Cisco 2621XM router
• Add, modify, and delete users, user groups, and domains
For more information on EPOM, refer to the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/voice/bts10200/bts3_2/epom_fm.htm
Broadband Access Center for Convergent Network Subscriber Provisioning (BAC) Release
2.5—BAC provides data-driven provisioning services that allow the creation of flexible, customizable
service, provisioning, and task profiles. In this solution, BAC is used to provision Cisco IOS-based CPE.
Provisioning features include incrementally adding, modifying, or deleting services based on customer
subscriber device needs and custom configuration of CPE and aggregation devices using templates.
BAC also enables full network service life-cycle management, starting with the creation of new service
offerings, and customization of the provision flow for activating, modifying, or deleting such service
offerings. BAC system provides an OSS interface for flow-through service provisioning, and a GUI for
standalone operation.
BAC includes a CORBA northbound interface for integration with other systems.
For more information on BAC , refer to the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/ccnsc_sp/2_0/index.htm
OL-3348-01 8-3
Accounting
Accounting
The Cisco BTS 10200 EMS is responsible for collecting and generating accounting data for voice
services. Voice service accounting data are presented as Call Detail Records (CDRs), which are sent to
third-party mediation system for transformation to a record format expected by the Service Provider’s
billing system. The external billing system is responsible for rating and generating invoices for billing.
This solution does not include any external mediation or billing systems.
On-net calls include any combination of calls between the local voice network subscribers. Billing for
on-net calls is processed based on Cisco BTS 10200 Softswitch CDR records.
Since the solution has only one Cisco BTS 10200 Softswitch, a call to or from a device managed by a
second Cisco BTS 10200 Softswitch is considered an off-net call.
For on-net to off-net local calls, there are two routing methods supported in the solution:
• Cisco BTS 10200 Softswitch routes calls to FT H.323 network to PSTN. N.B. The H.323 network
consists of gatekeeper and the gateway with PRI or R2 connection to PSTN. Settlement with PSTN
service provider may be required.
For on-net to off-net long distance calls, there are two routing methods supported by the solution:
• The Cisco BTS 10200 Softswitch routes calls to the H.323 network to PSTN, which then routes call
through an IXC service provider. In this case, settlement occurs between the local voice network
service provider and the IXC service provider.
8-4 OL-3348-01
A P P E N D I X A
Glossary
Table A-1 presents definitions for terms used in this document.
Table A-1 Acronyms and Definitions
Term Definition
ACR Anonymous call rejector
ANI Automatic number identification
ATA Analog telephone adaptor
BAC Broadband Access Center for Convergent Network Subscriber Provisioning
BDMS Bulk Data Management System
BML Business Management Layer
BMS Business Management System
B-number DN that a user enters as the forward-to number, also referred to as MN
BPR Broadband Provisioning Registrar
BTS Broadband Telephony Switch
CA Call agent
CDB Call data block
CDD Call Detail Data
CDR Call Detail Record
CFB Call forwarding busy
CFNA Call forwarding no answer
CFU Call forwarding unconditional
CFx Call forwarding features (call forwarding busy, call forwarding no answer, and call
forwarding unconditional)
CIC Cisco Information Center
CIDSD Calling identity delivery and suppression (per call)—delivery part
CIDSS Calling identity delivery and suppression (per call)—suppression part
C-IE CNS Intelligent Engine
CLI Command line interface
CLIP Calling line identification presentation
CLIR Calling line identification restriction
OL-3348-01 A-1
Appendix A Glossary
Table A-1 Acronyms and Definitions (continued)
Term Definition
CNAB Calling name delivery blocking
CNAM Calling name delivery
CND Calling number delivery
CNDB Calling number delivery blocking
C-NOTE Cisco Networking Services (CNS) Notification Engine
CNR Cisco Network Registrar
CoS Class of Service
CPE Customer Premise Equipment
C-PE CNS Performance Engine
CPOL Cisco Patent On-line
CW Call waiting
CWD Call waiting deluxe
DN Directory number
DN Directory Number
DSP Digital Stored Program Control Switch
DTMF Dual Tone Multi-tone Frequency
EML Element Management Layer
EMS Element management system
EPOM Extensible Provisioning and Operations Manager
FCAPS Fault, Configuration, Accounting, Performance, and Security management
functions
FCI Furnish Charging Information
FCP Feature Control Protocol
FE Fast Ethernet
FIM Feature interaction manager in Cisco BTS 10200
FQDN Fully Qualified Domain Name
FS Feature Server
FTP File Transfer Protocol
FXO Foreign Exchange Office
FXS Foreign Exchange Station
GE Gigabit Ethernet
IAD Integrated access device
ITU International Telecommunication Union
IVR Interactive Voice Response
LLQ Low latency queuing
MCF Multiple call forward
MDN Multiple directory number
MDRR Modified Deficit Round Robin
A-2 OL-3348-01
Appendix A Glossary
Term Definition
MDU Multiple Dwelling Unit
MGCP Media Gateway Control Protocol
MLHG Multiline hunt group
MN (See B-number)
MTU Multiple Tenant Unit
NE Network element
NML Network Management Layer
NMS Network management system
NOD Nature of dial
Noun Name of a database table in the Cisco BTS 10200 database
NSE Named Signaling Event
OAM&P Operation, administration, management and provisioning
OCB Outgoing call barring
OSS Operations Support System
PBX Private Branch Exchange
PCPS Per-call presentation status
PNL Programmable Network Layer
POTS Plain old telephone service
PPS Permanent presentation status
PRI Primary Rate Interface
PS Presentation status
PSTN Public switched telephone network
QoS Quality of service
RAS Registration, Admission, and Status Protocol
RTP Real Time Protocol
SDP Session Description Protocol
SML Service Management Layer
SMS Service Management System
SNMP Simple Network Management Protocol
SPCS Stored program controlled switch
Subscriber A customer, who has direct service interface with Flying Tiger network provider.
Subscriber Line A telephone line, which is connected with subscriber CPE
Table A database entity containing customer provisioned data
TMN Telecom Management Network
ToS Type of service
TWC Three way call
TWCD Three way calling deluxe
VAD Voice Activity Detection
OL-3348-01 A-3
Appendix A Glossary
Term Definition
VLAN Virtual LAN
VSC Vertical service code
WAN Wide area network
A-4 OL-3348-01
I N D EX
Cisco 2602 router sample configuration (H.323

A network) 6-27
access layer switch 2-11 Cisco 2611XM router 1-1, 2-9
accounting 8-4 Cisco 2621XM router 1-1, 2-9
acronyms A-1 Cisco 26x1XM router sample configuration 6-21
aggregation 2-7 Cisco 3500 switch 2-11
analog telephone adaptor 1-1 Cisco ATA 186 1-1, 2-7
ANI 7-2 Cisco ATA 186 and ATA 188 analog telephone
adaptors 2-7
announcement and voice mail servers 1-1
Cisco ATA 188 1-1, 2-7, 2-8, 7-1
announcement server 2-11
Cisco ATA 18x sample configuration 6-15
sample configuration 6-23
Cisco BTS 10200 Sofswitch EMS Release 3.2 8-1
announcement server features 4-6
Cisco BTS 10200 Softswitch 1-2, 2-3
bulk data management system 2-6
B call agent 2-4

element management systems 2-6
BDMS 2-6
feature server 2-6
bearer features 4-4
sample configuration 6-2
billing interoperability 7-1
Cisco Catalyst 2950 1-1, 2-7
Broadband Access Center for Convergent Network
Cisco IAD 2421 1-1, 2-7
Subscriber Provisioning v2.5 8-3
integrated access device 2-9
bulk data management system 2-6
interfaces 2-9
QoS features 2-9
C sample configuration 6-17
signaling/control 2-9
call agent 1-2, 2-3
Cisco Information Center Release 3.4.1 8-2
Cisco BTS 10200 Softswitch 1-2, 2-3
Cisco Network Registrar Management Tools 8-2
call progress tones 4-5
Cisco PGW 2200 signaling controller 2-14
canMapAlias field parameter 4-3
codec support 4-4, 4-8
cascading 7-1
Cognitronics CX500 announcement server 2-11
Centrex feature set 4-4
configuration and provisioning 8-2
Cisco 2601 router
CPE 2-7
sample configuration (H.323 network) 6-26
CPE devices 1-2
sample configuration (local voice network) 6-25
Cisco 2611XM 2-7
OL-3348-01 IN-1
Index
Cisco 2621XM 2-7 Cisco 2611XM configuration 6-25

Cisco ATA 186 2-7 Cisco 2621XM router configuration 6-27
Cisco ATA 188 2-7 Cisco 26x1XM configuration 6-21
Cisco IAD 2421 2-7 Cisco BTS 10200 Softswitch configuration 6-2
deployment options 3-1 Cisco IAD 2421 configuration 6-17
sample configurations 6-15 trunking gateway configuration 6-28
customer premises equipment 2-7 Extensible Provisioning and Operations Manager (EPOM)
Release 1.1 8-3
D
F
data features 4-8
failover limitations 7-2
definitions A-1
deployment options fast connect 4-1
Fast Ethernet switch 2-7
voice and data, larger-scale residential or SOHO users,
Cisco IAD 2421 3-3 Cisco Catalyst 2950 2-7
voice and data, small business, Cisco IAD 2421 3-7 fault management 8-1
voice and data, small business with PBX or KTS, Cisco Fax pass-through 1-1, 4-6
26x1XM 3-8
feature limitations 7-1
voice and data, small-scale residential or SOHO users,
feature server 2-6
Cisco ATA 188 3-2
figures
voice only, Cisco ATA 186 or Cisco IAD 2421 3-1
110 punch down block wiring 3-6
DHCP services 2-10
call flow of switchover from voice to fax
DSL links 7-2
passthrough 4-6
DTMF 4-3
functional overview of Cisco BTS Softswitch 2-4
DTMF relay 1-1, 4-3
sample Cisco ATA188 configuration 6-16
support 4-8
sample network 6-2
dual-tone multifrequency 4-3
service provider POP network design 5-2
solution with direct connect to the H.323 long-distance
network 1-3
E
voice and data, Cisco ATA 188 3-3
E1 links 7-2 voice and data, Cisco IAD 2421 and LAN connections to
Cisco Catalyst 2950 3-3
element management systems 1-2
voice only, Cisco ATA 186 3-2
see EMS 2-6
voice only, Cisco IAD 2421 3-2
EMS 1-2
wiring example, multiple POTS lines 3-7
Ethernet/IP infrastructure 2-11
wiring example for one or two POTS lines 3-5
Ethernet hub 3-2
firewalls 7-2
examples
foreign exchange station 1-1
announcement server configuration 6-23
see FXS 2-7
Cisco 2601 router directory gatekeeper
configuration 6-26 FXS 1-1, 2-7
IN-2 OL-3348-01
Index
G M
G.711 Media Gateway Control Protocol 2-5

A-law and U-law codecs 7-1 media servers 2-11
gatekeeper sample configurations 6-25 message waiting indicator 4-4
MGCP 2-5
MGCP-based call control and signaling support 1-2
H
support 2-5
H.225.0 modem over IP 7-1
setup message 4-1
signaling 4-3
N
H.245 signaling 4-3
H.323 2-5 NAT/PAT translation 7-2
features supported by the Cisco BTS10200 NMS 1-2
Softswitch 4-1
gatekeepers 2-12
hairpin 4-2 O
support 2-5
Octet 3a 4-3
H.323 tandeming 4-2
off-net calls 1-2
Hong Kong and China dial plans 1-1
on-net to off-net local calls 8-4
Hong Kong and China tone generation 1-1
on-net to off-net long distance calls 8-4
I
P
interaction between services 4-4
packet marking and port-based queuing on the Cisco ATA
IP infrastructure 2-11 188 4-9
IP Unity Unified Messaging Server 4-7 PBX 2-7
PBX or key telephone service (KTS) interconnect 1-1
PSTN interface 2-13
K
PSTN termination and long distance through the H.323
long-distance network 1-1
key system 2-7
L R
RAS
Long Reach Ethernet 3-1
LRE 3-1
messages 4-2
signaling 4-2
redundancy and fault tolerance 5-1
redundant network design
OL-3348-01 IN-3
Index
service provider POP 5-2

T
RJ-11 connector 1-1
T.38 fax relay 7-1
tables
S solution component network management summary 8-1
sample configuration solution components 2-1
Cisco BTS 10200 Softswitch 6-2 tech prefix-based routing 4-2
sample configurations 6-1 third-party announcement server 2-11
sample network and configurations 6-1 trunking gateway 2-13
service provider POP network elements trunking gateway sample configuration 6-28
5-2
announcement server farm 5-2
V
Cisco BTS 10200 Softswitch call agent, feature server,
and element management system 5-2 VLAN design 3-8
gatekeeper cluster for the Cisco BTS 10200 VLAN security and manageability 3-8
Softswitch 5-2
VoATM 2-9
service provider POP redundant network design 5-2
voice mail
Session Initiation Protocol 2-5
with MGCP and H.323 7-1
signaling protocols 2-5
voice-mail
SIP 2-5, 7-2
features 4-7
SIP-H.323 4-8
voice-mail protocols 2-12
SIP-MGCP 4-8
voice-mail server 2-12
SIP protocol definition 2-5
voice mail server farm
support 2-5, 4-8
voice mail server farm 5-2
solution architecture layers 1-2
voice VLAN support on the Cisco ATA 188 4-9
solution component
VoIP 2-9
functions 2-1
VoIP signaling protocols 2-5
hardware platforms 2-1
H.323 2-5
supported components 2-1
MGCP 2-5
types of components 2-1
SIP 2-5
solution components 2-1
solution component summary 2-1
solution features 4-1 W
solution network management 8-1
wiring 3-4
Spanning Tree Protocol 3-8
wiring plan
STP 3-8
when using the Cisco IAD 2421 with voice and data
supplementary services 4-3
customers 3-4
supplementary services to line subscribers 1-1
wiring for more POTS lines per unit 3-6
wiring for one or two POTS lines per unit 3-4
IN-4 OL-3348-01

Etx10 BK

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Etx10 BK

Enviado por

Direitos autorais:

Formatos disponíveis

Cisco Broadband Local Integrated Services

Solution-ETTX 1.0 Overview and Planning

Text Part Number: OL-3348-01

Document Objectives vii

Document Organization vii

Document Conventions viii

CHAPTER 1 Introduction 1-1

How the Solution Works 1-1

CHAPTER 2 Solution Components 2-1

Solution Component Summary 2-1

H.323 Gatekeepers 2-12

PSTN Interface 2-13

CHAPTER 3 CPE Deployment Options 3-1

CHAPTER 4 Solution Features 4-1

H.323 Features Supported by the Cisco BTS 10200 Softswitch 4-1

Bearer Features 4-4

Voice-Mail Features 4-7

CHAPTER 5 Redundancy and Fault Tolerance 5-1

Redundant Deployment of the Cisco BTS 10200 Softswitch 5-1

Service Provider POP Redundant Network Design 5-2

CHAPTER 6 Sample Network and Configurations 6-1

Cisco BTS 10200 Softswitch Sample Configuration 6-2

CPE Sample Configurations 6-15

Gatekeeper Sample Configurations 6-25

CHAPTER 7 Design Limitations 7-1

Feature Limitations 7-1

Subscriber Features Requiring ANI 7-2

NAT/PAT Translation 7-2

Failover Limitations 7-2

CHAPTER 8 Solution Network Management 8-1

Fault Management 8-1

Configuration and Provisioning 8-2

APPENDIX A Glossary A-1

Table 1 Document Contents

Chapters Title Content

Table 1 Document Contents (continued)

Chapters Title Content

boldface font Commands and keywords are in boldface.

Screen examples use the following conventions:

World Wide Web

Obtaining Technical Assistance

Technical Assistance Center

Cisco TAC Web Site

Cisco TAC Escalation Center

How the Solution Works

Two variations of the solution are illustrated:

Cisco H.323 Cisco SLT

IAD Q.931+/IP F-link

Figure 1-2 Solution Connecting Indirectly to PSTN

Solution Component Summary

Table 2-1 Solution Components

Type of Component Function Supported Component Hardware Platform

Location: Subscriber unit voice ports and 1 Ethernet uplink

Table 2-1 Solution Components (continued)

Type of Component Function Supported Component Hardware Platform

PSTN Interconnect Components

Table 2-1 Solution Components (continued)

Type of Component Function Supported Component Hardware Platform

The Call Agent: Cisco BTS 10200 Softswitch

Cisco BTS 10200 Softswitch Call Agent

Figure 2-1 Functional Overview of Cisco BTS Softswitch

Physical office environment