1. No, you cannot change the display on the IP phone of the NVRU label + correlation ID. Many have asked, zero were chosen. ;-)


2. Don’t use WAIT nodes with CVP in your ICM scripts

Regards,
Geoff

Why we should not use Wait nodes in CVP?

This was drummed into me on my first CVP course (CVP3) about 7 years back, and I heard it many times during the following years, from Cisco folks at TOIs (Transfer of Information) and other courses etc, at Networkers, on NetPro.

I think this was spelled out at the time for people making the transition from IP IVR, where an ICM wait node could work with the IVR, because of hold music. I took it to heart, but did not really ask why it was not allowed. I just never used them.

I figured everyone would have heard the same as me, and not use them. But I have seen fragments of scripts posted on NetPro with “wait” nodes, so I guess not everyone got the same memo.

What is a “wait node”?

I think we are just telling the Call Router to wait – which basically means: set a timer and come back to this script to this point in the script, in the specified time interval.

Maybe it’s inefficient with CVP. Maybe timers go off if we wait too long. I really don’t know.

It certainly doesn’t do anything. If I want it to wait 2 seconds, I would insert a Play Media microapp with 2 sec of silence.

I guess I could ask “what do you want to use the WAIT node for”?

Regards,
Geoff

Paul:
The call is being sent to ICM via a CUCM route point, then the CVP app is being invoked with the run external script node.

Geoffrey:
I don’t have anything I need to use it for now, just figured it would be good to know why not to in case a situation comes up in the future where we need something like that. That way I could explain to my coworkers why we shouldn’t use it.

Paul,

If you use a route pattern in CUCM to send the call directly to CVP you lose call context. Not a good thing.

Regards,
Geoff

Paul,

Understood. But normally the same route point is used for a warm transfer. At least that’s how I do it.

I use the DNPs a lot – you will see the label+corr id on the phone, as you say. But who cares in that context.

Basically I have a DNP “wildcard string” that’s the same as the number one would call from an IP phone (the route point). The wild card string actually maps to a slightly different number attached to the same call type that runs the same script. Just for call types and counting. The DNPs are in the CAD phone book – why hit CUCM when you don’t need to?

I see what you are saying though. I need to try it in my lab.

If my customers complain about that display, I could try the other strategy, although it complicates the CUCM a bit and adds static routes in the proxy for those route patterns. So far, no one has complained. ;-)

Regards,
Geoff