Author Message
hczhao
Joined: Feb 12, 2014
Messages: 51
Offline
Hi Expert

How can change private version.
I am trying below but not work.

((ITsapiPeer)peer).addVendor("ECS","2-13");

but the version is 15 when get via myProvider).getVendorVersion() method.

Is there any way can change private version on Jtapi.

the reason to change the version. I am facing below issue.
Request: a_32016.getRegisteredEndpoints()
AddressFrame.getRegisteredEndpoints(): caught TsapiMethodNotSupportedException
Message: unsupported by driver

but I can use the method in Tsapi Exerciser. the different between tsapi and jtapi exerciser is ECS version.
tsapi is 13
jtapi is 15
MartinFlynn
Joined: Nov 30, 2009
Messages: 1921
Online
It looks like your JTAPI is version is 8.0 but your AE Services is older - (7.1.1 - 8.0.1 I think).

This will not stop you from being able to use LucentV11Address.getRegisteredEndpoints().

For example, here is the JTAPI Exerciser output I got with JTAPI 8.1 and AE Services 8.0.1:

Request: a_32002.getRegisteredEndpoints()
=>a_32002.getRegisteredEndpoints() returnd 0 endpoints -


Request: a_32002.addCallListener(new MyCallListener()) [decode=true]
=>a_32002.addCallListener() returns void

Request: a_32002.getRegisteredEndpoints()
=>a_32002.getRegisteredEndpoints() returnd 1 endpoints -
LucentV11Address.getRegisteredEndpointInfo()
V11RegisteredEndpointInfo.getInstanceID() => 0
V11RegisteredEndpointInfo.getEndpointAddress() => 0.0.0.0
V11RegisteredEndpointInfo.getSwitchEndIpAddress() => 10.10.13.135
V11RegisteredEndpointInfo.getMacAddress() => 00:00:00:00:00:00
V11RegisteredEndpointInfo.getProductID() => SIP_Phone
V11RegisteredEndpointInfo.getNetworkRegion() => 1
V11RegisteredEndpointInfo.getMediaMode() => MM_CLIENT_SERVER (1)
V11RegisteredEndpointInfo.getDependencyMode() => DM_MAIN (1)
V11RegisteredEndpointInfo.getUnicodeScript() => US_NONE (0x0)
V11RegisteredEndpointInfo.getStationType() => 9640SIP
V11RegisteredEndpointInfo.getSignalingProtocol() => SP_SIP (2)
MartinFlynn
Joined: Nov 30, 2009
Messages: 1921
Online
Here is the description from the TSAPI Programmers Guide:

This service provides the service state of a station extension and a list of H.323 and/or SIP endpoints registered to that station extension.
The Query Endpoint Registration Info service is available beginning with Avaya Communication Manager Release 6.3.2 and AE Services Release 6.3.1.
This service is only available if the TSAPI Link is administered with ASAI Link Version 6 or later and if the application has negotiated private data version 11 or later.
Applications should use the cstaGetAPICaps() service and check the value of the queryEndpointRegistrationInfo parameter in the private data accompanying the CSTA Get API Caps Confirmation event to determine whether this service is available.
Applications should invoke cstaMonitorDevice() for the queried device before invoking this query because Avaya Communication Manager cannot provide the service state of a SIP station that is not monitored.

From this, I think you should check the AE Services configuration that TSAPI Link is administered with ASAI Link Version 6 or later.

Martin
hczhao
Joined: Feb 12, 2014
Messages: 51
Offline
Hi,

below is the version.

AES Version: 8.1.2.0.0.9-0

jtapi-sdk-8.1.0.0.0.9

TSAPI Links
Link Switch Connection Switch CTI Link # ASAI Link Version Security
1 CM20 7 10 Unencrypted
MartinFlynn
Joined: Nov 30, 2009
Messages: 1921
Online
That looks to me like it should work. If you need further support, you should open a Technical Support ticket and one of my colleagues will help you to look deeper into this problem.

Martin
hczhao
Joined: Feb 12, 2014
Messages: 51
Offline
Hi Martin,

thank you for your advise.
I have created a ticket below.

https://www.devconnectprogram.com/dpTroubleTicket/editUser/32112
Go to:   
Mobile view