asterisk users - Mar 2005 - Unknown signalling 896?

I've been beating my head a bit against the 1.0.6 Debian builds of
Asterisk, using an E100P (E1, single span) board.

In machines I've built in the past (back in 1.0.0 days), config I'm
using and that card and 1.0.0 driver combo worked fine.

ztcfg reports no problems:

	SPAN 1: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
	31 channels configured.

And zttool sees the card, and reports it in the state I expect (there's
no real E1 attached to it, so blue/red alarms..)

But * won't bring up chan_zap at all:

	ERROR[2215]: Signalling requested is PRI Signalling but line is
	in Unknown signalling 896 signalling
	ERROR[2215]: Unable to register channel '1-30'
	WARNING[2215]: chan_zap.so: load_module failed, returning -1
	WARNING[2215]: Loading module chan_zap.so failed!

Ideas? I'm sure it's something simple I've missed. :)

Config fragments follow:

==/etc/zaptel.conf=span=1,0,0,ccs,hdb3
bchan=1-15,17-31
dchan=16
loadzone=nz
defaultzone=nz
==end=
==/etc/asterisk/zapata.conf=context = default
switchtype = euroisdn
priindication = outofband
group = 2
signalling = pri_cpe
channel => 1-30
==end=
Thanks.

-- 
David Zanetti <david.zanetti@catalyst.net.nz>
Team Leader, Systems Administration
Catalyst IT Limited
+64-4-8032233 +64-21-402260
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url :
http://lists.digium.com/pipermail/asterisk-users/attachments/20050315/e191999f/attachment.pgp

David Zanetti wrote:
> I've been beating my head a bit against the 1.0.6 Debian builds of
> Asterisk, using an E100P (E1, single span) board.
> 
> In machines I've built in the past (back in 1.0.0 days), config I'm
> using and that card and 1.0.0 driver combo worked fine.
> 
> ztcfg reports no problems:
> 
> 	SPAN 1: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
> 	31 channels configured.
> 
> And zttool sees the card, and reports it in the state I expect (there's
> no real E1 attached to it, so blue/red alarms..)
> 
> But * won't bring up chan_zap at all:
> 
> 	ERROR[2215]: Signalling requested is PRI Signalling but line is
> 	in Unknown signalling 896 signalling
> 	ERROR[2215]: Unable to register channel '1-30'
> 	WARNING[2215]: chan_zap.so: load_module failed, returning -1
> 	WARNING[2215]: Loading module chan_zap.so failed!
> 
> Ideas? I'm sure it's something simple I've missed. :)
> 
> Config fragments follow:
> 
> ==/etc/zaptel.conf=> span=1,0,0,ccs,hdb3
> bchan=1-15,17-31
> dchan=16
> loadzone=nz
> defaultzone=nz
> ==end=> 
> ==/etc/asterisk/zapata.conf=> context = default
> switchtype = euroisdn
> priindication = outofband
> group = 2
> signalling = pri_cpe
> channel => 1-30
> ==end=
Notice the [channels] lines at the top of the zaptel.conf.sample?  You 
need it.

--Eric

-- 
Always do right. This will gratify some people and astonish the rest.
Mark Twain