We disabled it in the wct4xxp.c driver as well and everything has
worked great since then. I have heard from support to try raising the
threshold value while leaving hardware DTMF detection on and it didn't
help raising it by 100.
In the big picture, doing hardware DTMF detection gives you an
incr
Kevin P. Fleming wrote:
There are other steps that can be taken if necessary first.
Can you please elaborate on this? It may just save a lot of calls to Digium
support about the same issue. (I have noticed this sporadically).
___
--Bandwidth and C
On Wednesday 09 November 2005 21:46, Boris Bakchiev wrote:
> I noticed that the latest wct4xxp sources allow disabling DTMF support
> in VPM modules.
It just disables the VPM's capability to detect DTMF; DTMF detection still
works within Asterisk as it'll be done on the host CPU (i.e. the old way
Boris Bakchiev wrote:
PRI<->TE406P SPAN1<->TE406P SPAN3<->PABX
Please contact Digium technical support.
I noticed that the latest wct4xxp sources allow disabling DTMF support
in VPM modules.
There are other steps that can be taken if necessary first.
___
Hi,
I’m getting a lot of false DTMF detections on my
system.
Following is a diagram of my system:
PRI<->TE406P SPAN1<->TE406P SPAN3<->PABX
Basically anyone talking to me with a higher pitch
voice (Ladies) I get “beeps” all over the place.
If I unplug PRI from Asterisk and p
