Chapter 3: Solution Components

To support the various topologies and applications of the Cisco ASAP Solution, both Cisco and third-party components are required. Some components are required in all topologies. Other components, although optional, are mandatory for certain solutions (such as those requiring SS7 signaling). This chapter lists and discusses the actual components, both Cisco's and those of third parties, that can be used to implement a Cisco ASAP Solution.

Universal Port DSPs and Universal Gateways

At the heart of the solution is the universal port DSP, which defines what are known as universal gateways (UGs). This digital signal processor supports both data and full-featured voice processing. In addition, DSP firmware is assigned dynamically, so that no static preprovisioning of the DSPs is required. This greatly reduces maintenance overhead, particularly in networks with large numbers of subscribers. Table 3-1 lists the voice and data features supported by the universal DSP.

Table 3-1 Voice and Data Features of the Universal DSP
Voice Features	Data Features
Support for industry-leading CODECs: G.711, G.729a, G.723.1	Support for the following formats: V.92, V.44, V.90, V.110, V.120, PIAFS
Support for T.38 fax relay
G.168-compliant echo cancellation, programmable up to 128 msec
Programmable frame size
Generation and detection of DTMF and MF tones

With data and voice now accommodated dynamically, unified dial plans can be used to differentiate services on a call-by-call basis. (For a discussion of dial plans, see Dial Plans and Number Normalization.)

Major Components

Table 3-2 summarizes the major components, all of which are Cisco components. Required components are listed first, followed by optional components.

Note

Refer to the most current Cisco ASAP Solution Release Notes for the latest information regarding IOS versions, other application software, and the platforms they run on.

Table 3-2 Major Components of the Cisco ASAP Solution
Component	Description
Cisco Universal Gateways	Required. Use universal DSP to support both voice and data. Support small- to large-scale interconnects with wholesaler's TDM-based customers. Platforms include the Cisco AS5350 and Cisco AS5400.
Cisco Dial-Only Gateways	Optional. Platforms include the Cisco AS5300, Cisco AS5800, and Cisco AS5850¹.
Cisco H.323 Gatekeepers and Directory Gatekeepers	Required to support VoIP with RAS messaging. Allow voice network to be scaled to large sizes. Platforms include the Cisco 3660 and Cisco 7200.
Cisco Signaling Controllers	Optional. However, these components are required in SS7 interconnect solutions. The supported platform is the Cisco SC2200 running Cisco SS7 Interconnect for Voice Gateways.
Cisco SS7 Signaling Link Termination Systems	Optional. However, these components are required in SS7 interconnect solutions. The platform is currently the Cisco 2611, although other platforms may be available in later releases of the Cisco ASAP Solution.
Cisco L2TP Network Server	Optional. Any L2F/L2TP-compliant tunnel endpoint (home gateway). Provides large-scale L2TP tunnel aggregation. The Cisco 7200 VXR, among other platforms, can provide this service.
Cisco RPMS for Dial Services	Optional. Release 1.1 recommended for dial services. Enables port policy management (PPM) across multiple GWs.
Cisco Catalyst Switches	Optional. Both Cisco Catalyst 5000 and 6000 series switches are used. Cisco recommends Cisco Catalyst 6000 series switches for best VoIP QoS.

¹Initial releases of the Cisco ASAP Solution do not support voice services on the Cisco AS5850.

Cisco Universal Gateways

The Cisco ASAP Solution requires a range of small-, medium-, and large-scale PSTN interconnects with the wholesaler's TDM-based customers (typically IXCs, PTTs, or other wholesalers), depending on anticipated call volumes. Platforms include the Cisco AS5350 and the Cisco AS5400, along with various supporting network modules.

Note

In the context of dial services, the above platforms are most frequently referred to as network access servers, or NASs. In the context of H.323 voice services, these platforms are most frequently referred to as gateways, or GWs. H.323 is currently the only signaling protocol used by the Cisco ASAP Solution for VoIP services. In initial releases of the Cisco ASAP Solution, SIP- and MGCP-based services are not supported.

For the interface modules and signaling types supported by the Cisco UGs, see Table 3-3.

