Forge Home

rtpengine

This module installs, configure and manages Sipwise NGCP rtpengine.

4,599 downloads

3,900 latest version

5.0 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 1.0.2 (latest)
  • 1.0.1
  • 1.0.0
released Aug 2nd 2019
This version is compatible with:
  • Puppet Enterprise 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2016.4.x
  • Puppet >= 4.10.0 < 7.0.0
  • , , ,

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'alisio-rtpengine', '1.0.2'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add alisio-rtpengine
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install alisio-rtpengine --version 1.0.2

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download

Documentation

alisio/rtpengine — version 1.0.2 Aug 2nd 2019

rtpengine

Table of Contents

  1. Description
  2. Setup
  3. Usage
  4. Limitations
  5. Development

Description

This module installs, configure and manages Sipwise NGCP rtpengine.

The Sipwise NGCP rtpengine is a proxy for RTP traffic and other UDP based media traffic. It's meant to be used with the Kamailio or OpenSIPS SIP proxy and forms a drop-in replacement for any of the other available RTP and media proxies.

For more information please refer to the project repository: https://github.com/sipwise/rtpengine

Setup

This module affects the following:

  • Adds yum repositories for dependencies
  • Installs rtpengine and dependencies packages
  • Enables rtpengine service

Setup Requirements

This module requires Kamailio or OpenSIPS SIP proxy with the apropriate rtpengine module loaded.

The following snippet illustrates the rtpengine.so module config on opensips:

loadmodule "rtpengine.so"
modparam("rtpengine", "rtpengine_sock", "udp:127.0.0.1:22223") # CUSTOMIZE ME

For more information on how to configure rtpengine module on OpenSIPS please refer to the rtpengine Admin guide

Beginning with rtpengine

All you need to get this module up and running is calling the class:

include rtpengine

Usage

class{'rtpengine':
  rtpengine_min_port => 10000,
  rtpengine_max_port => 20000,
  repo_install      => false,
}

Parameters

  • $repo_install Boolean variable that controls if this module should config the required repositories. Default to true
  • $rtpengine_ctrl_socket String containing either just a port number, or an address:port pair, separated by colon, of the control socket. Default to '127.0.0.1:22223'
  • $rtpengine_listen_interface Specifies a local network interface for listening to the RTP packets. Default to the Ip address of the first ethernet interface
  • $rtpengine_min_port Integer defining the minimum local port from which rtpengine will allocate UDP ports for media traffic relay. Default to 30000.
  • $rtpengine_max_port Integer defining the maximum local port from which rtpengine will allocate UDP ports for media traffic relay. Default to 40000.
  • $rtpengine_max_sessions Integer defining the limit the number of maximum concurrent sessions. Default to 16000
  • $rtpengine_syslog_local Integer. Syslog level for opensips and rtpproxy log. Default to 5

Reference Reading

Limitations

This module was tested on CentOS 7 with OpenSIPS 2.4

Development

Please follow the licence guidelines