Hi Milos,
thanks for your response.I was able to install the Event Delivery SnapIn.
We are able to pull the presence state of a user via Adhoc Presence Retrieval.
But the following use case does not work (receive presence update events via long polling):
1) Login
2) pubSubContainersCreate
{
"pubSubContainer": {
"additionalResources": {
"capabilitiesPublication": {},
"presencePublication": {},
"serviceCapabilitiesSubscription": {},
"presenceSubscriptions": [ {}, {} ],
"watcherAuthReqSubscription": {},
"imSubscription": {},
"sentImSubscription": {},
"presentity": {}
},
"restPostbackUri": "https://subscribing-server.domain:port/EventDelivery/events"
}
}
3) presenceSubscriptionsReplace
{
"additionalProperties": {},
"resourceList": {
"additionalProperties": {},
"listDefaults": {
"aclConfirmHandling": "BLOCK",
"action": "ADD",
"additionalProperties": {},
"docType": "SUMMARY"
},
"presentities": [
{
"userIdentity": {
"addressSpaceId": "self"
}
},
{
"userIdentity": {
"addressSpaceId": "AVAYA_SMGR",
"userId": "user@domain.com"
}
},
]
}
}
4) long polling
In the presence services snapin (ps.log) log file we found the following warn message:
2019-09-16 14:06:32,709 [health-monitor-0] presence.health.HealthMonitorTask WARN - Health check failed - raising alarm HLTH_01 for issue: Number of configured users (1000) is over the support limit (0) for VM_PROFILE_1
In the event delivery snapin we receive the following warning:
2019-09-17 07:49:11,849 [GS-LRMI Connection-pool-1-thread-2] EventDelivery WARN - EventDelivery-7.1.2.0.9 - onEvent() Unacceptable content type application/vnd.avaya.presence-im.container.event.v1+json
2019-09-17 07:49:11,849 [GS-LRMI Connection-pool-1-thread-2] EventDelivery WARN - EventDelivery-7.1.2.0.9 - onEvent() Client accepted content type is application/*+json, application/json, /, text/plain
