[Asterisk-Dev] ZAPTEL driver questions - loop start hangup

[Matthew Butt]

I originally had it on Kewlstart but had a weird issue - as soon as the
remote person picks up, Asterisk hangs up the channel.  The drivers were
repoting NO BATTERY as soon as the call was picked up and I think
Asterisk was thinking this was the hangup signal.  

I managed to avoid this by increasing the debounce time to avoid the NO
BATTERY detection, but this caused other problems.

The BT techie (well call centre phone answerer!) also mentioned
something about MF4 but I can't find any reference to this anywhere!

Matthew Butt + T R I C Y C L E
 

-----Original Message-----
From: asterisk-dev-bounces at lists.digium.com
[mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of Jeffrey C.
Ollie
Sent: Tuesday, May 03, 2005 4:11 PM
To: Asterisk Developers Mailing List
Subject: Re: [Asterisk-Dev] ZAPTEL driver questions - loop start hangup

On Tue, 2005-05-03 at 12:44 -0400, Matthew Butt wrote:
> Hi all,
> 
> I'm trying to get UK BT Featurelines running with X100P cards.  BT
tell
> me that they're running Loopstart but without disconnect supervision.
> When a caller hangs up BT don't send any kind of busy/dial tone so
> there's no audible way of telling that a call has finished.
> 
> With the zap drivers running fxs_ls in debug mode I can see NO BATTERY
> then BATTERY (is this called a debounce?) when the caller hangs up
but:

Well, it looks like BT lied to you.  The loss of battery voltage is
disconnect supervision.  Change the Zaptel drivers and Asterisk to use
kewlstart signaling, which is loopstart plus disconnect supervision.

Jeff