ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    FreePBX 13 No Conference Room App

    Scheduled Pinned Locked Moved IT Discussion
    freepbxfreepbx 13voiptelephonycentos 7asteriskappmeetmeappconfbridge
    3 Posts 2 Posters 3.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • scottalanmillerS
      scottalanmiller
      last edited by

      Fresh install of FreePBX 13, following FreePBX's own instructions, and I am getting this error:

      0_1480876163029_Screenshot from 2016-12-04 13-28-41.png

      No Conference Room App : Neither app_meetme nor app_confbridge is configured in Asterisk, conferencing, paging and other functionality will not work properly.

      But app_confbridge is loaded and the FreePBX conference module is loaded too. Everything is fully up to date as well. Nothing on FreePBX's site seems to have any useful info on this.

      1 Reply Last reply Reply Quote 0
      • T
        tm1000
        last edited by

        This was happening because for some reason the conbridge.conf file (or an include therein) was not being created correctly and thus because conf files were missing confbridge was never loaded. I believe this was because conferences was not originally included in the tarball for 13 but we fixed this so it should be OK???? Not sure...

        scottalanmillerS 1 Reply Last reply Reply Quote 0
        • scottalanmillerS
          scottalanmiller @tm1000
          last edited by

          @tm1000 said in FreePBX 13 No Conference Room App:

          This was happening because for some reason the conbridge.conf file (or an include therein) was not being created correctly and thus because conf files were missing confbridge was never loaded. I believe this was because conferences was not originally included in the tarball for 13 but we fixed this so it should be OK???? Not sure...

          It was fixed this week? It was just six days ago that we saw it, but it's not been re-run since then.

          1 Reply Last reply Reply Quote 0
          • 1 / 1
          • First post
            Last post