sr-users November 2014

sr-users@lists.kamailio.org

91 participants
128 discussions

question
by Javier Ricke 03 Nov '14

03 Nov '14

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

2 1

mysql db error
by shmick＠riseup.net 03 Nov '14

03 Nov '14

running kamailio from deb http://deb.kamailio.org/kamailio jessie main mysql> show columns; ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 it was a while ago, but i used the included script and followed wiki instructions to create the initial DB from memory it was a simple 1 liner cmd any help is appreciated thanks mysql> show tables; +---------------------+ | … [View More]

2 1

Address already in use error when starting Kamailio service
by Mahmoud Ramadan Ali 03 Nov '14

03 Nov '14

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:… [View More]

3 3

Kamailio behind NAT - Wrong VIA Header
by Marko Seidenglanz 03 Nov '14

03 Nov '14

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 ;… [View More]

2 1

using time stamp
by bob sacamano 03 Nov '14

03 Nov '14

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

2 3

FIFO Error When Running Kamctl dispatcher reload
by Mahmoud Ramadan Ali 02 Nov '14

02 Nov '14

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: … [View More]

2 1

Re: [Kamailio-Users] /usr/local/sbin/kamdbctl create error
by vivi 01 Nov '14

01 Nov '14

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 … [View More]

2 1

Trouble with LCR removing $ru after upgrading to 4.1.6
by Will Ferrer 01 Nov '14

01 Nov '14

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:… [View More]

2 4

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 November 2014