There're two AES servers in our infrastracture (the old one and the new one).
When I try to start an event monitor on one of them, subscribedResourceAvailability error arrives.

-----------------------

Outgoing XML 3

<?xml version="1.0" encoding="utf-8"?>

<MonitorStart xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">

    <monitorObject>

        <deviceObject typeOfNumber="other" mediaClass="notKnown">220:ADACs8300:0.0.0.0:0</deviceObject>

    </monitorObject>

    <requestedMonitorFilter>

        <callcontrol>

            <conferenced>true</conferenced>

            <connectionCleared>true</connectionCleared>

            <delivered>true</delivered>

            <diverted>true</diverted>

            <established>true</established>

            <failed>true</failed>

            <held>true</held>

            <originated>true</originated>

            <retrieved>true</retrieved>

            <transferred>true</transferred>

        </callcontrol>

        <logicalDeviceFeature>

            <doNotDisturb>true</doNotDisturb>

            <forwarding>true</forwarding>

        </logicalDeviceFeature>

    </requestedMonitorFilter>

    <extensions>

        <privateData>

            <private><AvayaEvents><invertFilter>true</invertFilter></AvayaEvents></private>

        </privateData>

    </extensions>

</MonitorStart>

-----------------------

Incoming XML 3 220:ADACs8300:0.0.0.0:0

<?xml version="1.0" encoding="UTF-8"?><CSTAErrorCode xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"><subscribedResourceAvailability>generic</subscribedResourceAvailability></CSTAErrorCode>

Does this error appear only in case of licensing issues (lack of sufficient Basic TSAPI license I suppose)? Are there any CM configuration options which may lead to this behavior?

The full list of possibilities from the TSAPI Programmers reference is:

GENERIC_SUBSCRIBED_RESOURCE_AVAILABILITY (41)
The request has failed for one of the following reasons:
– A required feature has not been provisioned or enabled. For example:
o The deviceID corresponds to a station with type “CTI” and the “CTI Stations” feature is not enabled on Communication Manager.
o The deviceID corresponds to a non-CTI station
administered without hardware (AWOH) and the “Phantom Calls” feature is not enabled on Communication Manager.
o The deviceID corresponds to a SIP station, and the “Type of 3PCC Enabled” administered for the station is not set to “Avaya”.
o There is an off-pbx-telephone station-mapping
administered for deviceID on Communication Manager.
– The TSAPI Service could not acquire the license(s) needed to satisfy the request.

I think the lack of license is the most likely cause. If you monitor a device via 2 AE Services, you will consume 2 TSAPI Basic licenses.

Martin