[Asterisk-Users] FXO mode

[Dave Cotton]

On Thu, 2003-08-14 at 12:24, Andy Powell wrote:
> Can't find the message in a search.. but below is a msg retreved from my 
> archive..
> 
> this is what Mark sent a little while ago....
> I have no idea if it actually does anything to the card, but on a modprobe I 
> do get a msg saying it's using CTR21
> 
> Andy
> 
> >
> >I'm in Paris right now and can't test this change, but I've been
> >researching the DAA and there are a few international settings I can
> >change, so I've changed the driver in CVS so that you can specify
> >the operational mode.  Try "modprobe wcfxo opermode=1" if you're in most
> >of Europe and that should switch to CTR21 mode which slightly modifies a
> >few of the electrical characteristics of the DAA.
> >
> >As we add modes you'll be able to see them with "modprobe wcfxo
> >opermode=-1" and then doing a dmesg.
> >
> >Anyway all you folks that had some trouble like this try it out and let me
> >know if it makes any difference.
> >
> >Mark
> >
> >_______________________________________________

Thanks Andy. The stage I'm at at the moment is that I've removed the
code for the US and so dmesg will show CTR21 without the modprobe
option. But I don't think that is the whole problem.

Last night I posted showing that the problem is repeatable and only
occurs in one certain circumstance. I think it is within voicemail.c. If
the caller exits voicemail by pressing # the line is dropped correctly,
if they just hang up voicemail continues to record. I put some debugging
statements into voicemail.c and I think that a condition statement is
never reached so the line is held up. The routine in question is 14
pages long, so it reminds me of my Cobol days when we used to lay the
printouts along the corridor to debug them.

As far as the option to modprobe is concerned couldn't zaptel.conf be
used for this as it would be more obvious, I only heard about the option
from your post last night.
 
-- 
Dave Cotton <dcotton at linuxautrement.com>