- sr-users - kamailio.org

module version mismatch for /usr/local/lib64/kamailio/modules/kex.so
by Abdul Basit 31 Oct '17

31 Oct '17

Hi, My kamailio installation with 5.0.3 was working fine. I update kamailio source to 5.0.4 and make all; make install I started receiving error below: /etc/init.d/kamailio start [FAIL] Not starting Kamailio SIP Server: invalid configuration file! ... failed! failed! [....] 0(7426) ERROR: <core> [core/sr_module.c:431]: version_control(): module version mismatch for /usr/local/lib64/kamailio/modules/kex.so; core: kamailio 5.0.3 (x86_64/lin[FAILmodule: kamailio 5.0.4 (x86_64/linux) ... failed! failed! kamailio.cfg is same as earlier. I removed kamailio sources and modules folder /usr/local/lib64/kamailio/modules/ I also dropped old kamailio postgres database and created new one after fresh source install of version 5.0.4 from git. # git clone https://github.com/kamailio/kamailio kamailio # cd kamailio # git checkout -b 5.0 origin/5.0 But this error persists. Whats the resolution? Is this a bug? -- regards, abdul basit

2 2

Source comparisons by DNS hostname
by Alex Balashov 31 Oct '17

31 Oct '17

Hi, Is there a reasonable way, in Kamailio, to determine whether the source of a given SIP message is equivalent to the IP address to which a given DNS hostname resolves? i.e. if(src_ip == 'fqdn.domain.xyz') but not src_ip, obviously. I can't find any core keywords that would seem to fit the bill for a composite comparison. Any other options? -- 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/

2 3

Radius accounting and cdr's
by Jan Hazenberg 31 Oct '17

31 Oct '17

Hi all, I have a question regarding radius accounting. I would like to have a config where i store local cdr records (and not the ACC records) and send accounting to radius as well. I have the following config: # ----- acc params ----- /* General settings */ modparam("acc", "log_level", 0) modparam("acc", "log_facility", "LOG_LOCAL2") /* Enable cdr's */ modparam("acc", "cdr_enable", 1) modparam("acc", "cdr_log_enable", 1) modparam("acc", "cdr_start_on_confirmed", 0) modparam("acc", "cdr_facility", "LOG_LOCAL2") modparam("acc", "cdr_on_failed", 1) /* what special events should be accounted ? */ modparam("acc", "early_media", 0) modparam("acc", "report_ack", 0) modparam("acc", "report_cancels", 0) modparam("acc", "detect_direction", 1) /* Accounting triggers (flags) */ modparam("acc", "log_flag", FLT_ACC) modparam("acc", "log_missed_flag", FLT_ACCMISSED) modparam("acc", "failed_transaction_flag", FLT_ACCFAILED) modparam("acc_radius", "radius_flag", FLT_ACC) modparam("acc_radius", "radius_missed_flag", FLT_ACCMISSED) modparam("acc_radius", "radius_config", "/etc/radiusclient-ng/radiusclient.conf") This works but stores the raw accounting records as well. If i disable the acc log_flag it stops sending radius accounting records (while the acc_radius log_flag is still enabled). Is it possible to send only radius accounting records and disable the local logging of those records, but leave the cdr logging enabled? Or is there a option where i can set only the cdr_log_level so accounting records will only show up when i increase the debug level? Another option is to use a seperate log facility for accounting and cdr's, but it would be nice if it is possible to disable the logging of accounting records and only keep the cdr's. I'm running kamailio 5.0.3. Thanks, Jan

2 2

Re: [SR-Users] Kamailio for Unified Communication
by Angel Elena 31 Oct '17

31 Oct '17

kamailio is a "proxy" server.... this features may be added by a media-server... freeswitch, asterisk, seems. You can put kamailio as "sip proxy" and you can add these services behind kamailio proxy -------------------------------- Ángel Elena Medina _o) craem(a)craem.net / \\ http://blog.craem.net _(___V @craem_ www.linkedin.com/in/angel-elena-medina -------------------------------- Zarafa Webapp. -----Mensaje original----- De: Jayanth Acharya <jayachar88(a)gmail.com> Enviado: Mar 31-10-2017 10:40 Asunto: [SR-Users] Kamailio for Unified Communication Para: Kamailio (SER) - Users Mailing List <sr-users(a)lists.sip-router.org>; > Hi, > > Can Kamailio be used to provide following broad-type of services ? > > 1. Unified Communication services > 2. Contact Center services > 3. Instant Messaging / Chat services > 4. Voicemail service > 5. Presence aware communication services > 6. Desktop sharing service > > For many/some of the above, I'd expect back2back user-agent capabilities to be > mandatory, and if I am not mistaken Kamailio doesn't support B2BUA mode. Or are > there some modules that may be used for this purpose ? > > thanks, > Jay > > _______________________________________________ > > Kamailio (SER) - Users Mailing List > > sr-users(a)lists.kamailio.org > > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > > >

1 0

Kamailio for Unified Communication
by Jayanth Acharya 31 Oct '17

31 Oct '17

Hi, Can Kamailio be used to provide following broad-type of services ? 1. Unified Communication services 2. Contact Center services 3. Instant Messaging / Chat services 4. Voicemail service 5. Presence aware communication services 6. Desktop sharing service For many/some of the above, I'd expect back2back user-agent capabilities to be mandatory, and if I am not mistaken Kamailio doesn't support B2BUA mode. Or are there some modules that may be used for this purpose ? thanks, Jay

1 0

Reinvite/ACK race
by Alex Balashov 30 Oct '17

30 Oct '17

Hi, I've got a scenario like so: UA A -----> Kamailio P ----> UA B 1. UA A initiates call through Kamailio P; 2. Dialog is established and confirmed, with Record-Route; 3. UA B sends reinvite #1 through P to A; 4. UA B sends 2xx reply; 5. UA B sends end-to-end ACK for reinvite #1 and almost simultaneously sends reinvite #2. The temporal delta is between reinvite #2 and ACK for reinvite #1 on the wire is 3 ms. So, the result — for all kinds of stochastic processing and userspace scheduling type reasons — is that the reinvite is forwarded first, before the ACK. That leads to a 500 / 491 scenario UA A. The cause, as we all know, is that Kamailio's worker threads are loosely coupled, and incoming UDP datagrams are distributed directly by the kernel. Is there any general guidance on what to do with these scenarios? I looked at RFC 5407 § 3.1.4, which appears to describe a similar, but not identical scenario involving an initial INVITE and subsequent reinvite. As far as I can tell, the recommendation in that standard is "space the messaging out more in time". Switching to TCP would presumably help, since any given flow would involve a single connection to a single worker thread and the transport would guarantee ordering. However, that's not really feasible in this implementation for a host of reasons. I know Kamailio has some config locking primitives, but I am extremely wary of complex synchronisation on dialog-identifying attributes, particularly if there is a possibility that such locks could stall a worker perpetually. Any other thoughts welcome! Cheers, -- 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/

2 2

unexpected behavior of save from registrar module
by Vasiliy Ganchev 30 Oct '17

30 Oct '17

Hi, community! I have in my Kamailio script following block (while REGISTER processing, after auth succeed): ..... /* Save to usrloc */ lock("LOCATION_LOCK"); if (!save("location")) { unlock("LOCATION_LOCK"); sl_reply_error(); exit(); } unlock("LOCATION_LOCK"); ...... According to module documentation - if "save" - failed (for any reason) - I expected the control to be returned to the script with error code "-1" But, there are cases - when this does not happen - which lead to deadlock for workers processing REGISTERs (I never unlock("LOCATION_LOCK")): - module answers with internal error - and return 0 from "save" function: https://github.com/kamailio/kamailio/blob/master/src/modules/registrar/save… - line 1013 My use case happened due to malfunctioning device that in some moment of time: - send REGISTER update - kamailio answers 200OK - device retransmit the same REGISTER (same CSeq) - during 20 seconds (hardcoded value in registrar module) - kamailio answers 200OK (and everything is ok) - if retransmission continue more than 20s - kamailio answered 400 Bad request, and did not return control to script (as a result I had no chance to unlock("LOCATION_LOCK") from code above) Tested it on kamailio 4.2.5 and 5.0.3. as for me, possible solutions are: - return -1 instead of 0 from "save" by default - if there are some reasons not to do this - we should change documentation, and explicitly mention that there are cases - when script execution is stopped. thanks in advance! cheers -- Sent from: http://sip-router.1086192.n5.nabble.com/Users-f3.html

3 5

sanity passes invalid uri
by Juha Heinanen 30 Oct '17

30 Oct '17

I noticed that K 5.0 sanity() test passes uri that contains ` (back quote) character. Config: modparam("sanity", "default_checks", 1024) /* URI checks */ modparam("sanity", "uri_checks", 3) /* RURI, From */ xlog("L_INFO", "Checking $ru\n"); if (!sanity_check()) xlog("L_INFO", "Check failed\n"); else xlog("L_INFO", "Check passed\n"); Syslog: Oct 27 17:17:38 lohi /usr/bin/sip-proxy[31946]: INFO: Checking sip:jh@te`st.fi Oct 27 17:17:38 lohi /usr/bin/sip-proxy[31946]: INFO: Check passed According to RFC3261: hostname = *( domainlabel "." ) toplabel [ "." ] domainlabel = alphanum / alphanum *( alphanum / "-" ) alphanum Is this a bug or am I missing something? -- Juha

2 2

Remove all cpecial characters (\n,\t etc)from xml body
by Yuriy Gorlichenko 30 Oct '17

30 Oct '17

Hi. I building external presentity service for web based phones Main trouble that i have at the xml body of PUBLISH message \n \t characters and because of it can't set body as string to the redis So I trying to find a way to remove special characters form the xml body for get oneline string instead of multiline I use native .cfg file for now and, unfortunattely, can not use lua or phyton I tried $var(body)=$(rb{s.rm,$var(RemoveThisStaff)}) where $var(RemoveThisStaff) = "\n" and "\t" but it was unsuccesfull. Maybe someone will help to kno how to do it.

2 2

Issue with sipcapture
by Nathan Leyton 28 Oct '17

28 Oct '17

Hi There I am new to Kamailio and have just installed and got it up and running as a sipcapture node. It is working well and logging all the hep sip traffic in my homer database. I have an issue with rtcp extracted to the msg column is not json. It is some kind of weird encoded string (not base64), this is not readable by homer in any way. When I use nonsip_hook I am able to extract the json from the hep and put it in the msg field. However when I return 1 from the hep route on sip to go back to main route I get parsing errors like so on all the sip messages:- Oct 27 15:03:41 ip-172-31-19-41 /usr/local/sbin/kamailio[22518]: ERROR: sipcapture [sipcapture.c:2711]: nosip_hep_msg(): couldn't parse sip message Oct 27 15:03:41 ip-172-31-19-41 /usr/local/sbin/kamailio[22518]: ERROR: <core> [core/receive.c:186]: receive_msg(): core parsing of SIP message failed (178.78.120.2:44389/1) Oct 27 15:03:41 ip-172-31-19-41 /usr/local/sbin/kamailio[22518]: ERROR: <core> [core/parser/msg_parser.c:331]: parse_headers(): bad header field [(null)] Oct 27 15:03:41 ip-172-31-19-41 /usr/local/sbin/kamailio[22518]: WARNING: <core> [core/receive.c:193]: receive_msg(): parsing relevant headers failed Oct 27 15:03:41 ip-172-31-19-41 /usr/local/sbin/kamailio[22517]: ERROR: <core> [core/parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) Oct 27 15:03:41 ip-172-31-19-41 /usr/local/sbin/kamailio[22517]: ERROR: <core> [core/parser/msg_parser.c:675]: parse_msg(): ERROR: parse_msg: message=<HEP3#002,> It never actually enters the main route. With nonsip_hook off, I enter the main route and all my sip messages are there in homer, just missing rtcp as the data is a weird encoded string. Hope someone can help Thanks Nathan -- Nathan Leyton / Chief Technology Officer nathan(a)callhandling.co.uk / 07482 917 412 Call Handling Ltd Office: 0333 321 0888 / Fax: 0333 321 0877 Bakerloo Chambers304 Edgware Road, London, W2 1DY www.callhandling.co.uk [image: htmlsig.com] <https://htmlsig.com/t/0000001BREBFR>

2 1

fix_nated_contact and IPv6
by Sebastian Damm 27 Oct '17

27 Oct '17

Hi, I'm trying to set up a Kamailio (4.1.3) server which converts between IPv6 and IPv4. Everything looks pretty good. Now I have a test client which sends packets via IPv6, but in contact header, SDP etc. there are still IPv4 addresses. (This comes from some converting from v4 to v6 earlier.) Thus, Kamailio tries to do a fix_nated_contact(). But after fixing, the Contact URI is wrong. Example: inbound Contact: <sip:bob@192.168.8.132> outbound Contact: <sip:bob@1234:1234:0:1234:0:0:0:2> The correct way of transforming the Contact URI would be: Contact: <sip:bob@[1234:1234:0:1234:0:0:0:2]> This incorrect Contact URI doesn't hurt first, but when the called party wants to hang up the call, it addresses the URI from Contact header, and Kamailio can't parse the Request URI: Jan 22 12:03:48 router /usr/sbin/kamailio[21309]: ERROR: pv [pv_core.c:304]: pv_get_ruri_attr(): failed to parse the R-URI Jan 22 12:03:48 router /usr/sbin/kamailio[21309]: ERROR: rr [loose.c:934]: loose_route(): failed to parse Request URI Jan 22 12:03:48 router /usr/sbin/kamailio[21309]: ERROR: domain [domain.c:140]: is_uri_host_local(): error while parsing R-URI Is this a bug in the nathelper module? Was it never meant to handle IPv6 addresses? Or do I understand something wrong? Best Regards, Sebastian

4 4

Too Long Contact URI
by Soltanici Ilie 27 Oct '17

27 Oct '17

Hi All, I cannot Register some softphones because of too long Contact header when using TCP protocol. Using UDP - everything works ok and this is how the Contact header looking: sip:XXXXXXXXX@XXX.XXX.XXX.XXX:64773;rinstance=6502234ef65ea6e7 But, switching to the TCP i'm receiving the following warning: WARNING: registrar [sip_msg.c:194]: check_contacts(): contact uri is too long:[sip:XXXXXXXXX@192.168.0.1:60471;rinstance=bf4d7aae0f099bf0;transport=tcp] How can i solve this issue? Thank You.

1 1

How to send OPTIONS message by kamailio server
by 吴妙灵 27 Oct '17

27 Oct '17

Hello, I don't know how to send OPTIONS message from kamailio server to user client,can you give me same advice? Cheers, Ada

4 3

Timer function didnot trigger the routing function
by RAJA SREE RATHNA gomathinayagam 27 Oct '17

27 Oct '17

Hi, I tried using the timer function to call a function after specific time but it was not working as specified. Could you please help me with some example using timer to trigger a function. I tried it using the description given in below link. www.kamailio.org/docs/modules/devel/modules/timer.html Thanks and regards, Rathna.

2 3

Kamailio v5.0.4 Released
by Daniel-Constantin Mierla 27 Oct '17

27 Oct '17

Hello, Kamailio SIP Server v5.0.4 stable release is out! This is a maintenance release of the latest stable branch, 5.0, that includes fixes since the release of v5.0.3. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.0.x. Deployments running previous 5.0.x versions are strongly recommended to be upgraded to v5.0.4. For more details about version 5.0.4 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2017/10/kamailio-v5-0-4-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda

2 4

Set timeout before 180/183 reply arrived
by Yu Boot 27 Oct '17

27 Oct '17

Hello. Have a problem with some uplinks. They sometimes respond "100 Trying" on initial INVITE and... that's all. A caller waits for about 30 seconds and cancel a call deciding there's something wrong with our network. How to use failure route when 180/183 answers don't arrive in 5 or 10 seconds after INVITE?

2 2

Get value of a custom header param
by Arsen 26 Oct '17

26 Oct '17

Hi guys! Is it possible to get value of a custom parameter of the authorization header? I've checked selects in the textops mod and try the following: if (is_present_hf("Authorization")) { xplog("L_ERR", "custom auth $sel((a)hf_value.authorization.edatech_opaque) \n"); } Arsen Semionov www.eurolan.info cell: +442035198881

3 5

Upgrading from 1.5 to 3.x
by Brandon Shiers 26 Oct '17

26 Oct '17

I have a client that has an old Kamailio 1.5 installation. They would like to migrate and get off their old hardware and old OS. I've read the upgrade page for the 1.5.x migration to 3.0.0, are there any gotchas to be aware of other than what's there? Brandon Shiers, Network Engineer 937 West Main Street Riverton, WY 82501 307.857.6704 (o) 307.840.2366 (c) 307.856.1499 (f) brandon.shiers(a)cerento.com<mailto:Brandon.Shiers@cerento.com> [http://www.cerento.com/emailsignatures/logo.jpg]

2 1

Regarding rtimer usage under specific condition
by RAJA SREE RATHNA gomathinayagam 26 Oct '17

26 Oct '17

Hello, While going through the rtimer module we noticed that it execute the routing function repeatedly after the given interval of time. But our specification is to execute the routing function only once and timer should be enabled based on specific condition. Also there is no enable or disable option for rtimer module as in timer module, whether rtimer module can be enabled based on specific condition.If it is possible could you please suggest the solution. Thanks & Regards, Rathna.

2 1

shared dialogs
by : Paolo Visintin - Time-Net S.r.l. 26 Oct '17

26 Oct '17

Hi kamailio users, I'm wondering if there's something already done with shared dialog among more kamailio instances, in order to manage branches initalized by another kamailio instance. A ctually seems not possible (also with db mode) because kamailio is looking into caller/callee_sock and if it's different does not manage in a "standard" failover environment (master / slave) with vIP and keepalived and $fs = VIRTUAL_IP everything is working fine but in a distributed environment this could not happen as the relay is managed by a kamailio proxy Thanks in advance Paolo

4 7

I-CSCF Prefixes IMPU with + Symbol
by Ron McLeod 25 Oct '17

25 Oct '17

I am working with v5.0.3 and the IMS extensions. When I attempt to send a SIP MESSAGE from the application server towards the UE, the I-CSCF used to determine the S-CSCF for the subscriber by sending a Location-Info request to the HSS. I found that this request was failing because the IMPU (IMS Public User Identity) was being mangled by the I-CSCF, prefixing the user part with a + symbol. The example configuration file for the I-CSCF does in-fact does cause the r-uri to be prefixed with a + symbol if one is not already present. I'm wondering why since it breaks the LIR/LIA lookup. AS I-CSCF HSS | MESSAGE | | | ---------------------> | | | sip:ron@provider1.test | | | | | | | | | | LIR | | | ----------------------> | | | sip:+ron@provider1.test | | | | | | | | | DIAMETER_UNKNOWN_USER | | | <---------------------- | | | | | | | | 403 | | | <--------------------- | | | FORBIDDEN | | route{ #!ifdef WITH_DEBUG xlog("I-CSCF >>>>>>>>>>>>>>>>>>>> $rm $ru ($fu => $tu ($si:$sp) to $tu, $ci)\n"); #!endif if !($rU =~ "\+.*") { prefix("+"); } ... Thanks, Ron

1 0

Testing for user=phone with siputils uri_param() doesn't work
by George Diamantopoulos 25 Oct '17

25 Oct '17

Hello, In my script I've had to test for the user=phone parameter in URIs. I thought uri_param() from siputils would be handy for this operation on the RURI, so I did: if ( !uri_param("user","phone") ) { add_uri_param("user=phone"); } Unfortunately this wouldn't work (uri_param returns -1), and I end up with double user=phone params in the RURI. I was able to work around this by changing the test to: if ( !($(ru{uri.uparam}) == "phone") ) { add_uri_param("user=phone"); } But I wanted to ask if this is intentional or if I should file a bug or something. Thanks. George

3 3

Planning Kamailio v5.0.4
by Daniel-Constantin Mierla 25 Oct '17

25 Oct '17

Hello, I am considering to release Kamailio v5.0.4 later this week, likely on Wednesday or Tuesday. If you are aware of any issue in branch 5.0 which is not yet reported on github.com/kamailio/kamailio issues tracker, then do it as soon as possible to have a chance to look at it. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training, Nov 13-15, 2017, in Berlin - www.asipto.com Kamailio World Conference - www.kamailioworld.com

3 5

usrloc module does not work with db_cluster
by Uri Shacked 25 Oct '17

25 Oct '17

Hi, I started using db_cluster module. DB are master-slave replication both ways. #!define DBURL "cluster://kamailio" when i stop the primary mysql server, all subscribers fails to register again. seems like the usrloc module does not work with the cluster. modparam("usrloc", "db_mode", 1) modparam("db_cluster", "cluster", "kamailio=>primary=9s9s;secondary=8s8s") it works OK for modules like dispatcher and htable to reload from DB. it shows the sql driver errors, but reloads from the secondary server. I need auto expire, so, p_usrloc is not a good option. working with version 4.2 any ideas ? Uri

2 1

FW: Mutual TLS with Skype for Business 2015
by Francisco Valentin Vinagrero 25 Oct '17

25 Oct '17

Hello, I'm trying to replace two old Audiocodes gateways (used to interconnect our Skype for Business infrastructure to the PSTN) with a new Kamailio cluster. I am having some trouble to get the TLS mutual authentication working with Kamailio. For the moment, I'm just trying to receive the incoming OPTIONS from SfB, but I get all the time certificate verification errors: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14089086:SSL routines:ssl3_get_client_certificate:certificate verify failed ERROR: <core> [tcp_read.c:1330]: tcp_read_req(): ERROR: tcp_read_req: error reading My tls.cfg is quite simple, with the same config for client and server (and one single listen=tls:<my IP>:5061 in the Kamailio.cfg file) [server:default] method = TLSv1+ verify_certificate = yes require_certificate = yes private_key = /usr/local/etc/kamailio/tls/key_gw_sfb.pem certificate = /usr/local/etc/kamailio/tls/cert_gw_sfb.pem # => This certificate's Subject is the DNS alias for the cluster, with all the kamailios in the cluster as Subject Alternative Names ca_list = /usr/local/etc/kamailio/tls/myca_and_sfbca.pem # => Kamailio and Skype for Business are signed by different CAs, so here I concatenated all intermediate and root CAs [client:default] method = TLSv1+ verify_certificate = yes require_certificate = yes private_key = /usr/local/etc/kamailio/tls/key_gw_sfb.pem certificate = /usr/local/etc/kamailio/tls/cert_gw_sfb.pem ca_list = /usr/local/etc/kamailio/tls/myca_and_sfbca.pem When I run Kamailio, I can see incoming OPTIONS from Microsoft Exchange Unified Messaging (UM), whose certificate I verify without any issues. UM presents a certificate issued for a single machine, so no Subject Alternative Names (SANs) are involved. The problem comes with the TLS handshake for the Skype Mediation pool. They have a certificate with Subject = DNS alias and all the physical machines that are behind the alias appear listed as Subject Alternative Names (SANs) in the certificate. As the only difference between UM and Skype's Mediation is the certificate's Subject, I think I am missing something on my configuration to validate the SANs instead of the subject. Is the TLS module doing any reverse DNS lookup to verify this? Thanks, Francisco.

1 0

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