Learn About Cisco IP Telephony for Release 4.x

Posted on
Share on Google+Share on LinkedInShare on FacebookShare on RedditTweet about this on TwitterEmail this to someone

The following are questions from MeasureUp’s Practice Test for the Cisco exam 642-444: Cisco IP Telephony for Release 4.x (CIPT-4.x). By passing this exam, you earn credit toward the Cisco Certified Voice Professional (CCVP) certification .

The audience for this exam includes individuals who are responsible for installing, configuring and supporting Voice over IP (VoIP)-related and public switched telephone network (PSTN)-related products. Experience working with Cisco's Unified CallManager will help you prepare for this exam.

Objective: Perform an installation and initial set up of a CallManager cluster.
Sub-objective: Configure DCHP, TFTP and NTP.

Multiple answers, multiple-choice

Users report they can no longer make or receive calls. You log in to the CallManager and see that all services are functional. While troubleshooting, the server administrator informs you that the company DNS server is down. You verify that the DHCP scope is configured to send option 66, but the phones are still not working. What can you do to resolve the issue? (Choose two.)

A.    Configure the IP address of the primary cluster member manually on each phone.
B.    Perform a power reset to each phone.
C.    Force a failover to the secondary cluster member.
D.    Stop and start the Cisco CallManager service.
E.    Configure the DHCP server with option 150.

 A, E

You should configure the DHCP server with option 150. All phones need to know which Trivial File Transfer Protocol (TFTP) server to contact to receive their configuration file. Option 66 provides the host names of the TFTP server and option 150 provides the IP address of the TFTP server. With the IP address, there is no need for DNS resolution.

Although it is not recommended, you could also hard code the IP address of the TFTP server on each phone. However, it is much easier to add option 150 to the DHCP scope.

You should not perform a power reset to each phone. Performing a power reset on each phone will simply restart the boot process. When the phone tries to resolve the TFTP server host name to its IP address, it will fail again.

You should not force a failover to the secondary cluster member. Failing over to the secondary cluster member will not help to resolve the TFTP server host name to its IP address.

You should not stop and start the Cisco CallManager service because doing so does not inform the phones of the IP address of the TFTP server.

IP Phone Startup
Authorized Self-Study Guide Cisco IP Telephony (CIPT), Second Edition
Chapter 3. Cisco Unified CallManager Installation and Upgrades

Objective: Configure CallManager to support a call between any two endpoints on-cluster and off-cluster.
Sub-objective: Describe the purpose and features of SRST and AAR.

Single answer, multiple-choice

You have a centralized CallManager environment with a single remote site. You add the Survivable Remote Site Telephony (SRST) configuration to the router in the remote site. The router configuration is shown below:

Remote_Office(config-cm-fallback)#access-code fxo 9
Remote_Office(config-cm-fallback)#default-destination 1234
Remote_Office(config-cm-fallback)#dialplan-pattern 1 5555555… .
Remote_Office(config-cm-fallback)#ip source-address port 2000
Remote_Office(config-cm-fallback)#keepalive 30
Remote_Office(config-cm-fallback)#max-ephones 24
Remote_Office(config-cm-fallback)#max-dn 48
Remote_Office(config-cm-fallback)#transfer-pattern 444…
Remote_Office(config-cm-fallback)#voicemail 5001

When the CallManager fails, how many extensions and IP phones will be supported?

A.    24 extensions and 48 IP phones.
B.    30 extensions and 24 IP phones.
C.    48 extensions and 24 IP phones.
D.    48 extensions and 1234 IP phones.


After you enter the call-manager-fallback command, you are able to enter subcommands to define parameters for SRST.

To define the maximum number of supported extensions, or DNs, use the max-dn command. In this example, you have set the maximum extensions to 48.

To define the maximum number of supported IP phones, use the max-ephones command. In this example, you have set the maximum IP phones to 24.

