Module: kamailio
Branch: master
Commit: 2ffc26aa671c40c482dc5f0eb1896e063f3d9b0e
URL: https://github.com/kamailio/kamailio/commit/2ffc26aa671c40c482dc5f0eb1896e0…
Author: Henning Westerholt <hw(a)skalatan.de>
Committer: Henning Westerholt <hw(a)skalatan.de>
Date: 2020-07-23T13:48:58Z
topos: add two new modes for topology hiding to preserve Contact user
- add two new modes for topology hiding to preserve Contact user
- add new variables contact_mode, cparam_name, a_contact_avp and b_contact_avp
- if contact_mode is 1, the internal key will be stored in a URI parameter
instead of the Contact user, and the Contact users will be taken from the msg
- contact_mode 2 is the same as 1, but the Contact users will be taken from AVPs
- default is contact_mode 0 - the existing (old) behaviour
---
Modified: src/modules/topos/doc/topos_admin.xml
Modified: src/modules/topos/topos_mod.c
Modified: src/modules/topos/tps_msg.c
Modified: src/modules/topos/tps_storage.c
---
Diff: https://github.com/kamailio/kamailio/commit/2ffc26aa671c40c482dc5f0eb1896e0…
Patch: https://github.com/kamailio/kamailio/commit/2ffc26aa671c40c482dc5f0eb1896e0…
<!--
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
Centos RPM repo is generating Kamailio 5.0.8 packages that can't be installed
Looks like same issue as: #1604
<!--
Explain what you did, what you expected to happen, and what actually happened.
-->
### Troubleshooting
By using the repo
https://download.opensuse.org/repositories/home:/kamailio:/v5.0.x-rpms/Cent…
when trying to install Kamailio 5.0.8, yum returns this error:
```
Downloading packages:
kamailio-5.0.8-2.el7.centos.x8 FAILED ================================================= ] 2.0 MB/s | 4.3 MB 00:00:00 ETA
http://download.opensuse.org/repositories/home%3A/kamailio%3A/v5.0.x-rpms/C…: [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=Kamailio clean metadata
Trying other mirror.
Error downloading packages:
kamailio-5.0.8-2.el7.centos.x86_64: [Errno 256] No more mirrors to try.
```
#### Reproduction
<!--
If the issue can be reproduced, describe how it can be done.
-->
#### 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).
-->
#### 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).
-->
### Possible Solutions
<!--
If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix.
-->
### Additional Information
CentOS Linux release 7.8.2003 (Core)
<!--
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`)
-->
--
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/2407
Hello,
Apparently, this is the way the code works:
t_reply.c:
if (relayed_code==503 && tm_remap_503_500){
/* replace a final 503 with a 500:
* generate a "FAKE" reply and a new to_tag (for easier
* debugging)*/
Lets see if maybe others can comment as well. Otherwise you could just open an issue on our tracker, it is probably not that hard to change this.
Cheers,
Henning
--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com<https://gilawa.com/>
From: sr-users <sr-users-bounces(a)lists.kamailio.org> On Behalf Of Gerry | Rigatta
Sent: Wednesday, July 22, 2020 8:58 PM
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Subject: [SR-Users] bug ? remap_503_500 breaks dialogs
Hi,
I am using Kamailio 5.2.
Apparently the remapping of 503 to 500 codes in the tm module does also change the to-tag. This behaviour breaks dialogs with yate and therefore calls hang and the 503 remains unacknowledged. After disabling the 503 to 500 remapping with modparam("tm", "remap_503_500", 0) all works fine again.
Changing the to-tag in a dialog seems to contradict RFC3261, or do I see this wrongly?
12<https://tools.ietf.org/html/rfc3261#section-12> Dialogs
A dialog is identified at each UA with a dialog ID, which consists of a Call-ID value, a local tag and a remote tag…"
Thanks for looking into this.
Gerry
Starting this issue to collect suggestions about what should be adjusted in the default config or options (global or module parameters) in preparation for Kamailio 5.4.0. The goal is not to recreate a completely new config, the current one being a good starting point for new deployments, but to tune its parameters with what people consider useful to have based on experiences encountered lately.
Compared with 5.3, there are already:
* replaced XMLRPC with JSONRPC
* option to use RTPEngine instead of RTPProxy
Other proposals I would do:
* enable path support by default in registrar/usrloc modules - it is disabled by default, a modparam needs to be set, but if set and no PATH header, then there is no effect. I met couple of cases when a Kamailio proxy was added in front of other Kamailio (usually coming as part of a PBX) and Path is not enabled there.
* set timer_procs for usrloc - as deployments grow with the population of registered endpoints, core time can be affected by scanning expired registrations
* load textopsx module and try to provide an example of using msg_apply_changes() probably within some `ifdef` - aiming to help new comers spot that changes as are immediately visible
Listing now, but to have in mind for other future releases, because the code is young in 5.4:
* keepalive to be done with usrloc module to get round trip timer, etc
*dlgs module loaded to see the basic stats about active calls - useful to help deciding when to do a restart or a maintenance shut down, even if it may not be 100% accurate if done after another restart (because there is no persistence, at least now), currently the stats being more or less in the fashion of active transaction stats
--
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/2381
<!-- 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
<!-- Describe your changes in detail -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2401
-- Commit Summary --
* ims_usrloc_scscf: added a new contact state, udomain/impu improvements
* ims_registrar_scscf: added a new registrar event, notification improvements
-- File Changes --
M src/modules/ims_registrar_scscf/cxdx_callbacks.c (4)
M src/modules/ims_registrar_scscf/reg_rpc.c (2)
M src/modules/ims_registrar_scscf/registrar_notify.c (154)
M src/modules/ims_registrar_scscf/registrar_notify.h (9)
M src/modules/ims_registrar_scscf/save.c (25)
M src/modules/ims_registrar_scscf/usrloc_cb.c (5)
M src/modules/ims_usrloc_scscf/impurecord.c (72)
M src/modules/ims_usrloc_scscf/udomain.c (39)
M src/modules/ims_usrloc_scscf/usrloc.h (7)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2401.patchhttps://github.com/kamailio/kamailio/pull/2401.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/2401