You will need to restart WebSphere by logging onto CE server and executing command: restart WebSphere

The WebSphere restart should take about 30 seconds to a minute. After restart, launch Collaboration Designer and you should see custom event listed. Another alternative to WebSphere restart is to re-install CollabDesigner/WFE snap-in.

In future release the addition of custom event and update to Designer will occur on the fly.

Hi Jan,

Your log snippet contains following error message:

2014-04-29 09:26:34,876 ERROR-[PRESENCE_V3-10.108.4.138:5248-2][PNL284] (NotificationExceptionsHandling.java:58) NotificationsRemoteExceptionHandling: Likely cause of failure - the notification listener is either notlistening at the end point registered or the response sent by the listener is incorrect and does not comply to the specification

2014-04-29 09:26:34,876 DEBUG-[PRESENCE_V3-10.108.4.138:5248-2][PNL284] (NotificationExceptionsHandling.java:60) org.apache.axis2.AxisFault: The host did not accept the connection within timeout of 10000 ms

Please check that your listener is receiving the message and that a proper response is being sent back to ACE. For response, I would recommend monitoring the HTTP traffic using tool ( Tcpmon, Wireshark, etc ). If you continue to have issues, please open a support ticket from the DevConnect Portal.


Thank you,
Dipesh

Hi Jan,

Please have a look at the Avaya Agile Communication Environment™ Web Services documentation, Chapter 18 - Presence. The publish presence is supported by ACE but only for AS 5300 users. It is not supported for other server providers.

Hi Jan,

The appcoredebug log file will contains information for events being sent from ACE to your application. In fact that is the primary log file you should reference to for most of the ACE APIs.

/var/avaya/ace/log/AppSrv01/app/appcoredebuglog.log

You will need to enable debug mode in order to view all logging.

1. Login to ACE OAMP Console
2. On the menu bar, choose Configuration, Server. Click the Logger tab.
The Debug Logger Configuration dialog box appears.
3. From the Group list, select the logger group.
4. From the Logger Level list, select the type of log messages to be stored and
generated into a log file (one of TRACE, DEBUG, INFO, WARN or ERROR), for the
selected logger group. Select DEBUG.
5. (Optional) From the Rotation Size list, select the size of the log file that stores the log
messages. When the log file reaches the specified threshold value, the system
closes the log file, opens a new one, and rotates the logs gathering into the new log
file.
6. Click Submit to save the configuration changes. Otherwise, click Reset to roll back
the changes.

Hi Jan,

One way is to use HTTP Handler. This is probably most equivalent to HttpServer.
http://support.microsoft.com/kb/308001

Another approach would be to use web model such as WCF ( a web service ), or full web MVC framework.
WCF - Create a web service and handle events from ACE: http://msdn.microsoft.com/en-us/library/dd456779(v=vs.110).aspx
MVC - Create contoller which can process ACE events: http://www.w3schools.com/aspnet/mvc_intro.asp

Regardless of the method above, if you observe ACE log file you will notice attempts being made to send events to application side endpoint. This is done periodically and if ACE is unable to send messages to the endpoint and if timeout has reached then ACE will stop sending events.

You have the correct link. You want to select "Avaya ACE Web Services Trainer Release 6.2.2.0 (20.8 MB .zip)" link and download the zip file. I've included the direct link here for you: https://www.devconnectprogram.com/fileMedia/download/8ad9a62b-e048-4af3-a150-c323fea54c80

Once downloaded, unzip the file and navigate to Trainer's Java source code located here:
\ACEWSTrainer_6.2.2.0\src\com\avaya\devconnect\acewstrainer\

You will find the calls to ACE web services ( including presence - startPresNotification method ) located in RequestManager.java. The TrainerGUI.java contains graphical code which is based on event listeners (e.g. button click) which triggers submit by user. Hope this helps!


Thanks,
Dipesh

The ordering of your API methods looks correct. Also, you are correct in that the reference parameter should be set to null when calling SubscribePresence() API. Your problem appears to lie in startPresenceNotification() method invocation. Your application must provide a unique correlator value for reference parameter that is globally unique to all applications using ACE. There are many schemes that could be used to guarantee uniqueness, including standardized mechanisms such as RFC4122 describing the Universally Unique IDentifier (UUID). Applications can embed additional context information in the correlator, as the correlator will accompany all events delivered to the application. The Avaya ACE Web Services Trainer provides code sample for Presence APIs. You will notice a built in utility that generates a correlator which serves the purpose of the sample. Although for Production deployments, it is advised to use RFC4122 or similar standard.

There are few things I would recommend checking..

1) Please check that you are providing file URI in proper file URI format such as this: playItem.setSource("file:///usr/tmp/MOH.wav");
2) Check file permission for directory/file where your wav is located. CE must be able to access the file.
3) There are set of default wav files that are deployed with AMS. You could see if the default wav file can be played. If so, then the issue could be with your wav file or permissions to the file/directory. The default wav file as follows:
playItem.setSource("file:///opt/avaya/ma/MAS/platdata/Announcements/mmf/system/default/twenty-five-dollars.wav");

