<div dir="ltr">I forgot to mention that I'm using the intercept application and that currently the DTMF event is received by both channels when inside a bridge.<br><br><br><div class="gmail_quote">On Mon, Aug 11, 2008 at 1:36 PM, Juan Jose Comellas <span dir="ltr"><<a href="mailto:juanjo@comellas.org">juanjo@comellas.org</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 currently have the need to know which channel originated a DTMF event when inside a bridge. I'm monitoring events through mod_event_socket. The problem is that, as far as I can see, the originating channel ID is never carried with the DTMF event. Is there any reason for this?<br>
<br>I've been looking for ways to modify FreeSWITCH to support this and I wanted to discuss it with the core developers to make sure that whatever modification I make is acceptable to be merged back into FS. The options I'm contemplating right now are:<br>
<br>1. Add the originating channel ID to the switch_dtmf_t struct. Pros: don't need to change the interfaces in any of the functions that are used to send DTMFs; cons: this change would make the struct almost 8x bigger than what it currently is.<br>
<br>2. Change switch_core_session_send_dtmf() (switch_core_io.c) to receive the channel ID as an argument and have the function pass the channel ID to all the event hooks when they are called.<br><br>Is any of these options acceptable? Does anybody have any recommendations about this?<br>
<br><br></div>
</blockquote></div><br></div>