Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


riogrande75 last won the day on February 14

riogrande75 had the most liked content!

Community Reputation

2 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Ok. Did not find this very old one, but why not tryin another 3.1 FW "General_Multi3_VTH1510_EngRusItlFreGerDutSpaPor_P_V3.100.0000.0.R.20170401", which is just slightly newer and easy to find?
  2. Whatfor do you need such an old firmware?
  3. If you have ever set up any SIP device, then it should not be a big deal to configure stn-number, server ip, port, username+pw in the VTO's webif in section "Netwok Settings". If you don't know how to set up a SIP port your pabx (NS700?), then you might have more luck in a panasonic pabx forum .
  4. I would add videosupport, allow alaw for all stations (european standard coding) and set dtmfmode to sip info (opening the door will be possible from sip pohones). But that has nothing to do with your problem. [19] type=friend host=dynamic secret=xxxx qualify=yes language=de username=19 callerid="Haustuer" <19> disallow=all canreinvite=no allow=h264 allow=alaw allow=ulaw videosupport=yes insecure=invite dtmfmode=info For diagnosis I would make it easier first, remove 9901 and different context stuff and let VTO call directly to VTH 9902. Also attach "sip show peers" to make analysis easier.
  5. Well, at my home it works with v4.3 fw on VTH5221, v3 on VTO and asterisk 11. If you add asterisk logs (sip set debug on), then we might get a clue on what's wrong. Also add relevant sections of sip.conf.
  6. I guess you did not get it, what a forum is for If you find someone who takes you by the hand and does all the work for you, pls. let me know too...🤗 I suggest you do some asterisk/freePBX tut's first, read this thread from the beginning and then once again. If you still don't know what it is all about, ask your local dealer for help.
  7. According to the install file, yes: root@vlinux3:~/Dahua-Firmware-Mod-Kit/General_VTOXXX_Eng_P_16M_SIP_V4.000.0000000.5.R.20181030.bin.extracted# cat Install { "Commands" : [ "burn dm365_ubl_boot_16M.bin.img bootloader", "burn custom-x.cramfs.img custom", "burn pd-x.cramfs.img pd", "burn kernel-x.cramfs.img kernel", "burn romfs-x.cramfs.img rootfs", "burn user-x.cramfs.img user", "burn web-x.cramfs.img web", "burn data-x.cramfs.img data", "burn gui-x.cramfs.img gui", "burn pcm-x.cramfs.img pcm" ], "Devices" : [ [ "VTO1210A-X", "1.00" ], [ "VTO1210B-X", "1.00" ], [ "VTO1210C-X", "1.00" ], [ "VTO1220A", "1.00" ], [ "VTO1220B", "1.00" ], [ "VTO6110B", "1.00" ], [ "VTO6000C", "1.00" ], <<<<<<<<<<<<<<<<<< [ "VTO6100C", "1.00" ], [ "VTO6100C", "1.10" ], [ "VTO6100C", "1.20" ], [ "VTO6210B", "1.00" ], [ "VTO6210B", "1.10" ], [ "VTO2000A", "1.00" ], [ "VTO2000A", "1.10" ], [ "VTO2000A", "1.20" ] ], "Vendor" : "General" }
  8. As mentioned (I hope), you have to use an old unsigned firmware. There even the config was not encrypted, so it could be read in clear text.
  9. Pls. dont flood this VTO thread with asterisk basic questions! Pls. read either a asterisk tut, this thread from the beginning or post a new thread with your problem.
  10. As far as I understand, FreePBX is simply a project adding a working webIf to asterisk. So everything should work as it does with a base asterisk. I run a asterisk on raspbian, no special version, just the stuff that you get with apt-get.
  11. Did not get 20181030 to work with my asterisk, moved back to a v3 to get it working fine. I use a old Grandstream GXV3140 (40 bucks on ebay), so that I have all home phone issues on one device. Off course any SIP client could/might work with asterisk, but that belongs to another forum and has not a lot to do with VTO2000A.
  12. Yes, I am using chan_sip as well, spares you a lot of trouble. Use v4 from 20180606 since the latter one does not even support asterisk. I just use a simple SIP video phone as my indoor station. Acutally it almost works out of the box and is cheaper than a RPi with a display module (~60-80$). My plan was to use a cheap android tablet but I was not happy with any of the heavy loaded sip clients available. There are some good ones, but they don't support h.264 then. If you really wanna develop it by your own, i suggest either linphone or DoorPi_Phone.
  13. What V4 firmware do you use? There are 2 available for VTO so far. Are you sure you setup your SIP server correctly? No audio could be a a-law/u-law issue too. To be sure, start a SIP trace (either on asterisk with "sip set debug on" or with wireshark on PC with client software). Do any other door opening code work (e.g.simply "1")? If not, do you send it as SIP INFO for sure? A trace would proof that as well.
  14. Regarding video: It is for sure a codec/resolution issue. Had the same with my sip phone initially. Dunno MicroSIP, but is there a way to check actual used codec like jitsi does? Try to lower main resolution to lowest (CIF/QCIF) and give it a shot. Unfortunately the resolution set in main gets used for sip calls too, better would be extra stream.
  15. I uploaded it here: VTO+VTH multilingual firmware I hope the "chinese-portuguese" is better than the "chinese-german"... If you don't like the sounds in your language, you either step back to an old SIP firmware as I did (where you are still able to personalize every sound file!) or you wait for a working V4 firmware, where you are at least able to deactivate the sounds. Too bad, that dahua does not implement a "sound" upload option. I guess, this would not be hard to implement but it would make this little device the only one on the market with such options.