sr-users January 2018

sr-users@lists.kamailio.org

83 participants
123 discussions

Re: [SR-Users] How to determine correct port to set in record-route header
by Pranathi Venkatayogi 30 Mar '18

30 Mar '18

Any help? From: Pranathi Venkatayogi Sent: Monday, January 23, 2017 2:35 PM To: 'Kamailio (SER) - Users Mailing List' <sr-users(a)lists.sip-router.org> Subject: How to determine correct port to set in record-route header Hi, I am using Kamailio behind NAT, unable to figure how to make it put “public ip” in Record-route header, I am manually inserting the hard-coded header myself as below. However now I am having trouble choosing the right port number in all scenarios. $var(dstPort) = 5061; if (dst_port==5060) { $var(dstPort) = 5060; } insert_hf("Record-Route: <sip:MY_PUBLICIP_ADDR:$var(dstPort);transport=tls;lr;nat=yes>\r\n", "Record-Route"); In one scenario I see the conflicting port numbers in “via” header vs “Record route”. The ACK is being set to port 5060 based on Record route header and is not being received by the callee. 2017-01-23 14:52:49.970233 [blink.exe 2780]: SENDING: Packet 11, +0:00:36.411867 10.0.27.108:58217 -(SIP over TLS)-> 172.31.211.31:5061 SIP/2.0 180 Ringing Via: SIP/2.0/TLS 63.149.103.72:5061;received=172.31.211.31;branch=z9hG4bK4799.7067bd2a48063748a4c353fa408eaefa.0 Via: SIP/2.0/UDP 10.0.16.52;rport=5060;branch=z9hG4bK4799.935a27c6ef5ad112225964cbe7c1be44.0;i=2 Via: SIP/2.0/TLS 10.11.200.12:51793;rport=51793;received=10.11.200.12;branch=z9hG4bKPj49f6aeca3f9b4155ab4c5304b544aa4d;alias Record-Route: <sip:63.149.103.72:5060;transport=tls;lr;nat=yes> Record-Route: <sip:10.0.16.52:5061;transport=tls;lr;nat=yes> Call-ID: 09ce10efa6a946bf9445ccc21857393e From: "cust1" <sip:cust1@devtranslation.sms-test.cyracom.com>;tag=95082caabecc42548c2fec5ccd29e5de To: <sip:spanish@translation.sms-test.cyracom.com>;tag=ec365cc8489b48a7bc5725d21b7d97a1 CSeq: 17422 INVITE Server: Blink 3.0.0 (Windows) Contact: <sip:20745891@10.0.27.108:58216;transport=tls> Allow: SUBSCRIBE, NOTIFY, PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, MESSAGE, REFER Content-Length: 0 Questions: 1. How can I let in-built record-route function automatically choose “public ip” so I can get rid of my manual insertion altogether. 2. If no option, what is the right way to choose the port on which packet is being received, so it is same as what is on “VIA”. 3. Any other pointers to improve the logic here?

3 3

authenticating to mongodb fails
by hdssdsdsdsfsdf hdssdsdsdsfsdf 21 Mar '18

21 Mar '18

When I connect using mongo, the credentials work: $ mongo kamailio -u "kam" -p "kam" MongoDB shell version v3.4.9 connecting to: mongodb://127.0.0.1:27017/kamailio MongoDB server version: 3.4.9 > db.subscriber.find() { "_id" : ObjectI ... But when I use the following DBURL in kamailio.cfg, kamailio fails to even login to mongo: #!define DBURL "mongodb://kam:kam@localhost/kamailio" If I disable mongodb authentication, kamailio starts up just fine again. Any idea what's going wrong here?

3 10

Need useful graphics ideas
by Karsten Horsmann 16 Mar '18

16 Mar '18

Hello List, I thought about some kind of Kamailio stats source (like registered users, calls active and some other things) to collect them into influx dB and draw them with grafana. How do you solved that? Timer based routes or statsd or whatever? Kind regards Karsten Horsmann

5 10

is_audio_on_hold() doesn't support rfc3264
by Julia Boudniatsky 13 Feb '18

13 Feb '18

FYI, After some tests found, that function "*is_audio_on_hold()*" (textops) *supports only rfc 254*3, where "hold" is indicated by setting the "c" destination addresses for the media streams to zero (0.0.0.0). The newest *rfc3264*, where "hold" is indicated by a=sendonly/inactive, *is not supported*. Kamailio version 4.4.6. Best regards, Julia

4 8

dmq_usrloc - which server?
by Alex Balashov 07 Feb '18

07 Feb '18

Hi, The Socket parameter of location entries is not replicated under dmq_usrloc. To make matters worse, the technical characteristics of the registrar module are such that I cannot straightforwardly modify the incoming Contact to add a rider indicating the server on which the register was received. The AoR domain is the same for all registrations received on any server in the DMQ mesh. To reach the registrants, I need to forward the registration to the correct server that corresponds to the true provenance of the registration. What is a reasonable way of finding out what that is? I don't see any method of injecting such values into the replicated contacts, as dmq_usrloc does not provide hooks for this. Thanks, -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

