sr-users

sr-users@lists.kamailio.org

10 participants
37525 discussions

Call termination via dialog RPC dlg.end_dlg for the SIP-UA behind NAT
by Denys Pozniak 11 Sep '18

11 Sep '18

Hello! When calling RPC command dlg.end_dlg, BYE for leg behind NAT sends according to the Contact header not to the real ip:port. RPC ul.dump shows correct address in Received: sip:2.2.2.2:7488, but looks dialog does not know real address. How can I force sending to the real address? [root@proxy1]# kamcmd dlg.list { h_entry: 3753 h_id: 6741 call-id: 0_618427980(a)10.10.10.10 from_uri: sip:1234567890@1.1.1.1:5060 to_uri: sip:3333333333@1.1.1.1:5060 state: 2 start_ts: 0 init_ts: 1536671492 timeout: 0 lifetime: 7200 dflags: 512 sflags: 4096 iflags: 32 caller: { tag: 2750096738 contact: sip:1234567890@10.10.10.10:5060 cseq: 2 route_set: socket: udp:1.1.1.1:5060 } callee: { tag: contact: cseq: route_set: socket: } profiles: { } variables: { } } [root@proxy1]# kamcmd ul.dump Info: { AoR: 1234567890 HashID: 262653578 Contacts: { Contact: { Address: sip:1234567890@10.10.10.10:5060 Expires: 1269 Q: -1.000000 Call-ID: 0_213504837(a)10.10.10.10 CSeq: 8 User-Agent: Yealink SIP-T21P Received: sip: 2.2.2.2:7488 Path: [not set] State: CS_NEW Flags: 0 CFlags: 65600 Socket: udp: 1.1.1.1:5060 Methods: 16383 Ruid: uloc-5b97c358-6052-1 Instance: [not set] Reg-Id: 0 Server-Id: 0 Tcpconn-Id: -1 Keepalive: 1 Last-Keepalive: 1536674159 Last-Modified: 1536674159 } } } -- BR, Denys Pozniak

1 0

Remove branch from branch list
by Yuriy Gorlichenko 11 Sep '18

11 Sep '18

Hi I'm trying to manipulate with branches at the $branch variable. 8 actually need to remove unneeded branch if not passed some checks. For now I Just rewriting uri and dst_uri with some face address but it looks little bit dirty way. Is here any an other more clear way to do this?

2 2

Record Routes
by Wilkins, Steve 11 Sep '18

11 Sep '18

Hello All, Can a Route: be removed?, if so, how? Thank you?

2 4

Logging of messages generated by Kamailio itself
by Konstantin Polyakov 11 Sep '18

11 Sep '18

Hello, Could somebody help with one issue? In some cases Kamailio can send messages itself. For example, when fr_inv_timer is expired Kamailio sends 408 to the INVITE sender and CANCEL to the INVITE receiver. These two messages (408 and CANCEL) are not printed into the log and I cannot find a way to do that. There are also other scenarios when some Kamailio modules send SIP messages by its own. So is there way to print out into log all such messages? My goal is to get full message flow in the log per certain call-id. Thank you in advance. Best regards. Konstantin

2 9

kamailio + rtpengine + custom filename
by Жан Базаров 11 Sep '18

11 Sep '18

Hello! Filenames have the format <call_ID>-<random>-<SSRC>.<extension> How i can change filename in start_recording() ???

2 1

tpops module
by volga629＠networklab.ca 11 Sep '18

11 Sep '18

Hello Everyone, I am using tcpops module for keepalive and on BYE when tcp keeplaive close is called produce this error in log. Sep 8 11:21:26 canlvprx01 /usr/sbin/kamailio[18933]: ERROR: <core> [core/sr_module.c:1781]: get_int_fparam(): Could not convert PV to int Sep 8 11:21:26 canlvprx01 /usr/sbin/kamailio[18933]: ERROR: tcpops [tcpops_mod.c:293]: w_tcp_keepalive_disable1(): invalid parameter 'con' (must be a number) kamailio-5.1.3-1.gitf0dce0c99.fc27.x86_64 if (is_method("BYE|CANCEL")) { $avp(bye_conid) = $conid; rtpengine_delete(); t_on_reply("4"); } onreply_route[4] { if(is_method("BYE") && t_check_status("200")) { tcp_keepalive_disable("$avp(bye_conid)"); } } volga629