Glad to hear it works!

Yes, your statement is correct. For CE 2.0, the ServiceLifeCycle relies on SIP servlet which requires the CallListener and generated sip.xml from the CE archetype.

I created a test service in my lab with class that implements ServiceLifeCycle and I am able to see the log statement. Using latest CE 2.0 SP2. I'm attaching the test service for you and log output below:


2014-03-13 11:44:27,709 [SoapConnectorThreadPool : 1] call.servlet.ListenersFinder INFO - Listener class "com.avaya.test.TestService.Poller" found with annotation "TheServiceLifeCycle" and implementation of "ServiceLifeCycle"
2014-03-13 11:44:27,712 [SoapConnectorThreadPool : 1] call.servlet.ListenersFinder INFO - Listener class "com.avaya.test.TestService.MyCallListener" found with annotation "TheCallListener" and implementation of "CallListener"
2014-03-13 11:44:27,759 [SoapConnectorThreadPool : 1] test.TestService.Poller INFO - TestService-1.0.0.0.0 - >>> Poller initialized


Thanks,
Dipesh

When you generate the Maven project via "mvn archetype:generate", did you select archetype, com.avaya.zephyr.sdk:service-archetype (Collaboration Environment Service Archetype)?

If not, please select Collaboration Environment Service archtype as it will generate the project with required configurations for the Call Listener. Specifically, the web.xml and sip.xml configuration files.

Once your project is created using archetype mentioned above, you will find MyCallListener class which is created for you automatically. Within this class, you will find that class uses @TheCallListener annotation and extends CallListenerAbstract.

The CE archetype provides a good starter template but if you need specific example then I would recommend reviewing HelloWorld sample service which is available within the SDK. If you have further queries please let me know.


Thanks,
Dipesh

Hi Daniel,

This forum is for Avaya Agile Communication Environment (ACE) product. For Experience Portal, please open a ticket so that we can get SME to assist with your questions.

Thanks,
Dipesh

Hi Josep,

The call identifier is necessary in order to answer the call as it identifies the unique call. Please have a look at Call Notifications chapter within ACE Web Services document. I believe this will answer both of your questions.

You can subscribe for call notifications on device(s) which will enable ACE to notify your client that a call event has occurred (e.g. ringing event, answer event, etc) using startCallNotification API. For ringing event, you will receive call identifier and this can allow your application to respond with answerCall (see Third Party Call Control Extensions chapter). Once you have answered, ACE will trigger another event to your application displaying parties on the call. Alternatively, you can also register for call events for a call session via makeCall by providing 'reference' parameter. This will provide you call notifications for all activities related to the call session. Please see makeCall request parameters details in web services documentation for details.

Both of these methods for call notifications subscriptions are available on ACE WebServices Trainer for you to exercise. The first method I mentioned above is located under Call Notifications tab and the second method is located in the makeCall Pane. Simply check the "Events" checkbox. If you observe the resulting SOAP output and events triggers, this will give you better idea.


Thank you,
Dipesh

Hi Josep,

The namespace looks correct as I see it here and as I mentioned previously, we do not have any PHP examples available. As you may know, we require technical support ticket opened via DevConnect portal for assistance with technical issues. In addition, the free technical support at your Registered membership level is limited to basic Tier 1-2 type questions which cover basic informational questions and API / Documentation issues.

Tier 3 and 4 support for more detailed questions, as you have submitted here, is provided through Support-enabled membership. For details please review https://devconnect.avaya.com/public/dyn/d_dyn.jsp?fn=876 Support enabled membership offers more in-depth investigation including trace capture, log file analysis or investigation with Avaya R & D.

We strongly recommend Support-enabled membership as a minimum level of support which allows you to take advantage of additional benefits including; priority response to technical questions, Tier 3 & 4 support for application development and more. A 2013 Support-enabled membership provides a block of ten (10) Enhanced Technical support hours for $2000.

If you wish to gain access to support without becoming a Support-enabled member, you may purchase support for this product at $300 per hour. To continue with per hour support, please open and reply in support ticket with your detailed questions and we will provide an estimate of the number of support hours required. You may then move forward with payment, or take some other avenue to get your issue resolved.

Regards,
Dipesh

Hi Josep,

The ACE Web Services are exposed so that web client can be written in variety of different languages (Java, .NET, PHP, etc). Currently we only have examples illustrating ACE Web Services in Java as Java is most commonly used language by our members.

I am not a PHP expert by any means but the error seems to indicate issue is with the header in your soap request. The response type expected does not match. You will need to investigate this further with PHP development experts.

I will also recommend using TCP monitoring tools such as WireShark or TCPMON to see what the actual request header is generated by your PHP soap_client call. You can execute same API call from SoapUI and observe the header there. The header seen from SoapUI should match request being sent from your PHP code. Again, to determine why request is not being formulated correctly, you will need to seek out help with PHP developers/community.


Thank you,
Dipesh