Search results

  1. M

    SOLVED No Call detail or recordings in GUI after update

    FreeSWITCH first writes a call detail record to the file system. FusionPBX then reads it using the cron job or service and loads it into the database. So use crontab to disable that service then make a phone call. If you make a call then you don't see a call detail record written to the file...
  2. M

    SOLVED No Call detail or recordings in GUI after update

    Check if you see call detail record XML files in this directory.
  3. M

    SOLVED No Call detail or recordings in GUI after update

    First off make sure you upgrade schema or upgrade.php. Then use this link to enable CDR - https://www.pbxforums.com/threads/crd-logs-and-recordings-not-showing-in-portal.8078/post-32553
  4. M

    Possible bug in call block: call block doesn't block calls the first time you add a rule unless you reload/rescan

    The Number One Reason the call block doesn't work is to fill in the Caller ID Name as if it is a description. Most of the time the description is better off left blank. I will test to see if it clears the cache after enabling it the first time.
  5. M

    Possible bug in call block: call block doesn't block calls the first time you add a rule unless you reload/rescan

    The first entry in the call block enables the call_block dialplan for the current domain. After that its enabled for all future new entries for that domain.
  6. M

    Possible bug in call block: call block doesn't block calls the first time you add a rule unless you reload/rescan

    FusionPBX 5.2.4 is not the current release. The latest release is 5.3.x.
  7. M

    Bug deleting entries from dialplan FPBX v5.2.4

    FusionPBX 5.3 is the current FusionPBX release. I just confirmed that this is not a problem on 5.3. This bug was fixed several months ago. The dialplan XML is deleted when the dialplan detail is deleted. I remember fixing this bug it was several months ago. It's a good thing 5.3 was released...
  8. M

    Bug deleting entries from dialplan FPBX v5.2.4

    If you press save again it will read the current dialplan settings and remove the line from the XML.
  9. M

    SOLVED IVR an time condition

    Hour of day doesn't work intuitively. When it's set to 9-4 it means all of 9 up to all of 4 until it's not 4 anymore(so it means 9-5). This is how FreeSWITCH looks at the hours.
  10. M

    Voicemail in 5.3 only shows the length and size on the first line.

    Sorry, this one is a bug I'll get it fixed soon.
  11. M

    FusionPBX IP Authentication

    You need to add your VoIP provider IP addresses to the Access Control list. If you are running a new version of FusionPBX then this would be the providers access control list. For those using an old outdated version, it is called domains access control list.
  12. M

    SOLVED IVR an time condition

    Ensure you set the time_zone variable in default settings to the correct time zone. You might want to send your call to the time condition extension first. Then send it to the open IVR and the closed IVR Menus or other desired destination.
  13. M

    Block Branch 5.3 - Master

    If you run this command It will tell you what branch you are on. If it indicates you are on 5.3, you are already on the right branch. If it says 5.2 or master then run the following.
  14. M

    Block Branch 5.3 - Master

    The FusionPBX official install script puts you on the 5.3 release branch. - https://github.com/fusionpbx/fusionpbx-install.sh/blob/master/debian/resources/config.sh If you update the Source Code from the web interface in Advanced -> Upgrade you will only get bug and security fixes from the...
  15. M

    Using default setting variables

    You want to use default settings in category: provision if you have a setting as yealink_480x272_wallpaper then in the provisioning template if you look around for a variable you will see the syntax looks like this. {$yealink_480x272_wallpaper} The template engine uses PHP Smarty so it requires...
  16. M

    Crd logs and recordings not showing in portal

    I'm interpreting the problem as the Call Detail Records are not loading into the database. Call Recording depends on the same table in Call Detail Records. So this would affect both features. If this is an upgrade go into your /etc/freeswitch/autoload_configs/xml_cdr.conf.xml. Update it to...
  17. M

    Variables are not being saved

    Advanced -> Variables is save to vars.xml file in /etc/freeswitch
  18. M

    Replicating the switch database between two nodes

    It seems alright mostly but make sure to keep PostgreSQL running for continued replication. And the config files don't change much so there the benefit on changing then depends on how much you change the configs. By default they aren't changed much. Most of FusionPBX is dynamically sending...
  19. M

    Fresh install - FreeSwitch not starting correctly

    SQLITE "busy" messages this is how SQLite works by default. When there is a write it locks the file writes the changes and unlocks the file. If something else tries to write to it while it is locked FreeSWITCH will log SQLite "busy" and say 299 this means it was busy one time. From there it...
  20. M

    Replicating the switch database between two nodes

    There is a file cache in /var/cache/fusionpbx. To be efficient, this is not cleared by default. It's cleared when it's changed locally. You can do many things with this, including replicate it or delete it when it's older than a certain amount of time.