Long Delay With Bringing Connections to Client Mobile Camera App Back Up After Idle Time
(Doc ID 2130961.1)
Last updated on AUGUST 19, 2019
Applies to:Oracle Communications Instant Messaging Server - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
We are using Instant Messaging 220.127.116.11.0.
We use a particular vendor's cameras that implement XMPP protocol to talk to the IM server.
The problem is that IM takes too much time to bring back up and running, all the user's connections (around 30-45 seconds) when the client application goes idle.
Other XMPP servers, for instance Openfire, are able to connect to the cameras instantly.
We think this could be a configuration problem, as we already know that the same vendor's cameras mobile app has the same behavior we are looking for, and they are using OCIM as their XMPP Server.
The problem is seen, using the following scenario:
• A user connects to its installation via the mobile app.
• Once the connection is made with the OCIM server, and it brings the user's roster, it gives access to every camera in its installation.
• The system works pretty fine as long as the user continues to interact with the app.
• The device is sending ping requests to the server every 30 seconds (cell phone).
• If the user stops interacting with the app, then the app goes into the background.
• The server then knows that the app has gone idle, so it closes the connection with the roster on behalf of the client (after around 35 seconds of inactivity).
• Once the user brings the app back to life, in our point of view, OCIM takes too much time to bring all of the user's connections back up and running (around 30-45 seconds). Sometimes it's better to log out and log in again to the app, to avoid this delay.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document