<!-- 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 -->
Fix coverity found issue. Unlikely to happen but still it was a bug leading to potential crashes.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1931
-- Commit Summary --
* siptrace: fix coverity found issue
-- File Changes --
M src/modules/siptrace/siptrace.c (6)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1931.patchhttps://github.com/kamailio/kamailio/pull/1931.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/1931
Module: kamailio
Branch: master
Commit: ccb8ba34736556a628497dcc6ac8b525cf201453
URL: https://github.com/kamailio/kamailio/commit/ccb8ba34736556a628497dcc6ac8b52…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2019-04-21T22:46:39+02:00
modules: readme files regenerated - rtp_media_server ... [skip ci]
---
Modified: src/modules/rtp_media_server/README
---
Diff: https://github.com/kamailio/kamailio/commit/ccb8ba34736556a628497dcc6ac8b52…
Patch: https://github.com/kamailio/kamailio/commit/ccb8ba34736556a628497dcc6ac8b52…
---
diff --git a/src/modules/rtp_media_server/README b/src/modules/rtp_media_server/README
index 3ed260c03e..5d4a74cbd2 100644
--- a/src/modules/rtp_media_server/README
+++ b/src/modules/rtp_media_server/README
@@ -38,7 +38,7 @@ Julien Chavanton
4.1. rms_answer (event_route)
4.2. rms_hangup ()
4.3. rms_bridge (target URI, event_route)
- 4.4. rms_session_check ()
+ 4.4. rms_dialog_check ()
4.5. rms_sip_request ()
4.6. rms_play (file, event_route)
@@ -48,7 +48,7 @@ Julien Chavanton
1.2. rms_answer usage example
1.3. rms_hangup usage example
1.4. rms_bridge usage example
- 1.5. rms_session_check usage example
+ 1.5. rms_dialog_check usage example
1.6. rms_sip_request usage example
1.7. rms_play usage example
@@ -71,7 +71,7 @@ Chapter 1. Admin Guide
4.1. rms_answer (event_route)
4.2. rms_hangup ()
4.3. rms_bridge (target URI, event_route)
- 4.4. rms_session_check ()
+ 4.4. rms_dialog_check ()
4.5. rms_sip_request ()
4.6. rms_play (file, event_route)
@@ -142,13 +142,14 @@ modparam("rtp_media_server", "log_file_name", "/var/log/rms/rms_ortp.log")
4.1. rms_answer (event_route)
4.2. rms_hangup ()
4.3. rms_bridge (target URI, event_route)
- 4.4. rms_session_check ()
+ 4.4. rms_dialog_check ()
4.5. rms_sip_request ()
4.6. rms_play (file, event_route)
4.1. rms_answer (event_route)
- Create a session and a call leg and call the event_route
+ Create a call leg : with a SIP dialog and an RTP session call the
+ event_route
This function can be used from REQUEST_ROUTE, REPLY_ROUTE and
FAILURE_ROUTE.
@@ -217,12 +218,12 @@ route {
t_reply("503", "server error");
}
}
- if(rms_session_check()) // If the dialog is managed by the RMS module, t
-he in-dialog request needs to be handled by it.
+ if(rms_dialog_check()) // If the dialog is managed by the RMS module, th
+e in-dialog request needs to be handled by it.
rms_sip_request();
...
-4.4. rms_session_check ()
+4.4. rms_dialog_check ()
Returns true if the current SIP message it handled/known by the RMS
module, else it may be handle in any other way by Kamailio.
@@ -230,10 +231,10 @@ he in-dialog request needs to be handled by it.
This function can be used from REQUEST_ROUTE, REPLY_ROUTE and
FAILURE_ROUTE.
- Example 1.5. rms_session_check usage example
+ Example 1.5. rms_dialog_check usage example
...
- if (rms_session_check()) {
- xnotice("This session is handled by the RMS module\n");
+ if (rms_dialog_check()) {
+ xnotice("This dialog is handled by the RMS module\n");
rms_sip_request();
}
...
@@ -244,15 +245,15 @@ he in-dialog request needs to be handled by it.
forwarded behaving as a B2BUA, the transaction will be suspended until
the second leg replies.
- If the SIP session is not found "481 Call/Transaction Does Not Exist"
- is returned.
+ If the SIP dialog is not found "481 Call/Transaction Does Not Exist" is
+ returned.
This function can be used from REQUEST_ROUTE, REPLY_ROUTE and
FAILURE_ROUTE.
Example 1.6. rms_sip_request usage example
...
- if (rms_session_check()) {
+ if (rms_dialog_check()) {
rms_sip_request();
}
...