VTO2000A new V4 firmware

Hi,
I have bricked my VTO2000A with SW 3.2. After all the support, which I got, I was able to unbrick it. Many thanks particularly to riogrande75 :) :cool:

Now I loaded:
- MCU (customer version only, not factory - should I load the factory version??)
- Software 4.300.0000001.0 R (main SW and language files (..., German, ...)).
to get the latest version of all FW/SW.

All flashing was confirmed by VDPConfig with green checkmark in the line of the VTO. After each flashing the VTO reboot automatically. During rebooting and before name plate LED went on, the buzzler was on for roughly 10 sec. (Why ??)
Factory reset was done in Web Server, also the 'clear config' was choosen during flashing.
Preset language is English. When I am pushing the ring button, the answer is as normal.
When I am changing to Dutch or French it is also fine.
When I am changing to German language, after roughly 1/4 sec the LED went off and VTO is going to reboot.
This happens also next time, when I am pushing the button again - the message is started, a reset is issued.
When I am changing back to Durch or English, it is working fine. When I am going back to German I have the problem again.

Do somebody has any idea, how to overcome it?

I flashed already the SW and laguage package two times; I downloaded also the files from

[FAQ] - Dahua VTO/VTH Firmware Link-Sammlung / Anleitungen

Hab mir gedacht, um die immer gleichen Fragen bzgl. aktueller FW für die VTO's und VTH's im Keim zu ersticken, mach ich mal eine Linksammlung dafür. Jeder ist gerne dazu eingeladen mitzuarbeiten, aktuellere Versionen zu posten oder mir per PM zukommen zu lassen, ich werde diese dann hier...
www.ip-phone-forum.de www.ip-phone-forum.de

two times to ensure, that the download from net w3 and the flashing was done fine (also the zip has a CRC inside, which seems to be fine).

No improvement.

Any ideas? Sorry, but I need the German language!
 
  • Like
Reactions: Roeland Lozie
So, after a long trial with a lots of try-and-error, I found the issue:

Before the update the VTO from SW 3.2 to SW 4.3, the loud speaker level was near the maximum value - why so ever it was necessary to have a loud message out of the loud speaker.
With the update to SW 4.3 it was still on this high level, also I requested to set all parameters back to factory values.
With this, the VTO makes a reset, when a meassage is going to be sent to the loud speaker.

When I reduce the loud speaker level, the VTO is not going to reset any more, when a the ring button is pushed and a message is provided via the loud speaker.
 
Other question:

I have additionally a VTO2000A-B (3 push button module). One button is necessary for a 2nd flat. If I want to use a button to call a cellphone (iDMSS+) only, with SW 3.2 I also need a VTH - even when it is installed somewhere in the basement.

Is it now possbile to forward this bell without having additional VTH and with SW 4.3? If so, how?
 
Hi.
I have some doubts about sip server.
on the router I get these things as attacks:
2019-12-23 15:32:03
Client Device Infected 192.168.1.110 212.83.164.13 SIP Asterisk PJSIP Endpoint Presence Disclosure (CVE-2018-12227).

Repeats many times and looking at the ips sometimes from China ... sometimes from the United States ... sometimes from Canada ... etc
use SIP VTO.
would it be advisable to use asterisk?
I currently have these firmwares:
VTO.....General_VTOXXX-data_EngDthFrnGerItlPorSpa_P_16M_SIP_PART_V4.300.0000001.0.R.20190322.bin
VTH.....General_VTH151X_Eng_SIP_V4.300.0000000.8.R.20190316.bin with language pack

Is it to worry me?
Is the dahua kit safe to have it connected to the internet?
 
@_lucas_ You are using latest SW, so don't worry about not havin "installed latest available".
As far as I sniffed traffic of VTO, it's connecting to google cloud services (push). These server can be everywhere.
If you do not trust cloud services in china/usa then just do not hook up your devices to the internet (as I do).

Chinese devices are not famous for their high security nor for data safety. There are lot's of known scurity vulnerabilites from Dahua. Off course I do not let anyone control access to my house.
I just get a push notification with a snapshot from the visitor via a safer source - this is sufficient.
 
  • Like
Reactions: IT-man and _lucas_
That interests me.
Buy these equipment to see who rings and answer from the phone ..... if I disconnect from the internet is a simple video intercom.
let's see if I can install my own asterisk on raspberry pi and improve security
 
Good Morning,

i am new to all this and wanted to ask, if there is a way to update to a newer firmware.
My Setup is the following:

VTOA2000 (2-wire) wir Fingerprint Accessmodul
VTH1550CHW (2-wire)

