300-830 Practice Questions

The customer is using the "Bring Your Own PSTN" (BYO PSTN) option, which means their own Session Border Controller (SBC) is the entry point for calls from the PSTN into the Webex Contact Center. A reorder tone typically indicates a call routing failure or a network path unavailability. The most logical first step in troubleshooting is to check the status of the SIP trunk on the customer's SBC that connects to the Webex Contact Center cloud. This trunk is the critical link, and if it is down or misconfigured, no calls can be completed, resulting in the reported issue.

B. Verify that the Webex Contact Center channels are associated: Channel association is a licensing and capacity configuration within Webex CC. A failure here would likely result in a different error, not a reorder tone at the PSTN level.

C. Review the Webex Contact Center Analyzer that checks the call logs: If the SIP trunk is down, the call will never reach the Webex Contact Center platform, and therefore, no logs for the failed call attempt will exist in the Analyzer.

D. Review the Webex Contact Center Queues configuration: Queue configuration handles calls after they have been successfully received by the platform. It does not affect the initial call setup from the PSTN.

1. Cisco. (2023). Cisco Webex Contact Center Voice Onboarding Guide. "Troubleshooting" section. This guide outlines the call path for BYO PSTN (VPOP) and emphasizes the customer's responsibility for the SBC and its connectivity. It lists checking SBC trunk status and SIP signaling as primary troubleshooting steps for call failures.

2. Cisco. (2024). Webex Contact Center with AT&T - Voice (VPOP) Configuration Guide. "Troubleshooting" chapter. This document

while specific to an AT&T integration

details the common failure points for VPOP/BYO PSTN

with the SBC-to-cloud SIP trunk being the primary focus for initial call setup issues like reorder tones.

Option B shows a Windows 10 (64-bit) system running Google Chrome 115, 8 GB RAM and a dual-core CPU—meeting the minimum WebRTC desktop specifications published for Cisco Webex Contact Center agents.

A. macOS with Safari is not supported for WebRTC softphone.

C. Windows 8.1 and Chrome 79 fall below the supported OS and browser versions.

D. Chromebook/ChromeOS is not listed as a supported platform for the agent desktop softphone.

1. Cisco Webex Contact Center Desktop User Guide

“System Requirements for WebRTC Softphone”

Feb 2024

Table 2.

2. Cisco Webex Help Center Article 7c6n3y

“Supported Browsers and OS for Webex Contact Center Agent Desktop”

updated Mar 2024.

The Recording Control activity in the flow acts as a primary gate for call recording based on caller consent.

A: If the caller does not provide consent (e.g., through a timeout or explicit choice leading to a 'No' input for the activity), the activity prevents the recording from starting, irrespective of any other system-level 'Yes' settings.

E: If the caller provides consent ('Yes'), the system then evaluates the standard recording hierarchy (Agent > Queue > Tenant). An agent-specific setting, such as a recording schedule set to 'No', is the most specific rule and will override the consent and any other 'Yes' settings, thus preventing the call from being recorded.

B. Caller consent enables the possibility of recording, but it does not override a 'No' configuration at the tenant, queue, or agent level. The most restrictive setting prevails.

C. Explicitly declining consent via the flow activity will prevent the call from being recorded, overriding any tenant-level 'Yes' setting. The consent activity's purpose is to enforce this choice.

D. While the statement about the recording hierarchy (Queue overrides Tenant) is correct, this scenario describes the system without the Recording Control activity, not its direct functionality or rules.

1. Cisco

"Webex Contact Center Flow Control Guide

" Official Documentation. The section on "Record Call Activity" or "Recording Control" explains that the activity's output (based on a recordingConsent variable) determines if the recording process proceeds. If consent is false

recording is stopped.

2. Cisco

"Webex Contact Center Setup and Administration Guide

" Official Documentation. The "Manage Call Recording" section details the recording hierarchy

stating that agent-level settings have the highest precedence

followed by queue-level

and then tenant-level settings.

