350-801 — Frequently Asked Questions

The primary requirements for Location-Based CAC involve defining 'Locations' and assigning them to devices. Each location is configured with a specific amount of audio and video bandwidth. When a call is placed between devices in different locations, UCM checks if sufficient bandwidth is available in the path. If not, the call is denied or rerouted based on the configuration. Key elements include setting up the locations, defining the bandwidth limits, and associating devices (phones, gateways) with the correct location.

Essential SNMP monitoring elements for a CUBE include CPU and memory utilization, the number of active calls/sessions, call failure rates, and interface statistics (input/output rates, errors, discards). Monitoring these metrics helps identify performance bottlenecks, resource exhaustion, or connectivity issues that could impact voice quality and call processing.

Device onboarding via activation codes typically involves generating a unique code within the Cisco UCM administration interface for a specific device or a range of devices. This code is then entered on the device itself (often through its web interface or on-screen menu). The device uses this code to authenticate with the UCM cluster and automatically download its configuration, simplifying the deployment process, especially for remote or bulk installations.

Within a policy map configuration, the priority command is used to specify the traffic class for Low Latency Queuing (LLQ). This command allocates a strict priority queue to the traffic class defined in the preceding class statement, ensuring that this traffic (like voice) is serviced before other queues, thus minimizing delay and jitter.

Common valid installer arguments for the Webex App in a Virtual Desktop Infrastructure (VDI) environment include options to enable or disable auto-update (/disableautoUpdate), configure the installation path (/installPath), or set optimization modes specifically for VDI (/enableVDIMode). These arguments allow administrators to customize the deployment to fit their specific VDI environment's requirements.

The Bulk Administration Tool (BAT) allows administrators to update Calling Search Spaces (CSS) for multiple devices simultaneously. This is done by creating a BAT job, selecting the target devices (e.g., phones, gateways) using a query, and then specifying the new CSS to be applied. This is far more efficient than manually changing the CSS on each device individually, especially in large deployments.

A common solution for PRI DSP resource errors on a Cisco ISR 4300 is to verify the DSP farm profile configuration and ensure that the correct number of DSPs are allocated and available. This may involve checking the dspfarm profile configuration for conferencing or transcoding, ensuring the codec complexity is set correctly (e.g., flex or high), and confirming that the physical PVDM modules are seated correctly and recognized by the router.

Sudden failure of Cisco SpeakerTrack can be caused by several factors. Common culprits include network connectivity issues between the camera and the endpoint, incorrect camera positioning or obstruction, firmware incompatibility between the camera and the video endpoint (like a Codec or Room Kit), or a misconfiguration in the endpoint's settings where SpeakerTrack is disabled or improperly configured.

Prerequisites for onboarding Webex devices to Control Hub include having a valid Webex subscription, ensuring the device has internet connectivity to reach Webex cloud services, and having the device in a factory-default state or properly reset. Additionally, you may need an activation code generated from the Control Hub portal or the device must be able to authenticate using an organization ID.

The main difference is their function and placement. A SIP Proxy primarily routes SIP signaling messages between User Agents (phones) and other proxies within a trusted network. An SBC sits at the edge of a network (the border) and provides security, interoperability, and policy enforcement for sessions crossing trust boundaries (e.g., connecting to an ITSP). SBCs handle both signaling and media, often performing NAT traversal, topology hiding, and transcoding, whereas a proxy typically only handles signaling.

Configuring a Self-Provisioning IVR in a Universal Device Template allows end-users to provision their own phones. When a new phone connects to the network, it is directed to an Interactive Voice Response (IVR) system. The user can then follow prompts to associate the phone with their specific directory number (DN) and user account, streamlining the deployment process and reducing the administrative burden on IT staff.

A 'Medium' OVA (Open Virtualization Archive) template is considered for this user range because it provides a balanced allocation of virtual resources (vCPU, RAM, and storage) suitable for a mid-sized cluster. It supports a specific number of registered devices and call processing capacity that fits within the 5,000-10,000 user scope without over-provisioning (using a Large/Extra Large template unnecessarily) or under-provisioning (using a Small template which would be insufficient).

In a Webex Dial Plan, 'Locations' are used to define specific sites or offices within an organization. They are crucial for routing calls correctly and applying specific dialing rules (like access codes for outside lines) based on where the user is physically located. This ensures that a user in the London office dials a local number differently than a user in the New York office, even if they are calling the same destination.

When the bandwidth limit for a location is exceeded, the Call Admission Control (CAC) mechanism will block the call to prevent oversubscription of the WAN link. Depending on the configuration, the system may play a reorder tone to the caller, redirect the call over the PSTN (if Automated Alternate Routing is configured), or simply fail the call attempt with a 'network busy' message.

Monitoring 'active sessions' is critical because it indicates the current load on the CUBE. A sudden spike might indicate a traffic surge or a potential Denial of Service (DoS) attack. Conversely, if the number of active sessions is consistently near the licensed capacity, it indicates a need for capacity planning and potentially upgrading the license to prevent call failures.