Hello,
Kamailio SIP Server v4.4.5 stable release is out.
This is a maintenance release of the latest stable branch, 4.4, that
includes fixes since the release of v4.4.4. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v4.4.x. Deployments running previous v4.x.x
versions are strongly recommended to be upgraded to v4.4.5.
For more details about version 4.4.5 (including links and guidelines to
download the tarball or from GIT repository), visit:
* https://www.kamailio.org/w/2017/01/kamailio-v4-4-5-released/
RPM, Debian/Ubuntu packages will be available soon as well.
Many thanks to all contributing and using Kamailio!
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Hi,
I have a server listening on a single tls-socket:
--------------------------------------------------------------------------
Bug in Record-Route???
--------------------------------------------------------------------------
listen=tls:47.11.23.42:443
I use this socket for both Websocket and SIP-TLS. Kamailio basically
does a WebSockets to SIP-TLS translation. For simplicity reasons, I
use only one TLS socket for both TLS and WebSockets.
If I simply do the following in my routing-script:
record_route();
$du = "sip:server;transport=tls";
it will simply add a single Record-Route header, e.g.:
Record-Route: <sip:47.11.23.42:443;transport=ws>
It will only add this single Record-Route header, despite the fact,
that it's actually translating between WebSocket and SIP-TLS.
The expected behaviour would be:
Record-Route: <sip:47.11.23.42:443;transport=ws>
Record-Route: <sip:47.11.23.42:443;transport=tls>
The problem is, that the upstream Proxy (a loadbalancer) only speaks
SIP-TLS and UDP (for Interconnecting) and not WebSockets. As a result,
in-Dialog-Requests fail, as the Loadbalancer cannot reach the next hop
using "transport=ws".
In the code, I did see, that COND_IF_DIFF_REALMS actually should also
check the protocol, so I'm not sure, why this is not happening.
--------------------------------------------------------------------------
Undocumented Feature / Workaround
--------------------------------------------------------------------------
Looking at the code of RR, I've found that I can actually set
"enable_double_rr" to 2, which will ALWAYS add a second Record-Route
header. Apart from the fact, that I don't need the second record-route
header always, it solves my problem.
At least the latter I will add to the docs, but however I haven't
found any time to look any deeper into the Bug.
Thanks,
Carsten
--
Carsten Bock
CEO (Geschäftsführer)
ng-voice GmbH
Millerntorplatz 1
20359 Hamburg / Germany
http://www.ng-voice.com
mailto:carsten@ng-voice.com
Office +49 40 5247593-40
Fax +49 40 5247593-99
Sitz der Gesellschaft: Hamburg
Registergericht: Amtsgericht Hamburg, HRB 120189
Geschäftsführer: Carsten Bock
Ust-ID: DE279344284
Hier finden Sie unsere handelsrechtlichen Pflichtangaben:
http://www.ng-voice.com/imprint/
when dealing with large db_text files, pkg_memory is not suitable for
operating the database.
implementing fetch allows modules like presence & registrar & usrloc
to query large tables without constraints on pkg_memory.
creates tmp tables in shared memory for query results
(cherry picked from commit 18c64d2c9ff1527655055f75aa22e7d68c307874)
Conflicts:
src/modules/db_text/db_text.c
src/modules/db_text/dbt_api.c
src/modules/db_text/dbt_base.c
src/modules/db_text/dbt_lib.c
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/941
-- Commit Summary --
* db_text: implement fetch and memory constraints
-- File Changes --
M src/modules/db_text/db_text.c (9)
M src/modules/db_text/db_text.h (4)
M src/modules/db_text/dbt_api.c (107)
M src/modules/db_text/dbt_api.h (6)
M src/modules/db_text/dbt_base.c (185)
M src/modules/db_text/dbt_lib.c (62)
M src/modules/db_text/dbt_lib.h (6)
M src/modules/db_text/dbt_res.c (202)
M src/modules/db_text/dbt_res.h (14)
M src/modules/db_text/dbt_tb.c (4)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/941.patchhttps://github.com/kamailio/kamailio/pull/941.diff
--
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/pull/941
when dealing with large db_text files, pkg_memory is not suitable for
operating the database.
implementing fetch allows modules like presence & registrar & usrloc
to query large tables without constraints on pkg_memory.
creates tmp tables in shared memory for query results
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/940
-- Commit Summary --
* db_text: implement fetch and memory constraints
-- File Changes --
M modules/db_text/dbt_api.c (109)
M modules/db_text/dbt_api.h (6)
M modules/db_text/dbt_base.c (186)
M modules/db_text/dbt_lib.c (62)
M modules/db_text/dbt_lib.h (6)
M modules/db_text/dbt_res.c (202)
M modules/db_text/dbt_res.h (14)
M modules/db_text/dbt_tb.c (4)
M modules/db_text/dbtext.c (8)
M modules/db_text/dbtext.h (4)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/940.patchhttps://github.com/kamailio/kamailio/pull/940.diff
--
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/pull/940