Hello,

i have additional information about the CM and AEs Version, that are considered to produce the error regarding the missing vdn events.
CM 10.1.3.1.0.974.27937
AES-10.1.3.1.0.49-0

Another question regarding the vdn listener implementiation with AES Jtapi SDK.
How should the client handle the AES provider events "PROVIDER_OUT_OF_SERVICE" and shortly afterwards (within 5 seconds) followed by "PROVIDER_IN_SERVICE"?
Should the listeners be functional after such events or should the client remove the old listeners and register new listener on the Vdn?

Kind regards

JTAPI Version: com.avaya:jtapi:8.1.3.6

We have implemented a listener that extends the CallControlTerminalConnectionListenerAdapter and register this at VDNs.

We have running the same application on multiple customer installations.
Since a few days/weeks on two installations, we can observe the behavior, that the Listener does stop to omit events.
The listener seems to run x days and is working fine, suddenly no more events are received.
There are no provider events (i. e. out of service) or error massages.

The customer with the errors has the following AES Version running: 10.8.200.91 (SW Version: 8.1.3.3.2.4-0)
Another customer with the errors has the following AES 8.1.3.8 with CM 8.1.3.3.0.890.27564.

Is there a way to check the listener if it still is receiving events or if the connection for this listener is expired?

Hello,

i have created a snapin via the maven archtype "com.avaya.zephyr.sdk:service-archtype".
I did not change any of the generated code.

I provided a class that should log incoming sip messages. If i install this service in breeze as "intercept service", i receive the message that the call is intercepted (snapin is triggered by breeze), but the Sip Message Listener does not log any message.

The logfile contains the message, that the sip message listener is not provided.

What could be the cause, that the sip message listener is not provided.

Listener code:

@IncomingMessageListener

public class IncomingSipMessageListenerImpl implements IncomingSipMessageListener {



    Logger logger = Logger.getLogger(IncomingSipMessageListenerImpl.class);



    @Override

    public void requestReceived(SipRequest sipRequest, Map<String, Object> map) {

        logger.info("requestReceived");

        Iterator<String> headerNameIterator = sipRequest.getHeaderNames();

        while (headerNameIterator.hasNext()) {

            String headerName = headerNameIterator.next();

            ListIterator<String> headerValue = sipRequest.getHeaders(headerName);

            if(headerValue.hasNext()) {

                String value = headerValue.next();

                logger.info(format("Show request header %s: %s", headerName, value));

            }

        }

    }



    @Override

    public void responseReceived(SipResponse sipResponse, Map<String, Object> map) {

        logger.info("responseReceived");



        Iterator<String> headerNameIterator = sipResponse.getHeaderNames();

        while (headerNameIterator.hasNext()) {

            String headerName = headerNameIterator.next();

            ListIterator<String> headerValue = sipResponse.getHeaders(headerName);

            if(headerValue.hasNext()) {

                String value = headerValue.next();

                logger.info(format("Show response header %s: %s", headerName, value));

            }

        }

    }

}

Logfile:

2022-03-30 11:35:59,286 [SoapConnectorThreadPool : 1610] SessionTracker FINEST - TheSipMessageListener is not provided

2022-03-30 11:35:59,286 [SoapConnectorThreadPool : 1610] SessionTracker FINEST - IncomingMessageListener is not provided

2022-03-30 11:35:59,286 [SoapConnectorThreadPool : 1610] SessionTracker FINEST - OutgoingMessageListener is not provided

2022-03-30 11:35:59,286 [SoapConnectorThreadPool : 1610] SessionTracker FINEST - findListeners CallReconstructionListener is not provided

2022-03-30 11:35:59,286 [SoapConnectorThreadPool : 1610] SessionTracker FINENo CallListener from properties.xml. Procced with scanning

2022-03-30 11:35:59,288 [SoapConnectorThreadPool : 1610] SessionTracker INFO-  Listener class "..MyCallListener" found with annotation "TheCallListener" and implementation of "CallListener"

2022-03-30 11:55:02,777 [SipContainerPool : 2] SessionTracker INFO - Entered callIntercepted.

2022-03-30 13:11:51,658 [SipContainerPool : 4] SessionTracker INFO - Entered callIntercepted.

properties.xml

<?xml version="1.0" encoding="UTF-8"?>

