Experienced problems with asterisk and x-lite ?

Kilian Krause kk@verfaction.de
Sat, 22 Jan 2005 16:45:07 +0100


--=-2bExJBwn1R+TYmzqbpkr
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi Jose,

[chan_h323]
>  I still don't think that can work at all with asterisk 1.0.x  branch
> (stable). Or if that can be made, that it doesn't need a lot of work we
> seem not having now.

well, as you pointed out correctly, right now chan_h323 is broken
anyway. I vote for testing chan_h323 CVS HEAD on some platforms (i could
offer ppc, alpha, mips at least) and evaluate its readyness for shipping
into SID. If that proves ok, try to move 1.0.4+chan_h323-CVS-HEAD into
SID and thus SARGE if possible. We're having 1.0.3 in SID still
(including that security fix), but using the official 1.0.4 should be
even better and more transparent for the user. As this is security
related we should be getting it into SARGE quite easily.

If chan_h323 CVS HEAD proves to at least work for some situations, maybe
ship with both h323 and oh323 but make asterisk-oh323 the new default.

Objections? Comments?

--=20
Best regards,
 Kilian

--=-2bExJBwn1R+TYmzqbpkr
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Dies ist ein digital signierter Nachrichtenteil

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBB8nUDvdkzt4X+wX8RAlaMAJ45g996CI1243ja1aSoTtMlqzgKXgCdG8HU
aaKQAboEKol33FiF907IxBI=
=Ytup
-----END PGP SIGNATURE-----

--=-2bExJBwn1R+TYmzqbpkr--