Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF - Deja Vu
The tone on/off conditions should be, minimum on 40ms and 50ms off. I recommend you to record a call with those double digit detections. If you can reproduce them yourself by dialing quickly it'd be even better. Once you have the recording you can run libteletone on the recorded audio (see libs/freetdm/src/detect_dtmf.c) and may be start tweaking it. You could also run spandsp dtmf detector over the recorded audio to see if does a better job (I'd think so). Another way to test if spandsp does better is to disable dtmf detection completely from freetdm (the disable_dtmf dial plan app does that) and then use spandsp_start_dtmf application on the dialplan (see mod_spandsp). I'd be interested in looking at the recording too, you can send it to my email if you want me to take a look. You can record all the read/write audio using: ftmod trace /path/prefix [] That starts recording all incoming and outgoing data on the channel (if no channel is specified all channels on the span are recorded), the specified prefix will be used for each of the files. The recording starts immediately (although if there is no call then most likely no one is reading/writing to the channel), you must stop the recording when done with: ftmod notrace [] 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. [email protected] On Sat, Jul 3, 2010 at 4:22 AM, Jeroen C. van Gelderen wrote: > > > If however you have this issue even with HW EC, > >call Sangoma tech support and we will be happy to look at the issue. > > I wish this was Sangoma hardware esp. with hardware ec :) > > My DTMF "bouncing" issues were indeed caused by echo but now that I've got > OSLEC running (thanks for patching that) calls are echo-free and crystal > clear. > > The issue now is that my users dial their transfers (-say- #44) reasonably > fast and that often causes two successive DTMF digits to be detected as one > (#4). > > In order to reliably reach the extension the clerk cannot dial more than > one > digit per second. That seems excessively slow. I suspect there must be a > knob somewhere to tune that (in libteletone)? Other causes to look for? > > Cheers, > -Slim > > > ___ > FreeSWITCH-dev mailing list > [email protected] > http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev > http://www.freeswitch.org > ___ FreeSWITCH-dev mailing list [email protected] http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF - Deja Vu
> If however you have this issue even with HW EC, >call Sangoma tech support and we will be happy to look at the issue. I wish this was Sangoma hardware esp. with hardware ec :) My DTMF "bouncing" issues were indeed caused by echo but now that I've got OSLEC running (thanks for patching that) calls are echo-free and crystal clear. The issue now is that my users dial their transfers (-say- #44) reasonably fast and that often causes two successive DTMF digits to be detected as one (#4). In order to reliably reach the extension the clerk cannot dial more than one digit per second. That seems excessively slow. I suspect there must be a knob somewhere to tune that (in libteletone)? Other causes to look for? Cheers, -Slim ___ FreeSWITCH-dev mailing list [email protected] http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF - Deja Vu
Hi, You can try the EC in speech recognition mode. By default, the ec is in normal mode. But you can set it to speech recognition mode with this: # wan_ec_client wanpipe1 msr msr = mode speech recognition Then verify the channel has the required mode: # wan_ec_client wanpipe1 stats You can take it back to normal mode (IIRC) with: # wan_ec_client wanpipe1 mn In any case I am interested in your problem with the ec in normal mode. I need to check with the driver developer to see if something changed in the ec settings. Please let me know if speech recognition mode helps. 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. [email protected] On Thu, Jul 1, 2010 at 1:46 PM, François Legal wrote: > Yes, CID works back again with HWEC disabled. However, I get echo without > HWEC ;-) > > > > François > > > > On Wed, 30 Jun 2010 18:48:40 -0400, Moises Silva > wrote: > > Just fyi, you can disable hw ec from the CLI so you don't have to > start/stop the port for your tests. Start the card with HWEC enabled, then > you can use wan_ec_client. > # wan_ec_client wanpipe1 disable > Then enable again: > # wan_ec_client wanpipe1 enable > You can verify it's enabled/disabled with > # wan_ec_client wanpipe stats > > 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. [email protected] > > > On Wed, Jun 30, 2010 at 6:29 PM, wrote: > >> I’ll give a try tomorrow with HWEC disabled. >> >> >> >> *De :* [email protected] [mailto: >> [email protected]] *De la part de* Moises Silva >> *Envoyé :* mercredi 30 juin 2010 23:15 >> *À :* [email protected] >> *Objet :* Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF - Deja >> Vu >> >> >> >> Can you try 3.5.12 with and without hw ec enabled and check if cid is >> there? >> >> >> 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. [email protected] >> >> On Wed, Jun 30, 2010 at 2:58 PM, François Legal >> wrote: >> >> Hello, >> >> >> >> did try to upgrade to wanpipe 3.5.12 (from 3.5.11) and thought the DTMF >> problem seems to be fixed (did not had the opportunity to really test it >> thourougthly), I seem to have lost the CID feature in the upgrade. >> >> Roll back to 3.5.11 and CID is back there. >> >> >> >> François >> >> >> >> >> >> On Mon, 28 Jun 2010 18:54:19 -0400, Moises Silva wrote: >> >> Hello, >> >> I spent a few hours playing with DTMF stuff and analog cards and it seems >> there is 2 issues at hand. >> >> 1. Bleeding DTMF. >> 2. Echo DTMF. >> >> The first issue, for software DTMF, can be solved with Anthony's pre >> buffer size feature. However that introduces delay by design, and it will >> not work for large DTMFs (if the dtmf is larger than the buffer). >> >> For hardware DTMF a new driver was just released that includes a >> configuration to allow the EC chip to perform the dtmf tone removal which >> cuts down the bleeding to only 20ms (in my testing) there is no way a DTMF >> detector will consider that a valid DTMF and therefore the bleeding should >> be solved with no delay introduced. The option is HWEC_DTMF_REMOVAL = YES, >> must be added along with the usual TDMV_HW_DTMF = YES in wanpipex.conf >> >> Ideally the software DTMF detector (in this case teletone) should cut it >> at the same time that it detects it. I thought may be spandsp would help, >> but it seems spandsp does not have an option to squelch the dtmf tone. May >> be Steve can help with that. I pinged him on IRC and he said he may get some >> code working, but there is no date for that and also that would involve >> integrating spandsp into FreeTDM, any reason to not do this now that spandsp >> is LGPL? >> >> As for the echo dtmf. It seems sometimes an outgoing DTMF may be detected >> as incoming DTMF due to echo. There is not much we can do there if you don't >> have echo cancellation. If however you have this issue even with HW EC, call >> Sangoma tech support and we will be happy to look at the issue. >> >> In another note, I added a variable and application to disable DTMF. >> >> >> That will disa
Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF - Deja Vu
Yes, CID works back again with HWEC disabled. However, I get echo without HWEC ;-) François On Wed, 30 Jun 2010 18:48:40 -0400, Moises Silva wrote: Just fyi, you can disable hw ec from the CLI so you don't have to start/stop the port for your tests. Start the card with HWEC enabled, then you can use wan_ec_client. # wan_ec_client wanpipe1 disable Then enable again: # wan_ec_client wanpipe1 enable You can verify it's enabled/disabled with # wan_ec_client wanpipe stats 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. [email protected] [1] On Wed, Jun 30, 2010 at 6:29 PM, wrote: I'll give a try tomorrow with HWEC disabled. DE : [email protected] [3] [mailto:[email protected] [4]] DE LA PART DE Moises Silva ENVOYÉ : mercredi 30 juin 2010 23:15 À : [email protected] [5] OBJET : Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF - Deja Vu Can you try 3.5.12 with and without hw ec enabled and check if cid is there? 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. [email protected] [6] On Wed, Jun 30, 2010 at 2:58 PM, François Legal wrote: Hello, did try to upgrade to wanpipe 3.5.12 (from 3.5.11) and thought the DTMF problem seems to be fixed (did not had the opportunity to really test it thourougthly), I seem to have lost the CID feature in the upgrade. Roll back to 3.5.11 and CID is back there. François On Mon, 28 Jun 2010 18:54:19 -0400, Moises Silva wrote: Hello, I spent a few hours playing with DTMF stuff and analog cards and it seems there is 2 issues at hand. 1. Bleeding DTMF. 2. Echo DTMF. The first issue, for software DTMF, can be solved with Anthony's pre buffer size feature. However that introduces delay by design, and it will not work for large DTMFs (if the dtmf is larger than the buffer). For hardware DTMF a new driver was just released that includes a configuration to allow the EC chip to perform the dtmf tone removal which cuts down the bleeding to only 20ms (in my testing) there is no way a DTMF detector will consider that a valid DTMF and therefore the bleeding should be solved with no delay introduced. The option is HWEC_DTMF_REMOVAL = YES, must be added along with the usual TDMV_HW_DTMF = YES in wanpipex.conf Ideally the software DTMF detector (in this case teletone) should cut it at the same time that it detects it. I thought may be spandsp would help, but it seems spandsp does not have an option to squelch the dtmf tone. May be Steve can help with that. I pinged him on IRC and he said he may get some code working, but there is no date for that and also that would involve integrating spandsp into FreeTDM, any reason to not do this now that spandsp is LGPL? As for the echo dtmf. It seems sometimes an outgoing DTMF may be detected as incoming DTMF due to echo. There is not much we can do there if you don't have echo cancellation. If however you have this issue even with HW EC, call Sangoma tech support and we will be happy to look at the issue. In another note, I added a variable and application to disable DTMF. That will disable DTMF (either software or hardware) in the leg executing that app. If you want to disable in the outgoing leg (before a bridge), you must export a special variable: The DTMF is enabled automatically on each call, so there is no need to enable it for each call. But in case you need to enable it: 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. [email protected] [8] On Wed, Jun 16, 2010 at 12:09 PM, Anthony Minessale wrote: openzap_pre_buffer_size is a variable you can set to specific number of MS 60 for example. it will pre_buffer the audio on the channel so when you detect dtmf it will completely drop the buffer so all of the original dtmf should be dropped as well. probably if the dtmf is too long then it will cause problems anyway. if that pre buffer does not fix anything it would point to echo or bleeding. We could make a variable to disable dtmf detection completely on a per-call basis possibly but you will still probably hear it bleeding. This type of problem was reported fixed with sangoma because of the echo canceler. I don't use dahdi or digium stuff much so I can't comment on what happens when you use it. On Wed, Jun 16, 2010 at 3:41 AM, François Legal wrote: Does this really fix it ? I wonder because the problem I see here is also that the FXS side detects the DTMF and then queues it on the FXO side for generation. That leads to the called party receiving twice the DTMF, the first one is the inband DTMF, the second is the one queued/generate
Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF - Deja Vu
Just fyi, you can disable hw ec from the CLI so you don't have to start/stop the port for your tests. Start the card with HWEC enabled, then you can use wan_ec_client. # wan_ec_client wanpipe1 disable Then enable again: # wan_ec_client wanpipe1 enable You can verify it's enabled/disabled with # wan_ec_client wanpipe stats 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. [email protected] On Wed, Jun 30, 2010 at 6:29 PM, wrote: > I’ll give a try tomorrow with HWEC disabled. > > > > *De :* [email protected] [mailto: > [email protected]] *De la part de* Moises Silva > *Envoyé :* mercredi 30 juin 2010 23:15 > *À :* [email protected] > *Objet :* Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF - Deja Vu > > > > Can you try 3.5.12 with and without hw ec enabled and check if cid is > there? > > > 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. [email protected] > > On Wed, Jun 30, 2010 at 2:58 PM, François Legal > wrote: > > Hello, > > > > did try to upgrade to wanpipe 3.5.12 (from 3.5.11) and thought the DTMF > problem seems to be fixed (did not had the opportunity to really test it > thourougthly), I seem to have lost the CID feature in the upgrade. > > Roll back to 3.5.11 and CID is back there. > > > > François > > > > > > On Mon, 28 Jun 2010 18:54:19 -0400, Moises Silva wrote: > > Hello, > > I spent a few hours playing with DTMF stuff and analog cards and it seems > there is 2 issues at hand. > > 1. Bleeding DTMF. > 2. Echo DTMF. > > The first issue, for software DTMF, can be solved with Anthony's pre buffer > size feature. However that introduces delay by design, and it will not work > for large DTMFs (if the dtmf is larger than the buffer). > > For hardware DTMF a new driver was just released that includes a > configuration to allow the EC chip to perform the dtmf tone removal which > cuts down the bleeding to only 20ms (in my testing) there is no way a DTMF > detector will consider that a valid DTMF and therefore the bleeding should > be solved with no delay introduced. The option is HWEC_DTMF_REMOVAL = YES, > must be added along with the usual TDMV_HW_DTMF = YES in wanpipex.conf > > Ideally the software DTMF detector (in this case teletone) should cut it at > the same time that it detects it. I thought may be spandsp would help, but > it seems spandsp does not have an option to squelch the dtmf tone. May be > Steve can help with that. I pinged him on IRC and he said he may get some > code working, but there is no date for that and also that would involve > integrating spandsp into FreeTDM, any reason to not do this now that spandsp > is LGPL? > > As for the echo dtmf. It seems sometimes an outgoing DTMF may be detected > as incoming DTMF due to echo. There is not much we can do there if you don't > have echo cancellation. If however you have this issue even with HW EC, call > Sangoma tech support and we will be happy to look at the issue. > > In another note, I added a variable and application to disable DTMF. > > > That will disable DTMF (either software or hardware) in the leg > executing that app. If you want to disable in the outgoing leg (before a > bridge), you must export a special variable: > > > The DTMF is enabled automatically on each call, so there is no need to > enable it for each call. But in case you need to enable it: > > > 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. [email protected] > >On Wed, Jun 16, 2010 at 12:09 PM, Anthony Minessale < > [email protected]> wrote: > > openzap_pre_buffer_size is a variable you can set to specific number of MS > 60 for example. > > it will pre_buffer the audio on the channel so when you detect dtmf it will > completely drop the buffer so all of the original > > dtmf should be dropped as well. probably if the dtmf is too long then it > will cause problems anyway. > > if that pre buffer does not fix anything it would point to echo or > bleeding. > > We could make a variable to disable dtmf detection completely on a per-call > basis possibly but you will still probably hear it bleeding. > > This type of problem was reported fixed with sangoma because of the > echo canceler. > > I don't use dahdi or digium stuff much so I can't comment on what h
Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF - Deja Vu
I’ll give a try tomorrow with HWEC disabled. De : [email protected] [mailto:[email protected]] De la part de Moises Silva Envoyé : mercredi 30 juin 2010 23:15 À : [email protected] Objet : Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF - Deja Vu Can you try 3.5.12 with and without hw ec enabled and check if cid is there? 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. [email protected] On Wed, Jun 30, 2010 at 2:58 PM, François Legal wrote: Hello, did try to upgrade to wanpipe 3.5.12 (from 3.5.11) and thought the DTMF problem seems to be fixed (did not had the opportunity to really test it thourougthly), I seem to have lost the CID feature in the upgrade. Roll back to 3.5.11 and CID is back there. François On Mon, 28 Jun 2010 18:54:19 -0400, Moises Silva wrote: Hello, I spent a few hours playing with DTMF stuff and analog cards and it seems there is 2 issues at hand. 1. Bleeding DTMF. 2. Echo DTMF. The first issue, for software DTMF, can be solved with Anthony's pre buffer size feature. However that introduces delay by design, and it will not work for large DTMFs (if the dtmf is larger than the buffer). For hardware DTMF a new driver was just released that includes a configuration to allow the EC chip to perform the dtmf tone removal which cuts down the bleeding to only 20ms (in my testing) there is no way a DTMF detector will consider that a valid DTMF and therefore the bleeding should be solved with no delay introduced. The option is HWEC_DTMF_REMOVAL = YES, must be added along with the usual TDMV_HW_DTMF = YES in wanpipex.conf Ideally the software DTMF detector (in this case teletone) should cut it at the same time that it detects it. I thought may be spandsp would help, but it seems spandsp does not have an option to squelch the dtmf tone. May be Steve can help with that. I pinged him on IRC and he said he may get some code working, but there is no date for that and also that would involve integrating spandsp into FreeTDM, any reason to not do this now that spandsp is LGPL? As for the echo dtmf. It seems sometimes an outgoing DTMF may be detected as incoming DTMF due to echo. There is not much we can do there if you don't have echo cancellation. If however you have this issue even with HW EC, call Sangoma tech support and we will be happy to look at the issue. In another note, I added a variable and application to disable DTMF. That will disable DTMF (either software or hardware) in the leg executing that app. If you want to disable in the outgoing leg (before a bridge), you must export a special variable: The DTMF is enabled automatically on each call, so there is no need to enable it for each call. But in case you need to enable it: 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. [email protected] On Wed, Jun 16, 2010 at 12:09 PM, Anthony Minessale wrote: openzap_pre_buffer_size is a variable you can set to specific number of MS 60 for example. it will pre_buffer the audio on the channel so when you detect dtmf it will completely drop the buffer so all of the original dtmf should be dropped as well. probably if the dtmf is too long then it will cause problems anyway. if that pre buffer does not fix anything it would point to echo or bleeding. We could make a variable to disable dtmf detection completely on a per-call basis possibly but you will still probably hear it bleeding. This type of problem was reported fixed with sangoma because of the echo canceler. I don't use dahdi or digium stuff much so I can't comment on what happens when you use it. On Wed, Jun 16, 2010 at 3:41 AM, François Legal wrote: Does this really fix it ? I wonder because the problem I see here is also that the FXS side detects the DTMF and then queues it on the FXO side for generation. That leads to the called party receiving twice the DTMF, the first one is the inband DTMF, the second is the one queued/generated by the FXO channel. For a clean fix, I guess some kind of application should be created, that would prevent DTMF to be queued on the other channel. Such application would then be called before the bridge. Maybe there is a cleaner way to do this. François On Tue, 15 Jun 2010 18:23:13 -0500, "Jeroen C. van Gelderen" wrote: > Hi everybody, > > I have a problem that is very similar to a problem > reported by François [1] except for the fact that > my FXS and FXO ports are on a Xorcom Astribank > device instead of a Sangoma. > > To quote François: "The problem is that each leg of > the bridge is detecting the inband DTMF, and so > [F]reeswitch sends each detected DTMF
Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF - Deja Vu
Can you try 3.5.12 with and without hw ec enabled and check if cid is there? 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. [email protected] On Wed, Jun 30, 2010 at 2:58 PM, François Legal wrote: > Hello, > > > > did try to upgrade to wanpipe 3.5.12 (from 3.5.11) and thought the DTMF > problem seems to be fixed (did not had the opportunity to really test it > thourougthly), I seem to have lost the CID feature in the upgrade. > > Roll back to 3.5.11 and CID is back there. > > > > François > > > > > > On Mon, 28 Jun 2010 18:54:19 -0400, Moises Silva wrote: > > Hello, > > I spent a few hours playing with DTMF stuff and analog cards and it seems > there is 2 issues at hand. > > 1. Bleeding DTMF. > 2. Echo DTMF. > > The first issue, for software DTMF, can be solved with Anthony's pre buffer > size feature. However that introduces delay by design, and it will not work > for large DTMFs (if the dtmf is larger than the buffer). > > For hardware DTMF a new driver was just released that includes a > configuration to allow the EC chip to perform the dtmf tone removal which > cuts down the bleeding to only 20ms (in my testing) there is no way a DTMF > detector will consider that a valid DTMF and therefore the bleeding should > be solved with no delay introduced. The option is HWEC_DTMF_REMOVAL = YES, > must be added along with the usual TDMV_HW_DTMF = YES in wanpipex.conf > > Ideally the software DTMF detector (in this case teletone) should cut it at > the same time that it detects it. I thought may be spandsp would help, but > it seems spandsp does not have an option to squelch the dtmf tone. May be > Steve can help with that. I pinged him on IRC and he said he may get some > code working, but there is no date for that and also that would involve > integrating spandsp into FreeTDM, any reason to not do this now that spandsp > is LGPL? > > As for the echo dtmf. It seems sometimes an outgoing DTMF may be detected > as incoming DTMF due to echo. There is not much we can do there if you don't > have echo cancellation. If however you have this issue even with HW EC, call > Sangoma tech support and we will be happy to look at the issue. > > In another note, I added a variable and application to disable DTMF. > > > > That will disable DTMF (either software or hardware) in the leg executing > that app. If you want to disable in the outgoing leg (before a bridge), you > must export a special variable: > > > > The DTMF is enabled automatically on each call, so there is no need to > enable it for each call. But in case you need to enable it: > > > > 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. [email protected] > > > On Wed, Jun 16, 2010 at 12:09 PM, Anthony Minessale < > [email protected]> wrote: > >> openzap_pre_buffer_size is a variable you can set to specific number of MS >> 60 for example. >> it will pre_buffer the audio on the channel so when you detect dtmf it >> will completely drop the buffer so all of the original >> dtmf should be dropped as well. probably if the dtmf is too long then it >> will cause problems anyway. >> if that pre buffer does not fix anything it would point to echo or >> bleeding. >> We could make a variable to disable dtmf detection completely on a >> per-call basis possibly but you will still probably hear it bleeding. >> This type of problem was reported fixed with sangoma because of the >> echo canceler. >> I don't use dahdi or digium stuff much so I can't comment on what happens >> when you use it. >> >> >> >> On Wed, Jun 16, 2010 at 3:41 AM, François Legal wrote: >> >>> Does this really fix it ? >>> I wonder because the problem I see here is also that the FXS side detects >>> the DTMF and then queues it on the FXO side for generation. That leads to >>> the called party receiving twice the DTMF, the first one is the inband >>> DTMF, the second is the one queued/generated by the FXO channel. >>> >>> For a clean fix, I guess some kind of application should be created, that >>> would prevent DTMF to be queued on the other channel. Such application >>> would then be called before the bridge. Maybe there is a cleaner way to >>> do >>> this. >>> >>> François >>> >>> On Tue, 15 Jun 2010 18:23:13 -0500, "Jeroen C. van Gelderen" >>> wrote: >>> > Hi everybody, >>> > >>> > I have a problem that is very similar to a problem >>> > reported by François [1] except for the fact that >>> > my FXS and FXO ports are on a Xorcom Astribank >>> > device instead of a Sangoma. >>> > >>> > To quote François: "The problem is that each leg of >>> > the bridge is detecting the inband DTMF, and so >>> > [F]reeswitch 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)" >>> > >>> > HIS words but evidenced by the MY
Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF - Deja Vu
Hello, did try to upgrade to wanpipe 3.5.12 (from 3.5.11) and thought the DTMF problem seems to be fixed (did not had the opportunity to really test it thourougthly), I seem to have lost the CID feature in the upgrade. Roll back to 3.5.11 and CID is back there. François On Mon, 28 Jun 2010 18:54:19 -0400, Moises Silva wrote: Hello, I spent a few hours playing with DTMF stuff and analog cards and it seems there is 2 issues at hand. 1. Bleeding DTMF. 2. Echo DTMF. The first issue, for software DTMF, can be solved with Anthony's pre buffer size feature. However that introduces delay by design, and it will not work for large DTMFs (if the dtmf is larger than the buffer). For hardware DTMF a new driver was just released that includes a configuration to allow the EC chip to perform the dtmf tone removal which cuts down the bleeding to only 20ms (in my testing) there is no way a DTMF detector will consider that a valid DTMF and therefore the bleeding should be solved with no delay introduced. The option is HWEC_DTMF_REMOVAL = YES, must be added along with the usual TDMV_HW_DTMF = YES in wanpipex.conf Ideally the software DTMF detector (in this case teletone) should cut it at the same time that it detects it. I thought may be spandsp would help, but it seems spandsp does not have an option to squelch the dtmf tone. May be Steve can help with that. I pinged him on IRC and he said he may get some code working, but there is no date for that and also that would involve integrating spandsp into FreeTDM, any reason to not do this now that spandsp is LGPL? As for the echo dtmf. It seems sometimes an outgoing DTMF may be detected as incoming DTMF due to echo. There is not much we can do there if you don't have echo cancellation. If however you have this issue even with HW EC, call Sangoma tech support and we will be happy to look at the issue. In another note, I added a variable and application to disable DTMF. That will disable DTMF (either software or hardware) in the leg executing that app. If you want to disable in the outgoing leg (before a bridge), you must export a special variable: The DTMF is enabled automatically on each call, so there is no need to enable it for each call. But in case you need to enable it: 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. [email protected] [1] On Wed, Jun 16, 2010 at 12:09 PM, Anthony Minessale wrote: openzap_pre_buffer_size is a variable you can set to specific number of MS 60 for example. it will pre_buffer the audio on the channel so when you detect dtmf it will completely drop the buffer so all of the original dtmf should be dropped as well. probably if the dtmf is too long then it will cause problems anyway. if that pre buffer does not fix anything it would point to echo or bleeding. We could make a variable to disable dtmf detection completely on a per-call basis possibly but you will still probably hear it bleeding. This type of problem was reported fixed with sangoma because of the echo canceler. I don't use dahdi or digium stuff much so I can't comment on what happens when you use it. On Wed, Jun 16, 2010 at 3:41 AM, François Legal wrote: Does this really fix it ? I wonder because the problem I see here is also that the FXS side detects the DTMF and then queues it on the FXO side for generation. That leads to the called party receiving twice the DTMF, the first one is the inband DTMF, the second is the one queued/generated by the FXO channel. For a clean fix, I guess some kind of application should be created, that would prevent DTMF to be queued on the other channel. Such application would then be called before the bridge. Maybe there is a cleaner way to do this. François On Tue, 15 Jun 2010 18:23:13 -0500, "Jeroen C. van Gelderen" wrote: > Hi everybody, > > I have a problem that is very similar to a problem > reported by François [1] except for the fact that > my FXS and FXO ports are on a Xorcom Astribank > device instead of a Sangoma. > > To quote François: "The problem is that each leg of > the bridge is detecting the inband DTMF, and so > [F]reeswitch 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)" > > HIS words but evidenced by the MY log :) > > The snippet below has DTMF coming in on the FXS port > (1:1) and bouncing between it and the FXO port (3:1). > The ports are simply bridged together with > > "bridge(OpenZap/3/1/F)" or "bridge(OpenZap/3/1/w)" > > I'm running: > > FreeSWITCH version: 1.0.head (git-01c0c69 2010-06-08 16-22-21 -0500) > dahdi: Version: SVN-trunk-r8762 > > Output of lsdahdi at end of message. > > 8 2010-06-13 04:18:39.439252 [DEBUG] zap_io.c:2062 1:1 GENERATE DTMF [4] > 2010-06-13 04:18:39.637249 [DEBUG] mod_openzap.c:721 queue DTMF [4] > 2010-06-13 04:18:39.676248 [DEBUG] zap_io
Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF - Deja Vu
Hello, I spent a few hours playing with DTMF stuff and analog cards and it seems there is 2 issues at hand. 1. Bleeding DTMF. 2. Echo DTMF. The first issue, for software DTMF, can be solved with Anthony's pre buffer size feature. However that introduces delay by design, and it will not work for large DTMFs (if the dtmf is larger than the buffer). For hardware DTMF a new driver was just released that includes a configuration to allow the EC chip to perform the dtmf tone removal which cuts down the bleeding to only 20ms (in my testing) there is no way a DTMF detector will consider that a valid DTMF and therefore the bleeding should be solved with no delay introduced. The option is HWEC_DTMF_REMOVAL = YES, must be added along with the usual TDMV_HW_DTMF = YES in wanpipex.conf Ideally the software DTMF detector (in this case teletone) should cut it at the same time that it detects it. I thought may be spandsp would help, but it seems spandsp does not have an option to squelch the dtmf tone. May be Steve can help with that. I pinged him on IRC and he said he may get some code working, but there is no date for that and also that would involve integrating spandsp into FreeTDM, any reason to not do this now that spandsp is LGPL? As for the echo dtmf. It seems sometimes an outgoing DTMF may be detected as incoming DTMF due to echo. There is not much we can do there if you don't have echo cancellation. If however you have this issue even with HW EC, call Sangoma tech support and we will be happy to look at the issue. In another note, I added a variable and application to disable DTMF. That will disable DTMF (either software or hardware) in the leg executing that app. If you want to disable in the outgoing leg (before a bridge), you must export a special variable: The DTMF is enabled automatically on each call, so there is no need to enable it for each call. But in case you need to enable it: 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. [email protected] On Wed, Jun 16, 2010 at 12:09 PM, Anthony Minessale < [email protected]> wrote: > openzap_pre_buffer_size is a variable you can set to specific number of MS > 60 for example. > it will pre_buffer the audio on the channel so when you detect dtmf it will > completely drop the buffer so all of the original > dtmf should be dropped as well. probably if the dtmf is too long then it > will cause problems anyway. > > if that pre buffer does not fix anything it would point to echo or > bleeding. > > We could make a variable to disable dtmf detection completely on a per-call > basis possibly but you will still probably hear it bleeding. > > This type of problem was reported fixed with sangoma because of the > echo canceler. > I don't use dahdi or digium stuff much so I can't comment on what happens > when you use it. > > > > On Wed, Jun 16, 2010 at 3:41 AM, François Legal wrote: > >> Does this really fix it ? >> I wonder because the problem I see here is also that the FXS side detects >> the DTMF and then queues it on the FXO side for generation. That leads to >> the called party receiving twice the DTMF, the first one is the inband >> DTMF, the second is the one queued/generated by the FXO channel. >> >> For a clean fix, I guess some kind of application should be created, that >> would prevent DTMF to be queued on the other channel. Such application >> would then be called before the bridge. Maybe there is a cleaner way to do >> this. >> >> François >> >> On Tue, 15 Jun 2010 18:23:13 -0500, "Jeroen C. van Gelderen" >> wrote: >> > Hi everybody, >> > >> > I have a problem that is very similar to a problem >> > reported by François [1] except for the fact that >> > my FXS and FXO ports are on a Xorcom Astribank >> > device instead of a Sangoma. >> > >> > To quote François: "The problem is that each leg of >> > the bridge is detecting the inband DTMF, and so >> > [F]reeswitch 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)" >> > >> > HIS words but evidenced by the MY log :) >> > >> > The snippet below has DTMF coming in on the FXS port >> > (1:1) and bouncing between it and the FXO port (3:1). >> > The ports are simply bridged together with >> > >> > "bridge(OpenZap/3/1/F)" or "bridge(OpenZap/3/1/w)" >> > >> > I'm running: >> > >> > FreeSWITCH version: 1.0.head (git-01c0c69 2010-06-08 16-22-21 -0500) >> > dahdi: Version: SVN-trunk-r8762 >> > >> > Output of lsdahdi at end of message. >> > >> > 8<8<8<8<8<8<8< >> > [...] >> > 2010-06-13 04:18:39.217256 [DEBUG] mod_openzap.c:721 queue DTMF [4] >> > 2010-06-13 04:18:39.256255 [DEBUG] zap_io.c:2062 3:1 GENERATE DTMF [4] >> > 2010-06-13 04:18:39.397253 [DEBUG] mod_openzap.c:721 queue DTMF [4] >> > 2010-06-13 04:18:39.439252 [DEBUG] mod_openzap.c:780 Dropping frame! >> (write >> > not re
Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF - Deja Vu
openzap_pre_buffer_size is a variable you can set to specific number of MS
60 for example.
it will pre_buffer the audio on the channel so when you detect dtmf it will
completely drop the buffer so all of the original
dtmf should be dropped as well. probably if the dtmf is too long then it
will cause problems anyway.
if that pre buffer does not fix anything it would point to echo or bleeding.
We could make a variable to disable dtmf detection completely on a per-call
basis possibly but you will still probably hear it bleeding.
This type of problem was reported fixed with sangoma because of the
echo canceler.
I don't use dahdi or digium stuff much so I can't comment on what happens
when you use it.
On Wed, Jun 16, 2010 at 3:41 AM, François Legal wrote:
> Does this really fix it ?
> I wonder because the problem I see here is also that the FXS side detects
> the DTMF and then queues it on the FXO side for generation. That leads to
> the called party receiving twice the DTMF, the first one is the inband
> DTMF, the second is the one queued/generated by the FXO channel.
>
> For a clean fix, I guess some kind of application should be created, that
> would prevent DTMF to be queued on the other channel. Such application
> would then be called before the bridge. Maybe there is a cleaner way to do
> this.
>
> François
>
> On Tue, 15 Jun 2010 18:23:13 -0500, "Jeroen C. van Gelderen"
> wrote:
> > Hi everybody,
> >
> > I have a problem that is very similar to a problem
> > reported by François [1] except for the fact that
> > my FXS and FXO ports are on a Xorcom Astribank
> > device instead of a Sangoma.
> >
> > To quote François: "The problem is that each leg of
> > the bridge is detecting the inband DTMF, and so
> > [F]reeswitch 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)"
> >
> > HIS words but evidenced by the MY log :)
> >
> > The snippet below has DTMF coming in on the FXS port
> > (1:1) and bouncing between it and the FXO port (3:1).
> > The ports are simply bridged together with
> >
> > "bridge(OpenZap/3/1/F)" or "bridge(OpenZap/3/1/w)"
> >
> > I'm running:
> >
> > FreeSWITCH version: 1.0.head (git-01c0c69 2010-06-08 16-22-21 -0500)
> > dahdi: Version: SVN-trunk-r8762
> >
> > Output of lsdahdi at end of message.
> >
> > 8<8<8<8<8<8<8<
> > [...]
> > 2010-06-13 04:18:39.217256 [DEBUG] mod_openzap.c:721 queue DTMF [4]
> > 2010-06-13 04:18:39.256255 [DEBUG] zap_io.c:2062 3:1 GENERATE DTMF [4]
> > 2010-06-13 04:18:39.397253 [DEBUG] mod_openzap.c:721 queue DTMF [4]
> > 2010-06-13 04:18:39.439252 [DEBUG] mod_openzap.c:780 Dropping frame!
> (write
> > not ready)
> > 2010-06-13 04:18:39.439252 [DEBUG] zap_io.c:2062 1:1 GENERATE DTMF [4]
> > 2010-06-13 04:18:39.637249 [DEBUG] mod_openzap.c:721 queue DTMF [4]
> > 2010-06-13 04:18:39.676248 [DEBUG] zap_io.c:2062 3:1 GENERATE DTMF [4]
> > 2010-06-13 04:18:39.859244 [DEBUG] mod_openzap.c:780 Dropping frame!
> (write
> > not ready)
> > [...ad infinitum...]
> > 8<8<8<8<8<8<8<
> >
> > Because I needed DTMF pass-through working "now"
> > I applied an ugly HACK. This drops DTMF tones
> > detected on spans 3 and 4 (which are my FXO
> > spans). This is very WRONG but it does solve
> > my immediate problem:
> >
> > 8<8<8<8<8<8<8<
> > diff --git a/libs/openzap/mod_openzap/mod_openzap.c
> > b/libs/openzap/mod_openzap/mod_openzap.c
> > index 5aebfea..ff3b081 100644
> > --- a/libs/openzap/mod_openzap/mod_openzap.c
> > +++ b/libs/openzap/mod_openzap/mod_openzap.c
> > @@ -718,8 +718,12 @@ static switch_status_t
> > channel_read_frame(switch_core_session_t *session, switch
> > for (p = dtmf; p && *p; p++) {
> > if (is_dtmf(*p)) {
> > _dtmf.digit = *p;
> > - zap_log(ZAP_LOG_DEBUG, "queue DTMF
> [%c]\n",
> > *p);
> > - switch_channel_queue_dtmf(channel,
> &_dtmf);
> > + if (tech_pvt->zchan->span_id == 3 ||
> > tech_pvt->zchan->span_id == 4) {
> > + zap_log(ZAP_LOG_DEBUG, "Ignoring
> > DTMF [%c] on FXO port %d:%d\n", *p, tech_pvt->zchan->span_id,
> > tech_pvt->zchan->chan_id)
> > ;
> > + } else {
> > + zap_log(ZAP_LOG_DEBUG, "queue
> DTMF
> > [%c]\n", *p);
> > +
> switch_channel_queue_dtmf(channel,
> > &_dtmf);
> > + }
> > }
> > }
> > }
> > 8<8<8<8<8<8<8<
> >
> > Can someone point me in the "right" direction
> > instead? Do I need to do this at the OpenZAP/DAHDI
> > level by disabling some kind of DTMF detection
> > like was done for the Sangoma driver?
> >
> > Any and all pointers appreciated.
> >
> > Cheers,
> > -Slim
> >
> > [1] [
Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF - Deja Vu
Does this really fix it ?
I wonder because the problem I see here is also that the FXS side detects
the DTMF and then queues it on the FXO side for generation. That leads to
the called party receiving twice the DTMF, the first one is the inband
DTMF, the second is the one queued/generated by the FXO channel.
For a clean fix, I guess some kind of application should be created, that
would prevent DTMF to be queued on the other channel. Such application
would then be called before the bridge. Maybe there is a cleaner way to do
this.
François
On Tue, 15 Jun 2010 18:23:13 -0500, "Jeroen C. van Gelderen"
wrote:
> Hi everybody,
>
> I have a problem that is very similar to a problem
> reported by François [1] except for the fact that
> my FXS and FXO ports are on a Xorcom Astribank
> device instead of a Sangoma.
>
> To quote François: "The problem is that each leg of
> the bridge is detecting the inband DTMF, and so
> [F]reeswitch 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)"
>
> HIS words but evidenced by the MY log :)
>
> The snippet below has DTMF coming in on the FXS port
> (1:1) and bouncing between it and the FXO port (3:1).
> The ports are simply bridged together with
>
> "bridge(OpenZap/3/1/F)" or "bridge(OpenZap/3/1/w)"
>
> I'm running:
>
> FreeSWITCH version: 1.0.head (git-01c0c69 2010-06-08 16-22-21 -0500)
> dahdi: Version: SVN-trunk-r8762
>
> Output of lsdahdi at end of message.
>
> 8<8<8<8<8<8<8<
> [...]
> 2010-06-13 04:18:39.217256 [DEBUG] mod_openzap.c:721 queue DTMF [4]
> 2010-06-13 04:18:39.256255 [DEBUG] zap_io.c:2062 3:1 GENERATE DTMF [4]
> 2010-06-13 04:18:39.397253 [DEBUG] mod_openzap.c:721 queue DTMF [4]
> 2010-06-13 04:18:39.439252 [DEBUG] mod_openzap.c:780 Dropping frame!
(write
> not ready)
> 2010-06-13 04:18:39.439252 [DEBUG] zap_io.c:2062 1:1 GENERATE DTMF [4]
> 2010-06-13 04:18:39.637249 [DEBUG] mod_openzap.c:721 queue DTMF [4]
> 2010-06-13 04:18:39.676248 [DEBUG] zap_io.c:2062 3:1 GENERATE DTMF [4]
> 2010-06-13 04:18:39.859244 [DEBUG] mod_openzap.c:780 Dropping frame!
(write
> not ready)
> [...ad infinitum...]
> 8<8<8<8<8<8<8<
>
> Because I needed DTMF pass-through working "now"
> I applied an ugly HACK. This drops DTMF tones
> detected on spans 3 and 4 (which are my FXO
> spans). This is very WRONG but it does solve
> my immediate problem:
>
> 8<8<8<8<8<8<8<
> diff --git a/libs/openzap/mod_openzap/mod_openzap.c
> b/libs/openzap/mod_openzap/mod_openzap.c
> index 5aebfea..ff3b081 100644
> --- a/libs/openzap/mod_openzap/mod_openzap.c
> +++ b/libs/openzap/mod_openzap/mod_openzap.c
> @@ -718,8 +718,12 @@ static switch_status_t
> channel_read_frame(switch_core_session_t *session, switch
> for (p = dtmf; p && *p; p++) {
> if (is_dtmf(*p)) {
> _dtmf.digit = *p;
> - zap_log(ZAP_LOG_DEBUG, "queue DTMF
[%c]\n",
> *p);
> - switch_channel_queue_dtmf(channel,
&_dtmf);
> + if (tech_pvt->zchan->span_id == 3 ||
> tech_pvt->zchan->span_id == 4) {
> + zap_log(ZAP_LOG_DEBUG, "Ignoring
> DTMF [%c] on FXO port %d:%d\n", *p, tech_pvt->zchan->span_id,
> tech_pvt->zchan->chan_id)
> ;
> + } else {
> + zap_log(ZAP_LOG_DEBUG, "queue
DTMF
> [%c]\n", *p);
> +
switch_channel_queue_dtmf(channel,
> &_dtmf);
> + }
> }
> }
> }
> 8<8<8<8<8<8<8<
>
> Can someone point me in the "right" direction
> instead? Do I need to do this at the OpenZAP/DAHDI
> level by disabling some kind of DTMF detection
> like was done for the Sangoma driver?
>
> Any and all pointers appreciated.
>
> Cheers,
> -Slim
>
> [1] [Freeswitch-dev] FXS bridged on FXO ports and DTMF
>
http://www.mail-archive.com/[email protected]/msg02830.htm
> l
>
> [Freeswitch-dev] Problem with sending
> DTMF on FXS port bridged to an FXO port
>
http://lists.freeswitch.org/pipermail/freeswitch-dev/2010-April/003607.html
>
>
> 8<8<8<8<8<8<8<
> [r...@localhost freeswitch]# lsdahdi
> ### Span 1: XBUS-00/XPD-00 "Xorcom XPD #00/00: FXS" (MASTER)
> 1 FXSFXOKS
> 2 FXSFXOKS
> 3 FXSFXOKS
> 4 FXSFXOKS
> 5 FXSFXOKS
> 6 FXSFXOKS
> 7 FXSFXOKS
> 8 FXSFXOKS
> 9 Output FXOKS
> 10 Output FXOKS
> 11 Input FXOKS
> 12 Input FXOKS
> 13 Input FXOKS
> 14 Input FXOKS
> ### Span 2: XBUS-00/XPD-10 "Xorcom XPD #00/10: FXS"
> 15 FXSFXOKS
> 16 FXSFXOKS
> 17 FXSFXOKS
> 18 FXSF
Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF
Did it and it works. I then applied my patch for the MWI feature and it works too. The patch is already uploaded on JIRA. I'm connected to irc.freenode.net, my pseudo is Francois___. If there are some things you want to discuss... François On Mon, 7 Jun 2010 21:59:55 -0400, Moises Silva wrote: git pull and try again ... again, it'd be good if you can join IRC or ping me on google talk to discuss this. 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. [email protected] [1] On Mon, Jun 7, 2010 at 7:29 PM, Moises Silva wrote: Hi, Yes, I see the race now. Locking in the analog module is, in my opinion, lacking a refactoring, but I've tried to not touch much the analog module since I don't have much time to test it. Before showing you where the problem is, here is a brief explanation of the process for an outgoing call. When FreeSWITCH wants to place a call it will call the .outgoing_channel function pointer of the FreeTDM module, which points to channel_outgoing_channel in mod_freetdm.c line 1037. That function is called in the caller thread (assuming there is a caller), the caller may be a SIP endpoint, other analog channel or whatever technology FS supports. At this point ftdm_channel_call_place() will be called, which is pretty much a wrapper for the FTDM signaling module outgoing_call function pointer (span->outgoing_call) that is set depending on the signaling for that channel. In this case is analog_fxs_outgoing_call(). In the case of analog, this spawns a new thread, meaning the analog stack spawns a thread per call (where all current ISDN stacks have just 1 thread per span handling the signaling for all calls in that span at once). The problem right here is that ftdm_channel_open_chan is using ftdm_mutex_trylock(), and with the new code, the channel sometimes will be locked by a few microseconds by the outgoing routine, which, if at that particular moment ftdm_channel_open_chan is called by the service thread (ftdm_analog_channel_run), it will fail the whole call. This is legacy code I have leaved pretty much untouched, but I think I will get rid of it and use a regular ftdm_mutex_lock(). You can give that a try (just change trylock for lock ... or wait for me, I am cooking some changes now that are cleaning up some old and duplicated code when opening channels/requesting channels, should be ready tomorrow. 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. [email protected] [3] On Mon, Jun 7, 2010 at 4:17 PM, wrote: I'm in the process of testing the patch, and I have some troubles with FXS now. When bridging a call onto an FXS channel, the bridge fails. What seem to happen is the lock acquired in ftmod_analog.c line 83 is not released (seems it is not) before ftdm_analog_channel_run calls ftdm_channel_open_chan which in turn tries to acquire and fails the same lock. If I add a 500ms delay (ftdm_sleep) at the entrance of ftdm_analog_channel_run, the problem disappears. There seem to be a race condition here, but as I have no idea how threads are scheduled (nor within mod_freetdm neither in overall freeswitch) this is beyond my skills. However (I get the same kind of scheduling problems when trying to thread the MWI function) I'd be glad to learn how that works, so if you have any pointers… François DE : [email protected] [5] [mailto:[email protected] [6]] DE LA PART DE Moises Silva ENVOYÉ : jeudi 3 juin 2010 23:35 À : [email protected] [7] OBJET : Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF Something is f'd up there badly. I cannot reproduce this in my A200. Can you give me more details of how are you wiring things up? Also do "git pull", I just improved the DTMF logging to aid in in debugging. Reproduce the problem and pastebin the resulting logs. Regarding your MWI patch. I added some comments on JIRA. 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. [email protected] [8] On Thu, Jun 3, 2010 at 6:46 AM, François Legal wrote: So now using latest git and wanpipe is even worse compared to snapshot from last week. freetdm now also detects and queue the DTMF from the dialed number. The new patch is available. On Wed, 2 Jun 2010 16:26:49 -0400, Moises Silva wrote: I'm going to test this DTMF scenario now and let you know. In the meantime, would it be much to ask a patch that I can apply using git apply?? The patch still fails to apply using git, I see you are still using svn, try git plz. The code looks good though :-) Moises Silva Senior Software Engineer Sangoma Technologies Inc. | 50 McIntosh
Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF
git pull and try again ... again, it'd be good if you can join IRC or ping me on google talk to discuss this. 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. [email protected] On Mon, Jun 7, 2010 at 7:29 PM, Moises Silva wrote: > Hi, > > Yes, I see the race now. Locking in the analog module is, in my opinion, > lacking a refactoring, but I've tried to not touch much the analog module > since I don't have much time to test it. > > Before showing you where the problem is, here is a brief explanation of the > process for an outgoing call. > > When FreeSWITCH wants to place a call it will call the .outgoing_channel > function pointer of the FreeTDM module, which points to > channel_outgoing_channel in mod_freetdm.c line 1037. That function is called > in the caller thread (assuming there is a caller), the caller may be a SIP > endpoint, other analog channel or whatever technology FS supports. At this > point ftdm_channel_call_place() will be called, which is pretty much a > wrapper for the FTDM signaling module outgoing_call function pointer > (span->outgoing_call) that is set depending on the signaling for that > channel. In this case is analog_fxs_outgoing_call(). In the case of analog, > this spawns a new thread, meaning the analog stack spawns a thread per call > (where all current ISDN stacks have just 1 thread per span handling the > signaling for all calls in that span at once). > > The problem right here is that ftdm_channel_open_chan is using > ftdm_mutex_trylock(), and with the new code, the channel sometimes will be > locked by a few microseconds by the outgoing routine, which, if at that > particular moment ftdm_channel_open_chan is called by the service thread > (ftdm_analog_channel_run), it will fail the whole call. This is legacy code > I have leaved pretty much untouched, but I think I will get rid of it and > use a regular ftdm_mutex_lock(). > > You can give that a try (just change trylock for lock ... or wait for me, I > am cooking some changes now that are cleaning up some old and duplicated > code when opening channels/requesting channels, should be ready tomorrow. > > 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. [email protected] > > > On Mon, Jun 7, 2010 at 4:17 PM, wrote: > >> I’m in the process of testing the patch, and I have some troubles with >> FXS now. >> >> >> >> When bridging a call onto an FXS channel, the bridge fails. What seem to >> happen is the lock acquired in ftmod_analog.c line 83 is not released (seems >> it is not) before ftdm_analog_channel_run calls ftdm_channel_open_chan which >> in turn tries to acquire and fails the same lock. >> >> >> >> If I add a 500ms delay (ftdm_sleep) at the entrance of >> ftdm_analog_channel_run, the problem disappears. >> >> There seem to be a race condition here, but as I have no idea how threads >> are scheduled (nor within mod_freetdm neither in overall freeswitch) this is >> beyond my skills. However (I get the same kind of scheduling problems when >> trying to thread the MWI function) I’d be glad to learn how that works, so >> if you have any pointers… >> >> >> >> François >> >> >> >> >> >> *De :* [email protected] [mailto: >> [email protected]] *De la part de* Moises Silva >> *Envoyé :* jeudi 3 juin 2010 23:35 >> >> *À :* [email protected] >> *Objet :* Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF >> >> >> >> Something is f'd up there badly. I cannot reproduce this in my A200. >> >> Can you give me more details of how are you wiring things up? >> >> Also do "git pull", I just improved the DTMF logging to aid in in >> debugging. Reproduce the problem and pastebin the resulting logs. >> >> Regarding your MWI patch. I added some comments on JIRA. >> >> 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. [email protected] >> >> On Thu, Jun 3, 2010 at 6:46 AM, François Legal >> wrote: >> >> So now using latest git and wanpipe is even worse compared to snapshot >> from last week. freetdm now also detects and queue the DTMF from the dialed >> number. >> >> The new patch is available. >> >> On Wed, 2 Jun 2
Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF
Hi, Yes, I see the race now. Locking in the analog module is, in my opinion, lacking a refactoring, but I've tried to not touch much the analog module since I don't have much time to test it. Before showing you where the problem is, here is a brief explanation of the process for an outgoing call. When FreeSWITCH wants to place a call it will call the .outgoing_channel function pointer of the FreeTDM module, which points to channel_outgoing_channel in mod_freetdm.c line 1037. That function is called in the caller thread (assuming there is a caller), the caller may be a SIP endpoint, other analog channel or whatever technology FS supports. At this point ftdm_channel_call_place() will be called, which is pretty much a wrapper for the FTDM signaling module outgoing_call function pointer (span->outgoing_call) that is set depending on the signaling for that channel. In this case is analog_fxs_outgoing_call(). In the case of analog, this spawns a new thread, meaning the analog stack spawns a thread per call (where all current ISDN stacks have just 1 thread per span handling the signaling for all calls in that span at once). The problem right here is that ftdm_channel_open_chan is using ftdm_mutex_trylock(), and with the new code, the channel sometimes will be locked by a few microseconds by the outgoing routine, which, if at that particular moment ftdm_channel_open_chan is called by the service thread (ftdm_analog_channel_run), it will fail the whole call. This is legacy code I have leaved pretty much untouched, but I think I will get rid of it and use a regular ftdm_mutex_lock(). You can give that a try (just change trylock for lock ... or wait for me, I am cooking some changes now that are cleaning up some old and duplicated code when opening channels/requesting channels, should be ready tomorrow. 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. [email protected] On Mon, Jun 7, 2010 at 4:17 PM, wrote: > I’m in the process of testing the patch, and I have some troubles with > FXS now. > > > > When bridging a call onto an FXS channel, the bridge fails. What seem to > happen is the lock acquired in ftmod_analog.c line 83 is not released (seems > it is not) before ftdm_analog_channel_run calls ftdm_channel_open_chan which > in turn tries to acquire and fails the same lock. > > > > If I add a 500ms delay (ftdm_sleep) at the entrance of > ftdm_analog_channel_run, the problem disappears. > > There seem to be a race condition here, but as I have no idea how threads > are scheduled (nor within mod_freetdm neither in overall freeswitch) this is > beyond my skills. However (I get the same kind of scheduling problems when > trying to thread the MWI function) I’d be glad to learn how that works, so > if you have any pointers… > > > > François > > > > > > *De :* [email protected] [mailto: > [email protected]] *De la part de* Moises Silva > *Envoyé :* jeudi 3 juin 2010 23:35 > > *À :* [email protected] > *Objet :* Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF > > > > Something is f'd up there badly. I cannot reproduce this in my A200. > > Can you give me more details of how are you wiring things up? > > Also do "git pull", I just improved the DTMF logging to aid in in > debugging. Reproduce the problem and pastebin the resulting logs. > > Regarding your MWI patch. I added some comments on JIRA. > > 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. [email protected] > > On Thu, Jun 3, 2010 at 6:46 AM, François Legal > wrote: > > So now using latest git and wanpipe is even worse compared to snapshot from > last week. freetdm now also detects and queue the DTMF from the dialed > number. > > The new patch is available. > > On Wed, 2 Jun 2010 16:26:49 -0400, Moises Silva > wrote: > > I'm going to test this DTMF scenario now and let you know. > > In the meantime, would it be much to ask a patch that I can apply using git > apply?? The patch still fails to apply using git, I see you are still using > svn, try git plz. > > The code looks good though :-) > > 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. [email protected] > > On Wed, Jun 2, 2010 at 4:19 PM, wrote: > > I just updated to 3.5.11 and the result is the same. > > > > *De :* [email protected] [mailto: > [email protected]] *De
Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF
I’m in the process of testing the patch, and I have some troubles with FXS now. When bridging a call onto an FXS channel, the bridge fails. What seem to happen is the lock acquired in ftmod_analog.c line 83 is not released (seems it is not) before ftdm_analog_channel_run calls ftdm_channel_open_chan which in turn tries to acquire and fails the same lock. If I add a 500ms delay (ftdm_sleep) at the entrance of ftdm_analog_channel_run, the problem disappears. There seem to be a race condition here, but as I have no idea how threads are scheduled (nor within mod_freetdm neither in overall freeswitch) this is beyond my skills. However (I get the same kind of scheduling problems when trying to thread the MWI function) I’d be glad to learn how that works, so if you have any pointers… François De : [email protected] [mailto:[email protected]] De la part de Moises Silva Envoyé : jeudi 3 juin 2010 23:35 À : [email protected] Objet : Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF Something is f'd up there badly. I cannot reproduce this in my A200. Can you give me more details of how are you wiring things up? Also do "git pull", I just improved the DTMF logging to aid in in debugging. Reproduce the problem and pastebin the resulting logs. Regarding your MWI patch. I added some comments on JIRA. 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. [email protected] On Thu, Jun 3, 2010 at 6:46 AM, François Legal wrote: So now using latest git and wanpipe is even worse compared to snapshot from last week. freetdm now also detects and queue the DTMF from the dialed number. The new patch is available. On Wed, 2 Jun 2010 16:26:49 -0400, Moises Silva wrote: I'm going to test this DTMF scenario now and let you know. In the meantime, would it be much to ask a patch that I can apply using git apply?? The patch still fails to apply using git, I see you are still using svn, try git plz. The code looks good though :-) 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. [email protected] On Wed, Jun 2, 2010 at 4:19 PM, wrote: I just updated to 3.5.11 and the result is the same. De : [email protected] [mailto:[email protected]] De la part de Moises Silva Envoyé : mercredi 2 juin 2010 21:35 À : [email protected] 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. [email protected] On Wed, Jun 2, 2010 at 3:22 PM, 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. Thanks François ___ FreeSWITCH-dev mailing list [email protected] http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org ___ FreeSWITCH-dev mailing list [email protected] http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org ___ FreeSWITCH-dev mailing list [email protected] http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org ___ FreeSWITCH-dev mailing list [email protected] http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF
Something is f'd up there badly. I cannot reproduce this in my A200. Can you give me more details of how are you wiring things up? Also do "git pull", I just improved the DTMF logging to aid in in debugging. Reproduce the problem and pastebin the resulting logs. Regarding your MWI patch. I added some comments on JIRA. 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. [email protected] On Thu, Jun 3, 2010 at 6:46 AM, François Legal wrote: > So now using latest git and wanpipe is even worse compared to snapshot from > last week. freetdm now also detects and queue the DTMF from the dialed > number. > > The new patch is available. > > On Wed, 2 Jun 2010 16:26:49 -0400, Moises Silva > wrote: > > I'm going to test this DTMF scenario now and let you know. > > In the meantime, would it be much to ask a patch that I can apply using git > apply?? The patch still fails to apply using git, I see you are still using > svn, try git plz. > > The code looks good though :-) > > 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. [email protected] > > > On Wed, Jun 2, 2010 at 4:19 PM, wrote: > >> I just updated to 3.5.11 and the result is the same. >> >> >> >> *De :* [email protected] [mailto: >> [email protected]] *De la part de* Moises Silva >> *Envoyé :* mercredi 2 juin 2010 21:35 >> *À :* [email protected] >> *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. [email protected] >> >> On Wed, Jun 2, 2010 at 3:22 PM, 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. >> >> >> >> Thanks >> >> >> >> François >> >> >> >> >> ___ >> FreeSWITCH-dev mailing list >> [email protected] >> http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev >> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev >> http://www.freeswitch.org >> >> >> >> ___ >> FreeSWITCH-dev mailing list >> [email protected] >> http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev >> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev >> http://www.freeswitch.org >> >> > > ___ > FreeSWITCH-dev mailing list > [email protected] > http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev > http://www.freeswitch.org > > ___ FreeSWITCH-dev mailing list [email protected] http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF
So now using latest git and wanpipe is even worse compared to snapshot from last week. freetdm now also detects and queue the DTMF from the dialed number. The new patch is available. On Wed, 2 Jun 2010 16:26:49 -0400, Moises Silva wrote: I'm going to test this DTMF scenario now and let you know. In the meantime, would it be much to ask a patch that I can apply using git apply?? The patch still fails to apply using git, I see you are still using svn, try git plz. The code looks good though :-) 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. [email protected] [1] On Wed, Jun 2, 2010 at 4:19 PM, wrote: I just updated to 3.5.11 and the result is the same. DE : [email protected] [3] [mailto:[email protected] [4]] DE LA PART DE Moises Silva ENVOYÉ : mercredi 2 juin 2010 21:35 À : [email protected] [5] 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. [email protected] [6] On Wed, Jun 2, 2010 at 3:22 PM, 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. Thanks François ___ FreeSWITCH-dev mailing list [email protected] [8] http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev [9] UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev [10] http://www.freeswitch.org [11] ___ FreeSWITCH-dev mailing list [email protected] [12] http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev [13] UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev [14] http://www.freeswitch.org [15] Links: -- [1] mailto:[email protected] [2] mailto:[email protected] [3] mailto:[email protected] [4] mailto:[email protected] [5] mailto:[email protected] [6] mailto:[email protected] [7] mailto:[email protected] [8] mailto:[email protected] [9] http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev [10] http://lists.freeswitch.org/mailman/options/freeswitch-dev [11] http://www.freeswitch.org [12] mailto:[email protected] [13] http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev [14] http://lists.freeswitch.org/mailman/options/freeswitch-dev [15] http://www.freeswitch.org ___ FreeSWITCH-dev mailing list [email protected] http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF
I'm going to test this DTMF scenario now and let you know. In the meantime, would it be much to ask a patch that I can apply using git apply?? The patch still fails to apply using git, I see you are still using svn, try git plz. The code looks good though :-) 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. [email protected] On Wed, Jun 2, 2010 at 4:19 PM, wrote: > I just updated to 3.5.11 and the result is the same. > > > > *De :* [email protected] [mailto: > [email protected]] *De la part de* Moises Silva > *Envoyé :* mercredi 2 juin 2010 21:35 > *À :* [email protected] > *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. [email protected] > > On Wed, Jun 2, 2010 at 3:22 PM, 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. > > > > Thanks > > > > François > > > > > ___ > FreeSWITCH-dev mailing list > [email protected] > http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev > http://www.freeswitch.org > > > > ___ > FreeSWITCH-dev mailing list > [email protected] > http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev > http://www.freeswitch.org > > ___ FreeSWITCH-dev mailing list [email protected] http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
Re: [Freeswitch-dev] FXS bridged on FXO ports and DTMF
I just updated to 3.5.11 and the result is the same. De : [email protected] [mailto:[email protected]] De la part de Moises Silva Envoyé : mercredi 2 juin 2010 21:35 À : [email protected] 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. [email protected] On Wed, Jun 2, 2010 at 3:22 PM, 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. Thanks François ___ FreeSWITCH-dev mailing list [email protected] http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org ___ FreeSWITCH-dev mailing list [email protected] http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
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. [email protected] On Wed, Jun 2, 2010 at 3:22 PM, 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. > > > > Thanks > > > > François > > > > ___ > FreeSWITCH-dev mailing list > [email protected] > http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev > http://www.freeswitch.org > > ___ FreeSWITCH-dev mailing list [email protected] http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
