No Brainer to have.... also - how about some optional preemptive outbound SMS - Cron jobs could check for:Coming Soon: New SMS Toolkit for VitalPBX with Skyetel, Vitelity, and VoIP.ms DIDs
- @help – Play a list of supported SMS commands
- @news – Retrieve latest news headlines from Yahoo
- @weather – Retrieve weather report by zip code
- @wolfram – Siri-like query to Wolfram Alpha
- @whitelist – Whitelist a new IP address in your firewall
- @disa – Use DISA calling from your smartphone with password
- @cf on – Enable call forwarding from PBX extension to smartphone
- @cf off – Disable call forwarding from PBX extension
- @asteridex – Use AsteriDex Voice Dialer to place a call from PBX
- @fail2ban+ XXXXX – Restart Fail2Ban with PIN: XXXXX
- @fail2ban- XXXXX – Stop Fail2Ban with PIN: XXXXX
- @firewall+ XXXXX – Restart FirewallD with PIN: XXXXX
- @firewall- XXXXX – Stop FirewallD with PIN: XXXXX
- @asterisk+ XXXXX – Restart Asterisk with PIN: XXXXX
- @pbxstatus – Returns status of Asterisk, Fail2Ban, and FirewallD
You typically want to change SSH ports to reduce the noise from all the scanner bots hammering port 22. The goal is to decrease logging activity and network activity and therefore load. Less activity also means less chance of a compromise but that is not the primary goal imo. You're never going to be able to hide from all of them but anything is better than port 22.How about setting up ssh keys and disabling passwords on root logins.
Accessing root accounts over the internet with passwords is just plain insecure.
I agree that moving the ssh port off of port 22 is a good idea but I can also tell you from experience the bad guys will eventually find your alternate port. I have had ssh on alternate ports for the last 20 years or so but in the last 2 or 3 years the bad guys are finding the alternate ssh ports much more frequently.
No. Its an Aastra 9143i which works perfectly with FreePBX. The main line of the phone is on IncrediblePBX 16-15 and another line on the VitalPBX. I suspect there are some system settings akin to the FreePBX Settings>Advanced Settings that probably are not adjustable through the VitalPBX GUI.
VitalPBX bug report 0000148 submitted. The issue with "s" showing in the display instead of the dialed number became an issue when upgrading software from 2.3.8-1 to 2.3.8-3. However, the outbound caller-id lookup does not work for me on 2.3.8-1 either so far as updating the phone display with the name of the party you called.
So, do you backup the primary and restore it to the secondary server once a week, for example, so that changes to voicemail greetings, follow me settings, etc. on the primary server are always up to date on the secondary server?From my vantage point, HA isn't as crucial as it used to be. Almost all major SIP phones now have a failiover option on the phone itself. If your voicemails are delivered by email, then failover to another site is as easy as keeping both servers up to date. There's no voicemail to worry about. When the primary server fails, all of your phones will reconnect to the secondary server in less than a minute. And providers such as Skyetel provide similar failover services for trunking.