Asterisk 11 And Pulseaudio Setup As Local User

Home » Asterisk Users » Asterisk 11 And Pulseaudio Setup As Local User
Asterisk Users 6 Comments

I am trying to get Asterisk 11 to co-exist with a CentOS 7 box that has pulse audio running as a local user.

Has anyone done that?
What is the trick?

I changed directories

/var/run/asterisk, 
/var/spool/asterisk,
/var/log/asterisk,
/usr/lib/asterisk, 
/etc/dahdi and all that stuff.

The console channel gets errors on opening.

Thanks,

6 thoughts on - Asterisk 11 And Pulseaudio Setup As Local User

  • alsa_card_init^[[0m: snd_pcm_open failed: Connection refused soundcard_init^[[0m: Problem opening alsa capture device

    These are the errors I get.

    I changed the following:
    chown -R myuser:myuser /var/log/asterisk chown -R myuser:myuser /var/lib/asterisk chown -R myuser:myuser /var/spool/asterisk chown -R myuser:myuser /var/run/asterisk chown -R myuser:myuser /usr/lib/asterisk edited asterisk.conf and uncommented runuser and rungroup and changed to myuuser

    Then I get the above error when running

    Jerry

  • Am 3. Juli 2015 13:17:34 MESZ, schrieb Jerry Geis :

    Sounds more like wrong perms on the sound devices in /dev. Is your user in the audio group, or whatever it’s called on your box?

  • Ok digging deaper… I was always trying to run the session as su myuser -c “asterisk -fn”

    This does not seem to work.

    If I login as myuser and run “asterisk fn” it worked… I got a lot of crackly noise that I normally dont have but it worked.

    Any thoughts on why I cannot run the command as ‘su myuser -c “asterisk
    -fn”‘ ?

    Thanks

    jerry

  • If the problem is a permission thing I’d confirm that.

    Run Asterisk as root and see if the problem goes away.

    If so then you’ll have to work your way through devices and drivers and check who owns them and is able access them.

    I’d also try temporarily disabling SELinux to see if that helps.

    As with the first option this would be temporary – go back to running Asterisk as myuser or whatever and reenable SELinux regardless of the outcome.