[asterisk-users] Dahdi and Junghanns QuadBRI

Olivier oza-4h07 at myamail.com
Thu Dec 10 07:39:38 CST 2009


2009/12/10 Tzafrir Cohen <tzafrir.cohen at xorcom.com>

> On Thu, Dec 10, 2009 at 11:23:18AM +0100, Olivier wrote:
> > 2009/12/9 Tzafrir Cohen <tzafrir.cohen at xorcom.com>
> >
> > > On Wed, Dec 09, 2009 at 05:59:36PM +0100, Olivier wrote:
> > > > Tzafrir,
> > > > Would you say latest trunk (revision 7672) includes a fix for those
> > > OctoBRI
> > > > boards ?
> > >
> > > The only change was in dahdi-tools . As could be clearly seen from the
> > > output of lspci, wcb4xxp already handles this device.
> > >
> >
> > I could successfully get :
> > # dahdi_hardware
> > pci:0000:08:00.0     wcb4xxp+     1397:16b8 Junghanns OctoBRI ISDN card
> > # lsmod | grep wcb
> > wcb4xxp                73060  24
> > dahdi                 184936  52 dahdi_echocan_oslec,wcb4xxp
> >
> > (Thanks again for that).
> > Unfortunately, I can dial from one port to another. Here is my config (I
> > plugged a cat5 straight cable from port 1 to port 8, port 1 jumper is set
> to
> > TE, port 8 jumper is set to NT with terminator ON)
> >
> > # cat dahdi-channels.conf
> > ....
> > ; Span 1: B4/0/1 "B4XXP (PCI) Card 0 Span 1" (MASTER)
> > group=1,11
> > context=remote
> > switchtype = euroisdn
> > signalling = bri_cpe
> > channel => 1-2
> > context = default
> > group = 63
> >
> > ....
> > ; Span 8: B4/0/8 "B4XXP (PCI) Card 0 Span 8"
> > group=1,18
> > context=remote
> > switchtype = euroisdn
> > signalling = bri_net
> > channel => 22-23
> > context = default
> > group = 63
> >
> >
> > # cat /etc/dahdi/system.conf
> > ....
> > #
> > # Span 1: B4/0/1 "B4XXP (PCI) Card 0 Span 1" (MASTER)
> > span=1,1,0,ccs,ami
> > # termtype: te
> > bchan=1-2
> > hardhdlc=3
> > echocanceller=oslec,1-2
> > ...
> > # Span 8: B4/0/8 "B4XXP (PCI) Card 0 Span 8"
> > span=8,0,0,ccs,ami
> > # termtype: nt
> > bchan=22-23
> > hardhdlc=24
> > echocanceller=oslec,22-23
> >
> >
> > dahdi_tool shows all ports with "Red Alarm" status.
> >
> > from my dialplan :
> > Dial(DAHDI/g1/0155669909); Call <mydialer:0155669909>
> > [Dec 10 11:17:36] WARNING[3129]: app_dial.c:1745 dial_exec_full: Unable
> to
> > create channel of type 'DAHDI' (cause 34 - Circuit/channel congestion)
>
> Incoming calls work?
>

I can't tell as I'm only able to connect one port to another (I don't have
available ISDN access).
As I've got another Junghanns PCIe board left, I'll try to mount a new
machine configured with NT service and check if this changes anything (I'll
connect one machine's TE port to the other machine's NT port).

PS: This PCIe board is not loading wcb4xx driver and produces :
# dahdi_hardware
pci:0000:06:04.0     qozap-       1397:08b4 Generic Cologne ISDN card

# lspci -v -nn -s 06:04
06:04.0 ISDN controller [0204]: Cologne Chip Designs GmbH ISDN network
Controller [HFC-4S] [1397:08b4] (rev 01)
        Subsystem: Cologne Chip Designs GmbH Device [1397:b752]
        Flags: medium devsel, IRQ 11
        I/O ports at ec00 [size=8]
        Memory at feaff000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [40] Power Management version 2

So, when building a new machine, I'll likely use bristuff and 1.4.



> --
>               Tzafrir Cohen
> icq#16849755              jabber:tzafrir.cohen at xorcom.com<jabber%3Atzafrir.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 --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20091210/1b9feca0/attachment-0001.htm 


More information about the asterisk-users mailing list