sr-users February 2018

sr-users@lists.kamailio.org

90 participants
112 discussions

Kamailio Behind TCP Load Balancer
by Colin Morelli 04 Jun '18

04 Jun '18

Hey all, I'm looking to put Kamailio behind a TCP load balancer that is SIP-unaware. My application is deployed in AWS and I'm tying to place Kamailio behind an ELB. For the most part, everything is fine. For my specific implementation I'm disabling UDP as a signaling transport and using only TLS. This enables me to not have to worry about a SIP-aware LB at the edge because replies to an incoming request will be sent over the existing established TCP socket (avoiding any crazy routing requirements). However - this poses an issue with source addresses. Does Kamailio support anything like the proxy protocol ( http://www.haproxy.org/download/1.5/doc/proxy-protocol.txt) for getting TCP stream information from a load balancer? Do I need to go back to exposing it directly to the world so that I can get source addresses? Thanks, Colin

3 4

Kamailio Websocket Questions
by Nagorny, Dimitry 17 Apr '18

17 Apr '18

Hi List, two questions regarding Kamailio Websockets: 1. How do I send INVITE request TO the listening Websocket? I usually used for UDP/TCP/TLS these format, but somehow this is not working for Websocket because it gets in an endless loop: if ($rU=~"^(\+|00|0)?[1-9][0-9]{4,20}$") { $ru = "sip:" + $rU + "@" + $sel(cfg_get.pstn.gw_ip) + ";user=phone;transport=udp"; force_send_socket(udp:MY_EXTERN_IP:MY_EXTERN_PORT); rtpengine_offer("internal trust-address RTP AVP"); route(RELAY); exit; } 2. Why do I get these errors every time my Websocket Client is registering, but it still works and DB is inserted with registered location: ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 22) ERROR: <core> [parser/msg_parser.c:690]: parse_msg(): ERROR: parse_msg: message=<HTTP/1.1 101 Switching Protocols#015#012Sia: SIP/2.0/TCP 10.250.5.17:51283#015#012Sec-WebSocket-Protocol: sip#015#012Upgrade: websocket#015#012Connection: upgrade#015#012Sec-WebSocket-Accept: 6uLXlD/aBrzu/j3PYP3DWO7rvLE=#015#012Server: kamailio (4.3.5 (x86_64/linux))#015#012Content-Length: 0#015#012#015#012> I am using Kamailio 4.3.5 + CentOS 7.2. I appreciate every help I can get. Best Regards Dimitry Nagorny Trainee

3 4

RTPengine - Transcoding example available?
by Carsten Bock 10 Apr '18

10 Apr '18

Hi, Quick (and simple) question: Can someone provide a working RTPengine request, to enable Transcoding? I know, this is possible, but I thought before looking into deep, how this should be configured for the rtpengine_offer() command, could someone provide an example? Thanks, Carsten

6 13

topos redis -> failed to store
by Abdoul Osséni 02 Apr '18

02 Apr '18

Hello list, I activated topos and topos_redis backend. Now, I have the following errors: Jan 6 07:34:11 sd-110402 /usr/local/sbin/kamailio[30288]: {1 102 NOTIFY 645f4b58537f9df53b9ce65f4937d652@163.172.83.169:5064} ERROR: topos [tps_storage.c:394]: tps_storage_record(): failed to store Jan 6 07:34:11 sd-110402 /usr/local/sbin/kamailio[30292]: {1 102 NOTIFY 5b678085378e62c12c6f18154501feb3@163.172.83.169:5064} INFO: topos_redis [topos_redis_storage.c:163]: tps_redis_insert_dialog(): no uuid for this message Jan 6 07:34:11 sd-110402 /usr/local/sbin/kamailio[30292]: {1 102 NOTIFY 5b678085378e62c12c6f18154501feb3@163.172.83.169:5064} ERROR: topos [tps_storage.c:394]: tps_storage_record(): failed to store Jan 6 07:34:18 sd-110402 /usr/local/sbin/kamailio[30287]: {1 102 NOTIFY 2799d4a61e9defbc66dc67735e1c6e6c@163.172.83.169:5064} INFO: topos_redis [topos_redis_storage.c:163]: tps_redis_insert_dialog(): no uuid for this message Jan 6 07:34:18 sd-110402 /usr/local/sbin/kamailio[30287]: {1 102 NOTIFY 2799d4a61e9defbc66dc67735e1c6e6c@163.172.83.169:5064} ERROR: topos [tps_storage.c:394]: tps_storage_record(): failed to store Jan 6 07:34:18 sd-110402 /usr/local/sbin/kamailio[30290]: {1 102 NOTIFY 760fe2ce3427748514441de25cade2e4@163.172.83.169:5064} INFO: topos_redis [topos_redis_storage.c:163]: tps_redis_insert_dialog(): no uuid for this message Jan 6 07:34:18 sd-110402 /usr/local/sbin/kamailio[30290]: {1 102 NOTIFY 760fe2ce3427748514441de25cade2e4@163.172.83.169:5064} ERROR: topos [tps_storage.c:394]: tps_storage_record(): failed to store Jan 6 07:34:33 sd-110402 /usr/local/sbin/kamailio[30291]: {1 102 NOTIFY 7464fc2b503427423b0aba925fb13bc7@163.172.83.169:5064} INFO: topos_redis [topos_redis_storage.c:163]: tps_redis_insert_dialog(): no uuid for this message Jan 6 07:34:33 sd-110402 /usr/local/sbin/kamailio[30291]: {1 102 NOTIFY 7464fc2b503427423b0aba925fb13bc7@163.172.83.169:5064} ERROR: topos [tps_storage.c:394]: tps_storage_record(): failed to store Jan 6 07:34:35 sd-110402 /usr/local/sbin/kamailio[30287]: {1 102 NOTIFY 581e88181527f4221fbc7f893a564d6a@163.172.83.169:5064} INFO: topos_redis [topos_redis_storage.c:163]: tps_redis_insert_dialog(): no uuid for this message Jan 6 07:34:35 sd-110402 /usr/local/sbin/kamailio[30287]: {1 102 NOTIFY 581e88181527f4221fbc7f893a564d6a@163.172.83.169:5064} ERROR: topos [tps_storage.c:394]: tps_storage_record(): failed to store Could you help me to fix it? Abdoul OSSENI

