CVP "Send to VRU" and "Run Ext Script" Failures

Publisher

Cisco Systems

URL

https://www.cisco.com/c/en/us/support/docs/customer-collaboration/unified-customer-voice-portal-901/116178-technote-cvp-00.html

Published

2013-09-23

Updated

unknown

Accessed

2026-09-30

HTTP status

200

License

Cisco proprietary documentation; no-redistribution; short excerpts and locators only

Source notes citing this source

• For VRU-leg failures Cisco lists the IOS gateway debugs: debug voip ccapi inout, debug ccsip message, debug voip application vxml, debug voip application tcl commands and debug http msg. in context
• A CVP log message that the B2BUA is not configured with a route for the label-plus-correlation-ID number means CVP has neither a static route nor a proxy route that matches the VRU label toward the VXML gateway. in context
• The router trace 'Customer (n) has no valid network vru defined - using default' indicates the customer instance is not associated with a network VRU; the fix is to associate it with a valid network VRU. in context
• The router trace 'Customer not found for dialed number ... using default' indicates the dialed number has no customer instance assigned; Cisco's resolution is to define a customer instance for every dialed number rather than rely on the default. in context
• The router trace 'No label configured on network VRU ... for routing client ...' means the Type 10 network VRU lacks a label for that routing client; add a VRU label for each routing client. in context
• The router trace 'No NetworkVRU configured for peripheral for VRU capable call on dialed number' means the CVP PG peripheral has no Type 10 network VRU assigned. in context
• For SendToVRU failures Cisco's technote enables router tracing for Route Request, Script Selects, Network VRU Tracing and Call Queuing, and CVP Debug41. in context
• The CVP SendToVRU and Run External Script troubleshooting note requires a Type 10 network VRU, with a label added for every CVP PG. in context
• For SendToVRU to work, the VRU label length must match the Maximum Length of DNIS configured on CVP. in context
• A failed VRU leg can break at three separable points: the router finding a VRU label, CVP routing the label plus correlation ID, and the VXML gateway matching a dial-peer with the right application; each leaves evidence in a different log. inferred in context
• If the VRU dial-peer has no application bound, the gateway hands the call to the default application; the IOS VXML gateway needs the TCL bootstrap application with the cvphost parameter set and header-passing enabled. in context
• A VRU leg that reaches the VXML gateway but matches a default dial-peer instead of the VRU dial-peer fails to run the VRU script; causes include no VRU dial-peer, a pattern that does not match the DNIS, or a missing signature digit. in context
• The same technote says a VXML gateway fails to start the VRU leg when no incoming dial-peer pattern matches the VRU DNIS or the matching dial-peer has no bootstrap application, and warns that prepended significant digits can break the match. in context
• The same technote says the VRU label length must match the Maximum Length of DNIS configured on CVP. in context
• A Cisco technote lists four reasons ICM fails to find the VRU label at Send to VRU: the dialed number has no customer instance, the customer has no associated Network VRU, the Network VRU has no label for the routing client, or the peripheral gateway has no Network VRU configured. in context
• The same technote says Send to VRU fails when CVP has no static route or proxy route for the VRU label plus correlation ID, and advises checking that a route exists and that its destination address and port are right. in context
• The router resolves the network VRU through the dialed number's customer; the related router messages are 'Customer not found for dialed number', 'No network VRU is configured' and 'No label configured on network VRU'. in context
• If the routing client's PG has no network VRU, the router log shows 'No NetworkVRU configured for peripheral for VRU capable call' when a Send to VRU or Run Ext Script node runs. in context
• For CVP comprehensive call flows, the network VRU must be Type 10 with a label for each routing client, and the label length must match CVP's Maximum Length of DNIS setting. in context

Cite this source record

APA

WarmTransfer. (2013, September 23). CVP "Send to VRU" and "Run Ext Script" Failures. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-technote-116178-cvp-send-to-vru-failures

BibTeX

@misc{warmtransfer-cisco-technote-116178-cvp-send-to-vru-failures,
  title  = {CVP "Send to VRU" and "Run Ext Script" Failures},
  author = {{WarmTransfer}},
  year   = {2013},
  url    = {https://warmtransfer.net/knowledge/sources/cisco-technote-116178-cvp-send-to-vru-failures},
  note   = {Cisco Systems, accessed 2026-09-30}
}