Hey all,
Congratulation on 3.1 release !
Any news on when siremis v 2.0 is hitting the stores ?
In the mean time what about alpha/beta version of it ? Its nowhere on the
repos/sites (asipto etc..)
Is version 1.0.1 know to work smoothly with kamailio 3.1 ?
Cheers
--
Hi, in the doc of HTable module all the examples show "a=>size=4;". As
the doc says:
size - number specifying the size of hash table. The number of entries in
the table is 2^size
This is, the examples just allow 16 concurrent entries, which is not
enough in most of the cases.
Did I misunderstand something? or do the module examples use a non
very pertinent value?
Thanks a lot.
--
Iñaki Baz Castillo
<ibc(a)aliax.net>
Hello,
Kamailio (OpenSER) v3.0.4 is released. This is a maintenance release of
previous stable branch, 3.0.x, that includes fixes since release of
v3.0.3. There is no change to database or configuration file required to
upgrade to 3.0.4 from any 3.0.x version.
For more details about version 3.0.4, visit:
http://www.kamailio.org/w/2010/10/kamailio-v3-0-4-released/
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com
Hello,
Kamailio (OpenSER) version 1.5.5 is released. This is a maintenance
release of branch 1.5, the last in its series.
The project is officially maintaining the latest two stable branches,
these being now 3.0.x and 3.1.x. As it happened in the past, fixes can
still get into SVN branch 1.5, but there is no plan to package another
version 1.5.x.
If you still run 1.5.x, it is highly recommended that you start to plan
the migration to 3.x versions.
For more details about version 1.5.5, visit:
http://www.kamailio.org/w/2010/10/kamailio-v1-5-5-released/
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com
We had another one of these today, under high call volume:
(gdb) where
#0 0x0000003a60430265 in raise () from /lib64/libc.so.6
#1 0x0000003a60431d10 in abort () from /lib64/libc.so.6
#2 0x0000000000530a91 in qm_free (qm=0x2b343e1aa000, p=0x2b343eddf6e8,
file=0x2b343dd860c3 "dialog: dlg_hash.c",
func=0x2b343dd86b42 "destroy_dlg", line=176) at mem/q_malloc.c:447
#3 0x00002b343dd6a2ea in destroy_dlg (dlg=0x2b343fe1d6f8) at dlg_hash.c:176
#4 0x00002b343dd6d33a in unref_dlg (dlg=0x2b343fe1d6f8, cnt=1)
at dlg_hash.c:591
#5 0x00002b343dd73a04 in profile_cleanup (msg=<value optimized out>,
flags=<value optimized out>, param=0x6) at dlg_profile.c:317
#6 0x00000000004be9a1 in exec_post_script_cb (msg=0xa06e80,
type=<value optimized out>) at script_cb.c:195
#7 0x00000000004989f0 in receive_msg (
buf=0x8b6300 "BYE sip:15746317356@yyy.yyy.yyy.yyy:5060
SIP/2.0\r\nRecord-Route:
<sip:yyy.yyy.yyy.yyy;lr;ftag=gK0ebaf6d4>\r\nRecord-Route:
<sip:67.231.8.89;lr;ftag=gK0ebaf6d4>\r\nVia: SIP/2.0/UDP
xxx.xxx.xxx.xxx;branch=z9hG4bKd757."...,
len=<value optimized out>, rcv_info=0x7fff4a043230) at receive.c:221
#8 0x000000000052576a in udp_rcv_loop () at udp_server.c:532
#9 0x0000000000468dcd in main_loop () at main.c:1554
#10 0x000000000046be9f in main (argc=<value optimized out>,
argv=0x7fff4a043508) at main.c:2398
Is this a regression, or memory corruption from something else?
This is with CANCEL_REASON_SUPPORT #undef'd in tm_reply.h, btw.
--
Alex Balashov - Principal
Evariste Systems LLC
1170 Peachtree Street
12th Floor, Suite 1200
Atlanta, GA 30309
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
Hello,
Based on our project policy to support officially the last two stable
branches, I was thinking of packaging kamailio 1.5.5 to mark its end.
New fixes will go to svn if it is the case, but no new release in 1.5.x
series will be done.
Also, since testing for 3.1.0 brought some fixes to 3.0.x, we should do
as well 3.0.4. My proposal is next week, Wednesday, Oct 20.
Don't forget to report issues you are aware for these two branches.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com
Hi
I'm using version 1.5.4 and the module userblacklist is not working how I was
expecting.
The function check_user_black_list() returns the correct value. After some 5
minutes, it
changes its return value. I'm blocking users that are not in the table. However,
after this
time, the functions says that they exist, but it is not true.
Someone know why it happens? Could it be a module's bug?
#avp 100 is a part of the username's RURI
if(check_user_blacklist("$fU","$rd","$avp(s:100)"))
{
sl_send_reply("403", "Forbidden");
exit;
}
Tks,
bruno machado
Hi,
I have an application that uses dbtext. Starting with an empty location
table I have a client register with kamailio.
When kamailio is shut down the location records are written.
When kamailio starts again it fails when reading the location value.
The client does not provide an Allow: header. Field 16 in the location
table is a parsed version of the Allow: header.
When kamailio shuts down it writes a space ' ' for the value of field
16. This then causes the re-read to fail. Removing the space makes it
all work again.
I'd like to report this as a bug - and/or - even better - to get a quick
patch to sort the problem. Is this the right place to report? Or is
there an official form?
Thanks
Jeremy
Kamailio 3.0.3.
I am trying to change a variable (in the cfg variable framwork) from
sercmd, but I get an error
[root@sip-core-1 ~]# sercmd cfg.set_now_int recording enabled 1
error: 500 - command cfg.set_now_int not found
I have installed readline and ncurses which seems to be needed by
looking at sercmd.c.
Any ideas what I am missing?
--
Morten Isaksen
