I would like the URI transformations to be more generic so one can pick up the URI scheme, like HTTP: or TEL:
Just an idea
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/592
ENV: Debian 8
So on most Linux systems the /var/run folder is a tmpfs and after which clears after each reboot
As I try to start up kamailio after a reboot through kamctl I get the following error.
"ERROR: PID file /var/run/kamailio.pid does not exist -- Kamailio start failed"
Because kamailio does not have the permission to write to the /var/run folder as the kamailio user.
Would it be possible to add in the "kamctl" code a section where the SPECIFIED PID LOCATION (/var/run/kamailio) is checked and if it does not exist create it as the root user and chown it to the SPECIFIED USER (kamailio)? The way I have patched it for now is to create a init script that creates a /var/run/kamailio folder and chmods it to kamailio:kamailio
Thanks everyone!
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/231
I'm currently using version 4.4.2 and am having trouble trying to reset the statistics in the TMX module. According to its documentation, all statistics except “inuse_transactions” can be reset.
Checking the tmx_mod.c files for the statistics definition, I saw that the STAT_NO_RESET flag wasn't used for any statistic listed there (which seems odd because I think it should have been set for the inuse_transactions statistic):
`static stat_export_t mod_stats[] = {
{"UAS_transactions", STAT_IS_FUNC, (stat_var**)tmx_stats_uas_trans },
{"UAC_transactions", STAT_IS_FUNC, (stat_var**)tmx_stats_uac_trans },
{"2xx_transactions", STAT_IS_FUNC, (stat_var**)tmx_stats_trans_2xx },
{"3xx_transactions", STAT_IS_FUNC, (stat_var**)tmx_stats_trans_3xx },
{"4xx_transactions", STAT_IS_FUNC, (stat_var**)tmx_stats_trans_4xx },
{"5xx_transactions", STAT_IS_FUNC, (stat_var**)tmx_stats_trans_5xx },
{"6xx_transactions", STAT_IS_FUNC, (stat_var**)tmx_stats_trans_6xx },
{"inuse_transactions", STAT_IS_FUNC, (stat_var**)tmx_stats_trans_inuse },
{"active_transactions", STAT_IS_FUNC, (stat_var**)tmx_stats_trans_active},
{"rpl_received", STAT_IS_FUNC, (stat_var**)tmx_stats_rcv_rpls },
{"rpl_absorbed", STAT_IS_FUNC, (stat_var**)tmx_stats_abs_rpls },
{"rpl_generated", STAT_IS_FUNC, (stat_var**)tmx_stats_rld_loc_rpls},
{"rpl_relayed", STAT_IS_FUNC, (stat_var**)tmx_stats_rld_rcv_rpls},
{"rpl_sent", STAT_IS_FUNC, (stat_var**)tmx_stats_rld_tot_rpls},
{0, 0, 0}
};`
All seems ok, but when I try to reset the stats, the command simply doesn't work. The values remain unaltered. The clear command doesn't work either, it just returns the current values.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/820
Hello,
As you will see I have merged my branch back into master.
These changes add a new event route [tm:branch-failure] to the tm module
which is run when any failure response is received on a transaction.
The event_route uses a new route type BRANCH_ROUTE which limits the
functions that can be run in the route.
The functions t_check_status(), t_next_contact_flow(), t_relay() and
unregister() can be used in this route.
A new pv $T_reply_ruid is accessible in this route which can be used to
unregister a single contact entry.
The following example route can be used on a registrar to handle failed
or invalid flows:
event_route[tm:branch-failure] {
xlog("L_INFO", "event_route[tm:branch-failure]\n");
if (t_check_status("430|403")) {
if (!unregister("location", "$tu", "$T_reply_ruid"))
{
xlog("L_WARN", "failed to unregister $tu with
ruid $T_reply_ruid\n");
}
if (!t_next_contact_flow())
{
xlog("L_INFO", "No more flows\n");
}
else
{
xlog("L_INFO", "Next flow\n");
t_relay();
}
}
}
Any bugs, memory leaks etc. let me know!
Hugh
--
Hugh Waite
Principal Design Engineer
Crocodile RCS Ltd.
```
Jun 6 14:38:43 spce lb[27903]: : tls [tls_init.c:557]: init_tls_h(): ERROR: tls: init_tls_h: installed openssl library version is too different from the library the Kamailio tls module was compiled with: installed "OpenSSL 1.0.1t 3 May 2016" (0x1000114f), compiled "OpenSSL 1.0.1k 8 Jan 2015" (0x100010bf).#012 Please make sure a compatible version is used (tls_force_run in kamailio.cfg will override this check)
Jun 6 14:38:43 spce lb[27903]: CRITICAL: <core> [main.c:2577]: main(): could not initialize tls, exiting...
```
openssl was upgraded from 1.0.1k-3+deb8u5 to 1.0.1t-1+deb8u2
This seems not to work properly
https://github.com/kamailio/kamailio/blob/master/modules/tls/tls_init.c#L54…
```
#if OPENSSL_VERSION_NUMBER < 0x00907000L
WARN("You are using an old version of OpenSSL (< 0.9.7). Upgrade!\n");
#endif
ssl_version=SSLeay();
/* check if version have the same major minor and fix level
* (e.g. 0.9.8a & 0.9.8c are ok, but 0.9.8 and 0.9.9x are not) */
if ((ssl_version>>8)!=(OPENSSL_VERSION_NUMBER>>8)){
LOG(L_CRIT, "ERROR: tls: init_tls_h: installed openssl library "
"version is too different from the library the Kamailio tls module "
"was compiled with: installed \"%s\" (0x%08lx), compiled "
"\"%s\" (0x%08lx).\n"
" Please make sure a compatible version is used"
" (tls_force_run in kamailio.cfg will override this check)\n",
SSLeay_version(SSLEAY_VERSION), ssl_version,
OPENSSL_VERSION_TEXT, (long)OPENSSL_VERSION_NUMBER);
if (cfg_get(tls, tls_cfg, force_run))
LOG(L_WARN, "tls: init_tls_h: tls_force_run turned on, ignoring "
" openssl version mismatch\n");
else
return -1; /* safer to exit */
}
```
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/662
- updating code base to actual state.
- adding repliation for DLG_STATE_EARLY to prevent hanging up unconfirmed dialogs and its infinite replication.
- fixing dialog removal on peers to prevent die on timeout and possible infinite replication.
- fixing dialog removal on peers when master node cleanly restart.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/831
-- Commit Summary --
* Adding dialog replication via DMQ
-- File Changes --
M modules/dialog/dialog.c (14)
M modules/dialog/dlg_db_handler.c (6)
A modules/dialog/dlg_dmq.c (604)
A modules/dialog/dlg_dmq.h (48)
M modules/dialog/dlg_handlers.c (67)
M modules/dialog/dlg_hash.c (8)
M modules/dialog/dlg_hash.h (2)
M modules/dialog/dlg_profile.c (2)
M modules/dialog/doc/dialog_admin.xml (23)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/831.patchhttps://github.com/kamailio/kamailio/pull/831.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/831