Search results

  1. dbaum

    BUG Insertion of FQDN in IncrediblePBX on VitalPBX crashes system and locks out all access

    Additional info - this does not occur with native VitalPBX installation
  2. dbaum

    ALERT Following access recovery instruction in Nerd Vittles 30854 does not work

    Bill your attitude is inappropriate. I have been active with this project since PBX@Home and am not lazy as you inferred. I properly reported an error condition that is repeatable. What link would you like. I showed the command issued, referenced the Nerdvittles article by number and showed...
  3. dbaum

    BUG Insertion of FQDN in IncrediblePBX on VitalPBX crashes system and locks out all access

    Use of FQDN in the referenced installation causes system crash and total lockout requiring rebuiild.
  4. dbaum

    ALERT Following access recovery instruction in Nerd Vittles 30854 does not work

    Instruction 9 in the above referenced article includes a remote access recovery step that reads as follows: iptables -A vpbx_white_list -s 12.34.56.78 -j ACCEPT This step returns an error vpbx-white-list does not exist
  5. dbaum

    R.I.P. Fail2Ban does not jail unauthorized access attempts

    Also why do you recommend a vendor that has no telephone support (even at a price) and has unanswered tickets two years after entry)?
  6. dbaum

    R.I.P. Fail2Ban does not jail unauthorized access attempts

    Then why is your recommended vendor for VMs still loading it
  7. dbaum

    R.I.P. Fail2Ban does not jail unauthorized access attempts

    I am running a fresh install of Incredible PBX 12.0.76.6 in a VM at RentPBX. (PBX in a Flash Incredible PBX 11-12 with Incredible GUI (Centos 6.6) I had 128 failed login attempts under "cron" user. I had to manually ban the IP address/ [2019-11-25 09:46:12] NOTICE[809]: manager.c:3211...
  8. dbaum

    R.I.P. iptables, fail2ban, and add-fqdn problems

    Running PBX in a Flash Incredible PBX 11-12 with Incredible GUI (Centos 6.6) for some time. Went to add another FQDN with add-fqdn. Routine ran but did not show iptables rules in effect for the newly added fqdn. Examing iptables file does not show the addition of the fqdn entries that should...
  9. dbaum

    BUG add-ip not fully functional in 13-12

    But just in case, is there an upgrade script? Will a backup from 13-12 restore to 13-13?
  10. dbaum

    FYI "Trusted" Providers

    As part of increased security I would like to eliminate the "Trusted Providers" included in the Whole Enchilada and other releases. I presume I have to manually edit out the section from /etc/sysconfig/iptables to do this. Ward would you consider not including this section and use a script...
  11. dbaum

    FOOD FOR THOUGHT Potential Image Problem in RentPBX Installations

    Migrating to another relase. Ward please close thread.
  12. dbaum

    BUG add-ip not fully functional in 13-12

    Ward, thanks Will RentPBX support this? I have considerable credit with them and would like to stay with them.
  13. dbaum

    BUG add-ip not fully functional in 13-12

    When using add-fqdn, the final phase of the script displays the iptables rules in effect for the fdqn as of the completion of the process. When using add-ip, the final phase of the script displays the message "the following iptables rules are in effect for the" [the ip address] BUT there is no...
  14. dbaum

    TIPS PJSIP Introduction is a pain for migration from earlier vversions

    Ward, which do you consider "latest releases" I'm using the most recent release that RentPBX will install. I finally figured out the problem. After changing Chan_SIP to 5060 and then disabling the PJSIP you have to RESTART ASTERISK via reboot. The APPLY CHANGES in the GUI does not work. So...
  15. dbaum

    TIPS PJSIP Introduction is a pain for migration from earlier vversions

    new build compleeted with same problem. trying a two soft clients now. Zopier for Business did not work even with changing the port.
  16. dbaum

    TIPS PJSIP Introduction is a pain for migration from earlier vversions

    Yes I deleted all the extensions and tried manual creation. Still error. I just had install rebuilt by FreePBX. Will try again
  17. dbaum

    TIPS PJSIP Introduction is a pain for migration from earlier vversions

    In PJSIP I changed it to an unassigned port. In Chan_SIP I changed it to 5060. In advanced settings I select CHAN-sip as only protocol. Still get the same error message.
  18. dbaum

    TIPS PJSIP Introduction is a pain for migration from earlier vversions

    Normally I use BULK DID and BULK EXTENSIONS to migrate upward. While this has worked fine, the new default to PJSIP has created a problem. All extensions send message: NOTICE[6485]: res_pjsip/pjsip_distributor.c:347 log_unidentified_request: Request from...
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.
Top