<!-- 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 -->
- [ ] 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/3470
-- Commit Summary --
* imc: add support to modify member role
* imc: call handle_modify
* imc: db_mode support
* Merge branch 'kamailio:master' into master
* imc: destroy db only if db_mode is not 0
* Merge remote-tracking branch 'joeygo/master'
* imc: propagate content-type header
* Merge branch 'kamailio:master' into master
* Merge remote-tracking branch 'joeygo/master'
* Merge branch 'kamailio:master' into master
* rtpengine: support receiving dtmf events from rtpengine and raise an event
-- File Changes --
M src/modules/rtpengine/doc/rtpengine.xml (7)
M src/modules/rtpengine/doc/rtpengine_admin.xml (117)
M src/modules/rtpengine/rtpengine.c (405)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3470.patchhttps://github.com/kamailio/kamailio/pull/3470.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3470
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3470(a)github.com>
…callid param
<!-- 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 -->
- [ ] 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
- [ 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 -->
Using kamailio 5.4 version, we have had an issue with a carrier that sent a CANCEL with to-tag. To be able to process that request, we used the function t_cancel_callid, to convert that abnormal CANCEL to a regular one cancelling the current transaction for that call.
But we saw that it was not working since they sent the callid header named as CALL-ID.
Seems the matching between the stored callid header in memory and the param passed for the callid lookup matching, is being done in case sensitive way with a generated Call-ID: XXXXXXXX based on the called param of the function.
we have tested a wasy to do the comparision only with the callid header value, so we strip from the callid header stored at memory the Call-ID: (or CALL-ID:) part.
maybe there is another way to do that in other part of the code, but seems at least this worked for the tests
thanks a lot and regards
david
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3393
-- Commit Summary --
* tm:t_lookup_callid use only trans Call-ID header value to match with callid param
-- File Changes --
M src/modules/tm/t_lookup.c (10)
M src/modules/tm/t_msgbuilder.c (9)
M src/modules/tm/t_msgbuilder.h (1)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3393.patchhttps://github.com/kamailio/kamailio/pull/3393.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3393
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3393(a)github.com>
Hi everyone,
I'm having the following errors in kamailio when i try to make an outbound call to other server, I don't know what does it mean, if some one can help me
11(25) ERROR: <core> [core/receive.c:310]: receive_msg(): core parsing of SIP message failed (XX.XX.XX.XX.5060/1)
13(27) ERROR: <core> [core/parser/parse_fline.c:271]: parse_first_line(): parse_first_line: bad message (offset: 65)
13(27) ERROR: <core> [core/parser/msg_parser.c:681]: parse_msg(): ERROR: parse_msg: message=<BY�sip:asterisk@10.0.5.158:4080;alias=10.0.5.158~44730~1 SIP/2.0
Via: SIP/2.0/UDP 84.127.226.15:5060;branch=z9hG4bK3bc90b47;rport
Route: <sip:34.252.151.179:4060;r2=on;lr;ftag=5c7f862f-9692-4028-8af0-ebc224ba0e2a;vsf=AAAAAAAAAAAAAAAAAAAJCQABGgUAAAMJLjE4ODo1MDYw;nat=yes>,<sip:10.0.5.40:4070;r2=on;lr;ftag=5c7f862f-9692-4028-8af0-ebc224ba0e2a;vsf=AAAAAAAAAAAAAAAAAAAJCQABGgUAAAMJLjE4ODo1MDYw;nat=yes>
Max-Forwards: 70
From: <sip:692598435@kamailio.voip.svc.cluster.local>;tag=as6f32aa26
To: <sip:963441038@192.168.123.66:4060>;tag=5c7f862f-9692-4028-8af0-ebc224ba0e2a
Call-ID: b9a49c52-7829-4cdf-a88c-0064cc5bb438
CSeq: 102 BYE
User-Agent: Asterisk PBX 11.2-cert3
X-Asterisk-HangupCause: No user responding
X-Asterisk-HangupCauseCode: 18
Content-Length: 0
>
<!-- 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
- [x] Related to issue #3440
#### Description
implemented a way to dump the names of the variables stored in pv_cache this helped me to find out what was filling the pv_cache
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3448
-- Commit Summary --
* core: pv_cache_dump
-- File Changes --
M src/core/cfg_core.c (4)
M src/core/cfg_core.h (1)
M src/core/pvapi.c (33)
M src/core/pvapi.h (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3448.patchhttps://github.com/kamailio/kamailio/pull/3448.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3448
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3448(a)github.com>