300-830 Implementing Cisco Collaboration Cloud Customer ExperienceCLCCEv1.0 Questions and Answers

Cisco documents two Local Gateway trunking models for Webex Calling: registration-based trunks and certificate-based trunks. A registration-based trunk has the local gateway maintain SIP registration toward Webex Calling, and the signaling relationship is established through that registration. Cisco's trunk and dial plan documentation describes this model as an implicit connection based on the gateway's registration. A certificate-based trunk uses mutual TLS and certificate trust to authenticate signaling without SIP registration in the same way. These are the formal trunking choices used when integrating on-premises voice infrastructure with Webex Calling and, by extension, supporting Webex Contact Center telephony designs that use Local Gateway. DNS-based trunks are not a Cisco trunking model name in this context. PSTN trunks and enterprise trunks are generic or design descriptions, not the two Local Gateway models. For 300-830, the key is recognizing the official Webex Calling trunk model terminology. Reference: Cisco Help, Configure Local Gateway on Cisco IOS XE for Webex Calling; Configure trunks, route groups, and dial plans for Webex Calling.

The agent inherits the multimedia profile through the Desktop Profile when no explicit multimedia profile is assigned at the agent setting. In Webex Contact Center, desktop profiles govern key agent desktop behavior, including the experience and channel-related defaults that determine what an agent can use when signing in. The exhibit shows the user has no multimedia profile assigned directly, yet the agent can still accept voice and digital interactions. That means the applicable profile is coming from the desktop configuration assigned through the agent/team path. A skill profile would only describe routing skill values and proficiencies; it does not define how many or which media interactions the desktop can handle. A desktop layout controls widgets and user interface structure, not the multimedia interaction capacity. A site is an organizational grouping and not the source of the inherited multimedia profile in this scenario. The Desktop Profile is therefore the correct configuration object. Reference: Cisco Help, Manage desktop profiles; Webex Contact Center Setup and Administration Guide.

The Resolve Conversation node is a Webex CC Task/Engage integration node that depends on valid node authorization in Webex Connect. Cisco's Webex Connect documentation states that client applications such as Webex Connect must provide a valid access token to use Cisco Webex Contact Center and Webex Engage APIs, and that the token is generated from the configured node runtime authorization. If the Resolve Conversation node fails because it cannot call the Webex Contact Center integration properly, the administrator must authorize the Webex CC Task integration in Webex Connect with valid credentials. Changing the administrator password does not directly authorize the node runtime. Agent credentials are irrelevant because the flow node is running as an integration, not as an agent desktop session. A connector under Webex Contact Center integrations may be needed for some external API use cases, but the failing node shown is part of the pre-built Webex Connect/WxCC task authorization path. Reference: Webex Connect Help, Webex CC Task Integration Nodes and Node Authorizations; Resolve Conversation - WXCC.

RONA must expire before voicemail answers. Cisco's voice channel guidance for Webex Contact Center and Webex Calling explains that, when agents use Webex Calling endpoints, unanswered contact center calls should be redirected back to the contact center queue before the endpoint's voicemail rule answers. If voicemail answers first, the customer call is effectively consumed by the agent's mailbox instead of being requeued for the next available agent. Setting the RONA timer shorter than the voicemail ring interval causes the contact center platform to classify the offered contact as no-answer and requeue it. Direct calls to the agent still follow the normal Webex Calling voicemail configuration, so voicemail continues to work for non-contact-center calls. Making RONA longer than voicemail is exactly the wrong direction. Two lines may help operational separation but are not required for this behavior. Disabling voicemail would break the stated requirement that direct unanswered calls roll to voicemail. Reference: Cisco Help, Set up voice channels for Webex Contact Center.

A widget that executes background logic without presenting a visible user-interface panel belongs in the Headless area of the Agent Desktop layout. Cisco's custom desktop layout framework separates visible layout regions, such as panels or persistent areas, from headless widgets that run logic in the background. The requirement says the custom widget should trigger a CRM screen pop when an SMS arrives. That is event-driven background behavior; the agent does not need to see a standalone widget tab or panel for the code to work. A Panel object would be appropriate for visible content placed in the desktop interface. Navigation is used for navigation entries or visible application areas. Persistent is for UI that remains visible across desktop contexts. Headless is deliberately designed for invisible logic, event listeners, and background integrations that react to contact events, making it the correct object for this SMS-triggered CRM screen-pop logic. Reference: Cisco Help, Create custom desktop layout; Webex Contact Center Desktop developer documentation.

