4 Feb
2015
4 Feb
'15
3:42 p.m.
Hi,
I have latest stable release of RTPEngine deployed in a virtual machine
(KVM) along with Kamailio v4.2. All is working fine except i see this
message in RTPEngine logs,
--
rtpengine[16455]: [82qrjq0hdtt45afbqo98 port 40960] Kernelizing media
stream
rtpengine[16455]: [82qrjq0hdtt45afbqo98 port 40960] No support for kernel
packet forwarding available
--
using lsmod command i see that module xt_RTPENGINE is load.
--
Module Size Used by
iptable_mangle 12488 0
xt_RTPENGINE 22068 3
iptable_nat 12800 0
nf_nat 17924 1 iptable_nat
...
--
Also the iptables rule for RTPEngine exists, i.e.
--
Chain INPUT (policy ACCEPT 224K packets, 37M bytes)
pkts bytes target prot opt in out source
destination
224K 37M rtpengine all -- any any anywhere
anywhere
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
Chain OUTPUT (policy ACCEPT 224K packets, 37M bytes)
pkts bytes target prot opt in out source
destination
Chain rtpengine (1 references)
pkts bytes target prot opt in out source
destination
2022 414K RTPENGINE udp -- any any anywhere
anywhere RTPENGINE id:0
--
Yet still RTPEngine is not able to kernelize the RTP stream and does
user-space packet forwarding? Can you guys suggest what could be wrong here?
Thank you.
4 Feb
4 Feb
3:59 p.m.
New subject: RTPEngine - No support for kernel packet forwarding available
On 02/04/15 15:42, Muhammad Shahzad wrote:
Hi,
I have latest stable release of RTPEngine deployed in a virtual machine
(KVM) along with Kamailio v4.2. All is working fine except i see this
message in RTPEngine logs,
--
rtpengine[16455]: [82qrjq0hdtt45afbqo98 port 40960] Kernelizing media
stream
rtpengine[16455]: [82qrjq0hdtt45afbqo98 port 40960] No support for
kernel packet forwarding available
--
This message pops up if there's an unsupported combination of crypto
suites or transport protocols being used. I'm not aware of any such
combination in the current code base. Can you provide more details about
what kind of calls you're handling there?
cheers
4:17 p.m.
For the moment the message appears when a webrtc caller (using chrome
v40.0.2214.94 64-bit) dials voicemail service which is running on a legacy
sip server. The RTPEngine converts media from SAVPF to AVP for this audio
only call.
There may be other scenarios, since this is not the first time i see this
message. I will update here when i encounter those scenarios again.
Thank you.
On Wed, Feb 4, 2015 at 9:59 PM, Richard Fuchs <rfuchs(a)sipwise.com> wrote:
On 02/04/15 15:42, Muhammad Shahzad wrote:
Hi,
I have latest stable release of RTPEngine deployed in a virtual machine
(KVM) along with Kamailio v4.2. All is working fine except i see this
message in RTPEngine logs,
--
rtpengine[16455]: [82qrjq0hdtt45afbqo98 port 40960] Kernelizing media
stream
rtpengine[16455]: [82qrjq0hdtt45afbqo98 port 40960] No support for
kernel packet forwarding available
--
This message pops up if there's an unsupported combination of crypto
suites or transport protocols being used. I'm not aware of any such
combination in the current code base. Can you provide more details about
what kind of calls you're handling there?
cheers
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
4:22 p.m.
ah ok, looking closely at RTPEngine logs, i also see this message,
--
rtpengine[16455]: [j4ujoo87lsnjvapf4cmd port 41035] SRTCP output wanted,
but no crypto suite was negotiated
--
So you are right about crypto mismatch, however it is strange why SRTCP was
not negotiated with chrome ...
Thank you.
On Wed, Feb 4, 2015 at 10:17 PM, Muhammad Shahzad <shaheryarkh(a)gmail.com>
wrote:
For the moment the message appears when a webrtc
caller (using chrome
v40.0.2214.94 64-bit) dials voicemail service which is running on a
legacy sip server. The RTPEngine converts media from SAVPF to AVP for this
audio only call.
There may be other scenarios, since this is not the first time i see this
message. I will update here when i encounter those scenarios again.
Thank you.
On Wed, Feb 4, 2015 at 9:59 PM, Richard Fuchs <rfuchs(a)sipwise.com> wrote:
On 02/04/15 15:42, Muhammad Shahzad wrote:
Hi,
I have latest stable release of RTPEngine deployed in a virtual machine
(KVM) along with Kamailio v4.2. All is working fine except i see this
message in RTPEngine logs,
--
rtpengine[16455]: [82qrjq0hdtt45afbqo98 port 40960] Kernelizing media
stream
rtpengine[16455]: [82qrjq0hdtt45afbqo98 port 40960] No support for
kernel packet forwarding available
--
This message pops up if there's an unsupported combination of crypto
suites or transport protocols being used. I'm not aware of any such
combination in the current code base. Can you provide more details about
what kind of calls you're handling there?
cheers
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
7:16 p.m.
New subject: RTPEngine - No support for kernel packet forwarding available
Muhammad Shahzad writes:
I have latest stable release of RTPEngine deployed in
a virtual machine
(KVM) along with Kamailio v4.2. All is working fine except i see this
message in RTPEngine logs,
Please do not post the same question to two lists.
-- Juha
5 Feb
5 Feb
2:27 a.m.
I post it on both since i was a bit confused about which list is
appropriate for this question.
Anyways, i will toss a coin next time. ;-)
Thank you.
On Thu, Feb 5, 2015 at 1:16 AM, Juha Heinanen <jh(a)tutpro.com> wrote:
Muhammad Shahzad writes:
I have latest stable release of RTPEngine
deployed in a virtual machine
(KVM) along with Kamailio v4.2. All is working fine except i see this
message in RTPEngine logs,
Please do not post the same question to two lists.
-- Juha
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
3420
days inactive
3421
days old
5 comments
3 participants
participants (3)
-
Juha Heinanen -
Muhammad Shahzad -
Richard Fuchs