Hello Kamailio,
Is it possible to use RTPengine with a single UDP port for all calls instead of
a range of ports?
For example, when an invite is received or sent, the offered SDP for RTPengine
is to receive RTP packets on a single port that is the same for all other
calls, so that on
hi,
i have open around ~8000 rtp ports for around ~200calls (in peak)
with this statistic (current data, not from peak)
rtpengine_closed_sessions_total{reason="rejected"} 0
rtpengine_closed_sessions_total{reason="timeout"} 237405
rtpengine_closed_sessions_total{reason="silent_timeout"} 103
Hello all,
I'm currently doing some experiments with RTPENGINE and I need some help
configuring it.
First scenario i'm under NAT and Kamailio receives an INVITE with a private
address, rewrites (c) line on SDP with it's own IP address and relays the
message to the destination endpoint. After
Hi Team
I think, I might have found something that was overseen in the
rtpengine module.
A (ipv6) <=> rtpengine <=> B (ipv4)
Invite+SDP from B to A
It looks like this works as expected. A SDP c= line is created
containing an ipv6 address.
Invite, no SDP from A to B
Reply with SDP offer from B
Hi all
I wonder, if there is a documentation on what action is performed by
rtpengine_manage() on which kind reply.
Am I right, that rtpengine_manage(), on any 4XX reply causes a delete?
So if there is a re-invite (for example to switch to T.38) and the
other party replies with 488 which in
Hi All,
Hope you are all well?
I am hoping you can help with a bit of syntax I am struggling to get working in
the intended way. (We are using Kamailio 5.5.3 and using Kemi/python.)
The scenario is in AWS where we have separate Kamailio and RTPengine instances,
with a cluster of FreeSWITCH
I try to workout if - currently it would work, or - where and how to debug
more:
I face - 2 interfacec - public internet (so, TLS + sRTP) is desired
and private - old infrastructure - i mus only use plain RTP
172.23.9.70 - private ip - from this endpoint of kamailio and rtpengine should
Hi,
The destination address and port match with what is expected. I don't have
policy routing nor network namespaces. I do have containers, including for
Kamailio, but all are using host networking. I am also using gre tunnels
which might be causing the issue. I am still investigating that
On 13/12/2022 09.04, [EXT] Michel Pelletier wrote:
Hello,
Thank you for your reply. I checked the versions and they look good.
xt_RTPENGINE is 11.1.1.3 and the daemon is 11.1.1.3-1~bpo11+1.
Looking at /proc/rtpengine/0/list I see the packet and byte counters
incrementing normally with 0
Hello,
Thank you for your reply. I checked the versions and they look good.
xt_RTPENGINE is 11.1.1.3 and the daemon is 11.1.1.3-1~bpo11+1. Looking at
/proc/rtpengine/0/list I see the packet and byte counters incrementing
normally with 0 errors. In wireshark, capturing on any, I see the stream
On 12/12/2022 14.53, [EXT] Michel Pelletier wrote:
I am proxying all RTP through RTPEngine. Everything works fine until
about 5 seconds into the call, when rtpengine enters kernelization,
after which all RTP forwarding ceases. I've checked the required
iptables entries, and all looks good.
Hello,
I am proxying all RTP through RTPEngine. Everything works fine until about
5 seconds into the call, when rtpengine enters kernelization, after which
all RTP forwarding ceases. I've checked the required iptables entries, and
all looks good.
Here is a description of my environment:
# cat
Clear now, thanks!
Cheers,
Daniel
On 16.06.22 20:41, Victor Seva wrote:
> Hi,
>
> On 6/15/22 11:46, Daniel-Constantin Mierla wrote:
>> Hello,
>>
>> good news, indeed! Thanks to all involved!
>>
>> Not being very familiar with all Debian releasing policies, does that
>> mean the next Debian
Hi,
On 6/15/22 11:46, Daniel-Constantin Mierla wrote:
Hello,
good news, indeed! Thanks to all involved!
Not being very familiar with all Debian releasing policies, does that
mean the next Debian stable (v 12) will ship it? Or is it going to take
one more release cycle, to go from Debian
Hello,
good news, indeed! Thanks to all involved!
Not being very familiar with all Debian releasing policies, does that
mean the next Debian stable (v 12) will ship it? Or is it going to take
one more release cycle, to go from Debian Unstable to Testing, then to
future Stable (v 13)?
Cheers,
To: SR-Users
Subject: [SR-Users] RTPengine in Debian
HI all,
Just a quick heads up that RTPengine is now available in Debian sid/unstable
mainline repositories. Big thanks to our own Victor Seva and Guillem Jover for
making this possible.
Cheers
com/>
From: Youssef Boujraf
Sent: Wednesday, March 30, 2022 5:01 PM
To: Henning Westerholt
Cc: Kamailio (SER) - Users Mailing List
Subject: RE: [SR-Users] RTPENGINE : Kamailio - Get status if max sessions
reached
Dear,
Yes we did it but get for he same call 4x return value (2x true &
--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com<https://gilawa.com/>
From: sr-users On Behalf Of Youssef
Boujraf
Sent: Wednesday, March 30, 2022 2:48 PM
To: sr-users@lists.kamailio.org
Subject: Re: [SR-Users] RTPENGINE : Kamailio - Get status if max se
Hi Youssef,
a good starting point is to write your Kamailio version and the parts of
the kamailio.cfg that is interesting.
Kind regards
Karsten Horsmann
__
Kamailio - Users Mailing List - Non Commercial Discussions
*
se or distribution of this email.
Please consider the environment before printing this email.
From: sr-users on behalf of Richard Fuchs
Organisation: Sipwise GmbH
Reply to: "Kamailio (SER) - Users Mailing List"
Date: Friday, 4 March 2022 at 4:04 am
To: "sr-users@lists.kamail
g"
Subject: Re: [SR-Users] rtpengine - SRTP <> RTP missing a=crypto
On 03.03.22 14:47, Rhys Hanrahan wrote:
Yes, from what I’ve seen in the logs there are multiple branches happening. One
between Teams and Kamailio and one between Kamailio and Asterisk.
That's just one branch; the i
Are you sure that you have multiple branches?
You mentioned that you have kamailio in between asterisk and MS. In
this case, usually this is a simple call with one branch.
You have multiple branches if you fork the call (parallel forking:
sending to multiple destinations when the initial invite is
Users Mailing List"
Date: Friday, 4 March 2022 at 1:29 am
To: "Kamailio (SER) - Users Mailing List"
Subject: Re: [SR-Users] rtpengine - SRTP <> RTP missing a=crypto
Awesome, thank you for this. I did take a look at the rtpengine logs earlier
but they didn’t seem particul
.
Thanks,
Rhys.
From: sr-users on behalf of Richard Fuchs
Organisation: Sipwise GmbH
Reply to: "Kamailio (SER) - Users Mailing List"
Date: Friday, 4 March 2022 at 1:17 am
To: "sr-users@lists.kamailio.org"
Subject: Re: [SR-Users] rtpengine - SRTP <> RTP missing a=crypto
Hi Richard,
Yes, from what I’ve seen in the logs there are multiple branches happening. One
between Teams and Kamailio and one between Kamailio and Asterisk.
In terms of the rtpengine processing, I’ve tried lots of different variations,
but right now I’ve got:
* Rtpengine_manage() by
Date: Thursday, 3 March 2022 at 11:06 pm
To: "sr-users@lists.kamailio.org"
Subject: Re: [SR-Users] rtpengine - SRTP <> RTP missing a=crypto
On 03.03.22 12:07, Rhys Hanrahan wrote:
Any advice appreciated, as this is my first time dealing with SRTP (and
rtpengine). Feeling very stuck
you can check
https://github.com/sipwise/rtpengine/issues/1035
On Fri, Oct 29, 2021 at 11:42 AM ke...@alcall.net wrote:
> Hello @everyone
>
> Please can you explain me how this message is errors or not ?
>
> « Oct 29 08:34:44 ip76 rtpengine[649]: WARNING: [YGiXZ1MmIA port 30104]:
> [ice]
re.
Hope this helps.
Thank you,
Stefan
From: sr-users on behalf of ?M S?
Sent: Friday, October 29, 2021 1:28 PM
To: ke...@alcall.net; Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] RTPENGINE [ice] Priority collision between candidate
pairs
It's just a warning, you ca
Users Mailing List" Subject: [SR-Users] RTPENGINE [ice] Priority collision between candidate pairsHello @everyonePlease can you explain me how this message is errors or not ?« Oct 29 08:34:44 ip76 rtpengine[649]: WARNING: [YGiXZ1MmIA port 30104]: [ice] Priority collision between candi
Hello @everyone
Please can you explain me how this message is errors or not ?
« Oct 29 08:34:44 ip76 rtpengine[649]: WARNING: [YGiXZ1MmIA port 30104]: [ice]
Priority collision between candidate pairs 9oZd7sWNVguf6cgl:e4b19f6635447b850 »
thank
rtpengine module README tells this about module dependencies:
3.1. Kamailio Modules
The following modules must be loaded before this module:
tm module - (optional) if you want to have rtpengine_manage() fully
functional
Looks like this is not correct. If Kamailio connects to
On 30/09/2021 13.34, [ EXT ] Alex Balashov wrote:
On Sep 30, 2021, at 1:32 PM, Richard Fuchs wrote:
On 30/09/2021 13.17, [ EXT ] Alex Balashov wrote:
I’m not sure how the mapping works internally. But whatever the operation is,
is that value stored somewhere or possible to store somewhere so
On 30/09/2021 13.17, [ EXT ] Alex Balashov wrote:
I’m not sure how the mapping works internally. But whatever the operation is,
is that value stored somewhere or possible to store somewhere so as to persist
across restarts in a turn-key way?
AFAICR the node is selected based on a
Yeah, but what happens if I handle an offer/answer with an overridden set ID —
let’s say that ID value comes from a database query or API or whatever at
initial INVITE processing — and then I restart Kamailio, and then a reinvite
occurs.
If I don’t know which set was used, the offer/answer
> On Sep 30, 2021, at 1:32 PM, Richard Fuchs wrote:
>
> On 30/09/2021 13.17, [ EXT ] Alex Balashov wrote:
>> I’m not sure how the mapping works internally. But whatever the operation
>> is, is that value stored somewhere or possible to store somewhere so as to
>> persist across restarts in a
I’m not sure how the mapping works internally. But whatever the operation is,
is that value stored somewhere or possible to store somewhere so as to persist
across restarts in a turn-key way?
> On Sep 30, 2021, at 12:44 PM, Daniel-Constantin Mierla
> wrote:
>
> Hello,
>
> wasn't it hashing
Hello,
wasn't it hashing them to get the hash id, and that was used for
selection of the rtpengine instance?
Cheers,
Daniel
On 30.09.21 17:49, Alex Balashov wrote:
> Hi,
>
> Sorry if I missed any developments on this, but:
>
> Kamailio does keep a runtime association of Call-ID+Ftag =>
Hi,
Sorry if I missed any developments on this, but:
Kamailio does keep a runtime association of Call-ID+Ftag => RTPEngine instance,
which is significant if an RTPEngine set with multiple members is used, or if a
non-default set is used for a given call.
When Kamailio is restarted, this
That’s what I’m wondering, even if kam-rtpengine is async, that’s won’t
solve the latency problem, it will only hide it. But if that’s what he
wants, go right ahead :)
On Thu, 12 Aug 2021 at 09:48, Yuriy Gorlichenko wrote:
> RTPengine since 9.0 provided HTTP transport for control protocol
RTPengine since 9.0 provided HTTP transport for control protocol messages.
you can use http_async_client as the easiest way to achieve async
communication between Kamailio and RTPengine.
But this doesn't resolve the latency problem. This will only unblock
workers to be able to handle other
Hello,
I may be grossly misunderstanding you, but how would doing async polling
with RTPEngine that solve a latency problem? I’m not trying to shoot down
the idea/question/request, just wondering.
David
On Thu, 12 Aug 2021 at 09:06, Mitesh Thakkar
wrote:
> Hi,
>
> Couple of week before I have
Hi,
Couple of week before I have posted feature request -
https://github.com/kamailio/kamailio/issues/2807
As suggested, I am trying to figure out how I can achieve it with async or
sworker modules. Can someone help me to understand how to use those modules
to achieve async connectivity?
Greetings.
I'm trying to set up annoncement playback for both parts of the call. I
have to play the file after the connection is established. Stop_media (all)
must be executed before playing
It turns out the construction:
block_media ("all");
play_media ("all file = / etc / kamailio / sounds
Hi,
so I understand it like: "it is already possible with kamailio" :-) !
But of course, support directly in rtpengine module would be also nice
to have.
Cheers,
Daniel
On 04.03.21 16:59, Arsen Semenov wrote:
> Hi,
>
> Also interested in this question.
> As I know it's not implemented in the
Hi,
Also interested in this question.
As I know it's not implemented in the Kamailio module yet.
As for now I used kemi lua to talk to rtpengine NG over websocket
protocol.
On Thu, Mar 4, 2021 at 8:28 PM Alex Balashov
wrote:
> Hi,
>
> Recent versions of RTPEngine (9.x+) implemented support for
Hi,
Recent versions of RTPEngine (9.x+) implemented support for speaking the
"NG" wire protocol over TCP, via the `--listen-tcp-ng` option.
Does the Kamailio `rtpengine` module support this, and/or are there any
plans to? We've run into a few scenarios where very large responses from
Hmm...interesting.
Is there logging which states the fallback is issued? If so, can someone
share?
Thanks.
On Mon, Sep 14, 2020 at 1:28 PM Richard Fuchs wrote:
> On 14/09/2020 13.14, Andrew Chen wrote:
> > Btw Richard Fuchs, to follow up on your comment, we have a load
> > generator running
Sergey Safarov,
Thanks for the response but we're not a CentOS house. Just Ubuntu.18.04.
One other question. Is Daniel's suggestion the only way to get around
kernel forwarding with our current setup? Will there be support for it in
the future without disabling module signature check?
On
Btw Richard Fuchs, to follow up on your comment, we have a load
generator running sipp which is non-SRTP traffic.
As for the fallback, how does that work exactly? We tried the following
today and it seems to have helped:
- Removed "--table" startup param in systems file
- Uncommented
On 14/09/2020 13.14, Andrew Chen wrote:
Btw Richard Fuchs, to follow up on your comment, we have a load
generator running sipp which is non-SRTP traffic.
As for the fallback, how does that work exactly? We tried the
following today and it seems to have helped:
- Removed "--table" startup
I have testes build on 5.7 kernel on CentOS 8 (custom rpm package)
You will find commit here
https://github.com/sipwise/rtpengine/issues/975
Sergey
On Fri, Sep 11, 2020 at 10:53 PM Daniel-Constantin Mierla
wrote:
> Related to tainted kernel, I faced the same issue when I deployed
> rtpengine
Thanks Daniel. Let me look at that option.
On Fri, Sep 11, 2020 at 3:52 PM Daniel-Constantin Mierla
wrote:
> Related to tainted kernel, I faced the same issue when I deployed
> rtpengine on a Suse Enterprise many months ago, so I do not really remember
> the exact steps, but there is a way to
Sorry let me clarify this line here:
"...at the time, I was running an older version 8.0.x so I recompiled all
the ngcp packages under this kernel and completed the installation without
issues.."
8.0.x is the older ngcp version. I recompiled version 9.0.1.0 under that
new kernel version
Thanks Alex.
So it turns out my rtpengine stopped working after our latest kernel
upgrade to:
Linux sjomainrtpe30 5.3.0-1035-aws #37-Ubuntu SMP Sun Sep 6 01:17:09 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
at the time, I was running an older version 8.0.x so I recompiled all the
ngcp packages
Hey guys,
Is this the right place to ask about rtpengine (ngcp) related issues with
kernel packet forwarding?
Thanks.
--
Andy Chen
Sr. Telephony Lead Engineer
achen@ fuze.com
--
*Confidentiality Notice: The information contained in this e-mail and any
attachments may be confidential. If you
Related to tainted kernel, I faced the same issue when I deployed
rtpengine on a Suse Enterprise many months ago, so I do not really
remember the exact steps, but there is a way to disable the check of
signed kernel modules (iirc, these are only the ones coming from the
kernel source tree, so if
On 11/09/2020 15.29, Andrew Chen wrote:
Thanks Alex.
So it turns out my rtpengine stopped working after our latest kernel
upgrade to:
Linux sjomainrtpe30 5.3.0-1035-aws #37-Ubuntu SMP Sun Sep 6 01:17:09
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
at the time, I was running an older version
There is an RTPEngine mailing list, I believe, but RTPEngine questions
are often posed here given its close association with Kamailio. What's
going on?
On 9/11/20 2:57 PM, Andrew Chen wrote:
Hey guys,
Is this the right place to ask about rtpengine (ngcp) related issues
with kernel packet
Hello,
Yeah that’s what I’m thinking.
This is on AWS where i added a secondary IP to the instance, wanting to
segregate the “public” and “private”
But under the hood they’re both private IPs able to reach the private
network, and that’s where my problem comes, because the OS simply selects
the
Check your output to the command "ip route show table local".
For a connected network, the kernel will select the source IP based on
these rules. From memory I think, it is possible to change the "src"
parameter to use a different IP, so you can play with that.
Anyway, as a general rule, I don't
you can also look
https://www.usenix.org/system/files/login/articles/login_summer16_10_anderson.pdf
On Sun, Jul 5, 2020 at 8:02 AM Sergey Safarov wrote:
> Required configure police based routing
>
> https://www.drdobbs.com/policy-routing-in-linux/199100936
>
>
>
Required configure police based routing
https://www.drdobbs.com/policy-routing-in-linux/199100936
I know this is more of a networking routing question, just trying to see if
you can find a better solution than re-architecturing the network. Although
maybe that’s the best approach, since this is a pretty new setup. Maybe
it’s better to do it now and not using work-arounds?
On Sun, 5 Jul 2020
Hello guys,
I have rtpengine running on a box with ips like this:
external: 172.10.0.10 (advertise 10.10.10.1)
internal: 172.10.0.11
Both Ips are on the same network.
When i do rtpengine_manage i set "direction=external direction=internal",
and the SDP offer is correct.
The problem I'm having
Interesting. Thanks for the tidbit. I will play around with
msg_apply_changes and find the right place for it.
On Fri, Jun 26, 2020 at 9:01 AM Richard Fuchs wrote:
> Rtpengine takes and replaces the entire SDP body, so if there's another
> module also manipulating the SDP, one module won't
Thanks Richard.
I do have the nathelper module running but not rtpproxy. How does
nathelper cause this issue?
On Fri, Jun 26, 2020 at 8:27 AM Richard Fuchs wrote:
> Looks like you're using both rtpengine and some other SDP-modifying module
> together, such as nathelper or rtpproxy, without
Rtpengine takes and replaces the entire SDP body, so if there's another
module also manipulating the SDP, one module won't see the changes made
by the other one unless you call msg_apply_changes in between, leaving
you with bits of string in the wrong places.
Cheers
On 26/06/2020 08.50,
Looks like you're using both rtpengine and some other SDP-modifying
module together, such as nathelper or rtpproxy, without calling
msg_apply_changes() in between.
Cheers
On 25/06/2020 16.46, Andrew Chen wrote:
Hi forum,
I'm starting my rtpengine project and I'm facing a strange problem
Hi forum,
I'm starting my rtpengine project and I'm facing a strange problem with
rtpengine. I am seeing this in the SDP part of the INVITE:
a=rtcp:52021
a=rtcp-mux
2001:470:7:3A7:0:0:0:2
a=direction:active
a=oldmediaip:54.153.25.234
As you can see there is a random insert of the local
--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com<https://gilawa.com/>
From: sr-users On Behalf Of Gaurav Bmotra
Sent: Tuesday, June 2, 2020 8:13 AM
To: Kamailio (SER) - Users Mailing List ; Kamailio
(SER) - Users Mailing List
Subject: [SR
hi
i m using kamailio 5.3 ans install rtpengine on different server
kindly help me what will be the configuration in case of kamailio
and rtpengine
thank you
--
*Regards:*
Gaurav Kumar
___
Kamailio (SER) - Users Mailing List
I found this from 2015...
https://github.com/kamailio/kamailio/pull/390
If it's still holding true, looks like it's rehashed?
--fred
On Mon, 2020-05-25 at 18:02 -0400, Alex Balashov wrote:
> Hi,
>
> When using a single RTPEngine, or a single RTPEngine per set, it is
> possible to make
Hi,
When using a single RTPEngine, or a single RTPEngine per set, it is
possible to make stateless RTPEngine calls from Kamailio, since
everything is keyed by Call-ID + tag.
In other words, one can set up a call, answer it, restart Kamailio, and
still send a 'delete' to RTPEngine
Hi,
setid was type, it is 1 and 2. I have just used made-up addresses.
DEBUG shows even strage output
DEBUG: rtpengine [rtpengine.c:3071]: select_rtpp_node_old(): rtpengine hash
table lookup failed to find node for calllen=20 callid=f27oej9e3k0o3vhidpoc
viabranch=
DEBUG: rtpengine
Sorry not properly read in the beginning, i thought both answer and offer
sent to the same server that triggered the same bug i encountered but they
were not.
Not sure weird it is? The answer suppose go to the same rtpengine server as
the offer. Try increasing kamailio's debug level and tweak with
So upgrade to version 8.2.1.2 did not helped. Issue is probably in kamailio
module itself, because all requests and responses are correct.
> On 6 Mar 2020, at 09:52, Michal Popovic wrote:
>
> Hi,
>
> will try on newest version and be back with result.
>
> Thanks
>
>> On 6 Mar 2020, at
Hi,
will try on newest version and be back with result.
Thanks
> On 6 Mar 2020, at 09:47, Lợi Đặng wrote:
>
> Hi, what's your sipwise rtpengine version? I once encountered similar issue
> when the call >60s not yet answered, not sure if the same bug, you may want
> to upgrade your
Hi, what's your sipwise rtpengine version? I once encountered similar issue
when the call >60s not yet answered, not sure if the same bug, you may want
to upgrade your rtpengine.
https://github.com/sipwise/rtpengine/blob/b507e245b2356f8b965a2671ab5f19a4cac837b0/debian/changelog
* [a6d9c78]
Hi,
we are facing the issue with automated failover in same SIP dialog in rtpengine
module. This issue occurs after we upgraded version 4.4.7 to 5.3.2 and only for
rtpengines that are in another datacenter with latency higher than about 100ms.
configuration
modparam("rtpengine",
Thanks for the info Yuri!
I tried several scenarios but without success. My sip proxy has ipv4
and ipv6 address. The other nodes use ipv4. When there is a request
for a ipv6 UAC/customer comming to the proxy the rtpengine/sipwise is
rewriting the sdp with the correct ipv6 address of the proxy. So
Look here
https://www.kamailio.org/docs/modules/5.3.x/modules/rtpengine.html#rtpengine.p.write_sdp_pv
Then you will be able to get it with string operations.
On Thu, 23 Jan 2020, 14:25 Pafel, wrote:
> My bad, I am using rtpengine module but not rtpproxy.
>
> Regards,
> Pavel
>
> На ср,
My bad, I am using rtpengine module but not rtpproxy.
Regards,
Pavel
На ср, 22.01.2020 г. в 18:41 Pafel написа:
> Hello,
> I am using kamailio 5.3, rtproxy module and sipwise rtpengine. Is there
> any way I can get the rewritten / relay address and port by the
> rtpproxy/rtpengine. In avp or
Hello,
I am using kamailio 5.3, rtproxy module and sipwise rtpengine. Is there any
way I can get the rewritten / relay address and port by the
rtpproxy/rtpengine. In avp or some other variable?
Regards,
Pavel Siderov
___
Kamailio (SER) - Users Mailing
rwise will error
>>>>> echo 'del 0' > /proc/rtpengine/control
>>>>>
>>>>>
>>>>> this part seems to be very relevant indeed!
>>>>>
>>>>> Op ma 6 jan. 2020 om 17:41 schreef Nicolas Breuer <
>>>>> nicol
control
>>>>>
>>>>>
>>>>> this part seems to be very relevant indeed!
>>>>>
>>>>> Op ma 6 jan. 2020 om 17:41 schreef Nicolas Breuer <
>>>>> nicolas.bre...@belcenter.biz>:
>>>>>
>
will error
>>>> echo 'del 0' > /proc/rtpengine/control
>>>>
>>>>
>>>> this part seems to be very relevant indeed!
>>>>
>>>> Op ma 6 jan. 2020 om 17:41 schreef Nicolas Breuer <
>>>> nicolas.bre...@belcenter.biz>:
>>>>
>>
,
>>>>
>>>>
>>>>
>>>> Check cat /proc/rtpengine/0/list
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *De :* sr-users *De la part de*
>>>> davy van de moere
>>
schreef Nicolas Breuer <
>> nicolas.bre...@belcenter.biz>:
>>
>>> Hey Davy,
>>>
>>>
>>>
>>> Check cat /proc/rtpengine/0/list
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *De :* sr-users *De la part de*
6 janvier 2020 14:47
> *À :* Henning Westerholt
> *Cc :* Kamailio (SER) - Users Mailing List
> *Objet :* Re: [SR-Users] RTPEngine performance - How far are you pushing
> your systems
>
>
>
> Ok, I'll get my SIPP warmed up then ... ;) thx for the feedback!
>
>
>
>
users *On Behalf Of *davy
> van de moere
> *Sent:* Monday, January 6, 2020 12:52 PM
> *To:* Kamailio (SER) - Users Mailing List
> *Subject:* [SR-Users] RTPEngine performance - How far are you pushing
> your systems
>
>
>
> Dear all,
>
>
>
> Not a direct question
services – https://gilawa.com<https://gilawa.com/>
From: sr-users On Behalf Of davy van de
moere
Sent: Monday, January 6, 2020 12:52 PM
To: Kamailio (SER) - Users Mailing List
Subject: [SR-Users] RTPEngine performance - How far are you pushing your systems
Dear all,
Not a direct question on ka
Dear all,
Not a direct question on kamailio, but on rtpengine, so feel free to ignore
:)
I have a farm of rtpengine servers , supporting our set of kamailio's.
On recent decent hardware (hp dl360 gen9/10 servers), I typically push my
systems upto 2500 channels per machine. Then I tend to see
Subject: Re: [SR-Users] RTPengine with rejected RE-INVITE when port is changing
On 05.12.19 11:33, Daniel Tryba wrote:
> On Thu, Dec 05, 2019 at 09:37:51AM +, Laurent Schweizer wrote:
>> Hello,
>>
>> I already see old post about this :
>> https://opensips.org/pipermail
On 05.12.19 11:33, Daniel Tryba wrote:
> On Thu, Dec 05, 2019 at 09:37:51AM +, Laurent Schweizer wrote:
>> Hello,
>>
>> I already see old post about this :
>> https://opensips.org/pipermail/users/2014-November/030451.html
>>
>> but I???m interested to know if now they is a solution
>>
>>
On Thu, Dec 05, 2019 at 09:37:51AM +, Laurent Schweizer wrote:
> Hello,
>
> I already see old post about this :
> https://opensips.org/pipermail/users/2014-November/030451.html
>
> but I???m interested to know if now they is a solution
>
> so the issue is a RE-INVITE rejected (415
Hello,
I already see old post about this :
https://opensips.org/pipermail/users/2014-November/030451.html
but I’m interested to know if now they is a solution
so the issue is a RE-INVITE rejected (415 Unsupported Media or 488 ) and the
RTP port is changing.
Is that case the old RTP relay
Hi,
Kamailio's rtpengine module has an internal hash table with call-id as a
key and when you call rtpengine_manage()/_offer()/_answer()/_delete()
kamailio finds corresponding rtpengine instance to send command to. So
it's inside rtpengine module and not in tm or dialog and thus unlikely
to
Ok. There are a possibility to get instance was chosen by rtpengine_offer via
rtp_inst_pvar.
But is there way to force answer/delete to this instance or need to get some
uri_to_setid function?
Regards, Igor
On May 31, 2019, 17:04 +0300, Alex Balashov , wrote:
> You can’t be sure, if the
Thanks, that's one of ideas where to store info.
Regards, Igor
On May 31, 2019, 17:04 +0300, Alex Balashov , wrote:
> You can’t be sure, if the command is issued from a different Kamailio
> instance. I’d suggest sticking the RTPEngine set ID into an RR parameter,
> simply because it’s both
You can’t be sure, if the command is issued from a different Kamailio instance.
I’d suggest sticking the RTPEngine set ID into an RR parameter, simply because
it’s both stateless and dialog-persistent.
—
Sent from mobile, with due apologies for brevity and errors.
> On May 31, 2019, at 10:01
1 - 100 of 263 matches
Mail list logo
