sr-users

sr-users@lists.kamailio.org

42 participants
37519 discussions

ACC module
by Voip support 13 Feb '20

13 Feb '20

Dear Community, I have setup ACCDB module to save missed / failed and successful calls. My issue is that i am getting duplicated entries for INVITE / BYE in acc database table. For example: id;method;from_tag;to_tag;callid;sip_code;sip_reason;time;src_ip;dst_user;dst_domain;src_user;src_domain;cdr_id 231838;INVITE;21-7FC1D85;1914472180948750;KKyIdaaJceAu7pzN(a)172.16.0.35;200;OK;2020-02-11 19:16:28;22.33.44.55;nlb124#78019989897056;11.11.11.11;asterisk;172.16.0.35;0 231839;INVITE;21-7FC1D85;1914472180948750;KKyIdaaJceAu7pzN(a)172.16.0.35;200;OK;2020-02-11 19:16:28;22.33.44.55;nlb124#78019989897056;11.11.11.11;asterisk;172.16.0.35;0 231840;INVITE;21-7FC1D85;1914472180948750;KKyIdaaJceAu7pzN(a)172.16.0.35;200;OK;2020-02-11 19:16:28;22.33.44.55;nlb124#78019989897056;11.11.11.11;asterisk;172.16.0.35;0 231841;BYE;21-7FC1D85;1914472180948750;KKyIdaaJceAu7pzN(a)172.16.0.35;200;OK;2020-02-11 19:16:36;22.33.44.55;;190.196.153.130;asterisk;172.16.0.35;0 231842;BYE;21-7FC1D85;1914472180948750;KKyIdaaJceAu7pzN(a)172.16.0.35;200;OK;2020-02-11 19:16:36;22.33.44.55;;190.196.153.130;asterisk;172.16.0.35;0 231844;BYE;21-7FC1D85;1914472180948750;KKyIdaaJceAu7pzN(a)172.16.0.35;200;OK;2020-02-11 19:16:36;22.33.44.55;;190.196.153.130;asterisk;172.16.0.35;0 Following way: # ----- acc params ----- /* what special events should be accounted ? */ modparam("acc", "early_media", 0) modparam("acc", "report_ack", 0) modparam("acc", "report_cancels", 0) /* by default ww do not adjust the direct of the sequential requests. * if you enable this parameter, be sure the enable "append_fromtag" * in "rr" module */ modparam("acc", "detect_direction", 0) /* account triggers (flags) */ modparam("acc", "log_flag", FLT_ACC) modparam("acc", "log_missed_flag", FLT_ACCMISSED) modparam("acc", "log_extra", "src_user=$fU;src_domain=$fd;src_ip=$si;" "dst_ouser=$tU;dst_user=$rU;dst_domain=$rd") modparam("acc", "failed_transaction_flag", FLT_ACCFAILED) /* enhanced DB accounting */ #!ifdef WITH_ACCDB modparam("acc", "db_flag", FLT_ACC) modparam("acc", "db_missed_flag", FLT_ACCMISSED) modparam("acc", "db_url", DBURL) #modparam("acc", "db_extra", # "src_user=$fU;src_domain=$fd;src_ip=$si;" # "dst_ouser=$tU;dst_user=$rU;dst_domain=$rd") modparam("acc", "db_extra", "src_user=$fU;src_domain=$fd;dst_user=$rU;dst_domain=$rd;src_ip=$si") # our lines modparam("acc", "cdrs_table", "acc_cdrs") modparam("acc", "cdr_on_failed", 1) #!endif Then in routing config i set setflag(FLT_ACC FLT_ACCMISSED FLT_ACCFAILED in several places. My question is - each setflag cause an entry to be saved in DB? How can i debug and resolve the issue of duplicates. I am trying to use a CDR script found somewhere on siremis sites to do the accounting but it's making trouble because due to duplicates in acc table i am getting cdrs unique key violations. Secondary question is - if a BYE is not received / lost is there any way to send a check triggered by kamailio to each caller and callee side to check if dialog is still active. I would not like to use session timers (as endpoints need to support it). Best regards, Tom

2 7

URI Mapping in Presence?
by Mark Boyce 12 Feb '20

12 Feb '20

