use this file...
/home/admin/xln_S8300_134140_20080124.tar.gz

I will get the document corrected.

If you are unaware of the FAQs, click on the FAQs item in the left panel menu on this page.

this is a FAQ on the devconnect site (drawback must be a devconnect member to view it(free registered member signup is available as you know) to view the FAQs.. The FAQ gets the info up in the short term, long term is to have the documentation updated to include this for all to view.

John

It will look like ths:
Q: What does a 'switch connection' state of "Invalid Client" mean is configured incorrectly?

A: Check that the hostname of the AE Services server (Linux> hostname) matches the value that is provisioned in Communication Manager's 'change ip-services' System Access Terminal form in the field titled 'AE Services server' on page 3. The hostname/AE Services server is case sensitive and must match in both places.

I can also get an AES FAQ posted in the next few days that covers this subject.

Not that I am aware of as of 4.1, however I can work to get an improvement made to either the admin & maintenance guide, and or the online help. We'll see when and where it gets done.

John

Check that the hostname of the AE Services server (Linux> hostname) matches that which is provisioned in CM's 'change ip-services' SAT form on page 3. The hostname is case sensitive.

Michael,
Which specific sat commands are you interested in using? Full support of UDP implies quite a few forms.

The AES is a separate product that allows access to all the CM APIs.. This allows better scalability for applications in an enterprise, and allows a single point of access to multiple CMs by an application.

I read the CM4 as a statement that the software release on Communication Manager is 4.something (this can be collected from a linux prompt issuing the swversion, or from the system access terminal using the 'list config software' command).

That release does support an adjunct processor called Applications Enablement Services (or AES). The AES provides the JTAPI interface for Call Contact Integration.

There may be certain licensing that needs to be enabled on Communication Manager to support the AES adjunct. That would require a closer inspection of the customer configuration

So the simple answer is... I think so.

Some additional documentation is available for the SA8520 feature by entering a support request ticket via the devconnect web portal.

It is possible to take a phone that is logged in as extension XXXX and cause it to become logged in as extension YYYY through commands at the system access terminal. These commands can be accessed through the system management service (SMS) API supported by AE Services. Thus programmatic access is achievable.

It is not possible to take a phone that is logged out, and cause it to be logged in with an arbitrary extension/password. This would require an API to the phone itself, and there is not a programmatic interface that allows this functionality.

If you want to investigate this further, you need to look into the IP-hoteling feature " (SA8520) - Hoteling Application for IP Terminals"

Once the feature (SA8520) is enabled, you will see the extra field (IP Hoteling?)on the station form. you set the field to 'Y'. Then use the command 'enable ip-registration old xxxxx new yyyyy mac zzzzz' The MAC address field is optional.
The MAC address option provides some degree of protection from moving the "wrong" set. The provided value must match the MAC address of the device presently registered against the old extension.

There is a 'list tti-' command which provides information on the stations that could be acted on by the 'enable ip-registration' command.

There is a 'disable ip-registration' command as well as I recall, but my notes don't tell me anything about when you would want to use it.

I encourage anyone to work with the SAT first to understand the feature behavior, and then with the SMS interface.

Any information that is not in the action or model field in SMS should be put into the qualifier field exactly in the format it would be invoked on the SAT.

John

Computer Telephony Adjunct Link does not use the ASAI core and plus licensing on CM. Instead if the Computer Telephony Adjunct Link is used the licensing of functionality is done by the product at the other end of the Computer Telephony Adjunct Link which is either Avaya CT (legacy product) or AES. AES uses the adjunct link for TSAPI/JTAPI and for CVLAN for Interaction Center only. If TSAPI basic is licensed on AES then the application will have access to "ASAI Core" capabilities. If TSAPI advanced is licensed on AES for this CM then the application will have "ASAI PLUS" capabilities and it will also have phantom calls and cti stations (and the other ASAI Plus related features) .

as root or sroot

/sbin/service mvap restart

mvap is all the AE Services including TSAPI. and this is the safest (supported) way to restart the services.

Error 41,
An attempt to open a stream to a CTI-LINK or OAM name (Tserver/PBX ID) was made but this name is not in the Security Data Base.

The link is not in the SDB because it is not in-service. It is not in service because the license on the simulator version you have has expired. The license for the simulator you have was good during the first quarter of 2008, and expired 3/31/2008 (there was a grace period through the end of April 30, 2008). You will need to procure a new version of the simulator to get an operational simulator (now called Avaya IPCoDE)