Jump to content

riogrande75

Members
  • Content Count

    62
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by riogrande75

  1. In fact yes, if you are experienced enough to modify the firmware with the toolset mentioned above (BotoX/Dahua-Firmware-Mod-Kit). I dunno the changes of V3.3, but I guess everything of your setup should work with 201704 too. I have a similar setup like you, but my phone is a GXV3140 and server is asterisk. By lowering the video resolution for voip calls (not the rtsp stream!), I got it working just like you. To have video in the phones displayed before actually answering the call, you need to activate a SIP function called early media. Currently I am working on this issue as well.
  2. Since a few days there is a brand new SIP fw out:ftp://ftp.asm.cz/Dahua/videovratni/VTO2000A,VTO2000A-C/firmware/SIP_20180105/General_VTOXXX_Eng_P_16M_SIP_V3.300.0000001.0.R.20180105.bin No info regarding changes so far (as usual). Any testers arround?
  3. While checking the config.export, I found the parameter "SIPServerRedundancy:x.x.x.x" and some corresponding variables at the very end of the file: SIPServerRedundancy:192.168.1.39, UserEnable:true UserID:19 UserType:0} Web:{Enable:true,Port:80} DialRule:{BuildingModeEnable:false DiaSeperator:# ExtentionModeEnable:true UnitModeEnable:false} ... SIPKeepAlive:{FailTimes:3,KeepAliveTime:60,SipServerEnable:true}} It looks like the VTO2000A might be able to handle a redundant SIP server as soon as the keepalive mechanism detects a fault. At least DAHUA tried to implement something like this. I put the IP of my backup asterisk there, but so far it don't want to register there (main server disable, off course). It would make sense for a security device like a doorbell to have such feature.
  4. I guess I found the solution by myself! I found out, that the file that gets created with "Export Config" is a simple textfile. After analyzing it, the parameters regarding the "TalkbackDevice" seemd to me to have something to do with the SIP settings. "TalkbackDevice": {"AudioChannel":0,"AudioEnable":true,"AudioStream":"Main","VideoChannel":0,"VideoEnable":true,"VideoStream":"Main"}, So I changed the VideoStream for TalkBackDevice from "Main" to "Extra1" and uploaded the config again. The "AudioStream" parameters changed itself then to "Extra1". And now I get a resolution of 320x240 in SIP video calls. It really seems that did the trick! Maybe this is helpful for other issues regarding video as well - just edit the config manually.
  5. Did you have a look at this: https://www.ip-phone-forum.de/threads/im-dialplan-per-script-ein-snapshot-erzeugen-f%C3%BCr-die-fritzbox-t%C3%BCrsprechanlage.288096/#post-2185372 I just did wiring of the 24V via wires 4/5 and 7/8 by myself. I pulled out the power wires and then I crimped a RJ45 at the remaining ethernet wires (1/2+3/6). Do you know the HTTP API for Dahua devices: https://support.amcrest.com/hc/en-us/articles/232310368-HTTP-API-SDK-for-Amcrest-products This might help you.
  6. For sip video calls I got a used Grandstream GXV3140 phone. It supports h.264 codec, but unfortunately I am not able to get it working fine with my VTO2000A. Call setup is ok, audio is good, but video is shown as a "grey pixel soup". I guess, the phone can't handle VTO's "high-res" h264 video (800x480) from main profile. I expect also, VTO's extra format when set to QVGA (320x24) might work on my phone. Any Idea, where I might be able to set the used video profile for SIP calls to "extra"?
  7. Yes, but this should not be a problem. The SIP FW comes officially from dahua. Yes, this should work. A long as the phone supports h.264 codec (like GXV3240 does), you do not have to transcode it. Yes - I do it as well. No - it needs 12-24V DC, which can off course be delivered via the spare wires of a CAT5/6/7 cable like many other "cheap" devices do.
  8. Hi! Is there anyone out there, who still has a old SIP firmware, where telnet is still included? I would extract this one and check the difference to newer ones - then I am able to help.
  9. Off course. Just connect it to your wifi and install/configure a sip client app. I prefer BriaMobile ($$), but there are some good ones for free (e.g. zoiper).
  10. I guess the reason is: you have a VTO2000A(1mp) and not a VTO2000A-C (1.3mp, modular). According to a datasheet I found, this seems to be different.
  11. I managed to replace all sound files in the actual SIP firmware (20170425) and installed my VTO2000A finaly at my house' door. I receive emails with pics when someone rings the door and added the cam in my synology's surveillance station. Off course my physical phones ring with a special sound (distinctive ringing) while my soft phones (windows/android) show video too. Nice goody from a russian site: when I get a visitor while I watch TV, my linux based satellite-receiver switches the channel to my VTO's cam automatically. I am very happy with it so far. There is only thing I was not able to figure out so far: How does the sabotage contact work? Is it just this noisy sound outside my door, or does anything happen on the network too (FTP-Upload, SIP-call,...)?
  12. What app do you use on the mobile phones to get video? So far I only had success with BriaMobile($). Where do you register the Mobile phones - asterisk or fritzbox?
×