Hello,
As someone new to the OpenSER/Kamailio/OpenSIPS world I can attest to
the need to have fairly robust example config files. I put together
an "OK" configuration file which Daniel was nice enough to polish up
for me. While the core and module documentation is fantastic, it is
difficult to put all the pieces together at the beginning.
Something that would be VERY useful in my opinion is to provide 3 or 4
example files, each with a different general functionality.
Perhaps an LCR example, a Dispatcher example, a Registrar example, etc.
The point would be to provide simple concise flows which would be easy
to read, study, and eventually expand upon (or combine) to suite the
needs of the users particular network and deployment.
I would be happy to provide my configuration as the 'simple dispatcher
/w failover'.
thanks,
Geoff
On Mon, Feb 16, 2009 at 7:51 AM, Elena-Ramona Modroiu <ramona(a)asipto.com> wrote:
Hi,
looking at the default config file, we deliver something pretty useless
and very insecure.
I propose to add to it several features so it becomes really usable:
- mysql support - even some use radius for aaa, mysql is for sure used
for usrloc. Those using other db drivers can just replace the module
- auth against db and check auth username against from/to username to
avoid spoofing
- accounting - at least to syslog to store more than default data which
gives nothing useful right now. Thinking to from/ruri username and
domain at least in order to have caller and callee details
- usrloc to database
- nat traversal support with nathelper and rtpproxy - if rtpproxy is not
running, will be just warnings at startup
- the first part of the config will have some help of how to configure
the environment to start the sip server (e.g., add user, ...)
What do you think?
Regards,
Ramona
_______________________________________________
Kamailio (OpenSER) - Users mailing list
Users(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
http://lists.openser-project.org/cgi-bin/mailman/listinfo/users