I'm using the group module to assign groups to users. As the
documentation states, "the table content is loaded into memory at
startup and all regular expressions are compiled". Having to restart
Kamailio is cumbersome every time the table is updated. Is there a
method to reload the table via kamcmd?
Also, I had no luck in getting the non-regex method of group to
recognize a table entry, for example, 159(a)mydomain.com was split into
159 and mydomain.com, yet it get_user_group wouldn't match it. It was
only when I started using the regex table that I had success.
Hi there. I had a working Kamailio proxy working where i could call from one polycom test phone to another. But then I tried to integrate freeswitch with it... (following the article found at: http://kb.asipto.com/freeswitch:kamailio-3.1.x-freeswitch-1.0.6d-sbc as a baseline. )
Now when I dial a phone, it's just silent for a few seconds... after which i get a busy tone.
I did a tcpdump and have been reviewing the file in wireshark. It looks like my two test phones are registered properly... but as you can see, the INVITE is not getting an OK back. It just keeps on retrying the invite. I'm not sure how to go about troubleshooting this.
Any suggestions on where to start would be appreciated. In the meantime, I'm googling around to see if I can find anything that might help me figure this out.
thanks.
Hello,
I disable the rr module and only use SIP elements for dialog match
modparam("dialog", "dlg_match_mode", 2)
Upon receipt of a BYE request, the request is correctly forwarded and the
call ended but the dialog still exists with ref_count = 2
kamctl fifo dlg_list
dialog:: hash=731:5167
state:: 3
ref_count:: 2
timestart:: 1394625569
timeout:: 29082806
callid:: 77dd7249530067080de983411e94569c@10.100.8.12:5060
from_uri:: sip:10.100.8.12:5060
from_tag:: as03e52e3f
caller_contact:: sip:10.100.8.12:5060
caller_cseq:: 102
caller_route_set::
caller_bind_addr:: udp:10.100.8.94:5060
callee_bind_addr:: udp:10.100.8.94:5060
Do you have any idea ? Should I remove manually the dialog using a module
function?
Thanks for your help
Best regards,
Hi,
a new release of Siremis is out - v4.1.0 - web management interface that
is compatible out of the box with Kamailio v4.1.x series.
More details, including link to install tutorial, are available at:
- http://siremis.asipto.com/2014/03/25/siremis-v4-1-0-released/
Regards,
Ramona
Hi, i have installed the new version ok kamailio 4.1.2.
I don't know why Kamailio crash writing this ob the log:
: <core> [mem/q_malloc.c:468]: qm_free(): BUG: qm_free: freeing already
freed pointer (0x7fc3ab755eb0), called from dialog: dlg_hash.c:
dlg_update_cseq(591), first free dialog: dlg_hash.c: dlg_update_cseq(591) -
aborting
Anybody can help me to undertand what is the problem?
thanks
Hello Everyone,
I am trying compare domain part of uri with ldap query result, getting some syntax warning
1.
arn_at(): warning in config file /etc/kamailio/kamailio-ldap.cfg, line 992, column 17-39: constant value in if(...)
2.
3.
4.
ldap_result("sipExtension/$avp(extension)");
5.
ldap_result("sipDomain/$avp(domain)");
6.
ldap_result("password/$avp(password)");
7.
8.
}
9.
10.
if ("$avp(s:domain)" =~ "$fd") {
11.
xlog("L_INFO", "Not alllowed $fd");
12.
sl_send_reply("403","Not allowed $fd");
13.
exit;
14.
}
15.
any help thank you
I would like to report a bug on the presence module
kamailio 4.0.5
setting custom table names via
modparam("presence", "presentity_table", "kam_presentity")
modparam("presence", "active_watchers_table", "kam_active_watchers")
modparam("presence", "watchers_table", "kam_watchers")
does work, i can see entries on the table when logged in.
however these things show up from time to time, seems like it is not
looking for the custom table name.
/usr/local/sbin/kamailio[20406]: ERROR: db_mysql [km_dbase.c:122]:
db_mysql_submit_query(): driver error on query: Table 'kam.presentity'
doesn't exist
/usr/local/sbin/kamailio[20406]: ERROR: <core> [db_query.c:132]:
db_do_query_internal(): error while submitting query
/usr/local/sbin/kamailio[20406]: ERROR: <core> [db_query.c:429]:
db_fetch_query_internal(): unable to query db for fetch
/usr/local/sbin/kamailio[20406]: ERROR: presence [publish.c:108]:
msg_presentity_clean(): failed to query database for expired messages
/usr/local/sbin/kamailio[20406]: ERROR: db_mysql [km_dbase.c:122]:
db_mysql_submit_query(): driver error on query: Table 'kam.presentity'
doesn't exist
/usr/local/sbin/kamailio[20406]: ERROR: <core> [db_query.c:291]:
db_do_delete(): error while submitting query
/usr/local/sbin/kamailio[20406]: ERROR: presence [publish.c:227]:
msg_presentity_clean(): failed to delete expired records from DB
/usr/local/sbin/kamailio[20406]: ERROR: db_mysql [km_dbase.c:122]:
db_mysql_submit_query(): driver error on query: Table 'kam.watchers'
doesn't exist
/usr/local/sbin/kamailio[20406]: ERROR: <core> [db_query.c:291]:
db_do_delete(): error while submitting query
/usr/local/sbin/kamailio[20406]: ERROR: presence [subscribe.c:745]:
msg_watchers_clean(): cleaning pending subscriptions
/usr/local/sbin/kamailio[20406]: ERROR: db_mysql [km_dbase.c:122]:
db_mysql_submit_query(): driver error on query: Table 'kam.active_watchers'
doesn't exist
/usr/local/sbin/kamailio[20406]: ERROR: <core> [db_query.c:291]:
db_do_delete(): error while submitting query
/usr/local/sbin/kamailio[20406]: ERROR: presence [subscribe.c:2220]:
update_db_subs_timer(): deleting expired information from database
Kelvin Chua
Hello,
After couple of weeks without issue, my Kamailio 4.0 has begun to reject
calls this week-end.
The first error : ERROR: <core> [msg_translator.c:2012]:
build_res_buf_from_sip_res(): ERROR: build_res_buf_from_sip_res: out of mem.
OR
ERROR: <core> [msg_translator.c:2012]: build_res_buf_from_sip_res(): ERROR:
build_res_buf_from_sip_res: out of mem
Followed by
ERROR: <core> [forward.c:812]: do_forward_reply(): ERROR: forward_reply:
building failed
And sometimes, at the end of the line there is a "needs" in addition:
ERROR: <core> [msg_translator.c:2164]: build_res_buf_from_sip_req(): ERROR:
build_res_buf_from_sip_req: out of memory ; needs 469.
The starting options are: OPTIONS="-P /var/run/$prog.pid -m 256".
Regards,
Igor.
It seems this happens when we try to set the auth_count back to 0 after a
successful registration is the following line:
$sht(a=>$au::auth_count) = 0;
Nick Raper
Voice Engineer
T +27 (0) 21 710 8400
C +27 (0) 82 777 0855
hymax.co.za <http://www.hymax.co.za/>
<http://www.hymax.co.za/> cid:image001.jpg@01CF3399.D9DDFA50
cid:image006.png@01CF339B.A5608F70
This e-mail and any attached files are intended for the named addressee
only. It contains information which may be confidential and
legally privileged and also protected by copyright. Unless you are the named
addressee (or authorized to receive for the addressee)
you may not copy or use it, or disclose it to anyone else. If you received
it in error please notify the sender immediately and then
delete it from your system. We make every effort to keep our network free
from viruses. However you do need to check this
e-mail and any attachments to it for viruses, as we can take no
responsibility for any computer virus which may be transferred
by way of this e-mail.
From: Nick Raper [mailto:nick.raper@hymax.co.za]
Sent: 24 March 2014 11:57 AM
To: 'sr-users-bounces(a)lists.sip-router.org'
Subject: Registration error setting pvar
Hi,
Can anyone assist with troubleshooting this error? It happens on client
REGISTER requestes. The registration is successful but we get the following
errors:
10(2994) ERROR: <core> [lvalue.c:363]: lval_pvar_assign(): setting pvar
failed
10(2994) ERROR: <core> [lvalue.c:416]: lval_assign(): assignment failed at
pos: (1075,31-1075,31)
version: kamailio 4.1.2 (i386/linux) 6fa599
I am using a modified script and DB from version 3.2.1 as we are looking at
upgrading our current live servers to ver 4.1.2.
I have attached a full debug log of the register.
Regards,
Nick Raper
Voice Engineer
T +27 (0) 21 710 8400
C +27 (0) 82 777 0855
hymax.co.za <http://www.hymax.co.za/>
<http://www.hymax.co.za/> cid:image001.jpg@01CF3399.D9DDFA50
cid:image006.png@01CF339B.A5608F70
This e-mail and any attached files are intended for the named addressee
only. It contains information which may be confidential and
legally privileged and also protected by copyright. Unless you are the named
addressee (or authorized to receive for the addressee)
you may not copy or use it, or disclose it to anyone else. If you received
it in error please notify the sender immediately and then
delete it from your system. We make every effort to keep our network free
from viruses. However you do need to check this
e-mail and any attachments to it for viruses, as we can take no
responsibility for any computer virus which may be transferred
by way of this e-mail.
