Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: Vic on January 01, 1970, 12:00:00 AM
-
Hi, all,
I need some major help with basic Genesys:
virtual routing points they only exist within Genesys right?
I was under the impression that we can use them to logicall separate calls for reporting purposes without actually splitting the physical calls themselves.
Most of our IVR solutions use VRPs for loadlancing. I was reviewing some of my notes earlier and ran across a rather interesting note that I found on Genesys support site:
VRP DOES NOT SUPPORT VOICE CALLS
So, in other words, we cannot forward the calls to it...
So, how DO you use VRPs then? Can why can't we route a call from a REAL RP to a VRP?!!! Since the call is parked on a real CDN, from a PBX point of view, nothing would change...
Anyone?
Thanks,
Vic
-
As per 6.5 Release Notes:
Virtual route points are only used in IVRBehindSwitch mode. The currently documented syntax is as follows:
[VirtualRoutePoints]
tsname=vrp1:vrp2:vrp3
where 'tsname' is the name of the TServer application on which the virtual route points are defined and vrp1, vrp2 and vrp3 are the virtual route point DN names.
This syntax is still supported, but has been extended to allow you to assign an alias name for a virtual route point. For instance, to assign the alias name 'sales' to vrp1 you would code the following:
tsname=vrp1|sales:vrp2:vrp3
From the IVR Driver, then you can send a RouteGet on DN 'sales' and this would be translated into a route request on virtual route point vrp1.
This feature becomes important when configuring load balanced IVR Servers because it is not possible for two (or more) IVR Servers to use the same virtual route point. In other words, each IVR Server 'owns' the virtual route points that it is configured with. In this case you would configure two virtual route points one for each IVR Server and give them the same alias name. This way the IVR client can load balance between multiple IVR Servers and use the same logical route point for routing operations (that is, the virtual route point alias name).
For example, on IVR Server 1:
[VirtualRoutePoints]
tsname=vrp1|sales
and on IVR Server 2:
[VirtualRoutePoints]
tsname=vrp2|sales
Then route requests on the 'sales' alias to IVR Server 1 would be issued on vrp1, and route requests on the 'sales' alias on IVR Server 2 would be issued on vrp2.