sr-users November 2018

sr-users@lists.kamailio.org

68 participants
89 discussions

Phone does not set "Expire-header" but "Contact expire", immediately expires
by Kevin Olbrich 07 Nov '18

07 Nov '18

Hi! I have a phone (Mitel 6930) that does not send an Expire-header but "expire" in Contact during REGISTER: Session Initiation Protocol (REGISTER) > Request-Line: REGISTER sip:pbx.example.com SIP/2.0 > Message Header > Via: SIP/2.0/TLS 192.168.6.16:5061;branch=xxxxxxxxxxxxxxxx;rport > Route: <sip:pbx.example.com;lr=lr;transport=tls> > Max-Forwards: 70 > From: "Example" <sip:121212_6666@pbx.example.com>;tag=b0cec92c3e > To: "Example" <sip:121212_6666@pbx.example.com> > Call-ID: aaaaaaaaaaaaaaaaa > CSeq: 1190442896 REGISTER > Accept-Language: de > Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, UPDATE, > PRACK, SUBSCRIBE, INFO, PUBLISH > Allow-Events: talk, hold, conference, LocalModeStatus > Contact: "Example" <sip:121212_6666@192.0.2.1:62336 > >;+sip.instance="<urn:uuid:00000000-0000-1000-8000-08000FB888F5>";expires=300 > Supported: path, gruu > User-Agent: Mitel 6930/5.0.0.2041 > Aastra-Line: 1 > Aastra-Mac: AAAAAAAAAAAA > Content-Length: 0 This results in successful register, kamailio forwards REGISTER to asterisk (endpoint registered) and immediatly kamailio sends a new REGISTER with Expire set to 0 to asterisk: Session Initiation Protocol (REGISTER) > Request-Line: REGISTER sip:192.168.99.112:5060 SIP/2.0 > Message Header > Via: SIP/2.0/UDP 192.168.99.111:5060 > ;branch=z9hG4bK9f9e.599cf243000000000000000000000000.0 > To: <sip:121212_6666@192.168.99.112> > From: <sip:121212_6666@192.168.99.112 > >;tag=7e4f6993bfbf831f6b016fea6683cdca-b98a > CSeq: 10 REGISTER > Call-ID: 2bc5fd1061b31723-1350(a)192.168.99.111 > Max-Forwards: 70 > Content-Length: 0 > User-Agent: kamailio (5.1.6 (x86_64/linux)) > Contact: <sip:121212_6666@192.168.99.111:5060> > Expires: 0 The phone is then unregistered - the phone also shows "no service". It looks like Kamailio generates this message on it's own (and I don't know why). I am still learning to implement kamailio as proxy. Reading the docs, I would expect Kamailio to automatically eval the correct parameter: > If the processed message contains neither Expires HFs nor expires contact > parameters, this value will be used for newly created usrloc records. [1] What did I miss? Phones which use the Expire-header are working fine. Kind regards Kevin [1] default_expires - http://www.kamailio.org/docs/modules/5.2.x/modules/registrar.html

3 10

busy lamp field
by Kevin Olbrich 06 Nov '18

06 Nov '18

Hi! Can someone share his kamailio.cfg with working busy lamp field in a kamailio-as-proxy scenario? My config is based on the example shipped with 5.1.x and asterisk as the backend. Calling works fine but PUBLISH / SUBSCRIBE is handled by kamailio itself. I am not sure but this might be the part where I should relay the request to asterisk(?): #!ifdef WITH_PRESENCE > if (!t_newtran()) { > sl_reply_error(); > exit; > } > if(is_method("PUBLISH")) { > handle_publish(); > t_release(); > } else if(is_method("SUBSCRIBE")) { > handle_subscribe(); > t_release(); > } > exit; > #!endif Currently the lights are "broken", some phones show them on, some off. Kind regards Kevin

2 1

Kamailio SQL error
by Marcos Pytel 06 Nov '18

06 Nov '18

