Re: Using mISDN+CAPI with asterisk on RasperryPI
"Maciej S. Szmigiero" <[email protected]> Wed, 27 Sep 2017 23:50:25 +0200
| Newsgroups | gmane.linux.isdn.i4l.user |
|---|---|
| Message-ID | <[email protected]> |
Hi Jan,
On 27.09.2017 22:47, Jan Neuhäußer wrote:
> Dears,
>
> I recompiled chan_capi and got a step further, but only a little:
(..)
> socket(PF_LOCAL, SOCK_SEQPACKET, 0) = 19
> connect(19, {sa_family=AF_LOCAL, sun_path="/run/mISDNcapid/sock"}, 110) = -1 EACCES (Permission denied)
> close(19) = 0
>
> (/var/run or /run makes no difference, one is a softlink to the other, (/var/run -> /run) )
>
> The rights on the socket were as follows:
>
> root@raspbx:/run/mISDNcapid# ls -l
> insgesamt 0
> srw-rw-rw- 1 root dialout 0 Sep 26 21:34 sock
>
> Still asterisk is member of group dialout.
>
You can also check permissions of /run/mISDNcapid directory itself,
if this does not help then check if supplementary group list of the asterisk
process includes the dialout group, that is, if id of this group is in "Groups:"
line of /proc/PID/status (but because this socket has rw access also for other users
only the parent directory permissions should matter).
I remember there was a bug (at least on Gentoo) that Asterisk was being started
without any supplementary groups.
Otherwise, it might be something like SELinux blocking the access?
> Cheers,
> Jan
Maciej
_______________________________________________
isdn4linux mailing list
[email protected]
https://www.isdn4linux.de/mailman/listinfo/isdn4linux