Author Message
Anonymous

How I can get the VDN (alphanumeric) of a inbound call?

I have two routes for inbound calls and I need to known what route was selected and I understand that every route have a VDN attached to him... how can I get it using jtapi?


thanks in advance
CraigJohnson5
Joined: Oct 24, 2013
Messages: 413
Offline
The delivered event to the agent phone will have the distributing VDN if you are monitoring the VDN. See LucentV7CallInfo in the javadoc for more information on this private data that is available in a delivered (alerting) event. So basically if you have a listener on the VDN, then when a call comes to your application you can cast the CallCtlConnAlertingEv to LucentV7CallInfo to use getDistributingVDNAddress.
JuanSalazar
Joined: Nov 6, 2013
Messages: 2
Offline
When I cast a call in alerting event to LucentV7CallInfo I received a null value in getDistributingVDNAddress method for inbound call.
is this ok?
CraigJohnson5
Joined: Oct 24, 2013
Messages: 413
Offline
The call is coming to the Agent from a VDN?

Are you monitoring the VDN as well as the agent?

Have you looked at the TSAPI logs on AE Services to verify where or not there is a distributing VDN in the delivered event?

In the Product FAQ's for AE Services TSAPI, the top FAQ is about turning on the tracing on AE Services.
JuanSalazar
Joined: Nov 6, 2013
Messages: 2
Offline
To initiate a VDN monitoring I need this data and this could be dynamic and configured in AES or CM. Is there a way to get a list (programmatically) of all the VDNs corresponding to the agent session?
CraigJohnson5
Joined: Oct 24, 2013
Messages: 413
Offline
You can use JTAPI to find out what skills an agent is logged into by getting the logged in agents for each ACDAddress. There is not a way to trace this back to a VDN alone using JTAPI.

How are the VDN's dynamic? Usually the skills an agent logs into can change, but that is different than a VDN changing which vector it sends a call to. One monitor on a VDN will allow AE Services collect more information about the call. There is no need to put a monitor on a VDN per agent that is logged in. If you know the VDN's in the system that end up routing calls to agents running your application then you can place a monitor on each one of them, and that will suffice.

If you really want an agent to have a list of VDN's that might route to it then you would have to make use of the System Management Service. The service contains models for VDN, Vector, and Agent. Using all three you could come up with a list that you can write to a database to make available in your application.
Go to:   
Mobile view