Why is insert_update doing nothing in Kamailio db insert_update ?
As explained in the following article the design of "UPSERT" in
PostgreSQL requires to be explicit about the constraint on which
we accept to do update modification to Kamailio database framework/API
would be required to expose
### Description
When using the dialog track_cseq_updates feature (to increase the cseq for
calls that are authenticated using the uac uac_auth) together with topos, it
seems like a reply is not handled by topos.
Log Messages
I have a 2219 line debug log demonstrating this, i can supply
Module: kamailio
Branch: master
Commit: b2e8a193d086df58437c5b4d4df5dce684d88c61
URL:
https://github.com/kamailio/kamailio/commit/b2e8a193d086df58437c5b4d4df5dce684d88c61
Author: Juha Heinanen
Committer: Juha Heinanen
Date: 2017-03-18T11:40:56+02:00
Hello,
yes, you can create PR for backporting, it would be the easiest way to
review and see if anything gets broken.
As we just released 5.0, I expect that 5.1 will be sometime in autumn or
later.
Cheers,
Daniel
On Thu, Mar 16, 2017 at 12:53 PM, Luis Azedo wrote:
> Hi
Hello,
my (long term) plans were to add a way to obfuscate the Call-ID (more for
the cases when it includes an IP address), no plans for the moment to
generate new call-id for each branch in B-side. But contributions are
welcome, of course...
Cheers,
Daniel
On Fri, Mar 17, 2017 at 10:29 AM,
It was a good catch after all, indeed it should not segfault and now should be
fixed.
Yesterday I didn't have time to add here the comments about it, but as jsonrpcs
replaced the mi_fifo, its default transports were changed in 5.0, given that
xhttp is not loaded by default.
I also added a