Currently being frustrated trying to compile the latest mISDN and after getting zero feedback from the isdn4linux list when I asked about it, so wondering whether to jump ship to bristuff... (All HFC based cards) mISDN has worked very well for me so-far - I have PBXs with 100+ days up time and 1000's of calls using it, so it'll be hard for me to jump ship as it were.. Although going over to a "unified" Zap structure does have it's advantages too ... So comments, ponderings or anecdotes, etc. ... ? Gordon
Gordon Henderson schrieb:> So comments, ponderings or anecdotes, etc. ... ?Bristuff worked perfectly fine for me for about 5 years. HOWEVER, you should keep in mind, that bristuff are very extensive patches against the zaptel dirvers and also against the core. So regarding updates you are totally depending on Junghanns. That means especially that there can be noticeable delay after an update of asterisk until the bristuff update is available. This *can* be bad if the update is a security update. Technically, I had very little problems. Even using a HFC-S card as internal ISDN bus worked like a charm. I just went to full IP because SIP trunks are cheaper in Finland than ISDN connections. Terve, Stefan -- Last words of a stormchaser: "Where is that rotation on the radar?!"
2008/9/8 Stefan Gofferje <list-asterisk-users at gofferje.homelinux.org>> Gordon Henderson schrieb: > > > So comments, ponderings or anecdotes, etc. ... ? > > > Unfortunately, I must say we had bitter experiences recently with bothmISDN and Bristuff : echo, CLI, available channels tagged as busy (see Bristuff mailing list). Anything that could change this situation would be welcome ... -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20080908/4f54500a/attachment.htm