<!-- 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 -->
- remove a variable creation
Put two variable accessible to the entire function, renaming one to have some clarity.
Remove the useless variable.
- Change from using snprintf to memset (no more \0 at last position)
This fix possible a memory overflow while using `snprintf`. This also add a \0 at the end of the structure, so a more direct approach with `memset` was used.
- change the destination of an allocated space being smaller than the source
Elements were being put into a smaller string, this commit makes the destination bigger then the source.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3095
-- Commit Summary --
* pv_headers: fix possible mem. overflow issue and wrong size string
-- File Changes --
M src/modules/pv_headers/pvh_func.c (26)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3095.patchhttps://github.com/kamailio/kamailio/pull/3095.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3095
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3095(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, ...)
- [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 -->
Ported mi functions to RPC. Note that in order to send long number strings (e.g. username) from kamcmd one must prefix it with "s:"
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3097
-- Commit Summary --
* userblocklist: add RPC functions
-- File Changes --
M src/modules/userblocklist/userblocklist.c (348)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3097.patchhttps://github.com/kamailio/kamailio/pull/3097.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3097
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3097(a)github.com>
Determine dialog event types for dialog callback on module
initialization, since these will not change.
<!-- 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 -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3079
-- Commit Summary --
* pua_dialoginfo: Determine dialog event types in mod_init
-- File Changes --
M src/modules/pua_dialoginfo/pua_dialoginfo.c (29)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3079.patchhttps://github.com/kamailio/kamailio/pull/3079.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3079
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3079(a)github.com>
#### 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:
- [ ] PR should be backported to stable branches
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
Fix for the following compiler warnings:
```
core/crypto/sha256.c:548:32: warning: argument 1 of type ‘sha2_byte[]’ {aka ‘unsigned char[]’} with mismatched bound [-Warray-parameter=]
548 | void sr_SHA256_Final(sha2_byte digest[], SHA256_CTX* context) {
| ~~~~~~~~~~^~~~~~~~
In file included from core/crypto/sha256.c:36:
core/crypto/sha256.h:86:22: note: previously declared as ‘uint8_t[32]’ {aka ‘unsigned char[32]’}
86 | void sr_SHA256_Final(uint8_t[SHA256_DIGEST_LENGTH], SHA256_CTX*);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
core/crypto/sha256.c:611:47: warning: argument 2 of type ‘char[]’ with mismatched bound [-Warray-parameter=]
611 | char *sr_SHA256_End(SHA256_CTX* context, char buffer[]) {
| ~~~~~^~~~~~~~
In file included from core/crypto/sha256.c:36:
core/crypto/sha256.h:87:34: note: previously declared as ‘char[65]’
87 | char* sr_SHA256_End(SHA256_CTX*, char[SHA256_DIGEST_STRING_LENGTH]);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
core/crypto/sha256.c:911:32: warning: argument 1 of type ‘sha2_byte[]’ {aka ‘unsigned char[]’} with mismatched bound [-Warray-parameter=]
911 | void sr_SHA512_Final(sha2_byte digest[], SHA512_CTX* context) {
| ~~~~~~~~~~^~~~~~~~
In file included from core/crypto/sha256.c:36:
core/crypto/sha256.h:98:22: note: previously declared as ‘uint8_t[64]’ {aka ‘unsigned char[64]’}
98 | void sr_SHA512_Final(uint8_t[SHA512_DIGEST_LENGTH], SHA512_CTX*);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
core/crypto/sha256.c:940:47: warning: argument 2 of type ‘char[]’ with mismatched bound [-Warray-parameter=]
940 | char *sr_SHA512_End(SHA512_CTX* context, char buffer[]) {
| ~~~~~^~~~~~~~
In file included from core/crypto/sha256.c:36:
core/crypto/sha256.h:99:34: note: previously declared as ‘char[129]’
99 | char* sr_SHA512_End(SHA512_CTX*, char[SHA512_DIGEST_STRING_LENGTH]);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
core/crypto/sha256.c:986:32: warning: argument 1 of type ‘sha2_byte[]’ {aka ‘unsigned char[]’} with mismatched bound [-Warray-parameter=]
986 | void sr_SHA384_Final(sha2_byte digest[], SHA384_CTX* context) {
| ~~~~~~~~~~^~~~~~~~
In file included from core/crypto/sha256.c:36:
core/crypto/sha256.h:92:22: note: previously declared as ‘uint8_t[48]’ {aka ‘unsigned char[48]’}
92 | void sr_SHA384_Final(uint8_t[SHA384_DIGEST_LENGTH], SHA384_CTX*);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
core/crypto/sha256.c:1015:47: warning: argument 2 of type ‘char[]’ with mismatched bound [-Warray-parameter=]
1015 | char *sr_SHA384_End(SHA384_CTX* context, char buffer[]) {
| ~~~~~^~~~~~~~
In file included from core/crypto/sha256.c:36:
core/crypto/sha256.h:93:34: note: previously declared as ‘char[97]’
93 | char* sr_SHA384_End(SHA384_CTX*, char[SHA384_DIGEST_STRING_LENGTH]);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3098
-- Commit Summary --
* core/crypto: fix several mismatched bound warnings
-- File Changes --
M src/core/crypto/sha256.c (16)
M src/core/crypto/sha256.h (9)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3098.patchhttps://github.com/kamailio/kamailio/pull/3098.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3098
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3098(a)github.com>
Hallo all,
I would need help with Kamailio. I hope, you can give me some hints.
I would like use Kamailio for CFNRy feature call forward no replay, i.e.
* call is forked to multiple destination
* 180 is received, call is ringing, but not answered, no 200 OK is received from some destination
* after predefined time (CFNRy timer), only this specific branch has to be rerouted to another destination
Expected behaviour is described in this flow:
[cid:image001.png@01D85B0C.FCF06DE0]
My current behavior:
* Kamailio TM module is involved for parallel forking (https://www.kamailio.org/docs/modules/stable/modules/tm.html#:~:text=1.-,Ov…)
* all branches are CANCEL-ed, it is not possible send CANCEL just to one specific branch
[cid:image002.png@01D85B0C.FCF06DE0]
My questions:
* is it possible to CANCEL just specific branch?
* is it possible start timer just for specific branch?
* do you think is it possible somehow implement this feature with Kamailio?
Thanks a lot in advance for any comment.
Pavel.