Hello,
being discussed at the previous IRC devel meeting before the summer,
it's time to plan the preparation for next major release, respectively
Kamailio 5.1 series.
As an initial proposal, a timeline can be:
- Mon, Oct 16, 2017 - freeze the development
- in 3-4 weeks after that, create the branch 5.1
- 2-3 weeks after, do the release of v5.1.0
That means more or less by end of November we will have first version of
5.1 series.
There are still 4 weeks of development, …
[View More]hopefully enough to get ongoing
work finished. I know from github tracker that there are people working
on redis support for usrloc. I will focus on exporting more functions to
kemi, right now should be around 60%, by freeze should be more than 80%
(likely that means all of what most of people use these days, because
there are some modules that I guess are not much used). Maybe one or two
modules will be pushed as well from my side.
I think we should also do an IRC devel meeting to try to sync better on
this. Maybe by mid of next week, I will send another email shortly.
Should anyone have more details to add or adjust the proposal, do not
hesitate to reply to mailing list!
Cheers,
Daniel
--
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - www.asipto.com
Kamailio World Conference - www.kamailioworld.com
[View Less]
(cherry picked from commit dbd57c3eac30e1de54d98eb2ba8f608a17f7adbf)
<!-- 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 …
[View More]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 -->
- [ ] Commit message has the format required by CONTRIBUTING guide
- [ ] Commits are split per component (core, individual modules, libs, utils, ...)
- [ ] Each component has a single commit (if not, squash them into one commit)
- [ ] 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)
- [ ] 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
- [ ] 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/1272
-- Commit Summary --
* sipcapture: fix HEP3 capture-id >= 2^16
-- File Changes --
M modules/sipcapture/sipcapture.c (4)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1272.patchhttps://github.com/kamailio/kamailio/pull/1272.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/1272
[View Less]
The 100 character hard-coded maximum length of the kazoo module's amqp_connection parameter is too short. The limit was previously bumped from 50 to 100 following on from #529 but this is still too short.
Example use case, using Hashicorp's vault to dish out AMQP credentials yields a connection URL like this:
amqp://aws-ec2-13e1e70e-d4d3-abbe-5f3b-7b631f83def7:63b8d362-72d1-878e-81ca-d62667503495@rabbitmq.service.consul:5672
https://github.com/kamailio/kamailio/blob/…
[View More]48791fae1ba8508b18856d90e85a93df0…
--
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/1269
[View Less]
I let two kamailio server processes run in two Nat IP , and DNS to keep loadbalance. but DNS can return two Nat IP,when the IP it returns is not the same as the account register,the server cann't deal with request,i wonder if i can use Nat IP to keep DNS loadbalance?
--
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/1268
<!--
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 …
[View More]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 -->
- [x] PR should be backported to stable branches
- [x] Tested changes locally
- [x] Related to issue #1265
#### Description
Add columns referenced by [p_usrloc_mod.c](https://github.com/kamailio/kamailio/blob/6c01e2692d5ff56dd…
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1266
-- Commit Summary --
* p_usrloc: Fix #1265: missing columns in location.sql file.
-- File Changes --
M src/modules/p_usrloc/location.sql (4)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1266.patchhttps://github.com/kamailio/kamailio/pull/1266.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/1266
[View Less]
Module: kamailio
Branch: master
Commit: 9c9366473280c52d7f79348637a56264420d48fc
URL: https://github.com/kamailio/kamailio/commit/9c9366473280c52d7f79348637a5626…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2017-10-09T16:46:17+02:00
modules: readme files regenerated - path ... [skip ci]
---
Modified: src/modules/path/README
---
Diff: https://github.com/kamailio/kamailio/commit/9c9366473280c52d7f79348637a5626……
[View More]Patch: https://github.com/kamailio/kamailio/commit/9c9366473280c52d7f79348637a5626…
---
diff --git a/src/modules/path/README b/src/modules/path/README
index d2e3d69398..4d6e7cba5c 100644
--- a/src/modules/path/README
+++ b/src/modules/path/README
@@ -292,6 +292,13 @@ if (!add_path("loadbalancer", "ob")) {
address as domain-part, and the address the request has been received
from as received-parameter.
+ If the “outbound” module was loaded before this module, and outbound is
+ required for this request, the header will be in the form “Path:
+ <sip:flowtoken@1.2.3.4;lr;received=sip:2.3.4.5:1234;ob>”, where
+ “flowtoken” is the RFC 5626 flow-token that can be used to identify the
+ source and local address and transport the request was received on, and
+ where “1.2.3.4” is the address of the outgoing interface.
+
This function can be used from REQUEST_ROUTE.
Example 1.8. add_path_received() usage
[View Less]
<!-- 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 …
[View More]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
- [ ] 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 -->
- added the possiblity to have the received parameter and flow toke
in the add_path_received function
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1261
-- Commit Summary --
* path: insert flow token in path header with received
-- File Changes --
M src/modules/path/doc/path_admin.xml (9)
M src/modules/path/path.c (78)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1261.patchhttps://github.com/kamailio/kamailio/pull/1261.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/1261
[View Less]
using ""%" HEX HEX" mechanism for escaping from RFC 2396
#### Pre-Submission Checklist
- [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 (…
[View More]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:
- [ ] PR should be backported to stable branches
- [x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
I consider it non breaking because with the existing a field containing an ASCII vertical bar '|' would break the separator count and result in broken CDRs, etc. in this case changing the default behavior is probably recommended, someone could abuse this flaw.
Test: consider the following message, the '|' character in the call-id will break the accounting event.
```
INVITE sip:+11231234567@127.0.0.101 SIP/2.0
Via: SIP/2.0/UDP 1.1.69.51:5070;rport;branch=z9hG4bKPjpM.BvWCQzoS0BJ7TgnuLF9YtmHQTlDgd
Max-Forwards: 70
Call-ID: fG8qa5Xc-iNDLhIAnuLZP|njL1sojRRD
```
With the encoding it is replaced with '%7C', no modifications should be required to systems processing the ACC events since different behavior will only take place when there is an invalid ACC event:
```
cat /var/log/acc/acc_129.log
INVITE|upDPn89PCIq7SLTssEGoLoSbC-jDRnfj||fG8qa5Xc-iNDLhIAnuLZP%7CnjL1sojRRD.|403|Forbidden
```
Extra comments:
I corrected the documentation on the command 'flatstore.rotate', since it was not working, but this one is 'flatstore.k_rotate'
If I understand correctly this module was never migrated from SER to Kamailio completely ...
This change may be the only important one for operation, so I am not proposing any extra refactoring.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1262
-- Commit Summary --
* db_flatstore: encode delimiter param
-- File Changes --
M src/modules/db_flatstore/db_flatstore.c (5)
M src/modules/db_flatstore/doc/db_flatstore.xml (14)
M src/modules/db_flatstore/doc/db_flatstore_params.xml (11)
M src/modules/db_flatstore/km_flatstore.c (15)
M src/modules/db_flatstore/km_flatstore.h (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1262.patchhttps://github.com/kamailio/kamailio/pull/1262.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/1262
[View Less]
Hello,
writing to inform everyone that currently the qq.com domain is
blacklisted by the kamailio.org email server due to high volume of spam
sent to many admin addresses and mailing lists. Spamassassin had very
hard time digesting and filtering, as content kept changing and
addresses were random.
I didn't get the chance yet to check if we have subscribers with this
domain, so, as a fast lane, if you use it and don't have the possibility
to quickly switch to another email server domain, write …
[View More]me to try to
whitelist the address. Hopefully, if anyone is affected, there is not
much inconvenience, but it was the only quick solution that could be
applied for the moment.
Cheers,
Daniel
--
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - www.asipto.com
Kamailio World Conference - www.kamailioworld.com
[View Less]
Hello,
How do i include Expires header for 200 OK message?
One of the manual says this.. how do i modify my existing config file to
include this?
I am using : /usr/local/etc/kamailio/kamailio.cfg for configuration.
Rgds,
MGSK
1.4.9. expires_offset (int)
The value that should be subtracted from the expires value when sending a
200OK for a publish. It is used for forcing the client cu send an update
before the old publish expires.
*Default value is "0".*
*Example 1-9. Set expires_offset …
[View More]parameter*
...
modparam("presence", "expires_offset", 10)
[View Less]