<service xmlns="http://archiveschemas.aus.avaya.com/properties"

	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

	xsi:schemaLocation="http://archiveschemas.aus.avaya.com/properties properties.xsd"

    name="${serviceName}" version="${serviceVersion}" application="${serviceName}-${serviceVersion}">

	<smgr>

		<description>SessionTracker</description>

		<orig_order>1</orig_order>

		<orig_group>1</orig_group>

		<term_order>1</term_order>

		<term_group>1</term_group>

		<fs_component>true</fs_component>

	</smgr>

</service>

Hello,

i am testing the current use case:
Via clientSDK I have implemented an attented transfer.

User A is starting a phone call with User B. (Call 1)
User B sets the call with Uer A on hold.
User B starts a phone call with User C. (Call 2)
User B is forwarding User A to User C.

if use the attentedTransfer() method to execute the transfer.
Uer B is executing call2.attentedTransfer(call1);

Is it possible to provide call information of User A to User C?

Kind regards,
Domenic

Hello,

i am trying to use the Node Status API to request the status of nodes in the cluster.
The environment is one breeze cluster with one server.

The request of "Cluster.getNodeStatus()" results in an exception:

2022-02-07 10:55:15,341 [WebContainer : 25] CallParkSnapIn ERROR - CallParkSnapIn-1.1.4 - Failed to request node status

com.avaya.collaboration.cluster.NodeStatusException: getListOfNodeStatus Node Status either null or empty

        at com.avaya.collaboration.cluster.util.NodeStatusRetrieverImpl.getListOfNodeStatus(NodeStatusRetrieverImpl.java:77)

        at com.avaya.collaboration.cluster.ClusterDelegateImpl.getNodeStatus(ClusterDelegateImpl.java:38)

        at com.avaya.collaboration.cluster.Cluster.getNodeStatus(Cluster.java:82)

        at mycode.wrapper.BreezeFactoryWrapper.getNodeStatus(BreezeFactoryWrapper.java:51)

.......

Caused by: com.avaya.collaboration.cluster.NodeStatusException: getListOfNodeStatus Node Status either null or empty

        at com.avaya.collaboration.cluster.util.NodeStatusRetrieverImpl.getResponse(NodeStatusRetrieverImpl.java:118)

        at com.avaya.collaboration.cluster.util.NodeStatusRetrieverImpl.getListOfNodeStatus(NodeStatusRetrieverImpl.java:72)

        ... 48 more

Is it possible to use getNodeStatus() method in this setup?
Do i have to change the settings in system manager to use this method?

The other feature of the snapin work fine, call handling is executed succesfully.

Kind regards,
Domenic

Hello,

i have developed a callable snapin which receives calls and starts a audio playback.
The snapin contains a rest controller which receives request to forward or drop the received calls.

The snapin is installed on a breeze setup which is a cluster with two servers.

Now i tried a kind of HA-Testing:
In case the incoming call is handled by server 1, the call is answered and the audio is played.
I shutdown the VM of the server 1 and send a drop call request to the rest controller within the snapin.
The server 2 is handling the call and tries to execute the "call.drop()" method.

This action causes the following exception:

....

java.lang.IllegalStateException: Request timed out after 5000 ms

        at com.avaya.collaboration.call.gs.interact.RemoteCommandManagerImpl.invoke(RemoteCommandManagerImpl.java:103)

        at com.avaya.collaboration.call.util.FeatureCallHelperImpl.invoke(FeatureCallHelperImpl.java:90)

        at com.avaya.collaboration.call.ProxyCall.drop(ProxyCall.java:123)

        at com.mycode.call.CallService.dropCall(CallService.java:92)

        at com.mycode.call.CallController.dropCall(CallController.java:27)

....

I was expecting, that the snapin is able to drop the call, regardless which server is handling the request.

Kind regards,
Domenic

Hello,

can someone estimate when a new version will be available or the problem will be fixed?

Kind regards,
Domenic

Hello,

i have downloaded the presence snapin bundle with version8.1.2.0.140.
The bundle only contains the PResence Rest API documentation with release 8.1.0 from March 2019.

I can not find any description about the bsid.

Have there been other changes?

The problem is still that i can not execute the long poll request.
The logfiles of the EventDelivery Snapin only complains about bad request:
validateRequestAndGetRestPathParameters() sending error response indicating that the request was bad

