<!-- 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 -->
- [ ] PR should be backported to stable branches
- [x ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
topos_redis: support SUBSCRIBE dialog
topos: SUBSCRIBE dialog
topos: documentation for SUBSCRIBE dialog
topos: add description for dialog_expire key
Add support for dialog subscribe when using topos.
When a Subscribe is received, a Subscribe dialog is created. Dialog TTL is set according to expire received in SIP request.
At each resubscribe the TTL is refresh according to expires set in SIP request.
Notify (in-dialog) with header event set are supposed to be inside a Subscribe dialog.
bugfix:
topos: when contact mode is set to 1, contact uri created is malformed if received contact has no user part
In this case we have a sip uri like : sip:@host
htable: ht_dmq_replicate_action was always called on ht_rm_items even if dmq was not activated
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2662
-- Commit Summary --
* topos: when contact mode is set to 1, contact uri created is malformed if received contact has no user part
* topos_redis: support SUBSCRIBE dialog
* htable: ht_dmq_replicate_action was always called on ht_rm_items even if dmq was not activated
-- File Changes --
M src/modules/htable/htable.c (4)
M src/modules/topos/doc/topos.xml (9)
M src/modules/topos/doc/topos_admin.xml (7)
M src/modules/topos/tps_msg.c (5)
M src/modules/topos/tps_storage.c (41)
M src/modules/topos/tps_storage.h (2)
M src/modules/topos_redis/doc/topos_redis.xml (9)
M src/modules/topos_redis/topos_redis_storage.c (75)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2662.patchhttps://github.com/kamailio/kamailio/pull/2662.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/2662
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
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 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
<!--
Explain what you did, what you expected to happen, and what actually happened.
-->
Extreme logging introduced in 5.4.4 here:
https://github.com/kamailio/kamailio/blob/2015cfdfd777085dad98a606fc41946af…
and here:
https://github.com/kamailio/kamailio/blob/2015cfdfd777085dad98a606fc41946af…
### Troubleshooting
Logging level for these should be DEBUG?
#### Reproduction
<!--
If the issue can be reproduced, describe how it can be done.
-->
Install Kamailio 5.4.4.
#### Debugging Data
<!--
If you got a core dump, use gdb to extract troubleshooting data - full backtrace,
local variables and the list of the code at the issue location.
gdb /path/to/kamailio /path/to/corefile
bt full
info locals
list
If you are familiar with gdb, feel free to attach more of what you consider to
be relevant.
-->
```
```
#### Log Messages
<!--
Check the syslog file and if there are relevant log messages printed by Kamailio, add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
20(70) INFO: ctl [io_listener.c:518]: handle_stream_read(): bytes processed: 29
20(70) INFO: ctl [io_listener.c:498]: handle_stream_read(): bytes read: 35
20(70) INFO: ctl [io_listener.c:518]: handle_stream_read(): bytes processed: 35
20(70) INFO: ctl [io_listener.c:498]: handle_stream_read(): bytes read: 18
20(70) INFO: ctl [io_listener.c:518]: handle_stream_read(): bytes processed: 18
20(70) INFO: ctl [io_listener.c:498]: handle_stream_read(): bytes read: 29
20(70) INFO: ctl [io_listener.c:518]: handle_stream_read(): bytes processed: 29
20(70) INFO: ctl [io_listener.c:498]: handle_stream_read(): bytes read: 29
20(70) INFO: ctl [io_listener.c:518]: handle_stream_read(): bytes processed: 29
```
#### SIP Traffic
<!--
If the issue is exposed by processing specific SIP messages, grab them with ngrep or save in a pcap file, then add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
(paste your sip traffic here)
```
### Possible Solutions
<!--
If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix.
-->
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.4.4 (x86_64/linux)
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, 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, TLS_PTHREAD_MUTEX_SHARED
ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: unknown
compiled with gcc 8.3.0
```
* **Operating System**:
<!--
Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
Kernel details (output of `uname -a`)
-->
```
(paste your output here)
```
--
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/2661