Andrew Kohlsmith wrote:
So now if you run a query (on purpose or not) and your DB chugs away and locks up the processor and you start dropping calls... I guess you can make asterisk realtime priority to avoid that, and so long as your nondeterministic DB doesn't tie up a lookup or whatnot it'll be fine. I dunno it's just not that important to me, nor do I see it solving any real problems.
Assuming you're not working with a huge database, most of it will be cached in RAM. Just as filesystem caching will speed up reading flat files, it's going to ensure snappy database reponses. The overhead of running a relatively small DB on the same box as the PBX is going to be less than the network latency of querying the DB on an external box.
As the PBX dropping calls - well, if you allow SIP phones on the LAN to re-invite, it pretty much means your PBX just has to handle call setup. Asterisk is only going to use resource if it's having to transcode the codec or if it's handling a channel translation (ie SIP to Zaptel).
_______________________________________________ Asterisk-Dev mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
