Hi,
I have a Kamailio v4.3.0 with SVN Rev. c6aa95 running an RLS based presence
setup. Everything works fine when end-user has UDP transport, however, if
user has TCP or TLS transport then i aggregated NOTIFY sent by RLS gives
send error,
--
WARNING: <core> [forward.c:231]: get_send_socket2(): protocol/port mismatch
(forced tls:X.X.X.X:5061, to udp:Y.Y.Y.Y:12345)
--
(X.X.X.X is server IP and Y.Y.Y.Y is end user IP).
Not sure if it is configuration issue or some bug, so posting it to both
mailing list.
Please help.
Thank you.
Hello,
Kamailio SIP Server v4.2.6 stable release is out.
This is a maintenance release of the previous stable branch, 4.2, that
includes fixes since release of v4.2.5. There is no change to database
schema or configuration language structure that you have to do on
installations of v4.2.x. Deployments running previous v4.x.x versions
are strongly recommended to be upgraded to v4.2.6 (or to 4.3.x series).
For more details about version 4.2.6 (including links and guidelines to
download the tarball or from GIT repository), visit:
* http://www.kamailio.org/w/2015/07/kamailio-v4-2-6-released/
RPM, Debian/Ubuntu packages will be available soon as well.
Note: the latest stable branch is 4.3, at this moment with its latest
release v4.3.1. See more details about it at:
* http://www.kamailio.org/w/kamailio-v4-3-0-release-notes/
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/miconda - http://www.linkedin.com/in/miconda
Hello List,
Im planing to update the app_java module to be usable with Oracle Java 8.
Should I do this in a new module, etc. app_java8, or update the existing one? And is the community interested in such a module?
Kind Regards
Jon Schøpzinsky
Firstcom
Module: kamailio
Branch: master
Commit: b0a776b31220fc5e8599288b14ddb9ffccb24c0f
URL: https://github.com/kamailio/kamailio/commit/b0a776b31220fc5e8599288b14ddb9f…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2015-07-31T18:40:31+02:00
registrar: updated the docs for registered(...) function
---
Modified: modules/registrar/README
Modified: modules/registrar/doc/registrar_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/b0a776b31220fc5e8599288b14ddb9f…
Patch: https://github.com/kamailio/kamailio/commit/b0a776b31220fc5e8599288b14ddb9f…
---
diff --git a/modules/registrar/README b/modules/registrar/README
index e3f5a7f..8756816 100644
--- a/modules/registrar/README
+++ b/modules/registrar/README
@@ -891,15 +891,16 @@ lookup_branches("location");
4.4. registered(domain [, uri [, match_option [, match_action]]])
- The function returns true if the AOR in the Request-URI is registered,
- false otherwise. The function does not modify the message being
- process, it neither rewrites the Request-URI if a contact is found nor
- append branches.
+ The function returns true if the AOR in the URI is registered, false
+ otherwise. The function does not modify the message being process, it
+ neither rewrites the Request-URI if a contact is found nor append
+ branches. If uri parameter is not provided, then it considered to be
+ the Request-URI for SIP requests and To-URI for SIP replies.
Meaning of the parameters is as follows:
* domain - Name of table that should be used for the lookup.
- * uri (optional) - SIP URI to do be used instead of R-URI. It can be
- a dynamic string with pseudo-variables.
+ * uri (optional) - SIP URI to do be used instead of Request/To-URI.
+ It can be a dynamic string with pseudo-variables.
* match_option (optional) - flag parameter to restrict contact
search. use reg_xavp_cfg to set the values to compare to.
flag values is as follows:
@@ -911,7 +912,7 @@ lookup_branches("location");
flag values is as follows:
+ 1 - set xavp_rcd with value from matched contact
- This function can be used from REQUEST_ROUTE, FAILURE_ROUTE.
+ This function can be used from ANY_ROUTE.
Example 1.31. registered usage
...
diff --git a/modules/registrar/doc/registrar_admin.xml b/modules/registrar/doc/registrar_admin.xml
index 672cee8..f1c7063 100644
--- a/modules/registrar/doc/registrar_admin.xml
+++ b/modules/registrar/doc/registrar_admin.xml
@@ -1110,10 +1110,12 @@ lookup_branches("location");
<function moreinfo="none">registered(domain [, uri [, match_option [, match_action]]])</function>
</title>
<para>
- The function returns true if the AOR in the Request-URI is
+ The function returns true if the AOR in the URI is
registered, false otherwise. The function does not modify the
message being process, it neither rewrites the Request-URI if a
- contact is found nor append branches.
+ contact is found nor append branches. If uri parameter is not
+ provided, then it considered to be the Request-URI for SIP requests
+ and To-URI for SIP replies.
</para>
<para>Meaning of the parameters is as follows:</para>
<itemizedlist>
@@ -1126,7 +1128,7 @@ lookup_branches("location");
<listitem>
<para>
<emphasis>uri</emphasis> (optional) - SIP URI to do be used instead
- of R-URI. It can be a dynamic string with pseudo-variables.
+ of Request/To-URI. It can be a dynamic string with pseudo-variables.
</para>
</listitem>
<listitem>
@@ -1160,7 +1162,7 @@ lookup_branches("location");
</listitem>
</itemizedlist>
<para>
- This function can be used from REQUEST_ROUTE, FAILURE_ROUTE.
+ This function can be used from ANY_ROUTE.
</para>
<example>
<title><function>registered</function> usage</title>
```
Jul 30 14:36:38 sp1 proxy[34000]: CRITICAL: <core> [pass_fd.c:275]: receive_fd(): EOF on 36
Jul 30 14:36:38 sp1 proxy[33972]: ALERT: <core> [main.c:728]: handle_sigs(): child process 33995 exited by a signal 6
Jul 30 14:36:38 sp1 proxy[33972]: ALERT: <core> [main.c:731]: handle_sigs(): core was generated
Jul 30 14:37:38 sp1 proxy[33972]: CRITICAL: <core> [main.c:637]: sig_alarm_abort(): shutdown timeout triggered, dying...
Jul 30 15:12:39 sp1 proxy[15644]: WARNING: jsonrpc-c [jsonrpc_io.c:448]: connect_server(): Failed to connect to 172.16.74.93 on port 8991... No route to host
Jul 30 15:12:39 sp1 proxy[15644]: ERROR: jsonrpc-c [jsonrpc_io.c:91]: jsonrpc_io_child_process(): failed to connect to any servers
Jul 30 15:12:39 sp1 proxy[15644]: ERROR: <core> [sr_module.c:900]: init_mod_child(): Error while initializing module jsonrpc (/usr/lib/x86_64-linux-gnu/kamailio/modules/jsonrpc-c.so)
Jul 30 15:12:39 sp1 proxy[15644]: ERROR: <core> [main.c:1651]: main_loop(): error in init_child
Jul 30 15:12:39 sp1 proxy[15590]: ALERT: <core> [main.c:725]: handle_sigs(): child process 15644 exited normally, status=255
Jul 30 15:12:39 sp1 proxy[15654]: CRITICAL: <core> [pass_fd.c:275]: receive_fd(): EOF on 14
```
I would say that the functions should respond with error if no server is connected but kamailio should be able to start.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/269