Cant Make a Call using AES DMCC API

[avc899860862902]

I downloaded Avaya Aura AES Release 10.2 Dec 2023 DMCC .NET SDK and am trying to create a demo to initialize a call between local sales rep in the office and external customer. The only dll included was ServiceProvider.dll.
I have been tried asking ChatGPT and Copilot to generate me some sample code to make call but some of the options it says I should have... I dont seem to using Visual Studio and C#.net

I have been able to connect to AES using StartApplicationSession call. I can successfully call DeviceId, GetPhysicalDeviceName, GetPhysicalDeviceInformation APIs..
but when i try to make call: serviceProvider.getThirdPartyCallController.MakeCa ll(txtDeviceId.Text, txtCallTo.Text, null);
- It returns error: <stateIncompatibility>invalidDeviceState</stateIncompatibility>

Any thoughts, suggestions? Am I using the correct SDK/APIs?

[jtb1]

DMCC can certainly do a MakeCall operation.
Make sure the station extension you are originating the call from is in-service (you can manually place a call from it) and it is speakerphone equipped. service state of an extension can be checked at the SAT using 'status station xxx' command.
I am not sure how you are getting anything to work if you are not using c# though.

[flynn1]

You will find links to useful information at https://support.avaya.com/forums/for...rking-with-wti

1. For Call Control functions, such as MakeCall, the TSAPI Programmers Guide and TSAPI traces on AES will give you the best information. Especially, when trying to figure out why something isn't working.
2. The DMCC .Net SDK comes with the DMCC Dashboard. This allows you to make API calls without writing code.
3. The DMCC also includes the SimpleRecord sample application. There are C# and VB versions. These mostly use DMCC first Party functions but it does use SingleStepConference which is also a Call Control function.

Martin

[avc899860862902]

Unfortunately, i don't have any access to telecom systems... They gave me an AES login id so i could test AES DMCC integrations. I asked the telecom to run the 'status station xxx' call as requested...
- I did look at sample codes that were included in install... there is a MakeCall API call using serviceProver ThirdPartyController but it doesnt work for me... invalidDeviceState.
- And the SingleStepConference also is part of ThirdPartyController but requires me to have an ActiveCallId...

I need to initiate a call.. I tried to use ServiceProvider.getDevice but it says the device was not present in the dictionary...
when i make API call RequestSystemStatus, it shows tLinkdown... is that an issue?

[flynn1]

I highly recommend that you use the DMCC Dashboard to familiarize yourself with how the DMCC interface works.

You should also use the sample application to see how the .NET Client is modeled and put together. There is also no way to avoid reading the DMCC .Net Programmers Guide.

ServiceProvider.getDevice() just returns a Device object that has previously been created and populated by the application. For example, see how the application handles ownerDevice. In function ServiceProvider_OnStartApplicationSessionResponse( ), the application uses serviceProvider.GetNewDevice() to create a Device object. It then adds callback functions and, uses ownerDevice.GetDeviceId() have AES allocate a Device ID for it. When AES returns a DeviceID, ownerDevice_OnGetDeviceIdResponse() is called and the application can start monitors on the device. The sample application also registers a terminal for the device. You would not do this as you only intend to use Call Control features.