[asterisk-r2] DTMF issue after migrating Unicall -> OpenR2

[Norman Schmidt]

Hello Moisés, here goes:

Asterisk version:

CLI> core show version
Asterisk 1.4.21.2 built by root @ servidor on a i686 running Linux on
2009-04-12 19:48:21 UTC   

OpenR2 patch downloaded from:
http://openr2.googlecode.com/files/openr2-asterisk-1.4.21.patch

CLI> mfcr2 show version
OpenR2 version: 1.1.0, revision: exported   

LibopenR2 version 1.1.0 download from:
http://openr2.googlecode.com/files/openr2-1.1.0.tar.gz

Zaptel version 1.4.12.1
# cat /sys/module/zaptel/version
1.4.12.1                        

Norman

> ----- Mensagem Original -----
> Assunto: Re: [asterisk-r2] DTMF issue after migrating Unicall -> OpenR2
> De: Moises Silva <moises.silva at gmail.com>
>  Para: "Norman Schmidt"
<norman at omegatecnologia.com>,asterisk-r2 at lists.digium.com
> Data: 20/04/2009 13:07
> 
> 
> > which is called to get its IVR on the internal leg of the gateway (group
3).
> > Any clue or starting point? Is this related to the zaptel OpenR2 patch?
> 
> In short, this does not seem related to R2. But I need your Asterisk
> version and the exact download link of the patch you applied to verify
> how the code looks. However, this WARNING you see, is displayed by
> Asterisk when the zaptel driver could not generate/send the requested
> DTMF digit, sounds like a driver problem, but I am not aware of any
> zaptel issues that would result in DTMF failures (more concretely
> ZT_DIAL command failures).
> 
> Post here the following:
> 
> Asterisk version (core show version)
> OpenR2 patch download link.
> Zaptel/DAHDI Version (/sys/module/dahdi/version or
/sys/module/zaptel/version)
> 
> If you are still using Zaptel and not DAHDI, you should try to upgrade
> to DAHDI. You don't need to change anything in the dial plan, you can
> work with DAHDI using Asterisk compatibility mode with Zaptel (AFAIR).
> 
> Moisés Silva,
> 
> 
> -- 
> "I do not agree with what you have to say, but I’ll defend to the
> death your right to say it." Voltaire