16 May
2005
16 May
'05
7:38 p.m.
Senad, Thanks for your response.
There are several reasons.
The 2 biggest are..
1 - We offer our customers the option to forward calls when an IAD is not
registered .. In order to do that the registration interval needs to be
relatively low.
2 - We've had some issues with setting registration intervals higher than 10
minutes. It seems to work about 99.5% of the time, but occaisionally an
endpoint won't reregister before the reg interval on SER times out. I
believe this is a bug in our endpoint and have been working with them on
that. Setting the reg interval below 10 minutes has eliminated that problem
for the time being .. However, even if this problem was fixed by the IAD
manufacturer we still have the first reason (above) that would keep us from
being able to increase the interval.
Darren
On 5/16/05 1:23 PM, "Senad J" <senad(a)bicom.us> wrote:
serusers-bounces(a)lists.iptel.org wrote:
Hey All,
This is a long email, so please bare with me...
Up until now we have used our primary SER serve as both registrar and
call routing engine. However, we've recently hit a growth point
where the registration load on our servers is high enough that it's
affecting our call routing.
We currently have about 4,000 IAD's all registering every 5 minutes.
why every 5 minutes?
If you set it to highr figure, that will automatically reduce registration
load !
So - my question is .. How do I take load off of
the primary server??
Would implementing radius for authentication fix this problem? I am
very familiar with radius (using Freeradius) and could easily set
this up, but I would prefer not to go to the trouble if it's not
going to help with the load.
Has anyone else had an issue with client authentication via MySQL and
auth_db causing a high load with SER?
is your MYSQL on same host as SER?