Search results

I spun up a vps on ionos (cloud vps) and used Debian 11 and installed Fusionpbx in a production environment with no issues. It's running now. I haven't tried Debian 11 on any Vultr servers but I can't think of why the server host would affect Debian 10 vs Debian 11 with Fusionpbx.

You can always set it to where if the call park is not picked up in XX minutes then the call rings back. I set this up in the dial plan

I thought 8am meant the entire 8 am hour and 5pm meant the entire 5pm hour. So to get the phone ring from 8am - 5pm I would actually set it 8am -4pm?? The Fusionpbx site says that the time is the whole hour. confusing but . ..

I had the same issue today. Numbers not being blocked. I went into the dial plan as suggested above and changed the order from 40 to 25. It works.

I just spun up a new Debian server (11). Logged in via ssh using Putty apt-get update apt-get upgrade Then wget -O - https://raw.githubusercontent.com/fusionpbx/fusionpbx-install.sh/master/debian/pre-install.sh | sh; cd /usr/src/fusionpbx-install.sh/debian && ./install.sh Worked perfect...

I have verified that my server time is correct. EST. As you can see from the attached image the calls are supposed to go to IVR-NICODA Monday - Friday 8:00am - 5:00pm This works fine. But, when 5pm rolls around, calls are suppose to go to 401VM-After hours. They do not - they continue to go...

Please disregard - I am now able to login. Firewall issue to port 80. The issue I am having now is the internal sip profile says its not running (via gui) and when I click on START, it acts like it's going to start but never does/. If i click on restart it says in yellow highlight, INVALID...

I changed the internal sip profile port from 5060 to 5070 and then decided to change it back. I RESTARTED the internal profile via the gui. It would not restart. So I rebooted the server. After the reboot I no longer have GUI access at all. It just does nothing, and eventually says page...

Whenever I put some on park, it appears to work fine. The caller hears the hold music, But the logs tell a different story 2022-01-03 21:14:39.391592 [ERR] mod_local_stream.c:880 Unknown source default 2022-01-03 21:14:39.391592 [ERR] mod_local_stream.c:880 Unknown source default 2022-01-03...

Adrian again I appreciate you accommodating me and giving me good advice. I am by no means at the level I should be but I’m constantly learning day by day and people like you really help me out tremendously. Thank you again

Ok, thank you.

I have seen many people discuss inserting your numeric ip address (ie: 155.23.222.222) in the rtp field ( $${local_ip_v4}) in the sip profile Is this necessary and do I need to do that for some reason? So I need to change $${local_ip_v4} to the actual numeric ip address...

Adrian - If you are dropping them why does your output all say ACCEPT?

I went to this website and followed the instructions on blocking all foreign IP addresses. This makes sense since all my clients are in the USA. https://linoxide.com/block-ips-countries-geoip-addons/ I run into an error message after I run the following commands: # wget...

Thank you very much Mark for clarifying. I stand corrected. You are correct. I’m not sure why but In my installation somehow all my devices set at 5080. Now when I go back and create a new device it is showing 5060. Thank you for your input and your time

Hi Matthew - Did you ever write a how to?

I have the same issues at times. Years ago, when I was provisioning Yealinks, I would select the BLF field and in the value field enter the ext # ie: 1001 Later I realized I needed to add the domain after the extension ie: 1001@domain.yourdomain.com After this it worked fine in some...

In my screenshot above, a device set up, you are saying that should not be 5080? It populates by default. Why on a new fusion installation does it autopopluate 5080 on the device set up? Also, in response to your help with assigning sip listening ports on my yealinks. The reason I did this...

That sounds like a limit on your inbound DID provider. Fusionpbx does not (out of the box) limit inbound calls.

In the device settings, you have the choice to set up your device as UDP or TCP. I am assuming you use port 5080 regardless Now I was told that some of the natting issues I was having would actually benefit by using TCP rather than UDP Can anyone shed light on this? Does TCP really offer a...