3 3

Simultaneous usage of t_on_reply() and t_on_failure()
by Володимир Іванець 10 Sep '18

10 Sep '18

Hello everyone, I wanted to ask those who know if Kamailio's behavior I'm facing is expected or I should make some improvements to the configuration. Kamailio version is 5.1.0. I have a route where RTPEngine parameters are being collected and *rtpengine_offer()* is called. After that *t_on_reply("REPLY_SIP_TO_SIP");* followed by the *t_on_failure("FAILURE_SIP_TO_SIP");* are used. The idea is to process all responces except 415 or 488 from UAC as usual in *onreply_route[REPLY_SIP_TO_SIP]* and use *failure_route[FAILURE_SIP_TO_SIP]* to update SDP with *rtpengine_offer()* if necessary. *onreply_route[REPLY_SIP_TO_SIP]* just goes to *exit;* if *$rs* equals 415 or 488. This works fine with Htek phone which sends 100, 180 and then 488. But I can not see *failure_route[FAILURE_SIP_TO_SIP]* execution for calls to Zoiper which replies with 100 and immediately 415. t_on_failure(failure_route) documentation says: "Sets failure routing block, to which control is passed after a transaction completed with a negative result but before sending a final reply." and to be honest I don't really understand how lacking of responce prevents failure_route from executing. Thanks a lot!

4 5

Crashed kamailio drouting
by Евгений Голей 08 Sep '18

08 Sep '18

Good evening. I have errors on the server (kamailio v 5.1.0) "kamailio [30529]: segfault at 0 ip 00007f9c00c29cfb sp 00007fffa9808310 error 4 in drouting.so [7f9c00c26000 + 39000]" which cause the service to stop. Although the drouting module has been used for a long time, this has never happened. This was done after adding the functions of the dispatcher module. What could be the reason ? Example error in system kamailio [20728]: segfault at 0 ip 00007f32c1c8fcfb sp 00007fff78430d00 error 4 in drouting.so [7f32c1c8c000 + 39000] in the logs of kamailio 018-09-08T22: 30: 29.0448 "ALERT: <core> [main.c: 746]: handle_sigs (): child process 10556 exited by a signal 11" 2018-09-08T22: 30: 29.0452 "ALERT: <core> [main.c: 749]: handle_sigs (): core was generated" 2018-09-08T22: 30: 29.0456 "INFO: <core> [main.c: 771]: handle_sigs (): terminating due to SIGCHLD" -- BR Evgeniy

1 0

kamailio.cfg errors with this example from documentation
by Wilkins, Steve 07 Sep '18

07 Sep '18

$var(x) = "abcd"; $(var(x){s.substr,1,0}); Hello all, I took the example from the documentation, but Kamailio.cfg has errors with this example. Errors=> 0(14444) CRITICAL: <core> [core/cfg.y:3489]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 827, column 1-23: pvar with transformations in assignment left side 0(14444) CRITICAL: <core> [core/cfg.y:3492]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 827, column 24: syntax error 0(14444) CRITICAL: <core> [core/cfg.y:3492]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 827, column 24: bad command Thank you,

2 5

Via header line missing
by Karlheinz Knapp 07 Sep '18

07 Sep '18

Hi, hm.... the only reason why I'm playing with kamailio is that it should be able to translate IPv6 from customer phones behind Fritz!Box (NAT) to IPv4 used by the provider (which is not able to handle IPv6). But it looks that he accept in general the packet with 2 Via lines (also with IPv6 as address) and send a normal reply. The second Via is not needed, because he have to send to the first Via. And if it really comes to trouble, I can remove it with kamailio :) If it is not possible to make a complete translation with kamailio, then I have to search again for an other solution. But still: why is this one Via line not transmitted on the IPv6 side? Only when I do some modifications it appears magically. That's not a normal behaviour in my opinion. If you or Henning can not reproduce this behaviour, then it's possible that I start TeamViewer and I can show this on our installation (only at normal working hours). Btw. I use sngrep to display all the messages, but it works stable and reliable. Best regards, i.A. Bernd

1 0

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