Hi,

Below are the version details.

I am using TSAPI Client and Serviceprovider.dll(Active recording)

CM Version 6.3.17.0-SP17
AES Version 6.3.3
TSAPI Client - 7.0
Serviceprovider.dll - 7.1.1.54

Are the versions are compatible?

Thank You.

Hi,

After upgraded with the TSAPI Client library 7.x version, the application has been able to get events after reallocting the buffer size returned by the acsgeteventblock for ACSERR_UBUFSMALL errors. The events returned for those cases are either the conference or transfer.

In those cases the u.transferred.transferredConnections.connection[tc].staticDevice.deviceID or pUns->u.conferenced.conferenceConnections.connectionList->connection[i].party returns more than 12 parties in the connection. How this is possible as a max of 6 party conference only allowed? Where maybe the problem?

ThankYou

Hi,

acsgetevtblock() returns ACSERR_UBUFSMALL error ,application retries with acsgetevtblock() again with the return buffer size . still getting the same error. The problem gets resolved after closing the link after a certain Time and reopen the link.

In Lab, I tried to allocate fewer buffers, and API got failed with the same error. Then the retry logic worked without a problem. So I think this won't be an application problem.

In the customer place, 3 application is running connecting to 3 different AES. The problem happens to all 3 applications at the same time. Is something do we need to check in AES? AES Version is 6.3.3

Thanks

Pratheep

Hi,

In Transfer event for few calls primary old call id comes as the call id belongs to consultation call leg and secondary new call id comes as the primary call id .
AES and CM versions are 6.1.1 and 6.0 respectively. Is this behavior normal ? normally primary old call id comes as the primary call id and secondary call id comes as the consultation call. We have some logic problem due to this behaviour. Is there any notes on Avaya to solve this?

Hi,

We have two applications X and Y. X monitors the VDN 4000 and Y monitors the VDN 5000.

1) Call comes to VDN 4000
2) Answered by Agent
3) Warm/Cold Transfer call to VDN 5000

Now application X wont receives any CTI events related to VDN 5000

If application Y(not monitored) is not running then application X receives the events related to VDN 5000 after transfer call.

Is this is the behavior of CSTAMonitorcallsviaDevice ()?

We dont want to use CSTAMonitorCall and also not to monitor the VDN 5000 in application X.

How to get the CTI events for VDN 5000 with out monitoring that VDN in application X?

Hi,
When application registers DMCC Device getting below response for some of the extensions. The password for the extensions are correct.
reason: Registration Reject reason: securityDenial
Login Denied - Access Code invalid. diagnostic string= code= 63773

This is happening always when we restart or start the application ,application try to register and randomly happening for some of the extensions.

Below is AES and CM version

AES is version 7.1.2.0.0.3-0
CM is version CM 7.1.3.0.0.532.24515

In AES management console ,under networking - Ports - TSAPI ports you can see list of ports used by encrypted TLINK and unencrypted TLINKS. 1066 is the starting port for encrypted TLINK. Once connection been established with 450 ,then depending upon the link I think JTAPI or TSAPI sdk connects to port between 1066 to 1081 for encrypted link.

Hi,

Below are the clients used to connect to AES server
JTAPI Client with SDK Version 6.3.3
TSAPI Exerciser Version 7.0.0

AES software Version - 7.0.0.0.0.13

When i choose Encrypted Tlink i could see the port no 1066 been used. But i dont see any TLS Handshake messages between client and server sending Hello and exchanging Keys in wireshark. How to confirm TSAPI or JTAPI application uses TLS and also TLS version information mentioned for the above software versions?

As default certificate got expired on jan 2018 we created a new Avaya SystemManager CA certificate and both the application uses the same certificate exported from AES.

Thank you Martin.

I read the 6.3.3 JTAPI document, says 6.3.3 JTAPI SDK automatically negotiate PrivateData Version 11 with TSAPI Service . Suppose if I run this 6.3.3 application with 5.x AES Server, which will support PrivateData up to version 7 ,definitely Private data negotiation will get fail in startup(normally this will happen in TSAPI). Even tough it got failed do the jtapi application receives Private data event for Version 8 in 5.x.

Can JTAPI Application developed using 6.3.3 JTAPI Client SDK inter operate or work with Previous AES Versions like 6.3,6.2,6.1 and 5.x ?

Thanks . It's Working.

I am not getting Event cause EC_DO_NOT_DISTURB in tsapi exerciser ,even the soft phone is configured as DO NOT Distrub. I am getting as EC_DEST_NOT_OBTAINABLE. Is there any settings to be done on CM. Any document to configure DO Not Distrub in CM?

I got the event in TSAPI Exerciser for One-x communicator. How to get these event for HardPhones? I unplugged the HardPhone i am not getting any events.

I want to get the EndpointRegistered and Endpointunregistered event in jtapi application. So I need to monitor the Address of the station not the terminal.

I am running TSAPI exerciser and not getting this event in 7.x environment. The link is configured with ASAI version 7.

When do I get this event? I tried logoff one-x communicator and login again I did not get this events in TSAPI exerciser.