pkozul
-
Content Count
17 -
Joined
-
Last visited
Posts posted by pkozul
-
-
Did you try setting your other phones explicitly to dtmfmode=rfc2833 ? I have all my phone in dtmfmode=rfc2833 except the VTO which is set to info.That was how I had it set originally, but today I also tried setting them all to info. I wonder if it's something to do with how FreePBX does things.
-
Below are my settings. I set all my extensions to use DTMF mode 'info'. My VTO (extension 8001) rings extension 5000 which is a call group, and that call group dials extensions 8003, 8007, etc. During a call, I pressed 123 and could hear the tones, but the VTO did not show any signs of relay being activated and no voice indicating that the door is unlocked.
[5000] deny=0.0.0.0/0.0.0.0 secret=xxxxxxxxxxx dtmfmode=info canreinvite=no context=from-internal host=dynamic trustrpid=yes sendrpid=no type=friend session-timers=accept nat=force_rport,comedia port=5060 qualify=yes qualifyfreq=60 transport=udp avpf=no force_avp=no icesupport=no encryption=no namedcallgroup= namedpickupgroup= dial=SIP/5000 permit=0.0.0.0/0.0.0.0 callerid=Doorbell ring group <5000> callcounter=yes faxdetect=no [8001] deny=0.0.0.0/0.0.0.0 secret=xxxxxxxxxxx dtmfmode=info canreinvite=no context=from-internal host=dynamic trustrpid=yes sendrpid=no type=friend session-timers=accept nat=force_rport,comedia port=5060 qualify=yes qualifyfreq=60 transport=udp avpf=no force_avp=no icesupport=no encryption=no namedcallgroup= namedpickupgroup= dial=SIP/8001 permit=0.0.0.0/0.0.0.0 callerid=Doorbell <8001> callcounter=yes faxdetect=no [8003] deny=0.0.0.0/0.0.0.0 secret=xxxxxxxxxxx dtmfmode=info canreinvite=no context=from-internal host=dynamic trustrpid=yes sendrpid=no type=friend session-timers=accept nat=force_rport,comedia port=5060 qualify=yes qualifyfreq=60 transport=udp avpf=no force_avp=no icesupport=no encryption=no namedcallgroup= namedpickupgroup= dial=SIP/8003 permit=0.0.0.0/0.0.0.0 callerid=Tetyana <8003> callcounter=yes faxdetect=no [8007] deny=0.0.0.0/0.0.0.0 secret=xxxxxxxxxxx dtmfmode=info canreinvite=no context=from-internal host=dynamic trustrpid=yes sendrpid=no type=friend session-timers=accept nat=force_rport,comedia port=5060 qualify=yes qualifyfreq=60 transport=udp avpf=no force_avp=no icesupport=no encryption=no namedcallgroup= namedpickupgroup= dial=SIP/8007 permit=0.0.0.0/0.0.0.0 callerid=Samsung Tablet <8007> callcounter=yes faxdetect=no
-
Hey !!! I am able to unlock my door via my SIP phones !!!Here is an example of how i configured my VTO (8801), my xLite Softphone and my SIP trunk (fritzbox). I can open the door with xlite and with my IP phones connected to my fritz!box. I am 99,99% sure the magic is done by the "dtmfmode=info" statement in my VTO configuration (8001). After pushing 55 (the unlock code i defined in VTO webgui) it takes about 3 seconds before i hear the relay clicking and the "The door is unlocked" mp3 ...
[fritzbox] type=peer qualify=yes nat=no secret=xxxxxxxx username=626 host=fritz.box dtmfmode=rfc2833 insecure=port,invite fromuser=626 fromdomain=fritz.box context=incoming [xlite] type=friend host=dynamic secret=xxxxxxxx context=users deny=0.0.0.0/0 permit=192.168.1.0/16 [8001] type=friend host=dynamic pedantic=no username=8001 callerid=Türklingel secret=xxxxxxxx dtmfmode=info context=users disallow=all allow=ulaw allow=h264
This would be great if I could get it working on my end.
My VTO is configured as following with FreePBX. I changed DTMF mode as you suggested, but still couldn't get it to unlock. The VTO is still set to the default Open Door Command of 123. I pressed those keys during a call but the VTO did not seem to react.
Any ideas? Are there any other settings you had to change on the VTO? Thanks!
[8001] deny=0.0.0.0/0.0.0.0 secret=xxxxxxxxxxxxxxxxxxxxx dtmfmode=info canreinvite=no context=from-internal host=dynamic trustrpid=yes sendrpid=no type=friend session-timers=accept nat=force_rport,comedia port=5060 qualify=yes qualifyfreq=60 transport=udp avpf=no force_avp=no icesupport=no encryption=no namedcallgroup= namedpickupgroup= dial=SIP/8001 permit=0.0.0.0/0.0.0.0 callerid=Doorbell <8001> callcounter=yes
-
Excellent Serge! Just want we wanted to hear.
In the next few days I will hopefully get time to try repacking the firmware as well, with different sound files.
Cheers.
-
/etc/asterisk/extensions_custom.conf[macro-dial-ringall-predial-hook] exten => s,n,Ringing() exten => s,n,Answer
Oops... minor correction in the macro I posted earlier. The first line should have a 's,1' and not an 's,n'. This is the correct macro to ensure a ringing sound is heard on the VTO when waiting for a caller to answer:
[macro-dial-ringall-predial-hook] exten => s,1,Ringing() exten => s,n,Answer
-
Thank You Pkozul fpr you Configuration.I'm using raspberry too, but without follow-me. Pure asterisk
I switched to the new Thread too. My big Porblem was that i not set the realm to asterisk and .... has headatack.
I tested after that how the Indoor Station VTH1550 and some Voip-Clients are working with the SIP-Clients and Asterisk. Seems very good.
Greetings
Great to hear. What do you think of the VTH1550? I am considering getting one myself.
-
Hello pkozul,can you please post the Asterisk Conf-Files.
I and other people are trying the same.
Are you using the internal SIP-Server in VTO and Asterisk as Client or the Registrar in Asterisk?
I'm trying right now to use the internal SIP-Server, because it works good wit VTH indoor Station. Do you have tested it with a VTH too or only SIP-Clients.
But it this case is something very strange - Asterisk registered with 9901 at the VTO, but when i call 9901 or other (pres Ring Button), then the VTO is trying to connect to the Asterisk as Client with username 8001 In other words, if i don#t make something wworng th VTO is trying to resgiter self a the Asterisk for this one call. But i don't know what Password for 8001 is set inside the VTO.... admin and 888888 doesn't work.
I can make from asterisk outgoing call to VTO over Number 8001 but i don't become a Picture - only Sound.
Per sip show channels i see, that my Linphone Client has activated alaw and h264, but the 9901 line to the VTO use only alaw without h264. It seems he doesn't accept self calls with activetad video?! But why works with VTH and not wih Asterisk and Linphone. Wrong Realm?
This is because it would be very kindly if you can post here you settung for asterisk and VTO.
Thanks
Hi gerdshi,
Sorry, I somehow missed your message on here.
I am using my own SIP server, which is Asterisk on the Raspberry Pi (FreePBX). I installed the Follow Me module and used it to create a ring group, so that when someone presses the button on the VTO, it dials a bunch of extensions to make sure one of us at home knows about it.
I don't have a VTH unit and have only been testing with SIP clients (Jitsi has worked well on my Windows machine). I have a Windows phone but have not come across a good SIP client on there. My wife has Bria installed on her iPhone which works well.
In terms of configuring the VTO, below are the settings I recall changing:
Local Config > A&C Manager
Villa Call Number: 5000 (the extension I created in Asterisk for the Follow Me call group)
LAN Config > LAN Config
No.: 8001 (the extension I created in Asterisk for the VTO)
Network Config > SIP Server Config
IP Address: 192.168.1.220 (IP address of my Asterisk server)
Port: 5060
Username: 8001
Password: •••••••••• (password / secret I created in Asterisk for extension 8001)
SIP Realm: asterisk
Sip Server: Enable
In terms of Asterisk configuration changes, I documented the changes in the other thread Allodo started:
http://www.cctvforum.com/viewtopic.php?f=6&t=52356
Let me know how you go.
-
Hi Serge,
Just getting back to you regarding your suggestion about how to get the VTO to play music or make ringing sounds while waiting for it to establish a call.
I tried your suggestion but couldn't get it working. I think it's because I'm using Follow Me to manage the ring group I have set up, and that has it's own dial plans, macros, etc.
In any case, I finally got it working. I simply added the following macro, which is a 'hook' that allows you to inject your own code as the ring group is being called.
/etc/asterisk/extensions_custom.conf
[macro-dial-ringall-predial-hook] exten => s,n,Ringing() exten => s,n,Answer
I believe this is only really relevant for those using FreeBPX and the Follow Me module to handle ring groups.
We're getting there slowly... keep up the great work!
-
Maybe there is some helpful stuff in that project?There is a lot of helpful stuff in there, thanks a lot !
The author of that project just said he is actively working on it and will hopefully have support for CramFS in the next few days.
-
I started analyzing the firmware to replace mp3 files. I think i am pretty close to be able to replace them.Great work Serge.
Not sure if you have come across this before, but another guy has done some work around unpacking / repacking firmware images for Dahua IP cameras.
https://github.com/BotoX/Dahua-Firmware-Mod-Kit
Maybe there is some helpful stuff in that project?
-
Which Dashua app are you talking about ? If it can open the door it should be possible to tcpdump the traffic an simulate that request using a bash script (curl ?) called by asterisk.Hi Serge,
I don't own a VTH indoor monitor, but I can see in the manual (in section 2.2.) that it talks about remotely unlocking the door:
As you said, it would be great if someone could capture the traffic to see what is actually being sent by the VTH indoor monitor to unlock the door. Anyone here able to do that?
I believe there are some mobile apps (iDMSS and gDMSS) from Dahua, but not sure if they can be used to unlock the door.
-
Great info Serge. That is really useful.
On a separate note, I have found a way to unlock the front door during a video call with the VTO. For example, if I answer the call when someone rings from the VTO, during the call I can press a combination of keypad numbers in my app (DTMF), and that triggers a shell script on the Raspberry Pi which controls a relay to unlock the door. This means I am not even using of the VTO's built-in connections for unlocking the door (which I think requires a Dahua indoor station, or Dahua app). I haven't ordered a relay and door strike yet, but I have a few options in that area. I can either use a separate relay that I connect to the Raspberry Pi, or I can use one of the relays on my alarm panel. Either way, I can control these relays via the shell script that gets executed.
So, the way I got this working is by using 'dynamic features' within Asterisk, which allows you to use DTMF within your calls.
First, I defined a new dynamic feature called 'unlock-door'.
/etc/asterisk/globals_custom.conf
DYNAMIC_FEATURES = unlock-door
Then, I configured the 'unlock-door' dynamic feature to run the macro 'unlock-door' whenever DTMF code 777 is pressed.
/etc/asterisk/features_applicationmap_custom.conf
unlock-door => 777,self/callee,Macro,unlock-door
To ensure this 'unlock-door' dynamic feature is available in each call, I added it to 'the [from-internal]' context. As you can see within there, I also enabled extension *777 as an additional way to unlock the door (this is not via DTMF, but rather an extension that can be dialed at any time to unlock the door). Finally, I created the 'unlock-door' macro the does the actual work, that is, executes the shell script 'unlock-front-door.sh' (which controls the relay, and can do whatever else you want it to). You can see I used a condition in there, so that the shell script can only be executed by extensions other than the VTO2000A (which uses extension 8001).
/etc/asterisk/extensions_custom.conf
[from-internal] exten => s,1,Set(__DYNAMIC_FEATURES=unlock-door) exten => *777,1,Macro(macro-unlock-door,s,1) [macro-unlock-door] exten => s,1,ExecIf($["${CALLERID(num)}"!="8001"]?System(/var/lib/asterisk/agi-bin/unlock-front-door.sh)) exten => s,n,MacroExitBTW, I have not made any changes to any other Asterisk config files. The above three files were all empty when I started, as they have been provided by FreePBX / Asterisk to allow you to add your own stuff.
As per my earlier post, I installed the Follow Me module within FreePBX to allow the VTO to call extension 5000, which is an extension I created to act as a ring group. For that extension,, I enabled Follow Me, and simply added all my other extension numbers to the ring group within the Follow Me tab for extension 5000.
I think I am very close to achieving what I wanted with the VTO200A.
The only thing left I can think of is finding a way to replace the voice/sound files on there, but I don't think anyone has been able to successfully replace these files and repack the firmware.
Also, has anyone been able to get the VTO to make ringing sounds when the button is pressed and it waits for someone to answer? I have tried a few things, but no luck. It would be good if the VTO could emit some rings or beeps while waiting for the other extensions to answer, rather than just a voice saying 'Calling..' (from what i remember) and then silence until someone answers, or until it times out. If all else fails, I will try to wire up a simple speaker (or cheap doorbell simply to make noise throughout the house) and see if I can get Asterisk to execute a shell script when the VTO initiates a call, in order to activate the speaker/doorbell. Not sure if that's possible with Asterisk, but worth investigating.
-
Hi Allodo,
I also have a VTO2000A but my set up is a little different to yours, as I don't have a Fritzbox.
After a bit of digging around, I finally have my system working. My set up is as follows:
- Dahua VTO2000A as front door intercom at our home - used as SIP client
- Asterisk (FreePBX) running on Raspberry Pi - used as my server
- Mobile phones at home - used as SIP clients
To get the VTO2000A working as a SIP client, I needed to flash it with the SIP version of the firmware.
ftp://ftp.asm.cz/Dahua/videovratni/VTO2000A,VTO2000A-C/firmware/20160505-SIP.ZIP
In FreePBX, I created the following extensions for my various SIP clients at home:
- 8001 - used for the VTO2000A
- 8002 - used for mobile phone A
- 8003 - used for mobile phone B
- 8004 - used for laptop
- 5000 - used as a special number to handle Follow Me
As you can see, I created extension 5000 to support Follow Me, which is a module I installed within FreePBX. Among other things, it allows you create a 'ring group' so that the VTO2000A can call multiple extensions at the same time when the doorbell is pressed. I was originally using the Ring Group module, but that didn't work for me as the calls kept getting terminated after 5 seconds.
In terms of SIP client software on my devices, I tried both Zoiper and Bria on the iPhone and they both work OK.
On my laptop (Windows), I tried Linphone and Jitsi and both work fine.
From what I recall, in all of the SIP clients, I needed to install/enable/purchase support for H.264 since this is the video codec used by the VTO2000A.
Overall, I'm, happy with the system now. Whenever someone rings our front doorbell, all of our devices start ringing and the first one to answer establishes the video call with the person at the front door.
Cheers.
-
Hi there,
I have a Dahua VTO2000A intercom and was unable to power it using my TP-Link PoE switch.
Do you think it would have the same pinouts as the Dahua cameras? If so, I'd like to try it, but a bit worried if I end up frying it.
Thanks,
Pete
-
Hi there,
Just in case anyone else needs this info...
I finally got my VTO2000A working using SIP. Whenever someone presses the button on the intercom, it calls an extension I created in Asterisk. This extension is configured using the Follow Me module and I set it up to dial a bunch of other extensions at the same time (mobile phones, tablet, etc.).
The first extension to answer the call establishes a video call with the intercom. This works great using Bria on my iPhone, and I also tested it using Linphone and Jitsi on my laptop.
In terms of overall set up. I have Asterisk running as part of FreePBX (on the Raspberry Pi).
On the VTO2000A, I installed the SIP version of the firmware and configured it to use the Asterisk SIP server.
-
Hi there,
Has anyone had any luck in getting their VTO2000A working with SIP? I installed the SIP firmware on the device recently.
I have a Raspberry Pi with Asterisk running on it. The mobile phones in the house each have their own SIP extension and I was hoping I could get the VTO2000A to dial a SIP group extension number and establish a video call, when the doorbell is pressed.
So far, this works for audio, but I don't know how to get video working. Maybe the Dahua firmware does not support sending video via SIP? If that's the case, how else can we get the video to be sent to the other devices?
Thanks!
Dahua VTO2000A, SIP Firmware and Asterisk
in Installation Help and Accessories
Posted
He he. I am considering the same. I probably should look at getting to the bare metal rather than relying on a web-based user interface to manage my Asterisk settings.