Dahua VTO2000A, SIP Firmware and Asterisk
Hi,
after I get some questions over PN about VTO2000A with SIP and Asterisk, I think it is usefull to make this Thread. So everyone could ask here or post solutions for problems.
I have an VTO2000A and an VTH1550CH. But I want more flexibility.
What do I wanna have at end?
If someone rings the bell of VTO, I want ringing the VTH1550CH, ringing my FritzFon (over Fritzbox) and when I'm not at home, my Android-Smartphone should ringing to. And everything with Video. Well ringing with Videostream over Fritzbox will not work because the Fritzbox doesn't support SIP Video. But there is a possibility to use Snapshots instead.
My problems so far:
- Main problem with SIP Firmware is that there will be no Push Notification on Dahua Android App gDMSS
- When I use SIP Firmware with VTH1550 I only could use VTO as SIP Server to get connection between those two. But then my FritzFon will not ring.
- When I use Asterisk as SIP Server my FritzFon are ringing but I get no Snapshot and I couldn't connect my VTH. I could insert the Dahua URL for Snapshots but this will not work with Fritzbox.
- When I use Fritzbox as SIP Server, the FritzFon are ringing but when I pick up the FritzFon the VTO will end call after a few seconds because Fritzbox sends "183 Session Progress" as Answer and the VTO only accept "180 Ringing" as answer.
Solution for connection between Fritzbox and VTO. If you wanna use Fritzbox with Telephone for ringing you have to use Asterisk as SIP Server and send an "180 Ringing" before Dial(). I will post my extensions.conf and sip.conf. My Fritzbox will give "621" as number for Doorstation and callingnumber is 9901. So I gave the VTO as No. 8001 and 9901 as Villa Call Number. On Lan-Config / Server Type is Asterisk and Network Config / SIP Server Conifg is IP of Asterisk Username "8001" password you entered on extensions.conf and Realm is "asterisk". The VTO-No. must be something like 800x. I've added pictures of settings. I think this will be much easier to understand Here my extensions.conf: [general] static=yes writeprotect=no [ausgehend] exten => _9901,1,Set(CALLERID(num)=9901) exten => _9901,n,Dial(Local/alle@tfe-zuhause,50,w) [tfe-zuhause] exten => alle,1,Ringing() exten => alle,n,Dial(SIP/9901@videodoorgateway,50,w) [default] include => ausgehend include sip.conf: [general] language=de bindport = 5060 bindaddr = 0.0.0.0 type=friend context=eingehend externrefresh=30 nat=force_rport,comedia srvlookup=yes transport=udp localnet=192.168.1.xxx/255.255.255.0 ;directmedia=no [8001] host=dynamic username=VTO2000A type=friend secret=qwertz context=ausgehend disallow=all allow=ulaw allow=h264 [videodoorgateway] context=eingehend type=friend insecure=invite nat=force_rport,comedia instead username=621 fromuser=621 fromdomain=fritz.box secret=AnyPassword host=192.168.1.xxx dtmfmode=rfc2833 disallow=all allow=ulaw ;allow=h264 I'm not very familiar with Asterisk, but with this settings connection between Fritzbox and VTO will work. What is missing is to create an URL with Snapshot when someone rings the bell. Maybe someone has solutions and will post it here so everyone could pick up what he needs to get this real good hardware work well. Because Dahua will not give support. So we have to help ourselves. If you post any solution, please write what system will work e.g. Android App or IPhone App with Asterisk (Videostream will work or not) and then what settings are needed to get it working. I'm anxious to see your solutions or questions EDIT: Here screenshots of settings in VTO: That's all
- When I use SIP Firmware with VTH1550 I only could use VTO as SIP Server to get connection between those two. But then my FritzFon will not ring.
- When I use Asterisk as SIP Server my FritzFon are ringing but I get no Snapshot and I couldn't connect my VTH. I could insert the Dahua URL for Snapshots but this will not work with Fritzbox.
- When I use Fritzbox as SIP Server, the FritzFon are ringing but when I pick up the FritzFon the VTO will end call after a few seconds because Fritzbox sends "183 Session Progress" as Answer and the VTO only accept "180 Ringing" as answer.
Solution for connection between Fritzbox and VTO. If you wanna use Fritzbox with Telephone for ringing you have to use Asterisk as SIP Server and send an "180 Ringing" before Dial(). I will post my extensions.conf and sip.conf. My Fritzbox will give "621" as number for Doorstation and callingnumber is 9901. So I gave the VTO as No. 8001 and 9901 as Villa Call Number. On Lan-Config / Server Type is Asterisk and Network Config / SIP Server Conifg is IP of Asterisk Username "8001" password you entered on extensions.conf and Realm is "asterisk". The VTO-No. must be something like 800x. I've added pictures of settings. I think this will be much easier to understand Here my extensions.conf: [general] static=yes writeprotect=no [ausgehend] exten => _9901,1,Set(CALLERID(num)=9901) exten => _9901,n,Dial(Local/alle@tfe-zuhause,50,w) [tfe-zuhause] exten => alle,1,Ringing() exten => alle,n,Dial(SIP/9901@videodoorgateway,50,w) [default] include => ausgehend include sip.conf: [general] language=de bindport = 5060 bindaddr = 0.0.0.0 type=friend context=eingehend externrefresh=30 nat=force_rport,comedia srvlookup=yes transport=udp localnet=192.168.1.xxx/255.255.255.0 ;directmedia=no [8001] host=dynamic username=VTO2000A type=friend secret=qwertz context=ausgehend disallow=all allow=ulaw allow=h264 [videodoorgateway] context=eingehend type=friend insecure=invite nat=force_rport,comedia instead username=621 fromuser=621 fromdomain=fritz.box secret=AnyPassword host=192.168.1.xxx dtmfmode=rfc2833 disallow=all allow=ulaw ;allow=h264 I'm not very familiar with Asterisk, but with this settings connection between Fritzbox and VTO will work. What is missing is to create an URL with Snapshot when someone rings the bell. Maybe someone has solutions and will post it here so everyone could pick up what he needs to get this real good hardware work well. Because Dahua will not give support. So we have to help ourselves. If you post any solution, please write what system will work e.g. Android App or IPhone App with Asterisk (Videostream will work or not) and then what settings are needed to get it working. I'm anxious to see your solutions or questions EDIT: Here screenshots of settings in VTO: That's all
Ok, here we go. These instructions are based on a Debian 8 system. But this should work on most distributions i guess, only the package installation will be different.
You must have root rights for this to work !
Install Python 3: apt install python3
Install needed tools for next steps: apt install build-essential wget unzip cramfsprogs u-boot-tools squashfs-tools
IMPORTANT: Install modified squashfs3 tools as our old VTO Linux kernel does not support squashfs4 (that is how you can easily brick your VTO)
cd wget https://github.com/BotoX/squashfs-tools/archive/v3.4.zip unzip v3.4.zip cd squashfs-tools-3.4/squashfs-tools make install
Download the firmware-mod-tools:cd wget https://github.com/BotoX/Dahua-Firmware-Mod-Kit/archive/master.zip unzip master.zip
Extract / Unpack the firmware. Be sure the extract script says "WARNING Autodetected config: VTO":cd Dahua-Firmware-Mod-Kit-master cp ~/General_VTO2000A_Eng_P_16M_SIP_V1.200.1000.0.R.20160505.bin . <------ copy your img file into this directory, this line must of course be adapted ./extract.py General_VTO2000A_Eng_P_16M_SIP_V1.200.1000.0.R.20160505.bin
Make your modifications. Sound files for example are in General_VTO2000A_Eng_P_16M_SIP_V1.200.1000.0.R.20160505.bin.extracted/data-x.cramfs.img.extracted/Sounds
Go back to Dahua-Firmware-Mod-Kit-master root folder. If you followed step by step it should be in your home directory:
cd ~/Dahua-Firmware-Mod-Kit-master
Repack the firmware. Be sure the build script says "WARNING Autodetected config: VTO":./build.py General_VTO2000A_Eng_P_16M_SIP_V1.200.1000.0.R.20160505.bin.extracted
The newly packed firmware is now in the General_VTO2000A_Eng_P_16M_SIP_V1.200.1000.0.R.20160505.bin.extracted/build subdirectory:cd General_VTO2000A_Eng_P_16M_SIP_V1.200.1000.0.R.20160505.bin.extracted/build ls -la drwxr-xr-x 2 root root 4096 Oct 17 17:59 . drwxr-xr-x 9 root root 4096 Oct 17 17:59 .. -rw-r--r-- 1 root root 12352 Oct 17 17:59 custom-x.cramfs.img -rw-r--r-- 1 root root 12288 Oct 17 17:59 custom-x.cramfs.img.raw -rw-r--r-- 1 root root 901184 Oct 17 17:59 data-x.cramfs.img -rw-r--r-- 1 root root 901120 Oct 17 17:59 data-x.cramfs.img.raw -rw-r--r-- 1 root root 255584 Oct 17 17:59 dm365_ubl_boot_16M.bin.img -rw-r--r-- 1 root root 13073267 Oct 17 17:59 General_VTO2000A_Eng_P_16M_SIP_V1.200.1000.0.R.20160505.bin <---------------- -rw-r--r-- 1 root root 467 Oct 17 17:59 Install -rw-r--r-- 1 root root 1686604 Oct 17 17:59 kernel-x.cramfs.img -rw-r--r-- 1 root root 45120 Oct 17 17:59 pd-x.cramfs.img -rw-r--r-- 1 root root 45056 Oct 17 17:59 pd-x.cramfs.img.raw -rw-r--r-- 1 root root 3117120 Oct 17 17:59 romfs-x.cramfs.img -rw-r--r-- 1 root root 3117056 Oct 17 17:59 romfs-x.cramfs.img.raw -rw-r--r-- 1 root root 5857344 Oct 17 17:59 user-x.cramfs.img -rw-r--r-- 1 root root 5857280 Oct 17 17:59 user-x.cramfs.img.raw -rw-r--r-- 1 root root 1441856 Oct 17 17:59 web-x.cramfs.img -rw-r--r-- 1 root root 1441792 Oct 17 17:59 web-x.cramfs.img.raw That's it. This should work ..... Flash it and light a candle before rebooting edit1: added mkimage edit2: added squashfs-tools edit3: added info about config file autodetection Serge
Install needed tools for next steps: apt install build-essential wget unzip cramfsprogs u-boot-tools squashfs-tools
IMPORTANT: Install modified squashfs3 tools as our old VTO Linux kernel does not support squashfs4 (that is how you can easily brick your VTO)
cd wget https://github.com/BotoX/squashfs-tools/archive/v3.4.zip unzip v3.4.zip cd squashfs-tools-3.4/squashfs-tools make install
Download the firmware-mod-tools:cd wget https://github.com/BotoX/Dahua-Firmware-Mod-Kit/archive/master.zip unzip master.zip
Extract / Unpack the firmware. Be sure the extract script says "WARNING Autodetected config: VTO":cd Dahua-Firmware-Mod-Kit-master cp ~/General_VTO2000A_Eng_P_16M_SIP_V1.200.1000.0.R.20160505.bin . <------ copy your img file into this directory, this line must of course be adapted ./extract.py General_VTO2000A_Eng_P_16M_SIP_V1.200.1000.0.R.20160505.bin
Make your modifications. Sound files for example are in General_VTO2000A_Eng_P_16M_SIP_V1.200.1000.0.R.20160505.bin.extracted/data-x.cramfs.img.extracted/Sounds
Go back to Dahua-Firmware-Mod-Kit-master root folder. If you followed step by step it should be in your home directory:
cd ~/Dahua-Firmware-Mod-Kit-master
Repack the firmware. Be sure the build script says "WARNING Autodetected config: VTO":./build.py General_VTO2000A_Eng_P_16M_SIP_V1.200.1000.0.R.20160505.bin.extracted
The newly packed firmware is now in the General_VTO2000A_Eng_P_16M_SIP_V1.200.1000.0.R.20160505.bin.extracted/build subdirectory:cd General_VTO2000A_Eng_P_16M_SIP_V1.200.1000.0.R.20160505.bin.extracted/build ls -la drwxr-xr-x 2 root root 4096 Oct 17 17:59 . drwxr-xr-x 9 root root 4096 Oct 17 17:59 .. -rw-r--r-- 1 root root 12352 Oct 17 17:59 custom-x.cramfs.img -rw-r--r-- 1 root root 12288 Oct 17 17:59 custom-x.cramfs.img.raw -rw-r--r-- 1 root root 901184 Oct 17 17:59 data-x.cramfs.img -rw-r--r-- 1 root root 901120 Oct 17 17:59 data-x.cramfs.img.raw -rw-r--r-- 1 root root 255584 Oct 17 17:59 dm365_ubl_boot_16M.bin.img -rw-r--r-- 1 root root 13073267 Oct 17 17:59 General_VTO2000A_Eng_P_16M_SIP_V1.200.1000.0.R.20160505.bin <---------------- -rw-r--r-- 1 root root 467 Oct 17 17:59 Install -rw-r--r-- 1 root root 1686604 Oct 17 17:59 kernel-x.cramfs.img -rw-r--r-- 1 root root 45120 Oct 17 17:59 pd-x.cramfs.img -rw-r--r-- 1 root root 45056 Oct 17 17:59 pd-x.cramfs.img.raw -rw-r--r-- 1 root root 3117120 Oct 17 17:59 romfs-x.cramfs.img -rw-r--r-- 1 root root 3117056 Oct 17 17:59 romfs-x.cramfs.img.raw -rw-r--r-- 1 root root 5857344 Oct 17 17:59 user-x.cramfs.img -rw-r--r-- 1 root root 5857280 Oct 17 17:59 user-x.cramfs.img.raw -rw-r--r-- 1 root root 1441856 Oct 17 17:59 web-x.cramfs.img -rw-r--r-- 1 root root 1441792 Oct 17 17:59 web-x.cramfs.img.raw That's it. This should work ..... Flash it and light a candle before rebooting edit1: added mkimage edit2: added squashfs-tools edit3: added info about config file autodetection Serge