sr-users November 2014

sr-users@lists.kamailio.org

91 participants
128 discussions

by Javier Ricke

i work with asterisk, but i have problem at the moment to send audio rtp, because ip is private, kamailio will could solution this problem? regards

9 years, 5 months

mysql db error

by shmick＠riseup.net

9 years, 5 months

Address already in use error when starting Kamailio service

by Mahmoud Ramadan Ali

Hiiiiii everyone, I'm receiving this error when starting Kamailio saying that it can not resolve my ip addresses used by Kamailio and another "127.0.0.1:5060 : Address already in use " error message...so how can i fix this please ? Nov 2 15:39:26 Kamailio /usr/local/sbin/kamailio[7692]: CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 35 Nov 2 15:39:44 Kamailio kamailio: WARNING: <core> [socket_info.c:1392]: fix_hostname(): could not rev. resolve 192.168.100.1 Nov 2 15:39:44 Kamailio kamailio: WARNING: <core> [socket_info.c:1392]: fix_hostname(): could not rev. resolve 192.168.50.1 Nov 2 15:39:44 Kamailio kamailio: WARNING: <core> [socket_info.c:1392]: fix_hostname(): could not rev. resolve 192.168.100.1 Nov 2 15:39:44 Kamailio kamailio: WARNING: <core> [socket_info.c:1392]: fix_hostname(): could not rev. resolve 192.168.50.1 Nov 2 15:39:44 Kamailio /usr/local/sbin/kamailio[7726]: ERROR: <core> [tcp_main.c:2876]: tcp_init(): bind(b, 0x7faebd135ca4, 16) on 127.0.0.1:5060 : Address already in use

9 years, 5 months

Kamailio behind NAT - Wrong VIA Header

by Marko Seidenglanz

Hello, We are using Kamailio 4.2 and RTPEngine 3.3 hosted on a VM behind NAT in Google Cloud Engine. Asterisk 11 + Kamailio + RTPEngine are on the same machine and Kamailio is used as WebRTC Gateway. INVITES, that are rewritten by Kamailio look like the following: INVITE sip:eTden7KoNSdMVCUNYIwmz@wh2.24dial.com SIP/2.0 Record-Route: <sip:0.0.0.0:5064;lr=on;nat=yes> Via: SIP/2.0/UDP 0.0.0.0:5064 ;branch=z9hG4bK86f5.88fb7f8810c91758b5f3962420d3a4ef.0 Via: SIP/2.0/UDP 10.240.1.95:5060 ;received=127.0.0.1;branch=z9hG4bK05952ee6;rport=5060 Max-Forwards: 69 From: "Anonymous" <sip:anonymous@anonymous.invalid>;tag=as7900b63f To: <sip:eTden7KoNSdMVCUNYIwmz@wh2.24dial.com> Contact: <sip:anonymous@10.240.1.95:5060;alias=127.0.0.1~5060~1> Call-ID: 0662d336694c60ed60ed5310571a1aee@10.240.1.95:5060 CSeq: 102 INVITE User-Agent: Asterisk PBX 11.13.1 Date: Mon, 03 Nov 2014 09:01:39 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Content-Type: application/sdp Content-Length: 676 P-hint: outbound As you can see, Kamailio uses 0.0.0.0 for Record-Route as well as for VIA Header. It uses the address configured in kamilio.cfg (listen=udp:0.0.0.0:5064) I know, that we could use the advertise parameter to tell kamailio the external IP. The problem is, that IPs in GCE are dynamically assigned to the VMs. Thus static configuration of external IP is not sufficient for our setup. Is there a way, to let Kamailio gather it's external IP dynamically. (E.g. using a STUN server or something like that?) Another possibility would be to tell Kamailio it's external IP via a start parameter. Is that possible? Any help would be grateful. Kind regards, Marko Seidenglanz

9 years, 5 months

using time stamp

by bob sacamano

