Alex Balashov wrote: > Yehavi Bourvine wrote: > >> OK, but I still did not get a reply to my original question: Why using >> SIP registrar in front of Asterisk and not simply use bare Astersik? >> can't it handle the load? (remember - in my case it doesn't handle the >> RTP, only signalling). Can't it handle so much registrations? (I am >> using realtime DB, it is has any relevance). > > My experience has shown that using a dedicated registrar for large > installs is more effective; it doesn't tie up resources on the Asterisk > box with all those registration refreshes, for one. A product built to > be a high-throughput standalone registrar will handle the concurrency > requirements and perform better. >
Some of this is just a general design principle, nothing specific to registration. Once a VoIP platform gets to be big enough, a lot of the logical elements that go into it get centralised into distinct and dedicated components that are federated into a delivery platform. It's no longer considered a good idea at that point to have one process perform many different functions that have varying concurrency and blocking implications. -- Alex Balashov Evariste Systems Web : http://www.evaristesys.com/ Tel : (+1) (678) 954-0670 Direct : (+1) (678) 954-0671 Mobile : (+1) (706) 338-8599 _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
