sr-users

sr-users@lists.kamailio.org

42 participants
37517 discussions

Kamailio Realtime Integration with Asterisk
by Floimair Florian 02 Nov '17

02 Nov '17

Hi! I found a few tutorials from Daniel on this topic , the latest being https://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astd… . Has anyone ever tried this with a more recent Asterisk version (13 or newer) and using chan_pjsip instead of chan_sip? I'd be willing to update the tutorial once I get it running but I would like to avoid going through obstacles that were already handled ;-) My desired setup is 2 Asterisk boxes (which share configuration, useres and registrations via DB) behind a Kamailio as Load-balancer (got that working already). With best regards Florian Floimair COMMEND INTERNATIONAL GMBH A-5020 Salzburg, Saalachstraße 51 f.floimair(a)commend.com<mailto:f.floimair@commend.com> http://www.commend.com<http://www.commend.com/> Security and Communication by Commend FN 178618z | LG Salzburg

1 0

Mutual TLS with Skype for Business 2015
by Francisco Valentin Vinagrero 02 Nov '17

02 Nov '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.

4 11

Reading the P-Assserted-identity header
by Gertjan Wolzak 01 Nov '17

01 Nov '17

Hello Kamailions, I receive anonymous calls where the PAI has a prefix which I need to strip before forwarding the call to a proxy. I am trying to read the the header with $hdr(P-Asserted-Identity) and I tried the $ai pseudovariable, but I get an empty reply back every time. xlog("PAI is $ai"); results in ; "Nov 1 16:19:55 proxy04 /usr/local/sbin/kamailio[14814]: ERROR: <script>: PAI is <null>" Same for xlog("PAI is $hdr(P-Asserted-Identity). This works for the Privacy header but not the P-Asserted-Identity header. Hope someone can tell me what I am doing wrong.... Rgds, Gertjan

3 2

Record-Route IP Value
by Soltanici Ilie 31 Oct '17

31 Oct '17

Hi All, Having the following Header: Record-Route: <sip:192.168.1.1;lr;did=637.07c7c2d7> How can i extract only IP value from this header? Thank You.

2 3

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

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