Hi community.
This message is specially dedicated to developers of the kamailio project.
I need to find solution how to make authentication for connections of cnxcc
with redis.
For that moment, cnxcc module is able to connect to redis only without
password (Carlos Ruiz Díaz will add this possibility later?).
So that, this makes database vulnerable.
Well, furthermore I don't want to use local redis database, cuz I think
machine that contains kamailio daemon, must perform just this kind of
actions - SIP proxying (kamailio server is not to be a database server or
anything else).
For that moment we use separate redis db for cases like that, but this is
not best practice I think.
I already tried to find solution (for e.g. connections via another module
like db_redis:
https://github.com/kamailio/kamailio/pull/1432) but I got advice -
achieving my goal by sr-users mailing list.
Please pay attention for my request. I think this will be very helpfull for
others.
--
--
BR, Donat Zenichev
Wnet VoIP team
Tel Ukraine: +380(44) 5-900-800
Tel USA: +164(67) 8-174-17 (ext 1320)
https://w-net.us/ <http://wnet.ua>
Greetings list,
I am trying to install Kamailio 5.1 from source code on Debian 8.10. But It
is failing with below error. Don't know what could be wrong.
Any suggestion is much appreciated. Thanks.
make --no-print-directory -C ./squirrel/squirrel SQMARCH64="-m64"
CC_EXTRA_FLAGS="-fPIC" \
OUT="../../libsquirrel.a" sq64
gcc -O2 -m64 -D_SQ64 -fno-exceptions -fno-rtti -Wall -fno-strict-aliasing
-c sqapi.cpp sqbaselib.cpp sqfuncstate.cpp sqdebug.cpp sqlexer.cpp
sqobject.cpp sqcompiler.cpp sqstate.cpp sqtable.cpp sqmem.cpp sqvm.cpp
sqclass.cpp -I../include -I. -Iinclude -fPIC
gcc: error trying to exec 'cc1plus': execvp: No such file or directory
gcc: error trying to exec 'cc1plus': execvp: No such file or directory
gcc: error trying to exec 'cc1plus': execvp: No such file or directory
gcc: error trying to exec 'cc1plus': execvp: No such file or directory
gcc: error trying to exec 'cc1plus': execvp: No such file or directory
gcc: error trying to exec 'cc1plus': execvp: No such file or directory
gcc: error trying to exec 'cc1plus': execvp: No such file or directory
gcc: error trying to exec 'cc1plus': execvp: No such file or directory
gcc: error trying to exec 'cc1plus': execvp: No such file or directory
gcc: error trying to exec 'cc1plus': execvp: No such file or directory
gcc: error trying to exec 'cc1plus': execvp: No such file or directory
gcc: error trying to exec 'cc1plus': execvp: No such file or directory
Makefile:51: recipe for target 'sq64' failed
make[3]: *** [sq64] Error 1
Makefile:44: recipe for target 'libsquirrel.a' failed
make[2]: *** [libsquirrel.a] Error 2
Makefile:511: recipe for target 'modules' failed
make[1]: *** [modules] Error 1
make[1]: Leaving directory '/usr/src/kamailio/src'
Makefile:27: recipe for target 'all' failed
make: *** [all] Error 2
Br, Aqs.
I noticed this when I start a correctly configured kamailio:
Feb 27 21:55:45 rautu /usr/bin/sip-proxy[29529]: WARNING: registrar [registrar.c:369]: mod_init(): empty reg_xavp_cfg or sock_flag not set -> resetting
Neither of those two are mandatory. I'm not using registered()
function. Please downgrade the message to info or debug level.
-- Juha
I realize the transcoding support is rather new, however has anyone run any real world tests on it yet? Trying to get a sense of what the performance will be.
I'm aware that it's forced into userspace for transcoding so it's not *nearly* as efficient as the iptables module, however even if I have to throw a rack full of whiteboxes at it to get anywhere close to decent numbers that's still going to be comparable to a lot of the commercial options out there right now.
Brooks Bridges | Engineering Manager
O1 Communications
4359 Town Center Boulevard, Suite 217
El Dorado Hills, California 95762
office: 916.235.2097 | main: 888.444.1111, Option 2
email: bbridges(a)o1.com<mailto:bbridges@o1.com> | web: www.o1.com<http://www.o1.com/>
Hello,
Kamailio SIP Server v5.0.6 stable release is out.
This is a maintenance release of the previous stable branch, 5.0, that
includes fixes since the release of v5.0.5. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v5.0.x. Deployments running previous v5.0.x
versions are strongly recommended to be upgraded to v5.0.6 or v5.1.x.
For more details about version 5.0.6 (including links and guidelines to
download the tarball or from GIT repository), visit:
* https://www.kamailio.org/w/2018/02/kamailio-v5-0-6-released/
RPM, Debian/Ubuntu packages will be available soon as well.
Note: the latest stable branch is 5.1, at this moment with its latest
release v5.1.1 (and v5.1.2 planned to be out in the next few days). See
more details about it at:
* https://www.kamailio.org/w/kamailio-v5-1-0-release-notes/
Many thanks to all contributing and using Kamailio!
Cheers,
Daniel
--
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - www.asipto.com
Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com
Dear list..
I'm using kamailio on a live enviroment with dialogs support.. what I
made is a script that permit me to see the concurrent call (live) with
all parameters using the info saved on dialogs tables.
The problem is that if the call is not going on the first termination of
LCR but for examples in the second, the dialog is not updated with the
paramenter of the second supplier..
Is this problem only on my system or maybe i forgot to make some
configuration steps ?
Regards
Laura
Hello,
Kamailio SIP Server v4.4.7 stable release is out.
This is the last planned maintenance release of the old stable branch,
4.4, that includes fixes since the release of v4.4.6. There is no change
to database schema or configuration language structure that you have to
do on upgrading previous installations of v4.4.x. Deployments running
previous v4.x.x versions are strongly recommended to be upgraded to
v4.4.7, or even better to v5.0.x or 5.1.x.
For more details about version 4.4.7 (including links and guidelines to
download the tarball or from GIT repository), visit:
* https://www.kamailio.org/w/2018/02/kamailio-v4-4-7-released/
RPM, Debian/Ubuntu packages will be available soon as well.
Note: theb branch 4.4 is going out of maintenance life time, the latest
stable branch is 5.1, at this moment with its latest release v5.1.2. See
more details about it at:
* https://www.kamailio.org/w/kamailio-v5-1-0-release-notes/
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
Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com
Hello there,
I'm using xHTTP and json_rpc module to receive http instructions to reload
htable's from database to memory.
The way i'm calling the json_rpc in kamailio script is the following:
$var(json_rpc)='{"jsonrpc": "2.0", "method":
"htable.reload", "id":"htable"}';
jsonrpc_exec($var(json_rpc));
The execution of this command doesn't give any errors, but the changes made
on htable database weren't transmitted to the memory.
I have attached the kamailio log where you can see that there isn't any
erros on json_rpc execution during reload instructions, the strange thing
here is that the htable module only says:
2018-02-23 14:33:44.968 DEBUG: htable [ht_db.c:96]: ht_db_open_con():
database connection opened successfully
doesn't report if the reload was success or not.
Those logs attached were printed with kamailio debug set to level 4.
The kamailio version is 4.4.2.
Thank you
--
Best Regards
José Seabra
Thanks, Juha.
You are correct. That feature request is directly relevant to this thread.
I will upvote the feature request, and add a link back to this thread.
The proposed workaround of using async workers is the one I opted to use.
>A common design which avoids this is to use TCP at the client edge and
>UDP inside the network core. This is one of the reasons why TCP is not
>optimal for use inside the core.
That makes sense, but is unfortunately not an option for me due to strict security requirements.
I need to use TLS on the whole path.
Another option I explored was to have the edge proxies not always use the same TCP connection for sending to the registrar.
If I could find a way to load balance across a number of TCP connections, that would probably work for me.
Perhaps there is a way the DISPATHCER module can be configured to accomplish this.
Maybe the dispatcher configuration can list multiple copies of the same destination, but each having a different send socket address, and then can load balance across those.
Does that make any sense?