00 · Header
T4 · Webex Contact Center Enterprise
CVP & VXML IVR
Unified Customer Voice Portal is the VoiceXML IVR in the Unified CCE design guides. This room keeps the standalone model, the comprehensive model, and the Webex CCE hosting sentence in separate boxes.
01 · Executive summary
Five lines, then why it matters
- The VXML Server is a J2EE-compliant application server for dynamic VoiceXML applications. It can be installed without the Call Server. [cite:2]
- Standalone without reporting uses the VXML Server (Standalone) option. Standalone with reporting uses the VXML Server option and adds a Call Server and a Reporting Server. [cite:1]
- Comprehensive combines Call Director using SIP and VRU-Only. Basic ports play .wav files and collect DTMF. Advanced ports add ASR, TTS, and VXML Server applications. [cite:1]
- From Unified CVP 11.5(1), the Call Server IVR service lives on the VXML Server, which builds the VXML pages for the microapplications. [cite:2]
- The January 2025 Webex CCE note says custom CVP applications can be hosted on Webex CCE. That sentence is older than 12 months. [cite:5] re-check
02 · Architecture map
Two models, two legs
- 1Standalone: VVB HTTP to VXML Server
- 2Comprehensive: switch leg and VRU leg share one Call Server
Mermaid source (not rendered; the SVGs are the pictures)
flowchart LR PSTN[PSTN or CUBE] -->|SIP invite| VVB[Cisco VVB] VVB -->|HTTP| VXML[VXML Server] VXML -->|VoiceXML| VVB GW[Ingress gateway switch leg] --> CS[Call Server] CS --> VRU[Cisco VVB VRU leg]
03 · Core concepts
What the CVP 15 guide separates
A J2EE-compliant application server for creating and deploying dynamic VoiceXML applications. The standalone install omits the Call Server and is built for self-service. [cite:2]
Applications are created in Call Studio and deployed to the VXML Server. The configuration guide’s standalone procedure says to deploy the application as a zip file. CVPSNMPLogger is enabled by default on a new deployed application. [cite:1]
Without reporting, choose VXML Server (Standalone) in the Operations Console. With reporting, choose VXML Server, and the Call Server routes messages between components. Calls arrive through Cisco VVB and run VoiceXML on the VXML Server. Cisco VVB performs ingress. [cite:1]
The Solution Design Guide, updated March 15, 2025, says the Comprehensive call flow is the only one you can use in a Reference Design. Standalone VXML Server, Call Director, and VRU-Only are listed as non-reference alternates. [cite:3] re-check
SIP calls that use Unified CVP micro-applications use the IVR Service of the Call Server that holds the switch leg. VoiceXML fetches go to that Call Server. Micro-application VoiceXML traffic must return only to the same Call Server. Comprehensive calls always use the same Call Server for the switch leg and the VRU leg. [cite:1]
Port license and VRU type
| Item | What the guide prints | Cite |
|---|---|---|
| Basic comprehensive ports | .wav files and DTMF input | [cite:1] |
| Advanced comprehensive ports | ASR/TTS servers and VXML Server applications | [cite:1] |
| Network VRU | Type 10 serves both the switch leg and the VRU leg. Connect with the SendToVRU node in ICM Script Editor. | [cite:1] |
| ICMH view | Unified ICMH sees the two legs as a single call routed through different peripherals. | [cite:1] |
| IVR service move | From 11.5(1), the Call Server IVR service is on the VXML Server. Configure IVR settings on the IVR tab. | [cite:2] |
| Session invalidation | The VXML Server user guide recommends keeping session_invalidation_delay at 30 seconds in global_config.xml. The file is edited by hand under %CVP_HOME%\VXMLServer\conf. | [cite:4] re-check |
04 · Ecosystem
Sisters around the IVR
Glossary
- VXML Server
- J2EE server that runs dynamic VoiceXML applications. Standalone install does not include the Call Server. [cite:2]
- Call Studio
- The tool that creates the application deployed to the VXML Server. [cite:1]
- Cisco VVB
- Virtualized Voice Browser. In the standalone figure it receives the SIP invite and requests VoiceXML over HTTP. [cite:1]
- Switch leg
- Comprehensive leg where the gateway does TDM-to-VoIP and call switching. [cite:1]
- VRU leg
- Comprehensive leg where Cisco VVB provides VRU voice treatment. [cite:1]
- Micro-application
- VoiceXML pages the VXML Server creates for Unified CVP microapplications after the 11.5(1) move. [cite:2]
- SendToVRU
- ICM Script Editor node the comprehensive ICME section names for connecting the call to the Network VRU. [cite:1]
- Type 10
- Network VRU type that serves both the switch leg and the VRU leg in the comprehensive ICME model. [cite:1]
- ReqICMLabel
- Call Studio decision element used when a standalone script looks up a label in ICM. [cite:1]
- Flow Designer
- The build-and-manage article is for Webex Contact Center flows. It is not the Call Studio chapter. [cite:6]
- Hybrid IVR
- The July 2023 Webex CCE note: traditional ASR/TTS/CRM plus Dialogflow CX, with some nodes on premises and some in the cloud. [cite:5] re-check
- CVP on Webex CCE
- January 2025 what’s-new: custom code applications, including CVP applications, can be hosted on Webex CCE. [cite:5] re-check
Mind map
Mermaid source (not rendered)
mindmap
root((Unified CVP))
Standalone
Comprehensive
Call Studio
Cisco VVB
Sister matrix
| Sister | What the cited page says | Why it matters here | Config touchpoint | Typical failure | Cite |
|---|---|---|---|---|---|
| Workforce management | py6u9h lists WFO feature SKUs for Webex Contact Center Enterprise, CCE, and CCX. | WFM is not a CVP call-flow model. | The SKU table in that article. | Sizing IVR ports from a WFM interval. | [cite:7] |
| Quality management and recording | The CVP call-flow chapter does not print a QM retention number. | Prompt recording and agent recording are different stores. | Read the Enterprise quality-management guide for the release you run. | Quoting a Calling retention figure as CVP reporting retention. | [cite:1] |
| E911, RAY BAUM, Kari, RedSky | The CVP call-flow chapter does not configure emergency calling. | An IVR label is not a dispatchable location. | Read the Webex CCE 9-1-1 section the what’s-new page points at, and the phone’s emergency path. | Treating a CVP transfer as proof of 911 compliance. | [cite:5] re-check |
| Analytics and reporting | Standalone reporting requires a Call Server and a Reporting Server. CUIC stock reports are a different guide. | CVP reporting and CUIC are adjacent, not the same screen. | Operations Console reporting flag, then T4-R07 for CUIC. | Expecting Live Data refresh inside the VXML log. | [cite:1] |
| Salesforce | Not named in the CVP call-flow chapter read here. | CRM screen-pop is a desktop integration. | Read the CRM guide for the desktop you deployed. | Putting a CRM URL in the VXML app and calling that the Finesse gadget. | [cite:6] |
| Dynamics 365 | Not named in the CVP chapter. Cisco’s multi-tenant connector is not Microsoft’s Dynamics 365 Contact Center. | The name collision still applies. | Read the connector guide for the product on the subscription. | Installing the multi-tenant connector as a CVP element. | [cite:6] |
| ServiceNow | Not named in the CVP chapter. | Same boundary as the other CRM rows. | Read the ServiceNow guide for the release you run. | Using a multi-tenant ServiceNow article as the VXML design. | [cite:6] |
| Virtual agents and AI Assistant | July 2023 what’s-new describes Hybrid IVR with Dialogflow CX. The Control Hub AI Assistant article is a multi-tenant Webex Contact Center article. | Name the product on the article. | Hybrid IVR node choice is in the what’s-new example. AI Assistant toggles are in the multi-tenant article. | Turning on a multi-tenant assistant and calling it a CVP element. | [cite:5] re-check |
| IVR and self-service | This room’s subject. Standalone is self-service. Comprehensive adds queuing and VoIP routing to agents. | The model decides whether ICM owns the queue. | Operations Console call-flow choice and Call Studio. | Queuing in a standalone app that the design guide says has no Unified CCE queuing control. | [cite:1] [cite:3] |
| Digital channels | VoiceXML is voice. Webex CCE digital channels are named on the what’s-new page as email, chat, SMS, and later WhatsApp and Facebook Messenger. | A VXML app does not become chat. | Manage Digital Channels gadget, cited from the what’s-new page. | Promising SMS from a Call Studio audio element. | [cite:5] re-check |
| Identity and SSO | The CVP chapter does not define the agent IdP. | Call Studio login and agent desktop login are different consoles. | Read identity for the Webex org in Control Hub, and the CVP Operations Console account separately. | Reusing a Finesse password as the Operations Console password in a runbook. | [cite:1] |
Integration edges
| From | To | Mechanism | What moves | Cite |
|---|---|---|---|---|
| Ingress gateway or CUBE | Cisco VVB | SIP invite | The self-service trigger number configured on VVB | [cite:1] |
| Cisco VVB | VXML Server | HTTP | URL request, then VoiceXML instructions | [cite:1] |
| VoiceXML | ASR, TTS, media server | References inside the instructions | Voice input, TTS, or .wav playback | [cite:1] |
| Call Studio | VXML Server | Deployed application | A zip the configuration procedure tells you to deploy | [cite:1] |
| ICM Script Editor | Network VRU | SendToVRU | The comprehensive ICME connection to Type 10 | [cite:1] |
| Call Server IVR service | VXML Server | Service move at 11.5(1) | Microapplication VXML pages | [cite:2] |
| Standalone with ICM lookup | ICM | ReqICMLabel | A label lookup without the chapter calling that comprehensive queuing | [cite:1] |
| Webex CCE host | CVP application | What’s-new hosting note | Custom VXML and Call Server apps moved onto Webex CCE | [cite:5] re-check |
Bridges
| CVP idea | Where to read the neighbor | Peer label | Cite |
|---|---|---|---|
| Call Studio application | Multi-tenant flows are built in Flow Designer. Open nhovcy4 for that canvas. | Amazon Connect and Genesys flow builders are orientation labels. No equivalence is claimed. | [cite:6] |
| Comprehensive queue and transfer | On-premises UCCE uses SendToVRU and Script Editor. The design guide limits Reference Designs to Comprehensive. | Teams Phone is not this IVR. | [cite:1] [cite:3] |
| Hosted CVP on Webex CCE | The January 2025 note is the cloud sentence. It does not rewrite the CVP 15 call-flow chapter. | No peer IVR parity is published on help.webex.com. | [cite:5] |
Future hooks
- Canon plan: when a newer CVP configuration guide replaces Release 15.0(1), re-read the standalone figure before teaching the SIP invite step.
- The March 15, 2025 design-guide sentence that Comprehensive is the only Reference Design call flow stays re-check until that chapter is newer than 12 months.
- Dialogflow project steps are not in the July 2023 what’s-new paragraph. Read the CCAI guide before you teach a bot project.
Ecosystem troubleshooting
| Symptom | Likely mix-up | Check | Move | Cite |
|---|---|---|---|---|
| A Reference Design packet uses standalone queuing | Non-reference flow used where the design guide allows only Comprehensive | Does the packet say Reference Design? | Move queuing to Comprehensive, or mark the design non-reference. | [cite:3] |
| VoiceXML hits a second Call Server | Micro-application rule ignored | Which Call Server owns the switch leg? | Return VoiceXML only to that Call Server. | [cite:1] |
| The runbook says build the IVR in Flow Designer | nhovcy4 was pasted onto Unified CVP | Which product is on the subscription? | Call Studio for this room. Flow Designer for multi-tenant Webex Contact Center. | [cite:6] |
| Chat is drawn as a VXML element | Digital channels were merged into voice | What’s-new channel list | Leave chat on the Manage Digital Channels gadget. | [cite:5] |
05 · Flow
The standalone figure, then the comprehensive legs
| Step | From | To | Protocol | Notes | Cite |
|---|---|---|---|---|---|
| 1 | PSTN or service provider | Ingress gateway or CUBE | Call delivery | Standalone figure, first line. | [cite:1] |
| 2 | Gateway | Cisco VVB | SIP invite | Trigger number configured on VVB for the self-service application. | [cite:1] |
| 3 | Cisco VVB | VXML Server | HTTP | URL request. | [cite:1] |
| 4 | VXML Server | Cisco VVB | VoiceXML | Instructions may reference ASR/TTS and media-server .wav files. | [cite:1] |
| 5 | Ingress gateway | Call Server | SIP switch leg | Comprehensive: gateway does TDM-to-VoIP and call switching. | [cite:1] |
| 6 | Cisco VVB | Caller | VRU leg | VRU voice treatment. May include ASR/TTS. | [cite:1] |
| 7 | VVB | Same Call Server | VoiceXML fetch | Micro-applications return only to the Call Server that holds the switch leg. | [cite:1] |
| 8 | ICM script | Network VRU Type 10 | SendToVRU | Comprehensive ICME connection named in the guide. | [cite:1] |
06 · Config
Operations Console steps the guide names
- Decide the model. Standalone without reporting: Device Management path that selects VXML Server (Standalone). Standalone with reporting: VXML Server, plus a Call Server and a Reporting Server. [cite:1]
- For a Cisco VVB standalone deployment, define the VXML Server applications, configure the base gateway and VVB settings, and configure the dial-peer that triggers the self-service application. [cite:1]
- Create the application in Call Studio and deploy it to the VXML Server. The procedure says to deploy it as a zip file. [cite:1]
- Enable loggers in Call Studio. CVPSNMPLogger is on by default for a new deployed application. [cite:1]
- If the script must ask ICM for a label, use the ReqICMLabel element. Pass data in Peripheral Variables 1–10. The guide says those values are taken as is. [cite:1]
- For comprehensive ICME, configure the IVR service to work with Cisco VVB. Use SendToVRU. Keep both legs on the same Call Server. [cite:1]
- IVR settings for microapplications are on the VXML Server IVR tab, because the IVR service moved at 11.5(1). [cite:2]
Screenshot slot: Operations Console call-flow choice, with hostnames redacted.
07 · Limits
Numbers and rules that have a page
| Item | Value | Source | Verified? |
|---|---|---|---|
| Standalone minimum, no reporting | VXML Server, Call Studio, and a gateway | [cite:1] | Quoted |
| Standalone with reporting | Also a Call Server and a Reporting Server | [cite:1] | Quoted |
| Reference Design call flow | Comprehensive only | [cite:3] | re-check Guide updated March 15, 2025 |
| Basic versus Advanced | Basic: .wav and DTMF. Advanced: ASR/TTS and VXML Server applications | [cite:1] | Quoted. Guide updated December 12, 2025 |
| Micro-app VoiceXML target | Same Call Server as the switch leg | [cite:1] | Quoted |
| session_invalidation_delay | Recommended default 30 seconds | [cite:4] | re-check |
| Custom SIP headers, standalone | Initial INVITE only, not reinvite. August 2023 what’s-new. | [cite:5] | re-check |
| Non-reference sizing table | The design guide says those limits are for non-reference designs only. Do not size a Reference Design from that table. | [cite:3] | re-check |
08 · Troubleshooting
Wrong model, wrong server, wrong tool
| Symptom | Likely cause | Evidence | Fix | Cite |
|---|---|---|---|---|
| Reporting is empty on a standalone app | The (Standalone) option was selected | That option does not require a Reporting Server | Use the VXML Server option and add Call Server plus Reporting Server | [cite:1] |
| Self-service never starts | SIP invite trigger does not match VVB | Guide: gateway sends the trigger configured for the self-service application | Match the dial-peer to that trigger | [cite:1] |
| Prompts play from the wrong Call Server | VoiceXML was aimed at a second server | Micro-application traffic returns only to the switch-leg Call Server | Point fetches at that Call Server. Comprehensive uses one Call Server for both legs | [cite:1] |
| ASR is licensed and still silent | Port level is Basic | Basic is .wav and DTMF. Advanced adds ASR/TTS | Confirm Advanced port licensing before you debug the speech server | [cite:1] |
| A Reference Design review rejects the IVR | Standalone or VRU-Only was used | Design guide: Comprehensive is the only Reference Design call flow | Change the model or label the design non-reference | [cite:3] |
| Queue treatment never connects | SendToVRU is missing | Comprehensive ICME names that node for the Type 10 VRU | Add SendToVRU in Script Editor | [cite:1] |
| ICM lookup element returns nothing useful | Peripheral variables were transformed | The guide says variables 1–10 are taken as is | Pass the values unchanged | [cite:1] |
| End-of-call logging errors | session_invalidation_delay set to 0 | User guide: too small a delay breaks end-of-call logging | Keep the recommended 30 seconds unless you test a change | [cite:4] |
| Custom header missing on reinvite | Expected, on the August 2023 note | Headers are on the initial INVITE only | Read the header on the first INVITE | [cite:5] |
| IVR tab is missing on the Call Server | Looking at the pre-11.5(1) place | IVR service moved to the VXML Server | Configure the IVR tab on the VXML Server | [cite:2] |
09 · Self-question ladder
Twelve rungs
L0What is the VXML Server?
A J2EE-compliant application server for dynamic VoiceXML applications. It can run without the Call Server. [cite:2]
L1What breaks if you want reports and you picked VXML Server (Standalone)?
That option does not require a Call Server or a Reporting Server. Reporting needs the other option plus both servers. [cite:1]
L1Which three components does standalone require before reporting is added?
VXML Server, Call Studio, and a gateway. [cite:1]
L2What are the four steps in the standalone VVB figure?
PSTN or provider to the ingress gateway or CUBE. SIP invite to VVB. HTTP request to the VXML Server. VoiceXML back to VVB, optionally pointing at ASR, TTS, or .wav files. [cite:1]
L2What does each comprehensive leg do?
Switch leg: gateway does TDM-to-VoIP and call switching. VRU leg: Cisco VVB does VRU voice treatment. [cite:1]
L2Why must micro-application VoiceXML return to one Call Server?
The IVR Service of the Call Server that has the switch leg receives the fetches. The guide says the traffic must return only to that Call Server. [cite:1]
L3How do you prove a Reference Design is using the allowed CVP flow?
The design guide says Comprehensive is the only call flow you can use in a Reference Design. Standalone is listed under non-reference. [cite:3] re-check
L3Basic ports are quiet when the caller speaks. What do you check?
Basic supports .wav and DTMF. ASR and TTS are Advanced. [cite:1]
L3Where did the Call Server IVR service go?
To the VXML Server, beginning with 11.5(1). Microapplication pages are created there. [cite:2]
L4How is comprehensive different from multi-tenant Flow Designer?
This room’s script tool is Call Studio, and the queue handoff the guide names is SendToVRU. Flow Designer is the Webex Contact Center flow article. [cite:1] [cite:6]
L4What does the January 2025 Webex CCE note add?
Custom code applications can be hosted on Webex CCE, including a move of CVP applications that use VXML and Call servers. The note is older than 12 months. [cite:5] re-check
L5What constraint stops you from treating standalone as a full contact-center queue?
The design guide describes standalone as a VRU with no integration to Unified CCE for queuing control or subsequent call control, and it excludes that flow from Reference Designs. [cite:3] re-check
10 · Lab
Paper lab: label the model before you draw the ports
11 · Quiz
Twelve checks
Standalone without reporting requires:
- Call Server and Reporting Server
- VXML Server (Standalone) option, and no Call Server or Reporting Server
- SendToVRU
- Flow Designer
Reveal
B. [cite:1]
The standalone minimum, before reporting, is:
- VXML Server, Call Studio, and a gateway
- Router and Logger only
- CUIC and Finesse
- Two Call Servers
Reveal
A. [cite:1]
The gateway sends a SIP invite to Cisco VVB. What must that invite carry, according to the standalone figure?
Reveal
The trigger number configured in Cisco VVB for the self-service application. [cite:1]
Cisco VVB gets VoiceXML instructions by:
- An HTTP URL request to the VXML Server
- A CUIC export
- A Finesse gadget
- BGP
Reveal
A. [cite:1]
Comprehensive Basic ports support:
- .wav files and DTMF
- ASR and TTS only
- Digital chat
- Live Data
Reveal
A. Advanced adds ASR/TTS and VXML Server applications. [cite:1]
Micro-application VoiceXML is fetched from a different Call Server than the switch leg. What does the guide require?
Reveal
VoiceXML for micro-applications must return only to the same Call Server as the switch leg. [cite:1]
The only CVP call flow the design guide allows in a Reference Design is:
- Standalone
- Call Director
- Comprehensive
- VRU-Only
Reveal
C. The chapter was updated March 15, 2025, so this stays re-check. [cite:3]
Draw two legs. Label which one is the gateway and which one is Cisco VVB.
Reveal
Switch leg on the gateway. VRU leg on Cisco VVB. [cite:1]
From CVP 11.5(1), microapplication VXML pages are created by:
- The VXML Server
- CUIC
- Finesse
- Partner Hub
Reveal
A. The Call Server IVR service moved to the VXML Server. [cite:2]
A script needs an ICM label from a standalone Call Studio app. Which element does the guide name?
Reveal
ReqICMLabel. Peripheral Variables 1–10 are taken as is. [cite:1]
SendToVRU connects the call to:
- The Network VRU
- A Finesse workflow
- Edge Connect
- A Calling hunt group
Reveal
A. Type 10 serves both legs in the comprehensive ICME section. [cite:1]
Someone cites Flow Designer as the Unified CVP builder. Which article did they open?
12 · Audio
Slots for Studio
Transcript slot
Studio fills this from the cites. The prompt is the spoken outline.
Transcript slot
Studio fills this from the cites. The prompt is the spoken outline.
Transcript slot
Studio fills this from the cites. The prompt is the spoken outline.
13 · Interview
Oral answers
30 seconds. Unified CVP has a standalone self-service model and a comprehensive switch model. Standalone needs the VXML Server, Call Studio, and a gateway. Reporting adds a Call Server and a Reporting Server. Comprehensive is the Reference Design flow.
2 minutes. In the standalone figure the call hits an ingress gateway or CUBE, the gateway sends a SIP invite to Cisco VVB with the trigger, VVB requests VoiceXML over HTTP, and the instructions can point at ASR, TTS, or .wav files. Comprehensive has a switch leg on the gateway and a VRU leg on VVB. Micro-application VoiceXML returns only to the Call Server that owns the switch leg. Type 10 and SendToVRU are the ICME names. Basic ports are .wav and DTMF. Advanced adds speech and VXML applications.
30 seconds, the tool. I build the app in Call Studio. Flow Designer is the multi-tenant Webex Contact Center canvas, not this chapter.
2 minutes, the cloud sentence. A January 2025 what’s-new line says Webex CCE can host custom CVP applications. I keep that sentence marked re-check, and I do not let it erase the CVP 15 call-flow chapter. Hybrid IVR, from July 2023, is the note that mixes on-premises ASR/TTS with Dialogflow CX. That date is also re-check.
What you will not say. You will not size a Reference Design from the non-reference limits table. The design guide says those limits apply to non-reference designs only.
14 · Citations
Ledger
Retrieved 2026-10-14. Study notes from public sources.
- Configuration Guide for Cisco Unified Customer Voice Portal, Release 15.0(1), chapter Unified CVP Call Flow Models — cisco.com — updated December 12, 2025 — CVP 15 call flow models. Standalone variants, VVB sequence, comprehensive legs, Basic and Advanced, same Call Server, Type 10, SendToVRU, Call Studio deploy, ReqICMLabel.
- Configuration Guide for Cisco Unified Customer Voice Portal, Release 15.0(1), chapter VXML Server Configuration — cisco.com — VXML Server configuration. J2EE server. IVR service moved to the VXML Server at 11.5(1).
- Solution Design Guide for Cisco Unified Contact Center Enterprise, Release 15.0(1), chapter Non-Reference Designs — cisco.com — updated March 15, 2025 — Non-reference designs. Comprehensive is the only Reference Design call flow. re-check
- User Guide for Unified CVP VXML Server and Unified CVP Call Studio, Release 15.0(1), VXML Server configuration — cisco.com — global_config.xml. Hand edit. Recommended session_invalidation_delay of 30 seconds. re-check
- What’s new for administrators in Webex Contact Center Enterprise — help.webex — article nhy3hvdb — help.webex.com article nhy3hvdb. January 2025 custom CVP hosting. July 2023 Hybrid IVR. August 2023 custom SIP headers on the initial INVITE. September 2022 pointer to the Webex CCE 9-1-1 section. Digital-channel list on the same page. re-check
- Build and manage flows with Flow Designer — help.webex — article nhovcy4 — help.webex.com article nhovcy4. Cited as the multi-tenant flow article, not as Call Studio.
- Webex WFO: Feature Specific SKUs — help.webex — article py6u9h — help.webex.com article py6u9h. Scoped to Webex Contact Center Enterprise, Contact Center Enterprise, and Contact Center Express.
15 · Re-engineer later
Still open
- Open questions: the VXML user-guide update date for the 30-second recommendation; Dialogflow project steps beyond the July 2023 paragraph.
- Facts still marked re-check: the March 15, 2025 Reference Design sentence, session_invalidation_delay, and every what’s-new paragraph dated before October 2025.
- Assets missing: Operations Console screenshot, exported SVGs, audio.
- Ideas for v1.0: a one-page model card generated from the call-flow chapter at review time.
- Next review: re-read the non-reference chapter and nhy3hvdb before teaching those sentences as current.
Sources and go deeper
Checked links were opened this month. A confirm row has no address because that page was not opened.
- Wikipedia Webex (Wikipedia) last checked 2026-10
- Vendor doc Webex Help Center last checked 2026-10
- DevDocs Webex developer documentation last checked 2026-10
- DevDocs Webex developer getting started last checked 2026-10
- Community Webex community last checked 2026-10
- SRND Cisco Collaboration design zone last checked 2026-10
- RFC RFC 3261 SIP: Session Initiation Protocol last checked 2026-10
- Port table IANA service name and port number registry last checked 2026-10
- Port table Port reference for Webex Calling last checked 2026-10
- Wikipedia Call centre (Wikipedia) last checked 2026-10
- Wikipedia Interactive voice response (Wikipedia) last checked 2026-10
- Release notes What's new for administrators in Webex Contact Center last checked 2026-10
- Vendor doc CVP 15 call flow models last checked 2026-10
- Vendor doc VXML Server configuration last checked 2026-10
- Vendor doc Non-reference designs last checked 2026-10
- Vendor doc global_config.xml last checked 2026-10
- Vendor doc help.webex.com article nhy3hvdb last checked 2026-10
- Vendor doc help.webex.com article nhovcy4 last checked 2026-10
- Vendor doc help.webex.com article py6u9h last checked 2026-10
sources.json for this page.