Which two directory services are supported by Cisco Unified Communications Manager for Lightweight Directory Access Protocol integration? (Choose two.)
A. Windows Active Directory 2008
B. Novell eDirectory
C. iPlanet Directory Server 4.0
D. Sun ONE Directory Server
E. Open Lightweight Directory Access Protocol 2.1
Correct Answer: AD Section: CUCM Explanation
LDAP Directory Configuration Checklist
If you want to do so, you can add users from your corporate directory to the Cisco Unified Communications
Manager database by synchronizing the user data to the database.
Cisco Unified Communications Manager allows synchronization from the following directories to the
Microsoft Active Directory 2000
Microsoft Active Directory 2003
Microsoft Active Directory 2008
Microsoft Active Directory Application Mode 2003
Microsoft Lightweight Directory Services 2008
iPlanet Directory Server 5.1
Sun ONE Directory Server 5.2
Sun ONE Directory Server 6.x
Note: Microsoft Active Directory Application Mode support is limited to those directory topologies already supported with a native Active Directory connection. No additional topologies, such as multi-forest, multi-tree single forest, or global catalog are supported.
Cisco Unified Communications Manager supports the following types of synchronization:
Automatic synchronization, which synchronizes the data at regular intervals.
Manual synchronization, which allows forcing the synchronization.
Stop synchronization, which stops the current synchronization. If synchronization is in progress, check for agreement.
When creating a new softphone for a Cisco Unified Presence user, which phone type should you select if you are using Cisco Unified Personal Communicator Release 7.1?
A. Cisco Unified Personal Communicator
B. Cisco Unified Client Services Communicator
C. Cisco Unified Client Services Framework
D. Cisco Unified Personal Communicator Framework
Correct Answer: A Section: Unified Personal Communicator Explanation
(Cisco Unified Personal Communicator Release 7.1) Guidelines for Configuring the Softphone Device Name
When you create a softphone device for each Cisco Unified Personal Communicator user, you must specify a device name. Make sure that the device name conforms to these guidelines:
Derives from the username.
Starts with UPC.
Contains only uppercase letters, or numerals.
Contains no more than 12 additional characters after UPC.
Link: http://www.cisco.com/en/US/docs/voice_ip_comm/cups/8_0/english/install_upgrade/deployment/guide/ dgclient.html#wp1135232
One user from your company wants to use a signaling protocol on the voice gateways that require registration with the Cisco Unified Communications Manager. Which protocol should you suggest to him?
Correct Answer: D
Media Gateway Control Protocol (MGCP)
MGCP provides Cisco Unified Communications Manager with a powerful, flexible and scalable resource for call control. Cisco Unified Communications Manager uses MGCP to control media on the telephony interfaces of a remote gateway and also uses MGCP to deliver messages from a remote gateway to appropriate devices.
MGCP enables a call agent (media gateway controller) to remotely control and manage voice and data communication devices at the edge of multiservice IP packet networks. Because of its centralized architecture, MGCP simplifies the configuration and administration of voice gateways and supports multiple (redundant) call agents in a network. MGCP does not provide security mechanisms such as message encryption or authentication.
Using MGCP, Cisco Unified Communications Manager controls call processing and routing and provides supplementary services to the gateway. The MGCP gateway provides call preservation (the gateway maintains calls during failover and fallback), redundancy, dial-plan simplification (the gateway requires no dial-peer configuration), hookflash transfer, and tone on hold. MGCP-controlled gateways do not require a media termination point (MTP) to enable supplementary services such as hold, transfer, call pickup, and call park. If the MGCP gateway loses contact with its Cisco Unified Communications Manager, it falls back to using H.323 control to support basic call handling of FXS, FXO, T1 CAS, and T1/E1 PRI interfaces.
Link: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/9_0_1/ccmsys/ CUCM_BK_CD2F83FA_00_system-guide_chapter_0100111.html
Which value should you assign to option 150 for DHCP to operate correctly in a Cisco Unified Communications Manager Express environment?
A. FTP server of the DNS server
B. MAC address of the DHCP server
C. MAC address of the TFTP server
D. IP address of the TFTP server
Correct Answer: D Section: CUCME Explanation
Configuring a Router-Based DHCP Server
RTR# configure terminal RTR(config)# ip dhcp excluded-address 172.16.1.1 172.16.1.9 RTR(config)# ip dhcp excluded-address 172.16.2.1 172.16.2.9 RTR(config)# ip dhcp pool DATA_SCOPE RTR(dhcp-config)# network 172.16.2.0 255.255.255.0 RTR(dhcp-config)# default-router 172.16.2.1 RTR(dhcp-config)# dns-server 22.214.171.124 RTR(dhcp-config)# exit
RTR(config)# ip dhcp pool VOICE_SCOPE RTR(dhcp-config)# network 172.16.1.0 255.255.255.0 RTR(dhcp-config)# default-router 172.16.1.1 RTR(dhcp-config)# option 150 ip 172.16.1.1 RTR(dhcp-config)# dns-server 126.96.36.199
What device enables Call Admission Control in a CME environment?
Correct Answer: D Section: CUCME Explanation
Cisco IOS Gatekeeper Zones A Cisco IOS gatekeeper can provide call routing and call admission control between devices such as Cisco Unified CM, Cisco Unified Communications Manager Express (Unified CME), or H.323 gateways connected to legacy PBXs. It uses the H.323 Registration Admission Status (RAS) protocol to communicate with these devices and route calls across the network.
Gatekeeper call admission control is a policy-based scheme requiring static configuration of available resources. The gatekeeper is not aware of the network topology, so it is limited to simple hub-and-spoke topologies. Refer to the section on Design Considerations for Call Admission Control, for detailed topology examples.
For a listing of the available Cisco IOS gatekeeper platforms and the features supported on each platform, refer to the Cisco IOS H323 Gatekeeper Data Sheet at
The call admission control capabilities of a Cisco IOS gatekeeper are based on the concept of gatekeeper zones. A zone is a collection of H.323 devices, such as endpoints, gateways, or Multipoint Control Units (MCUs), that register with a gatekeeper. There can be only one active gatekeeper per zone, and you can define up to 100 local zones on a single gatekeeper. A local zone is a zone that is actively handled by that gatekeeper – that is, all H.323 devices assigned to that zone register with that gatekeeper.
When multiple gatekeepers are deployed in the same network, a zone is configured as a local zone on only one gatekeeper. On the other gatekeepers, that zone is configured as a remote zone. This configuration instructs the gatekeeper to forward calls destined for that zone to the gatekeeper that “owns it” (that is, the gatekeeper on which that zone is configured as a local zone).
For details on configuring the gatekeeper, refer to the Cisco IOS H.323 Configuration Guide at
The bandwidth value deducted by the gatekeeper for every active call is double the bit-rate of the call, excluding Layer 2, IP, and RTP overhead. For example, a G.711 audio call that uses 64 kbps would be denoted as 128 kbps in the gatekeeper, and a 384-kbps video call would be denoted as 768 kbps. Table 11-4 shows the bandwidth values used by the gatekeeper feature for some of the most popular call speeds.
Ensurepass offers Latest 2013 640-461 Real Exam Questions , help you to pass exam 100%.