3 8

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

Dimensioning ds_hash_size value for dispatcher module
by Alvaro Araos 14 Mar '18

14 Mar '18

Hi, In the documentation of the dispatcher module it is said that in order to use the algorithm 10 (load balancing) the parameter ds_hash_size must be set, in the definition it is said that the value is in powers of 2, that is to say if it is set to 8, this is equal to 2 ^ 8 = 256 slots, but still I do not understand how to dimension this value for my needs. I do not know whether to put 8, 4, 9, etc. Saludos, ALVARO ARAOS MÉNDEZ Director de Tecnología en FONOIP +56 2 2947 9000 alvaro(a)fonoip.com | www.fonoip.com [1] Moisés Chacón 46, El Monte, RM Links: ------ [1] http://www.fonoip.com

2 2

kamailio Rx_AAR qusetions
by Lv, Victor (NSB - CN/Qingdao) 14 Mar '18

14 Mar '18

Hi All, I am trying to send two Rx_AAR after Kamailio receive 200 OK with SDP: The first one for termination part is worked well, but in MT_aar_reply route block, it's not works. The one I marked with red color, is there anyone know how configure Kamailio to send two Rx_AAR after receive 200 OK SDP? Thanks a lot!! Victor +++++++++++++++++++++++++++++++++++++++++++++++++++++++ if (t_check_status("200")){ xlog("L_DBG", "IMS: Received 200 nside orig_initial_reply\n"); $var(aarret) = Rx_AAR("MT_aar_reply", "term","",2); xlog("L_DBG", "AAR return code is $var(aarret)\n"); } on MT_aar_reply block: route[MT_aar_reply] { #this is async so to know status we have to check the reply avp switch ($avp(s:aar_return_code)) { case 1: xlog("L_DBG", "Diameter: Term AAR success on media authorization\n"); break; default: xlog("L_ERR", "IMS: AAR failed Term\n"); xlog("L_ERR", "IMS: ttag: "+ "$avp(TTAG_CUSTOM_AVP)"); xlog("L_ERR", "IMS: ftag: "+ "$avp(FTAG_CUSTOM_AVP)"); xlog("L_ERR", "IMS: callid: "+ "$avp(CALLID_CUSTOM_AVP)"); #comment this if you want to allow even if Rx fails if(dlg_get("$avp(CALLID_CUSTOM_AVP)","$avp(FTAG_CUSTOM_AVP)","$avp(TTAG_CUSTOM_AVP)")){ dlg_terminate("all", "Sorry no QoS available"); exit; } $var(aarret) = Rx_AAR("MO_aar_reply", "term","",2); xlog("L_DBG", "AAR return code is $var(aarret)\n");

4 8

kamailio does not start with db_mongdb and usrloc
by Stephane Focant 13 Mar '18

13 Mar '18

