Learn to design dialing plans utilizing VoIP features from Avaya CS 1000 7.x systems.
Voice Over IP (VoIP) technology is an integral part of a cost-effective and practical solution for many customers, because it allows secure communications using industry standards, such as H.323 and SIP signaling, over geographically disbursed IP data networks. In this course, you will learn about Avaya Communications Server (CS) 1000 dialing plan design and configuration requirements for the Call Server, associated H.323 and SIP Gateways on the Signaling Servers, and the centralized management of an IP Peer Dialing plan using Network Routing Servers.
What You'll Learn
- CS 1000 IP Peer Networking features and capabilities
Configuring Avaya CS 1000 Call Server to support IP Peer Networking
Configuring the Virtual Trunk Gateways (H.323 and SIP) to support IP Peer
Using Network Routing Service Manager to configure and manage Network
Routing Service for IP Peer Networking
Configuring the Avaya CS 1000 Call Server and IP Phones to support IP
Peer Networking (Zone-based Dialing Deployment)
Validating Call Server, Signaling Server, and Network Routing Service
Configuring the CS 1000 VoIP Emergency Services Assess (ESA)
Who Needs to Attend
Personnel responsible for implementing an IP Peer Network solution for a network including multiple Avaya Communication Server 1000 systems
- Avaya Communication Server 1000 Familiarization Release 7.x (0200)
- Avaya Communication Server (CS) 1000 7.x System Administration and Management (6351)
There are no follow-ons for this course.
Certification Programs and Certificate Tracks
This course is part of the following programs or tracks:
- Avaya Certified Support Specialist (ACSS) - Avaya Communication Server 1000 for Avaya Aura�
1. Avaya CS 1000 IP Peer Networking Overview
2. Configure Avaya CS 1000 Call Server for Distributed Deployment Model
3. Configure Avaya CS 1000 SIP Gateway
4. Configure Avaya CS 1000 H.323 Gateway
5. Configure Network Routing Service
6. Emergency Service Access
7. Zone-Based Dialing
Lab 1: Log in to element manager and configure the CS 1000 Call server for
IP peer networking.
Lab 2: Enable the ISDN feature for this customer.
Lab 3: Add a virtual D-channel.
Lab 4: Add an IP telephony node or change the existing node to include LTPS,
H.323 and SIP gateway functionality.
Lab 5: Define VGW codecs.
Lab 6: Configure a bandwidth zone for virtual trunks.
Lab 7: Add SIP virtual routes for the existing customer.
Lab 8: Add SIP virtual trunks for the existing customer (optional to add
H.323 virtual routes and trunks if there will still be an NRS for the customer).
Lab 9: Configure an ESN data block for the customer for routing control.
Define CDP and limits for the lists and tables that are required.
Lab 10: Define an NCTL data block for the customer.
Lab 11: Create Route List Blocks and point them to the virtual SIP routes
that were built.
Lab 12: Log in to session manager and configure a SIP domain, locations for
your CS 1000 systems, adaptations for the CS 1000 systems, SIP entities,
SIP entity links and routing policies, required dial patterns for the CS
Lab 13: Putty into session manager via the IP address and set up a trace.
Lab 14: Make test calls through session manager.
Lab 15: Configure ESA service parameters for the customer.
Lab 16: Build an ESA data block.
Lab 17: Add an emergency services directory number (ESDN).
Lab 18: Modify numbering plan zone for ESA.
Lab 19: Add an emergency response location (ERL).
Lab 20: Verify configuration by making an emergency test call.
Lab 21: Set up zone based dialing (ZBD) for the customer. Make sure
the ZBD package is equipped.
Lab 22: Enable ZBD and speed call/pretranslation for the customer.
Lab 23: Build a speed call list for pretranslation - Configure it and
Lab 24: Enable numbering zones in the IP telepohony node and configure a
numbering zone for the customer.
Lab 25: Adjust Dialing and Numbering Plan configuration as required.
Lab 26: Configure the ZBD flexible numbering plan and set up phones to
Lab 27: Configure H.323 routes and trunks for the customer and NRS
programming to support H.323 call routing (optional).