Author Message
NobuhiroTentaku
Joined: Jul 7, 2021
Messages: 86
Offline
Dear Sir,

VDN number links to am extension number and I think VDN is something like an extension number.
However I cannot get information and state like LucentTerminalConnection.getCallControlState() from VDN f different from extension numbers.
Is there any way and/or configuration to handle VDN as extension number?

Best regards,
MartinFlynn
Joined: Nov 30, 2009
Messages: 1847
Offline
A VDN is very different to a Station. I don't think it ever has a state within a call as the call never stays on a VDN. The call is always passed on to something else, such as a Vector.

Martin
JohnBiggs
Joined: Jun 20, 2005
Messages: 993
Location: Rural, Virginia
Online
VDNs have a sequence of digits that address them, you could call it an extension... within communicationmanager terminonlgy, it is an extension. However not all extensions are stations.. there are many objects that have extensions, not all are stations. JTAPI/TSAPI services are largely (although not exclusively) oriented toward stations. A VDN is a pilot number that access a vector. the vector is a forum of routing logic... the VDN coupled with a vector make decisions about how to route calls to destinations (ultimately stations or trunks). While a VDN/vector may spend minutes or even hours making a decision about how to route a call, and the call exists within the vector processing in that interval, the normal JTAPI services are not available for that call since those services are largely focused on calls at stations (there are some JTAPI/TSAPI methods that provide information about calls at VDNs - but more just events providing information about the call - none supporting queries about the call).
NobuhiroTentaku
Joined: Jul 7, 2021
Messages: 86
Offline
I got it. Thank you.

Best regards,
Go to:   
Mobile view