Before setting the maximum number of IP phones, it is best practice to refer to the Cisco Web site to verify the maximum number support by the router.

Cisco CallManager System Guide, Release 4.1(3) – System-Level Configuration Settings

Objective: Given a list of IP phone features, configure the CallManager to support the given feature set.
Sub-objective: Configure call forward.

Single answer, multiple-choice

You configure Call Forward and Pickup Settings for a line as shown in the exhibit.

When someone calls this extension while the line is busy, how will the call be handled?

A.    The call will be forwarded to voice mail.
B.    The call will be forwarded to extension 5000.
C.    The call will be forwarded to extension 5001.
D.    The call will only hear a busy signal.


In this example, you have selected to have internal calls forwarded to extension 5000 and external calls forwarded to extension 5001 when the line is busy, but you also selected Voice Mail, so your manual settings will be ignored.

You have many options while configuring call forwarding for a directory number. You can specify a different number to forward the call to for internal and external calls, for busy, no answer and no coverage calls.

When you configure Internal behavior, the respective External behavior will inherit the settings assigned to Internal. You can overwrite the inherited settings manually.

An important caveat is that even if you specify an internal and/or external number to forward to, selecting the Voice Mail option box will overwrite the Coverage/Destination configuration.

Cisco CallManager Features and Services Guide, Release 4.1(3) – Multilevel Precedence and Preemption

Objective: Given a specific set of IP telephony applications and tools, configure CallManager to support the applications.
Sub-objective: Install and configure BAT and TAPS to bulk add/manage phones/users.

Multiple answers, multiple-choice

You are installing the Bulk Administrative Tool (BAT) release 4.1(1) for use in your CallManager environment. Which of the following are specifications of BAT? (Choose three.)

A.    BAT must be installed on a publisher in the CallManager environment.
B.    BAT requires Internet Explorer 4.01 Service Pack 2 or later.
C.    BAT must be installed on a subscriber in the CallManager environment.
D.    Because of its streamlined design, BAT can be used at any time.
E.    BAT requires Internet Explorer 5.0 or later.
F.    Because of its huge overhead, BAT should be used off hours.

A, B, F

To have read/write access to the CallManager database, you must install BAT on the publisher, which is the only server with the read/write copy of the CallManager database. The subscribers receive a read-only copy of the CallManager database. Therefore, you cannot install BAT on any subscriber.

To access the Web-based BAT, you must use either Internet Explorer 4.01 Service Pack 2 or later or Netscape 4.5 or later. You may be able to access BAT using third-party browsers, but you will not be able to receive Cisco support for any issues if you do not use the Cisco-specified browsers.

BAT is used to automate changes to multiple phones in a batch process. Because it involves many changes to many devices, it is recommended that you run BAT off hours to ensure CallManager resources are not exhausted.

Bulk Administrative Tool User Guide, Release 4.1(1) – Installation

Objective: Monitor and manage an IP telephony network using Internal Server Tools.
Sub-objective: Describe the tools inherent in the operating system and database, and also provided by Cisco, to monitor CallManager operation.

Single answer, multiple-choice

You are experiencing issues with your CallManager server. You want to use Event Viewer on the server to troubleshoot. What should you review to see CallManager specific events?

A.    System log
B.    Security log
C.    DNS server log
D.    Application log


You should review the application log. CallManager will write events to the application log. You can check the application log to quickly see if there were any events leading up to the problem you are troubleshooting. It is common to see multiple information and warning events prior to the error event. The event that occurred prior to the error event often provides more troubleshooting data than the actual error event.

The system log contains operating system and local service events such as services failing to start or drivers failing to load. The security log contains security events such as successful and failed log-on attempts and file access. The DNS server log contains events related to the DNS server service running on the server.

System Event Viewer Tips
Microsoft TechNet

Share on Google+Share on LinkedInShare on FacebookShare on RedditTweet about this on TwitterEmail this to someone


Posted in Archive|