sr-users

sr-users@lists.kamailio.org

42 participants
37519 discussions

CNXCC
by Keith 14 Aug '15

14 Aug '15

Hi All, I have CNXCC setup, it is kind of working but when I run kamcmd cnxcc.check_client the call information is still there even when the call is disconnected. Is this right? I basically want to make sure a customer can only have x number of simultaneous calls. Thanks Keith

1 0

Re: [SR-Users] cnxcc
by Keith 13 Aug '15

13 Aug '15

Hi Guys, Trying to use cnxcc but cnxcc.so is not in the modules folder. What is the easiest way to install? Thanks Keith

1 0

Problems investigating a crash in the siptrace module (4.3.1)
by Sven Neuhaus 13 Aug '15

13 Aug '15

Hi, we're experiencing crashes in the siptrace.so module with Kamailio 4.3.1. I looked at the core dump with gdb but it complained about missing debugging symbols so all I could see was that it called do_action() before branching into an unknown function in the siptrace module. I then installed the kamailio-dbg package to get the debugging symbols. This had the weird effect that get the error "Cannot access memory at ..." in GDB and no longer see *any* function names (previously only the names in the siptrace module were missing. Any idea whats going on? # gdb /usr/sbin/kamailio core GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/sbin/kamailio...Reading symbols from /usr/lib/debug/.build-id/e7/8dc57031d294f320b360d8f2f875a005db757e.debug...done. done. [New LWP 31426] Cannot access memory at address 0x3840f881f9c13908 Cannot access memory at address 0x3840f881f9c13900 (gdb) list 1771 main.c: No such file or directory. (gdb) info threads Id Target Id Frame * 1 LWP 31426 0x00007fbc89403f0f in ?? () (gdb) bt full #0 0x00007fbc89403f0f in ?? () No symbol table info available. #1 0x0800011000d46460 in ?? () No symbol table info available. #2 0xffffffff00000001 in ?? () No symbol table info available. #3 0x0000000000d63230 in ?? () No symbol table info available. #4 0x00000000d59d000a in ?? () No symbol table info available. #5 0x0000000000000000 in ?? () No symbol table info available. # dpkg -l kamailio\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==============================-====================-====================-================================================================= ii kamailio 4.3.1+wheezy amd64 very fast and configurable SIP proxy un kamailio-berkeley-modules <none> (no description available) un kamailio-carrierroute-modules <none> (no description available) un kamailio-cpl-modules <none> (no description available) ii kamailio-dbg:amd64 4.3.1+wheezy amd64 very fast and configurable SIP proxy [debug symbols] un kamailio-ldap-modules <none> (no description available) un kamailio-lua-modules <none> (no description available) un kamailio-mysql-modules <none> (no description available) un kamailio-perl-modules <none> (no description available) ii kamailio-postgres-modules:amd6 4.3.1+wheezy amd64 PostgreSQL database connectivity module for Kamailio un kamailio-presence-modules <none> (no description available) un kamailio-python-modules <none> (no description available) un kamailio-radius-modules <none> (no description available) un kamailio-snmpstats-modules <none> (no description available) un kamailio-tls-modules <none> (no description available) un kamailio-unixodbc-modules <none> (no description available) un kamailio-xml-modules <none> (no description available) un kamailio-xmpp-modules <none> (no description available) Regards, -Sven

2 2

Kamailio SCTP with CentOS
by Mellow Yellow 13 Aug '15

13 Aug '15

