sr-users

sr-users@lists.kamailio.org

7 participants
37522 discussions

registrar lookup with different URI
by Maarten Ureel 30 Sep '18

30 Sep '18

Hello I want the registar module to lookup a user with a different 'name' as the RURI. We have the extension & domain in variables, but the RURI is ext@ip-of-server, e.g. 200(a)1.1.1.1<mailto:200@1.1.1.1>, while we want to perform the lookup for 200(a)somedomain.tld<mailto:200@somedomain.tld>. We have somedomain.tld in a header, so we have it in a variable. However, if we perform the lookup like this (using Python module): lookup_result = KSR.registrar.lookup('location') We get a negative result, and the debug logs show that it tries to locate 200(a)1.1.1.1<mailto:200@1.1.1.1> - which makes sense. So according to docs you can specify an URI, however when I do this: lookup_result = KSR.registrar.lookup('location' '200(a)somedomain.tld') lookup_result is "False" and the function is not executed, according to docs because it cannot obtain the parameters for this function. How can we force the registrar module to lookup a different user?

1 0

Dialog timout reset when receiving a re-INVITE
by jenus＠cyberchaos.nl 30 Sep '18

30 Sep '18

Hello, I have a issue with setting the dialog timeout for a call. It works fine until i receive a re-INVITE. The re-INVITE seems to reset the dialog timeout back to the default value configured in the module parameters (7200 in my case). I use "dlg_set_timeout("900");" to set the timeout to 900 seconds. When i receive a re-INVITE i see the following in the debug logs: DEBUG: dialog [dlg_handlers.c:647]: get_dlg_timeout(): invalid AVP value, using default timeout This happens even with the "timeout_avp" module parameter disabled. I'm running kamailio 5.1.3. Thanks, Jan

3 2

Restoring htable shared variables via dmq after Kamailio restart
by Denys Pozniak 28 Sep '18

28 Sep '18

Hello! I have 2 nodes that replicates htable variables via DMQ. How can I recover them after one node restarting? -- BR, Denys Pozniak

3 2

kamailio rtp connection
by Pieter Muller 28 Sep '18

28 Sep '18

Good day all I hope Im on the right place to ask the question. Im a newbie to kamailio and have a little problem understanding how to set kamailio correctly. Scenario: VoIP Supplier (IP:161.161.252.20{Private Net}) à Connect via routing to Kamailio Server(155.155.16.2 eno2{private Net}),Kamailio Server(187.221.197.252 eno1{public facing})àconnect to PBX(public IP set in dispatcher) à connect to RTP server(Public IP) Now the problem is that if you call in Number(a)161.161.252.20 <mailto:Number@161.161.252.20> is send to kamailio, kamailio then sends it down to dispatcher IP and that PBX responds directly back via rtp server to 161.161.252.20. The 161.161.252.20 IP is private and cannot be reached from the cloud and vice versa . How do I get kamailio to be the middle man between 161.161.252.20 and RTP server(all traffic must go via the kamailio server) Is there specific modules I must load. Im running Kamailio 4.4 Any help would be muchly appreciated. Regards Pieter

2 3

Important: new module exports interface
by Daniel-Constantin Mierla 28 Sep '18

28 Sep '18

Hello, as a result of collaborative work at Kamailio Developers Meeting, we succeeded to merge the two existing module exports interface (one for kamailio modules and the other one from ser modules) in a single one. All public modules were updated, but if you have any private module then you have to update as well in order to get it compiled with the latest master. Just look at one of the modules (e.g., sl is a good option) and all the fields in mod exports structure have comments with their meaning. In short: we removed unused fields for statistics, mi commands and extra-processes (from kamailio old interface) and oncancel (from ser old interface), kept the rpc exports from ser interface and pv exports and dlopen flags from kamailio interface. The other fields were common in both interfaces, but be aware that order was also changed. If you have a module implementing the old ser interface, you also need to add the free_fixup_field in functions exports tructure -- you can just set it to 0. With this we have now a single mod exports interface in all modules, the core is also cleaner as we got rid of the various compatibility layers. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com

1 0

INFO: maintenance work on deb.kamailio.org
by Daniel-Constantin Mierla 28 Sep '18

28 Sep '18

Hello, we will do some maintenance work on deb.kamailio.org server these days in order to move to a better infrastructure, so it may not be available for a while -- the DNS needs to be updated as well, this also can affect you if your router/provider does caching. Once we finish with the migration, we will send updates. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com

