Johansson Olle E wrote:
> Based on experience of problems with several Asterisks
in production,
> I don't agree with you.
>
> We really need to make Asterisk servers that run mainly
SIP to SIP
> calls scale
> over multiple processors. We have had several instances
where Asterisk
> totally blocks one CPU while the rest is idle. We don't
see this if we
> gateway
> to zaptel or other protocols, then media becomes a
major issue.
If you're primarily making SIP to SIP calls, then you should
probably be using a
real SIP proxy.
> Something I need to port back from the chan_sip3 work
is the
> allocation and
> parsing of packets that is a major pain. I simplified
this in chan_sip3
> so that I only allocated the packet once and limited
the number of times
> I looked for various frequently used headers.
Cool, performance enhancements are always welcome ...
--
Russell Bryant
Senior Software Engineer
Open Source Team Lead
Digium, Inc.
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.c
om--
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
|