Hi, we detect a change in XProtect 2019 API for protocol integration with Mobile Server.
When we ask for a video channel (either push or pull), we expect in response XML an address and port for the connection. Our customer, trying XProtect 2019, find out that the response XML lacks of these informations so we can’t create the connection to the video channel and push/pull images.
We can’t find any reference of this change in API docs or changelogs.
Is there a behaviour change in mobile server request/response so we have to adeguate our application? Or maybe an option we can set in mobile server configuration to fallback in previous behaviour?
Hi Emanuele,
Those parameters are removed from the response of the RequestStream command.
There were introduced long time ago but we found that in some situations (for example complex network configurations) Mobile server could misguide its client for correct ones.
Therefore it was decided that non of clients should use them.
Instead, clients know what is the address of the communication channel (resp address and port), as they fire successful commands to the server.
And they should be used for video channel address generation.
Parameters were left for backward compatibility with already more than 3 years old version of one of the Milestone Mobile clients.
I’ve checked the latest online version of the protocol documentation and fortunately they are not mentioned there (for the RequestStream command).
It is not possible to return Mobile server to previous behavior, except downgrading it.
Another direction that can be examined is switch from protocol integration to API one. Nowadays we do have pretty good MIP SDK Mobile integration possibilities for Web (JS), iOS (Swift), Android (Java) and Windows (.NET).
Of course those won’t work if your integration is based on C++ or Java (not mobile).
Hi, we made necessary changes in our software in order to correctly communicate with Mobile Server (using Protocol Integration).
After we made those changes, our customer has pointed out that with this version of Mobile Server, pushing video from mobile applications is slower than before.
Instead, pushing video from Milestone app has the same speed as always.
Although we made all the necessary changes in order not to use old address and port for the connection (we use now Mobile Server address and port), we didn’t make any other changes in our software.
Can you help us find with some hint?
Hi Emanuele,
I do not remember for any significant changes in the protocol for video push.
Somewhere around quoted version (2019 R1) where introduced video push with audio, but as far as I remember, protocol hasn’t been changed, but only extended (e.g. should be fully backward compatible).
I’ll ask around however.