I setup FreePBX 17 as a Proxmox VM for testing VoIP in an office.
I was able to register two Yealink phones and two Zoiper softphones.
I have been unable to register an Axis 8105-E Network Door Station.
I set up extension 280 for the 8105-E in FreePBX.
I logged in to the Axis 8105-E Web GUI and used the SIP Setup Assistant to:
Add an account with the User ID 280 (the FreePBX extension no)
Password copied from FreePBX Secret
Caller ID 280 again
Registrar Address is the FreePBX IPaddr.
Next I added the two Yealink phones as two recipients using the ‘extension@IPaddr’ format (ex [email protected]) .
Next I added the DTMF sequence of 99 to trigger “Unlock Door”.
On the Configure SIP Settings screen, I have “Allow incoming SIP calls” selected.
I did not use any of the NAT Traversal settings because I do not think I am behind a firewall.
DTMF sequence 99 (Unlock Door) triggers Unlock Door (AccessDoor)
DTMF sequence 99 (Unlock Door) triggers Door Buzzer (PlayClip)
SIP Settings —
Incoming SIP Calls: true
Enable ICE: false
Enable STUN: false
Enable TURN: false
When I click finish in the wizard, The Registration Status in the Axis Web GUI for the 8105-E is Red Request Timeout (208).
I should say that I initially set up the Axis 8105-E using the “Axis Camera Station Edge” Windows app.
When I click the call button on the 8105-E it does ring on both the
“Axis Camera Station Edge” Windows app and the
“Axis Camera Station Edge” iPhone app
Maybe this is causing a conflict. idk. I don’t even know how it is ringing on those two apps. I just installed the apps and signed in.
This sounds like a weird configuration, however one would not expect that to prevent registration. One would not normally configure an office VoIP so that one phone could directly contact another, without going through a PABX. In fact one would not normally know the IP addresses of the phones, as only the PABX would know them as a result of their registrations.
Also NAT isn’t something that is made necessary by firewalls (although the software that implements firewalls often implements traversal mechanisms). Your network manager should know whether you have NAT, as that is a key design decision for them. (Standard home and small business systems have NAT traversal to the internet, but not between internal devices.)
You need to capture the REGISTER on the FreePBX box. If it doesn’t get there, you do not have a FreePBX related problem. If it does. you need to see if it gets through the FreePBX firewall, and ends up on the right port on Asterisk. If it does, you need to look at the Asterisk logs to see why it is being rejected.
Thanks for the detailed reply to my strange problem.
I did expect everything to go through FreePBX. What threw me off is that I could not figure out how to set up the Axis 8105-E Door station with the web gui. I followed Chris’ (Crosstalk solutions) video tutorial ( https://youtu.be/6eNNLBgCjq0?si=6AuIIXC95vsrtVlW ) where he recommends setting up the Axis Door Station by installing the ‘Axis Camera Companion’ app which has been replaced by the ‘Axis Camera Station Edge’ app.
During this setup process I set up things like updating firmware, setting up motion recording, audio and other basic settings like name, resolution,
Somehow when I set up the 8105-E with the Axis app, it automatically alerts every app installed with the same Username everytime the Boorbell/Intercom button is pressed.
The Axis Camera Companion app was designed “back in the day” by Axis as a K.I.S.S. solution, the way it worked is all cameras, devices, door cams, etc. registered into the “Axis Cloud” When you were configuring the Axis devices, you were actually sending configuration commands to the cloud and the devices were all registered into the cloud. This is why all of that nonsense got replaced by the new app.
Axis devices are the Cadillac of the security industry and they charge $$$$$$ for them. Because of that, unlike most of the security vendors, they have a very good support department. Your going to find answers far quicker by emailing Axis’s support department, than asking here. Just tell them you have a VoIP PBX that has hardware desk phones from Yealink and softphones that are registered into it and they are all working fine, and you want to connect the 8105-E into the PBX, and it’s not working. They will help you out I’m sure.
FreePBX Firewall Intrusion Detection does have the 8105-Es IP Banned!
I moved it to the custom Whitelist and now it is Registered and is working as expected. Thank you to Stewart1 and david55.
When I click on the Axis 8105-E Door Button, it instantly calls all extensions set up in FreePBX (as well as all devices that have the Axis Camera Edge app installed). I am able to answer the call and see the video as soon as I answer.
I have two much more minor issues:
When I answer the call and speak, there is a significant delay between the time I speak and the time I can hear myself in the Axis 8105-E.
If I do not answer the door in time, it plays the Voicemail message for one of the extensions. How do I change this so no message is played if no one answers just like a traditional door bell?
It was a full 5 second delay through a mobile phone (which was connected through the Axis app & not FreePBX) but I just retested it with the Yealink phones (FreePBX) and there is almost no delay now. I will test it more throughout the day.
I don’t use the model you have, but I have a number of I8016-LVE units in use for video door intercoms. They more or less “just work”. At one point there was a firmware problem that caused them to hang, and needed to be manually rebooted, but that was a good while ago; I’ve had no firmware problems (that I know of) for at least the last year.
One of my clients uses them on “employee doors” so that temp workers and contractors can be let into the building by a shift supervisor, using a cell phone. We use Clearly Anywhere soft phone on that cell phone; they’re able to answer the door and unlock it with very little delay. Ultimately we’re quite happy with this solution.
Are you still having any problems with your setup?
on the voicemail part of your question: Either your doorbell got a specific extension from the freePBX, then you may see the doorbell as an extension, or the doorbell has no extension and is just calling into the freepbx, then a specific inbound route may help where you can configure the ringtime, you can configure a target (ring group or extension or specific message after xx seconds saying eg ‘sorry nobody at home’.
All of the Yealink T58 phones play a ‘doorbell’ ringtone when they receive a call from the A8105-E.
If no one answers it just stops ringing without going to Voicemail which is the behavior I want.
If I answer on a Yealink T58 phone I can speak and type a DTMF code to allow the door to unlock.
When I type in the DTMF code the A8105-E will play an audio clip of a buzzer to alert the person that they can come in.
“ISSUES”:
The only real issue I am having is that when the A8105-E plays the ‘buzzer’ audio clip it will stop playing the buzzer as soon as I hang up. I believe I set the clip to play as long as the door is unlocked but it will stop as soon as I hang up. If I could solve this minor issue it would be perfect for my use case.
Another minor issue is that one of the extensions in the call group is a zoiper softphone on an iPhone. It sort of works if the Zoiper app is open when the A8105-E button is pressed. If the phone is locked, I won’t see anything.
This would be more of an issue but I found a workaround by enabling an Axis web gui “Action Rule” to make a “Video Management Software call” when the button is pressed. I don’t know if this is a Zoiper issue or iPhone issue. I don’t think it is a FreePBX issue.
Another Zoiper softphone issue is that I set the A8105-E to accept SIP calls. If I call th A8105-Es extension from a Yealink T58 phone I can see the Video & hear audio/speak. If I call the extension from a Zoiper softphone I can hear audio & speak but no video is displayed. I am guessing this si also a Zoiper issue.
Thank you to Stewart1 and david55.