Hi All Looking for the best way to achieve mapping from requested uri to actual uri in presence subscription. The scenario I’ve been presented with is that there is a direct relation between extension number and sip user but they are not the same thing. So for example; Extension 10 is mapped to SIP user sip-SomethingLong Extension 11 is mapped to SIP user sip-SomethingEvenLonger When extension 10 subscribes to 11 we end up with something like this; From: “Extension 10" <sip:sip-SomethingLong@ourpbx.com:5060>;tag=12345678 To: <sip:11@ourpbx.com:5060>;tag=987654321-c8bd I *think* what I need to end up with in presence db is; presently_uri = sip:sip-SomethingEvenLonger@ourpbx.com to_user = 10 (Is that right?) However I can’t see a standard way to achieve this. Manage_subscribe will let me override the watcher uri but not the watched. Anyone see a simple way to achieve this? Thanks Mark

2 2

Generating provisional responses from kamailio instance
by George Diamantopoulos 12 Feb '20

12 Feb '20

Hello all, I would like to use rtpengine's media playback capabilities in an early media scenario. The use case is as follows: * Kamailio receives an incoming INVITE * During INVITE processing, kamailio config script determines that an early media message should be played back and then the call should fail with 4xx * To that effect, Kamailio sends out a locally-generated 183 Progress and instructs rtpengine to playback an audio file * After the audio file has finished playing, kamailio responds with 4xx to the INVITE Is this possible at all? Thanks! BR, George

3 2

Kamailio crashes after Contact expires event route
by Sergiu Pojoga 12 Feb '20

12 Feb '20

