Please login or register to access secure site features.

Note: By continuing to use DevConnect Program Services you agree to our latest Registered Member Terms.

Sign in using DevConnect ID

Forgot password?

Trouble logging in?

Submit a ticket for Registration Support.

I have an SSO ID

?
sign in

Don't have a DevConnect or SSO ID ?

Create a DevConnect account or join the program.

register now
^

FAQ: Application Enablement Services

See All Content
X

FAQ: JTAPI

Exceptions

Why does the CallCenterProvider.getACDAddresses()JTAPI method throw a TsapiPlatformException with the error "Security Database is turned off, No List will be returned."?

The CallCenterProvider.getACDAddresses()method returns an array of ACD Addresses associated with the Provider and within the Provider's domain. This list is static; i.e., it does not change after the Provider is first created. If the CTI user used in the JtapiPeer.getProvider() method has unrestricted access, then the CallCenterProvider.getACDAddresses()method throws the above mentioned exception. If the user has restricted access and no ACD Addresses are associated with this Provider, then the method returns null. In order to avoid the exception, enable restricted CTI access for the CTI user that is being used in the JtapiPeer.getProvider()method. Using a web browser, navigate to the AE Service's Home OA&M page (http://<IP-Address-of-AE-Services>), click on AE Server Administration, login with CTI username and password and select CTI OAM Administration. From that page, navigate to Administration -> Security Database -> CTI Users -> List All Users. Select the radio button for the CTI user that the application utilizes and click Edit. Click on the Unrestricted Access "Disable" button to enable "Restricted Access" for the CTI user. The following screenshots show this sequence.

For more information, refer to the section titled Security Database objects in Chapter 6 of Avaya MultiVantage® Application Enablement Services Administration and Maintenance Guide, Release 4.2, 02-300357, Issue 10, May 2008, available on http://www.avaya.com/devconnect.

Why would a JTAPI application receive an exception 'orig Terminal not associated with orig Address' while making a call using the Call.Connect() method?

While invoking the Call.Connect() method, it is necessary to provide the originating Terminal object, the corresponding Address associated with the originating Terminal object and a valid destination telephone number. The originating Address must be associated with the originating Terminal (i.e. Address.getTerminals()should include originating Terminal) and the originating Terminal must be associated with the originating Address (i.e. Terminal.getAddress()should include the originating Address). If the originating Terminal is not associated with the originating Address, then the JTAPI service throws an InvalidArgumentException containing the above error message. In Avaya's implementation, there can be only one Address associated with a Terminal. In other words, there is a 1:1 relationship between Address and Terminal in Avaya's JTAPI implementation.