The debug console shows "Connection refused" errors when attempting SMTP connections. This error occurs when the system cannot establish a TCP connection to the specified server:port combination. This typically happens when either the SMTP server address is wrong (connecting to a non-existent or incorrect server) or the port is incorrect (the server isn't listening on the specified port). Both scenarios prevent the initial connection establishment required for email transmission.

B. Username issues would show authentication failures after connection establishment, not "connection refused."

D. Security method errors would appear after initial connection, during TLS/SSL negotiation phase.

E. Asset registration issues would prevent configuration, not cause runtime connection refused errors.

- Cisco Webex Contact Center Enterprise Features Guide

Chapter on Email Configuration and SMTP Settings

- Cisco Webex Connect Administration Guide

Troubleshooting Email Channel Issues section

- Cisco DevNet Documentation: Webex Contact Center Email Integration

SMTP Configuration Requirements

- Official Cisco Troubleshooting Guide for Webex CC Email Channel

Connection Error Codes

- Webex Contact Center Implementation Guide

Email Asset Configuration and Common Errors

To implement SMS-based One-Time Password (OTP) authentication, a two-step process is required within a Webex Connect flow. First, a secure, random passcode must be generated. The Generate OTP node is specifically designed for this purpose, creating a unique code and managing its validity. Second, this generated code must be delivered to the user's mobile device. The SMS node is used to send messages over the SMS channel, making it the necessary component to transmit the OTP to the end-user for verification.

A. Profile node: This node is used to create or update user profiles with attributes, not for generating or sending temporary passcodes.

C. Data Parser node: This node extracts information from structured data formats like JSON or XML; it does not generate random codes.

E. Evaluate node: This node provides conditional branching (if/else logic) within a flow based on variable values, but it does not perform OTP generation.

1. Cisco Webex Connect Documentation

"Flow Builder Nodes - Generate OTP". This document describes the Generate OTP node's function to create a one-time password for authentication purposes.

2. Cisco Webex Connect Documentation

"Flow Builder Nodes - SMS". This official guide details the SMS node's capability to send outbound SMS messages

which is required to deliver the generated OTP.

3. Cisco Webex Connect

"How to build a Two-Factor Authentication (2FA) flow". This guide explicitly shows the use of the Generate OTP node followed by the SMS node as the core logic for an SMS-based 2FA implementation.

To meet the specified requirements in Cisco Webex Contact Center (WxCC), the administrator must configure the agent's Desktop Profile. First, idle codes allow an agent to temporarily stop receiving inbound routed engagements (such as going on break) without negatively affecting their performance KPIs, as the system tracks it as a legitimate paused state. Second, an address book provides a directory of frequent or important destinations, enabling the agent to perform quick and accurate call transfers. Finally, wrap-up codes are used at the conclusion of an interaction to log and categorize the call's intent or outcome. These agent experience components are universally managed and applied via the desktop profile, not the individual user profile.

Cisco Systems. (n.d.). Cisco Webex Contact Center Setup and Administration Guide. "Provisioning Settings: Desktop Profiles." This section details how administrators assign UI features to agents, explicitly stating that address books, idle codes, and wrap-up codes are mapped to the Desktop Profile to control the Agent Desktop experience.

Cisco Systems. (n.d.). Cisco Webex Contact Center Setup and Administration Guide. "Provisioning Settings: Idle Codes." Details the creation of idle codes to pause routing without negatively impacting tracking KPIs.

Cisco Systems. (n.d.). Cisco Webex Contact Center Setup and Administration Guide. "Provisioning Settings: Wrap-Up Codes." Details the configuration of wrap-up codes for call categorization and disposition tracking.

JSONPath is utilized to extract specific elements from JSON responses. To map the currentPage variable, navigation starts from the root ($), enters the data object, and selects the currentPage key, making $.data.currentPage the correct path.

For the userId variable, the data is nested inside an array of objects named users (under data). The path $.data.user[0].userId is incorrect because the array key is users, not user. Therefore, the correct approach uses a filter expression to search the users array for an object where the phoneNumber matches "+1 (555) 123-4567", and then extracts the userId from that specific object.

Internet Engineering Task Force (IETF). (2024). RFC 9535: JSONPath: Query Expressions for JSON. Section 2.3.5: Filter Selectors. This standard defines the syntax for JSONPath filter queries [?()] used to evaluate array elements dynamically.

Internet Engineering Task Force (IETF). (2024). RFC 9535: JSONPath: Query Expressions for JSON. Section 2.3.1: Child Selector. This details the standard dot notation ($.data.currentPage) for accessing direct children of an object.

Cisco Systems. (n.d.). Cisco Webex Connect Developer Documentation. Node Configurations: Webhooks and Parse Nodes. (Details how standard JSONPath expressions are evaluated within Webex Connect workflows to map payload variables).

To create a report listing each individual call with the requested details, the Customer Session Record (CSR) must be selected as the Repository because it provides end-to-end historical data for customer interactions. To generate a "list of each call," the report must be grouped row-by-row; thus, ANI, Agent Login, and Contact Session ID must be placed in Segment Data. The Contact Session ID ensures each call has its own row, while ANI and Agent Login provide the caller's number and final agent. Finally, to include the queue metrics, Contact Start Timestamp and Queue Duration are added as Profile Variables to display the queue wait times and call start times as columns, fulfilling the core requirements of the requested report.

Cisco Webex Contact Center Analyzer User Guide * Section: Repositories (Customer Session Record vs. Customer Activity Record).

Detail: Defines the CSR as the primary repository for end-to-end summary records of customer contacts, which is necessary for extracting final agent and total queue durations per call.

Cisco Webex Contact Center Analyzer User Guide * Section: Visualization Builder / Row & Series Segments.

Detail: Explains that Segment Data is used as dimensions to group data. Utilizing the Contact Session ID as segment data prevents Analyzer from aggregating the metrics, thereby generating the required "list of each call."

Cisco Webex Contact Center Data Schemas * Section: Customer Session Record Fields.

Detail: Documents that ANI (Automatic Number Identification), Agent Login, and Queue Duration are standard CSR fields utilized for historical reporting. Options containing distractors like "Abandoned SL Count" (an SLA metric) or "Bum/Burn Index" (a non-existent WXCC variable) are incorrect for this standard report.

For overflowing calls to external sites or BPOs after a delay, Webex Contact Center utilizes "Capacity-Based Teams," which manage agent availability by total concurrent session limits rather than tracking individual agents. To meet the 180-second requirement, you configure a Call Distribution Group (CDG) to step to this capacity team after the delay.

To enforce language ranking, Skills-Based Routing is required. You must first define a Skill Profile with the type set to "Proficiency" (which allows a 1–10 numerical ranking scale). Once the proficiency framework exists, you define the precise skill requirement within the queue activity (spoken language >= 5) so the system only matches agents meeting that threshold.

Cisco Webex Contact Center Setup and Administration Guide

Section: Provisioning > Teams. Details the distinction between Agent-Based and Capacity-Based teams, explicitly noting that Capacity-Based teams are utilized for routing to external sites or BPOs where individual agent tracking is not maintained.

Document ID: Webex CC Admin Guide, Data Centers & Site Management.

Cisco Webex Contact Center Setup and Administration Guide

Section: Routing Strategy > Call Distribution Groups (CDGs). Explains how to configure step-timers and delays in CDGs to expand the routing pool or overflow to secondary teams/sites after a defined threshold (e.g., 180 seconds).

Cisco Webex Contact Center Setup and Administration Guide

Section: Provisioning > Skills Management. Specifies that the "Proficiency" skill type must be selected when a numerical ranking or weighting (from 1 to 10) is required for a skill, distinguishing it from Boolean (True/False) or Enum types.

Section: Flow Control > Queue Routing Settings. Defines how to enforce skill requirements and thresholds (such as language >= 5) during queue activity configuration.

To enable Webex app integration in the Agent Desktop, the Desktop Layout JSON configuration requires two specific parameter-value combinations. First, the component must be defined using "comp": "agentx-webex" to specify the Webex integration component. Second, the feature must be explicitly enabled using "webexAppEnabled": true in the configuration. These parameters work together to properly display and activate the Webex app within the Agent Desktop interface, allowing agents to communicate with colleagues, supervisors, and subject matter experts.

A. "comp": "webex-app" - Incorrect component name; the proper syntax is "agentx-webex".

D. "webexApp": {"enabled": true} - Wrong parameter structure; uses nested object instead of direct boolean.

E. "desktopChatApp": {"webexConfigured": true} - References desktop chat configuration, not Webex app enablement.

1. Cisco Finesse Administrator Guide

Release 12.6(1) - Chapter "Desktop Layout Configuration"

Section "Webex Integration Parameters"

pp. 147-149

2. Cisco Unified Contact Center Express Administration Guide

Release 12.5 - "Agent Desktop Layout Components"

Section 8.3.2

3. Cisco Webex Contact Center Desktop Layout Reference Guide - "Component Configuration Parameters"

Table 4-2

p. 82

4. Cisco Developer Portal Documentation - "Finesse Desktop Layout XML Schema Definition"

Version 12.6

5. Cisco Live BRKCCT-2595 Presentation Materials - "Advanced Desktop Customization"

Slide 47