Thanks for the help. Actually, intrigrant, the documentation is not complete. For example, they may list a supported function, "LineGetCallSTatus", but give no indication which elements in the structure they support or don't support. In particular, we need them to update the tStateEntry time, which they are not doing. How do we get them to properly update this field? Even better, a device specific function that gives us the call begin time so we know how long it has been in the queue if we load an application to monitor calls after the PBX already has calls in the ACD queue.
It does not appear that there is support in TAPI 2 for an "Is an agent logged in?". It is in their TAPI 3 implementation through a device specific feature in the MSP part of the implenentation, which is normally only for audio. Why? Can we get that as a device specific feature in TAPI 2, which is the lower level API and should have the richest feature support.
And lastly, it appears that through TAPI, the TSP will only report the first 10 calls in the ACD queue. They are all in the "offering" state awaiting answer. Is this a configuration issue that we can fix, or a severe limitation in the TSP. If the latter, how can we get them to allow us to see ALL the calls that we need to manage?
I'm not sure what the links were for since A. Julmar is a competitor to our offerings since we develop tools to make telphony development easy for TAPI and SIP, and B. This was code using their tools to dial in an ASP app, which has nothing to do with my question about how to get help with configuring Avaya's TAPI offering. Sorry if the original posting sounded like venting, I just wanted to find people who could actually comment on the internal workings of the TSP offerings. Thanks again for all the help.