Re: [SR-Users] How to add a new module to existing Kamailio Server?

How did you install kamailio in the first place? I use a packet manager to install kamailio and any additional module that i need afterwards. Tihomir. Sent from my iPhone > On 13 Feb 2018, at 11:59, Arun NV wrote: > > I am using a Kamailio 4.4 server. And I would

Re: [SR-Users] RTPEngine QoS statistics and leg labelling

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

[SR-Users] How to add a new module to existing Kamailio Server?

I am using a *Kamailio 4.4* server. And I would like to install *http_async_client* module to this server. I have looked in the module directory(*/usr/local/lib64/kamailio/modules*) to check whether this *http_async _client* module already exists there, but it was not there. And I searched for a

Re: [SR-Users] RTPEngine QoS statistics and leg labelling

All right, I think what I have learned is that the stats simply aren't being collected for the SSRC in the endpoint that corresponds to my "inb" (inbound) label — just the "outb" (outbound): Here's the complete dump. Note in the MOS stats that the stats for this SSRC are empty: 222410830

Re: [SR-Users] RTPEngine QoS statistics and leg labelling

Well, both the 'query' command and final logging confirm that the labels are correct for the respective from-tags: Feb 14 05:10:32 evaristesys-legacy rtpengine[7354]: INFO: [c6fa30199831602c397d627d5a2662d3]: Final packet stats: Feb 14 05:10:32 evaristesys-legacy rtpengine[7354]: INFO:

Re: [SR-Users] RTPEngine QoS statistics and leg labelling

Ah, okay, coercing it to use Convert::Bencode (for lack of CentOS rh524-perl Bencode module) was not a productive thing to do. :-) On Tue, Feb 13, 2018 at 09:29:49PM -0500, Alex Balashov wrote: > After I finally got the Perl client to work, unfortunately it raised > more questions than answers.

Re: [SR-Users] RTPEngine QoS statistics and leg labelling

On Tue, Feb 13, 2018 at 07:34:30PM -0500, Richard Fuchs wrote: > The average is the average between the two, the min is the min between > the two, and the max is the max between the two. Ach so! Jetzt alles ist klar! -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 /

Re: [SR-Users] RTPEngine QoS statistics and leg labelling

On 2018-02-13 07:32 PM, Alex Balashov wrote: Hi Richard, On Tue, Feb 13, 2018 at 06:34:53PM -0500, Richard Fuchs wrote: It's the min, max, and average between the two call legs (and other contributing sources that may have been involved in the call). When you say "between", do you mean the

Re: [SR-Users] RTPEngine QoS statistics and leg labelling

Hi Richard, On Tue, Feb 13, 2018 at 06:34:53PM -0500, Richard Fuchs wrote: > It's the min, max, and average between the two call legs (and other > contributing sources that may have been involved in the call). When you say "between", do you mean the average of the values of the two respective

Re: [SR-Users] RTPEngine QoS statistics and leg labelling

On 2018-02-13 06:16 PM, Alex Balashov wrote: ... 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"

Re: [SR-Users] RTPEngine Transcoding

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

[SR-Users] RTPEngine QoS statistics and leg labelling

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

Re: [SR-Users] RTPEngine Transcoding

On 2018-02-13 06:07 PM, Social Boh wrote: Thank you for your answer but I don't see any option to activate transcoding on Kamailio RTPEngine module Just use the options as described in rtpengine's readme. Kamailio's module will pass them through just fine. Cheerse

Re: [SR-Users] RTPEngine Transcoding

Thank you for your answer but I don't see any option to activate transcoding on Kamailio RTPEngine module Regards --- I'm SoCIaL, MayBe El 13/02/2018 a las 17:49, Richard Fuchs escribió: > On 2018-02-13 03:34 PM, Social Boh wrote: >> Hi List, >> >> I just read on the RTPEngine page the Proxy

Re: [SR-Users] ways to track all messages of a dialog

Also for real time monitoring you can try sngrep tool Original Message Subject: [SR-Users] ways to track all messages of a dialogFrom: Fabian Borot To: sr-users@lists.kamailio.orgCC: I need to track all messages (SIP Requests, SIP Responses) for some SIP

Re: [SR-Users] ways to track all messages of a dialog

I think you need to read about sipcapture moduleAlso you can manage to install homer server which is very important in any sip enviromentRegards Original Message Subject: [SR-Users] ways to track all messages of a dialogFrom: Fabian Borot To:

Re: [SR-Users] Use RTPProxy in 302 scenario

Thank you Daniel, I think I need to call it at least 2 times to get the IP:Port combination to be used on the call, then a 3rd time to release the resources (I call it in the loose_route() route section for the ACK and BYE etc): 1- when the request to the Providers obtained in the 302 Response

[SR-Users] Can rtpengine change network interface of estabished call?

Hi, Is it possible to define two pairs of network interfaces for rtpengine, e.g. int/ext and up/down? If so during a call established between interfaces 'int' and 'ext', is it possible to send a re-INVITE from the calling party on interface 'ext', to update the RTP destination to an IP on a

Re: [SR-Users] (no subject)

Hello, if you set use_received param for path module, then the received address in Route header is set as dst uri, see:   - https://www.kamailio.org/docs/modules/stable/modules/path.html#path.p.enable_r2 All you need to do is: loose_route(); t_relay(); Note that loose_route() is dealing with

Re: [SR-Users] (no subject)

Hi Daniel, thanks for you e-mail... i will try that approach. in the main time i exploited the "received" parameter in route header sent by freeswitch and with a bit of manipulation i managed to rout the call back to WS client :=) Im will definitely try to enable r2 and come back with the

Re: [SR-Users] (no subject)

Hello, you have an explicit set of $fs, which is setting the send socket. You have to do then when receiving from WS, not when going to WS. In 5.1, you can try to enable:   - https://www.kamailio.org/docs/modules/stable/modules/path.html#path.p.enable_r2 and then let kamailio do all about send

Re: [SR-Users] onend_route() ?

Hello, the onsend_route is a routing block that you only need to define, like: onsend_route {     xlog("outgoing buffer is: [[$sndto(buf)]]\n"); } Cheers, Daniel On 09.02.18 22:01, Wilkins, Steve wrote: > >   > > I meant to reply to Kamailio mailing list. > > *From:*Wilkins, Steve > *Sent:*

Re: [SR-Users] Request Timeouts

Hello, can you paste here the full content of such INFO request received by kamailio (as text)? The 408 means that kamailio tried to forward it, but the target didn't reply. Cheers, Daniel On 11.02.18 17:56, Wilkins, Steve wrote: > Hi All, Alex > > Alex, you mentioned you might know why