View unanswered posts | View active topics


Reply to topic  [ 90 posts ]  Go to page Previous  1, 2, 3, 4, 5, 6
Author Message
  
 Post subject: Re: Dahua VTO2000A, SIP Firmware and Asterisk
PostPosted: Thu Jan 12, 2017 11:51 am 
Registered User

Joined: Jan 2017
Posts: 3

Offline
@Allodo

Good to know. Obviously people took up your advice ;)

And yes I tried to set port 3800 but it was only settable in VTO and not in ConfigTool.
It looks as if ConfigTool 4.00.0 doesn't support that anymore.
After searching and using ConfigTool 3.20.0 it works fine.

And as several times stated: make sure to clear cache of your browser to avoid incomplete configuration view in VTO.

Thanks and cheers


Top
 Profile  
Reply with quote  

  
 Post subject: Re: Dahua VTO2000A, SIP Firmware and Asterisk
PostPosted: Thu Jan 12, 2017 4:16 pm 
Registered User

Joined: Jan 2017
Posts: 3

Offline
[quote="Allodo"]@Grumpy
You have to use Port 3800 in Config Tool for flashing Firmware.

Do you have to set the port 3800 in the conf GUI? of do you set it in the config tool?
because when i change it to 3800 in the gui, after the nessecary reboot it's back to 37777


Top
 Profile  
Reply with quote  

  
 Post subject: Re: Dahua VTO2000A, SIP Firmware and Asterisk
PostPosted: Fri Jan 13, 2017 2:49 am 
Registered User

Joined: Jun 2016
Posts: 19

Offline
@fabjan
You have to set Port 3800 in Config Tool. Better use an older Version of Config Tool.
After that you can Flash every Version of Firmware for VTO2000A you want ;)


We should annoy the Dahua support so long until they finally supplement the Firmware ;)

