300-810 Practice Questions

:

To troubleshoot desk phone control issues in Cisco Jabber for Windows, the "Show Connection

Status" option provides essential information about the Jabber client's connection to services like

Cisco UCM:

Displays status of services: Shows the status of CTI, TAPI, and other connections needed for desk

phone control.

Troubleshooting information: Can highlight if there are any connectivity issues or failures that would

explain the problem.

Reference:

Cisco Jabber for Windows Documentation: This should have a section on troubleshooting and may

mention the "Show Connection Status" feature.

Cisco Unified Attendant Console Advanced (CUACA) integrates with Cisco Unified Communications

Manager (UCM) to provide advanced call handling features for attendants. CUACA communicates

directly with the Cisco CallManager Service for core call routing, call control, and call state

information.

Cisco CTI Manager Service: While CTI (Computer Telephony Integration) plays a role in CUACA

interactions, the core communication happens through the CallManager Service.

Cisco DirSync Service: This service synchronizes directory information between UCM and other

systems, but it's not directly involved in CUACA communication.

Cisco TAPS Service: TAPS (Telephony Application Programming Services) provides a development

framework for UCM, not core call routing functionalities used by CUACA.

Within Cisco Unity Connection call handlers, the "caller input settings" section determines whether

callers can transfer out of the current call handler and potentially to other destinations. This section

allows you to configure:

Transfer Keys: Defines specific keys callers can press to initiate transfers

Transfer Destinations: Determines where calls can be transferred (extensions, other call handlers,

voicemail, etc.)

Reference:

Cisco Unity Connection Administration Guide: Look for the "caller input settings" and "call handler

configuration" sections, which should outline how to enable and configure caller-initiated transfers.

Toll fraud prevention on Cisco Unity Connection often involves restriction tables, which define

patterns of phone numbers that are allowed or disallowed. To prevent users from dialing out using

trunk access codes and potentially making unauthorized long-distance calls, here's the logic:

Identify trunk access codes: Determine the specific codes that allow external calls on each phone

system. These are often single-digit codes like "9".

Add patterns to restriction tables: Within the Cisco Unity Connection restriction tables, create

patterns that block any number starting with the trunk access code for each respective phone

system.

The scenario describes an issue where Message Waiting Indicators (MWIs) aren't lighting up for SIP-

integrated Cisco Unity Connection users, even though calls reach voicemail. This points towards a

configuration problem with MWI notifications on Cisco UCM.

A. Modify the SIP Trunk Security Profile on Cisco UCM: While SIP trunk security is important, it likely

wouldn't affect MWI functionality in this case.

B. Increase the Delay Between Requests timer on Cisco Unity Connection: This setting might be used

for other purposes but wouldn't directly address MWI notification issues on Cisco UCM.

C. Assign a Calling Search Space to the SIP Trunk on Cisco UCM: Calling Search Space defines call

routing, not MWI notification.

This option explains why the user sessions have not fallen back to the homed nodes after the failed

service or server was restored. The Client Re-Login upper limit setting determines how long the

Jabber clients will attempt to re-login to their homed nodes after a failover event. If the failed service

or server is offline longer than this setting, the Jabber clients will stop trying to re-login and will

remain on the backup node until the administrator manually initiates a fallback or recovery. The

default value for this setting is 30 minutes, but it can be changed in the Server Recovery Manager

Service Parameters. Reference:

https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communicationsmanager-im-presence-service/200958-IM-and-Presence-Server-High-Availability.html

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/configAdminGuide/11

_5_1/cup0_b_config-and-admin-guide-1151su5/cup0_b_imp-system-configuration-

1151su5_chapter_0100.html

:

:

: