URS 8.x - VTO calls are transfered to the starting of the strategy (ivr_info=F)

[valeriu.craciun]

URS 8.x - VTO calls are transfered to the starting of the strategy although use_ivr_info = false.

After sending the call to the VTPort ( using IVR Treatment block ), when the call comes back to the origination Routing Point, the URS Server seems to treat the call as new one and starts over the strategy - reading configuration, attaching user data, but also keeping the same ConnectionID.

Description of our environment:
* URS version 8.0.100.17 - running on RedHat ES 5
* T-Server version 8.0.101.03 - T-Server for Nortel Communication Server 1000 with SCCS/MLS - running on RedHat ES 5
* URS StatServer version 8.0.000.30 - running on RedHat ES 5
* VT Server version 7.0.100.09 - runing on Windows 2003 SP1
* VT StatServer version 7.2.001.02 - runing on Windows 2003 SP1

Uploaded files are:
* URS Server log file in the timeframe of the wrong interaction
* URS StatServer log file in the timeframe of the wrong interaction
* VT Server log file in the timeframe of the wrong interaction
* VT StatServer log file in the timeframe of the wrong interaction
- all are contained in the file named "logs.zip"

May also specify that our VTO Script are defined with the Transfer action using a variable ( k_routing_point ) so that the URS server takes control over the call. The ConnectionID that can be tracked with the wrong VT Transfer is 013b01f2b612e283, ani 744444026.

Thanks

[valeriu.craciun]

SOLVED!!!! Upgraded URS to version 8.1.000.11 and it returned to normal behaviour, the use_ivr_info = false is working as described by the documentation and the call continues after the IVR Treatment block.