Allodo

Well look here for SIP: If you want only to use Dahua-Components you don't need SIP-Firmware And here you can find Firmware: ftp://ftp.asm.cz/Dahua/kamerove_systemy/_Firmware/06VDP/

Maybe there: uploadfiles.io/ You mean the light of the bell sign? Typically this is always on. But I don't have a fingerprint, because of that I don't know if the light only goes on, when someone is ringing. And I don't know where you can manage it, sorry

@bassbumper Very good news for all of us How you get multilanguage and is there a limit in length for ringtones? Could you upload your firmware as example? There is now only one big problem left in firmware. If the VTO could react on "183 Session Progress" which the AVM Fritz!Box is answering over SIP when ringing, we don't need Asterisk anymore because the VTO could be working with Fritz!Box directly. But I really don't know where to find anything about it and how to change the behaviour of VTO.

Well good news " title="Applause" /> It seems that the VTH has the same behaviour as VTO on startup. The IP-Address of VTH1510 at startup is 192.168.1.108 and it's looking for an update-firmware over TFTP. Because of this, the Unbricking-Method should also work on VTH But I've not tested it I've analyzed the Sounds with Cool Edit Pro 2.1. They have an Sampling Rate of 16000 8-Bit Signed Stereo And the only channel which is OK is the right. On the left channel is only noise. But when I open it only with Mono, there is only noise. Maybe someone knows better about analyzing PCM-Sound-Files

@bassbumper I created the VTH1510.py like you did. For everyone who wanna try this, you have to insert the VTH1510 also in configs.py. In configs.py is every Hardwarescript listed. I've posted the link to the Unbricking tutorial two times, but my posts seems to be eliminated With this turorial I've unbricked my bricked VTO. The magic seems to be that the VTO at startup tries to update firmware by looking over TFTP. But you have to build an own existing network, like discribed in the turorial. Within the VTO could connect to your PC und upload the extracted firmware-packages. Magic Words in G**Gle: Dahua IPC EASY unbricking / recovery over TFTP (Use the third link) You could see this with Wireshark. Maybe the VTH has the same behaviour

@bassbumper Well I got a lot of problems with Stitch, but good to know that it will run Could you please post here the Script so anyone should use it, or is it in newer version of Dahua-Firmware-Mod-Kit included? For testing I've just copied the VTO2000A-Script an changed one line in it and unpacking works well so far. But I couldn't find any Sound-Files only *.pcm. But these Files I couldn't play. If the rebuild works well, then I wanna change these terrible Soundfiles of VTH with nice ones and Speech to German I'm just a little bit scrarry by flashing modded firmware because I've bricked my first VTO. But now there is an easy way to unbrick it and maybe the same solution will work for VTH. But therefor I have to sniff with Wireshark what happens when VTH is started.

@bassbumper Dahua has removed the Telnet-Access in newer Firmware If anything is strange after changing firmware, old settings are visible and something like that, clear your browsercache. I think that firmware of VTO and VTH are nearby the same and has the same structure. You could try to unpack the firmware the same way you do it for VTO. If this will work fine, the rebuild should also work. But I've not tested it, so if you do it, try it on your own risk. And if it works well, let us know about it Oh, by the way, if anyone should try to modify the firmware and want to use Debian. Only try it with Debian Jessie (8.xxx) not with Stitch (9.xxx)

@abyss79 You have to change the Port in your Config-Tool to 3800.

@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

@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

@unschuldsjuenger Till now you must use Asterisk if you wanna use VTO with Fritz!Fon. That's an Problem about communication between Fritzbox and the VTO. The VTO sends an INVITE to the Fritzbox. The Fritzbox answers with 183 SESSION PROGRESS, but the VTO don't know this answer. The only answer the VTO understands is 180 RINGING. Because of this the VTO Ends the Call. I've informed the Dahua-Support about this behaviour. There was no answer about it Maybe everyone with this Problem should contact Dahua-Support. So they see that a lot of People wanna use this combination and they could include it in an SIP-Firmware. If the VTO would understand 183 Session Progress, an FritzFon could be used directly. But therefor the Dahua-Support has to build it in Firmware.

@Grumpy You have to use Port 3800 in Config Tool for flashing Firmware. Interesting Link, because this is my post, but I don't know this Website. This is the Original-Post: http://www.cctvforum.com/viewtopic.php?f=6&t=51296&hilit=VTO

@ unschuldsjuenger You must reset the VTO by SSH, try another browser or empty your browsercache. The last two things sometimes works, but when you reset the VTO by SSH I had always success For Reset by SSH you have to use putty oder WinSCP under Windows. Putty is an standalone program which is only an executable File (nothing to install). Before you can use putty you have to allow Telnet on VTO. Just type this in your browser: http:///cgi-bin/configManager.cgi?action=setConfig&Telnet.Enable=true e.g. http://192.168.1.110/cgi-bin/configManager.cgi?action=setConfig&Telnet.Enable=true After that telnet-Session is enabled and you can use putty to connect to the VTO Login user: admin Password: 7ujMko0admin If your password is an other then type as password: 7ujMko0 + your password Then you type the following on console: rm -rf /mnt/mtd/* rm -rf /mnt/backup/* reboot The VTO will reboot an all settings are resetted

Well I've not tested the latest Firmware but the older Firmware from this page (which I've used) always are in English and not CZ. Maybe there is a possibilty to change to English in Settings. There are two kinds of firmware, the international one (which has no SIP). There you can choose language and the other one is with SIP and always was in English. Maybe tomorrow I will find time to test the newer Firmware

After a long time for wait I get my new VTO I've tested some achievements from here and it seems to work well. But I still get no Video on my Android App (Zoiper, Linphone or Bria) and didn't get a call on 3G, only on WiFi. These two things I'm still missing for turning my VTO to productive. Can anyone help me to solve the problems? I would like to use myfritz.net for DynDns.