[asterisk-users] vzaphfc?

[Tzafrir Cohen]

On Tue, Jan 02, 2007 at 11:10:56PM +0100, Remco Barendse wrote:
> On Fri, 29 Dec 2006, Julian J. M. wrote:
> 
> >It's not necessary to recompile the kernel for mISDN support. Check
> >http://www.laimbock.com/asterisk/
> >
> >Grab the mISDN source rpm, and build it.
> >
> >$ wget 
> >http://www.xs4all.nl/~pjl/downloads/asterisk/srpms/mISDN-cvs20061107-2_fc6.lc.src.rpm
> >$ rpmbuild --rebuild mISDN-cvs20061107-2_fc6.lc.src.rpm
> >
> >then check /usr/src/redhat/RPMS/i386/
> >You should have the kernel modules and userspace applications. Once
> >installed, I could enable chan_misdn in asterisk 1.4 without issue,
> >and it's working great in NT mode with ISDN phones. I haven't tested
> >asterisk 1.2, but there is no it shouldn't work as well.
> 
> I deleted all the bristuff modules i could find plus the old asterisk 
> libs, compiled zaptel, libpri and asterisk from scratch but can't get it 
> to work.
> 
> First I get errors about something I guess is missing from misdn, later 
> errors about zaptel.
> 
> I'll just toss the HFC-S card and convert the ISDN line to analog.
> 
> These are the errors :
> .mISDN_close: fid(14) isize(131072) inbuf(0x2a96ee6010) irp(0x2a96ee6010) 
> iend(0x2a96ee6010)
> Jan  2 23:07:23 WARNING[25747]: misdn_config.c:642 _build_port_config: 
> misdn.conf: "ports=(null)" (section: intern) invalid or out of range. 
> Please edit your misdn.conf and then do a "misdn reload".
> Jan  2 23:07:23 WARNING[25747]: misdn_config.c:642 _build_port_config: 
> misdn.conf: "ports=(null)" (section: first_extern) invalid or out of 
> range. Please edit your misdn.conf and then do a "misdn reload".
> Jan  2 23:07:23 WARNING[25747]: misdn_config.c:642 _build_port_config: 
> misdn.conf: "ports=(null)" (section: second_extern) invalid or out of 
> range. Please edit your misdn.conf and then do a "misdn reload".
> P[ 0] Got: 1 from get_ports
> P[ 0] -- mISDN Channel Driver Registred -- (BE AWARE THIS DRIVER IS 
> EXPERIMENTAL!)
> ......Jan  2 23:07:23 ERROR[25747]: chan_zap.c:10603 setup_zap: Unknown 
> signalling method 'bri_cpe_ptmp'

our Asterisk is not bristuffed. And you don't expect to use ZapBRI,
anyway.

BTW: with 1.4 and latest 1.2, bristuffed zaptel could basicaly work with
the signalling  type pri_cpe/pri_net, though this is not well-tested and
may not perform as well as bristuffed asterisk/libpri.

> Jan  2 23:07:23 ERROR[25747]: chan_zap.c:10228 setup_zap: Signalling must 
> be specified before any channels are.
> Jan  2 23:07:23 WARNING[25747]: loader.c:414 __load_resource: chan_zap.so: 
> load_module failed, returning -1
> Jan  2 23:07:23 WARNING[25747]: loader.c:554 load_modules: Loading module 
> chan_zap.so failed!

You have zaptel channels configured in your zapata.conf .

BTW: I guess that this is 1.2 and not 1.4, because 1.4 should not fail
just becasue chan_zap.so has failed to set up some channels.

-- 
               Tzafrir Cohen       
icq#16849755                    jabber:tzafrir at jabber.org
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com       
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir