When I just tried to do a commit today, I got the following error:
```
kamailio $ git ci .
error: 'pkg/docker' does not have a commit checked out
fatal: updating files failed
```
It is related to the `pkg/docker` submodule referencing to kamailio/kamailio-ci.
Not sure if this is due to a new git version or something else, because I did commits in that folder a few days ago.
To get is sorted out, I did:
```
kamailio $ git submodule update pkg/docker
Submodule path 'pkg/docker' not initialized
Maybe you want to use 'update --init'?
kamailio $ git submodule update --init pkg/docker
Submodule 'pkg/docker' (https://github.com/kamailio/kamailio-ci.git) registered for path 'pkg/docker'
Cloning into '/.../kamailio/pkg/docker'...
Submodule path 'pkg/docker': checked out 'b92a1c899b8c474afadd0cf29dd7cb4ea01a3466'
```
Then it worked to do the commit.
I wonder if this is going to break the process we were used with, specially the installation guidelines from GIT repo. Therefore I open this item to see if we really need the to have `pkg/docker` submodule, or better have the docker files directly in the repo. Other options to keep things sane and simple?
Git version:
```
$ git --version
git version 2.22.0
```
--
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/2003
### Description
Trying to duplicate TLS SIP messages to the remote host directly from Kamailio by using Siptrace Module. Those are the parameters used by the module:
```
modparam("siptrace", "trace_on", 1)
modparam("siptrace", "force_send_sock", "sip:192.168.1.1:5000")
modparam("siptrace", "trace_mode", 0)
modparam("siptrace", "trace_flag", 22)
modparam("siptrace", "duplicate_uri", "sip:192.168.1.100")
modparam("siptrace", "trace_to_database", 0)
modparam("siptrace", "hep_mode_on", 0)
modparam("siptrace", "xheaders_write", 1)
modparam("siptrace", "trace_local_ip", "MY_EXTERNAL_IP_ADDR")
modparam("siptrace", "trace_sl_acks", 0)
```
But seems that Kamailio is ignoring the parameter "force_send_sock" and keep sending from the first listen interface from the configuration file.
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.2.7 (x86_64/linux) 9ea54f
```
* **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`)
-->
```
CentsOS 7 3.10.0-1127.el7.x86_64
```
--
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/2330
- Current code takes some time to start checking (ping_interval). So, if someone sets a really high ping_interval it takes a while to get destination status. This change fires the first OPTIONS check just 3 seconds (fixed) after the destination is added. The checks would be done with the pace defined in ping_interval.
<!-- 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)
- [ ] 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 -->
Current code takes some time to start checking (ping_interval). So, if someone sets a really high ping_interval it takes a while to get destination status. This change fires the first OPTIONS check just 3 seconds (fixed) after the destination is added. The checks would be done with the pace defined in ping_interval.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2326
-- Commit Summary --
* keepalive: early start of OPTIONS checking
-- File Changes --
M src/modules/keepalive/keepalive.h (5)
M src/modules/keepalive/keepalive_api.c (4)
M src/modules/keepalive/keepalive_core.c (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2326.patchhttps://github.com/kamailio/kamailio/pull/2326.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/2326
#### 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
- [ ] 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
#### Description
Add str_hash_case_get() and str_hash_case_set() functions
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2332
-- Commit Summary --
* core: add case functions for str_hash get and set
-- File Changes --
M src/core/str_hash.h (34)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2332.patchhttps://github.com/kamailio/kamailio/pull/2332.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/2332
Hi,
Since Chrome M72, the default format of SDP generated by Chrome's WebRTC
stack has been changed to "unified-plan" instead of Google's old "plan-b"
format, which has no been deprecated and planned to be removed sometime in
mid 2020. Here are more details about it.
https://webrtc.org/getting-started/unified-plan-transition-guide
This poses a big problem for non-web WebRTC clients, servers and proxies
(such as RTPEngine) which will stop working as soon as Google Chrome
removes support for legacy "plan-b" SDP format.
In kmaialio's RTPEngine module, so far I have seen no support for this new
"unified-plan" SDP format.
Are there any support planed for future?
Meanwhile, if there any way to add support for it in Kamailio via SDP
manipulation e.g. SDPOPS module etc.
Thank you.
--
Muhammad Shahzad Shafi
Tel: +49 176 24 73 85 20