Skip to content

voice4net/rtpengine-systemd

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

37 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Running the RTPEngine Under Systemd Control

To run the RTPEngine under systemd control, follow these steps:

Clone the repository to your local machine:

# git clone https://github.com/voice4net/rtpengine-systemd.git

# cd rtpengine-systemd

Edit the configuration file "rtpengine-conf " to reflect your configuration. Then install the files in your system:

# cp rtpengine-conf /etc/default/rtpengine-conf

# cp rtpengine.service /usr/lib/systemd/system/rtpengine.service

#  cp rtpengine-start /usr/bin/rtpengine/rtpengine-start
#  cp rtpengine-stop-post /usr/bin/rtpengine/rtpengine-stop-post

# chmod +x /usr/bin/rtpengine/rtpengine-start

# chmod +x /usr/bin/rtpengine/rtpengine-stop-post

In the systemd unit file, the option "ExecStopPost" is used to clean the system after the RTPEngine daemon is stopped. This involves: deleting the forwarding table, the iptables related rules, and unload the kernel module (xt_RTPENGINE).

Now you can enable/start/stop/status of the rtpengine service as following:

# systemctl enable rtpengine.service

# systemctl start rtpengine.service

# systemctl status rtpengine.service

# systemctl stop rtpengine.service

If you do enable, then the rtpengine will be automatically started by the systemd after boot.

Note: This work is a translation of the SipWise ngcp-rtpengine-daemon.init script to what Systemd needs.

About

Runing Sipwise RTPEngine Under Systemd Control

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Shell 100.0%