Jiri Kuthan wrote:
loooking at it from the merged sip-router perspective,
I rather recommend
oob. All the things you are mentioning and actually many more are in there
including configuration facilities for debian.
thanks for suggestion. It could be too complex for startup, however, I
see default ser.cfg comes now with mysql enabled, as well (for auth,
...). What is missing from what I was looking for in the first place is
the nat traversal.
Regards,
Ramona
-jiri
Elena-Ramona Modroiu 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