sr-users

sr-users@lists.kamailio.org

42 participants
37519 discussions

RTPengine: shouldn't SDP <sess-version> be incremented when SDP is updated in-dialog?
by George Diamantopoulos 20 Nov '18

20 Nov '18

Hello all, I have the following issue (I think) with RTP engine. An INVITE comes in, and rtpengine will rewrite the SDP accordingly, as configured in kamailio.cfg. After some time a reINVITE is sent out in the opposite direction, for session refresh purposes. As I use rtcp-mux-offer in kamailio.cfg for this direction, RTPengine will inject the rtcp-mux parameter, and this reINVITE is forwarded to the UAC that sent the original INVITE. However, the SDP in the reINVITE is exactly the same as the SDP in the 200 OK to the original INVITE, with the exception of the rtcp-mux parameter. Since the SDP offered from the same end has changed, shouldn't session version be incremented as well? Does this sound like something that should be reported as a bug to rtpengine? Or am I missing something here? Thanks! Best regards, George Diamantopoulos

3 4

Number of sql connections
by Duarte Rocha 19 Nov '18

19 Nov '18

Greetings, I have my core parameter listen like this : listen=udp:eth0 children=12 Like this and the other settings, my kamailio has 21 threads and 20 Sql connections. If I add more listens, listen=udp:eth0 listen=udp:eth0:5072 listen=udp:eth0:5074 Now I have 45 threads and 45 Sql connections. Why does this happen and can i set a a number of threads and/or sql connections that doesn't change with the number of "listen" parameters that i have ? Best Regards, Duarte Rocha

3 2

recording audio stream
by bill＠telopar.net 18 Nov '18

18 Nov '18

Hi All: I have a project that requires that I record the audio streams from an ongoing phone call. It seems that rtp_proxy module should do that, but I can't seem to get it to work. My config file: *if(nat_uac_test("8")) { //rtpproxy_manage("co"); xlog("L_INFO", "rtpproxy Call is going to private IPv4 Media Server Engage RTPProxy Now\n"); rtpproxy_manage("crwie","10.1.1.2"); } else { //rtpproxy_manage("cor"); xlog("L_INFO", "rtpproxy Call is coming from a private IPv4 Media Server Engage RTPProxy Now\n"); rtpproxy_manage("crwei","10.1.1.2"); } *There appears to be conversations going on with rtpproxy on both legs of the call. But I seem to be missing the step that records the audio*. *Anybody have an example of how to do this. TIA, Bill **

4 3

Which algorithm to use as load-balance
by David Villasmil 16 Nov '18

16 Nov '18

Hello, Is it possible to set an algorithm like the following? fs1 - Priority 10 - maxload 20 calls fs2 - Priority 10 - maxload 20 calls fs3 - Priority 9 - maxload 20 calls fs4 - Priority 8 - maxload 20 calls fs5 - Priority 7 - maxload 20 calls So that, whenever any new call comes in, fs1 and fs2 would be used, meaning the fs with the highest priority would be use UNLESS there's 20 calls on that server, in which case, the next server with the highest priority would be used. Thanks!, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337 ᐧ

2 7

Freeradiusclient Interim-Update Support
by Hamid Hashmi 16 Nov '18

16 Nov '18

Dear All Is module acc_radius supports interim updates? If yes then how to configure it. Regards Hamid R. Hashmi

2 3

textops module get_body_part function gives boundary error even if not multipart
by YAS0 CANER 16 Nov '18

16 Nov '18

Hello, i try to get content from Invite request but it gives boundary error. it is not multipart or mixed content but it checks boundary and gives error. Thanks. My message INVITE Content-Type: application/resource-lists+xml <resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists"> <list> <entry uri="100?Call-ID=$calli&From=$fromtag&To=$toTag&Session-ID=1"/> <entry uri="103?Call-ID=$calli2&From=$fromtag2&To=$toTag2&Session-ID=2"/> </list> </resource-lists> static int ki_get_body_part_helper(sip_msg_t* msg, str* ctype, pv_spec_t *dst, int mode) { ... if(get_boundary(msg, &boundary)!=0) { LM_ERR("Cannot get boundary. Is body multipart?\n"); return -1; } .... int get_boundary(struct sip_msg* msg, str* boundary) params.s = memchr(msg->content_type->body.s, ';',msg->content_type->body.len); if (params.s == NULL) { LM_INFO("Content-Type hdr has no params <%.*s>\n", msg->content_type->body.len, msg->content_type->body.s); return -1; }

1 0

signal 15 received and .. on Kamailio 5.1.6
by AL RSM 16 Nov '18

16 Nov '18