I am using the request from the login response, so i do not change any parameters.

Where can i find more information about the error? (Maybe which parameter or header is wrong)

Kind regards,
Domenic

message deleted

Hello Pavan,

thanks for your response.

If i use the request with the bsid:

https://PresenceServer/services/EventDelivery/event-delivery/channels/long-polling/bsid/57f2ef45-61ea-4079-bdc3-1a94a15695/clients/clientCustomer

The request results in a "400 Bad Request".

The logfile contains the following entries (log level is "all")

2020-05-05 14:27:33,844 [WebContainer : 5] EventDelivery FINE - EventDelivery-8.1.2.0.3 - doGet() subscribing to notification URL=/EventDelivery-8.1.2.0.3/event-delivery/channels/long-polling/bsid/3d17183d-ad29-4e29-9878-657a7236dd64/clients/12345

2020-05-05 14:27:33,845 [WebContainer : 5] EventDelivery FINEST - EventDelivery-8.1.2.0.3 - validateRequestAndGetRestPathParameters() active threads=1135

2020-05-05 14:27:33,845 [WebContainer : 5] EventDelivery ERROR - EventDelivery-8.1.2.0.3 - validateRequestAndGetRestPathParameters() sending error response indicating that the request was bad

Any idea, why the request is bad?

Kind regards,
Domenic

Hello,

we have build an application that uses the presence rest api.
Connecting to the the Event Delivery Snapin and receiving updates work fine with:

Event Delivery Snapin: 7.1.2.0.9
Presence Services Snapin: 7.1.2.0.233

We are able to authenticate, create a pubSub container and long poll the events.
Here a part of the response from presence after login:

{

    "presenceImResources": {

        "userId": "502",

        "clientId": "clientCustomer",

        "resources": {

            "notificationService": {

                "longPolling": {

                    "method": "GET",

                    "href": "https://PresenceServer/services/EventDelivery/event-delivery/channels/long-polling/users/502/clients/clientCustomer"

                }

            }......

But with the following snapin versions, the long polling request result in a "400 Bad Request":
Event Delivery Snapin: 8.1.2.0.3
Presence Services Snapin: 8.1.2.0.23

Here a part of the response after login (login and pubSub container works):

{

    "presenceImResources": {

        "bsid": "57f2ef45-61ea-4079-bdc3-1a94a1569501",

        "clientId": "clientCustomer",

        "resources": {

            "notificationService": {

                "longPolling": {

                    "method": "GET",

                    "href": "https://PresenceServer/services/EventDelivery/event-delivery/channels/long-polling/bsid/57f2ef45-61ea-4079-bdc3-1a94a15695/clients/clientCustomer"

                }

            }...

I dont understand why userid is not in the response, and what the bsid is used for.

The latest documentation that i have found was "Release 8.1.0 March 2019". In this document the bsid is not described.

Kind regards,
Domenic

Hello,

the problem could be solved by using

String callId = com.avaya.collaboration.call.Call.getId();

If we are using the ID of the Call and not the UCID, the call can be retrieved from Breeze.

Kind regards,
Domenic

Hello,

i am using the javascript CSDK.

Kind regards,
Domenic

Hello,

i have tested the web gateway (version 3.7.0.0.225) setup with the Communication Services Package Sample App version 4.1.1.
The app works fine, i can execute calls to other endpoints.
But if i logout the user i can see error messages in the browser console.

The first error message is:

Access to XMLHttpRequest at 'https://WEBGATEWAY-URL/csa/bsid/0c6651b0-3653-42-9f3d-d02f636d527/resources/tenants/default/users/self/clients/0c6651b0-3653-42-9f3d-d02f636d527' from origin 'null' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

The second message is:

DELETE https://WEBGATEWAY-URL/csa/bsid/0c6651b0-3653-42-9f3d-d02f636d527/resources/tenants/default/users/self/clients/0c6651b0-3653-42-9f3d-d02f636d527 net::ERR_FAILED

The webgateway has enabled "Cross-Origin Resource Sharing" and "Allow access from any origin".

What could cause this error message?

Kind regards,
Domenic

Hello,

i am using the presence rest api to request presence status data.
The rest api returns calendar information, if a current calendar is active in outlook/exchange.

Is it also possible to request calendar data of future appointments?

Kind regards,
Domenic