sergey-safarov created an issue (kamailio/kamailio#4290)
### Description
According to [RFC3261](https://www.ietf.org/rfc/rfc3261.html#section-18.3) Section 18.3
```
In the case of message-oriented transports (such as UDP), if the
message has a Content-Length header field, the message body is
assumed to contain that many bytes. If there are additional bytes in
the transport packet beyond the end of the body, they MUST be
discarded.
```
In the current Kamailio implementation, extra bytes are analyzed, and this triggers a failed sanity check.
### Troubleshooting
#### Reproduction
To reproduce required prepare config file
```
listen=udp:127.0.0.1:5060
loadmodule "xlog.so"
loadmodule "sl.so"
loadmodule "sanity.so"
modparam("sanity", "autodrop", 0)
modparam("sanity", "noreply", 1)
route{
if(sanity_check()) {
sl_send_reply("200", "OK");
exit;
}
xerr("sanity checks failed\n");
sanity_reply();
drop;
}
```
And start using a command like
```
kamailio -DD -E -f kamailio.cfg
```
Then need to send options using a command like
```
cat options-extra.txt | nc -u 127.0.0.1 5060
```
Where `options-extra.txt` is a file from the attached archive
[options.tar.gz](https://github.com/user-attachments/files/20838024/options.…
If you remove extra bytes after the OPTIONS message, then Kamailio does not generate an error.
This can be tested using the command
```
cat options-normal.txt | nc -u 127.0.0.1 5060
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4290
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4290(a)github.com>
flantel created an issue (kamailio/kamailio#4218)
### Description
If I add a prefix of greater than 12 characters in to prefix_route it does not return the correct route but instead acts as if no record was found.
### Troubleshooting
#### Reproduction
Create a prefix_route prefix of more than 12 characters and the route will not be chosen.
#### Debugging Data
There is none.
#### Log Messages
prefix_route does not seem to produce DEBUG level messages.
### Additional Information
```
kamailio 5.8.6 (x86_64/linux)
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4218
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/4218(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 -->
- [ ] 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/4170
-- Commit Summary --
* hide all record routes except last one in reply messages
-- File Changes --
M src/modules/topoh/th_msg.c (16)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/4170.patchhttps://github.com/kamailio/kamailio/pull/4170.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4170
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/4170(a)github.com>
Hello @miconda
By mistake, I pushed my private branch to the Kamailio repo and immediately sent a message to the dev maillist to force revert to the correct commit.
For some reason, it hasn't happened.
yes, Daiel I understand this should not happen.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/commit/26982449b7dabe0413258a7602d8810…
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/commit/26982449b7dabe0413258a7602d88107c8f7e7d9/160477300(a)github.com>