I built K master and tried to use 5.2 config. That resulted in error:
Apr 30 15:47:10 salmon /usr/bin/sip-proxy[1659]: ERROR: siptrace [siptrace.c:908]: w_sip_trace3(): no duplicate_uri modparam nor duplicate uri sip_trace() argument provided!
I think it has been practice that backwards compatibility is provided by the next version.
Juha Heinanen writes:
I built K master and tried to use 5.2 config. That resulted in error:
Apr 30 15:47:10 salmon /usr/bin/sip-proxy[1659]: ERROR: siptrace [siptrace.c:908]: w_sip_trace3(): no duplicate_uri modparam nor duplicate uri sip_trace() argument provided!
I think it has been practice that backwards compatibility is provided by the next version.
This is my 5.2 config:
# -- siptrace params modparam("siptrace", "db_url", "MYSQL_SIP_PROXY_USAGE_URL") modparam("siptrace", "trace_flag", TRACE)
# -- function call sip_trace();
I has to work as before without messing up with any duplicate stuff.
Hello Juha,
I think we don't have a policy that mandates strict backward compatiblity going from one major version to another. This only applies to minor version upgrades.
Have a look e.g. to this link, from 5.1 to 5.2 we also broke the compatibility for some modules there (e.g. dispatcher).
https://www.kamailio.org/wiki/install/upgrade/5.1.x-to-5.2.0
That said, we should of course try to not break configurations without a proper reason. All backward incompatible changes needs to be documented in the migration document for the upcoming 5.3 version.
Cheers,
Henning
Am 30.04.19 um 14:51 schrieb Juha Heinanen:
I built K master and tried to use 5.2 config. That resulted in error:
Apr 30 15:47:10 salmon /usr/bin/sip-proxy[1659]: ERROR: siptrace [siptrace.c:908]: w_sip_trace3(): no duplicate_uri modparam nor duplicate uri sip_trace() argument provided!
I think it has been practice that backwards compatibility is provided by the next version.
Kamailio (SER) - Development Mailing List sr-dev@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
On 30.04.19 14:51, Juha Heinanen wrote:
I built K master and tried to use 5.2 config. That resulted in error:
Apr 30 15:47:10 salmon /usr/bin/sip-proxy[1659]: ERROR: siptrace [siptrace.c:908]: w_sip_trace3(): no duplicate_uri modparam nor duplicate uri sip_trace() argument provided!
I think it has been practice that backwards compatibility is provided by the next version.
I looks like an invalid check introduced with the latest development on the module, the sip_trace() should work without duplicate uri because it can write directly to the database. It should be fixed to work without those parameters for module or function.
Cheers, Daniel
https://github.com/kamailio/kamailio/issues/1942
Am 01.05.19 um 13:10 schrieb Daniel-Constantin Mierla:
On 30.04.19 14:51, Juha Heinanen wrote:
I built K master and tried to use 5.2 config. That resulted in error:
Apr 30 15:47:10 salmon /usr/bin/sip-proxy[1659]: ERROR: siptrace [siptrace.c:908]: w_sip_trace3(): no duplicate_uri modparam nor duplicate uri sip_trace() argument provided!
I think it has been practice that backwards compatibility is provided by the next version.
I looks like an invalid check introduced with the latest development on the module, the sip_trace() should work without duplicate uri because it can write directly to the database. It should be fixed to work without those parameters for module or function.
Cheers, Daniel
-
Daniel-Constantin Mierla -
Henning Westerholt -
Juha Heinanen