Hey guys, I've been pulling out my hair for a few days trying to get SCTP with Kamailio working in CentOS 7... with no luck at all. When attempting to start Kamailio via the 'kamctl start' command I get the following error: INFO: Starting Kamailio : ERROR: PID file /var/run/kamailio.pid does not exist -- Kamailio start failed When attempting to start Kamailio via the 'systemctl start kamailio' command, I get the following: Job for kamailio.service failed. See 'systemctl status kamailio.service' and 'journalctl -xn' for details. When checking the 'systemctl status kamailio -l' command, I get the following: kamailio.service - SYSV: Kamailio is a fast, reliable and flexible SIP Server. Loaded: loaded (/etc/rc.d/init.d/kamailio) Active: failed (Result: exit-code) since Thu 2015-08-13 00:42:51 AEST; 14s ago Process: 19229 ExecStart=/etc/rc.d/init.d/kamailio start (code=exited, status=1/FAILURE) Aug 13 00:42:51 Elastix5.workgroup /usr/sbin/kamailio[19242]: INFO: rr [rr_mod.c:174]: mod_init(): outbound module not available Aug 13 00:42:51 Elastix5.workgroup /usr/sbin/kamailio[19242]: INFO: usrloc [hslot.c:51]: ul_init_locks(): locks array size 1024 Aug 13 00:42:51 Elastix5.workgroup /usr/sbin/kamailio[19242]: ERROR: ctl [init_socks.c:115]: init_unix_sock(): ERROR: init_unix_sock: bind: No such file or directory [2] Aug 13 00:42:51 Elastix5.workgroup /usr/sbin/kamailio[19242]: ERROR: ctl [ctl.c:273]: mod_init(): ERROR: ctl: mod_init: init ctrl. sockets failed Aug 13 00:42:51 Elastix5.workgroup /usr/sbin/kamailio[19242]: ERROR: <core> [sr_module.c:945]: init_mod(): Error while initializing module ctl (/usr/lib64/kamailio/modules/ctl.so) Aug 13 00:42:51 Elastix5.workgroup /usr/sbin/kamailio[19242]: INFO: <core> [sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Aug 13 00:42:51 Elastix5.workgroup kamailio[19229]: Starting kamailio: Aug 13 00:42:51 Elastix5.workgroup systemd[1]: kamailio.service: control process exited, code=exited status=1 Aug 13 00:42:51 Elastix5.workgroup systemd[1]: Failed to start SYSV: Kamailio is a fast, reliable and flexible SIP Server.. Aug 13 00:42:51 Elastix5.workgroup systemd[1]: Unit kamailio.service entered failed state. So I started to think there was an issue with the SCTP config or whether SCTP was enabled in CentOS. However, everything looks fine: # cat /proc/modules sctp 217455 2 - Live 0xffffffffa03ed000 # /sbin/lsmod | grep sctp sctp 217455 2 libcrc32c 12644 2 xfs,sctp # more /proc/sys/net/sctp/addip_enable 1 # checksctp SCTP supported SCTP modules installed properly: Package lksctp-tools-devel-1.0.13-3.el7.x86_64 already installed and latest version Package lksctp-tools-doc-1.0.13-3.el7.x86_64 already installed and latest version Package lksctp-tools-1.0.13-3.el7.x86_64 already installed and latest version Running the ' sctp_test' command between two servers, SCTP is working fine... I can capture SCTP packets between the servers. I've left the Kamailio.cfg file as is... with the only modification being made to enable the SCTP module to start: enable_sctp = 1 Checking 'kamailio -v' USE_SCTP is enabled: # kamailio -v version: kamailio 4.3.1 (x86_64/linux) f38e67 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, F_MALLOC, DBG_F_MALLOC, 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_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: f38e67 compiled on 18:17:56 Jul 20 2015 with gcc 4.8.2 I've tried installing Kamailio with the precompiled rpms for CentOS 7, and I also followed some guides on installing in via GIT & compiling it myself... however the issue still remains. Any help would be greatly appreciated as I've completely run out of ideas, and there isn't much info on the web about Kamailio & SCTP. Thanks, Rob

2 2

upgrade V4.2.5 to V3.1 -Build error
by Yasin CANER 13 Aug '15

13 Aug '15

3 3

XCap Server + Postgre
by Igor Olhovskiy 12 Aug '15

12 Aug '15

Hi! I'm experience really strange behavior of Kamailio. Right now it's using postgre database When trying to implement XCAP server capabilities, according to http://kamailio.org/docs/modules/4.3.x/modules/xcap_server.html#idp76784 on a block if (!www_authorize("xcap", "subscriber")) { www_challenge("xcap", "0"); exit; } While trying to test it via browser (user test, pass test) I've got these errors in log Aug 12 12:34:57 sip01 /usr/sbin/kamailio[7655]: WARNING: db_postgres [km_dbase.c:235]: db_postgres_submit_query(): postgres result check failed with code 7 (PGRES_FATAL_ERROR) Aug 12 12:34:57 sip01 /usr/sbin/kamailio[7655]: WARNING: db_postgres [km_dbase.c:239]: db_postgres_submit_query(): postgres query command failed, connection status 0, error [ERROR: relation "subscriber" does not exist#012LINE 1: select password from subscriber where extension='test' AND u...#012 ^#012] Aug 12 12:34:57 sip01 /usr/sbin/kamailio[7655]: WARNING: db_postgres [km_dbase.c:235]: db_postgres_submit_query(): postgres result check failed with code 7 (PGRES_FATAL_ERROR) Aug 12 12:34:57 sip01 /usr/sbin/kamailio[7655]: WARNING: db_postgres [km_dbase.c:239]: db_postgres_submit_query(): postgres query command failed, connection status 0, error [ERROR: relation "subscriber" does not exist#012LINE 1: select password from subscriber where extension='test' AND u...#012 ^#012] Aug 12 12:34:57 sip01 /usr/sbin/kamailio[7655]: WARNING: db_postgres [km_dbase.c:235]: db_postgres_submit_query(): postgres result check failed with code 7 (PGRES_FATAL_ERROR) Aug 12 12:34:57 sip01 /usr/sbin/kamailio[7655]: WARNING: db_postgres [km_dbase.c:239]: db_postgres_submit_query(): postgres query command failed, connection status 0, error [ERROR: relation "subscriber" does not exist#012LINE 1: select password from subscriber where extension='test' AND u...#012 ^#012] Aug 12 12:34:57 sip01 /usr/sbin/kamailio[7655]: ERROR: db_postgres [km_dbase.c:247]: db_postgres_submit_query(): 0x7f3fb0660b10 PQsendQuery Error: ERROR: relation "subscriber" does not exist#012LINE 1: select password from subscriber where extension='test' AND u...#012 ^#012 Query: select password from subscriber where extension='test' AND user_context='xcap' Aug 12 12:34:57 sip01 /usr/sbin/kamailio[7655]: ERROR: <core> [db_query.c:132]: db_do_query_internal(): error while submitting query Aug 12 12:34:57 sip01 /usr/sbin/kamailio[7655]: ERROR: auth_db [authorize.c:175]: get_ha1(): failed to query database Without this block, I don't get user auth. Is it a bug or it's mine misconfiguration? -- Best regards, Igor

