Hi,
First of all I would like to mention, that I'm very new to Kamailio. :)
My target is to create simple load-balancing similar what have Kazoo,
basically 2 servers will share same domain name.
I installed 2 Kamailio 4.3 servers and configured this 2 servers with one
domain address. I used almost default config with:
#!define WITH_MYSQL
#!define WITH_AUTH
#!define WITH_USRLOCDB
#!define WITH_MULTIDOMAIN
#!define WITH_NAT
#!define WITH_NATSIPPING
Calls are going through if I register both clients to one server.
But all my calls are failing, when clients are registered to different
servers with error "404 Not Found". Maybe somebody can give me a hint how
to make this work.
Thank you!
With kind regards,
Jurijs
Any help regarding the below would be appreciated.
BR,
Ali
From: Ali Taher [mailto:ataher@vanrise.com]
Sent: Wednesday, July 22, 2015 1:39 PM
To: 'Kamailio (SER) - Users Mailing List' <sr-users(a)lists.sip-router.org>
Cc: 'Ali Taher~Vanrise Technical Support' <ataher(a)vanrise.com>
Subject: Kamailio mod_destroy() ERROR
Hello,
I'm getting below error when starting Kamailio.
ERROR: ctl [ctl.c:379]: mod_destroy(): ERROR: ctl: could not delete unix
socket /tmp/kamailio_ctl: Operation not permitted (1)
Any advice ?
Regards,
Ali
Hello,
I have configured kamailio 4.0.4 long back. Now, I wanted to enable the
usage of port 5061 with TLS. By doing so, the client(video camera) can
place outgoing calls fine. But while receiving an incoming call, the
message does not get sent out to the other client. Hence, the call fails. I
can place and receive calls on port 5060 successfully without any issues.
Can anyone please tell me why port 5061 is giving me a problem.
Also, as a test, I set up kamailio on another machine(version 4.1) and 5061
works fine in all directions. It's only on the other machine that I have
problems with.
Appreciate any help!
Thank you,
Ankhit
Hello there,
I'm using the dmq and htable modules to limit the number of concurrent
calls in several kamailio's servers.
Every call that one kamailio server receives, kamailio increments a htable
variable that is replicated to other kamailios through dmq, but if one of
these kamailios fails or is restarted it looses the data from htable
variable used to count the number of calls and it is not recovered again
when kamailio starts again.
Is there any way to recover the data from htable variable when kamailio
starts, from another kamailio instances through dmq module?
Best Regards
--
Cumprimentos
José Seabra
Using RTPBreak and sox im able to convert rtpproxy rtp files to wav. Later
you could convert to mp3 if liked
Just to share with list
https://github.com/albersag/rtpproxy-utils
Any comment is well appreciated
Best Regards
Hi All,
I have an issue with the dmq_is_from_node() function, whereby it does
not detect a node is on the bus if it has been removed from its "table"
due to previously failed, i presume, ping requests.
I have the following snippet in my main routing block:
if(is_method("KDMQ")) {
if (dmq_is_from_node()) {
dmq_handle_message();
exit;
} else {
xlog("L_INFO", "KDMQ message recieved from node not on our
bus!! ($si:$sp) Dropping.");
exit;
}
}
I have the following dmq module parameters enabled for dmq:
modparam("dmq", "server_address", DMQ_ADDRESS)
modparam("dmq", "notification_address", "sip:lb.domain.com:5060")
modparam("dmq", "multi_notify", 1)
modparam("dmq", "num_workers", 4)
DMQ_ADDRESS is set to each of the addresses in the lb.domain.com for
each local kamailio instance
lb.domain.com resolves to the following addresses:
10.6.0.109
10.6.0.110
10.6.0.111
If I start up the 1st instance of kamailio and do not start the other 2
within the default ping timout then I get the expected log message of
dmq removing the nodes from its table, for example:
kamailio[26657]: ERROR: dmq [notification_peer.c:588]:
notification_resp_callback_f(): deleting server sip:10.6.0.111:5060
because of failed request
kamailio[26657]: ERROR: dmq [notification_peer.c:588]:
notification_resp_callback_f(): deleting server sip:10.6.0.110:5060
because of failed request
However, if I then start one, or both, of the other nodes, then the KDMQ
requests are dropped due to my snippet above, I presume, because
dmq_is_from_node() checks its "active" table. See messages below as an
example of the above snippet in action:
kamailio[26656]: INFO: <script>: KDMQ message recieved from node not on
our bus!! (10.6.0.110:5060) Dropping.
kamailio[26656]: INFO: <script>: KDMQ message recieved from node not on
our bus!! (10.6.0.111:5060) Dropping.
Is this expected behaviour from the dmq_is_from_node() function? I would
have expected it to always check the addresses resolved in the
notification address, or am I using this function in a manner not intended.
Any suggestions/tips would be greatly appreciated.
Thanks
Hello,
(cross-posting as it impacts users as well)
Currently we generate and install the TLS self-signed certificates when
tls module is installed, including them in the debian packages (and I
guess in rpms).
Debian has a policy of reproducible builds, meaning that from same
source tree snapshot the same binary packages should result.
Even more important considering the impact on security, it would be
better that the certificates are generated locally on the installation
server, to be distinct. Right now, people relying on default
installation config/certificates (and I guess there are many, at least
in testing phase), are exposed to eavesdropping, because the private key
is available in public packages.
My proposal is to move generation of self signed certificates to kamctl.
There can be a kamctl.tls file to be deployed by the tls package (same
is done by kamctl.mysql, being part of mysql package), which should add
a new group of commands, among them something like:
kamctl tls generate-certificate
The drawback is that before enabling tls and starting kamailio, one has
to run the above command. We can document that in tls module readme and
in kamailio.cfg in the comments related to WITH_TLS define.
Anyone with comments, pros/cons?
Other suggestions on how to address the reproducible builds as well as
solve the security issue for the default installation?
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
Hello,
I'm getting below error when starting Kamailio.
ERROR: ctl [ctl.c:379]: mod_destroy(): ERROR: ctl: could not delete unix
socket /tmp/kamailio_ctl: Operation not permitted (1)
Any advice ?
Regards,
Ali
Hi,
I was wondering how can I replace From header username to perform the following authentication check with the new value:
route[AUTH]......if (!auth_check("$fd", "subscriber", "1")) { auth_challenge("$fd", "1"); exit;}...
Thanks,Al
Hello Daniel,
After update my kamailio to version 4.3 and change the table location as
required in migration process, kamailio start giving some errors:
[root@ccp1 kamailio]# 35(7637) ERROR: db_mysql [km_dbase.c:121]:
db_mysql_submit_query(): driver error on query: Unknown column 'partition'
in 'where clause'
35(7637) ERROR: <core> [db_query.c:132]: db_do_query_internal(): error
while submitting query
that's is because the column name "partition" is reserved word (
http://dev.mysql.com/doc/refman/5.6/en/keywords.html) in mysql ndbcluster
engine, so what i did to fix this issue was add a new modparam in
modules/usrloc/ul_mod.c file:
{"partition_col", PARAM_STR, &partition_col},
with this i can configure what name i want for this column in kamailio
module configuration and configure a diferent column name in table
location(ex: modparam("usrloc", "partition_col", "partitionusrloc") ), Can
you please check out if what i did is the correct way to fix it, in order
to avoid damage something else.
Best regards
--
Cumprimentos
José Seabra
