<!-- 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/2248
-- Commit Summary --
* siptrace: log correct dialog event
-- File Changes --
M src/modules/siptrace/siptrace.c (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2248.patchhttps://github.com/kamailio/kamailio/pull/2248.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/2248
Module: kamailio
Branch: master
Commit: 4efab96e097faa3de6385d09e271d631ee27b47b
URL: https://github.com/kamailio/kamailio/commit/4efab96e097faa3de6385d09e271d63…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2020-03-12T17:01:15+01:00
modules: readme files regenerated - siptrace ... [skip ci]
---
Modified: src/modules/siptrace/README
---
Diff: https://github.com/kamailio/kamailio/commit/4efab96e097faa3de6385d09e271d63…
Patch: https://github.com/kamailio/kamailio/commit/4efab96e097faa3de6385d09e271d63…
---
diff --git a/src/modules/siptrace/README b/src/modules/siptrace/README
index 749c89ea65..ca0d73ca26 100644
--- a/src/modules/siptrace/README
+++ b/src/modules/siptrace/README
@@ -75,7 +75,7 @@ Camille Oudot
List of Examples
1.1. Set db_url parameter
- 1.2. Set sip_trace parameter
+ 1.2. Set table parameter
1.3. Set trace_flag parameter
1.4. Set trace_on parameter
1.5. Set traced_user_avp parameter
@@ -222,7 +222,7 @@ modparam("siptrace", "db_url", "dbdriver://username:password@dbhost/dbname")
Default value is “sip_trace”.
- Example 1.2. Set sip_trace parameter
+ Example 1.2. Set table parameter
...
modparam("siptrace", "table", "strace")
...
@@ -283,7 +283,7 @@ modparam("siptrace", "trace_table_avp", "$avp(s:siptrace_table)")
3.7. duplicate_uri (str)
The address in form of a SIP URI where to send a duplicate of traced
- message. It uses UDP all the time.
+ message.
Default value is "NULL".
<!-- 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 -->
- [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 -->
Allow duplicating messages via HEP over any configured protocol.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2244
-- Commit Summary --
* siptrace: duplicate via HEP with any protocol
-- File Changes --
M src/modules/siptrace/doc/siptrace_admin.xml (4)
M src/modules/siptrace/siptrace.c (25)
M src/modules/siptrace/siptrace_hep.c (30)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2244.patchhttps://github.com/kamailio/kamailio/pull/2244.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/2244
Tracking here the issue exposed by @linuxmaniac via PR #924, as it was merged and then reverted (by #1248), so anyone can be aware of as well as comment/propose solutions for it.
> Add "-fno-strict-aliasing" to compilation flags
>
> Fixes a slew of:
> "dereferencing type-punned pointer will break strict-aliasing rules"
> warnings from GCC for lines of the form:
> Py_INCREF(Py_True);
> and
> Py_INCREF(Py_False);
>
> due to the cast from PyIntObject* to PyObject*
>
> GCC is technically correct here; see:
> http://www.python.org/dev/peps/pep-3123/
> though this is unlikely to lead to non-working machine code.
The initial proposed patch for `src/modules/app_python/Makefile` is:
```
@@ -22,6 +22,8 @@ ifeq ($(OS), freebsd)
LIBS+=-pthread
endif
+# python2 https://www.python.org/dev/peps/pep-3123/
+DEFS+=-fno-strict-aliasing
DEFS+=-I${PYTHON_INCDIR}
DEFS+=-DKAMAILIO_MOD_INTERFACE
```
--
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/issues/1249
Hello Subhra,
Great! Could you share the here steps that lead to the success that others might be able to learn from it as well?
Cheers,
Henning
--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com<https://gilawa.com/>
From: subhra giri <subhraprakash79(a)gmail.com>
Sent: Saturday, March 7, 2020 11:18 AM
To: Henning Westerholt <hw(a)skalatan.de>
Subject: Thank you --- Compilation success
Dear Henning
Compilation is successful for MIPS.
Thank you very much
Subhra Prakash Giri
On Sat, Mar 7, 2020 at 1:26 PM subhra giri <subhraprakash79(a)gmail.com<mailto:subhraprakash79@gmail.com>> wrote:
Dear Henning
I tried to compile directly on MIPS board, but there is no make file in my board. so it is not compiling.
I am not getting Make for MIPS board.
Is there any other way to compile on x86 for mips board.
Thanks and Regards
Subhra Prakash Giri
On Fri, Mar 6, 2020 at 6:43 PM Henning Westerholt <hw(a)skalatan.de<mailto:hw@skalatan.de>> wrote:
Hi Subhra,
I meant with native platform – to test compilation directly on the MIPS board, not sure if you understood it the same way.
Cheers,
Henning
From: subhra giri <subhraprakash79(a)gmail.com<mailto:subhraprakash79@gmail.com>>
Sent: Friday, March 6, 2020 1:11 PM
To: Henning Westerholt <hw(a)skalatan.de<mailto:hw@skalatan.de>>
Cc: sr-dev(a)lists.kamailio.org<mailto:sr-dev@lists.kamailio.org>
Subject: Re: [sr-dev] Regarding MIPS Compilation
Dear Henning
Executing "make cfg " gives below output
[root@www kamailio-5.3.2]# make cfg
make -C src/ cfg
target architecture <mips64>, host architecture <x86_64>
----------------------------------------------------------------------------------------------------------------------------------------------------------
In native platform it is compiling successfully. But giving problem for target platform i.e mips64-octeon-linux.
Please help me with steps for mips compilation
Thanks and Regards
Subhra Prakash Giri