sr-users

sr-users@lists.kamailio.org

1 participants
37563 discussions

Problems this morning using Iptel.org
by swill 08 May '14

08 May '14

Hi, I use a configuration of ipkall and iptel.org, Most of the time this works out as a great incoming solution, however, today, it seems to be ending the call as i answer, I use only one softpphone at a time, but have tried it on Zoiper, 3cx, and Phonerlite, It does the same thing, call it, it rings, answer it and it immediately goes to "Call ended". I've done powercycle reboots on my HTC EVO 4G LTE, and on my PC it acts the same on all three. It registers fine on them all, I just cant determine if it is an IPKall or an Iptel problem..Is anyone else having an issue?? Are there any suggestions on what further troubleshooting I could do?? Thanks Michael

2 1

Kamailio auto restart if stopped
by JR Richardson 07 May '14

07 May '14

Hi All, Just had a strange occurrence where kamailio has been up and running fine for several months and just died with a strange error: root@sip-router3:~# kamailio -V version: kamailio 4.1.1 (x86_64/linux) ac7d55 May 7 10:09:51 sip-router3 /usr/local/sbin/kamailio[2275]: : <core> [mem/q_malloc.c:468]: qm_free(): BUG: qm_free: freeing already freed pointer (0x7faf565586d0), called from <core>: mem/shm_mem.c: sh_realloc(88), first free <core>: mem/shm_mem.c: sh_realloc(88) - aborting May 7 10:09:51 sip-router3 /usr/local/sbin/kamailio[2271]: ALERT: <core> [main.c:775]: handle_sigs(): child process 2275 exited by a signal 6 May 7 10:09:51 sip-router3 /usr/local/sbin/kamailio[2271]: ALERT: <core> [main.c:778]: handle_sigs(): core was not generated May 7 10:09:51 sip-router3 /usr/local/sbin/kamailio[2271]: INFO: <core> [main.c:790]: handle_sigs(): INFO: terminating due to SIGCHLD May 7 10:09:51 sip-router3 /usr/local/sbin/kamailio[2279]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 7 10:09:51 sip-router3 /usr/local/sbin/kamailio[2277]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 7 10:09:51 sip-router3 /usr/local/sbin/kamailio[2273]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 7 10:09:51 sip-router3 /usr/local/sbin/kamailio[2272]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 7 10:09:51 sip-router3 /usr/local/sbin/kamailio[2274]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 7 10:09:51 sip-router3 /usr/local/sbin/kamailio[2276]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 7 10:09:51 sip-router3 /usr/local/sbin/kamailio[2278]: INFO: <core> [main.c:841]: sig_usr(): INFO: signal 15 received May 7 10:09:51 sip-router3 /usr/local/sbin/kamailio[2271]: ERROR: ctl [ctl.c:379]: mod_destroy(): ERROR: ctl: could not delete unix socket /tmp/kamailio_ctl: Operation not permitted (1) Not sure what that means, memory leak? I started started it right back up with no indication of a problem. Running Kamailio for many years, I have never had an instance of it just shut down before. So I'm wondering if there are any safe scripts that check the running process for kamailio and restart if automatically if not running? I dug around a bit but not seeing any hits for auto start kamailio scripts. And another question would be if this occurrence of shutting down should be of concern or not? Thanks. JR -- JR Richardson Engineering for the Masses

2 1

Can "presence" module handle publish reqs with several dialog entries?
by Klaus Feichtinger 07 May '14

07 May '14

Hi, during simulating scenarios in relation with the notify problem I have so far, I became unsure, if Kamilio (in principal) is supporting handling of PUBLISH requests (event "dialog") that contain _more than_ one (1) dialog entry. I know that it can generate notify requests with a message body that contains more than one dialog entry. But that´s not automatically the same as handling publish requests.... So - is Kamailio able or not? Did anybody ever use it in such a scenario? regards, Klaus

2 7

Problem initial configuration of Kamalio
by Mr.Gab 07 May '14

07 May '14

Hello everybody, i'm new to kamalio and i'm trying to install on a centos server hosted on a open-stack IaaS platform. I followed the official wiki adding the "advertise statement" and define WITH_NAT. I added 3 user as test 100 101 102 that i can see typing kamctl db show subscriber but if i try to register with Bria i get Failed. Theese are sip packets that i sniffed with tcpdump. http://pastebin.com/sa74HJqM can someone help a noob to understad how to debug this kind of problem with kamalio? i tried googling but i didn't find anything. Thank you all in advice

1 0

Routing incoming calls to Asterisk trunk
by Teleport Engineer 07 May '14

07 May '14

