Jump to content
Vodia PBX forum
rob al

[HOWTO] install on 64bit Ubuntu/Debian

Recommended Posts

I found a pretty easy way to get this installed on 64bit Ubuntu, so i thought i'd share:

1. Download the Deb from the wiki e.g. on thsi page http://wiki.snomone.com/index.php?title=Installers_(Release_4.5):

wget http://downloads.snom.net/snomONE/debian/v4.5/snomone_4.5.0.1075-i386.deb

2. Unpack it:

mkdir snomone
dpkg -x snomone_4.5.0.1075-i386.deb ./snomone

3. Copy the app to the install dir

sudo mkdir /usr/local/snomONE
sudo cp ./snomone/usr/local/snomONE /usr/local/snomONE
sudo chown -r root:root /usr/local/snomONE

4. Install the startup script:

sudo cp ./snomone/etc/init.d/snomONE /etc/init.d/snomONE
sudo chmod +x /etc/init.d/snomONE
sudo update-rc.d snomONE defaults

5. get find the latest update from the wiki e.g. http://wiki.snomone.com/index.php?title=Upgrades_(Release_4.5), and download the Centos64 bit binary e.g.

wget http://downloads.snom.net/snomONE/centos64/v4.5/pbxctrl-centos5-4.5.0.1090

6. rename, change the owner of the files + make the main file executable:

cp pbxctrl-centos5-4.5.0.1090 /usr/local/snomONE/pxbctrl
sudo chown root:root /usr/local/snomONE/pxbctrl
sudo chmod +x /usr/local/snomONE/pxbctrl

7. Start service:

sudo service snomONE start

 

and hey presto! you should be able to browse to your server on port 80!

 

You can repeat steps 5 and 6 to upgrade (stop the service first). Don't use the updater built in to the product as this will download the 32bit version.

Share this post


Link to post
Share on other sites

It works. Some comments:

 

  • I would start with "cd /tmp"
  • should be "chown -R" and not "chown -r"
  • "pxbctrl" should be "pbxctrl"
  • To start the service on debian use "/etc/init.d/snomONE start"

Share this post


Link to post
Share on other sites

I found a pretty easy way to get this installed on 64bit Ubuntu, so i thought i'd share:

1. Download the Deb from the wiki e.g. on thsi page http://wiki.snomone....rs_(Release_4.5):

wget http://downloads.snom.net/snomONE/debian/v4.5/snomone_4.5.0.1075-i386.deb

2. Unpack it:

mkdir snomone
dpkg -x snomone_4.5.0.1075-i386.deb ./snomone

3. Copy the app to the install dir

sudo mkdir /usr/local/snomONE
sudo cp ./snomone/usr/local/snomONE /usr/local/snomONE
sudo chown -r root:root /usr/local/snomONE

4. Install the startup script:

sudo cp ./snomone/etc/init.d/snomONE /etc/init.d/snomONE
sudo chmod +x /etc/init.d/snomONE
sudo update-rc.d snomONE defaults

5. get find the latest update from the wiki e.g. http://wiki.snomone....es_(Release_4.5), and download the Centos64 bit binary e.g.

wget http://downloads.snom.net/snomONE/centos64/v4.5/pbxctrl-centos5-4.5.0.1090

6. rename, change the owner of the files + make the main file executable:

cp pbxctrl-centos5-4.5.0.1090 /usr/local/snomONE/pxbctrl
sudo chown root:root /usr/local/snomONE/pxbctrl
sudo chmod +x /usr/local/snomONE/pxbctrl

7. Start service:

sudo service snomONE start

 

and hey presto! you should be able to browse to your server on port 80!

 

You can repeat steps 5 and 6 to upgrade (stop the service first). Don't use the updater built in to the product as this will download the 32bit version.

 

Are folks still using these steps to install snom ONE on Ubuntu? I ask b/c I noticed that the downloadable on the snom ONE wiki is no longer a .deb, but an install script instead. Earlier today, I was able to install Deb64 (the script figured it out automatically) on a 64-bit Ubuntu Server 12.04 LTS. Everything went smoothly; so smoothly, in fact, that the forces that be could not have allowed that to happen and now I find myself troubleshooting why I can no longer connect via the PBX's web portal and why I'm not able to terminate a test call. blink.gif

Share this post


Link to post
Share on other sites

Everything went smoothly; so smoothly, in fact, that the forces that be could not have allowed that to happen and now I find myself troubleshooting why I can no longer connect via the PBX's web portal and why I'm not able to terminate a test call.

 

The PBX tries to bind to the sockets like 80, 443 which are protected sockets. In Linux, that might take a while if the socket was in use before and there are connections in wait state. This is an open issue; unfortunately not an easy one. Workaround is to wait for at least 60 seconds before restarting the service on Linux.

Share this post


Link to post
Share on other sites

The PBX tries to bind to the sockets like 80, 443 which are protected sockets. In Linux, that might take a while if the socket was in use before and there are connections in wait state. This is an open issue; unfortunately not an easy one. Workaround is to wait for at least 60 seconds before restarting the service on Linux.

 

Here's a random question: Would creating virtual hosts in Apache2, on ports 80 and 443, be a viable workaround?

Share this post


Link to post
Share on other sites

Here's a random question: Would creating virtual hosts in Apache2, on ports 80 and 443, be a viable workaround?

 

No. On the OS level there are just sockets. One a packet was routed into a process there is no way to put it back into the socket.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...