On 2016-11-27 06:46 AM, Max Grobecker wrote:
Hi,
you could try switching the DTMF mode of the ATA's SIP peer (and also in the
ATA itself) to INBAND transmission.
In this mode, the ATA doesn't need to recognise DTMF tones and your Asterisk
can interpret it.
For this to work, the ATA needs to us
Hi,
you could try switching the DTMF mode of the ATA's SIP peer (and also in the
ATA itself) to INBAND transmission.
In this mode, the ATA doesn't need to recognise DTMF tones and your Asterisk
can interpret it.
For this to work, the ATA needs to use a G.711 codec. Inband DTMF needs an
uncompre
On 2016-11-22 07:49 PM, Pete Mundy wrote:
One direction that may be worth exploring further is his ATA's config (or
perhaps swapping it for a different model). Eg adjusting echo cancellation or
line impedance settings.
I have to be careful here as I auto-provison these devices and changes
w
On 23/11/16 13:49, Pete Mundy wrote:
One direction that may be worth exploring further is his ATA's config (or
perhaps swapping it for a different model). Eg adjusting echo cancellation or
line impedance settings.
Is the ATA he is using the same as the ATA you use?
Failure to correctly recog
One direction that may be worth exploring further is his ATA's config (or
perhaps swapping it for a different model). Eg adjusting echo cancellation or
line impedance settings.
Is the ATA he is using the same as the ATA you use?
Failure to correctly recognise and decode DTMF is just one of ma
I am hoping someone else has seen this and can offer a solution or at
least a direction to investigate. I am running 11.23. Most of my
clients are fine but one has a strange behaviour. He has a Grandstream
HT701 like most of my clients who use an ATA. He can make call and they
are crystal c