Hello, I'd setup a test environment where Kamailio accepts external invites and routes them to an internal Asterisk (actually working as an SBC). My dialplan works fine routing the INVITE to the internal Asterisk, but the SIP message goes into the defaul sip context (the one configured in sip general), and not in the context defined for the sip trunk between Kamailio and Asterisk. The sip trunk is configured like this: [kamailio] disallow=all host=kamailio port=5060 insecure=port,invite type=friend context=from-sip-external fromdomain=mydomain qualify=yes allow=alaw allow=g722 So I expect that all the sip invites coming from kamailio should be executed in from-sip-external context. But it doesn't work like this since each invite goes in the default context. The invite that goes to Asterisk is like this <--- SIP read from kamailio-external:5060 ---> INVITE sip:extension@asterisk:5060;transport=UDP SIP/2.0 Record-Route: <sip:kamailio-external:5060;nat=yes;ftag=905e4921;lr=on> Via: SIP/2.0/UDP kamailio-external:5060;branch=z9hG4bK277a.aea3ad87.0 Via: SIP/2.0/UDP caller:28021;rport=28019;received=caller;branch=z9hG4bK-d8754z-d11f1fa1d0fb2ab4-1---d8754z- Max-Forwards: 69 Contact: <sip:524@caller:28019;transport=UDP> To: <sip:extension@kamailio-external> From: <sip:524@caller:28007>;tag=905e4921 Call-ID: YzEzMDM1NDZhZTllMTRiMDJmY2MyZTE0ZWZjMzE5OTc. CSeq: 1 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri User-Agent: Z 3.2.21357 r21367 Allow-Events: presence, kpml Content-Type: application/sdp Content-Length: 260 What I think is that in the sip message there is no information about kamailio internal ip address but only about kamailio-external address and then Asterisk put it into the default context. If this is the reason, should I change the trunk ip address in Asterisk and should I do some manipulation on the incoming packet on kamailio? Or maybe I should use kamailio-external as fromdomain in the trunk configuration? Thanks.

2 1

Asterisk-Kamailio set up
by VOIP Tests 07 May '14

07 May '14

Hello, I have a set up with Asterisk-Kamailio as explained in http://kb.asipto.com/asterisk:realtime:kamailio-3.1.x-asterisk-1.6.2-astdb. This set up has been working well for us for sometime now. We are now moving Asterisk to a stand alone server ( not installing it on the same box as asterisk ) but we are running into some issues. I have just made some changes to the Asterisk bind IP address and port and also set up Kamalio as a peer on asterisk. When I make an extension to extension call the calls are failing from the FROMASTERISK route ( call is getting cancelled ). Can someone let me know what changes I need to make to correct the issue? Some pointer will help. Thank you, Arun

2 2

How to enable TLS compression
by 刘日新 06 May '14

06 May '14

Hi, all. I has configure kamailio.cfg as below: #!ifdef WITH_TLS modparam("tls", "session_id", "vic22") modparam("tls", "session_cache",1) modparam("tls", "tls_disable_compression",0) modparam("tls", "config", "/usr/cfg/tls.cfg") #!endif I was sure that this configure segment was included , in case that I set a wrong path to modparam("tls", "config", "/wrong paths/tls.cfg") the kamailio can`t boost and raised error. But, when I debug this configure with gdb, I found that, within method : init_tls_compression(), Line 384 of tls_init.c 384 } else if (cfg_get(tls, tls_cfg, disable_compression)){ 385 LOG(L_INFO, "tls: init_tls: disabling compression...\n"); 386 sk_SSL_COMP_zero(comp_methods); The param value from cfg was always 1, namely: * print ((struct cfg_group_tls *)tls_cfg)->disable_compression 1 Why that? Are there something wrong? B.R. Rixin liu

4 3

Dispatcher question
by Volkan Oransoy 06 May '14

06 May '14

Hi all, I have a multidomain setup that I share load, among two freeswtich servers with a kamailio loadbalancer using dispatcher. For specific applications like queues, I need to match a sip domain with a freeswitch server. A domain should match same freeswitch server on every request. Which algorithm should I use with ds_selecy_dst, or what is the most appropriate way to do this? Thanks. /Volkan

2 1

Port 5061 problem
by aawaise 05 May '14

05 May '14

Hello, I have configured TLS on kamailio server. Problem is that in kamailio.cfg, when I use command port =5061. Kamailio doesnot start and error given in logs is >> ERROR: tcp_init : bind(a, 0x9007f4, 16) on MyIP:5061 : Adress already in >> use >> ERROR: Error while initializing TCP port of TLS Socket MyIP:5061 I tried the command " netstat -lntp | grep 5061 " to see what service or app is using the port 5061. I found no result. It is not used by any application apparently. Any help will be highly appreciated. Thanks. Aawaise -- View this message in context: http://sip-router.1086192.n5.nabble.com/Port-5061-problem-tp127464.html Sent from the Users mailing list archive at Nabble.com.

5 6

Location table not updated
by VOIP Tests 05 May '14

05 May '14

Hello, can someone let me know the reason that the location table does not get updated? Out of 15 extension only a few registered phones details get updated in this table and the rest are not. But I can see all the extension in Kamailio when I run kamctl ul show --brief. Thank you, Arun

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