00 Β· Header
Scripting & ICM Routing
T4-R04. Script Editor for Unified CCE 15.0(1): create a routing script, schedule it on a call type, send the call to a Type 10 VRU, queue it, and run an external script. Updated April 30, 2025.
01 Β· TL;DR
Schedule the script, then give the VRU something to play
- Call Type Manager has a Script tab, a Period tab, and an optional Description. [cite:1]
- Run External Script, Play, Menu, Collect Data, or Queue before Send To VRU implies a Send To VRU for several VRU types. [cite:2]
- If Run External Script fails, test Call.VRUStatus. The guide says 2 means the VRU is likely not functioning, and later nodes on that failure branch should be avoided. [cite:2]
- A sample flow queues to three skill groups and plays an announcement every 30 seconds while a Wait node and a Run External Script alternate. [cite:2]
- The guide was updated April 30, 2025. re-check [cite:2]
02 Β· Map
The script the guide tells you to build
Study diagram of the queue-and-treatment loop. The 30-second announcement is the sample in the Network VRU chapter, not a universal timer you invent. [cite:2]
03 Β· Core
A script does nothing until a call type schedule runs it
The Scripting and Media Routing Guide for Unified CCE Release 15.0(1), chapter Common Tasks, says Script Editor creates, modifies, and schedules routing scripts. File, New, or the New button, asks you to select a Routing script or an Administrative script. The Edit window opens with a Start node. File, Save asks for a script name. The guideβs header date is the same 15.0(1) book. The Network VRU chapter used for the node behavior was updated April 30, 2025. re-check [cite:1] [cite:2]
Scheduling associates the script with a call type: Script, Call Type Manager, Schedules tab, select the call type, Add. The Script tab selects the script. The Period tab defines when the schedule is effective. Description is optional. OK on both dialogs. [cite:1]
If the Network VRU is Type 10, which the guide says is typically used only with Unified CVP, the Router uses a two-step transfer. The first moves the call to Unified CVP. The second automatic transfer sets up a VRU leg that uses the VXML Gateway or Cisco Virtualized Voice Browser for IVR treatment. The purpose is to simplify Comprehensive call flow configuration. For calls that are front-ended by Unified CVP, only a single automatic transfer from the switch leg to the VRU leg occurs. For calls from Unified CM, the correlation ID is added to the end of the Type 10 transfer label. [cite:2]
The Queue node does not send instructions to the VRU. On success it exits immediately and the call is assumed to be at the VRU. The script should continue with Run External Script so the VRU plays music or an announcement until an agent is free. The sample call flow queues the call for three skill groups, then cycles Wait and Run External Script so the caller hears an announcement every 30 seconds. When an agent is free, the call leaves queue, script execution ends, and the call is delivered. Do not use Route Select in that cycle. [cite:2]
| Node | What the chapter says | Cite |
|---|---|---|
| Send to VRU | Valid for Types 3, 5, 6, 7, and 10. Include it as a visual aid even when an earlier node implies it. | [cite:2] |
| Implicit Send to VRU | Run External Script, Play, Menu, Collect Data, or Queue before Send to VRU assumes the send for Types 3, 5, 6, and 7. | [cite:2] |
| Run External Script | Valid for all VRU types. Success and failure branches. If the call is not yet at a VRU, CCE sends it. | [cite:2] |
| Queue | Exits immediately. Does not instruct the VRU. | [cite:2] |
| Queue to Precision Queue | Also exits to a Run External Script for treatment. Can queue the same call to other targets. | [cite:2] |
On the failure branch of Run External Script, test Call.VRUStatus. If the value is 2, the VRU is likely not functioning, so the script should avoid more Run External Script nodes on that branch. The guide also says the last Send To VRU or Translation Route to VRU failed if the routing client did not respond within 20 seconds, or the last Run External Script failed because the scriptβs timeout expired. Uninterruptible nodes, including an uninterruptible external script, make the CallRouter wait. The Wait node and an interruptible Run External Script are interruptible. Every other node is uninterruptible. Calls can be routed when they reach an interruptible node. [cite:2]
Find Nodes can search by section, node type, or string. That is how you locate a node in a large script. [cite:1]
04 Β· Ecosystem
Ecosystem and sister technologies
ICM scripts schedule against call types. Webex Contact Center flows and Connect digital flows are different tools.
- Routing script
- The File, New choice that opens on a Start node and returns a destination. [cite:1]
- Administrative script
- The other File, New choice. This room does not invent its node list. [cite:1]
- Call Type Manager
- Script menu. Schedules tab binds a script to a call type and a period. [cite:1]
- Type 10 two-step
- Transfer to CVP, then an automatic VRU leg on VVB or the VXML gateway. [cite:2]
- Send to VRU
- Connects the call to the Network VRU. Sometimes implied by an earlier node. [cite:2]
- Run External Script
- Tells the VRU which Network VRU script to run. Success and failure branches. [cite:2]
- Call.VRUStatus 2
- On the failure branch, the guide says the VRU is likely not functioning. [cite:2]
- 20 seconds
- Routing client did not respond to the last Send To VRU or Translation Route to VRU. [cite:2]
- 30 seconds
- The sample announcement interval between Wait and Run External Script. [cite:2]
- Interruptible node
- Wait, and an interruptible Run External Script. Other nodes are uninterruptible. [cite:2]
- Queue node
- Marks the call queued and exits. It does not play audio. [cite:2]
Mind map source
mindmap
ICM script
Create
Schedule
Type 10
Queue
Run External Script
Failure status 2Sister-technology matrix
| Sister | What it is | Why it matters | Config touchpoint | Typical failure | Cite |
|---|---|---|---|---|---|
| Call type | What the schedule attaches to | T4-R03 defines the qualifiers. | Call Type Manager | Scheduling the script and forgetting the period. | [cite:1] |
| CVP | Typical Type 10 VRU | Two-step transfer, or one automatic transfer if CVP already front-ends the call. | Network VRU config | Using a Type 10 label with no correlation ID on a Unified CM call. | [cite:2] |
| VVB | IVR treatment on the VRU leg | Named with the VXML Gateway. | Type 10 second transfer | Expecting the Router to play the wav itself. | [cite:2] |
| Skill group | Queue to Skill Group | The sample uses three. | Queue tab | Stopping the script on the Queue node. | [cite:2] |
| Precision queue | Another queue node | Also needs a following Run External Script. | Same treatment rule | Treating it as a different audio mechanism. | [cite:2] |
| ECE | Run External Script can push a URL | Needs a Network VRU list entry to the URL map. | Configuration guide | Using that node as a web push on a voice-only VRU. | [cite:2] |
| CUIC | Not the script runner | Reports after the call. | T4-R02 | Debugging a node with a report row only. | [cite:3] |
| Flow Designer | Different product | No Start node equivalence is claimed. | T8-R01 | Pasting Queue Contact into this palette. | [cite:4] |
| Digital Connect | QueueTask is a Connect node | Not the ICM Queue node. | T3-R06 | Putting skill relaxations in Script Editor because Connect has them. | [cite:5] |
| E911 | Not a Script Editor node in these chapters | Keep emergency calls on the phone system path. | Outside the sales script | Queuing 911. | [cite:2] |
Integration edges
| From | To | Mechanism | What moves | Cite |
|---|---|---|---|---|
| Author | Script Editor | File, New | Routing or administrative script, Start node | [cite:1] |
| Script | Call type | Call Type Manager schedule | Period of effectiveness | [cite:1] |
| Router | Type 10 VRU | Two-step transfer | CVP, then VVB or VXML gateway | [cite:2] |
| Queue node | Success branch | Immediate exit | No VRU instruction | [cite:2] |
| Run External Script | VRU | Network VRU script | Success or failure | [cite:2] |
| Failure | Call.VRUStatus | Value 2 | Do not keep running external scripts | [cite:2] |
| Wait loop | Caller | Sample every 30 seconds | Until a skill-group agent is free | [cite:2] |
Cross-platform bridges
Webex Contact Center Flow Designer activities are documented on help.webex.com and taught in T8-R01. They are not ICM nodes. A Queue Contact activity is not this Queue node. [cite:4]
UCCE to multi-tenant migration notes in T6-R04 still mark unpublished script parity. This room does not close that gap.
Genesys routing strategies are not Call Type Manager schedules. No parity table is in the scripting guide.
Future-integration hooks
- Canon planning: administrative-script nodes stay TODO-verify until that chapter section is quoted node by node.
- April 30, 2025 is re-check. [cite:2]
- The 30-second figure is the sample flow, not a system default you can assume on every script. [cite:2]
Ecosystem troubleshooting
| Symptom | Likely sister-system cause | Check | Fix | Cite |
|---|---|---|---|---|
| The caller queues in silence | The Queue node exited and no Run External Script followed. | The success branch. | Add the external script the guide describes. | [cite:2] |
| More external scripts run after the VRU is dead | The failure branch has no status test. | Call.VRUStatus equals 2. | Stop the chain. | [cite:2] |
| A CVP-fronted call gets a second transfer you did not want | Type 10 from Unified CM adds a correlation ID and two steps. CVP-fronted calls use one automatic transfer. | Where the call originated. | Match the Type 10 note to the origin. | [cite:2] |
05 Β· Flow
From a new file to an interruptible treatment loop
| Step | From | To | Protocol or mechanism | Notes | Cite |
|---|---|---|---|---|---|
| 1 | Author | Script Editor | File, New | Routing script. Start node. | [cite:1] |
| 2 | Author | Call Type Manager | Schedules, Add | Script tab and Period tab. | [cite:1] |
| 3 | Router | Type 10 | Two-step or one automatic transfer | Depends on Unified CM versus CVP front-end. | [cite:2] |
| 4 | Script | Queue | Success exit | No audio yet. | [cite:2] |
| 5 | Script | Run External Script | VRU script | Interruptible micro-app can be routed away from. | [cite:2] |
| 6 | Agent free | Target | Script ends | The sample removes the call from queue. | [cite:2] |
06 Β· Config
Paths the articles name
- File > New. Choose Routing script. Save and name it. [cite:1]
- Script > Call Type Manager > Schedules > Add. Set the script and the period. [cite:1]
- Place Send to VRU, or know which earlier node implies it. [cite:2]
- Queue to Skill Group or Precision Queue, then Run External Script on the success branch. [cite:2]
- On failure, branch on Call.VRUStatus 2. [cite:2]
- Use Find Nodes when the script is too large to scan. [cite:1]
07 Β· Limits
Numbers worth memorizing
| Item | Value | Source | Verified? |
|---|---|---|---|
| New script starts with | A Start node | Common Tasks | Quoted [cite:1] |
| Call.VRUStatus failure value | 2 | Network VRUs, April 30, 2025 | re-check [cite:2] |
| Send to VRU response | 20 seconds, else that node failed | Same chapter | Quoted [cite:2] |
| Sample announcement interval | Every 30 seconds | Sample call flow in that chapter | Quoted [cite:2] |
| Sample skill groups | Three | Same sample | Quoted [cite:2] |
| Type 10 from Unified CM | Correlation ID appended to the transfer label | Same chapter | Quoted [cite:2] |
| Administrative script node list | Not copied | Common Tasks points at online help for the full list | TODO-verify |
08 Β· Trouble
Trouble
| Symptom | Wrong story | What the source supports | Do this | Cite |
|---|---|---|---|---|
| The new script has no Start node | The canvas is broken. | The guide says the new script opens with a Start node. | Use File, New again rather than pasting a fragment. | [cite:1] |
| The script never runs | The Router is down. | It may not be scheduled for this call type and period. | Open Call Type Manager. | [cite:1] |
| Silence in queue | The wav file is missing. | The Queue node does not instruct the VRU. | Add Run External Script. | [cite:2] |
| Route Select inside the music loop | Any node can sit there. | The guide says not to use Route Select in that cycle. | Remove it. | [cite:2] |
| Failure branch keeps playing scripts | The VRU will recover. | Status 2 means stop subsequent Run External Script nodes on that branch. | Test the variable. | [cite:2] |
| Send to VRU times out | The label is wrong only. | The guide gives 20 seconds for the routing client to respond. | Check the client and the VRU. | [cite:2] |
| Unified CM Type 10 label is short | The label pool is fine. | The correlation ID is added to the end of the transfer label. | Account for that suffix. | [cite:2] |
| An agent becomes free and the music continues | The Wait node is uninterruptible. | Wait and interruptible external scripts are the interruptible nodes. | Do not put treatment only on an uninterruptible node. | [cite:2] |
| Find Nodes cannot see a string | The script is corrupt. | Find Nodes searches section, type, or string. Confirm you are in the right mode. | Change the find mode. | [cite:1] |
| The same steps are taught as Flow Designer | The products merged. | These menus are Script Editor. Flow Designer is a different article. | Use the ICM names here. | [cite:4] |
09 Β· Self-question
Oral ladder
L1What does File, New ask?
Routing script or Administrative script. [cite:1]
L2What node is already on the canvas?
Start. [cite:1]
L3Where do you schedule it?
Script, Call Type Manager, Schedules. [cite:1]
L4What does a Type 10 Router do?
A two-step transfer, unless CVP already front-ended the call. [cite:2]
L5Does the Queue node play audio?
No. It exits immediately. [cite:2]
L6What node plays the hold treatment?
Run External Script. [cite:2]
L7What does Call.VRUStatus 2 mean?
The VRU is likely not functioning. Avoid more external scripts on that failure branch. [cite:2]
L8What is the 20-second failure?
The routing client did not respond to Send To VRU or Translation Route to VRU. [cite:2]
L9What interval does the sample use?
An announcement every 30 seconds. [cite:2]
L10Which nodes are interruptible?
Wait, and an interruptible Run External Script. Other nodes are not. [cite:2]
L11What must you not put in that cycle?
Route Select. [cite:2]
L12Why re-check the node chapter?
Updated April 30, 2025. [cite:2]
10 Β· Lab
Build the treatment loop on paper
11 Β· Quiz
Quiz
A new script opens with:
Answer
A Start node, after you choose Routing or Administrative. [cite:1]
The schedule menu is:
Answer
Script, Call Type Manager, Schedules, Add. [cite:1]
Type 10 with Unified CVP is:
Answer
A two-step transfer, then IVR on VVB or the VXML gateway. [cite:2]
The Queue node is the last node and callers hear silence.
Answer
Expected. The Queue node does not instruct the VRU. Add Run External Script. [cite:2]
Call.VRUStatus 2 means:
Answer
The VRU is likely not functioning. Do not run more external scripts on that failure branch. [cite:2]
Send to VRU fails at:
Answer
20 seconds without a routing-client response, in that chapterβs failure note. [cite:2]
The sample announcement interval is:
Answer
Every 30 seconds, cycling Wait and Run External Script. [cite:2]
Interruptible nodes named:
Answer
Wait, and an interruptible Run External Script. [cite:2]
Route Select sits between Wait and the music.
Answer
The guide says not to use Route Select in that cycle. [cite:2]
Unified CM Type 10 labels:
Answer
The correlation ID is added to the end of the transfer label. [cite:2]
Which earlier nodes imply Send to VRU?
Answer
Run External Script, Play, Menu, Collect Data, or Queue, for the types the chapter lists. [cite:2]
Draw queue success into treatment, and failure into status 2.
Answer
Queue exits. Run External Script plays audio. Failure checks Call.VRUStatus. [cite:2]
12 Β· Audio
Studio fills these
Transcript slot
Studio fills this. The prompt is the spoken outline.
Transcript slot
Studio fills this. The prompt is the spoken outline.
Transcript slot
Studio fills this. The prompt is the spoken outline.
13 Β· Interview
Oral-ready
1. 30 seconds. I create a routing script from File, New, and it opens on Start. I schedule it in Call Type Manager. [cite:1]
1. 2 minutes. The schedule has a script, a period, and an optional description. If it is not scheduled for this call type right now, it will not run. The book date I used is April 30, 2025, so I re-check it. [cite:1] [cite:2]
2. 30 seconds. Type 10 is a two-step transfer to CVP and then a VRU leg. [cite:2]
2. 2 minutes. Calls that CVP already front-ended get one automatic transfer. Calls from Unified CM get a correlation ID on the end of the label. [cite:2]
3. 30 seconds. The Queue node does not play audio. Run External Script does. [cite:2]
3. 2 minutes. The sample queues three skill groups and announces every 30 seconds using Wait. I do not put Route Select in that loop. [cite:2]
4. 30 seconds. On failure I read Call.VRUStatus. Two means stop. [cite:2]
4. 2 minutes. Twenty seconds without a routing-client response fails Send to VRU. Uninterruptible nodes make the router wait. Wait is interruptible. [cite:2]
5. 30 seconds. This editor is not Flow Designer and not Connect QueueTask. [cite:4] [cite:5]
5. 2 minutes. Administrative-script nodes are still TODO-verify as a full list. I will not invent them. [cite:1]
14 Β· Citations
Ledger
Retrieved 2026-10-14. Mirrors cites/T4-R04.md. Facts older than 12 months, and pages whose header date was not in the extract, stay marked re-check.
- Scripting and Media Routing Guide for Cisco Unified Contact Center Enterprise, Release 15.0(1), Common Tasks β cisco.com β Common Tasks β Release 15.0(1), retrieved 2026-10-14. File New, Start node, Call Type Manager, Find Nodes.
- Same guide, Network VRUs β cisco.com β Network VRUs β updated April 30, 2025, retrieved 2026-10-14. Type 10, Queue, Run External Script, Call.VRUStatus, 20 seconds, 30-second sample. re-check
- Unified CCE Product Architecture β cisco.com β Script Editor is named on the Administration and Data Server. T4-R02.
- Flow Designer essentials boundary β help.webex β Webex Contact Center Flow Designer is a different tool. T8-R01.
- Set up digital channels β help.webex β article n954r0k β QueueTask is a Connect node, not this Queue node.
15 Β· Re-engineer later
Open
- Open questions: the full administrative-script node list.
- Facts still TODO-verify: that node list.
- Facts still re-check: Network VRUs, April 30, 2025.
- Assets missing: a treatment-loop SVG export, audio. No production script exports.
- Next review date: next read of the 15.0(1) scripting guide.
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 Common Tasks last checked 2026-10
- Vendor doc Network VRUs last checked 2026-10
sources.json for this page.