Table 3-3 Cisco Universal Gateways, Interface Modules, and Supported Signaling Types
Platform	Interface Modules	Universal Port Capacity
Cisco AS5350	T1, E1, T3¹	T1/E1: 8 T31 Ports: 216 universal
Cisco AS5400	T1, E1, T3, CT3	T1/E1: 16 PRI (voice) T3² (data) Ports: 384 universal, 648 data

¹Available to reduce provisioning costs, although only 8 T1s can be enabled.

²T1 or T3 configuration.

Note

Currently, the Cisco 2500, Cisco 2600, and Cisco 3600 series routers are not supported by the Cisco ASAP Solution.

Product Literature

For product literature for the universal gateways, including data sheets, refer to the following URLs:

Cisco Dial-Only Gateways

In addition to universal gateways, the Cisco ASAP Solution supports the Cisco AS5300, Cisco AS5800, and Cisco AS5850 for dial-only service.

For the modules and signaling types supported by the Cisco dial GWs, see Table 3-4.

Table 3-4 Cisco Dial-Only Gateways, Interface Modules, and Supported Signaling Types
Platform	Interface Modules	Universal Port Capacity
Cisco AS5300	T1, E1	T1/E1: 8 Ports: 240 dial, 120 voice
Cisco AS5800	T1, E1, T3	T1/E1: 16 PRI (voice) T3¹ (data): 3 Ports: 72 T1/E1, 2047 dial, 1344 voice
Cisco AS5850²	E1, T3	E1: 86 T3: 4 Ports: 2688 dial

¹T1 or T3 configuration.

²Voice (sub-T3) is not supported.

Product Literature

For product literature for the dial-only gateways, including data sheets, refer to the following URLs:

Cisco H.323 Gatekeepers and Directory Gatekeepers

Cisco H.323 GKs and DGKs constitute the gatekeeper core. GKs are mandatory network elements used to scale a wholesale network to large sizes. Directory GKs (DGKs) further supplement network scalability and are mandatory if GK-based carrier interconnect is desired. The Cisco GKs and DGKs supported by the Cisco ASAP Solution are essentially IOS software images loaded onto a dedicated Cisco 3660 or Cisco 7200 series platform. Signaling among H.323 components is through RAS (Registration, Admission, and Status Protocol).

Resource Management

Cisco GKs determine the health of H.323 gateways by monitoring registration and unregistration (RRQ/URQ) messages and resource availability indicators (RAIs).

Call Routing

Cisco GKs provide call routing based on destination E.164 addresses. They may use their knowledge of local GW health levels to make routing decisions in order to increase the network availability of the GWs. Cisco GKs may also route calls between remote GKs within the same administrative domain by means of inter-GK LRQ (location request) RAS messages. Similarly, Cisco DGKs may also route calls to other carrier administrative domains by means of LRQ RAS messages.

Security

