Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by riogrande75

  1. 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
  2. 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.
  3. Where do u want to redirect it to? Do you run a machine with SmartPSS?
  4. 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.
  5. @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.
  6. 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.
  7. 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 General_VTO2000A_MCU_V3.000.0000.0.R.20180316.zip VTO2000A, VTO2000A-C, VTO2000A-2 General_VTO2000A-Master_MCU_V3.000.0000.0.R.20170515.bin I uploaded it for you guys:http://www.share-online.biz/dl/N4NELLIPXJ
  8. 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
  9. Use VDPconfig from toolbox to upgrade.
  10. Yes, indeed there is a V4 SIP firmware out there: https://support.vidimost.com/comment.php?dlid=497 It includes the new webinterface 2.0, some minor changes. But it still lacks the feature to install your own sound files. I hope they are still working on this, users all over the world want that.
  11. Yes, there was a change in the upgrade process. But I do always upgrade via TFTP method, so don't ask me about it. Nevertheless, you will not secceed in installing a customized firware anymore. Since beginning of 2018 all FW files are signed, that means it is impossible to change it - only the manufacturere (dahua) can do this. So you got either install a older, even customized firmware via tftp or you got to live with that until dahua releases a firmware where you can replace the sounds officially via the web interface. Good luck, Rio
  12. Then just factory reset it (press button on the back for 5 times)
  13. Didn't you unzip the .bin file from the archive? You must not just rename the whole archive from .zip to zip.bin!
  14. You can get it from here: https://www.dropbox.com/s/15mx30el5bfyolf/General_VTOXXX_Eng_P_16M_SIP_V3.300.0012000.0.R.20180627.zip?dl=0
  15. Ugrade software to version from 2018-06-27. There was a bugfix related to 3CX phone systems.
  16. Hi! Actually I wanted to know what software version you have on the VTO2000A. Settings in the SIP part of the VTO would be interresting too. In the past I faced this issue as well from time to time. Now, it seems a config change solved the issue.
  17. If eth interface comes up at least a very short period, then I am convinced the TFTP method should work. Connect the device to a 100MBit/s switch and set up a pc according to unbricking guide. Before doing the actual TFTP upgrade process, start wireshark on the pc and see it there is any tftp request from the device.
  18. Hi JM170! What software do you use? What asterisk version? Can you pls. post the part for the VTO ext. of your sip.conf.
  19. 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":"","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.
  20. The only chance I see, is to poll the device via the CGI_API every e.g.10 secs. and extract the info from there. Pls. see attached part of the DAHUA_HTTP_CGI_FOR_VDP.pdf document.
  21. riogrande75

    gDMSS software on Smart TV

    Depends on you TV. Due the age of my TV (2012 Samsung ES-Series) I just added the cam's rtsp stream as a channel on my enigma2 based satellite receiver. A little script switches to this channel as soon as someone rings at the door. This works perfect for me.
  22. riogrande75

    Use 24VDC to run 12VDC cameras

    Hi! I'd say that they were running fine with 24V due the voltage drop at the long cables. With, off course, less power@higher voltages the supply had obviously no problem. But you would have to look at the cam's power electronic part, to become more clear. My experience is also, that most 12V rated cams work with volatages from ~9V to 25V without any issue as long as it's not too hot at their installation place. What I still don't get, why did you mention 24VAC? I do not expect, the cam will work with AC at all - they egal have no built in rectifier. Also when I take a quick look at the AL400ULXPD16's specs, there is either 12V@4amp or 24V@3amps, but DC only.
  23. Just read this thread from the beginning, everything is explained in here.
  24. This sounds for me like a SIP issue. To get video before picking up the call, the destination (VTH) has to send a 183 SESSION PROGRESS + SDP message to the caller. This is called early media. Obviously the VTH is able to do this, the other phones not (or at least not out of the box). I'm working on this issue since a while. I do not have VTH, only VTO and 3rd-pty phones. It would be very, very helpful to get a SIP/LAN trace of both, the good and the bad case. Then I might be able to figure out how to get asterisk to act like the VHT.
  25. Anybody who would share his configuration export of a VTO2000A running 201801 SIP firmware? I wanna compare it with the old config (SIP 201704). I guess I might figure out what new features have been implemented by DAHUA.