If I send a request for SetAgentState and get a SetAgentStateResponse (ie. not a CSTAError), is it safe to assume that the agent is now in the state that was requested? If I send a SetAgentState to Ready and get a SetAgentStateResponse, can I safely assume the agent went into Ready state?

We have a product that has to poll the states of 100s to 1000 agents using DMCC's GetAgentState request. We are trying to figure out how best to tune the polling parameters to accommodate higher latency connections (150ms and up).

According to PSN28 ( https://downloads.avaya.com/css/P8/documents/101036842 ), we should limit the number of outstanding messages (messages that have been sent but have not received a reply) to a conservative value - and they give an example of 10 for that limit. Are there any other details on what would be considered conservative? For example, would 100 be fine? Less than 100?

Because of the outstanding message limit and the latency, the messages get backed up in a queue. We are aiming to poll for agent state changes every 2 seconds, but it's taking 15 seconds or more (eg. for 1000 users with a 150ms latency and 10 outstanding, it would be (1000 * 150) / 10 = 15000ms to go through all of the agents) because of these issues.

Increasing the outstanding limit will decrease this wait time, but we're not sure what values would be considered safe.

Are there any devices that I won't receive RTP streams for when using RegisterTerminalRequest (setting localMediaInfo in RegisterTerminalRequest registering in DEPENDENT mode and CLIENT media mode)? Will I always get streams regardless of protocol (SIP and so on)? Do all device types support it?

Judging from this, since what I'm doing is similar to call recording:
https://www.devconnectprogram.com/site/global/products_resources/avaya_aura_application_enablement_services/support/faq/dmcc/index.gsp#7

it looks like analog phones won't work.

Though I'm not sure how ServiceObserve and SingleStepConference work for call recording.

If I use a packet size greater than 20 in a RegisterTerminal request for Client Mode it gets ignored. When I get a MediaStartEvent I always get a packet size of 20, even though I asked for 40 or more.

Is there a way to get a larger packet size? I'm using G711U as the codec, but I'm not sure if that has anything to do with it. Using Avaya 7, maybe this is supported on newer versions?

Is there an easy way to associate an RTP stream with the call's CSTA call ID? MediaStartEvent doesn't contain this information.

I ran the DMCC dashboard on a different machine and I'm getting the audio streams while the softphone is running. It worked, thanks.

I would like to get the RTP streams for a device in real time. Using dashboard I've done a RegisterTerminalRequest, but I only get streams if the softphone isn't running. Using CLIENT media mode. If dashboard is running in MAIN dependency mode and softphone is not running I get RTP packets in client media. If dashboard is running in INDEPENDENT dependency mode and softphone is not running I get RTP packets in client media. I can't test DEPENDENT mode for obvious reasons. However, if I run the softphone in these scenarios I do not get any RTP packets in dashboard. I always get MediaStartEvents, but don't get the RTP packets if the softphone is running. The device ID is using a different instance from the softphone.

This is on Avaya 7. Is there any configuration that must be done on the switch to support this?

I seem to have the same problem and am using the XML SDK. What protocol version would I set for 7.1.1? I've only seen http://www.ecma-international.org/standards/ecma-323/csta/ed3/privA which is for 7.0. Is there anything else I'd need to do?

I'm getting a CSTA Error "coreCastor" when calling GetDisplay on certain phone models. On a pair of 1608-I's I get the error if I request the display and it's not empty (if the phone is idle I get the expected response). I also see the error if I monitor display updates and the display is change to non-empty.

I have a 9650C on my desk that works just fine though.

When I request a snapshot of a call with an external party I get a dynamic device ID (eg. T1122#2:xxx::0). Is there a way to request the device ID that contains the external number as seen in events (eg. 18005551234:xxx::0)? I need to snapshot calls for which I haven't received any events (calls already in progress) and where the event has <notKnown/> device IDs (I've seen this when picking up parked calls and blind transfer of a conference call).

Is there any documentation on the format of contentsOfDisplay when requesting GetDisplay on a device? I need to parse the phone number the device is currently on a call with. I realize this isn't going to work in all cases (during a conference for example the display simple says "Conference ...").