Details

    • Backend Engine:
      Asterisk 1.4.x
    • Backend Ver:
      1.4.37
    • Confirmation:
      Unreviewed

      Description

      I have these options set:
      leader wait: no
      Talker Opt yes
      Talker Detect yes
      Quiet mode no
      User count yes
      user join/leave yes
      MOH yes

      But after someone enters the user pin, it never asks them to record their name.

      I am using 2.8.1.4, and conference module 2.8.0.3

        Activity

        Hide
        mickecarlsson added a comment -

        Thank you mustardman for the feedback.

        To sum up this ticket, make sure to install dahdi complete http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete/dahdi-linux-complete-current.tar.gz for conferences to work.

        Show
        mickecarlsson added a comment - Thank you mustardman for the feedback. To sum up this ticket, make sure to install dahdi complete http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete/dahdi-linux-complete-current.tar.gz for conferences to work.
        Hide
        totalimpact added a comment -

        I definitely have dahdi-complete installed,

        root@pbx1:~ $ /etc/init.d/dahdi start
        Loading DAHDI hardware modules:
          dahdi_dummy:                                             [  OK  ]
        No hardware timing source found in /proc/dahdi, loading dahdi_dummy
        Running dahdi_cfg:                                         [  OK  ]
        

        although I get the feeling this is "out of freepbx's hands".

         
        [Jun 14 00:21:53] VERBOSE[6098] app_meetme.c:     -- Created MeetMe conference 1023 for conference '500'
        [Jun 14 00:21:53] WARNING[6098] app_meetme.c: No DAHDI channel available for conference, user introduction disabled (is chan_dahdi loaded?)
        

        After doing some bumbling on the asterisk.org forums, I have come up with this
        - digium dev has simply pulled the rug out from under us
        - https://issues.asterisk.org/view.php?id=17959 says that the core of dahdi supposedly handles all timing, and dahdi_dummy has been removed, the documentation backs this up
        - https://wiki.asterisk.org/wiki/display/AST/Timing+Interfaces
        BUT at the bottom it gives an entirely contradicting disclaimer that meetme is definitely dependant on dahdi_dummy.

        The thing that utterly drives me mad
        - I have this running on VZ containers and Xen also, and both have meetme that does work, and that does NOT work (meaning lacking dahdi_dummy/pseudo in asterisk), using asterisk 1.8.4, and 1.4.3x
        - and nobody can point me to what in the config or loaded modules makes this actually work or break.

        Show
        totalimpact added a comment - I definitely have dahdi-complete installed, root@pbx1:~ $ /etc/init.d/dahdi start Loading DAHDI hardware modules: dahdi_dummy: [ OK ] No hardware timing source found in /proc/dahdi, loading dahdi_dummy Running dahdi_cfg: [ OK ] although I get the feeling this is "out of freepbx's hands".   [Jun 14 00:21:53] VERBOSE[6098] app_meetme.c: -- Created MeetMe conference 1023 for conference '500' [Jun 14 00:21:53] WARNING[6098] app_meetme.c: No DAHDI channel available for conference, user introduction disabled (is chan_dahdi loaded?) After doing some bumbling on the asterisk.org forums, I have come up with this - digium dev has simply pulled the rug out from under us - https://issues.asterisk.org/view.php?id=17959 says that the core of dahdi supposedly handles all timing, and dahdi_dummy has been removed, the documentation backs this up - https://wiki.asterisk.org/wiki/display/AST/Timing+Interfaces BUT at the bottom it gives an entirely contradicting disclaimer that meetme is definitely dependant on dahdi_dummy. The thing that utterly drives me mad - I have this running on VZ containers and Xen also, and both have meetme that does work, and that does NOT work (meaning lacking dahdi_dummy/pseudo in asterisk), using asterisk 1.8.4, and 1.4.3x - and nobody can point me to what in the config or loaded modules makes this actually work or break.
        Hide
        totalimpact added a comment -

        mustardman
        - i looked into your idea, libtonezone.so is just 1 of many files required by dahdi, I compile dahdi-linux-complete on both the host and even the guest with mods for openvz, something like this:
        http://www.elastix.org/en/component/kunena/25-newbies-corner-/57615-elastix-20-and-openvz--proxmox-template.html

        Show
        totalimpact added a comment - mustardman - i looked into your idea, libtonezone.so is just 1 of many files required by dahdi, I compile dahdi-linux-complete on both the host and even the guest with mods for openvz, something like this: http://www.elastix.org/en/component/kunena/25-newbies-corner-/57615-elastix-20-and-openvz--proxmox-template.html
        Hide
        Mustard Man (Inactive) added a comment -

        Replying to [totalimpact|comment:9]:
        > mustardman
        - i looked into your idea, libtonezone.so is just 1 of many files required by dahdi, I compile dahdi-linux-complete on both the host and even the guest with mods for openvz, something like this:
        > http://www.elastix.org/en/component/kunena/25-newbies-corner-/57615-elastix-20-and-openvz--proxmox-template.html

        Yes, you have to do that as well. So basically, you have to have dahdi-complete installed on the physical server, and you also have to install it on the OpenVZ virtual server (after you install the ovzkernel and ovzkernel-devel dependencies). And you have map the /dev as per that elastix link.

        My method of just copying the required files over to the OpenVZ virtual server so chan_dandi and meetme compiles is better imho because you do not have to install ovzkernel which is totally unnecessary and a bit of a hassle on an openVZ virtual server.

        Show
        Mustard Man (Inactive) added a comment - Replying to [totalimpact|comment:9] : > mustardman - i looked into your idea, libtonezone.so is just 1 of many files required by dahdi, I compile dahdi-linux-complete on both the host and even the guest with mods for openvz, something like this: > http://www.elastix.org/en/component/kunena/25-newbies-corner-/57615-elastix-20-and-openvz--proxmox-template.html Yes, you have to do that as well. So basically, you have to have dahdi-complete installed on the physical server, and you also have to install it on the OpenVZ virtual server (after you install the ovzkernel and ovzkernel-devel dependencies). And you have map the /dev as per that elastix link. My method of just copying the required files over to the OpenVZ virtual server so chan_dandi and meetme compiles is better imho because you do not have to install ovzkernel which is totally unnecessary and a bit of a hassle on an openVZ virtual server.
        Hide
        mickecarlsson added a comment -

        Please guys, continue this discussion in the forum. Ticket is closed due to configuration error. Respect that. Thank you.

        Show
        mickecarlsson added a comment - Please guys, continue this discussion in the forum. Ticket is closed due to configuration error. Respect that. Thank you.

          People

          • Assignee:
            Unassigned
            Reporter:
            totalimpact
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development