VXMl transfer element help with setup on CVP comprehensive

[Albert]

Hello, I am using CVP in comprehensive mode with VVB on ucce. 
I was trying to transfer a call with callstudio transfer element, but I was not able to do it. 
When I was searching for documentation I only found out that this element should work in standalone mode. 
Is that statement correct or is there some configuration parameters that I have to do. 
Actually I am using label in ICM script for call transfers, but the VXML element gives me so much more options. 

[bill.king1]

What version is this one, what did you have in the Transfer element, what happened, was there anything in the App or Error log, etc.?
If you can provide more background, there might be more suggestions for you.

[david.macias]

it's likely that CVP doesn't know where to send the call because there is not dial plan entry for it. That's generally the first issue I see when using this element the first time.

david

[Albert]

We are running on version 12.5(1). 
The activity log doesn't have any errors there is only normal ending 

And I couldn't find any message in the CVP logs with the number that I was trying to transfer the call out. 
I am going to double check the dial number patterns in the OAMP, maybe I didn't have the right configuration for it. But the basic transfer with label in ICM script is working fine. 
Did you mean dial plan in cvp OAMP ? 

[david.macias]

Yes.

[Albert]

I have dial pattern that catch prefix like 3333> and than I try to route them to CUCM. But it's not helping at all. Dial pattern is working with label flawlessly. Isn't there any other setting that is mandatory for that elemnt to work? 
Any setting on VVB? 

To be sure I am pasting the screenshot of configured element. 

[therealptindall]

Your issue is that the VVB does a SIP REFER for VoiceXML non-bridged transfers.   This is executed entirely as fire and forget, which is why the Studio app shows the transfer as completed.   Unfortunately, the CVP SIP B2BUA which is the component in the call signalling path that receives the REFER does not consume SIP REFERs so it will all disintegrate.  

[david.macias]

Paul, are you saying this element doesn’t work with VVB?

[therealptindall]

It does work with VVB but there are things to be aware of regarding how it handles non-bridged transfers.   Implementing a SIP REFER to perform a non-bridged transfer will work in CVP VoiceXML standalone model for calls originating from either IOS devices or CUCM as both can be configured to consume the REFER.  Trying to do that in CVP comprehensive model won't work because the CVP call server doesn't consume SIP REFERs. 

Bridged transfers did used to work in CVP comprehensive model but were never a supported call flow so it's something you would implement at your own risk.   And, of course, bridged transfers mean 2 VVB call legs and a CVP session licence for the duration of the transfer.

[david.macias]

I have a customer using it, but it was already setup by the time I got there. Thanks for the extra education. I hope you're well.

david