Hello,
Trying to do priority load balancing (8) but i'm getting an error `unable
to update destination load - classic dispatching` anyone knows why?
i've got
```modparam("dispatcher", "db_url", DBURL)
modparam("dispatcher", "table_name", "dispatcher")
modparam("dispatcher", "flags", 2)
modparam("dispatcher", "dst_avp", "$avp(AVP_DST)")
modparam("dispatcher", "grp_avp", "$avp(AVP_GRP)")
modparam("dispatcher", "cnt_avp", "$avp(AVP_CNT)")
modparam("dispatcher", "dstid_avp", "$avp(dsdstid)")
modparam("dispatcher", "attrs_avp", "$avp(dsattrs)")```
Looking at the code, dstid_avp would be null, but not sure why?
I have set in the table the priorities as 10 for 2 gws (edited)
Regards,
David Villasmil
email: david.villasmil.work(a)gmail.com
phone: +34669448337
ᐧ
Hi, I just installed Kamailio 5.1.6 on Ubuntu 18.04. Starting Kamailio with the default config will give us the following in the log. Is this normal? Is there a way to fix this issue? Thanks, AL Nov 15 14:01:59 lab-proxy03 kamailio[13544]: * Stopping Kamailio SIP Server: kamailio Nov 15 14:01:59 lab-proxy03 /usr/local/sbin/kamailio[5182]: NOTICE: <core> [main.c:692]: handle_sigs(): Thank you for flying kamailio!!! Nov 15 14:01:59 lab-proxy03 /usr/local/sbin/kamailio[5213]: INFO: <core> [main.c:819]: sig_usr(): signal 15 received Nov 15 14:01:59 lab-proxy03 /usr/local/sbin/kamailio[5212]: INFO: <core> [main.c:819]: sig_usr(): signal 15 received .... Nov 15 14:01:59 lab-proxy03 /usr/local/sbin/kamailio[5182]: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Nov 15 14:02:00 lab-proxy03 kamailio[13544]: ...done. Nov 15 14:02:00 lab-proxy03 kamailio[13556]: * Starting Kamailio SIP Server: kamailio Nov 15 14:02:00 lab-proxy03 kamailio: INFO: <core> [core/sctp_core.c:74]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Nov 15 14:02:00 lab-proxy03 kamailio: INFO: <core> [core/tcp_main.c:4721]: init_tcp(): using epoll_lt as the io watch method (auto detected) .... Nov 15 14:02:00 lab-proxy03 /usr/local/sbin/kamailio[13596]: INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded Nov 15 14:02:00 lab-proxy03 /usr/local/sbin/kamailio[13596]: INFO: rr [rr_mod.c:175]: mod_init(): outbound module not available Nov 15 14:02:00 lab-proxy03 /usr/local/sbin/kamailio[13596]: INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Nov 15 14:02:00 lab-proxy03 /usr/local/sbin/kamailio[13596]: INFO: <core> [core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Nov 15 14:02:00 lab-proxy03 /usr/local/sbin/kamailio[13596]: INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Nov 15 14:02:00 lab-proxy03 /usr/local/sbin/kamailio[13596]: INFO: <core> [core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Nov 15 14:02:00 lab-proxy03 /usr/local/sbin/kamailio[13618]: INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/13618 Nov 15 14:02:00 lab-proxy03 /usr/local/sbin/kamailio[13619]: INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) Nov 15 14:02:00 lab-proxy03 kamailio[13556]: ...done.
Hi,
we are using kamailio 5.1 with siptrace module in trace_mode on. Everything works perfect except that option pings from nathelper module do not get duplicated. Is there a reason for that?
Thanks, Roman
Hi all,
I am trying to implement Diameter charging with Kamailio. I am following
below tutorial
https://www.kamailio.org/events/2016-KamailioWorld/Day2/15-Carsten.Bock-Dia…
But whenever I try to do the Ro_CCR from the INVITE block, Kamailio is
crashing and generating the core dump. I am new to diameter. I might be
doing something wrong here.
please someone help me here.
Please find the *diameter.xml* and *Diameter_core_dump_full_debug.txt* file.
diameter.xml
<http://sip-router.1086192.n5.nabble.com/file/t6374/diameter.xml>
Diameter_core_dump_full_Debug.txt
<http://sip-router.1086192.n5.nabble.com/file/t6374/Diameter_core_dump_full_…>
Here is my kamailio.cfg :
loadmodule "cdp"
loadmodule "cdp_avp"
loadmodule "ims_charging"
loadmodule "ims_dialog"
modparam("cdp","config_file","/etc/kamailio/diameter.xml")
modparam("cdp", "debug_heavy", 1)
# ----- ims_diameter_ro params -----
#modparam("ims_charging", "single_ro_session_per_dialog", 1)
modparam("ims_charging", "origin_host", "10.195.0.38");
modparam("ims_charging", "origin_realm", "10.195.0.38");
modparam("ims_charging", "destination_realm", "mydomain.com");
modparam("ims_charging","interim_update_credits",30);
modparam("ims_charging","timer_buffer",5);
# -- ims_dialog params --
modparam("ims_dialog", "dlg_flag", 8)
While starting the kamailio, i am getting following errors:
Nov 11 11:40:03 ip-10-195-0-38 /usr/local/sbin/kamailio[25653]: ERROR: cdp
[peerstatemachine.c:675]: add_peer_application(): Too many applications for
this peer (max 0), not adding Application 4:0.
Before crashing kamailio showing following error:
Nov 11 11:39:49 ip-10-195-0-38 /usr/local/sbin/kamailio[25571]: INFO: {1
18325 INVITE Nf6-dl2WeXF.LJhXotiRsuMhijsNx45o} <script>: Entered into INVITE
Block
Nov 11 11:39:49 ip-10-195-0-38 /usr/local/sbin/kamailio[25571]: ERROR: {1
18325 INVITE Nf6-dl2WeXF.LJhXotiRsuMhijsNx45o} ims_dialog
[dlg_handlers.c:264]: dlg_get_iuid_shm_clone(): ***** Requesting 8
Nov 11 11:39:49 ip-10-195-0-38 /usr/local/sbin/kamailio[25571]: CRITICAL: {1
18325 INVITE Nf6-dl2WeXF.LJhXotiRsuMhijsNx45o} <core>
[core/mem/q_malloc.c:144]: qm_debug_check_frag(): BUG: qm: prev. fragm. tail
overwritten(0, abcdefed)[0x7f467d438768:0x7f467d4387a0]! Memory allocator
was called from cdp: diameter_avp.c:157. Fragment marked by cdp:
peerstatemachine.c:602. Exec from core/mem/q_malloc.c:384.
Nov 11 11:39:49 ip-10-195-0-38 /usr/local/sbin/kamailio[25599]: CRITICAL:
<core> [core/pass_fd.c:277]: receive_fd(): EOF on 16
Nov 11 11:39:52 ip-10-195-0-38 /usr/local/sbin/kamailio[25567]: ALERT:
<core> [main.c:740]: handle_sigs(): child process 25571 exited by a signal 6
Nov 11 11:39:52 ip-10-195-0-38 /usr/local/sbin/kamailio[25567]: ALERT:
<core> [main.c:743]: handle_sigs(): core was generated
Nov 11 11:39:52 ip-10-195-0-38 /usr/local/sbin/kamailio[25567]: INFO: <core>
[main.c:766]: handle_sigs(): terminating due to SIGCHLD
Thanks you in Advance,
Venkey
--
Sent from: http://sip-router.1086192.n5.nabble.com/Users-f3.html
Hi,
Is it possible using topos module without db support?
I'm trying to use topos module with sqlite db backend, but I have any
concurrency problems during write procedure (I use WALL pragma).
When execute speed calls traffic sqlite emits an error trace telling
it's locked.
Is it possible to use a sort of hash tabel to save topos informations
and don't use the db?
Best regards,
Giuseppe
Hi,
We are running the old release of Kamailio 3.3.7 and getting the following notice log:
kamailio: NOTICE: <core> [sr_module.c:627]: /usr/local/lib64/kamailio/modules_k/perl.so: exports dlflags interface is deprecated and it will not be supported in newer versions; consider using mod_register() instead
Is there a way to fix this issue on the same Kamailio3.3.7 code?
Thanks,
AL
Hello,
I migrated from Kamailio 3.0.3 to Kamailio 5.1.4. and have two questions
about the execution sequence of the Request_Route.
The following condition trys to authenticate the first INVITE or REGISTER
request which normally does not have the Authorization Header:
route (auth)
..
..
..
route[auth]{
if ( !proxy_authorize("myrealm", "subscriber") ) {
proxy_challenge("myrealm", "0");
sl_reply_error();
exit;
};
return;
}
For sure the Return Code of "proxy_authorize" will not be one (1) at the
beginneing, so the proxy_challenge() will generate the "407 Proxy
Authentication Required" request and the agent will send the INVITE or the
REGISTER again with the Authorization-Header and the call or the
registration attempt succeeds. During my observation to the new returned
codes (values) of both proxy_authorize() and proxy_challenge() in Kamailio
5.1.4, I noticed the following differnet execution sequence of this
"Request_Route".
at Kamailio 3.0.3, and exactly after the proxy_challenge("myrealm", "0")
command was executed, no more commands were excuted as if it jumped out of
the if statement, and the proxy was wating for the new INVITE or REGISTER.
Hence the sl_reply_error() did not send any error reply. I wrote several
logging commad before and after the proxy_challenge("myrealm", "0"), so I
am pretty sure that the proxy_challenge("myrealm", "0") is last excuted
command to be excuted here.
at Kamailio 5.1.4, the behaviour was more logical and the proxy executes
commands which come under the proxy_challenge("myrealm", "0") like logging
commands or sl_reply_error() which generates usually the error reply " 500
I'm terribly sorry, server error occurred".
My first question is: May somebody explain this different behavior?
My second Question: assume that the agent will send a wrong credentials and
response, does the proxy_challenge("myrealm", "0") function terminate this
dialouge with 401 Unauthorized Error or I must add the following "if
condition" afterwards:
if ( !proxy_authorize("myrealm", "subscriber") ) {
proxy_challenge("myrealm", "0");
if (!$rc){
sl_reply_error(); '#### or I will be more
specific sl_send_reply (code, reason)
}
exit;
};
Thanks and best regards
Abdulaziz Alghosh