rickwookie

On ‎1‎/‎28‎/‎2019 at 1:22 PM, riogrande75 said:

Anyhow, don't use General_VTOXXX_Eng_P_16M_SIP_V4.000.0000000.5.R.20181030.bin as they removed asterisk support.

With that version installed I never got any successful connection setup to asterisk.

That's interesting. It's true that Asterisk is not an option in the drop down menu in that firmware, but I just set mine to 'VTO' and it connects without any problem to my RasPBX box. That's why I've assumed that this setting is irrelevant to the VTO as a SIP client.

8 minutes ago, hsmptg said:

Hi rickwookie

Thanks for your suggestions!

Regarding the use of V4, I was a bit scared of flashing it since I read some posts reporting some bricking problems after doing that.

But since you have this opinion I thing I will try it. It is General_VTOXXX_Eng_P_16M_SIP_V4.000.0000000.5.R.20181030.zip, right?

But my initial question remains: What is the use of the other bin files besides General_VTOXXX_Eng_P_16M_SIP_V4.000.0000000.5.R.20181030.bin?

About my access to the Dahua firmware site, well I just used an username/password that I found in ipcamtalk forum.

Regards

Oh ok, yes I thought that chuest login had stopped working, but no its still does work!

General_VTOXXX_Eng_P_16M_SIP_V4.000.0000000.5.R.20181030.bin is what I'm using. The other bin files are just subsets of that main file (e.g. to only update the language if you have that same firmware in another language installed, I assume).

3 minutes ago, hsmptg said:

Hi

I tried several things to solve the missing text on the webpages, and one of those things was in fact "clearing browser cache". So I did not had any certain about what had solve the problem. But since you and @rickwookie both point that issue, it seems that is really the way to manage it.

It is curious that you are just using Asterisk from cli since that was my initial idea. I would prefer just to install Asterisk in a clean Raspbian Stretch Lite image instead of having to use a RasPBX image. But for these initial tests it seems to be easier to use RasPBX.

My idea is to build with a Raspberry Pi plus a 7" display a SIP client equivalent to a VTH1550CH to connect to my VTO2000A. That way I could have in the same equipment a Video Intercom and my home automation (home assistant) terminal.

Regards

The only downside you using this in the SIP mode as opposed to the standard VTO-to-VTH mode is that it doesn't then notify the app (iDMSS Plus) when there's a call. Unless it does and I just haven't found a way to do it yet?

6 minutes ago, riogrande75 said:

Hi!
Just installed the fw it on my test vto as well. At first, it looked like yours (empty parameter fields), but I solved it with clearing browser cache (as I was expecting it). So I did not flash the language file at all.

