#### Pre-Submission Checklist
- [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:
- [X] PR should be backported to stable branches
- [X] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
LCR module exports information about selected gateways in flags and tag AVPs if you define corresponding modparams (flags_avp and tag_avp).
This PR exports a similar optional AVP that stores the id of the rule that selected each gateway. For that, a new modparam is added (rule_id_avp).
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/1546
-- Commit Summary --
* lcr: export rule_id_avp with matching rule id
-- File Changes --
M src/modules/lcr/doc/lcr_admin.xml (34)
M src/modules/lcr/lcr_mod.c (62)
M src/modules/lcr/lcr_mod.h (1)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/1546.patchhttps://github.com/kamailio/kamailio/pull/1546.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/1546
Am Sonntag, 27. Mai 2018, 15:17:23 CEST schrieb Igor Olhovskiy:
> Is http://www.asipto.com/pub/kamailio-devel-guide/ still holds actual info?
> Cause it’s mostly for 3.3 version, and now is 5.1
>
> And where to read, except source code of course, about how to develop
> modules for Kamailio?
(adding sr-dev as CC, as its a development question)
Hello Igor,
I would say that most of the core concepts (architecture, memory management, pseudo-
variables etc..) are still valid.
In my opinion the value of such a guide is not that it provides up to date information e.g. to
the specific layout of header files, but instead gives an overview about the concepts and
provide pointer to the appropriate parts of development.
About the module development question - you probably already saw the chapter 16.9
about module development in this guide. This is a good start.
Then look to some more simple modules like cfgutils or siputils to learn how to interact
exactly with the core, the cfg, SIP msg etc..
For a new database module the db_mysql module is a good starting point.
If you have more specific question, just ask them on our developer list sr-dev.
Best regards,
Henning
Hello,
A kamailio.org server maintenance work will be done today at 18:00 CEST.
There will be some minutes of downtime (should be less than 5') of the
following main services: website (including the wiki) and mailing lists.
Regards,
Oriol.
Hi.
I'm building small HTTP API using kemi lua on kamailio 5.1
version:
kamailio -v
version: kamailio 5.1.2 (x86_64/linux)
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: unknown
compiled on 18:16:53 Apr 7 2018 with gcc 4.8.5
On the system
Linux CentOS-74-64-minimal 3.10.0-693.17.1.el7.x86_64 #1 SMP Thu Jan 25 20:13:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
When i sending xhttp_reply I getting wrong code that kamailio sends to the client instead of code I use
Im used as this exmaple as template
int xhttp_reply(int code, str "reason", str "ctype", str "body")
as classic (with code in string)
`KSR.xhttp.xhttp_reply("200", "OK", application/json, "")`
So in both cases I getting next trouble:
When i trying to set params to the xhttp_reply i getting this in the log (on debug layer)
DEBUG: app_lua [app_lua_sr.c:1500]: sr_kemi_lua_exec_func_ex(): param[0] for: xhttp_reply is int: 200
DEBUG: app_lua [app_lua_sr.c:1496]: sr_kemi_lua_exec_func_ex(): param[1] for: xhttp_reply is str: OK
DEBUG: app_lua [app_lua_sr.c:1496]: sr_kemi_lua_exec_func_ex(): param[2] for: xhttp_reply is str: application/json
but next string I shows
DEBUG: xhttp [xhttp_mod.c:443]: xhttp_send_reply(): sending out response: 161110576 OK
This first 3 digits at the reslonse I see
**161** 110576
Digits are random, as positive as negative (with "-" at the start)
--
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/1544