This appendix contains several checklists to help you and the IP Telephony (IPT) deployment team collect and check all the preliminary customer information before deploying IP Phones, switches, gateways, and other IPT components. To obtain the answers to this questionnaire, you can take this questionnaire to the site where you are deploying IPT, or you can ask the customer to complete it. Completing this checklist ensures that all the prerequisite steps are completed before you start the deployment of IPT components.
This section contains checks to ensure that the following high-level preimplementation tasks are completed before you start deploying the IPT solution:
Project plan
Site information
Implementation team
The project manager who is assigned to the deployment project develops the project plan for implementing the IPT solution. You should contact the project manager to obtain the project plan and ensure that, at minimum, the high-level tasks listed in Table H-1 are included in the project plan.
Table H-1. Project Plan Tasks Verification
No. | Task Category | Included in the Project Plan? |
|---|---|---|
1 | Preimplementation preparations: procure all required equipment, establish the right contacts, and so on. | □ Yes □ No |
2 | Site survey tasks: check the readiness of the site | □Yes □ No |
3 | IPT implementation procedure: actual implementation of IPT components | □ Yes □ No |
4 | IPT add-on feature implementation: complete the implementation of additional applications such as AutoAttendant, Unity, and features in CallManager such as extension mobility and IP Manager Assistant (IPMA) | □ Yes □ No |
5 | Acceptance tests: test-case scenarios that need to be successfully executed on the deployed solution | □ Yes □ No |
6 | Post-implementation documentation: document the network topology and configurations | □ Yes □No |
7 | Customer acceptance: sign-off process in which the customer acknowledges project completion | □ Yes □ No |
Collecting the site information ahead of time helps you to obtain the necessary permissions for the implementation staff to enter the buildings within the sites beforehand (see Table H-2). In addition, if the deployment involves multiple sites, the project manager can plan for the additional remote resources required to perform the implementation at these sites.
Table H-2. Site Information
No. | Question | Answer |
|---|---|---|
1 | What is the company name? | Company name: |
2 | What is the site address? | Street: City: State: Country: Zip code: Phone: Fax: |
3 | Is building access approval required? | □ Yes □ No |
4 | Does everyone in the deployment team have access to the building and the server rooms? | □ Yes □ No |
5 | What are the normal hours of operation in the building? | Working hours: |
6 | Are any special access permissions required to work after hours? | □ Yes □ No |
7 | Who is the site coordinator contact? | Name: Work phone: Cell phone: E-mail: Pager: |
8 | Which room is designated for the equipment staging? | Room location: |
9 | Does the project team have an office space in which to work, equipped with office supplies, printers, and network connectivity at all the site locations? | □ Yes □ No |
An implementation team is the key to the successful deployment of the IPT network. Table H-3 lists the team members required for the implementation.
Table H-3. Implementation Team
No. | Team Member | Answer |
|---|---|---|
1 | Project manager | Name: Work phone: Cell phone: E-mail: Pager: |
2 | Project engineer(s) | Name: Work phone: Cell phone: E-mail: Pager: Name: Work phone: Cell phone: E-mail: Pager: |
3 | IPT design engineer(s) | Name: Work phone: Cell phone: E-mail: Pager: Name: Work phone: Cell phone: E-mail: Pager: |
4 | IPT implementation engineer | Name: Work phone: Cell phone: E-mail: Pager: |
The implementation readiness analysis includes four categories:
Site readiness
Voice network readiness
Data network readiness
IPT readiness
The following sections cover the checks required for each category before proceeding with the IPT deployment.
The site readiness analysis includes the checks to ensure that all the information is available to begin deploying the IPT endpoints (see Table H-4). The site readiness analysis includes tasks to do the following:
Identify equipment placement and termination points
Ensure that rack space is available to mount the equipment
Ensure that necessary cables and connectors are available
Check the power availability and stable environmental conditions
Table H-4. Site Readiness Analysis Checklist
No. | Question | Answer |
|---|---|---|
I. Equipment Placement and Termination | ||
1 | Do you have all the network topology diagrams available? | □ Yes □ No Attach list. |
2 | Do you have a list of termination points for the IP Phones available? Get a list of the buildings and .oors where IP Phones need to be deployed. | □ Yes □ No Attach list. |
3 | Do you have a list of termination points for the voice gateways? | □ Yes □ No Attach list. |
4 | What is the contact information for the local telephone company for each site? | Name of carrier: Contact phone: Phone number: E-mail: Contract number to be supplied when reporting problems: |
5 | Do you have a list of IP addressing/VLAN assignment information? | □ Yes □ No Attach list. |
II. Rack Space RequirementsYou should make sure that all IPT components have required rack space available for the installation. The rack space requirement varies depending on the type of server, switch, or router. You should obtain the number of rack units required to mount each hardware device. Refer to the vendors’ product documentation to obtain this information. | ||
1 | Do you have enough rack space to rack mount the CallManager servers? | □ Yes □ No Number of servers: Rack space units required per server: |
2 | Do you have enough rack space to rack mount the Unity servers? | □ Yes □ No Number of servers: Rack space units required per server: |
3 | Do you have enough rack space to rack mount the Unity Bridge servers? | □ Yes □ No Number of servers: Rack space units required per server: |
4 | Do you have enough rack space to rack mount the voice gateways? | □ Yes □ No Number of gateways: Rack space units required per gateway: |
5 | Do you have enough rack space to rack mount the gatekeeper? | □ Yes □ No Number of gatekeepers: Rack space units required per gatekeeper: |
6 | Do you have enough rack space to rack mount the application servers? | □ Yes □ No Number of application servers: Rack space units required per application server: |
III. Cabling and Termination PointsDifferent types of cables are required for implementing the IPT network in different parts of the network. | ||
1 | What type of cabling is used within the LAN? | □ Cat 3 □ Cat 5 |
2 | What are the T1/E1 line terminations for connecting the voice circuits? | Site: Building: Floor: |
3 | What are the locations of analog line terminations? | Site: Building: Floor: |
4 | Is distance between the telco termination and the voice gateway in acceptable range? | □ Yes □No Distance in feet: |
IV. Power and HVAC Requirements | ||
1 | Are the power requirements met, as evaluated in the planning phase? Power calculator: http://www.cisco.com/go/powercalculator | □ Yes □No |
2 | Can HVAC systems take the additional load of the equipment? | □ Yes □ No |
3 | Does the site have proper grounding for the equipment? | □Yes □ No |
The voice network readiness analysis includes checks to ensure that the customer has taken all the necessary steps required to integrate, if required, the newly deployed IPT system with legacy PBX, voice-mail, and Automated Call Distribution (ACD) systems. See Table H-5.
Table H-5. Voice Network Readiness Analysis Checklist
Question | Answer | |
|---|---|---|
I. Voice Circuit Analysis | ||
1 | Is the interfacing equipment required for integration of PBX, voice-mail, and ACD systems with CallManager available? | □Yes □No |
2 | Do the software versions that run on the PBX, voice mail, and other equipment requiring integration support CallManager? | □Yes □No |
3 | If moving the PSTN circuits from the PBX to the IPT system, does a different telco interface need to be requested? | □Yes □No |
4 | Who are the contacts for the PBX, voice-mail, and ACD systems? You might have to obtain a list of additional contacts, depending on need. This staff should have access rights to make congigurations changes. | PBX system contact name: Work phone: E-mail: Cell phone: Voice mail system contact name: Work phone: E-mail: Cell phone: ACD system contact name: Work phone: E-mail: Cell phone: |
5 | Did you place the order with the telco to terminate the new voice circuits? | □Yes □No |
6 | If you plan to migrate users from the PBX system to the IPT system, have you grouped the identified users? | □Yes □No |
The data network readiness analysis includes checks to ensure that the customer data network is ready to carry the voice traffic (see Table H-6). In this analysis, you check whether the customer has followed your recommendations to .ll the gaps in the infrastructure that were identified during the planning phase.
Table H-6. Data Network Readiness Analysis Checklist
Question | Answer | |
|---|---|---|
I. LAN Analysis | ||
1 | Are the switch ports on the LAN switches enabled? Are required QoS configurations—such as auxiliary VLAN, port trusts, speed/duplex, inline power, and recommended software versions—completed to connect the IP Phones, servers, and voice gateways? | □ Yes □ No □ Yes □ No |
2 | Is the DHCP server configured with all the scopes, correct default gateways, DHCP option 150 or 66, and DNS values? | □ Yes □ No |
3 | Is the IP helper address configuration that was completed on the routed interface pointing to the right DHCP server for each IP Phone VLAN segment? | □ Yes □ No |
4 | Did you provide the list of server names and IP addresses to the administrators of the DNS servers? This is required so that DNS servers can resolve the names of the voice servers properly. It is always better to do this in advance because the DNS replication process takes a few hours to replicate the information to all the servers in the network. | □ Yes □ No |
II. WAN Analysis | ||
1 | Are the WAN routers running the right Cisco IOS software to support the required QoS feature set? | □ Yes □ No |
2 | Is the configuration on the WAN routers in accordance with QoS recommendations to transport the voice traffic in the priority queue? | □ Yes □ No |
3 | If a gatekeeper is required for CAC, is it rack mounted, loaded with the right Cisco IOS software, and configured? | □ Yes □ No |
4 | Do the WAN routers have sufficient DRAM? | □ Yes □ No |
5 | Are the route-trip delay times between the central and branch sites within the acceptable range to achieve good quality on voice calls? | □ Yes □ No |
The IPT readiness analysis is intended to ensure that the detailed design tasks such as call-processing design, dial plan design, and decisions on the software versions to be deployed in the network are completed and all the necessary software and licenses are available. See Table H-7.
Table H-7. IPT Readiness Analysis Checklist
Question | Answer | |
|---|---|---|
I. IPT Readiness Analysis | ||
1 | Have you completed a detailed design for call-processing servers, dial plan, gateway selection, and sizing ? | □ Yes □ No |
2 | If you are deploying Cisco Unity, do you have a detailed design to deploy? | □ Yes □ No |
3 | Have you completed the design of the CRS/IPCC Express servers and other application servers? | □ Yes □ No |
4 | Have you completed the design of IPT features, such as AutoAttendant, IVR, Web Dialer, SoftPhone, Cisco IP Communicator, IPMA, and Extension Mobility? | □ Yes □ No |
5 | Do you have all the servers rack mounted and ready to start the installation of the software? | □ Yes □ No |
6 | Do you have all the available software disks and licenses? | □ Yes □ No |
7 | Do you have information on all the latest operating system service releases that need to be applied to servers? | □ Yes □ No |
Use Table H-8 to list the name and role of each server and where to connect the servers in the network.
Table H-8. Summary of Servers in the Network
Server Name | Role | Location of ServersSite/Building/Floor | Connected to Switch Name/Slot/Port/VLAN ID |
|---|---|---|---|
CCMSJPUB | CallManager publisher | ||
CCMSJSUB1 | CallManager subscriber 1 | ||
CCMSJSUB2 | CallManager subscriber 2 | ||
CRASJ1 | CRA primary server | ||
CRASJ2 | CRA backup server | ||
UNITYSJ1 | Unity primary server | ||
UNITYSJ2 | Unity backup server | ||
IPSVCSSJ1 | IPT services server | ||
TFTPDHCPSJ | TFTP and DHCP server |
Table H-9 lists the basic information you need to have while installing the basic operating system on any Cisco Architecture for Voice, Video and Integrated Data (AVVID) application servers.
Table H-9. Server OS Installation Configuration Parameters
No. | Configuration | Input |
|---|---|---|
1 | Cisco product key | |
2 | Username (this is just for registration) | |
3 | Name of the organization | |
4 | Computer name Changing the server name is not possible after CallManager installation. Choose a descriptive name that makes it easier to identify the server by role; for example, CCMSJPUB, CCMSJSUB1. | |
5 | DNS domain suffix | |
6 | Workgroup | |
7 | Current time zone, date, and time | Time zone: Date: Time: |
8 | TCP/IP properties (do not use DHCP for server IP addressing) | IP address |
Subnet mask | ||
Default gateway | ||
9 | DNS servers (optional) | DNS server 1 |
DNS server 2 | ||
10 | WINS servers (optional) | WINS server 1 |
WINS server 2 | ||
11 | LMHOST information | |
12 | Administrator password | |
13 | NIC configuration
Speed/duplex settings Check the settings that are configured on the switch port and match them accordingly. | □ Auto/Auto □ 10 Mbps/FULL □ 100 Mbps/FULL |
Table H-10 lists the information required to install the CallManager servers after you have completed the basic OS installation configurations specified in Table H-9.
Table H-10. CallManager Installation Parameters
No. | Configuration | Input |
|---|---|---|
1 | Server type | □ Publisher □ Subscriber |
2 | Backup server type | □Backup server □ Backup target |
3 | Password phraseThe password phrase is used to generate the passwords for the other service accounts. | |
4 | DC directory administrator password | |
5 | Administrator password |
Table H-11 organizes the acceptance tests into the following categories:
CallManager check
General IP Phone and feature tests
Centralized call processing with remote branches
Distributed call processing with multiple CallManager clusters
Advanced IPT tests
You might have to add more test cases depending on the complexity and types of integrations involved in your network. In addition, you should perform the tests outlined in Table H-11 after every upgrade on the CallManager and any other application servers to ensure that the system is functioning properly and that nothing ceased to function because of the upgrade.
Table H-11. IPT Implementation Acceptance Tests
Test Category: CallManager Check | ||
|---|---|---|
No. | Test Case | How to Perform |
1 | CallManager service status | Use the Real-Time Monitoring Tool (RTMT) to check whether all the services are up and running. |
2 | CallManager configuration | Check that the dial plan is configured according to the design. |
3 | CallManager device default configuration | Check whether the IP Phones and gateways are loaded with the right loads. |
4 | CallManager gateway | Place outgoing and incoming calls and verify that call routing is successful. |
5 | CallManager voice-mail integration | Access the voice-mail system and verify that it recognizes the IP Phone extensions. Leave a voice mail and check whether the MWI light comes up. Listen to the new voice mails and ensure that the MWI is off. |
6 | Class of Restriction (CoR) | Configure the IP Phones with different Calling Search Spaces based on their CoR category. For example, the CoR category is the lobby phone, employee phone, executive phone, and so forth. Make test calls from each IP Phone and verify that users can make permitted calls and that all other calls are denied. |
Test Category: General IP Phone and Feature Tests | ||
1 | Basic IP Phone | Make a phone call from IP Phone A to IP Phone B and ensure that two-way audio is established. |
2 | Call on-hold and retrieval | Press the Hold softkey on IP Phone A during the call and verify that the IP Phone user at IP Phone B is on hold. If Music on Hold (MoH) is configured, verify that the party on hold (IP Phone B user) hears the music. If MoH is not configured, verify that the user on hold hears beeps. |
3 | Call park | Make a phone call from IP Phone A to IP Phone B. Park the call at a different number and try to retrieve the call by dialing the call park number. |
4 | Group pickup | Make a phone call from IP Phone A to IP Phone B and pick up the call from IP Phone C by dialing the group pickup number. |
5 | Call transfer to an off-net IP Phone | Make a phone call from IP Phone A to IP Phone B and answer the call. Press the Transfer softkey on IP Phone B, dial an external PSTN phone number, and verify that the call is established between IP Phone A and the PSTN phone. |
6 | Call transfer to an on-net IP Phone | Make a phone call from IP Phone A to IP Phone B and answer the call. Press the Transfer softkey on IP Phone B and dial IP Phone C. Verify that the call is established between IP Phone A and IP Phone C. |
7 | Call forward to an off-net IP Phone | From IP Phone A, press the CFwdALL softkey and enter a PSTN number. Make a phone call from IP Phone B to IP Phone A and verify that the call is forwarded to the PSTN number. |
8 | Call forward to an on-net IP Phone | From IP Phone A, press the CFwdALL softkey and enter the phone number of IP Phone C. Make a phone call from IP Phone B to IP Phone A and verify that the call is forwarded to IP Phone C. |
9 | Ad Hoc conference | Make a phone call from IP Phone A to IP Phone B and answer the call. Press the Confrn softkey on IP Phone A and dial the extension of IP Phone C. Answer the call at IP Phone C. Press the Confrn softkey on IP Phone A to set up the Ad Hoc conference between all three IP Phones. Verify that all three phone users can hear each other. |
Test Category: Centralized Call Processing | ||
1 | Phone-to-phone dial-up to a remote site | Make a phone call from IP Phone A at the central site to IP Phone X at the branch site and verify that two-way audio is established. Also during the call, press the i button twice on the Cisco IP Phone and check that the phones are using the configured codec. |
2 | Call transfer to an IP Phone in a remote site | Make a phone call from IP Phone A to IP Phone B and answer the call. Press the Transfer softkey on IP Phone A and dial the extension of IP Phone X at the remote site. Verify that the call is established between IP Phone A and IP Phone X. |
3 | Call forward to an IP Phone in a remote site | From IP Phone A, press the CFwdALL softkey and enter the phone number of IP Phone X at the remote site. Make a phone call from IP Phone B to IP Phone A and verify that the call is forwarded to IP Phone X. |
4 | Ad Hoc conference over WAN link | Make a phone call from IP Phone A to IP Phone B and answer the call. Press the Confrn softkey on IP Phone A and dial the extension of IP Phone X at the remote branch. Answer the call at IP Phone X. Press the Confrn softkey on IP Phone A to set up Ad Hoc Conferencing between all three IP Phones and verify that all three phone users can hear each other. Also during the call, press the i button twice on the IP Phone and check that the phones are using the configured codec. You can use Performance Monitor to monitor performance objects for conferencing and transcoding resources (Refer to the “Document Registered Device Counts” section of Chapter 9, “Operations and Optimization,” for more information on doing this.) |
Test Category: Distributed Call Processing | ||
1 | Phone-to-phone dial-up test in different cluster | Make a phone call from IP Phone A in cluster 1 to IP Phone B in cluster 2 and verify that two-way audio is established. |
2 | Call transfer to an IP Phone in another cluster | Make a phone call from IP Phone A in cluster 1 to IP Phone B in cluster 2 and answer the call. Press the Transfer softkey on IP Phone A and dial the extension of IP Phone C in cluster 2. Verify that the call is established between IP Phone A and IP Phone C. |
3 | Call forward to an IP Phone in another cluster | From IP Phone A in cluster 1, press the CFwdALL softkey and enter the phone number of IP Phone B in cluster 2. Make a phone call from IP Phone C in cluster 1 to IP Phone A and verify that the call is forwarded to IP Phone B in cluster 2 and that the call is successful. |
Test Category: Advanced IPT Tests | ||
1 | Fax to fax | Send a fax message from one fax station to another fax station and verify that the fax transmission is successful. |
2 | CallManager failover | Stop the CallManager service on the primary subscriber. Verify that phones fail over to the backup subscriber and that all functionality is retained. Unplug the network cable for the primary subscriber. Verify that phones fail over to the backup subscriber and that all functionality is retained. |
Test Category: Dial Plan Testing | ||
1 | Local call routing | Make local calls and check that the called party receives the right caller ID and calling name. |
2 | Long-distance call routing | Make long-distance calls and make sure that they go via the right gateway. |
3 | On-net call routing | Make on-net calls to other locations. |
4 | Off-net call routing | Make off-net calls. |
5 | E911 or emergency call routing | Call the emergency number and inform the person that this is a test call. Verify that the public safety access point (PSAP) gets the right phone number and address. |