module-assistant support for zaptel

[Kilian Krause]

--=-qOo4WzY9ecoFb3Cj1bQb
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi Jose,

-(snip: all in SVN)-
great work! Thanks!

>  Last, I have a comment to make on device ownership. When we create them
> by hand, when udev or devfs is not being used, we set the ownership for
> them as root.dialout. At the same time, asterisk is being runned as
> asterisk.asterisk, and user asterisk is only added to audio group. Here
> there is a lack of coordination. Or we think that zaptel is going to be
> used only by asterisk, and we make devices as root.asterisk (which has
> the problem of failing if asterisk is not installed), or we add asterisk
> to dialout group, which has the problem of giving with thas asterisk
> power to lauch modem calls (using ppp, for example)

well, i'm not entirely sure what we should do with asterisk-chan-capi
with respect to this, but to me the whole VoIP in asterisk comes more as
a "comm" rather than "sound", thus i originally chose dialout. As zaptel
itself reads "sound" as Section, I could live very well with imposing
root.audio as permissions.
Yet this should be consequently thought through with chan-capi and
chan-misdn. Moreover there's chan_modem_i4l support in asterisk, which
needs to access /dev/ttyI having by default root.dialout permissions.
Thus long term it does sound wisest to put asterisk in audio _and_
dialout on the one hand, zaptel devices initialized root.audio
(consistent with Section: sound) on the other and check that chan-capi
and chan-misdn have root.dialout permissions access where needed.

--=20
Best regards,
 Kilian

--=-qOo4WzY9ecoFb3Cj1bQb
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)

iD8DBQBCRTdpvdkzt4X+wX8RAksOAJ9H+Lx7uKjSxq2+WQOMFhLTVBJ5HwCeOnrx
UydSlFp5+35GePXVniG2TOQ=
=EtP6
-----END PGP SIGNATURE-----

--=-qOo4WzY9ecoFb3Cj1bQb--