Hello everyone,
I want to port openSER on an embedded board,I need configure the openser without MySQL due to space constraint. So can you let me know whether this is possible also can you give any reference document on how to port on ARM 9 based boad.
Regards, Rathndran
Ratheendran R wrote:
I want to port openSER on an embedded board,I need configure the openser without MySQL due to space constraint. So can you let me know whether this is possible also can you give any reference document on how to port on ARM 9 based boad.
I don't know that this is really a good idea. While OpenSER is a relatively "low-level" component of VoIP infrastructure, it is heavily bound up in the higher layers of abstraction, including the point at which high-level application delivery happens. It's designed to run on real servers - at least, to achieve any real scalability. This isn't the same as PBX appliances.
Beyond that, there aren't too many ways to use OpenSER without database backing. Why does the database have to be on the same embedded machine as the proxy itself? Why can't it be centralised on a powerful set of servers?
To avoid database calls, you'd have to completely abandon use of a number of critical modules, and put all business logic statically in the route script. This is something for which it is not very well-suited; it is not a general-purpose programming language, and doesn't have many of the commonsensical, every-day primitives relied upon in common programming, and certainly no elegant or pretty ways to use them when they are available in some form. It's a highly specialised language.
About the only other thing you can do to pull this off is to use SEAS (SIP Express Application Server), a Java application server that can be used with OpenSER to provide request processing using servlet APIs and techniques. It is, however, commercial, and, being Java and all, obviously cannot run on the embedded system either.
It is a matter of taste and opinion, of course, but I think your project is a bad idea. If it must be done, I recommend using a database, albeit across a network. This is necessary for storage and performance reasons, as well.
-- Alex
13 aug 2009 kl. 15.45 skrev Alex Balashov:
Ratheendran R wrote:
I want to port openSER on an embedded board,I need configure the openser without MySQL due to space constraint. So can you let me know whether this is possible also can you give any reference document on how to port on ARM 9 based boad.
I don't know that this is really a good idea. While OpenSER is a relatively "low-level" component of VoIP infrastructure, it is heavily bound up in the higher layers of abstraction, including the point at which high-level application delivery happens. It's designed to run on real servers - at least, to achieve any real scalability. This isn't the same as PBX appliances.
In some cases, it's a really good idea ;-)
Some of the WRTG distros already use one version of SER in their systems as an ALG, application level gateway.
And yes, MySQL is not a requirement at all. It's just a matter of what you want to do. Check the documentation - we have a lot of it - and you will even find drivers for text-based configurations. Daniel can comment on the state of these, I'm sure.
/O
Olle E. Johansson wrote:
In some cases, it's a really good idea ;-)
Some of the WRTG distros already use one version of SER in their systems as an ALG, application level gateway.
A bizarre, but understandable application of it, I suppose.
And yes, MySQL is not a requirement at all. It's just a matter of what you want to do. Check the documentation - we have a lot of it - and you will even find drivers for text-based configurations. Daniel can comment on the state of these, I'm sure.
Yep, if you want to use OpenSER/Kamailio for some purpose that does not require dynamic information and so on, it is quite possible to do it without using a database.
However, I assumed that since the question was posed in this manner, there was an underlying assumption that things requiring a database need to be done. Otherwise, why even ask the question; in that case, it ought to be self-evident that there is no need to use a database to begin with, let alone MySQL.
-- Alex
On 13.08.2009 15:54 Uhr, Olle E. Johansson wrote:
13 aug 2009 kl. 15.45 skrev Alex Balashov:
Ratheendran R wrote:
I want to port openSER on an embedded board,I need configure the openser without MySQL due to space constraint. So can you let me know whether this is possible also can you give any reference document on how to port on ARM 9 based boad.
I don't know that this is really a good idea. While OpenSER is a relatively "low-level" component of VoIP infrastructure, it is heavily bound up in the higher layers of abstraction, including the point at which high-level application delivery happens. It's designed to run on real servers - at least, to achieve any real scalability. This isn't the same as PBX appliances.
In some cases, it's a really good idea ;-)
Some of the WRTG distros already use one version of SER in their systems as an ALG, application level gateway.
And yes, MySQL is not a requirement at all. It's just a matter of what you want to do. Check the documentation - we have a lot of it - and you will even find drivers for text-based configurations. Daniel can comment on the state of these, I'm sure.
db_text module (in 1.5 or later, named dbtext previously) should be pretty stable, I am not aware of misbehaviors. However, I haven't tested with heavy data, e.g., storing presence documents, but for auth, location, a.s.o. it has been used a lot.
Cheers, Daniel
Alex Balashov schrieb:
Ratheendran R wrote:
I want to port openSER on an embedded board,I need configure the openser without MySQL due to space constraint. So can you let me know whether this is possible also can you give any reference document on how to port on ARM 9 based boad.
I don't know that this is really a good idea. While OpenSER is a relatively "low-level" component of VoIP infrastructure, it is heavily bound up in the higher layers of abstraction, including the point at which high-level application delivery happens. It's designed to run on real servers - at least, to achieve any real scalability. This isn't the same as PBX appliances.
I tend to disagree.
You can use Kamailio as proxy and registrar fine without any database. Just keep registrations in memory. There are scenarios were authentication is not needed (e.g. closed networks with well known clients). And for routing purposes a DB is not needed.
regards klaus
Also, for small embedded systems, dbtext works like a charm. OpenSER works fine on ARM and small embedded systems. Check out http://svn.nslu2-linux.org/svnroot/optware/trunk/make/openser.mk More info on the project, here: http://www.nslu2-linux.org/ This is a generic make file that I created to cross compile openser for several embedded platforms.
Regards, Ovidiu Sas
On Thu, Aug 13, 2009 at 11:23 AM, Klaus Darilionklaus.mailinglists@pernau.at wrote:
Alex Balashov schrieb:
Ratheendran R wrote:
I want to port openSER on an embedded board,I need configure the openser without MySQL due to space constraint. So can you let me know whether this is possible also can you give any reference document on how to port on ARM 9 based boad.
I don't know that this is really a good idea. While OpenSER is a relatively "low-level" component of VoIP infrastructure, it is heavily bound up in the higher layers of abstraction, including the point at which high-level application delivery happens. It's designed to run on real servers - at least, to achieve any real scalability. This isn't the same as PBX appliances.
I tend to disagree.
You can use Kamailio as proxy and registrar fine without any database. Just keep registrations in memory. There are scenarios were authentication is not needed (e.g. closed networks with well known clients). And for routing purposes a DB is not needed.
regards klaus
Kamailio (OpenSER) - Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
Ratheendran R wrote:
So can you let me know whether this is possible also can you give any reference document on how to port on ARM 9 based boad.
Also, what makes you think such a reference document exists?
There's nothing in OpenSER/Kamailio that is overly architecture-specific. It's mostly standard C with a bunch of POSIX and BSD and System V-derived system calls.
Are you imagining there is inline assembly in the code, or what?
On Donnerstag, 13. August 2009, Alex Balashov wrote:
[...] There's nothing in OpenSER/Kamailio that is overly architecture-specific. It's mostly standard C with a bunch of POSIX and BSD and System V-derived system calls.
Are you imagining there is inline assembly in the code, or what?
Hi Alex,
actually there is some assembly code which is used for fast locking:
https://openser.svn.sourceforge.net/svnroot/openser/branches/1.5/fastlock.h
SCNR. :-)
But it will fallback to the generic (slower) implementation if there is no specific code available.
Henning
Henning Westerholt wrote:
actually there is some assembly code which is used for fast locking:
https://openser.svn.sourceforge.net/svnroot/openser/branches/1.5/fastlock.h
SCNR. :-)
Oh.
Well - ausgezeichnet! I stand corrected! :) Now, onto the matter of specification for the ARM9...
#elif defined __CPU_arm asm volatile( "# here \n\t" "swpb %0, %1, [%2] \n\t" : "=&r" (val) : "r"(1), "r" (lock) : "memory" );
...
#elif defined __CPU_arm asm volatile( " str %0, [%1] \n\r" : /*no outputs*/ : "r"(0), "r"(lock) : "memory" );
:)
-
Alex Balashov -
Daniel-Constantin Mierla -
Henning Westerholt -
Klaus Darilion -
Olle E. Johansson -
Ovidiu Sas -
Ratheendran R