VoIP Mailing List Archives

[z_gringo at hotmail.com]

I have a decent sized asterisk 1.4 installation of about 5000
registered users spread across various servers. I have noticed that
when keeping the SIP users in the Realtime database, the Asterisk
servers become completely unstable at around 600 - 800 users. MySQL
is running on a different set of servers, but the bottleneck is
definately the number of registered users. We can buy some room by
increasing the re-registration time, but not much.

If I take put
all the users in sip.conf instead of in the Realtime database, the
situation improves considerably. We leave the dialplan in realtime,
but put the users in sip.conf. This seems to eliminate most of the
problems.

Obviously, we can look at putting something in front
of Asterisk to manage the registration traffic, but why is Asterisk
having such a problem with this? Does anyone else have more than 600
users registering directly with Asterisk using Realtime?

_________________________________________________________________
Make every e-mail and IM count. Join the i?m Initiative from Microsoft.
http://im.live.com/Messenger/IM/Join/Default.aspx?source=EML_WL_ MakeCount
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20080527/fcc6da7a/attachment.htm

[greymanvoip at gmail.com]

Sounds more like a database problem than an Asterisk problem. Asterisk
shouldn't care if you have 50 million accounts in your realtime db
provided it gets timely responses to its queries and updates. I use a
Postgres database with Asterisk and realtime and have over 5000
registered SIP accounts in the one db.

Asterisk is very snesitive to unresponsive realtime db's (and
unresponsive DNS while you're at it). If your db starts to struggle
you can expect console freezes and other oddities on your Asterisk
servers.

Regards,

Greyman.