Hi all,
MQTT module does not build correctly on old debian'ish distributions.
Jenkins reported FTBS errors in wheezy, precise and trusty this night.
libmosquitto is very old there and has IMHO no or very limited TLS support.
It's my first module, so what's the policy? Should i add a compile
Module: kamailio
Branch: master
Commit: 81852e5ba1fa6983df44f591c40154ea5fcef6b8
URL:
https://github.com/kamailio/kamailio/commit/81852e5ba1fa6983df44f591c40154ea5fcef6b8
Author: Thomas Weber
Committer: Thomas Weber
Date: 2020-01-03T17:05:14+01:00
mqtt: add tls support
---
Modified: src
Module: kamailio
Branch: master
Commit: 9b3a7227e2dc12823be28bf1b261de1ebdb3f954
URL:
https://github.com/kamailio/kamailio/commit/9b3a7227e2dc12823be28bf1b261de1ebdb3f954
Author: Thomas Weber
Committer: Thomas Weber
Date: 2020-01-02T13:40:55+01:00
mqtt: module to support mqtt pubsub messaging
Module: kamailio
Branch: master
Commit: ea699419df555b4453e1eb96659cfec8912ac3bc
URL:
https://github.com/kamailio/kamailio/commit/ea699419df555b4453e1eb96659cfec8912ac3bc
Author: Thomas Weber
Committer: Thomas Weber
Date: 2020-01-03T17:31:34+01:00
mqtt: expose received message qos level via
I added TLS support in commit 81852e5. The documentation is enhanced as well.
It's now possible to have a plain connection as well as TLS with configurable
method, ciphers, client certificate and - if desired - disabled server cert
checks.
Parameters are more or less directly forwarded to
towe75 commented on this pull request.
> +
+ If defined, the module calls event_route[mqtt:message] when a message
+ is received from the broker.
+
+ All incoming messages are handled in a single mqtt dispatcher process.
+...
+event_route[mqtt:message] {
+xlog("mqtt message
@oej: it would IMHO only be simple for "static" subscriptions like
"kamailio/foo" -> on_mqtt_foo().
But what about wildcard subscriptions like "kamailio/+/unregister" or
"kamailio/#" ? I can, of course, forbit these mappings by some validation rule
but a cleaner solution would be to
@oej thank you for the **really** quick review (only a couple of minutes after
submission).
I will check the effort for TLS support. It should not be very high given the
fact that libmosquitto exposes a highlevel API for it.
Regarding event_route per subscription: it's a nice idea and saves
towe75 commented on this pull request.
> +
+ If defined, the module calls event_route[mqtt:message] when a message
+ is received from the broker.
+
+ All incoming messages are handled in a single mqtt dispatcher process.
+...
+event_route[mqtt:message] {
+xlog("mqtt message
!-- 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
### Description
### Troubleshooting
Reproduction
Point your browser to https://deb.kamailio.org
Debugging Data
The lets encrypt certificate expired on 2019-11-30
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it
Perfect, thank you.
--
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/1944#issuecomment-489013182___
Kamailio (SER) - Development Mailing
### Description
app_python and, in some places, app_python3 handles KEMI calls with 4 and more
parameters incorrectly. It uses "or" operations instead of "and" and thus it
will always tries to convert the call into a "str-str-str-str" invocation.
Also it's missing a "ssii" variant for calling
### Description
The KEMI function htable.sht_setx() allows us to set a expiration parameter
"exval":
`int sht_setxs(str "htname", str "itname", str "itval", int exval)`
Setting "exval" shows no effect, however.
### Possible Solutions
It seems that the "exval" parameter is not passed into
@miconda great! Glad i could help.
I will try it out in a few days. Cu at Kamailio World
Cheers
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I prepared some files in a zip:
https://drive.google.com/open?id=1qVap6BhbGpJwHL-Gf3aUCBOSSbekscs5 including
some instructions on how to reproduce. Kamailio config is down to 15 lines (5
modules only) and the python script is also bare bones with about 30 lines.
It boils down to:
1. setup
Daniel, i will shrink the script as much as possible and then i can surely
provide a full test case incl. sipp scenarios. Give me a few days, though.
By now i can say that this is the only place where i used a "@hf_value"
selector. Maybe the segfault occurs also if one uses it in a request
@miconda, i was able to isolate the problem to a single line of python script.
I did so by writing two sipp scripts to simulate our asterisk and the isp and
subsequently removing logic from the kamailio script.
Segfault happens when i use this selector within ksr_reply_route:
Ok, i attached to a random child and i get the expected output:
```
(gdb) p ksr_route_locks_set
$1 = (rec_lock_set_t *) 0x0
(gdb) p *ksr_route_locks_set
Cannot access memory at address 0x0
```
Strange. Can i check for some specific included module or is there some other
global config that
Sorry, i overlooked it.
Output is:
```
(gdb) p ksr_route_locks_set
$1 = (rec_lock_set_t *) 0x7c0100
(gdb) p *ksr_route_locks_set
Cannot access memory at address 0x7c0100
```
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it
@miconda not sure if it's useful but i tried to start kamailio with the
mentioned route_locks_size but could not get it up (tried with values
1,2,8,16,20).
```
Starting Kamailio (OpenSER) - the Open Source SIP Server...
Feb 01 09:47:57 ifens224 kamailio[11130]: INFO: pv [pv_shv.c:60]:
No, this parameter is not set, it should have the default value.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Hi,
we have crashes on some of our kamailio hosts:
```
/usr/sbin/kamailio[1833]: CRITICAL: [core/pass_fd.c:277]: receive_fd():
EOF on 9
/usr/sbin/kamailio[1820]: ALERT: [main.c:738]: handle_sigs(): child
process 1831 exited by a signal 6
/usr/sbin/kamailio[1820]: ALERT: [main.c:741]:
23 matches
Mail list logo
