Thank you,
I found the issue, i did not set serv-sobserv feature button for the observer
In the lab, I need to set the feature button for each observer extensions separately, but in actual deployment, I guess there would be a way to set it on mass, otherwise, it would not be possible to administer the button for thousand observers, is that correct?

Hi,
Iam trying this with the Dashboard, however, I got an exception response "requestIncompatibleWithObject" that does not help to tell what was wrong
I have registered 40018 as MAIN, which went find, and then try to activate observer service on 40016

---------------------
Outgoing XML 10
<?xml version="1.0" encoding="utf-8"?>
<ServiceObserveActivate xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.avaya.com/csta">
<observerDevice typeOfNumber="other" mediaClass="notKnown">40018:S8800:10.10.0.24:0</observerDevice>
<observeeDevice typeOfNumber="other" mediaClass="notKnown">40016:S8800:10.10.0.24:0</observeeDevice>
<observerConnStatus>serviceObserveNoTalkMode</observerConnStatus>
<nextCall>true</nextCall>
<observeeLocation>0</observeeLocation>
</ServiceObserveActivate>
-----------------------
Incoming XML 10
<?xml version="1.0" encoding="UTF-8"?>
<CSTAErrorCode xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
<operation>requestIncompatibleWithObject</operation>
</CSTAErrorCode>

Hello,
I the latest java developer guide, I see there is new ServiceObserveActivate/ServiceObserveDeactivate APIs for Service Observer recording method, but could not find any documents or guide about them
Some digging blindly into the sdk, look like it can be used like this:

ServiceObserveActivate sv = new ServiceObserveActivate();
sv.setObserverDevice(devID);
sv.setObserveeDevice(targetExt);

But I am still not sure how to use it properly
Please point me to an example how to use this activate/deactivate api
Thanks

Now iam running our application which was built with sdk 7.1 and latest mapping files, still the same exceptions

2018-05-08 20:52:37,237 com.avaya.proxy.castor.CastorUnmarshaller WARNING - Could not unmarshal: <?xml version="1.0" encoding="UTF-8"?>
<ServiceLinkStatusEvent xmlns="http://www.avaya.com/csta"><ns1:monitorCrossRefID xmlns:ns1="http://www.ecma-international.org/standards/ecma-323/csta/ed3">335</ns1:monitorCrossRefID><device><ns2:deviceIdentifier xmlns:ns2="http://www.ecma-international.org/standards/ecma-323/csta/ed3" typeOfNumber="other" mediaClass="voice" bitRate="constant">9600:AvayaAcm:172.25.8.20:0</ns2:deviceIdentifier></device><serviceLinkUp>true</serviceLinkUp></ServiceLinkStatusEvent>
The class for the root element 'ServiceLinkStatusEvent' could not be found.{file: [not available]; line: 2; column: 59}
at org.exolab.castor.xml.Unmarshaller.unmarshal(Unknown Source)
at org.exolab.castor.xml.Unmarshaller.unmarshal(Unknown Source)
at com.avaya.proxy.castor.CastorUnmarshaller.unmarshal(CastorUnmarshaller.java:186)
at com.avaya.mvcs.proxy.CstaUnmarshallerNode$CstaUnmarshallerProcessorThread.run(CstaUnmarshallerNode.java:198)
at com.avaya.common.util.concurrent.impl.RunnableWrapper.run(RunnableWrapper.java:57)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.xml.sax.SAXException: The class for the root element 'ServiceLinkStatusEvent' could not be found.
at org.exolab.castor.xml.UnmarshalHandler.startElement(Unknown Source)
at org.exolab.castor.xml.UnmarshalHandler.startElement(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)

We upgrade the SDK to latest 7.1 and got the same exception. Any advise?
Thanks

We upgraded AES
About the "client library", do you mean the SDK?

Hi,
We upgraded to 6.3 and the issue still persist? Do you have any other idea?

Hi,
I recently got this issue without our AES 6.1 when using DMCC Service Observer. The exception is
PM com.avaya.proxy.castor.CastorUnmarshaller unmarshal
WARNING: Could not unmarshal: <?xml version="1.0" encoding="UTF-8"?>
<ServiceLinkStatusEvent xmlns="http://www.avaya.com/csta"><ns1:monitorCrossRefID xmlns:ns1="http://www.ecma-international.org/standards/ecma-323/csta/ed3">221</ns1:monitorCrossRefID><device><ns2:deviceIdentifier xmlns:ns2="http://www.ecma-international.org/standards/ecma-323/csta/ed3" typeOfNumber="other" mediaClass="voice" bitRate="constant">9600:AvayaAcm:172.25.8.20:0</ns2:deviceIdentifier></device><serviceLinkUp>true</serviceLinkUp></ServiceLinkStatusEvent>
The class for the root element 'ServiceLinkStatusEvent' could not be found.{file: [not available]; line: 2; column: 59}
at org.exolab.castor.xml.Unmarshaller.unmarshal(Unknown Source)
at org.exolab.castor.xml.Unmarshaller.unmarshal(Unknown Source)
at com.avaya.proxy.castor.CastorUnmarshaller.unmarshal(CastorUnmarshaller.java:186)
at com.avaya.mvcs.proxy.CstaUnmarshallerNode$CstaUnmarshallerProcessorThread.run(CstaUnmarshallerNode.java:198)
at com.avaya.common.util.concurrent.impl.RunnableWrapper.run(RunnableWrapper.java:57)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.xml.sax.SAXException: The class for the root element 'ServiceLinkStatusEvent' could not be found.

I found this release note https://downloads.avaya.com/css/P8/documents/100176246 related to ServiceLinkStatusEvent issue, however, look like its only apply for AES6.2, while we are at 6.1

Please advise

Got it, Thanks for your help

I understand that the connectionid is combination of device id and callid, so there are multiple connectionid in each call. But let say, if I only monitored one extension in a call, what is the good way to get the connection id for other party?

Hi,
As in the doc, in order to set the SelectiveListening object for Selective Listening Hold, we would need ConnectionID of the parties. As I understand, ConnectionID which is retrieved from call events represent the call itself, aslo ConnectionID would be a combination of CallID and deviceID.
For example:
-A talk with B: ConnectionID=1 . A is monitored
-A and B and C in conference: I want to mute either A or B to C. How would I decide which connectionID for which A or B, since connectionID is for "between" A and B
Please advice
Thanks

Thanks for your quick answer

Hi,
We are having issue when trying to register a phone, got InvalidDeviceStateException. Then, we try with Dashboard, and have the same exception. However, after change a "Device instance" field to 1, instead of default, it seems to working
Can you please explain the issue
Thanks a lot

Thanks,
I have another question on this. When an extension got Terminated event, do I need to restart call monitor on that extension only, or the whole range of registered extensions? Since if its a switch issue, most likely all extensions will be affected

Hi,
Our DMCC application after running for a few weeks, would stop getting any Call Events such as Establish, Deliver..., while it still can getting media events such as media start/stop on the monitor extensions. We observed that about 2 seconds before we stop getting call events, there are Terminated events on monitor extensions. Eventhough Terminated event has description "A callback function which is automatically invoked on a listener previously added to a connectionID when the call has ended.", but i dont see it when calls ended at all in normal operation
We are using Multiple Registration method
Please let me know if you have experienced this issue
Thanks