<div dir="ltr"><br><br><div class="gmail_quote">On Tue, Oct 7, 2008 at 5:44 PM, jonathan augenstine <span dir="ltr"><<a href="mailto:jaugenstine@gmail.com">jaugenstine@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div dir="ltr">I have a question about the MeetMe module. I am doing some work for a
company that is related to the music on hold capability within
Asterisk. The requirement is that each caller who is placed into the
MOH have a unique connection and that will respond to DTMF entries.
Testing and code review reveals that the conferencing is not
interactive and is the same experience for all callers. I am
investigating the possibility of creating a module that would branch
from the app_meetme.c and support each caller having a unique MOH
connection that supports DTMF. My question is this - was the decision
to implement MOH on this module because of difficulties in implementing
a connection per caller or because of the expediency and resource
saving factor of only having one MOH connection for the entire
conference?<br><br>Jonathan<br><br></div><br></blockquote></div><br>Try pressing * while you are in a meetme, that may enlighten you to track down relevant code. (more specifically, the 's' option)<br clear="all">
<br>-- <br>Thanks,<br>Steve Totaro <br>+18887771888 (Toll Free)<br>+12409381212 (Cell)<br>+12024369784 (Skype)<br>
</div>