Hello, I have an issue when I try to use kamailio 5.1 with usrloc and db_mongdb modules. When I try to start kamailio, I get the following error: 0(22216) DEBUG: <core> [db.c:314]: db_do_init2(): connection 0x7f735b5c4100 not found in pool 0(22216) DEBUG: db_mongodb [mongodb_connection.c:55]: db_mongodb_new_connection(): connection open to: mongodb://10.0.12.149 ,10.0.12.150, 10.0.12.151/kamailio?replicaSet=sre_location&slaveOk=true&readPreference=primaryPreferred 0(22216) DEBUG: db_mongodb [mongodb_dbase.c:864]: db_mongodb_query(): query to collection [version] 0(22216) DEBUG: db_mongodb [mongodb_dbase.c:898]: db_mongodb_query(): query filter: { "table_name" : "location" } 0(22216) DEBUG: db_mongodb [mongodb_dbase.c:917]: db_mongodb_query(): columns filter: { "table_version" : 1 } 0(22216) DEBUG: <core> [db_res.c:120]: db_new_result(): allocate 56 bytes for result set at 0x7f735b5c4450 0(22216) DEBUG: db_mongodb [mongodb_dbase.c:746]: db_mongodb_store_result(): no result from mongodb 0(22216) DEBUG: <core> [db.c:404]: db_table_version(): no row for table location found 0(22216) ERROR: <core> [db.c:450]: db_check_table_version(): invalid version 0 for table location found, expected 9 (check table structure and table "version") 0(22216) ERROR: usrloc [dlist.c:659]: register_udomain(): error during table version check. 0(22216) DEBUG: <core> [db_pool.c:100]: pool_remove(): removing connection from the pool 0(22216) ERROR: registrar [registrar.c:651]: domain_fixup(): failed to register domain 0(22216) ERROR: <core> [core/route.c:1154]: fix_actions(): fixing failed (code=-1) at cfg:/usr/local/kamailio-5.1/etc/kamailio/kamailio.cfg:660 0(22216) ERROR: <core> [core/rvalue.c:3860]: fix_rval_expr(): failure in cfg at line: 660 col: 22 0(22216) ERROR: <core> [core/rvalue.c:3860]: fix_rval_expr(): failure in cfg at line: 660 col: 22 0(22216) ERROR: <core> [core/route.c:1154]: fix_actions(): fixing failed (code=-1) at cfg:/usr/local/kamailio-5.1/etc/kamailio/kamailio.cfg:663 ERROR: error -1 while trying to fix configuration 0(22216) DEBUG: tm [t_funcs.c:85]: tm_shutdown(): start 0(22216) DEBUG: tm [t_funcs.c:88]: tm_shutdown(): emptying hash table 0(22216) DEBUG: tm [t_funcs.c:90]: tm_shutdown(): removing semaphores 0(22216) DEBUG: tm [t_funcs.c:92]: tm_shutdown(): destroying tmcb lists 0(22216) DEBUG: tm [t_funcs.c:95]: tm_shutdown(): done 0(22216) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized 0(22216) DEBUG: <core> [core/mem/shm.c:261]: shm_destroy_manager(): destroying memory manager: q_malloc 0(22216) DEBUG: <core> [core/mem/q_malloc.c:1165]: qm_shm_lock_destroy(): destroying the shared memory lock 0(22216) DEBUG: <core> [core/mem/pkg.c:91]: pkg_destroy_manager(): destroying memory manager: q_malloc In mongoDB, I have the collection "version" in the db kamailio, and the entries needed for usrloc (location and location_attrs): sre_location:PRIMARY> use kamailio switched to db kamailio sre_location:PRIMARY> db.getCollection("version").find() { "_id" : ObjectId("5a8ec43c601b262bef82a595"), "table_name" : "location", "table_version" : 9 } { "_id" : ObjectId("5a8edb72a3ec40427577b8d0"), "table_name" : "location_attrs", "table_version" : 1 } And logs in mongo show the following info when kamailio starts: 2018-02-22T17:13:02.604+0100 I NETWORK [conn90] received client metadata from 10.0.12.180:56320 conn: { driver: { name: "mongoc", version: "1.9.2" }, os: { type: "Linux", name: "CentOS", version: "6.9 (Final)", architecture: "x86_64" }, platform: "cfg=0x1563000 posix=200809 CC=GCC 4.4.7 20120313 (Red Hat 4.4.7-18) CFLAGS="" LDFLAGS=""" } 2018-02-22T17:13:02.604+0100 I COMMAND [conn90] command admin.$cmd command: isMaster { isMaster: 1, client: { driver: { name: "mongoc", version: "1.9.2" }, os: { type: "Linux", name: "CentOS", version: "6.9 (Final)", architecture: "x86_64" }, platform: "cfg=0x1563000 posix=200809 CC=GCC 4.4.7 20120313 (Red Hat 4.4.7-18) CFLAGS="" LDFLAGS=""" }, compression: [], $readPreference: { mode: "secondaryPreferred" }, $db: "admin" } numYields:0 reslen:716 locks:{} protocol:op_query 0ms 2018-02-22T17:13:02.604+0100 I COMMAND [conn90] command kamailio.$cmd command: find { find: "version", filter: { table_name: "location" }, table_version: 1, $db: "kamailio", $readPreference: { mode: "primaryPreferred" }, $clusterTime: { clusterTime: Timestamp(1519315979, 1), signature: { hash: BinData(0, 0000000000000000000000000000000000000000), keyId: 0 } } } numYields:0 reslen:531 locks:{} protocol:op_msg 0ms 2018-02-22T17:13:02.605+0100 I NETWORK [conn90] end connection 10.0.12.180:56320 (9 connections now open) I probably miss something: it is not clear to me why kamailio is not able to retrieve the value of table_version for the table_name location. Any idea would be very welcome ! I use mongo-c-driver 1.9.2 and mongodb 3.6 Thank you. Stephane

3 14

2026

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