3 19

Issue with Socket selection on Forwarding ACK message
by Thomas Carvello 06 Feb '18

06 Feb '18

Hello, i have an issue with my Kamailio 4.1.9 configuration. This configuration is multi-homed, we have*two network* interfaces, one on a private network and on the public Internet. Kamailio is configured to listen on port 5060 and 5066 on both interfaces. We register two users Alice and Bob on the public Internet using port 5066. Both users are behind a NAT and we capture the SIP exchange on the proxy server. We have set the parameter mhomed=1 When Alice calls Bob, we have Alice Proxy Bob src=5063 dst=5066 INVITE ------------------> src=5066 ------ INVITE ---------------> dst=5060 dst=5066 <------- 200 OK -------------- src=5060 dst=5063 <------- 200 OK --------- src=5066 src=5063 dst=5066 -------- ACK -----------> *src=5060 (blocked by NAT)* ------ ACK-----x dst=5060 The ACK packet gets relayed with the wrong source port. Then the NAT rejects the packet and the call cannot be established. For some reason, when Bob calls Alice, the call is correctly established. Could it be because Bob happend to use 5060 as local port? Also, if we set nhomed=0 it works BUT we are not sure that multi homed is handled correctly. I was wondering if you have encounter this issue before? I have investigated the code for selection socket and what is the logic of this selection ? /*How does kamailo knows that it should choose 5066 as src port if the user is registered using port 5066 instead of 5066?* / Thank you for your time. Thomas

4 8

Fosdem dinner
by Daniel-Constantin Mierla 03 Feb '18

03 Feb '18

Hello, in the past 10 years or so, many of us met at Fosdem conference in Brussels (the edition this year happens during February 3-4) and had a dinner on Saturday evening. I know already couple of people from community that will go there, so the question is if there is any interest to organize again such event. If yes, it will be again on Saturday, on the evening of the 3rd of February. At the past editions, it turned into an all-RTC dinner, but we can consider to have it alone again (eventually with few other invited friends), if there are too many or people want a smaller meeting. Reply this week if you want to join, so we can estimate how many seats we need and have enough time to find a place that can accommodate us. More about Fosdem can be found at: - https://fosdem.org There is a devroom on Sunday with topics covering real time communications. I will have a presentation there. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

10 13

Case insensitive regexp in textops::search() function
by Andrey Deykunov 01 Feb '18

01 Feb '18

Hi, I have an htable containing some black list words (i.e. user IDs or phone models). To find matches of the words in every message I use the following script: sht_iterator_start("i1", "black_list"); while(sht_iterator_next("i1")) { if ( search($shtitval(i1)) ) { // do something } } sht_iterator_end("i1"); How can I modify search($shtitval(i1)) to get case insensitive matching? The example below does not work: sht_iterator_start("i1", "black_list"); while(sht_iterator_next("i1")) { $var(re) = $shtitval(i1) + "/i"; if ( search($var(re)) ) { // do something } } sht_iterator_end("i1"); Other possible modifications of $var(re) aren't working too. Thanks, Andrey

2 2

Partial/regex match on hash table key?
by Anthony Joseph Messina 31 Jan '18

31 Jan '18

Is is possible (without iterating through all entries in a hash table) to return the value based on a partial or regex match to the key? Something like... $var(one)=$sht(a=>*$var(two)) -- Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery F9B6 560E 68EA 037D 8C3D D1C9 FF31 3BDB D9D8 99B6

2 2

question about force_send_socket
by Fabian Borot 31 Jan '18

31 Jan '18

our kamailo has 2 IPs, a public (87.x.x.x) and a private (192.168.1.1). It is listening on all of them. For all calls it listens on the public IP but for some calls I need to forward the incoming INVITE to a server in the private network so I do a " force_send_socket(privateip:port)" before the route that forwards the INVITE to the server in the private network and that works. But then when the server in the private network replies with 302 I have to contact the servers inside the Contact header using the Public IP now so I do this hoping that it will switch back to the public IP: if (t_check_status("302")) { force_send_socket(PUBLIC_IP:5060); get_redirects("*"); t_relay(); } But it stays in the private, so the INVITEs to the servers inside the Contact header are sent from the Private IP and they are blocked. This would be the flow: customer INVITE -> kamailio(publicIP) kamailio (publicIP) 100 trying -> customer kamailio(privateIP) INVITE -> Server(privateIP) Server(privateIP) 302 redirect -> kamailio(privateIP) kamailio(privateIP) ACK -> Server(privateIP) after I would like this to happen kamailio(publicIP) INVITE -> Server1(publicIP) but instead this happens: kamailio(privateIP) INVITE -> Server1(publicIP) how can I switch back to the public IP to continue with this call flow? thank you

2 2

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 January 2018