1 1

Re: [SR-Users] No dispatcher failover
by Gertjan Wolzak 28 Sep '18

28 Sep '18

Alex, Thank you for the feedback, just the info I needed. Failover is working now just as it should. Now I just have to tweak the failover timing. Rgds, Gertjan Wolzak

1 0

Cannot handle Cancel Request properly
by Aqs Younas 28 Sep '18

28 Sep '18

Greetings list, I am getting hard time to make kamailio perfectly handle cancels request. I am using http_async_client and MSILO to handle push notifications. Case 1. When B party record exists in location but it is off-line and I send cancel *instantly* from Party A while kamailio is sending push to wake B Party up. modparam("tm", "failure_reply_mode", 3) modparam("tm", "cancel_b_method", 1) modparam("tm", "fr_timer", 30000) modparam("tm", "fr_inv_timer", 120000) You can see in below picture 407 being generated after some time. [image: default.PNG] What could be the reason of this problem? any pointer is much appreciated. Br, Aqs.

2 1

replay of tls delayed by 30 secs.
by Andrew Chen 28 Sep '18

28 Sep '18

Hi Kam community, Facing an urgent issue here and not sure how to troubleshoot it further. So our engineers been getting reports of unknown SIP timeouts and they suspect it's something on the Kamailio side. I've logged every transaction from receiving the message to done relaying it as shown below: Sep 24 18:38:13 sjoprodfnsg01 /usr/local/sbin/kamailio[42608]: INFO: <script>: [1589Fz-ses1-41d9a88aR70125425(a)xxx.xxx.xxx.xxx][4534123][CSeq 7] NG-FuzeMedia-Server/42ae58c/mediahub Relaying [UPDATE] from (xxx.xxx.xxx.xxx ) to ( xxx.xxx.xxx.xxx ) via (tls) Sep 24 18:38:13 sjoprodfnsg01 /usr/local/sbin/kamailio[42608]: INFO: <script>: [1589Fz-ses1-41d9a88aR70125425@ xxx.xxx.xxx.xxx ][4534123][CSeq 7] NG-FuzeMedia-Server/42ae58c/mediahub Done relay [UPDATE] from (xxx.xxx.xxx.xxx ) to ( xxx.xxx.xxx.xxx ) via (tls) When I pulled the 443 SIP trace from my tcpdump session, it shows the application data left the machine at 18:44 as shown here: [image: image.png] Note: This packet is encrypted and can't see the actual SIP message. This matches what was received on the client logs: 2018-09-24T18:38:44.032Z [40927] [INF] fuze.sip SipParser.cpp:549 LogSipMessage: xxx.xxx.xxx.xxx:443 - 4292B (local time 09/24 11:38:44) -------------------- RECEIVE: UPDATE sips:Luke_Surazski@ xxx.xxx.xxx.xxx:50795;id=37262838;inst=52241254 SIP/2.0 Via: SIP/2.0/TLS xxx.xxx.xxx.xxx:443;branch=z9hG4bK15f.5052c318e1766a0a9405f10708f43188.0;i=acbb7 Via: SIP/2.0/TCP xxx.xxx.xxx.xxx :38342;rport=38342;branch=z9hG4bK-55f913-t9-I214262897 What would cause such delays? I'm running Kamailio 4.1.5 Thanks. -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) achen@ <achen(a)thinkingphones.com>fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.*

2 9

subst_hf to rewrite a contact header
by Ben Hood 27 Sep '18

27 Sep '18

Hi, I’m wondering how to use subst_hf() properly. I’m trying to debug a broken flow by manually rewriting the contact header from Contact: <sip:b73c6f29-0101-4802-afcd-efb63f1e6d8f@10.10.10.12:5090;transport=udp> to Contact: <sip:2018092417381900003@81.x.x.x> by using $var(ctct) = "<sip:2018092417381900003@81.x.x.x>"; subst_hf("Contact", “/\<.+\>/$var(ctct)\r\n/", "a”); but the result is Contact: <sip:2018092417381900003@81.x.x.x> sip:b73c6f29-0101-4802-afcd-efb63f1e6d8f@10.10.10.12:5090;transport=udp Testing the regex with an external tool appears to match all of the original header, so I’m wondering why subst_hf doesn’t appear to rewrite the entire header. Is there something I’m doing wrong? TIA, Ben

3 7

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