sr-users

sr-users@lists.kamailio.org

28 participants
37537 discussions

kamailio implamentation
by kossivi HOLONOU 14 Mar '18

14 Mar '18

Hello, I am developing a project on MSRP Kamailio with webRTC client for my end of training project, can you help me with documentation or configuration side kamailio and webRTC client to implement to get there? Thank you for your support BesT Regards,Kossivi HolonouBO VAS EngineerDakar-Sénégal

1 0

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(… [View More]

2 2

Kamailio With SMPP
by Amar Tinawi 14 Mar '18

14 Mar '18

Hello Is there a method to integrate kamailio to an smpp smsc ? Thanks

2 1

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"); … [View More]

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) … [View More]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 [View Less]

3 14

permissions.allow in conjunction with trusted table
by Ben Hood 12 Mar '18

12 Mar '18

Hi, I'd like to trust HTTP requests from internal subnets and use the trusted table to manage permissions from external networks. Is there a way to configure permissions.allow to trust everything on a local subnet and use the DB table for everything else? Does the permissions module even work in that way (i.e. to use two sources of trust)? If so, what is the permissions.allow syntax to trust a CIDR? Or is it better to split the trust up based on listening ports (i.e. define the route blocks … [View More]

2 2

Tracking NAT Helper keepalives
by Mark Boyce 12 Mar '18

12 Mar '18

Hi All Is there any way to extract round trip lime state from keepalives? I have a customer who’d like to duplicate the qualify feature of Asterisk. ie latency / distance of endpoint from server. Can’t see any way to hook in from the docs. Thanks Mark

2 1

SBC rejects SIP INVITE from Kamailio+topos
by José Lopes 12 Mar '18

12 Mar '18

Hello, I am using Kamailio working as edge proxy with topos module active. Kamailio is proxing requests from Freeswitch's to the SBC Metaswitch. The Freeswitch sends SIP REGISTER requests and it is ok (Contact: < sip:1003@172.29.210.164:5070>). When Freeswitch sends SIP INVITE quest, it receives a reply with Forbiden (Contact: <sip:btpsh-5aa0219a-2a32-2@172.29.210.164:5070>). You can check the sip trace at https://pastebin.com/raw/JZUNgYx5 I analysed this issue on SBC … [View More]

2 1

Dialog Terminator
by Leonardo Assunção 12 Mar '18

12 Mar '18

Greetings, Does Kamailio has a method or variable that indicates who cancelled,rejected or terminated a call and, therefore ended the dialog? Currently i'm looking for the sources of BYE's, CANCEL and replies greater than 300 to first INVITE, but i would safer if such a method existed. Thanks in advance

2 1

Presence not notifying?
by Mark Boyce 11 Mar '18

11 Mar '18

Hi All Got a presence problem with what should be a very simple config. Would much appreciate someone having a look at the following and seeing if I’ve missed something obvious :-) Thanks Mark I’ve gone right back to basics and using the example at http://kb.asipto.com/kamailio:presence:k43-blf <http://kb.asipto.com/kamailio:presence:k43-blf> Changes to that example are; - Kamailio 5.1.2 - RTPEngine - NAT Enabled - JSON RPC replacing mi_rpc - HA1 Passwords Setup is; Three … [View More]phone 20,21,22 all on site behind a NAT (10.1.3.x local IP) at 1.2.3.4 External IP. Phone 21 has BLF Subscriptions on 20 and 22 Domain is set as “mykamailio.com” Kamailio is an Ubuntu server “In the cloud” on 5.6.7.8 (Assuming I have got my domain & ip rewrites correct on the cut’n’paste) What’s Happening; All three phones register 21 Issues SUBSCRIBE:Dialog for 20 and 22. Which get 202 Accepted back after a 407 Proxy Auth SUBSCRIBE sip:22@mykamailio.com:5060 SIP/2.0 Via: SIP/2.0/UDP 10.1.3.84:5065;rport;branch=z9hG4bK3894730624 From: "21@SBC-2" <sip:21@mykamailio.com>;tag=1678729960 To: <sip:22@mykamailio.com> Call-ID: 1544456221(a)10.1.3.84 CSeq: 1 SUBSCRIBE Contact: <sip:21@10.1.3.84:5065> Accept: application/dialog-info+xml Max-Forwards: 70 User-Agent: Yealink SIP-T26P 6.73.0.50 Expires: 1800 Event: dialog Content-Length: 0 I can see these arrive in active_watchers table; *************************** 2. row *************************** id: 2 presentity_uri: sip:20@mykamailio.com watcher_username: 21 watcher_domain: mykamailio.com to_user: 20 to_domain: mykamailio.com event: dialog event_id: to_tag: a6c744f901d779619c580c9ef48ab5e9-2651 from_tag: 1809677495 callid: 2674059037(a)10.1.3.84 local_cseq: 0 remote_cseq: 2 contact: sip:21@10.1.3.84:5065;alias=1.2.3.4~5065~1 record_route: expires: 1520711354 status: 1 reason: version: 0 socket_info: udp:5.6.7.8:5060 local_contact: sip:5.6.7.8:5060 from_user: 21 from_domain: mykamailio.com updated: -1 updated_winfo: -1 flags: 0 user_agent: Yealink SIP-T26P 6.73.0.50 If I make a call from 20 to 22 it works as expected but no notify is sent. For completeness the changes I’ve made to the kamailio.cfg file are; # diff kamailio.cfg_presence_example kamailio.cfg 6a7 > #!define WITH_NAT 119c120 < #!define DBURL "mysql://kamailio:kamailiorw@localhost/kamailio" --- > #!define DBURL "mysql://kamailiorw:password@localhost/test_kamailio" 169a171 > alias="mykamailio.com" 221c223 < mpath="/usr/local/lib/kamailio/modules/" --- > mpath="/usr/lib/x86_64-linux-gnu/kamailio/modules/" 228c230 < loadmodule "mi_fifo.so" --- > loadmodule "jsonrpcs.so" 245d246 < loadmodule "mi_rpc.so" 279c280 < loadmodule "rtpproxy.so" --- > loadmodule "rtpengine.so" 304,307d304 < # ----- mi_fifo params ----- < modparam("mi_fifo", "fifo_name", "/tmp/kamailio_fifo") < < 375,376c372,374 < modparam("auth_db", "calculate_ha1", yes) < modparam("auth_db", "password_column", "password") --- > modparam("auth_db", "calculate_ha1", no) > modparam("auth_db", "password_column", "ha1") > modparam("auth_db", "password_column_2", "ha1b") 414c412 < modparam("presence", "server_address", "sip:192.168.178.54:5060" ) --- > modparam("presence", "server_address”, "sip:5.6.7.8:5060") 454c452 < modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:7722") --- > modparam("rtpengine", "rtpengine_sock", "udp:127.0.0.1:2223") 835c833 < rtpproxy_manage("co"); --- > rtpengine_manage("co”); [View Less]

2 5

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