I suggest to read the manual, where all the parameters are described (well, at least most of 'em).

I don't know RasPBX as I youse asterisk in it's pure version (cli).

What I can say right after havin a quick look at the pics: IP and 8001 as registered number seem ok. If you press button on VTO a call to 9901 will be setup (1st pic).

I guess the problem is your SIP server. Is the ext. 8001 really configured correctly? I would deactivate auth just for testing purpous.

Also I would try to add VTO as CHAN_SIP and not PJSIP. I run all devices with chan_sip and everything is fine. In fact I did not play arround a lot with pjsip.

Additionally I would change the villa call number to fit your environment (e.g.1000/2000).

When you setup a SIP call to 8001 the vto should pick up the call automatically and you should have a audio/video connection if everything is setup correct.

If not: User asterisk debugging (sip set debug on) - that will point at the problem.

You beat me to the reply, but I would just add that I use PJSIP as it's now the default on RasPBX and everything works as I'd expect it to.

I wonder, why have they gone back to the V3,x branch if this is a newer build of firmware?! What's wrong with the "WEB SERVICE2.0" interface. I think it's much better, particularly the fact that you can see the video feed without using Internet Explorer!

@hsmptg So first of all. How do you get a login to that Dahua firmware site?!

Next: Blank web UI pages - you need to delete your browser cached data after a firmware update.

Villa Call Number: Yes this is the number dialled when you press the main call button in the VTO2000A. You will have to either create an extension or call group number in FreePBX to match this, or simply change this number to whatever you want to dial.

Local or Extense: Not entirely sure, but I think this referrers to either the in-built relay, or the "external" (is extense even a word?!) RS485 module.

Server Type: I always set mine to Asterisk for FreePBX, but actually on the most recent Firmware I have, Asterisk is not even an option, so I had to choose VTO. I don't think is matters, because perhaps it is only if you have "Server Enabled", which since we using this VTO as a SIP "CLIENT", then it's irrelevant.

As for the last username and password (and domain possibly), this is also only relevant for the device if it's acting as a SIP server, not as a client.

4 hours ago, SirUli said:

Does that work for you?

curl --user="admin:pass" http://hostname/cgi-bin/snapshot.cgi --digest -o /mnt/ramdisk/snapshot.jpg

Cheers,

Uli

Yes probably. Tbh I can also use

wget -O snapshot.jpg http://admin:password@<IP>/cgi-bin/snapshot.cgi

1 hour ago, SirUli said:

Exactly this url (i used http://admin:password/cgi-bin/snapshot.cgi) gives me a picture BUT (and that is why i don't use it) it takes ages to get the picture back and thus has a high delay. Therefore i'm using a solution like riogrande75 but with a daemon that runs continuously and writes every couple seconds the image to a ramdisk. Through that i have the "current" picture available for anything you can imagine, e.g. Telegram or Fritz!Fon

Wow. that command actually works and I get a jpeg instantly. It didn't used to work at all with the old firmware for me.

Problem is that, as with the unlock, it needs Digest HTTP Authentication, so it's difficult to do for me from a script command.

@SirUli since you're the king of the URL commands... I can get RTSP streams from the panel using:

rtsp://admin:password@cameraIP/cam/realmonitor?channel=1&subtype=0 for the main stream and

rtsp://admin:password@cameraIP/cam/realmonitor?channel=1&subtype=1 for the substream, but how can I get a still JPEG.

Thanks.

13 minutes ago, SirUli said:

Enable the internal SIP Server again, then make the room configuration and disable it again - seems to be a UI issue.

Regarding the HTTP command for unlocking:

• Primary Unlock (in the VTO2000A): http://admin:password@doorbell/cgi-bin/accessControl.cgi?action=openDoor&channel=1&UserID=101&Type=Remote
• Secondary Unlock (the DEE1010B? http://admin:password@doorbell/cgi-bin/accessControl.cgi?action=openDoor&channel=2&UserID=101&Type=Remote

Cheers,

Uli

 

Amazing!

Annoying that you have to wait for a reboot when switching modes, but hey ho.

In the Room Number Management, do I need to include the #0 after the extension/group number that I want to add (as 9901 has it listed as 9901#0)?

Btw, I didn't even know that the DEE1010B was a thing! Can you cascade them on the RS485 bus to get more than one extra channel (channel 3, 4, 5, etc.)?

Thanks once again both @jartashi and @SirUli.

32 minutes ago, jartashi said:

Just set Device type as Small apartment. (It was similar setting in old web interface called Modularized villa)  

Brilliant! Now I can unlock again!

Unfortunately, I can't seem to see where to set the number that the VTO calls once I change to "Small Appartment" mode. It will only call 9901.

Still can't find an unlock button in the web UI though. Does anyone know a cgi.bin? command that I can send to the VTO on port 80 to fire an unlock?

EDIT: I can see 9901 as the button label in the "Facade Layout", but clicking on that only pops up a blank Room List dialog. I can't add any rooms to the Room List though.

Does anyone know how to add and configure the additional modules in the new V4.x SIP firmware.

In the V3.x firmware, I could add a keypad module and set the layout to have it below the camera module. There is no layout section that I can find in V4.x.

Also, the unlock code (which I assume is the "First Unlock Command" under Local Setting->Access Control->Local) won't work from the keypad module now (entering eg #123#).

There is also no unlock button in the web interface that I can find (it used to be under the video window). Basically, how can I unlock now?!

Mine was '2016-03-21 V3' too. I dared to upgrade - so far no issues.

But mine was running fine with the old one too - so it's up to you.

 

I guess the MCU firmware is the uC's software in the devices, controlling hw like buttons,etc.

So if you have any issues that could be related to that, I would do the upgrade.

There is a pretty new MCU fw for slave devices (20180316).

 

Here a part of the .doc coming along with the fw files:

VTO2000A-B3
VTO2000A-B5
VTO2000A-B1	2.5.01.02.11739	General_VTO2000A_MCU_V3.000.0000.0.R.20180316.zip

VTO2000A, 
VTO2000A-C, 
VTO2000A-2	2.1.01.02.11605	General_VTO2000A-Master_MCU_V3.000.0000.0.R.20170515.bin

I uploaded it for you guys:http://www.share-online.biz/dl/N4NELLIPXJ

 

I have a card reader connected to the VTO2000A-C, specifically the VTO2000A-R. Do I have to update the slave firmware?

That MCU update for "slave devices" specifically only lists the separate call button (1, 3 & 5 button) modules in the accompanying notes. There's no reference to the VTO2000A-R, so I wouldn't try and use it the re-flash the MCU on your RFID reader module, even if we knew how to do it!

Mine was '2016-03-21 V3' too. I dared to upgrade - so far no issues.

But mine was running fine with the old one too - so it's up to you.

 

I guess the MCU firmware is the uC's software in the devices, controlling hw like buttons,etc.

So if you have any issues that could be related to that, I would do the upgrade.

There is a pretty new MCU fw for slave devices (20180316).

 

Here a part of the .doc coming along with the fw files:

VTO2000A-B3
VTO2000A-B5
VTO2000A-B1	2.5.01.02.11739	General_VTO2000A_MCU_V3.000.0000.0.R.20180316.zip

VTO2000A, 
VTO2000A-C, 
VTO2000A-2	2.1.01.02.11605	General_VTO2000A-Master_MCU_V3.000.0000.0.R.20170515.bin

I uploaded it for you guys:http://www.share-online.biz/dl/N4NELLIPXJ

Thanks!

Where are you getting these files from?! Is there an official source for firmware updates for the VTO line?

ConfigTool is old an outdated. Newer firmware versions require VDPconfig to work.

 

If you wanna flash MCU, pls. use latest MCU firmware "General_VTO2000A-Master_MCU_V3.000.0000.0.R.20170515.bin". Don't really know what it really does, but at least everything is up to date

Hmm...

...mine's reporting '2016-03-21 V3'

1) Where can I download the latest MCU file?

2) Should I risk updating it if we have no idea what's changed? - "If it ain't broke..."

In the firmware 4.0, there is the possibility to deactivate all audio messages and activate a "Ring, Ring, Ring..." type sound when making the call from the VTO. This at least is better than having to listen to the messages in pseudo English.

Perfect, well, good enough for me anyway. Since the internal screens can be heard ringing, from outside the front door, I don't need to replace the Chinese schoolgirl "calling now" with a "Ding Dong" sound really. I could activate the 'Ringback Sound' if needed though, which presumably I'd have some control over with the asterisk dialtone settings?

Use VDPconfig from toolbox to upgrade.

Do I have to use this instead of configtool for it to work? If so, it's asking me to choose "Main Program" or "MCU Program", which is it?

Thanks riogrande. I have seen that at least the sound messages can be deactivated.

Is that by using the new version 4.000 firmware? How do you update to that? When I try to load it using config tool, I just get the message "Failed to start upgrading".

Yes, there was a change in the upgrade process. But I do always upgrade via TFTP method, so don't ask me about it.

Nevertheless, you will not secceed in installing a customized firware anymore. Since beginning of 2018 all FW files are signed, that means it is impossible to change it - only the manufacturere (dahua) can do this.

So you got either install a older, even customized firmware via tftp or you got to live with that until dahua releases a firmware where you can replace the sounds officially via the web interface.

Good luck,

Rio

Aagh! This is big news. Where did you find that info? I've been through this whole thread and just on the point where I am trying to modify the firmware to change the less-than-desirable "Calling Now" sound, only to discover that it will be impossible!

Do you know what's the most recent SIP firmware that I can use that will allow this customisation, and where I can obtain it? Also, what features might I lose from the latest firmware by downgrading to this older version?