The kamailio package appears to be failing on SPARC:
https://buildd.debian.org/status/logs.php?arch=sparc&pkg=kamailio
and this is preventing the package from propagating to the testing
distribution.
https://release.debian.org/migration/testing.pl?package=kamailio
This means it is not eligible for inclusion in the next stable release
of Debian.
This may not be hard to fix and it is also possible to just declare that
SPARC is unsupported and exclude it from building there. As long as it
builds fine on all the other platforms then it should propagate to
testing/jessie
Hello,
attached you find an initial version of a kamailio OCF compliant resource agent for pacemaker, which is currently running within a prototype laboratory on Redhat Enterprise Linux 6.x. Please keep in mind that it survived testing in a very controlled environment and it is young and some issues/bugs are likely to be found.
I was allowed by FREQUENTIS to provide this script to the community under the GPL v2 license with the goal that putting this resources agent under the maintenance of the community, the safer and better it becomes long term.
Please note that I won't be able to respond on questions, because my mail account is going to be closed in a few days.
Regards,
Stefan Wenk
Internal note: The released version corresponds with rel_0_19_0.
Hi,
I've found some problems trying to use db_cassandra module for tables that
are not related to Kamailio and that are queried from the sqlops module.
Below there's a list where I describe them with some level of detail:
1. Querying from sqlops was impossible because of a parameter check that
reads the table name from the connection structure. This table name is
never set when using raw SQL (or CQL).
2. All data was being treated as string, not matter what their actual type
was. The table information for database schema was being ignored for raw
queries.
3. If you define your table structure beforehand, using CQL DDL for
example, all numeric types are inaccessible from inside the module because
of the problem described in the item above.
I fixed the problems of points #1 and #2. Sqlops module is now fully usable
with Cassandra and the table definition is being taken into account even
for raw queries. Some basic checks are also performed with field
definitions. The problem #3 remains; I was not able to fix it because I
don't have enough experience with Thrift. Hopefully, this will change soon
enough.
To avoid running into problems with point #3, one can simply create the
column family without specifying member types, and creating an index for
your primary key field (this will allow you to query using "where clause"
with that field as a condition). Later, define the table structure in plain
text with the correct database types and pass that information to cassandra
module (schema_path param), and the module should treat every value with
the correct type inside Kamailio memory space.
I've attached the patch of the fix. Hopefully, the original authors of the
module (who are copied on this email) will review it and authorize me to
push it to master.
Regards,
--
Carlos
http://caruizdiaz.com
+595981146623
Hello,
Kamailio SIP Server v4.1.1 stable release is out.
This is a maintenance release of the latest stable branch, 4.1, that
includes fixes since release of v4.1.0. There is no change to database
schema or configuration language structure that you have to do on
installations of v4.1.0. Deployments running previous v4.x.x versions
are strongly recommended to be upgraded to v4.1.1.
For more details about version 4.1.1 (including links and guidelines to
download the tarball or from GIT repository), visit:
* http://www.kamailio.org/w/2014/01/kamailio-v4-1-1-released/
RPM, Debian/Ubuntu packages will be available soon as well.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda