The main issue I have with running RTPEngine containers in host network mode is that they then cannot simultaneously participate in internal/overlay container networks, defeating efforts to manage them with various orchestration architectures.

Sent from mobile, with due apologies for brevity and errors.

On Feb 10, 2020, at 11:12 AM, Sergey Safarov <s.safarov@gmail.com> wrote:


> enable 1-to-1 NAT for RTP port range between host and vm (i recommend using iptables for this instead of using docker port expose feature).
More simple start container with host network

On Mon, Feb 10, 2020 at 7:02 PM M S <shaheryarkh@gmail.com> wrote:
You would need to install kernel module in host machine, only then it will be available in docker container. You will also need to mark container as privileged container and enable 1-to-1 NAT for RTP port range between host and vm (i recommend using iptables for this instead of using docker port expose feature).

Regarding RTPE compilation, yes it is quite difficult on Ubuntu 18.04. You have to tweak <git-repo>/debian/control file and manually add compat file. Also there are various dependencies that are not listed in wiki and cause problem in installation of deb packages, which you can install later on after reading the error messages.

As for install order, for me "dpkg -i *.deb" works fine and i control which features to use and which not from config file. Otherwise just install whatever seems appropriate to you, don't worry dpkg will install other ngcp-* packages as needed.

Hope this helps.


On Mon, 10 Feb 2020, 11:03 Voip support, <voipexpert0@gmail.com> wrote:
Dear Community,

I would like to use rtpengine but had a very hard time to do the compilation under ubuntu 16.04 and 18.04. 

On Ubuntu 18.04 after already compiled the rtpengine i was unable to install the deb packages.
Many different errors occurred.

I finally tried to install RTP engine on debian 10 and i was able to install it.

I am thinking of 2 use scenarios: 
- handling many concurrent calls like using rtpproxy for normall traffic
- make WebRTC to legacy RTP transcoding (convert WebRTC SDP to legacy SDP to use with non webrtc compliant sip server)

For the first scenario i imagine that it would be far better to run in-kernel mode because of performance.

For the second scenario i think userspace daemon should be fine ( i expect not much traffic maximum 50-100 calls).

However my question is what is the correct order of installing the deb packages.
Which packages do i really need.   

For running rtpengine in docker could i use Debian 10 OS and compile rtpengine and install just "ngcp-rtpengine-daemon_6.2.0.0+0~mr6.2.0.0_amd64.deb" ? (the in this case the host running docker can be any linux distribution?)

If i would like to run rtpengine in docker in kernel mode - is it possible or i need to use same linux distribution in host and docker container (because of the kernel match?)

Best regards,
Tom
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users