Hello team! Im using kamailio in sipwise! I get this errors: Nov 5 11:51:34 sipwise proxy[1943]: ERROR: <core> [db_query.c:235]: db_do_insert_cmd(): error while submitting query Nov 5 11:51:34 sipwise proxy[1943]: ERROR: presence [subscribe.c:2514]: update_db_subs_timer(): unsuccessful sql insert Nov 5 11:51:34 sipwise proxy[1943]: ERROR: db_mysql [km_dbase.c:127]: db_mysql_submit_query(): driver error on query: Duplicate entry '6c23f96-0001-0003-0030(a)10.7.255.250-f3067022b00c564156251ba2f28f' for key 'active_watchers_idx' (1062) How can I fix it? Thank you! Marcos.

2 2

db_mongodb_get_columns(): field [username] not found in result iterator
by Denys Pozniak 06 Nov '18

06 Nov '18

Hello! I want to keep user location in mongodb, but Kamailio does not start well. Configuration: loadmodule "usrloc.so" loadmodule "db_mongodb.so" modparam("usrloc", "db_insert_null", 1) modparam("usrloc", "db_url", "mongodb://mongodb.test/kamailio") modparam("usrloc", "db_mode", 2) modparam("usrloc", "timer_interval", 30) modparam("usrloc", "desc_time_order", 1) Mongodb: rs0:PRIMARY> use kamailio switched to db kamailio rs0:PRIMARY> db.location.find() { "_id" : ObjectId("5be024d6b9d8febf4ae19681"), "name" : "location", "version" : 9, "columns" : { "id" : { "type" : "int", "default" : null, "null" : false }, "ruid" : { "type" : "string", "default" : "", "null" : false }, "username" : { "type" : "string", "default" : "", "null" : false }, "domain" : { "type" : "string", "default" : null, "null" : true }, "contact" : { "type" : "string", "default" : "", "null" : false }, "received" : { "type" : "string", "default" : null, "null" : true }, "path" : { "type" : "string", "default" : null, "null" : true }, "expires" : { "type" : "datetime", "default" : "2030-05-28 21:32:15", "null" : false }, "q" : { "type" : "double", "default" : 1, "null" : false }, "callid" : { "type" : "string", "default" : "Default-Call-ID", "null" : false }, "cseq" : { "type" : "int", "default" : 1, "null" : false }, "last_modified" : { "type" : "datetime", "default" : "2000-01-01 00:00:01", "null" : false }, "flags" : { "type" : "int", "default" : 0, "null" : false }, "cflags" : { "type" : "int", "default" : 0, "null" : false }, "user_agent" : { "type" : "string", "default" : "", "null" : false }, "socket" : { "type" : "string", "default" : null, "null" : true }, "methods" : { "type" : "int", "default" : null, "null" : true }, "instance" : { "type" : "string", "default" : null, "null" : true }, "reg_id" : { "type" : "int", "default" : 0, "null" : false }, "server_id" : { "type" : "int", "default" : 0, "null" : false }, "connection_id" : { "type" : "int", "default" : 0, "null" : false }, "keepalive" : { "type" : "int", "default" : 0, "null" : false }, "partition" : { "type" : "int", "default" : 0, "null" : false } } } { "_id" : ObjectId("5be02a77175610be86a1a589"), "username" : "dummy_user" } Syslog: Nov 5 12:51:01 dev-rtpengine /usr/sbin/kamailio[21543]: ERROR: db_mongodb [mongodb_dbase.c:416]: db_mongodb_get_columns(): field [username] not found in result iterator Nov 5 12:51:01 dev-rtpengine /usr/sbin/kamailio[21543]: ERROR: db_mongodb [mongodb_dbase.c:815]: db_mongodb_store_result(): failed to set the columns Nov 5 12:51:01 dev-rtpengine /usr/sbin/kamailio[21543]: ERROR: db_mongodb [mongodb_dbase.c:1018]: db_mongodb_query(): failed to store result Nov 5 12:51:01 dev-rtpengine /usr/sbin/kamailio[21543]: ERROR: db_mongodb [mongodb_dbase.c:1027]: db_mongodb_query(): failed to do the query Nov 5 12:51:01 dev-rtpengine /usr/sbin/kamailio[21543]: ERROR: usrloc [udomain.c:457]: preload_udomain(): db_query failed Nov 5 12:51:01 dev-rtpengine /usr/sbin/kamailio[21543]: ERROR: usrloc [usrloc_mod.c:430]: child_init(): child(1): failed to preload domain 'location' Nov 5 12:51:01 dev-rtpengine /usr/sbin/kamailio[21543]: ERROR: <core> [core/sr_module.c:946]: init_mod_child(): error while initializing module usrloc (/usr/lib64/kamailio/modules/usrloc.so) (idx: 1 rank: 1 desc: [udp receiver child=0 sock=10.10.10.10:5060]) Nov 5 12:51:01 dev-rtpengine /usr/sbin/kamailio[21543]: ERROR: <core> [core/pt.c:340]: fork_process(): init_child failed for process 1, pid 21543, "udp receiver child=0 sock=10.10.10.10:5060" Nov 5 12:51:01 dev-rtpengine /usr/sbin/kamailio[21543]: CRITICAL: <core> [main.c:1607]: main_loop(): Cannot fork 2018-11-05T13:07:19.117+0100 D COMMAND [conn367] run command kamailio.$cmd { find: "version", filter: { table_name: "location" }, projection: { table_version: 1 } } 2018-11-05T13:07:19.118+0100 I COMMAND [conn367] command kamailio.version command: find { find: "version", filter: { table_name: "location" }, projection: { table_version: 1 } } planSummary: COLLSCAN keysExamined:0 docsExamined:2 cursorExhausted:1 numYields:0 nreturned:1 reslen:148 locks:{ Global: { acquireCount: { r: 2 } }, Database: { acquireCount: { r: 1 } }, Collection: { acquireCount: { r: 1 } } } protocol:op_query 0ms 2018-11-05T13:07:19.118+0100 D COMMAND [conn367] run command kamailio.$cmd { find: "location", filter: { username: "dummy_user" }, projection: { username: 1 } } 2018-11-05T13:07:19.119+0100 I COMMAND [conn367] command kamailio.location command: find { find: "location", filter: { username: "dummy_user" }, projection: { username: 1 } } planSummary: COLLSCAN keysExamined:0 docsExamined:2 cursorExhausted:1 numYields:0 nreturned:1 reslen:155 locks:{ Global: { acquireCount: { r: 2 } }, Database: { acquireCount: { r: 1 } }, Collection: { acquireCount: { r: 1 } } } protocol:op_query 0ms 2018-11-05T13:07:19.178+0100 D COMMAND [conn368] run command kamailio.$cmd { find: "location", filter: {}, projection: { username: 1, contact: 1, expires: 1, q: 1, callid: 1, cseq: 1, flags: 1, cflags: 1, user_agent: 1, received: 1, path: 1, socket: 1, methods: 1, last_modified: 1, ruid: 1, instance: 1, reg_id: 1, server_id: 1, connection_id: 1, keepalive: 1 } } 2018-11-05T13:07:19.179+0100 I COMMAND [conn368] command kamailio.location command: find { find: "location", filter: {}, projection: { username: 1, contact: 1, expires: 1, q: 1, callid: 1, cseq: 1, flags: 1, cflags: 1, user_agent: 1, received: 1, path: 1, socket: 1, methods: 1, last_modified: 1, ruid: 1, instance: 1, reg_id: 1, server_id: 1, connection_id: 1, keepalive: 1 } } planSummary: COLLSCAN keysExamined:0 docsExamined:2 cursorExhausted:1 numYields:0 nreturned:2 reslen:180 locks:{ Global: { acquireCount: { r: 2 } }, Database: { acquireCount: { r: 1 } }, Collection: { acquireCount: { r: 1 } } } protocol:op_query 0ms [root@dev-rtpengine kamailio]# kamailio -v version: kamailio 5.1.6 (x86_64/linux) 7d1964 flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144 MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 7d1964 compiled on 11:10:15 Nov 4 2018 with gcc 4.8.5 -- BR, Denys Pozniak

