On Ubuntu, `/bin/sh` defaults to `dash` whose built-in `echo` command does not support the `-e` flag. `printf`, on the other hand, supports backslash escapes by default so we use that instead.
In passing, also clean up some messy ANSI escape codes.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3671
-- Commit Summary --
* utils: Prefer `printf` over `echo -e`.
-- File Changes --
M pkg/kamailio/obs/kamailio.init (2)
M utils/kamctl/kamctl (2)
M utils/kamctl/kamctl.base (10)
M utils/kamctl/kamdbctl (6)
M utils/kamctl/kamdbctl.base (10)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3671.patchhttps://github.com/kamailio/kamailio/pull/3671.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3671
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3671(a)github.com>
Module: kamailio
Branch: master
Commit: 8d3d53f5f698da1357c3475ae136677099b2f702
URL: https://github.com/kamailio/kamailio/commit/8d3d53f5f698da1357c3475ae136677…
Author: Sean Bright <sean(a)seanbright.com>
Committer: Victor Seva <linuxmaniac(a)torreviejawireless.org>
Date: 2023-12-12T10:38:06+01:00
utils: Prefer `printf` over `echo -e`.
On Ubuntu, `/bin/sh` defaults to `dash` whose built-in `echo` command
does not support the `-e` flag. `printf`, on the other hand, supports
backslash escapes by default so we use that instead.
In passing, also clean up some messy ANSI escape codes.
---
Modified: pkg/kamailio/obs/kamailio.init
Modified: utils/kamctl/kamctl
Modified: utils/kamctl/kamctl.base
Modified: utils/kamctl/kamdbctl
Modified: utils/kamctl/kamdbctl.base
---
Diff: https://github.com/kamailio/kamailio/commit/8d3d53f5f698da1357c3475ae136677…
Patch: https://github.com/kamailio/kamailio/commit/8d3d53f5f698da1357c3475ae136677…
Hi
I have a kimailio box that receives messages from one interface and send it from another interface and I use dispatcher module successfully.
Now I assigned an I range to Linux loopback interface through Linux kernel anyip feature. And I can ping the range.
ip -4 route add local 192.168.0.0/24 dev lo
I want to send messages from source of the ip in this range but kamailio cant do this in the right way.
I added this two directives to kamailio.cfg:
mhomed=yes
ip_free_bind = 1
and when I want to use an ip from the list I use
$fs=”udp:192.168.0.120:5060”;
With no luck
If I use
force_send_socket(udp:192.168.0.120:5060);
kamailio returns an error
bad force_send_socket argument: 192.168.0.120:5060 (kamailio doesn't listen on it)
and if I add listen directive for one ip like:
listen=udp:192.168.0.120:5060
everything works fine but I want to be able to use any ip from list not just one ip.
Thanks.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3394
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3394(a)github.com>
When used `tcp_accept_haproxy=yes` and inbound connection from load-balancer received via IPv6 protocol and client real IPv4 then i can see error in the kamailio log
```
28(723055) ERROR: {1 27 REGISTER 4fkReTbLC-} siptrace [siptrace_hep.c:94]: trace_send_hep3_duplicate(): interworking detected ?
```
Looks like requried add haproxy protocol support into siptrace module
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3665
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3665(a)github.com>
### Description
When used haproxy protocol then from client perspetive TCP connection established to loadbalancer IP address.
Real Kamailio listener may be IPv6 and expected to see `$RAut` value with IP of load balancer IP.
Really I can see for first message from the client
```
sip:2600::6:45060;transport=tcp
```
For second message
```
Advertised socket URI: sip:[2600::6]:5060
```
For first case missed `[]` in the IP and expected to see loadbalancer IPv4 because client use IPv4 to establish connection to Kamailio.
### Expected behavior
Used loadbalancerserver IP from haproxy protocol for `$RAut` value and for `Record-Route` headers generation.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3667
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3667(a)github.com>
### Description
PKG memory errors when configured mask_callid in TOPOS.
### Troubleshooting
The poblem in detail desribed in mailing lists:
https://www.mail-archive.com/sr-users@lists.kamailio.org/msg19997.html
### Possible Solutions
Right way to configure topos for callid masking is:
modparam("topoh", "use_mode", 1)
modparam("topos", "mask_callid", 1)
modparam("topoh", "mask_callid", 1)
We need to set mask_callid module parameter for topoh also. There is not a word about this in the documentation,
so docs correction needed.
### Additional Information
* **Kamailio Version** - 5.7.X
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3606
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3606(a)github.com>
<!-- 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, ...)
- [ ] 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)
- [ ] New feature (non-breaking change which adds new functionality)
- [x] 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
This PR adds support for $hfl(Diversion)[] and $hflc(Diversion).
This parse_diversion.c was inspired by [parse_pai_ppi.c](https://github.com/kamailio/kamailio/blob/master/src/core/…. I am not sure if it's breaking the existing implementation and usage.
Any feedback and review is welcome.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3651
-- Commit Summary --
* parser: Extend diversion for multiple bodies
* pv: Add hfl and hflc support for Diversion header
-- File Changes --
M src/core/parser/parse_diversion.c (152)
M src/core/parser/parse_diversion.h (11)
M src/modules/pv/pv_core.c (71)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3651.patchhttps://github.com/kamailio/kamailio/pull/3651.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3651
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3651(a)github.com>