Jump to content

riogrande75

Members
 View Profile  See their activity

  • Content Count

    68

  • Joined

  • Last visited

  • Days Won

    2

Posts posted by riogrande75

  8. Posted

    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.

     

  11. Posted

    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"
}

     

  16. Posted

    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.

  17. Posted

    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.

  19. Posted

    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.

    • Like 1

  20. Posted

    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.

  24. Posted

    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.

  25. Posted

    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.

×