Re: [SR-Users] RTPEngine Transcoding
Hello! Good news! Please clarify how recording (pcap and proc) will work in case of transcoding if there is an influence on each other. On 14 February 2018 at 00:19, Alex Balashov wrote: > The attributes passed to rtpengine from the offer/answer/manage/query > functions are not all documented in the Kamailio RTPengine module docs, but > all values are accepted. > > -- Alex > > -- > Sent via mobile, please forgive typos and brevity. > > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- BR Denys Pozniak ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] Dimensioning ds_hash_size value for dispatcher module
Hi, In the documentation of the dispatcher module it is said that in order to use the algorithm 10 (load balancing) the parameter ds_hash_size must be set, in the definition it is said that the value is in powers of 2, that is to say if it is set to 8, this is equal to 2 ^ 8 = 256 slots, but still I do not understand how to dimension this value for my needs. I do not know whether to put 8, 4, 9, etc. Saludos, ALVARO ARAOS MÉNDEZ Director de Tecnología en FONOIP +56 2 2947 9000 alv...@fonoip.com | www.fonoip.com [1] Moisés Chacón 46, El Monte, RM Links: -- [1] http://www.fonoip.com ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] RTPEngine QoS statistics and leg labelling
On 2018-02-14 02:44 AM, Alex Balashov wrote: Okay, so after having a spelunk through the source code, I have the impression that this MOS / quality analysis functionality is limited solely to feedback off RTCP supports. I was under the impression from the documentation that RTPEngine does some stream analysis of its own, although in fairness, the documentation does not explicitly make this claim or the contrary one way or another. :-) It does gather some stats about the media streams on its own (even more so with the extended transcoding capabilities now), but at least one component of the MOS calculation (latency) depends on RTCP being provided by the RTP clients, so without that, no MOS score can be produced. Cheers ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] RTPEngine Transcoding
On 2018-02-14 05:40 AM, Denys Pozniak wrote: Hello! Good news! Please clarify how recording (pcap and proc) will work in case of transcoding if there is an influence on each other. They're completely independent of each other. The source data for recording are the packets as they're received (before transcoding). Cheers ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] RTPEngine Transcoding
So if we have 2 legs: opus (webrtc side) and pcm (sip side), pcap file will have also 2 incoming RTP streams: opus and pcm, correct? On 14 February 2018 at 14:19, Richard Fuchs wrote: > On 2018-02-14 05:40 AM, Denys Pozniak wrote: > >> Hello! Good news! >> Please clarify how recording (pcap and proc) will work in case of >> transcoding if there is an influence on each other. >> > > They're completely independent of each other. The source data for > recording are the packets as they're received (before transcoding). > > Cheers > > > ___ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- BR Denys Pozniak ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] RTPEngine Transcoding
On 2018-02-14 08:55 AM, Denys Pozniak wrote: So if we have 2 legs: opus (webrtc side) and pcm (sip side), pcap file will have also 2 incoming RTP streams: opus and pcm, correct? Yes, correct ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] ways to track all messages of a dialog
Thank you , but what I need is to be used inside the script, aside from logging
the processing of the messages for those call I also need to apply certain
logic in the kamailio script file, that is why I need something that can be
used from there. Sipcapture or sngrep are outside the scope of what I need.
Can somebody confirm whether the flags are suitable for this case ?
-Original Message-
From: Fabian Borot
Sent: Tuesday, February 13, 2018 5:06 PM
To: 'sr-users@lists.kamailio.org'
Subject: ways to track all messages of a dialog
I need to track all messages (SIP Requests, SIP Responses) for some SIP
dialogs. Let's say I need to log something specific on each state for calls
initiated from a certain IP (initial request, temporary replies, rejection with
a negative response, call was accepted with 200, termination with BYE,
termination with CANCEL etc. ).
I am thinking on using flags but I am not sure after reading the tutorial on
flags
(http://www.kamailio.org/dokuwiki/doku.php/tutorials:openser-flag-operations)
if that is going to work properly. The doc says: "They provide a very easy and
fast way of keeping states during processing a request or during a
transaction". I am afraid that the ACK if the call is accepted and the BYE
won't be tracked properly because they are not part of the initial transaction.
Also the doc does not mention if the flag is preserved among branches spawned
during the processing of the call.
The idea is for example:
request_route {
if (is_method("INVITE")){
if ($si == "192.168.168.100"){ #condition that would
set the flag, INVITE came from "my_IP"
#flag/mark dialog
setflag(1);
#log call from "my_IP" was received
}
route("INCOMING);
}
If(loose_route() ){
if (is_method("ACK")){
if(isflagset(1)){
#log ACK related to "my_IP" was received
}
}
if (is_method("CANCEL")){
if(isflagset(1)){
#log CANCEL related to "my_IP" was received
}
}
if (is_method("BYE")){
if(isflagset(1)){
#log BYE related to "my_IP" was received
}
}
}
}
Then :
route["INCOMING"] {
# do some processing
# do some processing
t_onreply("INCOMING");
t_on_failure("INCOMING");
t_relay();
}
onreply_route[INCOMING] {
#do some processing
if(isflagset(1)){
#log a reply related to "my_IP" was received
}
}
failure_route[INCOMING] {
#do some processing
if(isflagset(1)){
#log a negative reply related to "my_IP" was received
}
}
Will the flags work on this case ?
My 2nd approach is to use a htable and use the call_id for my calls as the key.
The on each route section (reply, failure_reply, ACK processing etc.) find the
$ci on the htable and if it is there do the appropriate action. But I need to
delete the key:value once the call ends or leave it autoexpire with a expire
value bigger than the max_call_duration_time that we have in our system.
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Raspberry Pi deb packages -> built
> > Just for fun, I'm planning to do some CPS stats tomorrow (if I got the > time) > > Ok, I'm posting back some stats I've found upon basic SIPp testing for Kamailio running on rpi 3. All the PI specs, Kamailio basic configs and SIPp xml scenarios I used can be found at [1]. All the tests were done in a LAN, using PI's ethernet interface, running kamailio 5.1.1. All the tests ran for 60 seconds, a couple of times. 1. REGISTER/200, __with db_text__: - at 900 cps test did finish: all UAC registered; pi htop threads were ~15-20% - at 950 cps test did NOT finish: got "Overload warning" on my UAC/UAS SIPp testing machine :( 2. INVITE/180/200/PAUSE(3sec)/BYE/200, __with no media__: - at 370 cps test did finish: all UAC->UAS calls completed; ~150 "180 Trying" Unexpected-Msg on UAC side; pi htop threads were ~50% - at 380 cps test did NOT finish: few(~5) UAC->UAS calls not completed; pi htop threads were ~50% The results are really impressive !!! (even if the used testing configs were really basic ones). Moreover, I think that I've reached the limit of my current SIPp testing machine, but not of PI's... [1] https://github.com/smititelu/rpi ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] KEMI
Hi, Where would one get the files which are imported when creating a Kamailio file using python? import Router.Logger as Logger import KSR as KSR Would be awesome if we could reference these and get code completion when using for instance Visual Studio code. So, basically, I'm looking for the KSR.py and Router.py files, but I cannot find them. Regards, Grant -Original Message- From: sr-users [mailto:sr-users-boun...@lists.kamailio.org] On Behalf Of Daniel-Constantin Mierla Sent: woensdag 7 februari 2018 16:02 To: Aleksandar Sosic Cc: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] KEMI I am more into Lua when it comes on doing something the native kamailio.cfg cannot do, that's because Lua has a decent range of extensions (external Lua libraries). JavaScript was added for those that do not need a lot of external extensions, but want to have script reload. Same for Squirrel, but that language is not so popular as JavaScript, however, there could be people liking it, being very minimal, thus expecting to need very low resources. Anyhow, once implemented, a kemi interpreter module should not need much maintenance. New kemi functions will be exported directly from the other modules. Cheers, Daniel On 07.02.18 14:12, Aleksandar Sosic wrote: > Thanks Dan for the extensive answer! > > My last question then is what kemi language do you use personally? :D > > Kind regards, > -- > Aleksandar Sosic > mail: alex.so...@timenet.it > skype: alex.sosic > cell: +385 91 2505 146 > > > On Tue, Feb 6, 2018 at 8:44 PM, Daniel-Constantin Mierla > wrote: >> The C code is the same for 99% of the KSR functions available either >> in python or javascript (or the other kemi languages). Only KSR.pv >> and KSR.x functions are implemented in the app_python or app_jsdt modules. >> So if such a KSR function is broken, it is the same everywhere >> >> Probably KSR.pv can be moved in a common place, but KSR.x are >> specific extensions for each interpreter, so it will stay in app_*. >> >> Then of course, it is a matter of the script interpreter, python vs >> js ducktape, which are external project, we just bind to them. Also, >> it is about the maintenance of app_python and app_jsdt. I am not the >> developer of app_python and I cannot assert its state, I just added >> the kemi enhancement. app_jsdt was developed by me, but I haven't >> used it extensively so far. >> >> Probably you can do some basic configs and test yourself and see what >> fits your needs better, you can start from the examples at: >> >> - >> https://github.com/kamailio/kamailio/tree/master/misc/examples/kemi >> >> In long term, you have to look at the extensions you may need, what >> python offers vs ducktape js interpreter in terms of their own >> extensions and libraries. >> >> Cheers, >> Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com ___ 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
Re: [SR-Users] RTPEngine QoS statistics and leg labelling
Hi Richard, On Wed, Feb 14, 2018 at 08:18:11AM -0500, Richard Fuchs wrote: > On 2018-02-14 02:44 AM, Alex Balashov wrote: > > Okay, so after having a spelunk through the source code, I have the > > impression that this MOS / quality analysis functionality is limited > > solely to feedback off RTCP supports. > > > > I was under the impression from the documentation that RTPEngine does > > some stream analysis of its own, although in fairness, the documentation > > does not explicitly make this claim or the contrary one way or another. > > :-) > > It does gather some stats about the media streams on its own (even more so > with the extended transcoding capabilities now), but at least one component > of the MOS calculation (latency) depends on RTCP being provided by the RTP > clients, so without that, no MOS score can be produced. Which statistics can RTPEngine compute over the stream on its own? Since I saw no metrics whatsoever for the B leg, I assumed none. I was running mr5.5.3 however. Does this differ in 6+? Also — I'm sure the question has been asked before — can RTPEngine send its own RTCP sender/receiver reports? My testing setup was: Phone --> Kamailio+RTPEngine --> Kamailio+RTPEngine --> Carrier (where tinkering(ITSP was happening) Is there a way to turn on backward RTCP feedback from #3 back to #2? -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] RTPEngine QoS statistics and leg labelling
On 2018-02-14 12:21 PM, Alex Balashov wrote: Hi Richard, On Wed, Feb 14, 2018 at 08:18:11AM -0500, Richard Fuchs wrote: On 2018-02-14 02:44 AM, Alex Balashov wrote: Okay, so after having a spelunk through the source code, I have the impression that this MOS / quality analysis functionality is limited solely to feedback off RTCP supports. I was under the impression from the documentation that RTPEngine does some stream analysis of its own, although in fairness, the documentation does not explicitly make this claim or the contrary one way or another. :-) It does gather some stats about the media streams on its own (even more so with the extended transcoding capabilities now), but at least one component of the MOS calculation (latency) depends on RTCP being provided by the RTP clients, so without that, no MOS score can be produced. Which statistics can RTPEngine compute over the stream on its own? Since I saw no metrics whatsoever for the B leg, I assumed none. I was running mr5.5.3 however. Does this differ in 6+? It keeps track of packet and octet counts. With transcoding engaged for a call, it also keeps track of packet loss and duplications. It could calculate jitter, but doesn't currently do so. Also — I'm sure the question has been asked before — can RTPEngine send its own RTCP sender/receiver reports? My testing setup was: Phone --> Kamailio+RTPEngine --> Kamailio+RTPEngine --> Carrier (where tinkering(ITSP was happening) Is there a way to turn on backward RTCP feedback from #3 back to #2? Not currently, but we may offer that capability in the future, especially to support video in an RTP/AVP to (S)AVFP bridging scenario. Cheers ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] RTPEngine QoS statistics and leg labelling
On Wed, Feb 14, 2018 at 12:49:04PM -0500, Richard Fuchs wrote: > It keeps track of packet and octet counts. Is that the stuff exposed via the traditional $rtpstat facility? What I was really looking to ascertain is that none of the statistics available under the new rtpengine module PVs are populated without RTCP. > With transcoding engaged for a call, it also keeps track of packet > loss and duplications. It could calculate jitter, but doesn't > currently do so. Aha, thank you! Is this an aspect of the transcoding functionality, or simply non-kernelised relay? -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] RTPEngine QoS statistics and leg labelling
On 2018-02-14 12:51 PM, Alex Balashov wrote: On Wed, Feb 14, 2018 at 12:49:04PM -0500, Richard Fuchs wrote: It keeps track of packet and octet counts. Is that the stuff exposed via the traditional $rtpstat facility? What I was really looking to ascertain is that none of the statistics available under the new rtpengine module PVs are populated without RTCP. Correct, these are all currently extracted from RTCP only. With transcoding engaged for a call, it also keeps track of packet loss and duplications. It could calculate jitter, but doesn't currently do so. Aha, thank you! Is this an aspect of the transcoding functionality, or simply non-kernelised relay? Both are needed. Without transcoding engaged for a call, rtpengine ignores most aspects of RTP, including sequence numbers and timestamps, which would be needed for stats keeping. Cheerse ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] RTPEngine Transcoding
Hello, So which version is the one with transcoding and repacketization support enabled? I don't see anything relevant in debian/changelog, not even in current master branch (which apparently will become version 6.2.x.x at some point). Is this baked in latest release mr6.1.1.1? Thanks! BR, George On 13 February 2018 at 22:34, Social Boh wrote: > Hi List, > > I just read on the RTPEngine page the Proxy RTP now support transcoding: > > https://github.com/sipwise/rtpengine#transcoding > > is there a plan to support it? > > Regards > > -- > --- > I'm SoCIaL, MayBe > > > ___ > 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
Re: [SR-Users] RTPEngine Transcoding
On 2018-02-14 04:07 PM, George Diamantopoulos wrote: Hello, So which version is the one with transcoding and repacketization support enabled? I don't see anything relevant in debian/changelog, not even in current master branch (which apparently will become version 6.2.x.x at some point). Is this baked in latest release mr6.1.1.1? Thanks! It's in current master and will be in 6.2. It's not in 6.1. Cheers ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] KEMI
They are created in C code and not visible as .py files. On Feb 15, 2018 12:03 AM, "Grant Bagdasarian" wrote: > Hi, > > Where would one get the files which are imported when creating a Kamailio > file using python? > import Router.Logger as Logger > import KSR as KSR > > Would be awesome if we could reference these and get code completion when > using for instance Visual Studio code. > So, basically, I'm looking for the KSR.py and Router.py files, but I > cannot find them. > > Regards, > Grant > > -Original Message- > From: sr-users [mailto:sr-users-boun...@lists.kamailio.org] On Behalf Of > Daniel-Constantin Mierla > Sent: woensdag 7 februari 2018 16:02 > To: Aleksandar Sosic > Cc: Kamailio (SER) - Users Mailing List > Subject: Re: [SR-Users] KEMI > > I am more into Lua when it comes on doing something the native > kamailio.cfg cannot do, that's because Lua has a decent range of extensions > (external Lua libraries). > > JavaScript was added for those that do not need a lot of external > extensions, but want to have script reload. > > Same for Squirrel, but that language is not so popular as JavaScript, > however, there could be people liking it, being very minimal, thus > expecting to need very low resources. > > Anyhow, once implemented, a kemi interpreter module should not need much > maintenance. New kemi functions will be exported directly from the other > modules. > > Cheers, > Daniel > > > On 07.02.18 14:12, Aleksandar Sosic wrote: > > Thanks Dan for the extensive answer! > > > > My last question then is what kemi language do you use personally? :D > > > > Kind regards, > > -- > > Aleksandar Sosic > > mail: alex.so...@timenet.it > > skype: alex.sosic > > cell: +385 91 2505 146 > > > > > > On Tue, Feb 6, 2018 at 8:44 PM, Daniel-Constantin Mierla > > wrote: > >> The C code is the same for 99% of the KSR functions available either > >> in python or javascript (or the other kemi languages). Only KSR.pv > >> and KSR.x functions are implemented in the app_python or app_jsdt > modules. > >> So if such a KSR function is broken, it is the same everywhere > >> > >> Probably KSR.pv can be moved in a common place, but KSR.x are > >> specific extensions for each interpreter, so it will stay in app_*. > >> > >> Then of course, it is a matter of the script interpreter, python vs > >> js ducktape, which are external project, we just bind to them. Also, > >> it is about the maintenance of app_python and app_jsdt. I am not the > >> developer of app_python and I cannot assert its state, I just added > >> the kemi enhancement. app_jsdt was developed by me, but I haven't > >> used it extensively so far. > >> > >> Probably you can do some basic configs and test yourself and see what > >> fits your needs better, you can start from the examples at: > >> > >> - > >> https://github.com/kamailio/kamailio/tree/master/misc/examples/kemi > >> > >> In long term, you have to look at the extensions you may need, what > >> python offers vs ducktape js interpreter in terms of their own > >> extensions and libraries. > >> > >> Cheers, > >> Daniel > > -- > Daniel-Constantin Mierla > www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced > Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World > Conference - May 14-16, 2018 - www.kamailioworld.com > > > ___ > 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
[SR-Users] [BUG?] 5.1.1 python_exec, extra chars ' 0' appended to args
Using 5.1, the python_exc args string is getting an extra [_0' appended
When I call python_exec("method", "string");
In python:
def method(self, msg, args):
KSR.info("DBG: {} {} {}".format(msg, args))
This will show 'string 0'; instead of string.
AAlba
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] [IGNORE] 5.1.1 python_exec, extra chars ' 0' appended to args
Apologies for the noise; it is working now. Not sure how I got the extra " 0" appended to the method arguments for python_exec(). AAlba ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
