I have got a wierd one. So I have an associated VRU for CVP under my Routing Client for the CVP PG (Type 10). And it is never invoked, however if I add the VRU under the Customer Definition, it is invoked. I am getting error's still (SendToVRU is aborted), I can see the label come into the VXML Gateway and trigger the bootstrap. Any insight on why I can't trigger the VRU from the routing Client? I feel like these are all linked together.
>however if I add the VRU under the Customer Definition, it is invoked.
Nothing surprising about that. It must be there.
It's the customer linked to the dialed number on the script that makes "Send to VRU" work. From the customer it looks up the NVRU to know where to signal on the "Send to VRU" node for the routing client.
Now you see the label come in - and it triggers the bootstrap. Is the correlation ID recoverable by the other side? Is the number of significant digits correct. When that label comes back, CVP needs to be able to strip off the correlation ID and find the paused script.
Use rtrtrace on the Router - you should be seeing some "dialog" failures.
How do I strip off the correlation ID in CVP. Also should I be adding the DNIS of my Network VRU label under ICM in the Call server? Lastly if I do add these DNIS in the call server with the corelation ID, it triggers an error on the PG. Should I set the maximum DNIS numbers to the original label length?
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...