SIPfoundry.org sipXphone Ebuild for Gentoo Linux
From SIPfoundry sipx, The Open Source SIP PBX for Linux - Calivia
Contents |
[edit] Configure the Portage Overlay directory
Ebuilds should not be placed within the standard portage tree. Every time an 'emerge sync' is performed, local changes are lost. Portage can be configured to look for ebuilds in 'overlay directories'.
| Code: Create the portage overlay directory |
mkdir /usr/local/portage |
| Code: Add Portage overlay to /etc/make.conf |
echo 'PORTDIR_OVERLAY="/usr/local/portage"' >> /etc/make.conf |
[edit] Checkout Ebuilds and Related Files using Subversion
The fastest way to get the ebuilds is by checking them out using Subversion. If you do not have Subversion itself on your system, emerge it now. You can disable the installation of Apache by adding USE="-apache2".
| Code: Emerge Subversion |
USE="-apache2" emerge --ask subversion |
| Code: Subversion Checkout |
mkdir /usr/local/portage/net-misc cd /usr/local/portage/net-misc # Check out sipXphone ebuild files svn checkout http://sipx-wiki.calivia.com/svn/sipx-ebuilds/net-misc/sipxportlib/ svn checkout http://sipx-wiki.calivia.com/svn/sipx-ebuilds/net-misc/sipxtacklib/ svn checkout http://sipx-wiki.calivia.com/svn/sipx-ebuilds/net-misc/sipxcalllib/ svn checkout http://sipx-wiki.calivia.com/svn/sipx-ebuilds/net-misc/sipxmedialib/ svn checkout http://sipx-wiki.calivia.com/svn/sipx-ebuilds/net-misc/sipxphone/ |
[edit] Emerge sipXphone
Audio is provided by sipXmediaLib. Local audio support will be enabled if alsa and oss are in your USE flags.
| File: /etc/make.conf |
# Add ALSA and OSS to your USE flags USE="alsa oss" |
Currently, only the development branch 'main' supports local audio and STUN. sipXphone does not build with sipX-libraries from the 2.8 branch. Issue the following to make sure development versions of the four required libraries are built.
| Code: Unmask sipXphone ebuild |
echo 'net-misc/sipxportlib ~x86' >> /etc/portage/package.keywords echo 'net-misc/sipxtacklib ~x86' >> /etc/portage/package.keywords echo 'net-misc/sipxcalllib ~x86' >> /etc/portage/package.keywords echo 'net-misc/sipxmedialib ~x86' >> /etc/portage/package.keywords echo 'net-misc/sipxphone ~x86' >> /etc/portage/package.keywords |
The following command first builds the development version 2.9 of sipXportLib, sipXtackLib, sipXcallLib and sipXmediaLib before building sipXphone.
| Code: Emerge sipXphone |
emerge --ask net-misc/sipxphone |
(In my case, WANT_AUTOMAKE=1.6 emerge --ask net-misc/sipxphone, had to be used; spblinux)
[edit] Start sipXphone
| Code: Start sipXphone |
cd /usr/local/sipx/bin && ./sipXphone.sh |
Enable the phone's web server by pressing 'More'. After restarting the phone you can access it with your browser.
[edit] Troubleshooting
[edit] Configuration
Default configuration directory:
/usr/local/sipx/share/sipxphone
User specific configuration directory:
~/.sipxphone
A set of default configuration files is copied to ~./sipxphone by the sipXphone.sh startup script. Also refer to SipXphone_Configuration_Files
[edit] Sound
sipXphone uses OSS, which together with the /dev/dsp device should be present on most desktop linux systems.
Using the ALSA driver compiled into the kernel should work fine. Using the ALSA module is for people who want the most recent ALSA code independently of their current kernel version.
KMix (kmix) can be used to tune volumes. Remember that you have to turn on "Mic" or "Capture" or possibly another input based on your sound device under the "Input" tab for the microphone to work.
Calling the FWD Echo service (this works without registering the phone with FWD. Make sure your firewall/NAT allows the phone to call an external IP address)
Call by URL: sip:613@fwd.pulver.com
[edit] Starting the Web server
The sipXphone softphone’s Web server runs directly on the PC and provides access to files that are stored on that PC. For security reasons, this Web server does not start automatically after emerging sipXphone.
| Code: Starting the built-in Web server |
|
To start the Web server, you perform these steps using the phone's UI:
|
After turning on the phone's internal Web server try netstat -lnt to verify that the port specified for the Web server is open.