2 5

Fwd: Fw: kamailio5.0.0 support presence
by chaos wu 06 Nov '18

06 Nov '18

Hi Kamailio expert, i want to use kamailio to simulate presence server, after receive subscribe, i need kamailio reply 200 OK, and then send out Notify, but now, it just forward the subscribe, don't reply, could you help check my cfg? thanks in advance. BRs

2 1

Development is open for future release v5.3.x series
by Daniel-Constantin Mierla 06 Nov '18

06 Nov '18

Hello, with the creation of branch 5.2 done this morning, the master branch is from now on open for adding new features, to be part of future release series v5.3.x. Any bug fix committed to master that applies to 5.2.x or older stable branches should be backported as usual with git cherry-pick to appropriate branches like 5.2 or 5.1. Expect that v5.2.0 will be released in about 2-3 weeks from now. Based on the workflow used during the past years, the next future release v5.3.0 should be out after another 8-10 months of development, plus 1-2 months of testing, so sometime in the summer or autumn of 2019. 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

Branch 5.2 has been created
by Daniel-Constantin Mierla 06 Nov '18

06 Nov '18

Hello, the branch 5.2 has been created, to be used for releasing v5.2.x series. To check out this branch, the following commands can be used: git clone https://github.com/kamailio/kamailio kamailio-5.2 cd kamailio-5.2 git checkout -b 5.2 origin/5.2 Pushing commits in this branch: git push origin 5.2:5.2 Note that 5.2 is an official stable branch, so only bug fixes, missing kemi exports (discuss on sr-dev if not sure) or improvements to documentation or helper tools can be pushed to this branch. As usual, if there is a bug fixed, commit and push first to master branch and then cherry pick to 5.2 branch. In few weeks, the first release from branch 5.2 will be out, respectively Kamailio v5.2.0. 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

