When writing to query_buffer with the help of the snprintf() function,
the result of the functio is written to variable query_buffer_len
instead of to the query_buffer.len itself. This leads to core dump
in some cases. Replaced "_" by "." in "query_buffer_len ="
<!-- 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 -->
- [x] 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 -->
When linking a Contact to an IMPU during SIP REGISTER in S-CSCF, a core dump can happen due to missing assignment of length to query_buffer.
Added the assignment.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1411
-- Commit Summary --
* ims_usrloc_scscf: assignment of length missing for query_buffer in
-- File Changes --
M src/modules/ims_usrloc_scscf/usrloc_db.c (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1411.patchhttps://github.com/kamailio/kamailio/pull/1411.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/1411
this module adds a new function `json_pua_publish()` which allows json data objects to be parsed and inserted into the presentity table.
the function is borrowed from the nsq and kazoo modules. it allows presence to be controlled without loading the nsq or kazoo modules.
this can be quite powerful as it will allow users to control presence by sending http json data objects to kamailio, for example:
```
event_route[xhttp:request] {
$var(call-id) = $(rb{json.parse,Call-ID});
if ($(rb{json.parse,Event-Package}) == "dialog") {
json_pua_publish($rb);
pres_refresh_watchers("$(rb{json.parse,From})", "$(rb{json.parse,Event-Package})", 1);
}
xhttp_reply("200", "OK", "text/html", "$rb");
}
```
example curl request to send presence update:
```
curl -d '{"Call-ID":"user01(a)my.domain.io","Event-Category":"presence","Event-Name":"update","Event-Package":"dialog","Expires":"3600","From":"sip:user01@my.domain.io","From-User":"user01","From-Realm":"my.domain.io","To":"sip:park+6003@my.domain.io","To-User":"park+6003","To-Realm":"my.domain.io","State":"confirmed"}' http://localhost:8080/presence/
```
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1408
-- Commit Summary --
* json_pua: new module
-- File Changes --
M src/modules/json/json_funcs.c (33)
M src/modules/json/json_funcs.h (35)
A src/modules/json_pua/Makefile (20)
A src/modules/json_pua/README (0)
A src/modules/json_pua/defs.h (130)
A src/modules/json_pua/doc/Makefile (4)
A src/modules/json_pua/doc/json_pua.xml (37)
A src/modules/json_pua/doc/json_pua_admin.xml (170)
A src/modules/json_pua/json_pua_mod.c (125)
A src/modules/json_pua/json_pua_mod.h (50)
A src/modules/json_pua/json_pua_publish.c (538)
A src/modules/json_pua/json_pua_publish.h (32)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1408.patchhttps://github.com/kamailio/kamailio/pull/1408.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/1408
Build Update for kamailio/kamailio
-------------------------------------
Build: #5422
Status: Errored
Duration: 10 minutes and 50 seconds
Commit: 64303a9 (master)
Author: Daniel-Constantin Mierla
Message: nathelper: add_rcv_param() - do not enclose to double quotes if URI param
- restrict adding the param to contact URI only for UDP, otherwise a
second transport parameter appears in the URI
- do not enclose the value in double quotes when adding as URI param, it
is not allowed by SIP specs grammar
- discussed on GH PR #1203
View the changeset: https://github.com/kamailio/kamailio/compare/f540ff43e526...64303a9398af
View the full build log and details: https://travis-ci.org/kamailio/kamailio/builds/332729892?utm_source=email&u…
--
You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications
Module: kamailio
Branch: master
Commit: 44dc6caa2b0ff5ac17d5ae14830feae6d8f9ebd7
URL: https://github.com/kamailio/kamailio/commit/44dc6caa2b0ff5ac17d5ae14830feae…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2018-01-24T12:01:31+01:00
modules: readme files regenerated - nathelper ... [skip ci]
---
Modified: src/modules/nathelper/README
---
Diff: https://github.com/kamailio/kamailio/commit/44dc6caa2b0ff5ac17d5ae14830feae…
Patch: https://github.com/kamailio/kamailio/commit/44dc6caa2b0ff5ac17d5ae14830feae…
---
diff --git a/src/modules/nathelper/README b/src/modules/nathelper/README
index 102a639ea0..d21c31c502 100644
--- a/src/modules/nathelper/README
+++ b/src/modules/nathelper/README
@@ -517,12 +517,14 @@ if (search("User-Agent: Cisco ATA.*") {fix_nated_sdp("3");};
5.3. add_rcv_param([flag]),
- Add a received parameter to the “Contact” header fields or the Contact
- URI. The parameter will contain the URI created from the source IP,
- port, and protocol of the packet containing the SIP message. The
- parameter can be then processed by another registrar. This is useful,
- for example, when replicating register messages using t_replicate
- function to another registrar.
+ Add a received parameter to the “Contact” header fields (available for
+ all transports) or to the Contact URI (available only for UDP traffic).
+
+ The parameter will contain the URI created from the source IP, port,
+ and protocol (if different than UDP) of the packet containing the SIP
+ message. The parameter can be then processed by another registrar. This
+ is useful, for example, when replicating register messages using
+ t_replicate function to another registrar.
Meaning of the parameters is as follows:
* flag - flags to indicate if the parameter should be added to