Thanks Michael! Dahdi show status is now showing all 4 spans. I only have one ISDN line here so only one "Alarm - OK" All calls (there are various msn's) are being seen. (didn't yet build the dialplan).
Any idea what this means: [Jun 18 19:39:04] NOTICE[372]: chan_dahdi.c:3099 my_handle_dchan_exception: PRI got event: HDLC Abort (6) on D-channel of span 1 I'm getting it repeated on span 1 about every 37 seconds. (why "PRI" ???) Thanks! -Graham- Michael Keuter wrote on 18/06/12 18:10: > > Am 18.06.2012 um 17:44 schrieb Graham S. Jarvis: > >> Hello All, >> >> Does anyone have a working set of config files that they could post here? >> >> I have flashing red lights and they go green when I plug in an ISDN line. >> eg: >> Jun 18 17:20:51 pbx user.info kernel: wcb4xxp 0000:02:08.0: new card sync >> source: port 1 >> >> So, wcb4xxp looks like it's running OK. >> >> BUT >> >> The config files that I've patched together from what google could find don't >> seem to be (quite) right. >> eg: >> Jun 18 17:16:35 pbx local0.warn asterisk[339]: WARNING[339]: >> chan_dahdi.c:7812 >> in handle_alarms: Detected alarm on channel 1: Red Alarm >> Jun 18 17:16:35 pbx local0.warn asterisk[339]: WARNING[339]: >> chan_dahdi.c:7812 >> in handle_alarms: Detected alarm on channel 2: Red Alarm >> Jun 18 17:16:35 pbx local0.warn asterisk[339]: WARNING[339]: >> chan_dahdi.c:7812 >> in handle_alarms: Detected alarm on channel 4: Red Alarm >> Jun 18 17:16:35 pbx local0.warn asterisk[339]: WARNING[339]: >> chan_dahdi.c:7812 >> in handle_alarms: Detected alarm on channel 5: Red Alarm >> Jun 18 17:16:35 pbx local0.warn asterisk[339]: WARNING[339]: >> chan_dahdi.c:4306 >> in dahdi_open: Unable to specify channel 7: No such device or address >> Jun 18 17:16:35 pbx local0.err asterisk[339]: ERROR[339]: chan_dahdi.c:12290 >> in >> mkintf: Unable to open channel 7: No such device or address here = 0, >> tmp->channel = 7, channel = 7 >> Jun 18 17:16:35 pbx local0.err asterisk[339]: ERROR[339]: chan_dahdi.c:16779 >> in >> build_channels: Unable to register channel '1-2,4-5,7-8,10-11' >> Jun 18 17:16:36 pbx local0.err asterisk[339]: ERROR[339]: codec_dahdi.c:579 >> in >> find_transcoders: Failed to open /dev/dahdi/transcode: No such file or >> directory >> >> and DAHDI STATUS in the Astlinux_GUI gives: >> No such command 'dahdi show status' (type 'core show help dahdi show' for >> other >> possible commands) >> >> I know I'm not far off!!! >> >> Thanks in advance, >> >> -Graham- >> >> >> Michael Keuter wrote on 14/06/12 22:45: >>> No, that card is supported by DAHDI out of the box. For some newer features >>> you need Asterisk 1.8.x. (CCBS, ...). If you used mISDN before, you need >>> to switch to DAHDI. >>> >>> There is a page about that in the Wiki. >>> >>> Sent from my iPad >>> >>> Michael >>> >>> Am 14.06.2012 um 22:03 schrieb "Graham S. Jarvis"<gsjar...@pt.lu>: >>> >>>> Hello All, >>>> >>>> now that I have my system booting...... >>>> (see: Booting problem - 1.0.3-Asterisk-1.4.44) >>>> >>>> I have a question about support for the Junghanns quadBRI (4-Port >>>> HFC-ISDN-card). >>>> >>>> I think you're going to tell me that I have to go back to 0.4.4 to have a >>>> system >>>> that supports the card. >>>> >>>> Thanks, >>>> >>>> -Graham- > > Here is a working "system.conf" with 4 ports PTP as slave: > ---------------------------- > > # Span 1: B4/0/1 "B4XXP (PCI) Card 0 Span 1" (MASTER) AMI/CCS > span=1,1,0,ccs,ami > # termtype: te > bchan=1-2 > hardhdlc=3 > echocanceller=oslec,1-2 > alaw=1-2 > > # Span 2: B4/0/2 "B4XXP (PCI) Card 0 Span 2" AMI/CCS > span=2,2,0,ccs,ami > # termtype: te > bchan=4-5 > hardhdlc=6 > echocanceller=oslec,4-5 > alaw=4-5 > > # Span 3: B4/0/3 "B4XXP (PCI) Card 0 Span 3" AMI/CCS > span=3,0,0,ccs,ami > # termtype: te > bchan=7-8 > hardhdlc=9 > echocanceller=oslec,7-8 > alaw=7-8 > > # Span 4: B4/0/4 "B4XXP (PCI) Card 0 Span 4" AMI/CCS > span=4,0,0,ccs,ami > # termtype: te > bchan=10-11 > hardhdlc=12 > echocanceller=oslec,10-11 > alaw=10-11 > > # Global data > loadzone = de > defaultzone = de > --------------------------------------------- > Here is the relevant part of chan_dahdi.conf: > > ; TE PTP > group=1 > signalling=bri_cpe > ; p2p TE mode => bri_cpe > ; p2mp TE mode => bri_cpe_ptmp > ; p2p NT mode => bri_net > ; p2mp NT mode => bri_net_ptmp > context=isdn_incoming > immediate=no > channel => 1-2,4-5,7-8,10-11 > callerid=asreceived > > > You don't need codec_dahdi, so put "noload => codec_dahdi.so" in your > modules.conf and restart Asterisk. > PTMP in NT mode does not work (very well). > > Michael > > http://www.mksolutions.info > > > > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > > > _______________________________________________ > Astlinux-users mailing list > Astlinux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pay...@krisk.org. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
