That is good news! Ofcourse a native onvif-driver that works just like other Iridium drivers is the best.

In the meantime I will give it a go to try and fix the current javascripts to make PTZ work.  We just installed the PTZ-camera at the clients location, so now he is getting a little bit impatient to play with his new toy on his control-screen.

No, I cannot get the PTZ control to work.

I have started logging response messages and see that the camera is complaining about unknown profiletoken "quality_h264".  This seems to be hardcoded in the XMLData unit.  Why ?

I also used Wireshark to compare what Iridium OnvifModule is sending to the camera and what Onvif Device Manager is sending.  The XML differs alot, especially where Iridium is using "tptz:" and "tt:" namespaces, where ODM just omits this.

Yesterday we installed the PTZ-camera at the clients location, so I do not have direct access to it anymore.

Now I use the external address to access the camera. This works fine in ODM, but the Iridium Onvif Module shows no image. I guess this is because the module uses the adres reported by the camera as the RTSP stream ?

Also : the arrows on the PTZ controls in the Module are wrong.  OK, this is just cosmetic and I can easily fix it myself, but thought you should now and fix it in the official module too.

I managed to change the ONVIF module a little to get it working with a camera that needs authentication for GetSystemDateAndTime.

First I changed in SOAP Unit:

this.GetSystemDateAndTime = function (in_oAuthData)

{

if (typeof in_oAuthData !== 'undefined')

{

return getAuthWrap(DATA.GetSystemDateAndTime.Data, in_oAuthData);

}

else

{

return getWrap(DATA.GetSystemDateAndTime.Data);

}

};

And then I changed in UNITOnvifCam:

function SyncTime()

{

//GCam.StateLoading(true);

l_oSubDevice.SetFeedback("StateLoading", true);

Send(SOAP.GetSystemDateAndTime(AuthData), SOAP.DATA.GetSystemDateAndTime.Action, syncTimeParse, Service);

l_bServicesError = false;

}

Now I can connect to the PTZ cameras and view their live stream

But: PTZ commands are NOT working :-(

Now that I got my test-camera working, I tried connecting to my clients PTZ cameras.

I already found out they use NS.S="SOAP-ENV", so I can manually add them.

I run into the next problem:  GetSystemDateAndTime   is requesting without authentication. Yes, I know the Onvif specs allow for this, BUT many cameras (including the Everfocus and Provision cameras my client has), do not allow unauthenicated.

The author of the working node.js Onvif implementaion writes about this:

/ The ONVIF spec says this should work without a Password as we need to know any difference in the
// remote NVT's time relative to our own time clock (called the timeShift) so we can calculate the
// correct timestamp in nonce authentication header.
// But.. Panasonic and Digital Barriers both have devices that implement ONVIF that only work with
// authenticated getSystemDateAndTime

His solution is:

if (xml && xml.toLowerCase().includes('sender not authorized')) {
// Try again with a Username and Password

I see that Onvif Device Manager uses this same work around. So can we implement this in the Iridium Onvif Module?

What do you mean by "does the web interface of your camera?"

Hi Vladimir, I did some more debugging, dumping the XML responses to IR.Log and found the camera I'm testing with uses 

NS.S="env", NS.D="env". So I got it to work manually. But I guess those parameters are different for many camera's.

So now, I'm trying to figure out how to use this module, without the scanner that does not work. Also in my project the GUI from the module would not be used.

I think there should be an option to manually add camera's, by inputting the address.

Normally all you need is the IP-adres, port, login and password.  Functions in the ONVIF module should handle everything else.

Can you please make sure that comments in Modules are in English instead of Russian? Having to use Google translate all the time during figuring out how this works, does not really help.

1. I told you the scanner does not work.

"Scanning for ONVIF cameras in my network gives no results, even though I have 5 of them. All of them are found with ODM.

Also scanning would only work within your own network, not for adding cameras that reside elsewhere on the internet. I think there should be an option to manually add camera's, by inputting the address."

2. I always have the latest Iridium release

iRidium Environment: 1.3.25.0.23568

iRidium Studio: 2.0.15.23568 (64 bit)
Transfer: 1.1.3.14538 (32 bit)
iRidium: 1.3.25.23568 (64 bit)
Server: 1.3.25.23568 (32 bit)

iRidium lite: 1.3.13.19979 (32 bit)
Server lite: 1.3.13.19979 (32 bit)

Dividing by product is fine, but in that case you should keep the language-forums and archive together with the main product forum as sub-forums or categories. 

Another simpler option: just make available the global search as a separate "advanced search" or something like that, so people can choose to search all, or maybe even have an option to choose which forums to search.

Hi Aleksandr,

Ah, now I see what happened: because I wrote an email to support with my personal email-adres, I guess automatically a new account was created for me. And when I click the "open comment" link in the reply-mai, I was automatically logged in with that new account.  So then I could not see the post that was "on moderation" anymore.

No, the search does not work great for the Iridium Support forums.

Example: when go to support.iridiummobile.net and I search for "Onvif", I get : No similar topics found.

But if I go to the Russian forum, I get 2 results

And if I go to the Archive, I get 1 result

See screenshots below.

I expect to see all search results in all forums and knowledgebases when searching from the main page.

Vladimir wrote he would ask the developer (= UserEcho) about this. But to show you this function is already implemented in the forum-software, I started the testforum at dennispiet.userecho.com

On there I made 2 knowledgebases and 3 forums.  When I do a global search "test", I get results from 3 forums and 2 knowledgebases.