Hello,
I am considering to release Kamailio v5.1.10 on Thursday, Jan 30, 2020,
to mark the end of official packaging from branch 5.1. At this moment
the last two stable branches are 5.2 and 5.3.
If anyone is aware of some commits for fixes that should be backported
to branch 5.1, write to sr-dev.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com
Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com
Changes to example files for PCSCF in misc/examples/ims to make funcitional with current stable version.
<!--
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
Changes to example files for PCSCF in misc/examples/ims to make funcitional with current stable version.
Changes:
- Loading IPsec module prior to IMS Usrloc PCSCF (Now required)
- removed modparam("ims_usrloc_pcscf", "hashing_type", 2) from example (This parameter was removed some time ago)
- Fix to formatting of single MySQL connection to work in current version
- Bind to any IP by default
- Dispatcher parameters only loaded if required
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2203
-- Commit Summary --
* misc: examples: IMS PCSCF kamailio.cfg update
* misc: examples: IMS PCSCF pcscf.cfg update
-- File Changes --
M misc/examples/ims/pcscf/kamailio.cfg (6)
M misc/examples/ims/pcscf/pcscf.cfg.sample (12)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2203.patchhttps://github.com/kamailio/kamailio/pull/2203.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/2203
hello all
we are trying to rewrite our code to lua kemi, and we have found some
issues/questions until we would like to share with you.
-module call_obj not exported, we have tested a patch for the module to
export the functions to kemi, which seems works fine
-KSR.xlog.xinfo seems not able to select a facility as we currently can
like xlog("LOG_LOCAL7", "L_NOTICE", "$var(xxxx)");
-module sipt not exported yet, must use ksr.x.modf ? will be exported for a
future version?
-on 5.3.0-dev5 we don't see the KSR.dialog.var_sets() and
KSR.dialog.var_get/e/w() functions in the code, so we do use KSR.pv
functions to set and retrieve those dialog vars. However i see them on
master branch. Which kamailio release would have them?
-sdpops function sdp_with_codecs_by_name seems to not me exported, is it on
a todo list?
-textops module, missing remove_hf and append_hf functions exported. We
already did a patch for the remove_hf, despite we could work with textopsx
remove_hf_value function to get the almost the same functionality.
However, with append_hf i'm having some more issues.
We cannot use modf to exec those funtions, we get something like
For ---> KSR.x.modf("append_hf", "User-Agent: test", "To");
I get something like ----> Jun 27 07:19:16 proxy-1
/usr/local/kamailio/sbin/kamailio[5525]: ERROR: app_lua [app_lua_sr.c:188]:
lua_sr_modf(): function 'append_hf' has fixup - cannot be used
I could append a new header and not only at the end of the message by
replacing a header called the same way, by doing something like
KSR.textopsx.insert_hf_value("header", "value");
KSR.textopsx.remove_hf_value("header[-1]");
but i'm not able to insert a header after another different one like we can
do with append_hf("header:value", "To") for instance.
Is it expected to have it on a next commit those append_hf and remove_hf
exported.
Would we do a pull request with the ki_remove_hf we already have and the
call_obj functions too? We can check to export append_hf too if it's not
planned to be done
thanks a lot and regards
david
- Added more accurate contact comparison when
sending NOTIFY to a subscriber.
<!-- 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/2202
-- Commit Summary --
* ims_reqistrar_scscf: Fix bug with multi-notifications
-- File Changes --
M src/modules/ims_registrar_scscf/registrar_notify.c (17)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2202.patchhttps://github.com/kamailio/kamailio/pull/2202.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/2202
Hi all,
I hope this is the right group for my question. It's related to a Kamailio build. I tried to build Kamailio in RHEL7 and I encountered some problems I could fix it locally. I tried to find any email in the user and the developer Kamailio groups by skimming the mails, however there is no clue about it. I need to know your opinion about it.
The build error is:
*******************************************************************
CC (gcc) [M app_sqlang.so] app_sqlang_api.o
CC (gcc) [M app_sqlang.so] app_sqlang_kemi_export.o
CC (gcc) [M app_sqlang.so] app_sqlang_mod.o
make --no-print-directory -C ./squirrel/squirrel SQMARCH64="-m64" CC_EXTRA_FLAGS="-fPIC" \
OUT="../../libsquirrel.a" sq64
gcc -O2 -m64 -D_SQ64 -fno-exceptions -fno-rtti -Wall -fno-strict-aliasing -c sqapi.cpp sqbaselib.cpp sqfuncstate.cpp sqdebug.cpp sqlexer.cpp sqobject.cpp sqcompiler.cpp sqstate.cpp sqtable.cpp sqmem.cpp sqvm.cpp sqclass.cpp -I../include -I. -Iinclude -fPIC
In file included from sqpcheader.h:14:0,
from sqapi.cpp:4:
/usr/include/c++/4.8.2/new:39:28: fatal error: bits/c++config.h: No such file or directory
#include <bits/c++config.h>
^
compilation terminated.
...
******************************************************************
As you can see above, the make command stopped in app_sqlang.so stage due to an including error. These problems are classic for builds on RHEL7 for a lot of tools we need to compile. So, I'm familiar with it and fixed it easily:
I just appended "-I/usr/include/c++/4.8.2/i686-redhat-linux/" in "INCZ?= -I$(SQUIRREL)/include -I." row for both ./src/modules/app_sqlang/squirrel/sqstdlib/Makefile and ./src/modules/app_sqlang/squirrel/squirrel/Makefile
Then Kamailio build is finished properly.
Uname output is here:
Linux gearbox07 3.10.0-862.6.3.el7.x86_64 #1 SMP Fri Jun 15 17:57:37 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux
My question is that if it's normal or not. Is there anybody who built Kamailio on RHEL7 environment here? Would you help me to understand the situation, please?
Thanks...
S. Cumhur Karahan
[http://s.turkcell.com.tr/SiteAssets/Genel/mail-imza.jpg] <https://tvplus.com.tr/>
Bu elektronik posta ve onunla iletilen butun dosyalar sadece gondericisi tarafindan almasi amaclanan yetkili gercek ya da tuzel kisinin kullanimi icindir. Eger soz konusu yetkili alici degilseniz bu elektronik postanin icerigini aciklamaniz, kopyalamaniz, yonlendirmeniz ve kullanmaniz kesinlikle yasaktir ve bu elektronik postayi derhal silmeniz gerekmektedir.
TURKCELL bu mesajin icerdigi bilgilerin do?rulu?u veya eksiksiz oldugu konusunda herhangi bir garanti vermemektedir. Bu nedenle bu bilgilerin ne sekilde olursa olsun iceriginden, iletilmesinden, alinmasindan ve saklanmasindan sorumlu degildir. Bu mesajdaki gorusler yalnizca gonderen kisiye aittir ve TURKCELLin goruslerini yansitmayabilir
Bu e-posta bilinen butun bilgisayar viruslerine karsi taranmistir.
________________________________
This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient you are hereby notified that any dissemination, forwarding, copying or use of any of the information is strictly prohibited, and the e-mail should immediately be deleted.
TURKCELL makes no warranty as to the accuracy or completeness of any information contained in this message and hereby excludes any liability of any kind for the information contained therein or for the information transmission, reception, storage or use of such in any way whatsoever. The opinions expressed in this message belong to sender alone and may not necessarily reflect the opinions of TURKCELL.
This e-mail has been scanned for all known computer viruses.
Hi ,
I have a cloud server, when I make call from a sip phone (registered with
kamailio),
in the INVITE header I am seeing the via header with public IP, is there
any way that I can modify via header to send only the private IP.
Please let me know, is it possible to replace.
[image: image.png]
the via headers that kamailio is sending to sip-gateway is
sip-phone ip:192.168.113.112
Via: SIP/2.0/UDP *221.20.20.12:5060 <http://221.20.20.12:5060>*
;branch=z9hG4bKaa6a.14c65f5675077ae7b0df70b02516979b.0
Via: SIP/2.0/UDP 192.168.113.112 :50386;received= 192.168.113.112
;branch=z9hG4bK-d87543-550b984016109617-1--d87543-;rport=50386
how to modify the first via header to have private-IP instead of public-IP..
I tried all the replace functions but it is not working.
--
Thanks and regards
Vinod.M.N