Hi All
In 4.2.0 Kamailio (S-CSCF), when I try to register an IMS endpoint, I get
403 from P-CSCSF.
When I checked the error logs, SCSCF logs look as below
1(5455) INFO: ims_auth [authorize.c:824]: authenticate(): uri=sip:
group4-imslab11.in nonce=b9eec0ad9d6d186408541d8a23a7c7a5
response=df89adebbf28f25d38d2f993f7cde033 qop= nc= cnonce= hbody=
1(5455) INFO: ims_auth [authorize.c:872]: authenticate(): UE said:
df89adebbf28f25d38d2f993f7cde033 and we expect
df89adebbf28f25d38d2f993f7cde033 ha1 599fb074cf189867eed06f3b6ebc0b97
(REGISTER)
1(5455) INFO: ims_registrar_scscf [cxdx_sar.c:79]: create_return_code():
created AVP successfully : [saa_return_code] - [-2]
12(5466) INFO: ims_registrar_scscf [cxdx_avp.c:138]: cxdx_get_avp():
cxdx_get_experimental_result_code: Failed finding avp
12(5466) INFO: ims_registrar_scscf [cxdx_avp.c:138]: cxdx_get_avp():
cxdx_get_charging_info: Failed finding avp
I have added an user necs_0 in hss_db, so why I get below error.
Please let me know what is missed here.
Is S-CSCF not able to contact HSS ??
Best Regards
kamal
version: kamailio 4.1.6 (x86_64/linux) 58746c
I looked through 4.1 commits but didn't catch anything that looked
like a fix for this but it's a very real possibility this is a
duplicate (again).
Any thoughts (backtrace attached)? Thanks!
--
Kristian Kielhofner
Hello,
I have recently moved some traffic to kamailio-4.2 (installed on a seperate
box) and it crashes quite often. Below is the backtrace of the core files -
<CORE#1>
(gdb) bt
#0 0x00000033d8c32635 in raise () from /lib64/libc.so.6
#1 0x00000033d8c33e15 in abort () from /lib64/libc.so.6
#2 0x000000000049add5 in sig_alarm_abort (signo=14) at main.c:689
#3 <signal handler called>
#4 0x00000033d8ce50c7 in syscall () from /lib64/libc.so.6
#5 0x00007f7ca2ea0a1e in futex_get (lock=0x7f7ca3334388) at
../../mem/../futexlock.h:110
#6 0x00007f7ca2ea1e99 in remove_dialog_timer (tl=0x7f7ca3384c98) at
dlg_timer.c:168
#7 0x00007f7ca2e83e9b in destroy_dlg (dlg=0x7f7ca3384c40) at dlg_hash.c:357
#8 0x00007f7ca2e84e19 in destroy_dlg_table () at dlg_hash.c:438
#9 0x00007f7ca2e50b89 in mod_destroy () at dialog.c:773
#10 0x000000000058dfd5 in destroy_modules () at sr_module.c:818
#11 0x0000000000499ad3 in cleanup (show_status=1) at main.c:564
#12 0x000000000049b096 in shutdown_children (sig=15, show_status=1) at
main.c:706
#13 0x000000000049d66c in handle_sigs () at main.c:797
#14 0x00000000004a4e57 in main_loop () at main.c:1757
#15 0x00000000004a8a43 in main (argc=2, argv=0x7fff58d21368) at main.c:2609
(gdb) quit
<CORE#2>
(gdb) bt
#0 0x00007f7ca2ea22d7 in update_dlg_timer (tl=0x58, timeout=10) at
dlg_timer.c:203
#1 0x00007f7ca2e824f3 in dlg_clean_run (ti=44865910) at dlg_hash.c:253
#2 0x00007f7ca2e566fc in dlg_clean_timer_exec (ticks=44865910, param=0x0)
at dialog.c:1250
#3 0x00000000005f93e8 in fork_sync_timer (child_id=-1, desc=0x7f7ca2eb3a71
"Dialog Clean Timer", make_sock=1, f=0x7f7ca2e566e3 <dlg_clean_timer_exec>,
param=0x0,
interval=90) at timer_proc.c:232
#4 0x00007f7ca2e50476 in child_init (rank=0) at dialog.c:730
#5 0x000000000058e385 in init_mod_child (m=0x7f7ca8c09eb8, rank=0) at
sr_module.c:930
#6 0x000000000058e0c0 in init_mod_child (m=0x7f7ca8c0b000, rank=0) at
sr_module.c:927
#7 0x000000000058e68f in init_child (rank=0) at sr_module.c:957
#8 0x00000000004a435c in main_loop () at main.c:1705
#9 0x00000000004a8a43 in main (argc=2, argv=0x7fff58d21368) at main.c:2609
(gdb) quit
kamailio -v
version: kamailio 4.2.0-pre0 (x86_64/linux) a78764-dirty
flags: STATS: Off, USE_TCP, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST,
DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, DBG_F_MALLOC,
USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER,
USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: a78764 -dirty
Kindly let me know which version to move.
--
Warm Regds.
MathuRahul
--
Warm Regds.
MathuRahul
Hi Dears,
I'm trying to configure Kamailio as SBC in multi home mode for Asterisk by
authenticating the inbound SIP registration requests,i'm following this
tutorial
http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb
to achieve this goal. i have modified the necessary changes like the
Asterisk DB URL and the SIP table name and Username and password column and
verified the Mysql connection.
My topology like this Asterisk (192.168.100.10)
<----Internal:192.168.100.1---->Kamailio<---External:192.168.50.1-----> SIP
Phone (192.168.50.2)
But when trying to register a SIP phone Kamailio generates these error
messages
Nov 22 17:19:20 debian /usr/local/sbin/kamailio[6434]: ERROR: db_mysql
[km_dbase.c:122]: db_mysql_submit_query(): driver error on query: Unknown
column 'secret' in 'field list'
Nov 22 17:19:20 debian /usr/local/sbin/kamailio[6434]: ERROR: <core>
[db_query.c:132]: db_do_query_internal(): error while submitting query
Nov 22 17:19:20 debian /usr/local/sbin/kamailio[6434]: ERROR: auth_db
[authorize.c:175]: get_ha1(): failed to query database
The Auth_DB Params in the configuration file is as follows.
# ----- auth_db params -----
#!ifdef WITH_AUTH
modparam("auth_db", "calculate_ha1", yes)
modparam("auth_db", "load_credentials", "")
#!ifdef WITH_ASTERISK
modparam("auth_db", "user_column", "account")
modparam("auth_db", "password_column", "secret")
modparam("auth_db", "db_url", DBASTURL)
modparam("auth_db", "version_table", 0)
#!else
modparam("auth_db", "db_url", DBURL)
modparam("auth_db", "password_column", "password")
modparam("auth_db", "use_domain", MULTIDOMAIN)
#!endif
I tried also to give the Auth_DB module all the paramaters like this but
still receiving the same error ! So any ideas about the cause of the
problem and how to solve it please ?
# ----- auth_db params -----
#!ifdef WITH_AUTH
modparam("auth_db", "user_column", "account")
modparam("auth_db", "password_column", "secret")
modparam("auth_db", "db_url", "mysql://
sipuser:sippassword@192.168.100.10/asterisk")
modparam("auth_db", "calculate_ha1", yes)
modparam("auth_db", "load_credentials", "")
#!ifdef WITH_ASTERISK
modparam("auth_db", "user_column", "account")
modparam("auth_db", "password_column", "secret")
modparam("auth_db", "db_url", "mysql://
sipuser:sippassword@192.168.100.10/asterisk")
modparam("auth_db", "version_table", 0)
#!else
modparam("auth_db", "db_url", "db_url","mysql://
sipuser:sippassword@192.168.100.10/asterisk")
modparam("auth_db", "password_column", "secret")
modparam("auth_db", "user_column", "account")
modparam("auth_db", "use_domain", MULTIDOMAIN)
#!endif
Hi All,
I am testing SIP messages through the proxy from one client to another and
the sender specifies TCP as the transport but Kamailio seems to overwrite
this and chooses UDP (TCP is specified in the contact header).
The receivers are manually registered using kamctl ul add so i am not sure
if this is forcing UDP or something else - I have redirected the messages
to wireshark and attached an example of Kamailio adding its VIA headers but
specifying UDP (taken from destination).
Basically I am getting TCP to Proxy the UDP from Proxy to Dest?
Thanks
Andrew
[image: Inline images 1]
Dear Kamailio Developers:
Hi.
I have some questions about kamailio, and want to gain some suggestions from you.
1、The 4 UDP child processes are using system resources(CPU、memory), but they are using only one CPU core(I use 8 core CPU). Why?
2、The ablity of handling the Concurrency is alike, no matter how many UDP child processes I use. Why? And what's the effection of the other UDP child processes?
彭学金
186-2708-0286
技术部 开发工程师
武汉九午科技有限公司
武汉市洪山区光谷大道国际企业中心锦丰楼A座405室
Tel:(027)87108832
Hello,
Since I done the upgrade of Kamailio into 4.2.0, there are, at least, one
new case where the RTPProxy is launched.
When I got an INVITE from my PSTN Gateway, for unknown reason (and not for
all calls), Record-Route is append with nat=yes. I looked into an old trace
and this behaviour didn't exist.
What could have changed that can explain this?
Regards,
Igor.
Hi All
We are experiencing an odd problem with 1 way audio in about %6-%8 of our
calls.
It seems to me that what is happening is that our kamailio installation
(using rtpengine) is some times ignoring the c= attribute that the carrier
is sending us, and sending our audio instead to either address in the
carriers o= attribute, or just to the same address we sent our sip invite
too.
We have looked at hundreds of calls and haven't found a reliable pattern
why this happens some times and not others. It really happens in a lot of
different scenarios with lots of different carriers and differently
formatted SDP packets.
I was wondering if any one had an idea where to start for a solution, or a
way to make rtpengine always send audio to the ip in the c= attribute we
are receiving from the carrier.
I haven't been able to find anything so far.
Thank you much for any assistance.
All the best.
Will
lets say that invite is parallel forked to two contacts. if the call is
answered, i would like to set in reply route an accounting avp that
contains the request uri of answering branch. i have tried $T_req($ru),
but that gives the original request uri. any suggestions?
-- juha