Use of SCTP on public SIP server
by Kevin Olbrich 06 Nov '18

06 Nov '18

Hi! I read about the SCTP module for Kamailio and I am not sure if I should load it (currently I am not). Does this provide any benefit when Kamailio is used as proxy in front of Asterisk? At least from Wikipedia and the kamailio docs, it sounds like I can load it and it does it's magic. The multihomed part caught my attention. Kinds regards Kevin

3 2

How register with STORE_PLAINTEXT_PW=0
by José Antonio Gutiérrez Delgado 05 Nov '18

05 Nov '18

Hello, I recently discovered that the Kamailio database stores the user's password directly. I have found that by changing STORE_PLAINTEXT_PW = 0 in the configuration file, it stops storing the password in the database, but if I make this change I can no longer register the users in Kamailio. How should I register if I do not store the password? Have I missed a step? I have read that it is related to the HA1 field but it has not been clear how to do it. I hope your help. Thank you. -- José Antonio Gutiérrez Delgado Responsable técnico Oficina: (+34) 923040031 <http://www.arsoft-company.com/> *Este mensaje se dirige exclusivamente a su destinatario/s y puede contener información privilegiada o confidencial. Si no es vd. el destinatario indicado, queda notificado de que la utilización, divulgación y/o copia sin autorización está prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.* *Antes de imprimir, piensa si es necesario. Cuidar el medioambiente es tarea de todos.*

2 2

Storing in-progress dialogs in database
by jenus＠cyberchaos.nl 05 Nov '18

05 Nov '18

Hi all, I'm testing with the new dlg_db_load_callid function to replicate dialogs to another (standby) kamailio instance on failover. This works fine for calls that are connected. But i'm missing the dialogs in "ringing" state. Looks like dialogs are written to database by the dialog module when we receive the 200OK/ACK for the invite transaction. The result is that the call gets connected on the other kamailio instance but without a dialog. Is it possible to store the early_dialogs that are in rining state in the database? If that is not the case can i still create a dialog when i only receive the 200OK/ACK to the INVITE transaction (INVITE was processed by another instance) since TM is not aware of the INVITE transaction? I also tried to reject the 200OK to the INVITE in the on reply route, but running into the same issue that TM does not know the INVITE transaction. Thanks, Jan

2 1

← Newer
1
2
3
4
5
6
7
8
9
Older →

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