The Start Media Stream activity and what feeds on it

Verified 2026-09-05 · 13 claims · sources tier 2 · 1 disputed

Also known as Start Media Stream, consult leg, suggested responses.

Cisco states that media streaming facilitates call transcription, summarization, suggested responses, and sentiment analysis, while naming no recipient of the stream 3. The feature requires administrative privileges to modify flows and requires the organization to be a customer of the Next Generation Media Platform 9.

How it works

The Start Media Stream activity exposes 2 configurable fields: Activity Label and Activity Description, with no destination, credential, or address field 13. It carries a system-enforced self-loop limit of 20 per interaction 11. Neither assigned source documents any counterpart activity or method to stop a media stream once started, and the string Stop Media Stream does not occur in either 7.

To scope streaming to specific queues, Cisco's prescribed pattern relies on a boolean global variable defaulting to False 10. A Set Variable activity sets this variable to True prior to the Queue Contact activity, and a Condition activity subsequently evaluates it to connect its True path to the Start Media Stream activity 10. Sources disagree on the event flow trigger, as the media streaming procedure instructs administrators to place the Condition activity after an AgentAnswered event, but that event name does not appear in the Flow Designer event handler list 1.

Cisco notes that queue-level conditional logic is unnecessary if streaming is desired for all calls, but never publishes how to enable it for all calls 2. In the field, documentation opens by naming streaming as a single feature facilitating 4 tasks, but then uses the word transcription throughout the procedure where media streaming is being configured 12.

Call legs and compliance properties

Cisco states that media streaming does not work on the consult leg, citing consult and transfer calls as examples 8. The documentation does not state what happens to an active stream when a consult begins, leaving continuing while excluding the consult leg, pausing, and ending as possibilities consistent with the text 4.

The documentation contains no instructions regarding notifying the caller or agent that a stream is running, making no mention of consent, notice, legal basis, or compliance 5. Furthermore, the documentation provides no retention period, storage location, or deletion behavior for streamed media or derived data, nor does it define authentication, authorization, or encryption properties for the stream 6.

See also

See also The Webex Contact Center Flow Designer activity set. See also Which Flow Designer activities can send customer data outside the platform. See also Webex Contact Center system limits reference.

Applicability

Across the claims in this article, the evidence covers Cisco Webex Contact Center, verified as of 2026-09-05. The deployment model is not covered by any claim in this article. Media streaming requires an organization to be a customer of the Next Generation Media Platform and requires administrative privileges to modify flows 9.

What remains uncertain

Which service receives the media stream is not covered by any claim in this article. How to enable streaming for all calls is not covered by any claim in this article. What happens to a running stream when a consult begins is not covered by any claim in this article. Whether transcription and media streaming are one control is not covered by any claim in this article.

WarmTransfer. (2026, September 5). The Start Media Stream activity and what feeds on it. WarmTransfer. https://warmtransfer.net/knowledge/wxcc-media-streaming

@misc{warmtransfer-wxcc-media-streaming,
  title  = {The Start Media Stream activity and what feeds on it},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/wxcc-media-streaming},
  note   = {Verified 2026-09-05}
}