[asterisk-users] Asterisk, POTS and plain handsets

[Steve Totaro]

On Thu, Jun 26, 2008 at 9:11 PM, Steve <astuser at braingia.org> wrote:
> Hello,
>
> I've spent a couple days searching and posted into the forum with no luck, apologies
> to anyone who reads the Digium forums for the cross-post.
>
> I'm having a problem with an asterisk set up where I have a TDM402B connected to a POTS
> line.  Also connected to the POTS line are plain telephones, non SIP, just plain
> old telephones.  When one of the normal handsets goes off-hook, asterisk
> reads it as an incoming call and starts handling it accordingly, running through the
> context for that channel as if an incoming call was detected.  I'd like asterisk to act
> like just another handset on the line or an answering machine and not do anything if a handset is used
> on that same line.
>
> It seems like maybe it's a voltage issue where asterisk or the zaptel module is sensing a
> voltage change on the line and so is doing what it thinks it should do.  I'd like to know
> how to dumb it down or make it less sensitive to the changes, if indeed that is the cause.
>
> I've tried various combinations of asterisk versions and zap module versions and various combinations of
> phone lines to the card and, well, everything else that I can think of.  So I'm hoping that
> someone out there has used an asterisk set up like this and maybe encountered the same
> things that I'm seeing.
>
> I'd be happy to post any configs that someone might find relevant.
>
> Steve

Post the output from Asterisk's CLI.  I think maybe your contexts are
overlapping or are the same.  It should say something to the effect of
"Starting simple switch"

Check what context your FXO channels are in, something like
context=from-verizon and then check the context of your FXS (plain
telephones), they should be in a different context such as
context=to-phones.

Also, make sure you have immediate=no

Then check your dialplan and make sure those contexts do what you want
and you are not accidentally including a context where it should not
be.

Thanks,
Steve Totaro