Hi All
Last few days we have tried to setup Kamailio for IMS server setup.
We have not been successful.
Now we are planning to use Kamailio 4.2.0 code base (Latest) to setup
Kamailio IMS setup.
I am looking for a link/document, that gives proper step by step
instructions how to setup Kamailio as IMS servers (P-CSCF, I-CSCF and
S-CSCF).
Can somebody kindly provide the official link or any other working link,
that I can follow to setup P-CSCF, I-CSCF ,S-CSCF and HSS.
Many thanks
Austin
Hey Daniel,
Thanks for your fast reply!
I am using the 4.2.0 out of debian packages (not nightly). Will shift on
nightly and retest.
Not a big deal regarding 150 seconds, maybe it should be a good reason
for async reloads (reply with the delay number of seconds when reload
will happen). Reloads can be always implemented outside of kamailio but
since everybody would need it I assume a more centralized approach would
be useful.
Anyway, thanks again!
DanB
On 24.10.2014 12:00, sr-users-request(a)lists.sip-router.org wrote:
> Hello,
>
> are you using branch 4.2 or some tgz/package from 4.2.0 release? There
> was a fix related to such issue, so 4.2 branch must be used (or debian
> nightly builds for 4.2).
>
> I will have to check the code how flexible that is, but afaik, the limit
> on reload interval was thought to avoid sending again registration
> requests while retransmissions from previous one can occur.
>
> Cheers,
> Danel
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
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
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
Using Kamailio 4.2, CentOS 6.5, as per the documentation here: https://github.com/sipwise/rtpengine
"Running make will compile the binary, which will be called rtpengine."
When trying to install rtpengine I got the following error when building "daemon"
[root@ip-10-0-2-68 daemon]# make
Usage: awk [POSIX or GNU style options] -f progfile [--] file ...
Usage: awk [POSIX or GNU style options] [--] 'program' file ...
POSIX options: GNU long options:
-f progfile --file=progfile
-F fs --field-separator=fs
-v var=val --assign=var=val
-m[fr] val
-O --optimize
-W compat --compat
-W copyleft --copyleft
-W copyright --copyright
-W dump-variables[=file] --dump-variables[=file]
-W exec=file --exec=file
-W gen-po --gen-po
-W help --help
-W lint[=fatal] --lint[=fatal]
-W lint-old --lint-old
-W non-decimal-data --non-decimal-data
-W profile[=file] --profile[=file]
-W posix --posix
-W re-interval --re-interval
-W source=program-text --source=program-text
-W traditional --traditional
-W usage --usage
-W use-lc-numeric --use-lc-numeric
-W version --version
To report bugs, see node `Bugs' in `gawk.info', which is
section `Reporting Problems and Bugs' in the printed version.
gawk is a pattern scanning and processing language.
By default it reads standard input and writes standard output.
Examples:
gawk '{ sum += $1 }; END { print sum }' file
gawk -F: '{ print $1 }' /etc/passwd
Makefile:88: .depend: No such file or directory
make: *** No rule to make target `aux.c', needed by `.depend'. Stop.
[root@ip-10-0-2-68 daemon]#
I was able to build the iptables-extension, the kernel failed because I dont have the dependencies but the daemon is required.
I think that I have all the dependencies:
[root@ip-10-0-2-68 daemon]# rpm -qa | egrep "pcre|pkgconfig|xml|glib|zlib|openssl|curl"
openssl-1.0.1e-30.el6_6.2.x86_64
glibc-common-2.12-1.132.el6_5.4.x86_64
zlib-1.2.3-29.el6.x86_64
curl-7.19.7-37.el6_5.3.x86_64
glibc-devel-2.12-1.132.el6_5.4.x86_64
libcurl-devel-7.19.7-37.el6_5.3.x86_64
openssl-devel-1.0.1e-30.el6_6.2.x86_64
glibc-2.12-1.132.el6_5.4.x86_64
pcre-7.8-6.el6.x86_64
libxml2-2.7.6-14.el6_5.2.x86_64
libcurl-7.19.7-37.el6_5.3.x86_64
python-pycurl-7.19.0-8.el6.x86_64
pkgconfig-0.23-9.1.el6.x86_64
glib2-2.26.1-7.el6_5.x86_64
dbus-glib-0.86-6.el6.x86_64
glibc-headers-2.12-1.132.el6_5.4.x86_64
zlib-devel-1.2.3-29.el6.x86_64
libxml2-devel-2.7.6-14.el6_5.2.x86_64
pcre-devel-7.8-6.el6.x86_64
[root@ip-10-0-2-68 daemon]#
Am I missing something here?, thank you
jp
Hi,
There does not seem to be a way to update the limits of pipes dynamically.
If I don't use DB backing, there is no MI/RPC command to flush existing
pipes and cause them to be recreated with reconstituted limits.
If I use DB backing and add pipes to the pl_pipes table, an SQL update
to the limit column does not influence existing pipes that have been
loaded from the DB on startup.
Am I missing something, or does the existing feature set of the module
simply not allow this?
Thanks,
--
Alex Balashov - Principal
Evariste Systems LLC
Tel: +1-678-954-0670
Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
Please be kind to the English language:
http://www.entrepreneur.com/article/232906
Another thing I have found is that having a certain amount of async
workers running, even if they are not doing anything, appears to cause
unexplained CPU load, even if the Kamailio instance is completely idle
and not processing any calls.
Here is the baseline load with no async workers:
[root@centosity6 ~]# uptime
14:06:28 up 2 min, 2 users, load average: 0.01, 0.00, 0.00
If I start Kamailio with 1 async worker...
modparam("async", "workers", 1)
async_workers=1
14:07:59 up 3 min, 2 users, load average: 0.00, 0.00, 0.00
Still nothing.
Now I try 2:
14:08:54 up 4 min, 2 users, load average: 0.45, 0.11, 0.04
14:08:59 up 4 min, 2 users, load average: 0.49, 0.12, 0.04
14:09:04 up 4 min, 2 users, load average: 0.53, 0.14, 0.04
14:09:09 up 4 min, 2 users, load average: 0.57, 0.15, 0.05
14:09:14 up 5 min, 2 users, load average: 0.60, 0.17, 0.05
14:09:19 up 5 min, 2 users, load average: 0.63, 0.18, 0.06
14:09:31 up 5 min, 2 users, load average: 0.69, 0.21, 0.07
14:09:37 up 5 min, 2 users, load average: 0.71, 0.22, 0.07
14:10:35 up 6 min, 2 users, load average: 0.89, 0.36, 0.13
14:11:07 up 6 min, 2 users, load average: 0.93, 0.42, 0.16
...
I don't have time right now to see if it will rise to infinity, but it
just keeps going up.
There are no SIP messages being received at all, and there is absolutely
nothing going on.
The ascent of the load average is much higher with >= 4 threads. I have
8 "CPUs" available from /proc/cpuinfo (quad-core processor with
HyperThreading).
When I attach strace to the PID of the Async Worker, there's nothing
going on except the normal recvfrom() blocking wait:
[root@centosity6 kamailio]# kamctl ps | grep Async
which: no greadlink in
(/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin:/)
Process:: ID=11 PID=1559 Type=Async Task Worker
Process:: ID=12 PID=1560 Type=Async Task Worker
[root@centosity6 kamailio]# strace -p 1559
Process 1559 attached - interrupt to quit
recvfrom(9,
[root@centosity6 ~]# strace -p 1560
Process 1560 attached - interrupt to quit
recvfrom(9,
Nor do the other Kamailio threads seem to be doing anything unusual. 'ps
aux' and 'top' show 0.0% CPU load on the Kamailio processes themselves,
and 'iowait' shows the system as 98-99% idle.
I suppose it's possible that this is a peculiarity of the testing
environment: I am running this on CentOS 6.5 inside VirtualBox, which I
think is KVM-based. I have not had a chance to duplicate this experiment
in a different kind of execution environment yet. It's possible that the
load average is simply being improperly indicated because of the VM
environment.
--
Alex Balashov - Principal
Evariste Systems LLC
Tel: +1-678-954-0670
Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
Please be kind to the English language:
http://www.entrepreneur.com/article/232906
Hi all,
is it possible to add in
http://kamailio.org/docs/modules/4.2.x/modules/tls.html
under the line
>
9.1. |tls_method| (string)
...
...
If rfc3261 conformance is desired, TLSv1 must be used. For compatibility
with older clients SSLv23 is a good option.
*Example 1.3. Set |tls_method| parameter*
...
modparam("tls", "tls_method", "TLSv1")
...
<
!!! *a warning **that the use of SSLv3 **susceptibility to POODLE
Vulnerability* !!!
--
*Rainer Piper*
Integration engineer
Koeslinstr. 56
53123 BONN
GERMANY
Phone: +49 228 97167161
P2P: sip:rainer@sip.soho-piper.de:5072 (pjsip-test)
XMPP: rainer(a)xmpp.soho-piper.de