Cisco GKs, in conjunction with an external server (such as RADIUS), may be used for secure call admission in intradomain call scenarios (calls within the same service provider's domain). Cisco GKs also have limited applications in implementing interdomain security functions for calls sent between carriers by means of IP interconnect.

External GKTMP Applications

Cisco GKs may act as a control point from which an application server can affect call routing, number translation, call admission/blocking, and the like. These application servers interface with a Cisco GK or DGK by means of GKTMP (Gatekeeper Transaction Message Protocol).

Note

The Cisco ASAP Solution does not specify any particular GKTMP application, but does not exclude any from being used.

CDR Generation

Cisco GKs have limited abilities to generate CDR reports for calls either in addition to or instead of generating them from the GW. This is an option if the wholesaler either does not own the GWs at a point of presence (POP), or simply wants to reduce the amount of messaging overhead associated with AAA in its smaller POPs. However, billing in this manner has limitations.

Cisco Signaling Controllers

These optional components are used in SS7 interconnect solutions. The supported platform is the Cisco SC2200 running Cisco SS7 Interconnect for Voice Gateways.

Note

Refer to Cisco ASAP Solution Release Notes for the software versions that are required.

Cisco SS7 Signaling Link Termination Systems

These optional components are used in SS7 interconnect solutions (where they are required). Signaling link termination (SLT) systems are Cisco 2611 platforms that are capable of terminating MTP1 and MTP2 SS7 layers and backhauling MTP3 and higher SS7 layers to the Cisco SC2200 in an SS7 interconnect application.

Cisco SLTs can be either colocated or located remotely with respect to the Cisco SC2200 hardware platform. However, with remote location, there are latency and loss requirements that must be met.

Cisco L2TP Network Server

L2TP (Layer 2 Tunneling Protocol) is the emerging IETF standard for Layer 2 tunneling (or building access Virtual Private Networks, or VPNs); it is compatible with the earlier L2F protocol. An extension of PPP, L2TP handles the server side of the L2TP protocol. The L2TP network server (LNS) is the initiator of outgoing calls and the receiver of incoming calls.

Traditional dial-up networking services support only registered IP addresses, which limits the types of applications that can be implemented over VPNs. L2TP supports multiple protocols and both unregistered and privately administered IP addresses over the Internet.

An LNS, also known as a home gateway, operates on any platform capable of PPP termination. The Cisco ASAP Solution can use, for example, the Cisco 7200 VXR broadband services aggregators as an LNS, to terminate VPDN tunnels for dial services. The total number of tunnels determines the maximum number of sessions a single LNS can handle. A single Cisco 7200 VXR can accommodate 1000 tunnels, and up to 8 sessions within each tunnel, for a total of 8000 sessions. User information can be stored locally, but it is most frequently stored on an AAA server.

Note

The Cisco 7200 VXR is not required. Cisco AS5400 and Cisco 6400 platforms can also perform this function, as can third-party equipment.

For more information about the platform, refer to Cisco 7200 VXR at the following URL:

For more information about LNS and VPDN, refer to Layer 2 Tunnel Protocol at the following URL:

Cisco RPMS for Dial Services

To enable port policy management for dial services across multiple GWs, a Cisco RPMS may be required. This makes it possible to model customers, services, and regions according to DNIS, trunk, or GW.

Cisco Catalyst Switches

Cisco Catalyst switches running ISL trunking are optional but useful adjuncts to traffic management in the Cisco ASAP Solution. Both Cisco Catalyst 5000 and 6000 series are used. For more information, refer to Multilayer LAN Switches at the following URL:

Note

Cisco recommends Cisco Catalyst 6000 series switches for best VoIP QoS.

Additional Components (for Management and Shared Services)

This section discusses the additional components, both Cisco's and those of third parties, that support shared services such as management and billing. Table 3-5 summarizes these components, which are provided by third parties.

Table 3-5 Additional Components of the Cisco ASAP Solution
Component	Description
Management Systems	Traffic and Network Management Systems •Cisco Resource Pool Management (RPM) and Cisco Resource Pool Management Server (RPMS) provide aggregation and allocation of dial resources. •Cisco Info Center (CIC) supports fault management and event correlation. •Cisco Internet Performance Manager (IPM) monitors performance of SP networks, with emphasis on QoS for VoIP. Element Management Systems •Cisco Universal Gateway Manager (UGM) helps manage access GWs. •Cisco Voice Manager (CVM) supports VoIP configuration and dial plan provisioning. •Cisco MGC Node Manager (CMNM) provides a CORBA-based fault, configuration, accounting, and performance management system (FCAPS). •Cisco Voice Services Provisioning Tool (VSPT) provides configuration and provisioning.
RADIUS-Based Platforms	•Cisco Access Registrar (an access policy server and proxy server for multiple services) •AAA database servers •RADIUS-based prepaid calling servers •RADIUS proxy servers
Billing Systems	Partition billing among SPs for voice and other services (typically are AAA/RADIUS based). The Cisco Billing and Measurements Server (BAMS) can also be used.
Unified Communications Application Server	Supports unified messaging.
TFTP Prompt Server	Maintains prompt database for GWs using interactive voice response.
NTP Time Server	Provides accurate timing across the network. Essential for billing and proper troubleshooting.

Management Systems

Resource and Network Management Systems

The Cisco ASAP Solution can take advantage of a variety of resource management systems, such as those that deal with port policy.

Network management systems (NMSs) are also optional components that are used for network monitoring, fault management, trap correlation, and reporting. Any NMS can extract this information from wholesale components through a variety of methods, such as SNMP, syslog, and AAA.

The following resource and network management systems can be used in the Cisco ASAP Solution:

Cisco Resource Pool Manager Server

Eliminating contention by controlling access to ports is critical to dial services. (Support is not yet provided for eliminating contention on voice ports.) The Cisco RPM (resource pool management) feature enables wholesalers to aggregate their dial resources across multipleUGs, and allocate subsets of these resources to retail ISPs. Cisco RPM allows providers to count, control, and manage dial resources, while also accounting for shared resources when different SLAs are implemented. RPM can be achieved by using the RPM component of the resource pooling solution on the UG itself, or by using that component in conjunction with one or more external Cisco RPMSs.

For more information about RPM, refer to Resource Pool Management at the following URL:

In a Cisco ASAP network, Cisco RPMS enables PPM across multiple UGs, and models customers, services, and regions according to DNIS, trunk, or GW. Cisco RPMS provides support for L2F/L2TP tunnel definition (VPDN access) and tunnel policy management for dial calls.

Note

In initial releases of the Cisco ASAP Solution, Cisco RPMS 1.1 is supported for tunnel policy management to provide PPM for dial services only. This includes preauthorization and the ability to configure Cisco RPMS to provide VPDN tunnel definition and policy management.

Resource pool management can be configured in a single, stand-alone UG. However, for reasons of scale, Cisco recommends that Cisco ASAP Solution implementations take advantage of a Cisco RPMS (RPMS 1.1 or later).

For more information about Cisco RPMS 1.1, refer to Cisco Resource Pool Manager Server 1.1 at the following URL:

Cisco Info Center

Cisco Info Center (CIC) is member of the CiscoWorks2000 family. CIC provides a variety of features with respect to fault management and event correlation.

Cisco Internet Performance Manager

Cisco Internet Performance Manager (IPM) is a performance management application that can monitor the performance of a service provider's network, with special application for voice. Cisco IPM provides a variety of features related to VoIP network performance.

Element Management Systems

Element management systems (EMSs) are optional components that are used for managing or provisioning other components in the solution.

The following element management systems may be used in the Cisco ASAP Solution:

Cisco Universal Gateway Manager

The Cisco Universal Gateway Manager (UGM) is an element management system for Cisco UGs. (The Cisco AS5300 is not supported.) Running on a Sun Solaris platform, Cisco UGM provides comprehensive FCAPS (Fault, Configuration, Accounting/Inventory, Performance, and Security) capabilities, for the configuration, management, and maintenance of dial networks. Cisco UGM accesses standards-based information through SNMP (Simple Network Management Protocol), Telnet, and FTP/TFTP.

Cisco Voice Manager

CiscoWorks2000 Voice Manager (CVM) is a web-based management and reporting application for Cisco UGs and GKs. CVM provides basic service provisioning (dial plan management) in voice applications, and integrates with third-party reporting tools for distributed reporting.

Note

Cisco CVM with Telemate provides limited provisioning support, and is not well-suited to large-scale service provider deployments. Applications from other vendors may work with CVM to provide more capability. CVM 2.0.2 is the only release currently supported.

Cisco MGC Node Manager

Cisco Media Gateway Controller Node Manager (CMNM) is an element management system for the Cisco SC2200 node. CMNM provides a single interface for fault, configuration, and performance management for all network elements within the node.

Cisco Voice Services Provisioning Tool

Cisco Voice Services Provisioning Tool (VSPT) is a GUI-based tool for provisioning the Cisco SC2200 (Sun Netra) hardware platform. VSPT can bulk load and import provisioning information, and supports incremental provisioning. It can also generate provisioning command scripts, and can be launched directly from CMNM.

RADIUS-Based Platforms

A variety of platforms that use the RADIUS (Remote Authentication Dial-In User Service) protocol are available to support the Cisco ASAP Solution for dial and voice services. This includes authentication, authorization, and accounting (AAA).

•

For dial services, the server maintains end-user (subscriber) information, such as user name and password.

•

For (prepaid) voice services, the server maintains end-user information such as credit card number and PIN, in addition to a real-time subscriber rating engine.

In addition, a RADIUS AAA server can be used simply as a place to receive and maintain CDRs (call detail records) from the GWs.

Cisco Access Registrar

Cisco Access Registrar (AR) is a RADIUS-compliant access policy server (and proxy server) designed to support the delivery of dial, VoIP, ISDN, and wireless, among other services. Based on Sun Solaris, Cisco AR helps service providers deploy access services by centralizing AAA information while simplifying provisioning and management. AAA RADIUS servers are used, for example, in card services to validate end users on the basis of called number or username and password combination. The AAA interaction occurs directly on the GW.

Version 1.6, recommended for use with the Cisco ASAP Solution, provides policy enforcement support, configuration replication for multiserver deployments, and a number of additional features to simplify administration and troubleshooting.

The Cisco ASAP Solution can use Cisco AR in wholesale dial services as an AAA server or proxy server, or to provide VPDN tunnel definition (without the use of L2TP tunneling) for dial-in data connections.

•

Authentication of users stored in an LDAP (Lightweight Directory Access Protocol) directory

•

Proxy RADIUS for support of wholesale dial, remote access outsourcing, and global roaming applications

•

Integration with third-party provisioning, billing, management, and operational systems of the service provider's choice

RADIUS Proxy Server

When a RADIUS proxy server is used in the wholesale SPs network, the DNIS can be used to authenticate users to one retail ISP or another. This provides a variety of benefits:

•

The retail ISP maintains the subscriber relationship, authenticating its own users and assigning its own IP addresses.

•

Authorization criteria are maintained in a central server, simplifying operations and facilitating scaling.

Billing Systems

For a discussion of billing, refer to Understanding and Provisioning AAA Billing, and Establishing Billing Systems for Calling Card Services, in Chapter 3, "Provisioning Shared Support Services," of the Cisco Wholesale Voice Solution Design and Implementation Guide.

For a discussion of back-to-back gateways, refer to Back-to-Back GW in Chapter 2, "Solution Architecture," of the Cisco Wholesale Voice Solution Overview.

In addition, the Cisco Billing and Measurements Server (BAMS) can be used. Refer to Billing and Measurements Server Phase 2 at the following URL:

Unified Communications Application Server

Unified communications (UC) servers support unified messaging—the convergence of voice mail, e-mail, and fax. UC servers allow a subscriber to take advantage of store-and-forward delivery, whereby a message recipient has the option of retrieving a message by means of phone, email, or fax at a convenient time. Open Packet Telephony (OPT) architecture is the cornerstone of unified communications.

TFTP Prompt Server

A prompt server is an optional component that maintains a prompt database for UGs running IVR functionality for applications such as card services. If they are not too big, prompt databases may be stored locally on the UG in flash memory. Larger prompt databases, such as those needed when there are many branded retailers or when many languages must be supported, may be downloaded dynamically as needed from a TFTP prompt server. TFTP servers are generic third-party devices that can be hosted on a wide variety of platforms.

TFTP servers are used to store a variety of files that do not need to reside on a local machine, and that would otherwise take up available limited memory on that machine. These files can be downloaded as needed. Example files include audio (IVR) files, IOS files, and configuration files (including dial peers).

NTP Time Server

Single-source timing is essential in synchronizing timing across multiple time zones. This is especially true where Cisco RPMS, billing applications, and other services are involved. Network Time Protocol (NTP) servers are a recommended source of high-quality timing. NTP provides a common time base for networked routers, servers, and other devices. Synchronized timing enables one to correlate syslog and Cisco IOS debug output to specific events. An NTP-enabled network usually gets its time from an authoritative time source. A Cisco router can provide this function, but more critical timing may require a device such as an atomic clock attached to a time server. NTP then distributes the timing across the network.

Table Of Contents

Solution Components

Universal Port DSPs and Universal Gateways

Major Components

Cisco Universal Gateways

Product Literature

Cisco Dial-Only Gateways

Product Literature

Cisco H.323 Gatekeepers and Directory Gatekeepers

Resource Management

Call Routing

Security

External GKTMP Applications

CDR Generation

Cisco Signaling Controllers

Cisco SS7 Signaling Link Termination Systems

Cisco L2TP Network Server

Cisco RPMS for Dial Services

Cisco Catalyst Switches

Additional Components (for Management and Shared Services)

Management Systems

Resource and Network Management Systems

Cisco Resource Pool Manager Server

Cisco Info Center

Cisco Internet Performance Manager

Element Management Systems

Cisco Universal Gateway Manager

Cisco Voice Manager

Cisco MGC Node Manager

Cisco Voice Services Provisioning Tool

RADIUS-Based Platforms

Cisco Access Registrar

RADIUS Proxy Server

Billing Systems

Unified Communications Application Server

TFTP Prompt Server

NTP Time Server