Jump to content

riogrande75

Members
  • Content Count

    57
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by riogrande75

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. Yes, yes and no. I am suggesting General_VTOXXX_Eng_P_16M_SIP_V4.000.0000000.1.R.20180606 if you really "need" V4 on asterisk. As mentioned, there is a V3 nonSIP firmware with portuguese audio messages available. In the latest english only V3 SIP fw (20181229) single audio messages cannot be disabled - i guess this a V4 "feature". BTW and once again: You can always move from one to any other firmware with your VTO2000A. If the dahua tools do not support that, just use the tftp method. But you need to have either a lot of experience with embedded devices/networking/electronix or you must read the whole unbricking thread VERY carefully.
  10. Well, it connects to my asterisk too (sip register is simple and does not have a lot of options). But there seems to be a problem when tryin to establish the connection. But maybe thats better with pjsip, my ast is still on chan_sip.
  11. No sorry - mistake. I got a SIP v3 firmware dated 20181229 english only.
  12. Either you use 1st v4 firmware I posted 20180629, or get back to v3 fw. Btw. I have a pretty new v3 fw with portugese lang (20181229), but non SIP.
  13. Dunno. I guess, webservice 2.0 is and will be the future. But even it seems that they changed simple html code only, it's very buggy now. Somehow they still release brand new versions in "old" web service 1.0 flavour. Anyhow, don't use General_VTOXXX_Eng_P_16M_SIP_V4.000.0000000.5.R.20181030.bin as they removed asterisk support. With that version installed I never got any successful connection setup to asterisk.
  14. Hi! Just installed the fw it on my test vto as well. At first, it looked like yours (empty parameter fields), but I solved it with clearing browser cache (as I was expecting it). So I did not flash the language file at all. I suggest to read the manual, where all the parameters are described (well, at least most of 'em). I don't know RasPBX as I youse asterisk in it's pure version (cli). What I can say right after havin a quick look at the pics: IP and 8001 as registered number seem ok. If you press button on VTO a call to 9901 will be setup (1st pic). I guess the problem is your SIP server. Is the ext. 8001 really configured correctly? I would deactivate auth just for testing purpous. Also I would try to add VTO as CHAN_SIP and not PJSIP. I run all devices with chan_sip and everything is fine. In fact I did not play arround a lot with pjsip. Additionally I would change the villa call number to fit your environment (e.g.1000/2000). When you setup a SIP call to 8001 the vto should pick up the call automatically and you should have a audio/video connection if everything is setup correct. If not: User asterisk debugging (sip set debug on) - that will point at the problem.
  15. Can you pls. post the download location of this firmware ( General_VTOXXX_Eng_P_16M_SIP_V3.300.0012001.0.T.20181229.zip)?
  16. You do not need sonia.zip and videodeamon.zip since this are the two main "programs" running on the VTO and are included in the firmware already (off course). No clue why dahua adds them as a zip file in the firmware archives separate. You can get video via vlc and rtsp://vto_ip:554/ Dunno "MicroSIP", but green screen and dots sound like a video resolution issue to me. Does you client support h.264 video with 800x480px? Use jitsi on windows to check, what resolution is set in VTO for sip calls. Did you check "CGI Enable" in "Security"-Tab?
  17. Unfortunately the command: http://<ip>/cgi-bin/snapshot.cgi? [channel=<channelNo>] from other Dahua IP cams does not work on my VTO. So I use this in a PHP script to grab a pic: $snapshot = shell_exec('avconv -y -i \'rtsp://admin:admin@vto_ip\' -f image2 -vframes 1 -pix_fmt yuvj420p /home/user/snapshot.jpg');
  18. No, I just own VTO's. Did you use internet explorer or any other browser?
  19. Why should a VTO2000A firmware work on a VTH1510C ? Off course not! But you better use General_VTH151X_Eng_SIP_V4.300.0000000.5.R.20181024. I uploaded it for you: http://www.share-online.biz/dl/8WXQAKJP9K8Z
  20. Just uploaded it here: http://www.share-online.biz/dl/4NKNMEJP0N52
  21. 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
  22. 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.
  23. Where do u want to redirect it to? Do you run a machine with SmartPSS?
  24. 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.
  25. @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.
×