Skip to content

Restcomm OSX native installation

Antonis Tsakiridis edited this page Aug 31, 2017 · 10 revisions
  • Install ipcalc, tmux, xmlstarlet and gnu-sed (I'm using brew, but feel free to use any method)
$ brew install ipcalc tmux xmlstarlet gnu-sed
  • Navigate to bin directory
cd RESTCOMM/bin/restcomm
  • Setup your networking at restcomm.conf. For me it is:
# Network configuration
NET_INTERFACE='en4'
PRIVATE_IP='192.168.2.2'
SUBNET_MASK='225.255.255.0'
NETWORK='192.168.2.0'
BROADCAST_ADDRESS='192.168.2.255'
#hostname of the server to be used at restcomm.xml. If not set the STATIC_ADDRESS will be used.
RESTCOMM_HOSTNAME='antoniss-mbp'

Important: Above I'm setting RESTCOMM_HOSTNAME and as a result if you use a self-signed certificate, then the hostname is used as certificate CommonName. The great thing about this, especially when working on a host that updates its IP regularly via DHCP, is that even if the IP changes, there will not be a issue with trust of the server certificate, as the hostname remains the same. If on the other hand you don't set RESTCOMM_HOSTNAME, the IP address would be used as SubjectAlternativeName.IPAddress when generating the certificate, which would cause issues if IP changed after certificate generation. For me this issue manifested itself when Restcomm Connect tried to download RCML when receiving a call at Number associated with an RCML App, which failed with SIP/2.0 500 Problem to setup the call.

  • Make sure that the hostname used above is dns resolvable to PRIVATE_IP, typically by updating /etc/hosts accordingly. For example for me /etc/hosts is as follows:
...
192.168.2.2   antoniss-mbp
...
  • Add VOICERSS key in restcomm.conf (to get text to speech functionality)
VOICERSS_KEY=<your key>
  • Make sure you have Java 1.7 so that JBoss AS 7.2.0 can run (not 1.8). Check it with:
$ java -version
  • Make sure JAVA_HOME env variable is there and points to the correct java home. For me it is:
$ export JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home
  • Enable encrypted communications with self-signed certificate (notice this is just for testing purposes, NOT be used in production) by editing advanced.conf like so:
#! /bin/bash

...
SECURESSL=SELF
...
  • Execute gsed_macos.sh that will replace all occurrences of sed with gsed so that scripts work properly on OSX.

  • Start Restcomm Connect as usual:

./start-restcomm.sh