Hi there, After below even route is triggered, Kamailio crashes with the following in logs: Feb 12 08:03:59 kamailio[24671]: INFO: <script>: Received HTTP/RPC request from IP=127.0.0.1 Feb 12 08:03:59 kamailio[24671]: WARNING: <script>: Contact myusername(a)sip.mydomain.net has expired Feb 12 08:03:59 kamailio[24671]: INFO: drouting [drouting.c:483]: rpc_reload(): RPC command received! Feb 12 08:03:59 kamailio[24675]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 59 Feb 12 08:03:59 kamailio[24614]: ALERT: <core> [main.c:745]: handle_sigs(): child process 24671 exited by a signal 11 Feb 12 08:03:59 kamailio[24614]: ALERT: <core> [main.c:748]: handle_sigs(): core was not generated Feb 12 08:03:59 kamailio[24614]: INFO: <core> [main.c:770]: handle_sigs(): terminating due to SIGCHLD Feb 12 08:03:59 kamailio[24675]: INFO: <core> [main.c:825]: sig_usr(): signal 15 received event_route[usrloc:contact-expired] { xlog("L_WARN", "Contact $ulc(exp=>aor) has expired\n"); # Remove the sip: from the front of the Received URI $var(exp_received) = $(ulc(exp=>received){s.substr,4,0}); sql_query("db", "UPDATE `dr_gateways` SET address = '127.0.0.1' WHERE address = '$var(exp_received)'", "rz"); sql_result_free("rz"); jsonrpc_exec('{"jsonrpc": "2.0", "method": "drouting.reload", "id": 1}'); } If I comment out the sql and jsonrpc_exec lines above - crash does not happen. Let me know if core dump is needed. Thanks, --Sergiu

2 1

RTP Engine in docker
by Voip support 12 Feb '20

12 Feb '20

Dear Community, I would like to use rtpengine but had a very hard time to do the compilation under ubuntu 16.04 and 18.04. On Ubuntu 18.04 after already compiled the rtpengine i was unable to install the deb packages. Many different errors occurred. I finally tried to install RTP engine on debian 10 and i was able to install it. I am thinking of 2 use scenarios: - handling many concurrent calls like using rtpproxy for normall traffic - make WebRTC to legacy RTP transcoding (convert WebRTC SDP to legacy SDP to use with non webrtc compliant sip server) For the first scenario i imagine that it would be far better to run in-kernel mode because of performance. For the second scenario i think userspace daemon should be fine ( i expect not much traffic maximum 50-100 calls). However my question is what is the correct order of installing the deb packages. Which packages do i really need. For running rtpengine in docker could i use Debian 10 OS and compile rtpengine and install just " ngcp-rtpengine-daemon_6.2.0.0+0~mr6.2.0.0_amd64.deb" ? (the in this case the host running docker can be any linux distribution?) If i would like to run rtpengine in docker in kernel mode - is it possible or i need to use same linux distribution in host and docker container (because of the kernel match?) Best regards, Tom

5 6

Dispatcher error with rtpptoxy
by Gaurav Bmotra 12 Feb '20

12 Feb '20

hi i m using kamailio 5.2.1 in Kubernetese on Host network it was working file but now the following issue i n getting call connecting but audio both way issue here is the logs that got -------------------------------- 2(14) ERROR: {1 2 INVITE EQEiv5Mjs-eV1OCGv6Potw..} rtpproxy [rtpproxy.c:2586]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy 4(16) ERROR: {2 2 INVITE EQEiv5Mjs-eV1OCGv6Potw..} rtpproxy [rtpproxy.c:2586]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy 4(16) NOTICE: {2 2 INVITE EQEiv5Mjs-eV1OCGv6Potw..} acc [acc.c:279]: acc_log_request(): ACC: transaction answered: timestamp=1578636040;method=INVITE;from_tag=88c92018;to_tag=2c3c0a16;call_id=EQEiv5Mjs-eV1OCGv6Potw..;code=200;reason=OK;src_user=200;src_domain=testcalls.aone.one;src_ip=157.39.9.195;dst_ouser=300;dst_user=300;dst_domain=106.78.70.57 4(16) ERROR: {2 2 INVITE EQEiv5Mjs-eV1OCGv6Potw..} db_mysql [km_dbase.c:126]: db_mysql_submit_query(): driver error on query: Unknown column 'src_user' in 'field list' (1054) 4(16) ERROR: {2 2 INVITE EQEiv5Mjs-eV1OCGv6Potw..} <core> [db_query.c:243]: db_do_insert_cmd(): error while submitting query 4(16) ERROR: {2 2 INVITE EQEiv5Mjs-eV1OCGv6Potw..} acc [acc.c:477]: acc_db_request(): failed to insert into database 6(18) ERROR: {2 2 INVITE EQEiv5Mjs-eV1OCGv6Potw..} rtpproxy [rtpproxy.c:2586]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy 8(20) NOTICE: {2 3 BYE EQEiv5Mjs-eV1OCGv6Potw..} acc [acc.c:279]: acc_log_request(): ACC: transaction answered: timestamp=1578636041;method=BYE;from_tag=88c92018;to_tag=2c3c0a16;call_id=EQEiv5Mjs-eV1OCGv6Potw..;code=200;reason=OK;src_user=200;src_domain=testcalls.aone.one;src_ip=157.39.9.195;dst_ouser=300;dst_user=300;dst_domain=106.78.70.57 8(20) ERROR: {2 3 BYE EQEiv5Mjs-eV1OCGv6Potw..} db_mysql [km_dbase.c:126]: db_mysql_submit_query(): driver error on query: Unknown column 'src_user' in 'field list' (1054) 8(20) ERROR: {2 3 BYE EQEiv5Mjs-eV1OCGv6Potw..} <core> [db_query.c:243]: db_do_insert_cmd(): error while submitting query 8(20) ERROR: {2 3 BYE EQEiv5Mjs-eV1OCGv6Potw..} acc [acc.c:477]: acc_db_request(): failed to insert into database 3(15) ERROR: {1 2 INVITE LH6sikNzpP9rXXMJvH20wQ..} rtpproxy [rtpproxy.c:2586]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy 9(21) NOTICE: acc [acc.c:279]: acc_log_request(): ACC: call missed: timestamp=1578636141;method=INVITE;from_tag=6b032a77;to_tag=;call_id=LH6sikNzpP9rXXMJvH20wQ..;code=408;reason=Request Timeout;src_user=200;src_domain=testcalls.aone.one;src_ip=157.39.9.195;dst_ouser=300;dst_user=300;dst_domain=106.78.70.57 9(21) ERROR: db_mysql [km_dbase.c:126]: db_mysql_submit_query(): driver error on query: Unknown column 'src_user' in 'field list' (1054) 9(21) ERROR: <core> [db_query.c:243]: db_do_insert_cmd(): error while submitting query 9(21) ERROR: acc [acc.c:477]: acc_db_request(): failed to insert into database 9(21) NOTICE: {1 2 INVITE LH6sikNzpP9rXXMJvH20wQ..} <script>: RTF_DISPATCH: INVITE 300 [LH6sikNzpP9rXXMJvH20wQ..] 9(21) NOTICE: {1 2 INVITE LH6sikNzpP9rXXMJvH20wQ..} <script>: RTF_DISPATCH: WARNING sip: 49.14.97.169:63353 is broken and marked as inactive 3(15) ERROR: {1 2 INVITE 2gY1N8nGCT02Ut7iAEpKWg..} rtpproxy [rtpproxy.c:2586]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy 8(20) ERROR: {2 2 INVITE 2gY1N8nGCT02Ut7iAEpKWg..} rtpproxy [rtpproxy.c:2586]: force_rtp_proxy(): incorrect port 0 in reply from rtp proxy 8(20) NOTICE: {2 2 INVITE 2gY1N8nGCT02Ut7iAEpKWg..} acc [acc.c:279]: acc_log_request(): ACC: transaction answered: timestamp=1578638074;method=INVITE;from_tag=b9979f2a;to_tag=c2952a71;call_id=2gY1N8nGCT02Ut7iAEpKWg..;code=200;reason=OK;src_user=200;src_domain=testcalls.aone.one;src_ip=157.39.9.195;dst_ouser=300;dst_user=300;dst_domain=106.78.71.32 8(20) ERROR: {2 2 INVITE 2gY1N8nGCT02Ut7iAEpKWg..} db_mysql [km_dbase.c:126]: db_mysql_submit_query(): driver error on query: Unknown column 'src_user' in 'field list' (1054) ------------------------------- plz help me thank you -- *Regards:* Gaurav Kumar

3 2

Same Via Tag for INVITE and ACK on S/L loadbalancer
by Sebastian Damm 11 Feb '20

11 Feb '20

Hi, I stumbled upon an interop problem with a carrier. We have the following scenario: Gateway --> Loadbalancer --> Carrier The loadbalancer generates a Via header for each request. But since it is stateless, the Via tag is generated for each request. As a consequence, the Via tag in the ACK differs from the one in the INVITE. And one carrier doesn't handle those ACKs if the Via tag differs. Is there a way to force the creation of a "deterministic" Via branch tag? For example, building it from a hash over call-id and from-tag or something like that? Thanks in advance Sebastian -- Sebastian Damm Voice Engineer __________________________________________ sipgate GmbH

5 10

Different REGISTER expires based on User-Agent
by mayamatakeshi 11 Feb '20

11 Feb '20

Hi, is it possible to reply with a different expires for a REGISTER depending on some condition like the User-Agent? I am thinking maybe I can use: $ulc(profile=>expires) = 600 (but my kamailio dev machine is out of service and I cannot test this right now).

5 8

Kamailio v5.1.10 Released
by Daniel-Constantin Mierla 10 Feb '20

10 Feb '20

Hello, Kamailio SIP Server v5.1.10 stable release is out. This is a maintenance release of the old stable branch, 5.1, that includes fixes since the release of v5.1.9. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.1.x. Deployments running previous v5.1.x versions are strongly recommended to be upgraded to v5.1.10, to v5.2.x or 5.3.x series. For more details about version 5.1.10 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2020/02/kamailio-v5-1-10-released/ RPM, Debian/Ubuntu packages will be available soon as well. Note: the branch 5.1 is an old stable branch, v5.1.10 being the last planned release out of it, to mark the end of official maintenance. The latest stable branches are now 5.2 and 5.3, at this time with v5.3.2 being the latest stable release. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - April 27-29, 2020 -- www.kamailioworld.com

1 0

Planning the release of v5.1.10
by Daniel-Constantin Mierla 10 Feb '20

10 Feb '20

Hello, I am considering to release Kamailio v5.1.10 on Thursday, Jan 30, 2020, to mark the end of official packaging from branch 5.1. At this moment the last two stable branches are 5.2 and 5.3. If anyone is aware of some commits for fixes that should be backported to branch 5.1, write to sr-dev. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com

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