Author Message
BrunoHaas2
Joined: Feb 5, 2009
Messages: 40
Offline
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
JohnBiggs
Joined: Jun 20, 2005
Messages: 1141
Location: Rural, Virginia
Offline
There may be a better description of these capabilities in the TSAPI for Communication Manager Programmer's guide. I do not have time to do a lot of digging for you, and alot of staff is already on holiday.

https://www.devconnectprogram.com/fileMedia/download/b8929483-72e5-4dd0-907f-e99b112dad83
page 1037-1038

They are probably exposed in the latest DMCC Dashboard as well.
BrunoHaas2
Joined: Feb 5, 2009
Messages: 40
Offline
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>
JohnBiggs
Joined: Jun 20, 2005
Messages: 1141
Location: Rural, Virginia
Offline
The XML by itself is often insufficient to troubleshoot. I suggest enabling FINEST tracing on AE Services and looking at the dmcc-trace log file.

https://www.devconnectprogram.com/site/global/products_resources/avaya_aura_application_enablement_services/support/faq/dmcc/index.gsp?tab=other&accordion=faq-60
BrunoHaas2
Joined: Feb 5, 2009
Messages: 40
Offline
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?
JohnBiggs
Joined: Jun 20, 2005
Messages: 1141
Location: Rural, Virginia
Offline
Threre are tools that allow for the mass provisioning of groups of stations. The Avaya Site Administrator (I dont think this is available anymore) and ProVision tools both allowed export of a station to a spreadsheet, manipulating rows of data and importing the spreadsheet back into the system as an 'add' or 'change' operation (delete was also supported IIRP).

You can also build applications to use System Management Services User Managment Web API or Applications Enablement Services System Management Service that can do bulk provisioning of various provisionable objects.

Communication Manager's SAT supports a duplicate station that can make copies of a station and add them as new stations. This operation is limited in the number it can duplicate (IIRP up to 16).

I am a bit surprised that activate/deactivate through the API of SO requires a button to be provisioned. I am not surprised that monitoring a station's service observing status requires a SO button to be provisioned.
Go to:   
Mobile view