Hi, I just installed Kamailio 5.1.6 on Ubuntu 18.04. Starting Kamailio with the default config will give us the following in the log. Is this normal? Is there a way to fix this issue? Thanks, AL Nov 15 14:01:59 lab-proxy03 kamailio[13544]: * Stopping Kamailio SIP Server: kamailio Nov 15 14:01:59 lab-proxy03 /usr/local/sbin/kamailio[5182]: NOTICE: <core> [main.c:692]: handle_sigs(): Thank you for flying kamailio!!! Nov 15 14:01:59 lab-proxy03 /usr/local/sbin/kamailio[5213]: INFO: <core> [main.c:819]: sig_usr(): signal 15 received Nov 15 14:01:59 lab-proxy03 /usr/local/sbin/kamailio[5212]: INFO: <core> [main.c:819]: sig_usr(): signal 15 received .... Nov 15 14:01:59 lab-proxy03 /usr/local/sbin/kamailio[5182]: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Nov 15 14:02:00 lab-proxy03 kamailio[13544]: ...done. Nov 15 14:02:00 lab-proxy03 kamailio[13556]: * Starting Kamailio SIP Server: kamailio Nov 15 14:02:00 lab-proxy03 kamailio: INFO: <core> [core/sctp_core.c:74]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Nov 15 14:02:00 lab-proxy03 kamailio: INFO: <core> [core/tcp_main.c:4721]: init_tcp(): using epoll_lt as the io watch method (auto detected) .... Nov 15 14:02:00 lab-proxy03 /usr/local/sbin/kamailio[13596]: INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded Nov 15 14:02:00 lab-proxy03 /usr/local/sbin/kamailio[13596]: INFO: rr [rr_mod.c:175]: mod_init(): outbound module not available Nov 15 14:02:00 lab-proxy03 /usr/local/sbin/kamailio[13596]: INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Nov 15 14:02:00 lab-proxy03 /usr/local/sbin/kamailio[13596]: INFO: <core> [core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Nov 15 14:02:00 lab-proxy03 /usr/local/sbin/kamailio[13596]: INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Nov 15 14:02:00 lab-proxy03 /usr/local/sbin/kamailio[13596]: INFO: <core> [core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Nov 15 14:02:00 lab-proxy03 /usr/local/sbin/kamailio[13618]: INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/13618 Nov 15 14:02:00 lab-proxy03 /usr/local/sbin/kamailio[13619]: INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) Nov 15 14:02:00 lab-proxy03 kamailio[13556]: ...done.

2 1

priority load balance
by David Villasmil 15 Nov '18

15 Nov '18

Hello, Trying to do priority load balancing (8) but i'm getting an error `unable to update destination load - classic dispatching` anyone knows why? i've got ```modparam("dispatcher", "db_url", DBURL) modparam("dispatcher", "table_name", "dispatcher") modparam("dispatcher", "flags", 2) modparam("dispatcher", "dst_avp", "$avp(AVP_DST)") modparam("dispatcher", "grp_avp", "$avp(AVP_GRP)") modparam("dispatcher", "cnt_avp", "$avp(AVP_CNT)") modparam("dispatcher", "dstid_avp", "$avp(dsdstid)") modparam("dispatcher", "attrs_avp", "$avp(dsattrs)")``` Looking at the code, dstid_avp would be null, but not sure why? I have set in the table the priorities as 10 for 2 gws (edited) Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337 ᐧ

2 1

"signal 15 received" and ... on Kamailio 5.1.6
by AL RSM 15 Nov '18

15 Nov '18

1 0

REFER packet - Kamailio gives request_uri instead request-uri -
by YAS0 CANER 15 Nov '18

15 Nov '18

Hello, i test on refer packet on Kamailio 5.3-dev . it gives route_uri (@route_uri) instead of request-uri ($ru). Could you give me help about it please. Thanks. Packet 2018/11/15 10:51:20.522512 192.168.1.109:5080 -> 192.168.1.120:5060 REFER sip:100@192.168.1.120 SIP/2.0 CSeq: 1 REFER From: <sip:105@192.168.1.120;transport=UDP>;tag=10215SIPpTag001 To: <sip:100@192.168.1.120;transport=UDP>;tag=7e3fb504 Call-ID: 1-10215(a)192.168.1.109 Max-Forwards: 70 Route: <sip:192.168.1.120;lr> Via: SIP/2.0/UDP 192.168.1.136:5080;branch=z9hG4bK-10215-1-7 Contact: <sip:105@192.168.1.136:5080> Refer-To: <sip:103@192.168.1.120> Referred-By: <sip:105@192.168.1.120;transport=UDP> Content-Length: 0 1(48532) WARNING: {1 1 REFER 1-10215(a)192.168.1.109} <script>: REFER in WITHINDLG [$ru sip:192.168.1.120;lr ] 1(48532) WARNING: {1 1 REFER 1-10215(a)192.168.1.109} <script>: REFER MYROUTE [ru sip:192.168.1.120;lr ] [route_uri sip:192.168.1.120;lr ] [ rU <null> ] Scenairo SIPP UAC -> Kamailio - > UAC 2 After call answered , SIPP send REFER request as above.

1 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users