[Freeswitch-dev] FXS bridged on FXO ports and DTMF

devel at thom.fr.eu.org devel at thom.fr.eu.org
Wed Jun 2 13:19:15 PDT 2010

I just updated to 3.5.11 and the result is the same.


De : freeswitch-dev-bounces at lists.freeswitch.org [mailto:freeswitch-dev-bounces at lists.freeswitch.org] De la part de Moises Silva
Envoyé : mercredi 2 juin 2010 21:35
À : freeswitch-dev at lists.freeswitch.org
Objet : Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF


I believe the problem was that the driver enabled even outgoing DTMF detection on the chip  ( which does not make much sense by default since you only care about incoming ) and was fixed a few months ago

Do you still see this behavior? which driver version?

Moises Silva
Senior Software Engineer
Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R 9T3 Canada
t. 1 905 474 1990 x 128 | e. moy at sangoma.com

On Wed, Jun 2, 2010 at 3:22 PM, <devel at thom.fr.eu.org> wrote:

I come back on this topic as I did not find a clean/good solution to this problem.


As reminder, the problem occurs when an FXS channel is bridged on an FXO channel (seen with sangoma A400 hardware with HW DTMF detection).

The problem is that each leg of the bridge is detecting the inband DTMF, and so freeswitch sends each detected DTMF from one leg to the other, and so on and so forth (as each leg detects the DTMF again and again).


I guess what would be needed for these cases is some application that would prevent detected DTMF to be sent to the other leg.


Can anybody give me a hint on whether or not such application exists, and if not, a starting point to try to create one.






FreeSWITCH-dev mailing list
FreeSWITCH-dev at lists.freeswitch.org


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-dev/attachments/20100602/0b4a729f/attachment.html 

More information about the FreeSWITCH-dev mailing list