Dahua VTO2000A, SIP Firmware and Asterisk

[JM170 0]

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".

 

Hello, i have downloaded version 4.0, according to the indications of RioGrande75, and I have updated using the VDPconfig application that comes within the ToolBox package of the Dahua tools. VDPconfig is simple, you just have to automatically search for the devices that are connected to the network, specifying the user and administration password, and then, once you have found it and it is initialized, you can access "Upgrade" and select the firmware file 4.0, finally click on "Upgrade", and that's it.

[JM170 0]

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?

 

I have used "Main Program"

[JM170 0]

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.

[rickwookie 0]

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?

 

 

[riogrande75 3]

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

[rickwookie 0]

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..."

[riogrande75 3]

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

[JM170 0]

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?

[JM170 0]

By the way, with the old SIP firmware, you could not read RFID cards with the VTO2000A-R module, now with the new SIP, yes i can !!!

[riogrande75 3]

In fact, I know how to update the MCU firmware of the main module (.bin file -> VDPconfig -> MCU Program) but I have no clue how to install the .hex files on slave devices.

I expect that cannot be done via IP, you need kind of a special serial programmer. But that's just my idea.

[JM170 0]

Hello, do you know what the "Active Reg." Option is for? within the "Network Setting" tab?

 

You have 3 options:

 

IP Address: ________

Port: __________

Device ID: ___________

[rickwookie 0]

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?

[rickwookie 0]

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!

[riogrande75 3]

@JM170: I did not yet try it by myself, but I guess it will show registered SIP devices when VTO acts as the SIP server.

 

@rickwookie: In fact "googeling". And yes, you are absolutely right regarding MCU update for slave devices.

[thka 0]

Just got my fingerprint sensor (VTO2000A-F) and playing with it.

 

What I noticed first: When someone opens the door with his finger, a TCP session from VTO to the server (in my case a SIP server, maybe VTHxxxx with dahua proprietary firmware) at port 5000 gets established and something like this gets submitted:

DHIP¨{"id":1122334455,"method":"global.login","params":{"clientType":"GUI","ipAddr":"192.168.123.123","password":"*******","userName":"8801"},"session":0}

So this can be used as a trigger to let a script query the API's "recordFinder.cgi" function. I tried it, works fine.

 

how did you configure the VTO? i don't get anything transmitted

[riogrande75 3]

Do you run a SIP firmware?

In fact I configured nothing else than the SIP server and the FTP server for the snapshot uploads (same IP). With sniffing I figured out, that there is a TCP session setup on port 5000.

Then I let a TCP server run on port 5000 and noticed the message.

I am pretty sure, it is addressed for SmartPSS (dahua windows sw), but so far I don't know where to set the a specific IP for it.

[thka 0]

thanks, on the SIP server I can now receive data

now i have to check how i can redirect port 5000 to my server

as sip server i use Asterisk on a Raspberry pi

[riogrande75 3]

Where do u want to redirect it to? Do you run a machine with SmartPSS?

[thka 0]

no, on a Windows Server 2008R2 with Home Automation Software IP-Symcon

https://www.symcon.de

[JM170 0]

Do you run a SIP firmware?

In fact I configured nothing else than the SIP server and the FTP server for the snapshot uploads (same IP). With sniffing I figured out, that there is a TCP session setup on port 5000.

Then I let a TCP server run on port 5000 and noticed the message.

I am pretty sure, it is addressed for SmartPSS (dahua windows sw), but so far I don't know where to set the a specific IP for it.

 

I've tried it with SmartPSS and it does not work.

[riogrande75 3]

Did not yet try it by myself. All I noticed is, that when I start SmartPSS on a windows machine, tcp port 5000 opens. So I expected it would be exactly the counterpart for the VTO.

[jamat65 0]

Hi everybody,

 

I'm trying to use VTO2000 as SIP Server but I'm not lucky.

 

I'm using the last version of the firmware, General_VTOXXX_Eng_P_16M_SIP_V4.000.0000000.1.R.20180606

 

I can connect sip clients (android apps) and make a call between them (I can see in status household settings page)

 

But VTO2000 client is not running (I can NOT see in status household settings page)

 

Is someone using vto as sip server? Any idea?

 

Thanks in advance

[riogrande75 3]

Hi!

I highly recommend not to use any non-dahua sip clients with the VTO's sip server.

I am not even sure if dahua devices run stable with it. Pls. use asterisk or any other supported sip server.

BTW: just found a newer v4 sip firmware: General_VTOXXX_Eng_P_16M_SIP_V4.000.0000000.5.R.20181030.zip

[jamat65 0]

OK, thanks. I'll try it.

 

Where can I get this new version? Do you know the advantages of this new version?

[JM170 0]

Hi!

I highly recommend not to use any non-dahua sip clients with the VTO's sip server.

I am not even sure if dahua devices run stable with it. Pls. use asterisk or any other supported sip server.

BTW: just found a newer v4 sip firmware: General_VTOXXX_Eng_P_16M_SIP_V4.000.0000000.5.R.20181030.zip

 

Where have you located this new version?

could you pass the download link, please?