Hi i trying to get
htable.dump mytable
via jsonrpc request
{jsonrpc: "2.0",
method: "htable.dump mytable"}
{
"jsonrpc": "2.0",
"error": {
"code": 500,
"message": "Method Not Found"
}
}
But via kamcmd it wroks perfect
Aslo i see that if i will make request withont param (core.version for
example)
IT works fime
How to make request with param?
Hello,
I am facing an issue with kamailio carrierroute.I have a setup where
multiple asterisk is behind a kamailio server.I am able to dispatch the
load by using carrierroute.
Its working perfectly for retail users.But problem is its not working for
wholesale users.I am attaching the dump for wholesale client.
here is a little descrption for the shark:-
192.151.149.102 is the wholesale client ip.
46.166.139.60:4848 is kamailio server.
46.166.139.60:3628 is asterisk server.
when 192.151.149.102 sends invite to 46.166.139.60:4848 [Kamailio] we are
getting 401. [dump2.pcap]
when 192.151.149.102 sends invite to 46.166.139.60:3628 [Direct Asterisk ]
we are getting 200. [dump.pcap]
here is the code i am using for load balancing:-
route[Carrer] {
#!ifdef WITH_CARRIERROUTE
if (!cr_route("default", "default", "$rU", "$rU",
"call_id")) {
xlog("L_ERR", "cr_route failed\n");
exit;
}
#!endif
$avp(s:host)= $rd+":"+$rp;
t_on_failure("1");
if (!t_relay()) {
sl_reply_error();
};
}
failure_route[1] {
revert_uri();
#!ifdef WITH_CARRIERROUTE
if (!cr_next_domain("default", "default", "$rU",
"$avp(s:host)", "$T_reply_code", "$avp(s:domain)"))
{
xlog("L_ERR", "cr_next_domain failed\n");
exit;
}
if (!cr_route("default", "default", "$rU", "$rU",
"call_id")) {
xlog("L_ERR", "cr_route failed\n");
}
t_on_failure("1");
route(NASIR);
exit;
#!endif
$avp(s:host)= $rd+":"+$rp;
if (!t_relay()) {
xlog("L_ERR", "t_relay failed-custom\n");
exit;
};
}
Hi list,
I'm facing a strange behaviour with dialog module and stop event route.
When a BYE request has been receved by Kamailio, no stop event route has
been fired but dialog state go to 5.
My config is following this guide:
http://kb.asipto.com/kamailio:presence:k43-blf
Using dialog_manage on RELAY route, as describe on this guide.
If i set more debug information, i can see dialog has been found and dialog
status incremented :
1(7) DEBUG: <core> [core/udp_server.c:491]: udp_rcv_loop(): received on
udp socket: (106/100/818) [[BYE sip:172.16.74.201:5060;prxroute=1 SIP/2.0
0D 0A Record-Route: <sip:172.16.74.24;r2=on;lr=on;ftag=1;ng]]
1(7) DEBUG: <core> [core/parser/msg_parser.c:604]: parse_msg(): SIP
Request:
1(7) DEBUG: <core> [core/parser/msg_parser.c:606]: parse_msg(): method:
<BYE>
1(7) DEBUG: <core> [core/parser/msg_parser.c:608]: parse_msg(): uri:
<sip:172.16.74.201:5060;prxroute=1>
1(7) DEBUG: <core> [core/parser/msg_parser.c:610]: parse_msg(): version:
<SIP/2.0>
1(7) DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param():
Found param type 232, <branch> =
<z9hG4bKc2c.939fa953ea648059586a7f684fd56b5a.0>; state=16
1(7) DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of
header reached, state=5
1(7) DEBUG: <core> [core/parser/msg_parser.c:492]: parse_headers(): Via
found, flags=2
1(7) DEBUG: <core> [core/parser/msg_parser.c:494]: parse_headers(): this
is the first via
1(7) DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param():
Found param type 235, <rport> = <5060>; state=6
1(7) DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param():
Found param type 232, <branch> = <z9hG4bK-69-1-10>; state=16
1(7) DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of
header reached, state=5
1(7) DEBUG: <core> [core/parser/msg_parser.c:492]: parse_headers(): Via
found, flags=78
1(7) DEBUG: <core> [core/parser/msg_parser.c:505]: parse_headers(): this
is the second via
1(7) DEBUG: <core> [core/parser/parse_addr_spec.c:185]: parse_to_param():
add param: tag=f651e13a-0aac-40d5-b877-1c24497ff87c
1(7) DEBUG: <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec():
end of header reached, state=29
1(7) DEBUG: <core> [core/parser/msg_parser.c:171]: get_hdr_field(): <To>
[87]; uri=[sip:+33975181257@sip.testinfratrunk.vox.fr]
1(7) DEBUG: <core> [core/parser/msg_parser.c:172]: get_hdr_field(): to
body [<sip:+33975181257@sip.testinfratrunk.vox.fr>]
1(7) DEBUG: <core> [core/parser/msg_parser.c:152]: get_hdr_field(): cseq
<CSeq>: <3> <BYE>
1(7) DEBUG: <core> [core/receive.c:232]: receive_msg(): --- received sip
message - request - call-id: [1-69(a)60.0.0.30] - cseq: [3 BYE]
1(7) DEBUG: <core> [core/receive.c:287]: receive_msg(): preparing to run
routing scripts...
1(7) DEBUG: maxfwd [mf_funcs.c:74]: is_maxfwd_present(): value = 69
1(7) DEBUG: <core> [core/parser/parse_addr_spec.c:185]: parse_to_param():
add param: tag=1
1(7) DEBUG: <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec():
end of header reached, state=29
1(7) DEBUG: <core> [core/parser/msg_parser.c:183]: get_hdr_field():
content_length=0
1(7) DEBUG: <core> [core/parser/msg_parser.c:89]: get_hdr_field(): found
end of header
1(7) DEBUG: sanity [sanity_mod.c:256]: w_sanity_check(): sanity checks
result: 1
1(7) NOTICE: <script>: {1 3 BYE 1-69(a)60.0.0.30} Initialisation des
variables.
1(7) DEBUG: tm [t_lookup.c:1018]: t_check_msg(): msg (0x7ffa420727d8) id=2
global id=1 T start=(nil)
1(7) DEBUG: tm [t_lookup.c:476]: t_lookup_request(): start searching:
hash=3116, isACK=0
1(7) DEBUG: tm [t_lookup.c:435]: matching_3261(): RFC3261 transaction
matching failed
1(7) DEBUG: tm [t_lookup.c:659]: t_lookup_request(): no transaction found
1(7) DEBUG: tm [t_lookup.c:1087]: t_check_msg(): msg (0x7ffa420727d8) id=2
global id=2 T end=(nil)
1(7) DEBUG: siputils [checks.c:123]: has_totag(): totag found
1(7) DEBUG: rr [loose.c:113]: find_first_route(): No Route headers found
1(7) DEBUG: rr [loose.c:960]: loose_route(): There is no Route HF
1(7) DEBUG: tm [t_lookup.c:1018]: t_check_msg(): msg (0x7ffa420727d8) id=2
global id=2 T start=(nil)
1(7) DEBUG: tm [t_lookup.c:1094]: t_check_msg(): T previously sought and
not found for msg (0x7ffa420727d8)
1(7) DEBUG: dialog [dlg_hash.c:768]: internal_get_dlg(): ref dlg
0x7ffa327dd588 with 1 -> 3
1(7) DEBUG: dialog [dlg_hash.c:770]: internal_get_dlg(): dialog callid='
1-69(a)60.0.0.30' found on entry 3063, dir=1
1(7) DEBUG: dialog [dlg_profile.c:536]: set_current_dialog(): setting
current dialog [3063:9173]
1(7) DEBUG: dialog [dlg_hash.c:1151]: next_state_dlg(): dialog
0x7ffa327dd588 changed from state 4 to state 5, due event 7 (ref 3)
1(7) DEBUG: dialog [dlg_hash.c:932]: dlg_ref_helper(): ref op on
0x7ffa327dd588 with 1 from dlg_handlers.c:1389
1(7) DEBUG: dialog [dlg_hash.c:936]: dlg_ref_helper(): ref dlg
0x7ffa327dd588 with 1 -> 4
1(7) DEBUG: dialog [dlg_handlers.c:1400]: dlg_onroute(): BYE successfully
processed
Do you have any hints concerning this issue ? Is it a bug or a config part
is missing ?
Thanks in advance,
Best regards.
Hello All
i'm facing strange behavior with Zoiper Client only in an IMS Kamailio
based system.
in IMS call scenario (ims to ims) a lot of Loop Detect Msgs Appeared in the
sip log.
while other clients like Acrobits did not occurred
i'm using TCP protocol and Wireshark shows a lot of (TCP Re-transmission
and TCP ACKed unseen Segment)
Any Suggestion
Thanks !
Hi,
At the moment, I'm trying to replace MySQL by MariaDB on my Kamailio server
(5.0.1) . In previous post I have been told that Kamailio supports MariaDB
and there is no special module to load.
This work is done on a new server running RHEL 7.4 and MariaDB 10.2.14 that
is installed under /opt/mysql/na/10.2.14 folder.
I encounter different problem:
- Without changing anything in the kamailio script, kamailio failed
to find the libmysqlclient.so.18 library.
- So I thought that I could get rid of the above error by changing
the MODULEPATH in the Kamailio-local.cfg as follows :
MODULEPATH="/usr/lib64/kamailio/modules/:/opt/mysql/na/10.2.14/lib64/"
But with this, I get 2 problem:
The kamailio.log that was written in a /opt/log/Kamailio folder is no longer
updated.
I can only find the errors in the /var/log/messages file:
May 23 11:19:19 vm-siprouter74 systemd: Starting SYSV: Kamailio is a fast,
reliable and flexible SIP Server....
May 23 11:19:19 vm-siprouter74 kamailio: Not starting : invalid
configuration file!
May 23 11:19:19 vm-siprouter74 kamailio: 0(3328) DEBUG: <core>
[core/cfg.lex:1822]: pp_define_get(): ### returning define ID
[DEFINE_LOG_FACILITY] value [LOG_LOCAL0]
May 23 11:19:19 vm-siprouter74 kamailio: 0(3328) DEBUG: <core>
[core/cfg.lex:1822]: pp_define_get(): ### returning define ID [LOCAL_LISTEN]
value [udp:129.227.82.109:5060]
May 23 11:19:19 vm-siprouter74 kamailio: 0(3328) DEBUG: <core>
[core/cfg.lex:1822]: pp_define_get(): ### returning define ID
[LOCAL_LISTEN_2] value [udp:127.0.0.1:5060]
May 23 11:19:19 vm-siprouter74 kamailio: 0(3328) DEBUG: <core>
[core/cfg.lex:1822]: pp_define_get(): ### returning define ID [MODULEPATH]
value ["/usr/lib64/kamailio/modules/:/opt/mysql/na/10.2.14/lib64/"]
May 23 11:19:19 vm-siprouter74 kamailio: 0(3328) DEBUG: <core>
[core/cfg.y:1632]: yyparse(): loading modules under
/usr/lib64/kamailio/modules/:/opt/mysql/na/10.2.14/lib64/
May 23 11:19:19 vm-siprouter74 kamailio: 0(3328) DEBUG: <core>
[core/cfg.y:1613]: yyparse(): loading module db_mysql.so
May 23 11:19:19 vm-siprouter74 kamailio: 0(3328) DEBUG: <core>
[core/sr_module.c:575]: load_module(): trying to load
</usr/lib64/kamailio/modules/db_mysql.so>
May 23 11:19:19 vm-siprouter74 kamailio: 0(3328) ERROR: <core>
[core/sr_module.c:582]: load_module(): could not open module
</usr/lib64/kamailio/modules/db_mysql.so>: libmysqlclient.so.18: cannot open
shared object file: No such file or directory
May 23 11:19:19 vm-siprouter74 kamailio: 0(3328) CRITICAL: <core>
[core/cfg.y:3401]: yyerror_at(): parse error in config file
//etc/kamailio/kamailio.cfg, line 191, column 12-24: failed to load module
May 23 11:19:19 vm-siprouter74 kamailio: 0(3328) DEBUG: <core>
[core/cfg.y:1613]: yyparse(): loading module jsonrpcs.so
May 23 11:19:19 vm-siprouter74 kamailio: 0(3328) DEBUG: <core>
[core/sr_module.c:575]: load_module(): trying to load
</usr/lib64/kamailio/modules/jsonrpcs.so>
To work around the problem we have created 2 symbol links:
<<< ln -s /opt/mysql/na/10.2.14/lib64/libmysqlclient.so.18.0.0
/usr/lib64/libmysqlclient.so.18 >>> the libmysqlclient error
<<< ln -s /myqdata/mysiprdb/data/my.cnf /etc/my.cnf >>> to fix the issue to
open the db
It seems that kamailio is always looking for the my.cnf in the /etc/
directory.
My concern are to share this job with people who have much more experience
with Kamailio.
I would like to know
- If the different workaround (ln) makes sense to you or is there
better change to do
- How to explain the logging issue when changing the modulepath
variable
- Is it true that kamailio is always looking for the my.cnf in the
/etc/ directory?
Any thoughts are welcome.
Thanks in advance.
Cordialement.
Patrick GINHOUX
Hi!
Is http://www.asipto.com/pub/kamailio-devel-guide/ still holds actual info?
Cause it’s mostly for 3.3 version, and now is 5.1
And where to read, except source code of course, about how to develop modules for Kamailio?
Regards, Igor
Greetings,
Is there any method on Kamailio that automatically rewrites the headers in
its compact form ?
I know how i can do it by re-writing each of the eligible headers, but i
was wondering if there is any way to do it automatically.
Thanks
Hey there,
I am currently using the UAC module to maintain remote registrations. I am just curious if it is possible to register new users immediately rather than waiting for reg_timer_interval? I am not seeing any functionality like that but just wondering if I am missing something or if it would be possible to add in. For example an RPC command that takes a key and instantly registers that user.
Thanks,
Greg
________________________________
Hello,
A kamailio.org server maintenance work will be done today at 18:00 CEST.
There will be some minutes of downtime (should be less than 5') of the
following main services: website (including the wiki) and mailing lists.
Regards,
Oriol.
