No subject


Sun Jul 19 19:54:31 CDT 2009


Max

--000e0cd4894e1258f70473ae0fee
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello!<div><br><div class=3D"gmail_quote">On Sat, Sep 12, 2009 at 3:59 PM, =
Hans Petter Selasky <span dir=3D"ltr">&lt;<a href=3D"mailto:hselasky at c2i.ne=
t">hselasky at c2i.net</a>&gt;</span> wrote:<br><div>=A0</div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex;">
<div><div class=3D"h5">&gt; &gt; The HFC-4S/8S cards are already supported =
by ISDN4BSD (FreeBSD 7,8,9).<br>
&gt; &gt;<br>
&gt; &gt; <a href=3D"http://www.selasky.org/hans_petter/isdn4bsd" target=3D=
"_blank">http://www.selasky.org/hans_petter/isdn4bsd</a><br>
&gt;<br>
&gt; They are, but ISDN4BSD requires non-stock chan_capi.<br>
<br>
</div></div>And what is the problem about that? The stock chan_capi used to=
 have some<br>
important features missing like dynamic config reload, and is not BSD<br>
licensed!</blockquote><div><br></div><div>I acidentally replied in private.=
 Re-sending to mailing list:</div><div><br></div><div><span class=3D"Apple-=
style-span" style=3D"font-family: arial, sans-serif; font-size: 13px; borde=
r-collapse: collapse; ">I am mostly concerned not about features (or licens=
e), but about maintainability.<br>


More information about the Asterisk-BSD mailing list