Hi!
I'm working with kamailio and rtpproxy.
When I configure the clients to send sip messages through TCP adding the
";transport=tcp" in the sip message the rtpproxy is not working anymore.
The code is never passing the point pasted below, inside route[NATMANAGE]
in kamailio.cfg
if (!(isflagset(FLT_NATS) || isbflagset(FLB_NATB))) return;
Therefore, rtpproxy_manage("co"); is never reached.
Could it be a parsing problem? ( check_route_param("nat=yes") )
The config file is exactly the same as the one provided in the kamailio
repository (the default one)
Thanks!
Hi people!
After a bit of research and lib installations, I've managed to build the
full kamailio deb packages for a raspberry pi 3 (version B) running
raspbian stretch (lite) that can be found at [1] (with a really few module
exceptions that might be used in really specific scenarios -> I think)
Just for fun, I'm planning to do some CPS stats tomorrow (if I got the
time), with a basic config and also share here, but, if someone else tried
it before and is able to share some stats/benchmarks, would be greatly
appreciated (and interesting to compare, given my "decent" rpi overclock),
because I'm also curious about VoIP stuff on raspberry pi! :D
[1] https://github.com/smititelu/rpi/tree/master/kamailio/5.1.1
Thank you,
Stefan
Hi everyone,
we're valuating on rewriting our kamailio routes in python.
We're doing a lot of string manipulation and GraphQL API queries so
the kamailio scripting language is a little bit limited for this use
case.
Can someone tell us if the KEMI framework is stable enough for production?
Kind regards,
--
Aleksandar Sosic
mail: alex.sosic(a)timenet.it
skype: alex.sosic
cell: +385 91 2505 146
Hello,
I'm trying to use this configuration:
Softphone A audio codec g722 and Opus
Softphone B audio codec PCMA and PCMU
Kamailio with rtpengine_manage with codec-transcode-PCMU
codec-transcode-PCMA in the request
Softphone A call Softphone B
The RTPEngine DEBUG show many Decoder Error:
https://pastebin.com/k1Zhw8HS
Thank you
Regards
---
I'm SoCIaL, MayBe
El 13/02/2018 a las 20:05, Richard Fuchs escribió:
> On 2018-02-13 07:22 PM, Social Boh wrote:
>> Thank you.
>>
>> which is the best way to implement ir
>>
>> codec-strip-all and the add codecs?
>>
>> Is there a document about how work the transcoding?
> It's really up to you and depends on what you want to achieve. Doing a
> strip-all and then adding codecs you want to offer is definitely one
> way. Another is to just add codecs that you know or think the peer may
> want to see.
>
> Cheers
>
5.1.1: if python_exec method returns 0, then the script hangs
If the python_exec method return -1, then expressions treat it as if
it returned zero.
Somewhere there seems to be an offset by 1 issue.
if (!python_exec("method")) {
# if you return -1, the script does not hang but treated like zero
}
##################
Example 1:
class kamailio(object):
def hello(self, msg):
KSR.info("hello, world\n")
return 0
Calling: python_exec("hello")
will cause script hang
###################
Example 2:
class kamailio(object):
def hello(self, msg):
KSR.info("hello, world\n")
return -1
Calling python_exec("hello")
if (!python_exec("hello")) {
## method returns -1
## why did we get here?
xlog("L_INFO","method return zero!\n");
}
shows INFO: <script>: method return zero!
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
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
Hello,
I am excited about the new media statistics from RTPEngine, exposed
conveniently into PVs, e.g. jitter, packet loss, MOS, time offset of
lowest and highest MOS scores, etc. Great work!
I am, however, having a bit of trouble understanding how to properly
apply this new functionality, as it is not clearly documented (IMHO):
1. What is the meaning of "global" statistics which do not take into
account an "A" and a "B" side? That is to say, if I have a packet loss
or a jitter or MOS score statistic using just the generic toplevel
values, e.g.
https://kamailio.org/docs/modules/5.1.x/modules/rtpengine.html#rtpengine.p.…
What does that mean?
A functional call ordinarily consists of an inbound and outbound RTP
stream direction relative to the endpoints on both sides of RTPEngine.
Inbound A --> server --> Outbound A
Outbound B <-- server <--- Inbound B
Where do the "global" stats situate themselves in relation to all this?
2. I am given to understand that the statistics for the "A" and "B"
sides of a bidirectional RTP stream can be separated based on an
arbitrary label, using these PVs:
https://kamailio.org/docs/modules/5.1.x/modules/rtpengine.html#rtpengine.p.…https://kamailio.org/docs/modules/5.1.x/modules/rtpengine.html#rtpengine.p.…
How do I use it properly?
My intuition was to try something like this:
rtpengine_offer("replace-origin replace-session-connection ICE=remove label=outbound");
And in the answer/manage handler on the SDP answer:
rtpengine_answer("replace-origin replace-session-connection ICE=remove label=inbound");
Later, when processing a BYE and obtaining subsequent media statistics,
I tried this:
if(check_route_param("proxy_media=yes")) {
$avp(rtpengine_a_label) = 'outbound';
$avp(rtpengine_b_label) = 'inbound';
rtpengine_delete();
route(LOG_RTPENGINE_STATS);
}
But this only gets me stats for the "A" leg in the JSON object I emit:
{
"server_addr": "udp:127.0.0.1:5050",
"a_label": "outbound",
"b_label": "inbound",
"a_leg": {
"min": {
"mos": "4.4",
"at": "0:04",
"packetloss": "0",
"jitter": "0",
"roundtrip": 0
},
"max": {
"mos": "4.4",
"at": "0:04",
"packetloss": "0",
"jitter": "0",
"roundtrip": 0
},
"avg": {
"mos": "4.4",
"packetloss": "0",
"jitter": "0",
"roundtrip": 0,
"samples": 2
}
},
"b_leg": {
"min": {
"mos": "<null>",
"at": "<null>",
"packetloss": "<null>",
"jitter": "<null>"
},
"max": {
"mos": "<null>",
"at": "<null>",
"packetloss": "<null>",
"jitter": "<null>"
},
"avg": {
"mos": "<null>",
"packetloss": "<null>",
"jitter": "<null>"
}
}
}
I also tried rtpengine_delete("label=inbound") (and outbound) individually.
Some clarity on how this all fits together would be appreciated. :-)
Many thanks to Sipwise for great work on it!
-- 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/
