[asterisk-dev] DTMF issues with 1.6.1.18

[Pavel Troller]

> Bryant Zimmerman wrote:
> > We having issues with DTMF on 1.6.1.18
> > 
> > Our systems are running rfc2833 with our national carriers. The issue 
> > that is arising is DTMF is degrading over time. When we send out DTMF we 
> > are told the DTMF messages are not correct. When I do a pcap the dtmf 
> > packets look ok but they just don't' work. If I restart asterisk the 
> > issues goes away with all of the carriers but comes back several days 
> > later.  My asterisk to asterisk DTMF is not effected so I don't 
> > understand what is happening.
> > 
> > I am dealing with multiple carriers and two of them are telling me that 
> > the DTMF packets are not correct when this error is occurring. Any ideas 
> > on what could be causing the DTMF packets to start being sent wrong? I 
> > have not been able to find any bug reports that would cover this.
> > 
> > Any help on how to start trouble shooting this one would be appreciated.
> 
> Can they tell you what is wrong? Sometimes support people will say something 
> very general in order to get out of it :)
> 
> Seems odd to me it would "degrade" but ok. Perhaps they can send you some logs 
> pointing out what part is wrong that they are seeing.
> 
> Leif.
> 
Hi!

I can vaguely remember that I was solving something like this for an older
1.6 release, maybe 1.6.0.x or early 1.6.1.x, I really can't remember exactly.
The symptoms were similar - after a restart all was working, but a few days
later the DTMF stopped working with SOME peers, not all. The RTP stream was
really corrupted, I'm not sure but mabye all the timestamps were zeros... Or
something like this. I've updated and since then, I didn't observe this 
anymore.

With regards, Pavel