Yes, but that module does not seem to provide that provide that functionality
either.
--
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/2895#issuecomment-950362453___
### Description
I am using kazoo-module for connecting Kamailio to RabbitMQ and publishing
messages to several consumers.
Now I´d like to extend my setup to a more sophisticated routing based on a
consistent hash-exchange
(https://github.com/rabbitmq/rabbitmq-consistent-hash-exchange), while
r
Thank you very much for the clarification. Maybe it would be good to add it to
the documentation.
The original description of the issue is for sure invalid, and can be
closed/rejected.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it
Thanks for that clarification - this is what I observed ;-)
>From this description in the module's documentation:
> TOS=... - change the IP TOS value for all outgoing RTP packets within the
> entire call in both directions. Only honoured in an “offer”, ignored for an
> “answer”. Valid values ar
### Description
Altough setting TOS to -1, the TOS-header of the outgoing RTP stream is always
set to the default TOS (184, resp 0xb0).
### Troubleshooting
Reproduction
Use following flags in rtpengine_manage:
`rtpengine_manage("ICE=remove record-call=on call-id=$avp(correlationId)
TOS=-1
Thanks for your fast response!
Do you maybe see any other solution/workaround that allows consuming messages
from the event-exchange-plugin?
--
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/kamaili
### Description
Consuming messages without message body fails due to a JSON parsing error:
```
ERROR: kazoo [kz_json.c:287]: kz_json_parse(): Error parsing json: unexpected
end of data
ERROR: kazoo [kz_json.c:288]: kz_json_parse():
ERROR: kazoo [kz_amqp.c:2960]: kz_amqp_send_worker_event(): error
Just opened https://github.com/kamailio/kamailio/pull/1706 - as this is my
first pull request at all, I hope I did everything correctly ...
--
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
…ailio/kamailio/issues/1681
Pre-Submission Checklist
- [ ] 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)
- [
Thanks for your suggestions. I first tried the periodic timer, but I somehow
did not get it working for the child-processes: altough I started a timer in
each child, and the timer-method was even executed per child, it was always
executed in the same process (verified with getpid()), so that the
Hi,
thanks for the responses.
While I agree that the default behavior makes fully sense for most (or nearly
all) modules, still there are usecases where a more tolerant handling would be
nice.
In my case, this is a multi-node homer-installation (as advised here:
https://github.com/sipcapture/ho
### Description
I´m using kamailio´s sqlops-module on a postgresql database.
If the database server gets unreachable during operation, sqlops detects this
and tries to reconnect:
```
14:40:48.784 WARNING: db_postgres [km_dbase.c:259]: db_postgres_submit_query():
postgres query command failed, co
The module sipcapture provides the modparams "custom_field1_header" to
"custom_field3_header", to store the content of up to three arbitrary header
fields as separate columns in the database. They can be used as all other
"standard" columns in homer.
However I found out that searching/filtering
13 matches
Mail list logo