So erveryone who read this should contact Dahua Support and should ask them, if they could insert right behaviour when 183 Session Progress comes as answer. Many other door stations support both formats. In the web interface, you can even partially set the door station to respond to. Hardware is so nice from Dahua but Firmware is [-X


Top
 Profile  
Reply with quote  

  
 Post subject: Re: Dahua VTO2000A, SIP Firmware and Asterisk
PostPosted: Sat Jan 14, 2017 9:58 am 
Registered User

Joined: Jan 2017
Posts: 3

Offline
Finally I got the VTO2000a working with Raspberry as SIP-server (asterisk) and Linphone as SIP-Client on an android smart phone.
With some helpfull input from this forum.
Thanks to all spending time on searching for solutions and sharing them with others.

One thing I couldn´t figure out so far:
The video stream on smartphone (SIP-client) is not visible before answering the call.
I would like to see who is at the door before I pick the call.

Does SIP support video preview at all ?

If not I would like to try another approach.
Found this command which should allow to stream video signal from VTO:
rtsp://admin:admin@192.168.1.110

Doesn`t work with any browser.
Using VLC-Media-Player shows the video but with terrible delay of about 4 seconds.

Since the video stream in the ConfigTool runs with acceptable delay I guess there is a way to stream the video signal properly.
Just don´t know how.

Any ideas or advice ?


Top
 Profile  
Reply with quote  

  
 Post subject: Re: Dahua VTO2000A, SIP Firmware and Asterisk
PostPosted: Mon Jan 30, 2017 2:13 pm 
Registered User

Joined: Jan 2017
Posts: 3

Offline
Does anybody know what happens on the LAN when you push the call button on the vto?
(not the sip version), the screen reacts, and all the smartphones get a push notification.. but i would like to listen for that push notification so i can play a ding dong sound on my raspi (who is connected to all the speakers in and around the house)


Top
 Profile  
Reply with quote  

  
 Post subject: Re: Dahua VTO2000A, SIP Firmware and Asterisk
PostPosted: Mon Feb 20, 2017 8:46 am 
Registered User

Joined: Feb 2017
Posts: 2

Offline
I have a problem and I need help
I bought on Aliexpress set of VTO2000A + VHT1550CH and I found on website
ftp://ftp.asm.cz/Dahua/kamerove_systemy/_Firmware/06VDP/Multi-baseline_firmware/
right firmware with polish language.
VTO2000A it has upgraded successfully but VHT155CH after the upgrade didn’t react to the touchpad, the screen is still black.
I analyzed processor’s board and I think I found port RS485 like in the pictures.

I connected it with computer via RS485 converter. On first sight it seems to be OK but the link works only one-way. It reads correctly but the processor doesn’t see any of sent asci codes by my computer. These are information read by link :
[list=]Checking DDR......OK
UBL Version: 1.46t(DM365)09:30:17 Sep 2 2014
Oscillator: 24MHZ
ARM Rate: 432 MHZ
DDR Rate: 340 MHZ
BootMode: SPI
Starting SPI Memory Copy...
DONE
U-Boot 1.3.6 (jerry) (Sep 2 2014 - 09:44:01)
DRAM: 128 MB
SF: Got idcode c2 20 18 c2 20
In: serial
Out: serial
Err: serial
Ethernet PHY: GENERIC @ 0x05,id:221513
total gio 2
gio[22]=1
gio[25]=1
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending throu gh gateway 192.168.1.1
Filename 'upgrade_info_7db780a713a4.txt'.
Load address: 0x80100000
Loading: *
Retry count exceeded; starting again
Fail to get info file!
Init error!
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending throu gh gateway 192.168.1.1
Filename 'failed.txt'.
Load address: 0x80200000
Loading: *
Retry count exceeded; starting again
==>use default images
.......
## Booting kernel from Legacy Image at 80007fc0 ...
Image Name: Linux-2.6.18_pro500-davinci_evm-
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1686440 Bytes = 1.6 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
XIP Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux............................................................. ..................................................... done, booting the kernel.
Checking DDR......OK
UBL Version: 1.46t(DM365)09:30:17 Sep 2 2014
Oscillator: 24MHZ
ARM Rate: 432 MHZ
DDR Rate: 340 MHZ
BootMode: SPI
Starting SPI Memory Copy...
DONE
U-Boot 1.3.6 (jerry) (Sep 2 2014 - 09:44:01)
DRAM: 128 MB
SF: Got idcode c2 20 18 c2 20
In: serial
Out: serial
Err: serial
Ethernet PHY: GENERIC @ 0x05,id:221513
total gio 2
gio[22]=1
gio[25]=1
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending throu gh gateway 192.168.1.1
Filename 'upgrade_info_7db780a713a4.txt'.
Load address: 0x80100000
Loading: *
Retry count exceeded; starting again
Fail to get info file!
Init error!
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending throu gh gateway 192.168.1.1
Filename 'failed.txt'.
Load address: 0x80200000
Loading: *
Retry count exceeded; starting again
==>use default images
......
## Booting kernel from Legacy Image at 80007fc0 ...
Image Name: Linux-2.6.18_pro500-davinci_evm-
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1686440 Bytes = 1.6 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
XIP Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux............................................................. ..................................................... done, booting the kernel.
Checking DDR......OK
UBL Version: 1.46t(DM365)09:30:17 Sep 2 2014
Oscillator: 24MHZ
ARM Rate: 432 MHZ
DDR Rate: 340 MHZ
BootMode: SPI
Starting SPI Memory Copy...
DONE
U-Boot 1.3.6 (jerry) (Sep 2 2014 - 09:44:01)
DRAM: 128 MB
SF: Got idcode c2 20 18 c2 20
In: serial
Out: serial
Err: serial
Ethernet PHY: GENERIC @ 0x05,id:221513
total gio 2
gio[22]=1
gio[25]=1
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending throu gh gateway 192.168.1.1
Filename 'upgrade_info_7db780a713a4.txt'.
Load address: 0x80100000
Loading: *
Retry count exceeded; starting again
Fail to get info file!
Init error!
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending throu gh gateway 192.168.1.1
Filename 'failed.txt'.
Load address: 0x80200000
Loading: *
Retry count exceeded; starting again
==>use default images
.......
## Booting kernel from Legacy Image at 80007fc0 ...
Image Name: Linux-2.6.18_pro500-davinci_evm-
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1686440 Bytes = 1.6 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
XIP Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux............................................................. ..................................................... done, booting the kernel.
Checking DDR......OK
UBL Version: 1.46t(DM365)09:30:17 Sep 2 2014
Oscillator: 24MHZ
ARM Rate: 432 MHZ
DDR Rate: 340 MHZ
BootMode: SPI
Starting SPI Memory Copy...
DONE
U-Boot 1.3.6 (jerry) (Sep 2 2014 - 09:44:01)
DRAM: 128 MB
SF: Got idcode c2 20 18 c2 20
In: serial
Out: serial
Err: serial
Ethernet PHY: GENERIC @ 0x05,id:221513
total gio 2
gio[22]=1
gio[25]=1
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending throu gh gateway 192.168.1.1
Filename 'upgrade_info_7db780a713a4.txt'.
Load address: 0x80100000
Loading: *
Retry count exceeded; starting again
Fail to get info file!
Init error!
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending throu gh gateway 192.168.1.1
Filename 'failed.txt'.
Load address: 0x80200000
Loading: *
Retry count exceeded; starting again
==>use default images
.......
## Booting kernel from Legacy Image at 80007fc0 ...
Image Name: Linux-2.6.18_pro500-davinci_evm-
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1686440 Bytes = 1.6 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
XIP Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux............................................................. ..................................................... done, booting the kernel.
Checking DDR......OK
UBL Version: 1.46t(DM365)09:30:17 Sep 2 2014
Oscillator: 24MHZ
ARM Rate: 432 MHZ
DDR Rate: 340 MHZ
BootMode: SPI
Starting SPI Memory Copy...
DONE
U-Boot 1.3.6 (jerry) (Sep 2 2014 - 09:44:01)
DRAM: 128 MB
SF: Got idcode c2 20 18 c2 20
In: serial
Out: serial
Err: serial
Ethernet PHY: GENERIC @ 0x05,id:221513
total gio 2
gio[22]=1
gio[25]=1
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending throu gh gateway 192.168.1.1
Filename 'upgrade_info_7db780a713a4.txt'.
Load address: 0x80100000
Loading: *
Retry count exceeded; starting again
Fail to get info file!
Init error!
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending throu gh gateway 192.168.1.1
Filename 'failed.txt'.
Load address: 0x80200000
Loading: *
Retry count exceeded; starting again
==>use default images
.......
## Booting kernel from Legacy Image at 80007fc0 ...
Image Name: Linux-2.6.18_pro500-davinci_evm-
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1686440 Bytes = 1.6 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
XIP Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux............................................................. ..................................................... done, booting the kernel.
# yyyyyy@@@@@yy%E%E%%%%%%%%%%%%%%&&&
Checking DDR......OK
UBL Version: 1.46t(DM365)09:30:17 Sep 2 2014
Oscillator: 24MHZ
ARM Rate: 432 MHZ
DDR Rate: 340 MHZ
BootMode: SPI
Starting SPI Memory Copy...
DONE
U-Boot 1.3.6 (jerry) (Sep 2 2014 - 09:44:01)
DRAM: 128 MB
SF: Got idcode c2 20 18 c2 20
In: serial
Out: serial
Err: serial
Ethernet PHY: GENERIC @ 0x05,id:221513
total gio 2
gio[22]=1
gio[25]=1
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending throu gh gateway 192.168.1.1
Filename 'upgrade_info_7db780a713a4.txt'.
Load address: 0x80100000
Loading: *
Retry count exceeded; starting again
Fail to get info file!
Init error!
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending throu gh gateway 192.168.1.1
Filename 'failed.txt'.
Load address: 0x80200000
Loading: *
Retry count exceeded; starting again
==>use default images
.......
## Booting kernel from Legacy Image at 80007fc0 ...
Image Name: Linux-2.6.18_pro500-davinci_evm-
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1686440 Bytes = 1.6 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
XIP Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux............................................................. ..................................................... done, booting the kernel.
Checking DDR......OK
UBL Version: 1.46t(DM365)09:30:17 Sep 2 2014
Oscillator: 24MHZ
ARM Rate: 432 MHZ
DDR Rate: 340 MHZ
BootMode: SPI
Starting SPI Memory Copy...
DONE
U-Boot 1.3.6 (jerry) (Sep 2 2014 - 09:44:01)
DRAM: 128 MB
SF: Got idcode c2 20 18 c2 20
In: serial
Out: serial
Err: serial
Ethernet PHY: GENERIC @ 0x05,id:221513
total gio 2
gio[22]=1
gio[25]=1
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending throu gh gateway 192.168.1.1
Filename 'upgrade_info_7db780a713a4.txt'.
Load address: 0x80100000
Loading: *
Retry count exceeded; starting again
Fail to get info file!
Init error!
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending throu gh gateway 192.168.1.1
Filename 'failed.txt'.
Load address: 0x80200000
Loading: *
Retry count exceeded; starting again
==>use default images
......
## Booting kernel from Legacy Image at 80007fc0 ...
Image Name: Linux-2.6.18_pro500-davinci_evm-
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1686440 Bytes = 1.6 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
XIP Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux............................................................. ..................................................... done, booting the kernel.
Checking DDR......OK
UBL Version: 1.46t(DM365)09:30:17 Sep 2 2014
Oscillator: 24MHZ
ARM Rate: 432 MHZ
DDR Rate: 340 MHZ
BootMode: SPI
Starting SPI Memory Copy...
DONE
U-Boot 1.3.6 (jerry) (Sep 2 2014 - 09:44:01)
DRAM: 128 MB
SF: Got idcode c2 20 18 c2 20
In: serial
Out: serial
Err: serial
Ethernet PHY: GENERIC @ 0x05,id:221513
total gio 2
gio[22]=1
gio[25]=1
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending throu gh gateway 192.168.1.1
Filename 'upgrade_info_7db780a713a4.txt'.
Load address: 0x80100000
Loading: *
Retry count exceeded; starting again
Fail to get info file!
Init error!
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending throu gh gateway 192.168.1.1
Filename 'failed.txt'.
Load address: 0x80200000
Loading: *
Retry count exceeded; starting again
==>use default images
......
## Booting kernel from Legacy Image at 80007fc0 ...
Image Name: Linux-2.6.18_pro500-davinci_evm-
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1686440 Bytes = 1.6 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
XIP Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux............................................................. ..................................................... done, booting the kernel.
Checking DDR......OK
UBL Version: 1.46t(DM365)09:30:17 Sep 2 2014
Oscillator: 24MHZ
ARM Rate: 432 MHZ
DDR Rate: 340 MHZ
BootMode: SPI
Starting SPI Memory Copy...
DONE
U-Boot 1.3.6 (jerry) (Sep 2 2014 - 09:44:01)
DRAM: 128 MB
SF: Got idcode c2 20 18 c2 20
In: serial
Out: serial
Err: serial
Ethernet PHY: GENERIC @ 0x05,id:221513
total gio 2
gio[22]=1
gio[25]=1
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending throu gh gateway 192.168.1.1
Filename 'upgrade_info_7db780a713a4.txt'.
Load address: 0x80100000
Loading: *
Retry count exceeded; starting again
Fail to get info file!
Init error!
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending throu gh gateway 192.168.1.1
Filename 'failed.txt'.
Load address: 0x80200000
Loading: *
Retry count exceeded; starting again
==>use default images
.......
## Booting kernel from Legacy Image at 80007fc0 ...
Image Name: Linux-2.6.18_pro500-davinci_evm-
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1686440 Bytes = 1.6 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
XIP Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux............................................................. ..................................................... done, booting the kernel.
Checking DDR......OK
UBL Version: 1.46t(DM365)09:30:17 Sep 2 2014
Oscillator: 24MHZ
ARM Rate: 432 MHZ
DDR Rate: 340 MHZ
BootMode: SPI
Starting SPI Memory Copy...
DONE
U-Boot 1.3.6 (jerry) (Sep 2 2014 - 09:44:01)
DRAM: 128 MB
SF: Got idcode c2 20 18 c2 20
In: serial
Out: serial
Err: serial
Ethernet PHY: GENERIC @ 0x05,id:221513
total gio 2
gio[22]=1
gio[25]=1
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending throu gh gateway 192.168.1.1
Filename 'upgrade_info_7db780a713a4.txt'.
Load address: 0x80100000
Loading: *
Retry count exceeded; starting again
Fail to get info file!
Init error!
TFTP from server 192.168.254.254; our IP address is 192.168.1.108; sending throu gh gateway 192.168.1.1
Filename 'failed.txt'.
Load address: 0x80200000
Loading: *
Retry count exceeded; starting again
==>use default images
.......
## Booting kernel from Legacy Image at 80007fc0 ...
Image Name: Linux-2.6.18_pro500-davinci_evm-
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1686440 Bytes = 1.6 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
XIP Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux............................................................. ..................................................... done, booting the kernel.
#
[/list]

By the test I found button on my keyboard, thanks to which I wrote ‘***’. It stopped the process ‘boot’. Next sending information from the keyboard caused converter’s damage. It stopped broadcasting.
Is it possible that is USB port or I2C, not RS485 ?
I also tried to connect by TFTP but I don’t know the procedure how I can send file update.img.
Does someone know the way how to load the software from scratch to my VHT1550CH? Thanks for advice. Jacek


You do not have the required permissions to view the files attached to this post. Please sign-in or register to view or download.


Top
 Profile  
Reply with quote  

  
 Post subject: Re: Dahua VTO2000A, SIP Firmware and Asterisk
PostPosted: Mon Feb 20, 2017 7:26 pm 
Registered User

Joined: Feb 2017
Posts: 6

Offline
I worked through most of the relevant info that has been posted here, (thanks, all) and will just add a few comments.
First, the POE is Dahua passive config, not regular IEEE 802.3af poe, so I used a 12v psu instead.

Flashed with the SIP firmware and set up as SIP client to use with an existing asterisk/ freepbx system. Got it working OK once the confusing menu was deciphered.

Initially, the VTO2000 was flooding my LAN with multicast packets, I guess that how it works with its own indoor units, but that screwed up my network. Disabled that with:
Code:
http://192.168.N.N/cgi-bin/configManager.cgi?action=setConfig&Multicast.TS[0].Enable=false


Nothing much to say about the video except that there isn't much choice with the parameters on either stream.

I wanted to use this with my asterisk pbx and that's where I was a bit disappointed. The silly announcements are only heard on the doorphone, and the other end has no call progress info. I may replace the announcements with tones, (like a normal phone!) which removes the need for language files.

Usually with doorphones, the call ends if the Door Open digits are entered, with audible feedback, but not here. The relay silently energizes and the call continues until a hard timeout (called Shout Time by Dahua) or until caller hangup.

By ending the Door Open digits with a hash, eg 123#, the relay will operate immediately btw.

So overall as a standalone doorphone its performance is only so-so, but it does the job at a fraction of the price of other units like this one:
https://www.axis.com/ng/en/products/axis-a8004-ve

Now, if only the firmware could be improved.....


Top
 Profile  
Reply with quote  

  
 Post subject: Re: Dahua VTO2000A, SIP Firmware and Asterisk
PostPosted: Fri Feb 24, 2017 8:21 am 
Registered User

Joined: Feb 2017
Posts: 6

Offline
A disadvantage I see with the Dahua http cgi implementation is that every command needs authentication, for example operating the door lock relay via, say a web browser is a 2-stage process requiring a username and password before execution.

Same would go for displaying the door sensor state. This seems pretty standard for all Dahua cameras, and it means that i/o is not easily accessible for use in third-party apps, for example in Home Automation.

If anyone can tell me differently, I would be glad to know how...


Top
 Profile  
Reply with quote  

  
 Post subject: Re: Dahua VTO2000A, SIP Firmware and Asterisk
PostPosted: Wed Mar 01, 2017 12:38 pm 
Registered User

Joined: Jan 2016
Posts: 5

Offline
Did anyone figure out how to detect when someone rings the VTO2000a doorbell using non-SIP firmware ?

It is possible using the http://ip/cgi-bin/VideoTalkPeer.cgi?action=attachState or action=attach commands for example ?


Top
 Profile  
Reply with quote  

  
 Post subject: Re: Dahua VTO2000A, SIP Firmware and Asterisk
PostPosted: Mon Mar 06, 2017 7:57 am 
Registered User

Joined: Jan 2017
Posts: 3

Offline
anyone figure out yet how to detect the vto doorbell button has been pressed? (using non-sip firmware)
I don't think the VideoTalkPeer.cgi can be used for that purpose.


Top
 Profile  
Reply with quote  

  
 Post subject: Re: Dahua VTO2000A, SIP Firmware and Asterisk
PostPosted: Mon Mar 06, 2017 11:32 am 
Registered User

Joined: Jun 2016
Posts: 19

Offline
@kasperskie
Well you can try to sniff your network with an tool called Wireshark.
Maybe you can see any pull and request from VTO.

I think thats the only way to see what the VTO is doing when the doorbell is ringing. Maybe there are other/better tools for sniffing network.

If you find out something interesting it would be nice if you can inform us all about it :)


Top
 Profile  
Reply with quote  

  
 Post subject: Re: Dahua VTO2000A, SIP Firmware and Asterisk
PostPosted: Thu Mar 16, 2017 5:37 pm 
Registered User

Joined: Feb 2017
Posts: 2

Offline
I have a problem and I need help
I bought on Aliexpress set of VTO2000A + VHT1550CH and I found on website
ftp://ftp.asm.cz/Dahua/kamerove_systemy/_Firmware/06VDP/Multi-baseline_firmware/
right firmware with polish language.
VTO2000A it has upgraded successfully but VHT155CH after the upgrade didn’t react to the touchpad, the screen is still black.
I analyzed processor’s board and I think I found port RS485 like in the pictures.

I connected it with computer via RS485 converter. On first sight it seems to be OK but the link works only one-way. It reads correctly but the processor doesn’t see any of sent asci codes by my computer. These are information read by link :


By the test I found button on my keyboard, thanks to which I wrote ‘***’. It stopped the process ‘boot’. Next sending information from the keyboard caused converter’s damage. It stopped broadcasting.
Is it possible that is USB port or I2C, not RS485 ?
I also tried to connect by TFTP but I don’t know the procedure how I can send file update.img.
Does someone know the way how to load the software from scratch to my VHT1550CH? Thanks for advice. Jacek


Top
 Profile  
Reply with quote  

  
 Post subject: Re: Dahua VTO2000A, SIP Firmware and Asterisk
PostPosted: Sat Mar 18, 2017 1:38 pm 
Registered User

Joined: Feb 2017
Posts: 6

Offline
Set up a debian machine in Virtualbox, and followed the instructions provided by Foxi352 to unpack-modify-repack the firmware to change the sounds. Only about 7 of the 30-odd sounds needed changing for doorphone use, so I generated tone files using Cool Edit at the same SR as the originals, and flashed the unit with the modified firmware..

Seemed to work OK but the unit was in a reboot loop cycling every 90 secs or so. Tried reflashing various firmwares, including the Czech version, they all worked, but the unit kept boot cycling. Initially suspected the extracted build file as it referenced two nonexistent image files:
Code:
Upgrade : Complete Total 98%... UPGRADED_ERR: LINE: 1074: invalid file: gui-x.cramfs.img
UPGRADED_MSG: extract gui-x.cramfs.img failed, skip...
UPGRADED_ERR: LINE: 1074: invalid file: pcm-x.cramfs.img
UPGRADED_MSG: extract pcm-x.cramfs.img failed, skip...
[libdvr] idestatus =0
Upgrade : Complete Total 100%...        UPGRADED_MSG: will reboot system
[libdvr] sync....

Removed these references from the install file, but that wasn't the problem.....
I had forgotten to do a full reset via telnet. #-o

After doing that, everything worked fine. So Foxi352s instructions worked perfectly, but its important to do the complete reset after flashing.


You do not have the required permissions to view the files attached to this post. Please sign-in or register to view or download.


Top
 Profile  
Reply with quote  

  
 Post subject: Re: Dahua VTO2000A, SIP Firmware and Asterisk
PostPosted: Tue May 09, 2017 12:51 pm 
Registered User

Joined: May 2017
Posts: 1

Offline
Hi!

I've been trying to get it to work for the past couple of hours.

I've installed the SIP firmware

I've setup the NetworkConfig->SIP Server config

I've setup the extension to call when the button is pressed under Local Config->A&C Manager



But the darn VTO2000A won't even register on my Freepbx (Asterisk) server, I don't even see it in the logs anywhere on the server.

Wireshard did however see a registration request.



Anyone had the same problem?


Thanks :)


Top
 Profile  
Reply with quote  

  
 Post subject: Re: Dahua VTO2000A, SIP Firmware and Asterisk
PostPosted: Sun May 21, 2017 1:56 pm 
Registered User

Joined: May 2017
Posts: 1

Offline
Note that CURL requires '' in part of the command, in addition, see example below:
curl --user admin:admin --digest http://192.168.1.108/cgi-bin/ptz.cgi?'action=start&channel=4&code=GotoPreset&arg1=0&arg2=1&arg3=0'


Top
 Profile  
Reply with quote  

Display posts from previous:  Sort by  
Reply to topic  [ 90 posts ]  Go to page Previous  1, 2, 3, 4, 5, 6


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  

It is currently Tue Jun 27, 2017 12:27 pm

The contents of this webpage are copyright © 2003-2016 CCTVForum.com. All Rights Reserved.