Currently i am trying to test mongodb for usrloc module of kamailio.
As expected kamailio is saving the contacts on DB.
However i am encountering a problem that the nathelper does not ping the registered contact on mongodb but when mysql is used it is ok even if ping_nated_only is set to 0.
If mysql:
```
modparam("usrloc", "db_url", DBURL)
modparam("usrloc", "db_mode", 3)
modparam("usrloc", "use_domain", 0)
modparam("usrloc", "timer_interval", 60)
modparam("usrloc", "db_ops_ruid", 1)
modparam("nathelper", "natping_interval", 30)
modparam("nathelper", "ping_nated_only", 0)
modparam("nathelper", "sipping_bflag", 7)
modparam("nathelper", "sipping_from", "sip:pinger@kamailio.org")
```
if mongodb
```
modparam("usrloc", "db_url", MONGODBURL)
modparam("usrloc", "db_mode", 3)
modparam("usrloc", "use_domain", 0)
modparam("usrloc", "timer_interval", 60)
modparam("usrloc", "db_insert_null", 1)
modparam("usrloc", "db_ops_ruid", 1)
modparam("nathelper", "natping_interval", 30)
modparam("nathelper", "ping_nated_only", 0)
modparam("nathelper", "sipping_bflag", 7)
modparam("nathelper", "sipping_from", "sip:pinger@kamailio.org")
```
```
version: kamailio 4.4.5 (x86_64/linux) f98162
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, 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 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: f98162
compiled on 08:56:05 Jan 10 2019 with gcc 4.6.3
```
Ah by the way only usrloc table is using mongodb, the rest of the module is using mysql, for testing only.
Can you advice if i am missing something?
Regards,
--
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/1805
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for feature requests.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
If you submit a feature request (or enhancement) add the description of what you would like to be added.
If there is no content to be filled in a section, the entire section can be removed.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment).
-->
### Description
Enable dialog module to user choose between INVITE or OPTIONS on send Re-INVITE on keep-alive
### Expected behavior
Make the dialog keep-alive through INVITE or OPTIONS. A user choice.
### Possible Solutions
In function dlg_send_ka of dlg_req_within.c:445, provide an option to choose the value from module config var, pv value, dlg flag, etc.
```
File: dlg_req_within.c
435 /* send keep-alive
436 * dlg - pointer to a struct dlg_cell
437 * dir - direction: the request will be sent to:
438 * DLG_CALLER_LEG (0): caller
439 * DLG_CALLEE_LEG (1): callee
440 */
441 int dlg_send_ka(dlg_cell_t *dlg, int dir)
442 {
443 uac_req_t uac_r;
444 dlg_t* di;
445 str met = {"INVITE", 6};
446 int result;
447 dlg_iuid_t *iuid = NULL;
```
### Additional Information
Just for local tests, i changed dlg_req_within.c:445 from {"OPTIONS",7} to {"INVITE",6} and worked like a charm. I don't know if this change will affect other parts of kamailio.
Let me know if this change affect something else.
Thanks.
--
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/1876
<!-- Kamailio Pull Request Template -->
<!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable branch
- backports to stable branches must be done with 'git cherry-pick -x ...'
- code is contributed under BSD for core and main components (tm, sl, auth, tls)
- code is contributed GPLv2 or a compatible license for the other components
- GPL code is contributed with OpenSSL licensing exception
-->
#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list -->
- [X] Commit message has the format required by CONTRIBUTING guide
- [X] Commits are split per component (core, individual modules, libs, utils, ...)
- [X] Each component has a single commit (if not, squash them into one commit)
- [X] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [X] Small bug fix (non-breaking change which fixes an issue)
- [X] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
<!-- Go over all points below, and after creating the PR, tick the checkboxes that apply -->
- [X] PR should be backported to stable branches
- [X] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
- added a worker_id for timer routines. when using rtimer in script with mode=4 there's no way to know which of the workers is in use. this is useful for db queries based on slot
- fixed {uri.tosocket} transformation
- added t_release_transaction to tm api
- fixed xavp_clone_level_nodata
- add sockinfo to $subs
- increase `MAX_DEFINES` as we run out of `defines`
Note: please use rebase instead of merge for this PR
to backport:
- https://github.com/kamailio/kamailio/commit/eea9c5f72b73df9c3d898cff18dced6…
- https://github.com/kamailio/kamailio/commit/e3ed896d80171feba78d3292484a09f…
- https://github.com/kamailio/kamailio/commit/b4696169e8b464da01774b1e40af677…
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1882
-- Commit Summary --
* core: allow a worker id in timer routines
* rtimer: use timer worker id
* pv: use parsed uri to compute tosocket
* tm: add t_release_transaction to api
* core: free resources in xavp_clone_level_nodata
* presence: add sockinfo to $subs
* core: increase max_defines from 256 to 512
-- File Changes --
M src/core/cfg.lex (4)
M src/core/timer.h (2)
M src/core/timer_proc.c (43)
M src/core/timer_proc.h (4)
M src/core/xavp.c (11)
M src/modules/presence/subscribe.c (6)
M src/modules/pv/pv_trans.c (37)
M src/modules/rtimer/rtimer_mod.c (34)
M src/modules/tm/t_funcs.h (1)
M src/modules/tm/tm_load.c (1)
M src/modules/tm/tm_load.h (1)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1882.patchhttps://github.com/kamailio/kamailio/pull/1882.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/1882