### Description
SQL queries that do not return a result set (such as INSERT, DELETE, UPDATE) always report errors when using db_unixodbc. The query succeeds, but the log indicates a failure.
#### Reproduction
Use db_unixodbc.so for sql queries.
Issue a valid query such as INSERT that is not expected to return a result set.
#### Log Messages
ERROR: db_unixodbc [res.c:52]: db_unixodbc_get_columns(): no columns returned from the query
ERROR: db_unixodbc [res.c:253]: db_unixodbc_convert_result(): getting column names failed
ERROR: db_unixodbc [dbase.c:271]: db_unixodbc_store_result(): failed to convert result
ERROR: <core> [db_query.c:197]: db_do_raw_query(): error while storing result
ERROR: sqlops [sql_api.c:297]: sql_do_query(): cannot do the query [DELETE FROM mytable WHERE id = 1]
### Additional Information
Kamailio Version 5.5.0
This issue was also reported to SR-users, but that user did not open an issue. (See https://lists.kamailio.org/pipermail/sr-users/2018-March/100581.html)
--
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/2810
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
If there is no content to be filled in a section, the entire section can be removed.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment).
-->
### Description
I enabled mhomed=1 as well as ip_free_bind=1, but kamailio does not recognize that there is internal and external traffic.
For example I also enabled modparam("rr", "enable_double_rr", 1), but the 2 Record-Routes both have the external IP.
In addition fix_nated_contact() and fix_nated_sdp don't work because they think all traffic is coming from the external IP.
<!--
Explain what you did, what you expected to happen, and what actually happened.
-->
### Troubleshooting
I tried a lot of things.
#### Reproduction
Set up a server with keepalived and a virtual IP and use any standard NAT config and it won't work.
<!--
If the issue can be reproduced, describe how it can be done.
-->
#### Debugging Data
<!--
If you got a core dump, use gdb to extract troubleshooting data - full backtrace,
local variables and the list of the code at the issue location.
gdb /path/to/kamailio /path/to/corefile
bt full
info locals
list
If you are familiar with gdb, feel free to attach more of what you consider to
be relevant.
-->
```
(paste your debugging data here)
```
#### Log Messages
<!--
Check the syslog file and if there are relevant log messages printed by Kamailio, add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
(paste your log messages here)
```
#### SIP Traffic
<!--
If the issue is exposed by processing specific SIP messages, grab them with ngrep or save in a pcap file, then add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
(paste your sip traffic here)
```
### Possible Solutions
I thought that ip_free_bind=1 would fix this issue, but it does not seem to have any effect.
<!--
If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix.
-->
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
(paste your output here)
```
* **Operating System**:
<!--
Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
Kernel details (output of `lsb_release -a` and `uname -a`)
-->
```
(paste your output here)
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3002
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3002(a)github.com>
### Description
Similar to pua:default_expires, a default expire value could be added for subscriptions.
The default expiration values are now hard coded for presence modules, in presence_*/add_events.c files.
### Expected behavior
Default expiration value that is configurable.
#### Actual observed behavior
Default expiration value is 3600.
### Possible Solutions
Adding a parameter presence : default_expires and use it in all presence_*/add_events.c files.
I can implement this myself.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2996
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/2996(a)github.com>