Subsequent to some previous E-Mails, I've been trying to dig into the ISDN - BRI situation a bit more. I have determined that I have a HFC card with Winbond chip, but I'm not sure what combination of drivers is best or usable. zaphfc is out because it only supports the cologne chip. misdn is a possibility. I haven't determined if it supports the card natively, or needs a card specific driver under it. capi is a possibility, but again, I don't know what driver, if any needs to be under it. capi can support misdn under it, but I don't know if this is an advantage or not, and again whether a card driver needs to be under misdn libpri 1.4.4 is supposed to work, provided you unpatch the bad patch in the source and compile it--again, I'm not sure what driver, if any needs to be under it. F9 detected the card and loaded some sort of driver support for it, but I don't know if that covers the lower levels appropriately. Can anyone provide more specific information or suggest which of these approaches is most likely to work, most likely to be stable, or supported for the future, or support the most features? It would appear there are at least four possible ways that might work, but I can't determine which is best. Thanks, Wilton -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20081030/b42b1e53/attachment.htm
On Thu, Oct 30, 2008 at 12:44:40PM -0600, Wilton Helm wrote:> Subsequent to some previous E-Mails, I've been trying to dig into the ISDN - BRI situation a bit more. I have determined that I have a HFC card with Winbond chip, but I'm not sure what combination of drivers is best or usable. > > zaphfc is out because it only supports the cologne chip.The HFC chip is "the cologne chip". The HFC-S chip is used in various common single-port ISDN cards.> > misdn is a possibility. I haven't determined if it supports the card natively, or needs a card specific driver under it. > > capi is a possibility, but again, I don't know what driver, if any needs to be under it. > > capi can support misdn under it, but I don't know if this is an advantage or not, and again whether a card driver needs to be under misdn > > libpri 1.4.4 is supposed to work, provided you unpatch the bad patch in the source and compile it--again, I'm not sure what driver, if any needs to be under it.This is if you have zaphfc.> > F9 detected the card and loaded some sort of driver support for it, but I don't know if that covers the lower levels appropriately. > > Can anyone provide more specific information or suggest which of these approaches is most likely to work, most likely to be stable, or supported for the future, or support the most features? It would appear there are at least four possible ways that might work, but I can't determine which is best. > > Thanks, > Wilton-- 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
Seemingly Similar Threads
- ISDN BRI NetJet
- Asterisk 1.4 and ISDN-BRI support
- Anyone here using JUNGHANNS.net douBRI 2.0 ISDN ?
- mISDN trouble with a HFC Cologne card, Asterisk Asterisk 1.2.4 on Linux 2.6.16.11 - incoming DTMF detection
- zaphfc - hfc pci based ISDN card : point2point & DDI