|
|
This chapter discusses key provisioning issues related to network components other than the gateway (covered in "Configuring a Universal Gateway for Service"), and that are not commonly considered network management applications (covered in "Using Management and Shared Support Services").
 |
Caution Certain features vary from one Cisco IOS release to another, as do configuration requirements. Before configuring a platform, always refer to the latest release notes for the solution. The release notes for the Cisco ASAP Solution are available at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/access/solution/asap/index.htm |
Dial access networks, as they must originate at the edge of the PSTN, must commonly (although not always) support SS7 signaling. Where SS7 signaling is required, the Cisco ASAP Solution relies on the Cisco SS7 Interconnect for Access Gateways Solution, which uses a Cisco SC2200 node. (A Cisco SC2200 node is also used to support SS7 signaling for voice services.)
For details, refer to Cisco SS7 Interconnect for Access Servers Solution Release 2.2 at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel7/soln/das22/index.htm
 |
Note There are special issues that must be taken into account when Cisco RPMS is used with SS7 signaling. Refer to SS7 Resource Groups. |
VoIP networks rely upon the H.323 standard for the transmission of real-time audio, video, and data communications over packet-based networks. Key components of an H.323-based network are the gateways (GWs), gatekeepers (GKs), and directory gatekeepers (DGKs) that signal among themselves using the H.323 RAS (Registration, Admission, and Status Protocol), in order to establish communications paths before bearer traffic is transmitted. Support for SS7 signaling may or may not be required.
|
Note In the case of the Cisco ASAP Solution, which supports both voice and dial services on a single platform, the term universal gateway, or UG, is used where GW would otherwise be used. |
Where SS7 must be supported, the Cisco ASAP Solution relies on the Cisco SS7 Interconnect for Voice Gateways Solution. Refer to Cisco SS7 Interconnect for Voice Gateways Solution, Release 1.3 at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel7/soln/voip13/index.htm
For an overview of the architecture of the Cisco SC2200 node and its components (including the Cisco 2611 SLT), as well as concise configuring and installation information, refer to Chapter 5, "Provisioning SS7-Based POPs," in the Cisco Wholesale Voice Solution Design and Implementation Guide, at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel7/soln/wv_rel1/wvpg/index.htm
The fundamentals of designing and provisioning H.323 networks for VoIP services are well covered in the Cisco Wholesale Voice Solution Design and Implementation Guide, at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel7/soln/wv_rel1/wvpg/index.htm
Chapter 2, "Provisioning the Gatekeeper Core," discusses the gatekeeper core and its components, as well as dial plans and traffic management. The following topics are covered there:
(Also see Chapter 4, "Designing a Solution," in the Cisco ASAP Solution Overview and Planning Guide at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/access/solution/asap/overview/index.htm )
|
Caution Not all CAC features will be available in early releases of the Cisco ASAP Solution. |
Configuring the gatekeeper is straightforward.
|
Caution Applications that are not compliant with T.38 Fax Relay, such as Microsoft NetMeeting, may not work properly unless certain configurations are applied to the dial peer as well as to the gatekeeper. For details, see UG and GK Configuration Requirements for Microsoft NetMeeting with T.38 Fax Relay. |
|
Note Refer to Configuring the Gatekeeper, in Chapter 2, "Provisioning the Gatekeeper Core," of the Cisco
Wholesale Voice Solution Design and Implementation Guide at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel7/soln/wv_rel1/wvpg/index.htm |
Step 2 Enable the Cisco VoIP CAC with RSVP feature. See Call Admission Control and RSVP.
Step 3 Establish a gatekeeper identity, as well as zones, gateway priorities, and a technology prefix.
Depending on the size of the network to be managed, directory gatekeepers and alternate directory gatekeepers may also be required. Configuration examples are presented in Chapter 2, "Provisioning the Gatekeeper Core," of the Cisco Wholesale Voice Solution Design and Implementation Guide at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel7/soln/wv_rel1/wvpg/index.htm
As noted in "Configuring a Universal Gateway for Service," a Cisco RPMS or Cisco AR may be required for accounting and management purposes. See the following sections, respectively:
Posted: Wed Jan 22 02:13:34 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.