Olivier
2012-Jun-21 09:30 UTC
[asterisk-users] Asterisk 10/1.6.1 and Dahdi/Libpri compatilities in BRI /PtmP
Hi, After an upgrade, I discovered yesterday strange things I would like to share here. Basically, I'me comparing platforms: The first one is a 2.6.26 (Debian Lenny) platform, with Asterisk 1.6.1.18, Libpri 1.4.10.2, Dahdi revision 8853 (must be between 2.3 and 2.5, I think). The second one is a 2.6.32 (Debian Squeeze) platform, with Asterisk 10.5.1, Libpri 1.4.12, Dahdi 2.6.1. Both are connected to telco BRI lines in TE/PtmP mode through a Junghanns QuadBRI board (wcb4xxp driver). Both handle incoming and outgoing calls correctly, as far as I can tell. But on the second one, though working fine, Dahdi keeps showing alarm messages such as: [71765.784120] wcb4xxp 0000:01:0e.0: new card sync source: port 1 [71767.484151] wcb4xxp 0000:01:0e.0: new card sync source: port 1 [71771.184119] wcb4xxp 0000:01:0e.0: new card sync source: port 2 [71794.184164] wcb4xxp 0000:01:0e.0: new card sync source: port 1 and "pri show spans" mostly (but not always) report worrying status: PRI span 1/0: Down, Active PRI span 2/0: In Alarm, Down, Active On the first box "pri show spans" constantly reports the line is up. On thing to note is I had to forbid hfcmulti in modprobe.d in the second box to comply with a warning from dahdi. Without that, I could see this line in the output of lsmod: mISDN-core
Olivier
2012-Jun-21 09:37 UTC
[asterisk-users] Asterisk 10/1.6.1 and Dahdi/Libpri compatilities in BRI /PtmP
My previous message was incomplete. On thing to note is I had to forbid hfcmulti in modprobe.d in the second box to comply with a warning from dahdi. Without that, I could see this line in the output of lsmod: mISDN-core hfcmulti 1. What is the root cause that makes a board change its sync source ? How can I check this ? 2. How can I get rid of these alarms ? 3. Shall I report this ? 4. Waht would you suggest ? Regards 2012/6/21, Olivier <oza_4h07 at yahoo.fr>:> Hi, > > After an upgrade, I discovered yesterday strange things I would like > to share here. > > Basically, I'me comparing platforms: > The first one is a 2.6.26 (Debian Lenny) platform, with Asterisk > 1.6.1.18, Libpri 1.4.10.2, Dahdi revision 8853 (must be between 2.3 > and 2.5, I think). > The second one is a 2.6.32 (Debian Squeeze) platform, with Asterisk > 10.5.1, Libpri 1.4.12, Dahdi 2.6.1. > Both are connected to telco BRI lines in TE/PtmP mode through a > Junghanns QuadBRI board (wcb4xxp driver). > Both handle incoming and outgoing calls correctly, as far as I can tell. > > But on the second one, though working fine, Dahdi keeps showing alarm > messages such as: > [71765.784120] wcb4xxp 0000:01:0e.0: new card sync source: port 1 > [71767.484151] wcb4xxp 0000:01:0e.0: new card sync source: port 1 > [71771.184119] wcb4xxp 0000:01:0e.0: new card sync source: port 2 > [71794.184164] wcb4xxp 0000:01:0e.0: new card sync source: port 1 > > and "pri show spans" mostly (but not always) report worrying status: > PRI span 1/0: Down, Active > PRI span 2/0: In Alarm, Down, Active > > On the first box "pri show spans" constantly reports the line is up. > > On thing to note is I had to forbid hfcmulti in modprobe.d in the > second box to comply with a warning from dahdi. Without that, I could > see this line in the output of lsmod: > mISDN-core >
Olivier
2012-Jun-25 15:22 UTC
[asterisk-users] Asterisk 10/1.6.1 and Dahdi/Libpri compatilities in BRI /PtmP
2012/6/25, Tzafrir Cohen <tzafrir.cohen at xorcom.com>:> On Fri, Jun 22, 2012 at 08:07:54PM +1200, Alec Davis wrote: >> Have a look at the latest blacklist sample in dahdi trunk >> http://svnview.digium.com/svn/dahdi/tools/trunk/blacklist.sample?view=log >> >> file: blacklist.sample >> ... >> # Some mISDN drivers may try to attach to cards supported by DAHDI. If >> you >> # have a card which is *not* supported by DAHDI but supported by one of >> the >> # below drivers you should feel free to remove it from the blacklist >> below. >> blacklist hfcmulti > > May collide with wcb4xxp > >> blacklist netjet > > May collide with wctdm and some other older drivers. > >> blacklist hfcpci > > May collide with zaphfc.May I ask where I can get this zaphfc from ? Is this the same refered to as vzaphfc (see http://www.voip-info.org/wiki/view/Asterisk+vzaphfc) ?> > -- > Tzafrir Cohen > icq#16849755 jabber:tzafrir.cohen at xorcom.com > +972-50-7952406 mailto:tzafrir.cohen at xorcom.com > http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >