[asterisk-r2] openr2 support with HFC-E1 card

[Yue Chen]

Can you give me any clue which driver should I use? Or I can only use Diguim
and Sangoma E1 card for openr2? Thanks so much!

Yue

On Fri, Jan 9, 2009 at 7:40 PM, Moises Silva <moises.silva at gmail.com> wrote:

> This board works with a complete different driver, not zaptel nor
> DAHDI, therefore you cannot use chan_zap or chan_dahdi with it.
>
> On Fri, Jan 9, 2009 at 6:38 PM, Melcon Moraes <melcon at gmail.com> wrote:
> > I have no idea where to start from. :)
> >
> > Never heard about that card, so:
> >
> > 1. If somehow it works with Zaptel/chan_zap you shouldn't use asterisk
> > 1.6 because DAHDI/chan_dahdi are the new zap*
> > 2. If the software that works only with zaptel is for BRI, I think it
> > will work  for you, since you need software for PRI.
> >
> > For the iten 1, asterisk 1.4.21 is the last with zaptel/chan_zap on
> > it. After that only dahdi stuff. There's a patch  for it here(Kudos to
> > Moy for that): http://www.moythreads.com/openr2-asterisk-1.4.21.2.patch
> >
> >
> > I'm sorry I couldn't be of more help.
> >
> > -MM
> >
> > On Fri, Jan 9, 2009 at 9:46 PM, Yue Chen <dspfac at gmail.com> wrote:
> >> Hi Everyone,
> >>
> >> I am new to both Asterisk and Openr2 so forgive me in advance for
> lacking of
> >> enough background knowledge (I am trying hard to catch up ...). I am
> >> building a project involves single port HFC-E1 card. I started with
> Asterisk
> >> 1.6 mfcr2 branch and can build everything without problem. The E1 card
> came
> >> with mISDN driver and it was installed. The name of the driver is
> hfcmulti.
> >>
> >> I did lspci and it give me the card physical information.
> >>
> >> 04:00.0 ISDN controller: Cologne Chip Designs GmbH ISDN network
> Controller
> >> [HFC- E1] (rev 01)
> >>
> >> When I do a dahdi_hardware, the system tells me
> >>
> >> driver should be 'cwain' but is actually 'hfcmulti'
> >> pci:0000:04:00.0 cwain+ 1397:30b1 HFC-E1 ISDN E1 card
> >>
> >> Apparently something is wrong. If my understanding is right, I should
> not
> >> use mISDN driver since it does not play with zaptel and chan_zap. It
> only
> >> works with chan_misdn. The cwain driver is maintained by junghanns.netas
> >> part of bristuff package which support BRI and zaptel. But I am not sure
> >> this is right. Before digging into the unknowns, I want to ask for some
> >> directions here. Thanks for help.
> >>
> >> Regards,
> >>
> >> ychen
> >>
> >> _______________________________________________
> >> --Bandwidth and Colocation Provided by http://www.api-digital.com--
> >>
> >> asterisk-r2 mailing list
> >> To UNSUBSCRIBE or update options visit:
> >>   http://lists.digium.com/mailman/listinfo/asterisk-r2
> >>
> >
> > _______________________________________________
> > --Bandwidth and Colocation Provided by http://www.api-digital.com--
> >
> > asterisk-r2 mailing list
> > To UNSUBSCRIBE or update options visit:
> >   http://lists.digium.com/mailman/listinfo/asterisk-r2
> >
>
>
>
> --
> "I do not agree with what you have to say, but I'll defend to the
> death your right to say it." Voltaire
>
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-r2 mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-r2
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-r2/attachments/20090109/b45a9a97/attachment.htm