hi, I am trying to see how long kamailio takes to process messages I saw the commands: set_time_stamp diff_time_stamp in older versions of kamailio but they dont seem to be available. I have been searching for info but have been unable to find anything. Is the command no longer available or is there some other way to use? thanks

9 years, 5 months

FIFO Error When Running Kamctl dispatcher reload

by Mahmoud Ramadan Ali

Hiiiii Everyone I have encountered that error whenever i try to use the #Kamctl dispatcher reload even thought that i have the "modparam("mi_fifo", "fifo_name", "/tmp/kamailio_fifo")" and loadmodule "mi_fifo.so" configured...any ideas how to solve this issue ?! root@Kamailio:/usr/local/etc/kamailio# kamctl dispatcher reload ERROR: Error opening Kamailio's FIFO /tmp/kamailio_fifo ERROR: Make sure you have the line 'modparam("mi_fifo", "fifo_name", "/tmp/kamailio_fifo")' in your config ERROR: and also have loaded the mi_fifo module.

9 years, 5 months

Re: [Kamailio-Users] /usr/local/sbin/kamdbctl create error

by vivi

Hi all.. I have solve the problem . Cheers, vivi From: vivi [mailto:vivi.hilton@gmail.com] Sent: Saturday, June 06, 2009 11:29 PM To: 'users(a)lists.kamailio.org' Subject: /usr/local/sbin/kamdbctl create error Hi all I have specify the wanted db type (DBENGINE=MYSQL) in the /usr/local/etc/kamailio/kamctlrc then I using "/usr/local/sbin/kamdbctl create" to create MySQL database, but I got this error: ERROR: database engine not specified, please setup one in the config script root@acer:/usr/local/src/kamailio-1.5.0/sip-server# vim /usr/local/etc/kamailio/kamctlrc root@acer:/usr/local/src/kamailio-1.5.0/sip-server# /usr/local/sbin/kamdbctl create MySQL password for root: INFO: test server charset ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) Usage: grep [OPTION]... PATTERN [FILE]... Try `grep --help' for more information. /usr/local/lib/kamailio/kamctl/kamdbctl.mysql: line 112: [: =: unary operator expected INFO: creating database openser ... ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) ERROR: Creating core database and grant privileges failed! Cheers, vivi

9 years, 5 months

Trouble with LCR removing $ru after upgrading to 4.1.6

by Will Ferrer

Hi We are having an odd issue with our LCR. This started after we upgraded from kamailio 4.1.0 to 4.1.6. Here is the situation: We populate our gw_uri_avp (stored in: $avp(i:709)) as follows: 16|1||||[gateway ip address]||5060||1|1. The $ru before running next gateway shows: sip:[destination number]@[our domain that the call came into]. This is how it should look before lcr occurs. Then we run next_gw(). We get these message in the logs during the running of next_gw DEBUG: lcr [lcr_mod.c:2156]: generate_uris(): r_uri <*1*[destination number]@[gateway ip address]:5060*1*>, dst_uri <> DEBUG: lcr [lcr_mod.c:2437]: next_gw(): added ruri_user_avp <[destination number]> DEBUG: lcr [lcr_mod.c:2473]: next_gw(): added flags_avp <1> DEBUG: lcr [lcr_mod.c:2480]: next_gw(): added tag_avp <> DEBUG: lcr [lcr_mod.c:2488]: next_gw(): added defunct_gw_avp <1253613379> The main thing to notice there is that there is now a 1 at the start and end of the r_uri shown in generate_uris. I am fairly certain those are new, and maybe related to what happens next. Immediately following the next_gw function running the $ru becomes: <null>, so of course the call doesn't go through. I have looked at the code for the lcr module and it looks like it wasn't changed in version 4.1.6. I found alot of other notes in the change log that had to do with the way uris are handled so it is possible one of those changes caused the problem. I am stumped currently. Any help any one can offer me would be very appreciated. All the best. Will Ferrer Swithsoft Inc

9 years, 5 months

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 2014