Signalling mismatch

I am using the following: Asterisk 1.2.17, Asterisk-addons 1.2.5, Asterisk-sounds 1.2.1, and FreePBX 2.2.1.

I had a working Asterisk server but after upgrading FreePBX to 2.2.3, it has the errors shown below. I am not saying upgrading caused it but it may be a factor.

error message from /var/log/asterisk/full:
ERROR[7455] chan_zap.c: Signalling requested on channel 1 is FXO Kewlstart but line is in FXO Loopstart signalling
ERROR[7455] chan_zap.c: Unable to register channel ‘1’

/etc/zaptel.conf:
fxols=1
fxols=2
fxols=3
fxols=4
fxols=5
fxols=6
fxols=7
fxols=8
fxsks=21
fxsks=22
fxsks=23
fxsks=24

loadzone = us
defaultzone = us

span=2,0,0,esf,b8zs
bchan=25-47
dchan=48

/etc/asterisk/zapata.conf
[channels]

some portions omitted from this post

signalling=fxo_ls
channel => 1
context=default

Running ztcfg -vvv would result in channel 1-8 as FXO Loopstart and channel 21-24 as FXS Kewlstart.

Hi,
I know it’s not directly answering your question, but why not use kewlstart on all channels?

I’d expect the analog trunks to be where signalling is critical & they are already set as fxsks.

Changing all the analog extensions to fxoks should ay least get things running.

The only difference between the two is that kewlstart provides end-of-call notification so any equipment connected to the line clears properly.
If you are using something like as analog fax or answering machine it will probably work better, you will not see any change on analog extension phones.

Using kewlstart in /etc/zaptel.conf allowed Asterisk to start working again.