My Firmware at the moment is 3.200. I find all kinds of newer Firmware Versions, but they all say SIP. I don't know anything about SIP.
Can i use this Version too, or is their a newer Firmware for my Setup without the SIP?

Thanks in advance for your help.

Greetings Steve
 
Hi

On January 2019, I successful attempt to update my VTO2000A firmware to version 4.000.0000000.5.R.20181030.
Today I noticed that a new version was available (4.300.0000000.1.R.20190305) and tried to update the firmware again.
As you can see I can access the VTO2000A using a browser at IP 10.0.5.245:

Chrome.png

But no matter the version of ConfigTool I use, I never reach the Upgrade button to start the process.
For instance, version 5.000.0000000.2 do not find any device:

ConfigTool_v5.000.0000000.2.png

Version 5.000.0000000.0 finds the VTO2000A in the "Modify IP" tab...

ConfigTool_v5.000.0000000.0_Modify_IP.png

... but in the "Upgrade" tab the device do not appear besides being found:

ConfigTool_v5.000.0000000.0_Upgrade.png

Even using older versions like the 4.09.0, my device is not detected:

ConfigTool_v4.09.0.png

The only one that allowed me to reach the upgrade stage was version 3.20.0 but only if I specify the IP:

ConfigTool_v3.20.0.png

But unfortunately after choosing the desired firmware bin file the process gives me an error:

ConfigTool_v3.20.0_Upgrade_Error.png

I read that the new Windows 10 can have so problems detecting the devices, so I repeated these tests in a Windows 7 machine with the same results!

So, what is going on???
Why I can not upgrade my current firmware?

Any suggestion is welcome!
Many thanks.
 
hsmptg said:
Hi

On January 2019, I successful attempt to update my VTO2000A firmware to version 4.000.0000000.5.R.20181030.
Today I noticed that a new version was available (4.300.0000000.1.R.20190305) and tried to update the firmware again.
As you can see I can access the VTO2000A using a browser at IP 10.0.5.245:

View attachment 70329

But no matter the version of ConfigTool I use, I never reach the Upgrade button to start the process.
For instance, version 5.000.0000000.2 do not find any device:

View attachment 70330

Version 5.000.0000000.0 finds the VTO2000A in the "Modify IP" tab...

View attachment 70331

... but in the "Upgrade" tab the device do not appear besides being found:

View attachment 70332

Even using older versions like the 4.09.0, my device is not detected:

View attachment 70333

The only one that allowed me to reach the upgrade stage was version 3.20.0 but only if I specify the IP:

View attachment 70334

But unfortunately after choosing the desired firmware bin file the process gives me an error:

View attachment 70335

I read that the new Windows 10 can have so problems detecting the devices, so I repeated these tests in a Windows 7 machine with the same results!

So, what is going on???
Why I can not upgrade my current firmware?

Any suggestion is welcome!
Many thanks.
Click to expand...

So couple of things. When you search in the "new" ConfigTool: did you enter your admin credentials in the "search settings" window? If not, that is the first thing to do.
Secondly, in your "old" ConfigTool screen, you connect to port 255, change that to port 3800.
 
  • Like
Reactions: hsmptg
catcamstar said:
So couple of things. When you search in the "new" ConfigTool: did you enter your admin credentials in the "search settings" window? If not, that is the first thing to do.
Secondly, in your "old" ConfigTool screen, you connect to port 255, change that to port 3800.
Click to expand...

Hi
Many thanks for the suggestions but...

... in the "new" ConfigTool I used the admin credentials, that is, the same ones that I am using in the Web Service 2.0, right?

1599823438479.png

Note that the ConfigTool says that it found 1 Device, but that device (my VTO2000A) is only listed in the "Modify IP" tab, not in the "Upgrade" tab!?!

1599823697882.png

... in the "old" ConfigTool, I believe that the 255 you mentioned in the "IP number" is not the port but the number of addresses that it will used from the Start IP. Besides if I try to input the value 3800, it changes to 1000 (probably the maximum span allowed).

But when I was trying in this "old" ConfigTool to upgrade once again... it worked!!!
What changed?
Well this time I insured the the tamper button in the back of my VTO2000A was really pressed!!!

1599825613225.png

After that I tried to access the Web Service without success... PANIC!!!
Then I realised that the Web Service of this 4.300.0000000.1.R.20190305 version can not be accessed using Chrome (like the v4.0) and I must use IExplorer instead!

1599825806197.png

Many thanks once again!!!
 
You must log in or register to reply here.
Top Bottom