The Exclusive multimedia profile type is used when an agent must handle only one interaction at a time. Cisco's multimedia-profile model controls how many simultaneous contacts an agent can receive and how different media types are blended. A blended profile can allow multiple channels, and a blended real-time profile is designed for voice plus real-time digital interactions under concurrency rules. Voice Only would restrict agents to voice and would not satisfy a team that handles voice, email, and chat. The scenario is not asking to remove digital channels; it says a few agents cannot focus on multiple interactions. Exclusive solves that by allowing the agent to work one contact regardless of channel, preventing simultaneous assignments that could reduce quality or agent performance. This is a tenant and desktop-experience configuration decision, not a queue routing problem. The agent can still be eligible for the configured channels, but the desktop capacity model keeps workload to one active interaction. Reference: Cisco Help, Webex Contact Center Setup and Administration Guide; Manage desktop profiles.

A Webex bot conversation must preserve conversation context between incoming messages. If each incoming message starts the Webex Connect flow from the beginning, the flow is treating every webhook event as a new start event instead of waiting for the next message from the same user. The Receive node is the correct mechanism for continuing the flow after the initial webhook trigger. It should use a custom event that matches the user email, because the user identity is what links the next inbound message to the same conversation path. Matching the bot email would identify the bot endpoint, not the specific human conversation participant. Creating multiple webhooks for different steps would fragment the design and still would not preserve state cleanly. A Call Flow node is useful for modularizing logic but does not by itself wait for and correlate the user's next message. The Receive node with the user-email custom event keeps the conversation from restarting. Reference: Webex Connect Help, Receive Node and flow debugging; Webex Connect Webex Chat/Webex Engage documentation.

Repository: Customer Session Record.

Segment Data: Contact Start Timestamp and Queue Duration.

Profile Variable: ANI, Agent Login, and Final Queue Name.

The report needs one row for each call, the caller's number, queue timing, and final agent. Cisco Analyzer separates data into repositories and data classes. Customer Session Record is the proper repository because it represents the end-to-end customer contact session and contains the contact session identifier needed for a list of calls. Contact Start Timestamp and Queue Duration are segment-level metrics that describe when the contact began and how long it waited in the queue. ANI, Agent Login, and Final Queue Name are profile or reporting variables that identify the caller's number, the final handling agent, and the queue outcome. Burn Index, abandoned service-level count, and idle code fields are not part of this requested report. Agent Activity Record would be appropriate for agent state history, but this report is customer-contact centered. Customer Activity Record is useful for detailed contact activities, but the drag-and-drop target asks for the repository and field groupings shown. Reference: Cisco Help, Cisco Webex Contact Center Analyzer User Guide; Webex Contact Center Analyzer Stock Reports.

Webex Connect provides two relevant troubleshooting tools for failed transactions: Debug Console and Export Logs. Cisco's Webex Connect Debug Console documentation states that it displays transaction details and historical logs for API, flow, and rule executions, including status, timestamps, service name, transaction source, and errors. That makes it the interactive tool for investigating a specific failure path. Export Logs is the bulk-download mechanism for inbound and outbound transaction logs across channels and can cover the last seven days or more depending on log availability and tenant configuration. Reports are useful for aggregated channel performance and trends, but not for pulling all failed transactions from a specific service with enough technical detail. Watchtower is not the primary transaction log export mechanism in the option set. Templates are reusable message or channel assets, not troubleshooting tools. For a seven-day failure investigation, Debug Console plus Export Logs is the correct pair. Reference: Webex Connect Help, Debug Console; Webex Connect Help, Export Logs.

The call reaches the initial greeting and accepts an IVR option, so the Local Gateway and inbound call delivery are working at least through the first media and signaling stage. The failure occurs after the caller makes a menu selection, which points at the flow branch or the next activity after that menu, not at the trunk itself. Cisco's Flow Designer documentation explains that flows define what happens at each stage of a call, including prompts, menu handling, queueing, transfers, and disconnect behavior. If a branch after the selected option has an invalid Queue Contact configuration, an invalid transfer destination, an unhandled error, or an incorrect terminal node, the customer may hear the greeting and then be disconnected. Analyzer can confirm call records after the fact, but the fastest root-cause path is to inspect the flow configuration and the branch selected by the caller. Queue or channel association issues would usually prevent reaching the intended IVR stage. Reference: Cisco Help, Build and manage flows with Flow Designer; Understand Routing and Queueing in Webex Contact Center.