2 3

kamailio as SIP Agent
by Sandeep Chakravarthi 12 Aug '15

12 Aug '15

Hi, We have a requirement with one of our telco We are using asterisk in our servers and we are planning to implement SIP-I protocol and we choosed kamailio for it. In Kamailio website, i came to know that kamailio will be supporting both SIP-I and SIP-T protocols Below is what we need and pls confirm whether it is possible or not? Asterisk PBX <-------> Kamailio <--------> Telco MSC Telco will be forwarding the calls to kamailio on sip-i protocol and kamailio server has to forward the calls to our Asterisk server by converting sip-i to standard sip protocol Similiarly Asterisk will be initiating sip call to kamailio server and kamailio server should convert it into SIP-I and should forward the call to Telco MSC 1. I am able to establish the SIP trunk [sending OPTIONS from asterisk and kamailio acknowledges with 200 OK] between Asterisk and Kamailio using dispatcher module in kamailio and sip.conf in asterisk. How to establish the SIP trunk between kamailio and telco MSC? [Generally MSC will act as SIP server and kamalio should send OPTIONS packet and MSC will acknowledges with 200 OK] My telco MSC has only provided me the MSC SIP IP and there were no username/passwords provided. Means i need to use IP based authentication for the SIP Trunk establishment. In Kamailio how to achieve it? Please help and any suggestions/feedback will be highly appreciated and thankful Regards, Sandeep

2 12

sdp manipulation in connection with rtpengine_offer/answer calls
by Juha Heinanen 12 Aug '15

12 Aug '15

it was not clear to me based on rtpengine module readme if rtpengine_offer/answer are same kind of sdp manipulation functions as, for example, sdpops module functions, i.e., will rtpengine functions pass to rtpengine the sdp as it is after possible earlier sdpops function calls and will possible sdpops functions calls after rtpengine function call keep on manipulating the sdp returned from rtpengine function call. -- juha

4 16

RTPProxy incorrect port 0 in reply from rtp proxy
by Grant Bagdasarian 12 Aug '15

12 Aug '15

Hello, I've been load testing kamailio(4.2) with rtpproxy(2.0) using sipp, and when I hit 50+ CPS I start getting the following error: "incorrect port 0 in reply from rtp proxy". I'm running 4 instances of rtpproxy on the same instance as kamailio. Could somebody tell me why I'm receiving this error? Do I need to run more instances of rtpproxy? # <#----------RTPPROXY Parameters----------#> modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:7721 udp:127.0.0.1:7722 udp:127.0.0.1:7723 udp:127.0.0.1:7724") In request_route: if (is_method("INVITE")) { record_route(); if (has_body("application/sdp")) { rtpproxy_manage(); } } In onreply_route: if (has_body("application/sdp")) { rtpproxy_manage(); } rtpproxy -s udp:127.0.0.1:7721 -u rtpproxy rtpproxy -p /var/run/rtpproxy/rtpproxy.pid -l 10.0.0.1 rtpproxy -s udp:127.0.0.1:7722 -u rtpproxy rtpproxy -p /var/run/rtpproxy/rtpproxy1.pid -l 10.0.0.1 rtpproxy -s udp:127.0.0.1:7723 -u rtpproxy rtpproxy -p /var/run/rtpproxy/rtpproxy2.pid -l 10.0.0.1 rtpproxy -s udp:127.0.0.1:7724 -u rtpproxy rtpproxy -p /var/run/rtpproxy/rtpproxy3.pid -l 10.0.0.1 Regards, Grant

1 1

Re: [SR-Users] LCR Routing - Cost based routing
by DanB 12 Aug '15

12 Aug '15

Hi Alexandru, Well the concept is simple: on INVITE, you will issue a special format evapi request. You will receive the list of suppliers in the reply (which is received in a separate route) and you continue processing from there. These suppliers are simple tags so your creativity will be the limit of what you can do with them - eg: direct ip addresses received or tags of suppliers which you can further translate with drouting module or any alias related one. For more information on LCR please find this year's presentation on Kamailio World (which I strongly recommend to be attended): https://www.youtube.com/watch?v=Hsvcwleb-fY You can also find the kamailio configuration which I have used in the worshop here: https://github.com/cgrates/cgrates/tree/master/data/tutorials/kamevapi/kama… Let me know if further questions (or join our irc or mailing list so we do not create too much noise here). DanB

3 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