|Exam Name||:||Troubleshooting Cisco IP Telephony and Video (CTCOLLAB)|
|Questions and Answers||:||250 Q & A|
|Updated On||:||Click to Check Update|
|PDF Download Mirror||:||300-080 Brain Dump|
|Get Full Version||:||Pass4sure 300-080 Full Version|
Which of these reasons can cause intrasite calls within a Cisco Unified Communications Manager cluster to fail?
The route partition that is configured in the CCD requesting service is not listed in the calling phone CSS.
The trunk CSS does not include the partition for the called directory number.
The MGCP gateway is not registered.
The calling phone does not have the correct CSS configured.
The calling phone does not have the correct partition configured.
You must integrate a third-party H.323 system with your existing Cisco Unified Communications Manager cluster. When you create an H.323 trunk from the cluster, calls from the cluster to the third-party H.323 system are failing. The vendor of the third-party H.323 device has confirmed that the H.323 call setup time must be reduced. Which two approaches reduce the call setup time from Cisco Unified Communications Manager to the third-party H.323 device? (Choose two.)
Implement a software MTP.
Implement a hardware MTP.
Implement transcoding with the router DSP resources.
Implement transcoding with the Cisco Unified Communications Manager resources.
Which two troubleshooting tools would initially be the best to use when troubleshooting the PSTN gateway side of a call routing issue while using Cisco Unified Communications Manager? (Choose two.)
RTMT trace output
Cisco IOS debug commands
Dialed Number Analyzer output
Cisco Unified Communications Manager alerts
Cisco IOS show commands
When a database replication issue is suspected, which three tools can be used to check the database replication status? (Choose three.)
Cisco Unified Communications Manager RTMT tool
Cisco Unified Communications Manager Serviceability interface
Cisco Unified Reporting
Cisco Unified Communications Manager CLI interface
Cisco IP Phone Device Stats from the Settings button
Cisco Unified OS Administration interface
To maintain proper database integrity, what is the recommended maximum round-trip delay between multiple Cisco VCS appliances in a cluster?
You are trying to register an H.323-based Cisco TelePresence system to Cisco Unified Communications Manager and a Cisco DX70 system to the Cisco VCS Control. Why do neither of the units want to register?
The H.323-based system needs an E164 number to register to Cisco Unified Communications Manager, and the Cisco DX70 needs to have the MAC address configured first on the Cisco VCS Control.
The H.323-based system needs to register to the Cisco VCS Control with an E.164 number, and the Cisco DX70 needs the TFTP address to register on the Cisco Unified Communications Manager.
Both systems need to register to the Cisco VCS Control, but the H.323-based system needs to have the gatekeeper setting set to “Direct.”
Both systems need to register to the Cisco Unified Communications Manager, as the Cisco VCS Control is used only for firewall traversal.
You need Cisco TelePresence Management Suite to register Cisco TelePresence systems.
You need Cisco TelePresence Server to register Cisco TelePresence systems.
Endpoints are configured for both H.323 and SIP using the same URI and Cisco VCS settings, but the endpoints register only as H.323 endpoints. What is causing this issue?
A firewall is blocking all traffic from the endpoints to the Cisco VCS.
The Cisco VCS has no SIP domains configured.
The Cisco VCS is blocking the endpoints because of duplicate ID entries.
The endpoints do not have the SIP option key installed.
SIP does not work, because SIP is used for Cisco Unified Communications Manager registration only.
Which issue would cause an MGCP gateway to fail to register with Cisco Unified Communications Manager?
missing the configuration command isdn bind-l3 ccm-manager under the ISDN interface
mismatched domain name on the MGCP gateway and Cisco Unified Communications Manager gateway configuration
misconfigured route group in Cisco Unified Communications Manager
incorrect MGCP IP address specified in the gateway configuration in Cisco Unified Communications Manager
You configured a Cisco ISR G2 as a SIP gateway, but the gateway does not show that it is registered with Cisco Unified Communications Manager. What is causing this issue?
Cisco Unified Communications Manager does not support SIP gateways.
The gateway does not have the UC license installed.
The gateway does not have Cisco Unified Border Element session licensing.
Cisco Unified Communications Manager does not show a SIP gateway as registered if it is not properly configured.
Cisco Unified Communications Manager never shows a SIP gateway as registered even when it is properly configured.
The Cisco ISR G2 cannot be a SIP gateway.
Refer to the exhibit.
An IP phone that is connected through a Cisco Catalyst 3750 Series Switch is failing to register with Cisco Unified Communications Manager. When the user presses the settings button on the phone, the Operational VLAN ID shows a blank entry. What is the most likely cause for this issue?
The switch may not be supplying inline power.
The spanning tree portfast command needs to be removed.
The trunk encapsulation is missing. The trunk must be configured for dot1.Q.
Cisco Discovery Protocol is disabled on the switch.
The Operational VLAN ID of the phone always shows as blank. The Admin. VLAN ID should be 110.
An IP phone that is connected through a Cisco Catalyst 3750 Series Switch is failing to register with the subscriber as a backup server. When the user presses the settings button on the phone, only the Cisco Unified Communications Manager publisher shows as registered. What is the most likely cause for this issue?
The phone does not have the correct Cisco Unified Communications Manager group in the device configuration page.
The Cisco Unified Communications Manager group that is applied through the device pool is misconfigured.
The ip-helper address command for the subscriber is not configured on the switch port.
The subscriber does not have the correct device pool configured.
The enterprise phone configuration does not have the call control redundancy enabled.