9 Dec
2007
9 Dec
'07
7:46 p.m.
Jiri Kuthan wrote:
MySQL 5.0.X automatically times out its sockets after a hardcoded period
of time. Unless you have configured the socket to auto reconnect (see
http://www.ideasip.com/support/utils/my_con.c.SER2 ), after a little
while, the socket will just time out and you will have to restart SER in
order to connect to the database (it will throw errors).
I agree.... that's why I added it as an optional -- something to think
about in the future, but not essential.
N.
At 14:00 09/12/2007, SIP wrote:
Agreed.
My assumptions are (at the basic level):
-SER 2.0 (in whatever state it's in atm)
-SERWeb
-RTPProxy
-SEMS
Yes. +ser_ctl.
Secondary (but no less important) items that are
a must-have:
-MySQL (I'm voting for 5 series here, but that will require my patch for
the mysql code in SER 2.0)
why the patch?
-Apache (req'd for SERweb)
-SIPsak
-ngrep (invaluable for debugging as well as learning)
Optional:
-mediaproxy
-freeradius
-radiusclient (for those who want to mesh SER with an existing radius
infrastructure perhaps)
Just to keep things focused, I think starting with just mysql would
be a more pragmatic (nothing against radius in next stage).
-jiri