I have had some success but still not able to perform selective listening. Getting error ambiguos error. See code:
Below is the XML transaction log. I didn’t include all the stuff leading up to the Selective Listening Hold attempt. It starts with a Snapshot request, the response for which shows that I had a three-way conference going on callID 65 and that the Agent’s device was “35046:S8720::0”. Then it shows the Selective Listening Hold request, and finally the error response (valueOutOfRange). I have no idea what value is out of range.

Outgoing XML 15
<?xml version="1.0" encoding="utf-8"?>
<SnapshotDevice 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">
<snapshotObject typeOfNumber="other" mediaClass="notKnown">35046:S8720::0</snapshotObject>
</SnapshotDevice>
-----------------------
Incoming XML 15 35046:S8720::0
<?xml version="1.0" encoding="UTF-8"?>
<SnapshotDeviceResponse xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
<crossRefIDorSnapshotData>
<snapshotData>
<snapshotDeviceResponseInfo>
<connectionIdentifier>
<callID>65</callID>
<deviceID typeOfNumber="other" mediaClass="notKnown" bitRate="constant">35046:S8720::0</deviceID>
</connectionIdentifier>
<localCallState>
<compoundCallState>
<localConnectionState>connected</localConnectionState>
<localConnectionState>connected</localConnectionState>
<localConnectionState>connected</localConnectionState>
</compoundCallState>
</localCallState>
</snapshotDeviceResponseInfo>
</snapshotData>
</crossRefIDorSnapshotData>
</SnapshotDeviceResponse>
---------------------
Outgoing XML 17
<?xml version="1.0" encoding="utf-8"?>
<SelectiveListeningHold xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.avaya.com/csta">
<selectiveListening>
<subjectConnection>
<callID xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">65</callID>
<deviceID typeOfNumber="other" mediaClass="notKnown" xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">35046:S8720::0</deviceID>
</subjectConnection>
<allParties>false</allParties>
<selectedParty>
<callID xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">65</callID>
<deviceID typeOfNumber="other" mediaClass="notKnown" xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">35046:S8720::0</deviceID>
</selectedParty>
</selectiveListening>
</SelectiveListeningHold>
-----------------------
Incoming XML 17
<?xml version="1.0" encoding="UTF-8"?>
<CSTAErrorCode xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
<operation>valueOutOfRange</operation>
</CSTAErrorCode>

Your problem here is that the subjectConnection and the selectedParty are the same (35046). You are asking Communication Manager to block audio from 35046 being heard by 35046 which, I think, does not make much sense and is probably not what you intended.

I suggest that you download a copy of "TSAPI for Avaya Communication Manager Programmer's Reference". It gives a much more detailed description of the Call Control functions than the DMCC Programmers Guide can.

I also suggest that you have a look at the Devconnect Product FAQ "What is the procedure for enabling and accessing the AE Services logs for TSAPI (trace, tracing, g3trace, csta_trace)?". It is in the "FAQ: AE Services TSAPI -> General" section. Coupled with the TSAPI reference, the TSAPI traces are a very powerful debugging tool and give much more information than DMCC error codes can.

Martin