A chat digital channel handled by Webex Contact Center agents needs a channel object of type Chat and an asset assigned to that channel. Cisco's digital channel setup model uses assets to represent external channel identities, such as a web chat asset, email asset, SMS asset, or social asset. The channel then connects that asset to Webex Contact Center routing so the conversation can be created, queued, and delivered to agents. Assigning a phone number is relevant to voice or SMS-style channel designs, not to a Web Chat asset. Creating an Email channel or Social Channel would build the wrong media type and would not make a chat widget route as chat. The two required steps therefore match the platform object model: create a channel with Chat as the channel type and assign the appropriate asset to that channel. Once that is done, flows and Queue Task nodes can route the chat to Webex Contact Center agents. Reference: Cisco Help, Set up digital channels in Webex Contact Center; Webex Connect Help, Livechat.

A Web Chat widget that is visible in configuration but does not load on the company website commonly points to an asset-domain mismatch. Cisco Webex Connect live chat assets require the website domain to be configured for the asset so the platform can validate where the widget is embedded. The exhibit shows the browser-side failure after widget code is implemented, which is consistent with the site domain not matching the domain configured for the Web Chat Asset. Missing Webex Connect flow configuration usually causes chat handling or routing failures after a chat is initiated, not the widget failing to load. A firewall block to a widget domain is possible in the real world, but the question says the engineer sees output in the browser while investigating Webex Contact Center, and the Cisco configuration control involved is the website domain on the asset. Content Security Policy allow-listing in Webex Contact Center is for desktop/embedded content behavior, not the primary asset-domain validation for web chat loading. Reference: Webex Connect Help, Livechat; Cisco Help, Set up digital channels in Webex Contact Center.

userId: $.data.users[?(@.phoneNumber == '+1 (555) 123-4567')].userId

currentPage: $.data.currentPage

The JSONPath mapping must match the structure shown in the API response. The userId variable is not a simple top-level property; it sits inside the users array. The expression must filter the users array for the object whose phoneNumber equals +1 (555) 123-4567 and then return that object's userId. That is why the filtered JSONPath expression using $.data.users[?(@.phoneNumber == '+1 (555) 123-4567')].userId is the correct mapping. The currentPage variable is directly under data, so the correct expression is $.data.currentPage. Expressions such as $.currentPage miss the data wrapper, and $.data.currentPage.number assumes currentPage is an object with a number property, which the response does not show. $.data.user[0] .userId is also wrong because the array name in the response is users, not user, and it would take the first user rather than the matching phone number. Reference: Webex Connect Help, Custom Node Integration; Webex Connect flow data parsing guidance.

WhatsApp and SMS are premium digital channels in the Webex Contact Center licensing model. Cisco's Webex Contact Center data sheet distinguishes Standard Agent and Premium Agent capabilities. Standard Agent includes core contact center functions and agent-assisted chat and email, while Premium Agent adds broader digital communication channels such as SMS, social channels, multichannel analytics, and supervisor monitoring capabilities. The scenario says the agent can receive Chat and Voice, so the agent is already provisioned for basic voice and chat handling. The missing capabilities are specifically WhatsApp and SMS, which are part of the higher digital-channel entitlement. An enhanced license is not the relevant license category in the Cisco Webex Contact Center agent-type model. The desktop layout can affect UI presentation, but it would not by itself entitle the agent to receive those channel types. The missing configuration is therefore the Premium license. Reference: Cisco Webex Contact Center Data Sheet; Cisco Help, Set up digital channels in Webex Contact Center.

Control Hub normalizes Webex Calling and Webex Contact Center numbers into E.164 format, and Cisco's voice channel setup guidance explains that numbers routed from Cloud Connected PSTN or Local Gateway are provisioned in +E.164 format for Control Hub. The fully qualified +1-450-783-2223 format is therefore valid. Cisco interfaces also accept common national display formatting for number entry in many workflows, such as parentheses around the area code, which corresponds to (450) 783-2223 in the option set. The bracketed version, hash-prefixed value, and dotted format are not acceptable telephony number formats for configuring a Webex Contact Center entry point number. The key is that the number must represent a valid PSTN telephone number that Control Hub can store and map to the entry point. The +E.164 version is the canonical final representation; the national style is an accepted entry/display form. Reference: Cisco Help, Set up voice channels for Webex Contact Center; Set up voice settings for Webex Contact Center.