There is not a scheduled next release of BDE at this time.

Since there is not an IP Office forum, I would suggest opening a DevConnect support ticket under the IP Office platform and someone can point you in the right direction there.

There is a JTAPI Conference Transfer sample application available. It also shows you how to attach data to the call using UUI. However, transferring to a VDN is technically not supported by TSAPI/JTAPI as you may receive the following error:

GENERIC_STATE_INCOMPATIBILITY (21) – The request failed for one of the following reasons:
– Both calls are alerting.
– Both calls are being service-observed.
– An active call is in a vector-processing stage.

There is a workaround for this by putting a 2 second wait step at the beginning of your vector.

For future enhancements it is best to open a GRIP with Avaya. They can tell you whether something will ever be added to a product, or if it's in the works. A GRIP can be opened at https://portal.avaya.com/apps/grip/partner.asp and you must have an Avaya login to proceed.

The way to do this is to use Application Enablement Services. This server connects to Communication Manager through a CTI link. The TSAPI service then runs on AE Services. Since you would like to use C# then I would suggest use the DMCC .NET SDK to develop an application that would connect to AE Services and monitor stations on the Communication Manager. Your client machines talk over a TSAPI link and if you are monitoring a station when a call comes in then you will get call events that will contain information about the call. There is not a call start time provided but you can base it off the established event that is received when an agent answers the phone. And when the connection clears at the end of the call you can use that time stamp against the established event time stamp to get the duration. The established event also contains calling and called party information as well as the trunk if it was an off pbx call.

I would encourage you to look at the AE Services Overview documentation as well as the DMCC programmer's guide. We do have a free AE Services remote lab that you can sign up for and use. It is preconfigured with stations so you can connect and run some test calls to see what data is available to you in the events. DMCC has a dashboard test tool so that you can run tests without have to develop your own application first.

So you have Communication Manager running on the S8400? What version? What phone call data are you looking for?

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.

Hi Adam, were you able to get connected? Have you tried the test application to verify the connection? Keep in mind that https://AES-IPAddress/sms/sms_test.php is the old deprecated string formatted version and https://AES-IPAddress/smsxml/smsxml_test.php is xml formatted.

TAPI is an IP Office interface. Please open a DevConnect support ticket under that product so the proper person can assist you.

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.

DevConnect does not support the Avaya Callback Assist Webservice API. I was able to find an API guide for it:

https://downloads.avaya.com/css/P8/documents/100169531

I'm not sure I follow. The observer on the provider listens for Out Of Service and In Service messages, and if one or the other occurs an event is thrown. So I am not sure why the need to monitor the provider every 30 seconds? If you create a new provider while it's out of service it will get an OOS event. What "service" are you restarting to get the InService event?

1. The JTAPI Conference Transfer application shows how to set and retrieve UUI

2. Using getTerminal on the AgentID will allow you to use getAgentID to return the station number.

Terminal terminal = provider.getTerminal(AgentID);
Agent[] agents = ((AgentTerminal) terminal).getAgents();

//Gets the agentid
String agentid = agents[0].getAgentID();

3. By "monitor call" are you talking about doing call recording? If so, you would need to use DMCC. You can use JTAPI to make a call using the service observing feature access code to barge in to a call and listen, but not do call recording.

4. Say you have callers A, B, and C

A calls B (Call 1)
B Consults with C (Call 2, and terminal connection on B->A is put on hold to call C)
Call 2 is dropped
The terminal connection on B to A is still on hold. Then, you can unhold the terminal connection on B to resume the call with A

You can make use of the JTAPI exerciser to verify this scenario.

Application Enablement Services works with Communication Manager. You can use TSAPI, JTAPI, or DMCC to get call events which contain data about the call. Please explain "CAD data" and how it is attached to the call on the "other" network?

Since you can put "auto" at the end of the qualifier it looks like SMS will run this command successfully. I use the SMS test application to verify functionality. That is available at http://[yourAES_IP]/smsxml/smsxml_test.php. I used '50001 auto' as my qualifier in my environment.