I built latest master on Debian stretch and got the compiler warnings
below.
-- Juha
---------------------------------------------------------------------------
CC (gcc) [M ipops.so] ip_parser.o
ip_parser.c:18:18: warning: 'ip_parser_en_main' defined but not used [-Wunused-const-variable=]
static const int ip_parser_start = 1;
^~~~~~~~~~~~~~~~~
ip_parser.c:16:18: warning: 'ip_parser_error' defined but not used [-Wunused-const-variable=]
^
ip_parser.c:15:18: warning: 'ip_parser_first_final' defined but not used [-Wunused-const-variable=]
/** Data **/
^
CC (gcc) [M ipops.so] rfc1918_parser.o
rfc1918_parser.c:19:18: warning: 'rfc1918_parser_en_main' defined but not used [-Wunused-const-variable=]
static const int rfc1918_parser_en_main = 1;
^~~~~~~~~~~~~~~~~~~~~~
rfc1918_parser.c:17:18: warning: 'rfc1918_parser_error' defined but not used [-Wunused-const-variable=]
static const int rfc1918_parser_error = 0;
^~~~~~~~~~~~~~~~~~~~
rfc1918_parser.c:16:18: warning: 'rfc1918_parser_first_final' defined but not used [-Wunused-const-variable=]
static const int rfc1918_parser_first_final = 28;
^~~~~~~~~~~~~~~~~~~~~~~~~~
....
CC (gcc) [M tls.so] tls_locking.o
tls_locking.c:98:13: warning: 'locking_f' defined but not used [-Wunused-function]
static void locking_f(int mode, int n, const char* file, int line)
^~~~~~~~~
tls_locking.c:83:13: warning: 'dyn_destroy_f' defined but not used [-Wunused-function]
static void dyn_destroy_f(struct CRYPTO_dynlock_value *l,
^~~~~~~~~~~~~
tls_locking.c:65:13: warning: 'dyn_lock_f' defined but not used [-Wunused-function]
static void dyn_lock_f(int mode, struct CRYPTO_dynlock_value* l,
^~~~~~~~~~
tls_locking.c:42:37: warning: 'dyn_create_f' defined but not used [-Wunused-function]
static struct CRYPTO_dynlock_value* dyn_create_f(const char* file, int line)
^~~~~~~~~~~~
...........
C (gcc) [M tls.so] tls_init.o
tls_init.c: In function 'init_ssl_methods':
tls_init.c:377:2: warning: 'TLSv1_client_method' is deprecated [-Wdeprecated-declarations]
ssl_methods[TLS_USE_TLSv1_cli - 1] = TLSv1_client_method();
^~~~~~~~~~~
In file included from /usr/include/openssl/ct.h:13:0,
from /usr/include/openssl/ssl.h:61,
from tls_init.c:45:
/usr/include/openssl/ssl.h:1598:1: note: declared here
DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_client_method(void)) /* TLSv1.0 */
^
tls_init.c:378:2: warning: 'TLSv1_server_method' is deprecated [-Wdeprecated-declarations]
ssl_methods[TLS_USE_TLSv1_srv - 1] = TLSv1_server_method();
^~~~~~~~~~~
In file included from /usr/include/openssl/ct.h:13:0,
from /usr/include/openssl/ssl.h:61,
from tls_init.c:45:
/usr/include/openssl/ssl.h:1597:1: note: declared here
DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_server_method(void)) /* TLSv1.0 */
^
tls_init.c:379:2: warning: 'TLSv1_method' is deprecated [-Wdeprecated-declarations]
ssl_methods[TLS_USE_TLSv1 - 1] = TLSv1_method();
^~~~~~~~~~~
In file included from /usr/include/openssl/ct.h:13:0,
from /usr/include/openssl/ssl.h:61,
from tls_init.c:45:
/usr/include/openssl/ssl.h:1596:1: note: declared here
DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_method(void)) /* TLSv1.0 */
^
tls_init.c:382:2: warning: 'TLSv1_1_client_method' is deprecated [-Wdeprecated-declarations]
ssl_methods[TLS_USE_TLSv1_1_cli - 1] = TLSv1_1_client_method();
^~~~~~~~~~~
In file included from /usr/include/openssl/ct.h:13:0,
from /usr/include/openssl/ssl.h:61,
from tls_init.c:45:
/usr/include/openssl/ssl.h:1604:1: note: declared here
DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_1_client_method(void)) /* TLSv1.1 */
^
tls_init.c:383:2: warning: 'TLSv1_1_server_method' is deprecated [-Wdeprecated-declarations]
ssl_methods[TLS_USE_TLSv1_1_srv - 1] = TLSv1_1_server_method();
^~~~~~~~~~~
In file included from /usr/include/openssl/ct.h:13:0,
from /usr/include/openssl/ssl.h:61,
from tls_init.c:45:
/usr/include/openssl/ssl.h:1603:1: note: declared here
DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_1_server_method(void)) /* TLSv1.1 */
^
tls_init.c:384:2: warning: 'TLSv1_1_method' is deprecated [-Wdeprecated-declarations]
ssl_methods[TLS_USE_TLSv1_1 - 1] = TLSv1_1_method();
^~~~~~~~~~~
In file included from /usr/include/openssl/ct.h:13:0,
from /usr/include/openssl/ssl.h:61,
from tls_init.c:45:
/usr/include/openssl/ssl.h:1602:1: note: declared here
DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_1_method(void)) /* TLSv1.1 */
^
tls_init.c:388:2: warning: 'TLSv1_2_client_method' is deprecated [-Wdeprecated-declarations]
ssl_methods[TLS_USE_TLSv1_2_cli - 1] = TLSv1_2_client_method();
^~~~~~~~~~~
In file included from /usr/include/openssl/ct.h:13:0,
from /usr/include/openssl/ssl.h:61,
from tls_init.c:45:
/usr/include/openssl/ssl.h:1610:1: note: declared here
DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_2_client_method(void)) /* TLSv1.2 */
^
tls_init.c:389:2: warning: 'TLSv1_2_server_method' is deprecated [-Wdeprecated-declarations]
ssl_methods[TLS_USE_TLSv1_2_srv - 1] = TLSv1_2_server_method();
^~~~~~~~~~~
In file included from /usr/include/openssl/ct.h:13:0,
from /usr/include/openssl/ssl.h:61,
from tls_init.c:45:
/usr/include/openssl/ssl.h:1609:1: note: declared here
DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_2_server_method(void)) /* TLSv1.2 */
^
tls_init.c:390:2: warning: 'TLSv1_2_method' is deprecated [-Wdeprecated-declarations]
ssl_methods[TLS_USE_TLSv1_2 - 1] = TLSv1_2_method();
^~~~~~~~~~~
In file included from /usr/include/openssl/ct.h:13:0,
from /usr/include/openssl/ssl.h:61,
from tls_init.c:45:
/usr/include/openssl/ssl.h:1608:1: note: declared here
DEPRECATEDIN_1_1_0(__owur const SSL_METHOD *TLSv1_2_method(void)) /* TLSv1.2 */
^
Hello,
I think it is time to migrate the mailing lists under kamailio.org
domain, respectively use lists.kamailio.org.
The lists.sip-router.org will still work, but lists.kamailio.org is
intended to become the primary domain for mailing lists.
The sip-router.org was the quick solution for integrating Kamailio and
SER in one project back in 2008, when kamailio.org and iptel.org still
needed to be operated for a while as independent projects. For few years
now, Kamailio is the only project name that is used out there and it
will make operating everything a bit smoother, more coherent and also
avoid eventual confusions for people new into the project.
As a matter of fact, we even had a small incident few weeks ago -- due
to split management of sip-router.org and DNS registration expire
notifications going to an email address on a different server than
kamailio.org, the domain was expired for few hours (although it was kept
on hold by registrar) and mailing lists started to be unavailable.
Fortunately that was discovered and fixed in time.
The names will stay the same sr-users and sr-dev, just primary domain
will be using kamailio.org (which should 'hopefully' work even now, as
this email was addressed with mixed sr-dev(a)lists.sip-router.org and
sr-users(a)lists.kamailio.org).
If anyone has different opinions or suggestions, let's discuss them!
Cheers,
Daniel
--
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - May 22-24 (USA) - www.asipto.com
Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com
I noticed that function result cannot be directly tested in
if-statement:
if (func_x() == y) ...
Why is that? Should I open a feature request or is it a no-go?
-- Juha
Module: kamailio
Branch: master
Commit: 617a9cfe72ac613606990a93af648bd12b1fc2d0
URL: https://github.com/kamailio/kamailio/commit/617a9cfe72ac613606990a93af648bd…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2017-04-10T14:01:21+02:00
modules: readme files regenerated - dialog ... [skip ci]
---
Modified: src/modules/dialog/README
---
Diff: https://github.com/kamailio/kamailio/commit/617a9cfe72ac613606990a93af648bd…
Patch: https://github.com/kamailio/kamailio/commit/617a9cfe72ac613606990a93af648bd…
---
diff --git a/src/modules/dialog/README b/src/modules/dialog/README
index b5eb202..f07e966 100644
--- a/src/modules/dialog/README
+++ b/src/modules/dialog/README
@@ -1456,10 +1456,9 @@ redlg_setflag("1");
Meaning of the parameters is as follows:
* side - where to send the BYE. It can be: 'caller', 'callee', or
- both.
+ 'all' (send to both sides).
- This function can be used from BRANCH_ROUTE, REQUEST_ROUTE,
- ONREPLY_ROUTE and FAILURE_ROUTE.
+ This function can be used from ANY_ROUTE.
Example 1.64. dlg_bye usage
...
Module: kamailio
Branch: master
Commit: 6b9e63f4e1948b53ce2b986c495085e34dc83165
URL: https://github.com/kamailio/kamailio/commit/6b9e63f4e1948b53ce2b986c495085e…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2017-04-10T13:51:38+02:00
dialog: clarification for dlg_bye() parameters in docs
---
Modified: src/modules/dialog/doc/dialog_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/6b9e63f4e1948b53ce2b986c495085e…
Patch: https://github.com/kamailio/kamailio/commit/6b9e63f4e1948b53ce2b986c495085e…
---
diff --git a/src/modules/dialog/doc/dialog_admin.xml b/src/modules/dialog/doc/dialog_admin.xml
index af1443e..88c6ed7 100644
--- a/src/modules/dialog/doc/dialog_admin.xml
+++ b/src/modules/dialog/doc/dialog_admin.xml
@@ -1753,13 +1753,12 @@ redlg_setflag("1");
<itemizedlist>
<listitem>
<para><emphasis>side</emphasis> - where to send the BYE. It can be:
- 'caller', 'callee', or both.
+ 'caller', 'callee', or 'all' (send to both sides).
</para>
</listitem>
</itemizedlist>
<para>
- This function can be used from BRANCH_ROUTE,
- REQUEST_ROUTE, ONREPLY_ROUTE and FAILURE_ROUTE.
+ This function can be used from ANY_ROUTE.
</para>
<example>
<title><function>dlg_bye</function> usage</title>