Re: Using mISDN+CAPI with asterisk on RasperryPI
Jan Neuhäußer <[email protected]> Tue, 03 Oct 2017 22:42:36 +0200
| Newsgroups | gmane.linux.isdn.i4l.user |
|---|---|
| Message-ID | <3427710.n6TajDOkEZ@tobi15> |
Hi Maciej,
Am Mittwoch, 27. September 2017, 23:50:25 CEST schrieb Maciej S. Szmigiero:
> 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
> >
> > 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,
Thanks for that hint, I changed the permissions of the directory and had success, but I had to set owner and group to asterisk:
After mISDNcapid started I found permissions 750, owner root, group dialout. Neither 770 nor 777 was successfull. At the end I created the directory before starting mISDNcapid, changed the permissions to 770 and the ownership to asterisk.asterisk.
> 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
Didn't check that, because the above helped.
Cheers,
Jan