-
Notifications
You must be signed in to change notification settings - Fork 6
SetupRHEL
-
If you're using RHEL5,6 or derivatives then you must install EPEL support first.
-
Build erlrtpproxy, erlang-rtplib and erlrtpproxy-ser RPMs. Also you might be interested in erlrtpproxy-radius RPM as well, but that's optional. You may download SRPM packages here. Prebuilt RPMs are also available.
-
Install erlrtpproxy (it will create erlrtpproxy user during installation) and erlang-rtplib via yum on each machine in your cluster
-
Raise max number of open files in
/etc/security/limits.conf
. -
Edit
/var/lib/erlrtpproxy/.hosts.erlang
. It should contain something like this:'192.168.100.1'.
'192.168.100.2'.
-
Edit
/var/lib/erlrtpproxy/.erlang.cookie
(it must exist on every host available in cluster and must contain the same value). No newlines are allowed (note-n
switch):echo -n `echo -n "yourpassphrase" | md5sum | cut -d " " -f 1 ` > /var/lib/erlrtpproxy/.erlang.cookie
chmod 600 /var/lib/erlrtpproxy/.erlang.cookie
chown erlrtpproxy:erlrtpproxy /var/lib/erlrtpproxy/.erlang.cookie -
Install OpenSSH public keys from main machine on every node. user erlrtpproxy from main node must be able to log in w/o password on every other note - ensure that trying to login manually. Note that w/o manually login first Erlang will refuse to login because of unknown host's fingerprint.
-
Edit
/etc/sysconfig/erlrtpproxy
config. At least you will need to adjust ERL_NODE value. -
Edit
/etc/erlrtpproxy.config
. You'll need to adjust syslog's address (only UDP is supported for now) and rtpproxy_radius settings (if you decide to use it). -
Install erlrtpproxy-ser on main node only (where your rtpproxy is running) and change
/etc/sysconfig/ser
according to your own setup. At least you will need to adjust ERL_NODE value. -
Edit
/etc/ser.config
. You need at least to provide address to listen for OpenSER/OpenSIPs/Kamailio commands at. -
Start erlprtpproxy first as any other system daemon by typing:
/etc/init.d/erlrtpproxy start
-
Start erlprtpproxy-ser controlling module as any other system daemon by typing:
/etc/init.d/ser start
-
Take a look at syslog's output (
/var/log/messages
) for details.