cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
824
Views
0
Helpful
10
Replies

Sending call to 3rd party VRU using Send-to-VRU node

Wayne Lockhart
Level 1
Level 1

Integrating ICM Script with 3rd party VRU using GED-125 interface and having trouble to send the call (transfer) from Cisco CallManager to 3rd party VRU. Send-to-VRU node  - it is not clear how to pass the destination for 3rd party VRU.

10 Replies 10

Chintan Gajjar
Level 8
Level 8

you can use send VRU only in case the VRU is Type 10, means it is able to understand the corr id and label.

 

in your case you can use translation route to VRU. in this case a label will go back to CUCM

CUCM will send it to third party VRU and VRU submits the request to ICM for the same DN.

 

 

Well, according to all Cisco documents Send-to-VRU could be used with at least VRU types 3 and 7. I was trying to use type 7.

The main problem I see is that there is no place to specify the destination for the call transfer. At least it is not obvious.

Basically, I have one PG with two PIMs - CUCM and VRU. VRU PIM talks to 3rd party VRU with no problems. Now when a call comes to CUCM and ICM script launched, I would want to transfer the SIP call to the 3rd party VRU - how to specify the destination such as "sip:12345@servername" whether using Send-to-VRU or Translation Route to VRU?

Thanks in advance.

i am not sure if you can use send to VRU with other then type 10 VRU, i have to revisit the SRNDs.

now coming to your point, if you would have to transfer call to VRU when its on CUCM. try this:

Set up a translation VRU on PG.

the label 12345 will go to CUCM RC, and come on DNIS 12345 on VRU RC (peripheral target).

once you have it setup correctly, you have make ready your CUCM to route 12345 to your 3rd party VRU. there are many ways, but one best way is to have sip trunk set up to your VRU.

have a route pattern as 12345 and point to SIP trunk.

thats it , now its your VRUs responsibility to handle the SIP invite and ask ICM for request instruction.

The main part I am confused about is on PG there are currently two PIMs - CUCM PIM and VRU PIM. When creating Translation Route, should it be done on CUCM PIM or on VRU PIM? Also, it looks like for Translation Route, I need to create a Service, then a Trunk Group, then the label.

It sounds to me that Translation Route must be created on CUCM PIM that is where I want to transfer the call to.

And VRU PIM seems to be related exclusively to Service Control Interface (GED-125) that is already working for me with no problems.

Update: this is the printout from rtr log - what could be the reason the transfer times out? Also, my concern is VRUID=5007, this is actually the configuration of another instance of VRU PG. So my main question is should I have one PG with two PIMs - CUCM and VRU or should I have two PGs where one PG has CUCM PIM and another PG has VRU PIM?

16:20:31:456 ra-rtr Trace: (65539 x 10004 : 0 0) TransferToVRU: Label=555, CorID=10004, VRUID=5007, RCID=5010
16:20:31:456 ra-rtr Trace: (65539 x 10004 : 0 0) TransferConnect sent. Dialog pending.
16:20:51:187 ra-rtr Trace: (65539 x 10004 : 0 0) Dialog timed out callstate is :(1).
16:20:51:189 ra-rtr Trace: (65539 x 10004 : 0 0) Dialog resuming (Script Node timed out.) status (2)
16:20:51:192 ra-rtr Trace: (65539 x 10004 : 0 0) RouteComplete:
16:20:51:192 ra-rtr Trace:  Route: DN=8136, ANI=8054, CED=, Label=555
16:20:51:193 ra-rtr Trace:  Route: CID=(151299,53576305), Labels=1
16:20:51:195 ra-rtr Trace: (65539 x 10004 : 0 0) Connect: CID=(151299,53576305), EventSelect=0, ServiceType=0, RCID=5010, Label(s)=555
16:20:51:196 ra-rtr Trace: (65539 x 10004 : 0 0) Deleting Dialog.
 

Thanks in advance.

 

--> you have to configure Translation routing on VRU PIM.

you can use the generic PG with one VRU pim and one CUCM pim (thats what you have and its completely fine)

for TR: you have to configure service on IVR PG, Network trunk group on IVR PG, and then set up TR on IVR PG where label will go back to CUCM client.

 

and lokking at the logs, you are using send to vru where ICM is sending label and corr id to RCID 5010 and as i said the send to VRU will not work with other then type 10 VRU.

 

regards

Chintan

Hmmm, I was actually using type 10 in the above printout. But I was certainly confusing Service, TrunkGroup, and label between CUCM and VRU PIMs.

Seems that Service, TrunkGroup, and Translation Route is configured properly now with label in Translation Route pointing to CUCM.

Now the problem is how to incorporate Translation Route into ICM script, specifically, what to enter in columns "Consider if", "Select Min Value of", and "Route".

Thanks.

well you can do many things with consider if, and the route will be selected only if the condition is true. the one thing you could do is if peripheral is online, if you have trunks available.

but for your purpose you can put 1=1, that is always true.

for select min value you can put 1

and route will be the translation route you configured.

Good news is that I got Translation Route working - call gets routed to 3rd party IVR.

Bad news is that I got various errors in rtr log such as:

12:41:07:557 ra-rtr Target Val_PG5_1.SVC1(ID 5061) was ignored as no routes were configured for translation route TRANSRTE1(ID 5063).

or

16:36:10:570 ra-rtr Trace: (65542 x 0 : 0 0) No peripheral target available for translation route TRANSRTE1 (ID 5063) with routing client PG5_CUCM_PIM2 (ID 5010). 
 

Where the Route, Peripheral Target, and Label must be configured - on Service screen or Translation Route screen?

In some configurations Route column has no entries in dropdown.

Now I just see Translation Route sends the call to IVR and then goes to Failure terminal.

Thanks,


 

Actually, I was able to send the call from ICM script to 3rd party VRU using Send-to-VRU node.

I am still using type 10 Network VRU as this seems to be the go-forward option.

Thanks a lot for your help.

and if call does continue in call routing script, then you are all set and good to go.

cheers