Instead of speculating (registrations, some error in the call setup,
etc), why doesn't the OP just run a quick oprofile profile on the
machine in question, to see what is actually consuming his CPU
resources?
If you find that the machine is spending 40% of it's time processing
registrations, it will show up quite clearly (well, a bit less
clearly from the way I remember chan_iax2, with one huge socket_read
() function, but the CPU time probably isn't there). Similarly, if
he's transcoding or such, and that is the major use of time, it will
also show up.
-SteveK
On Nov 24, 2006, at 9:17 PM, Derek Smithies wrote:
On Fri, 24 Nov 2006, Tim Panton wrote:
IAX's repeated registrations every 30 seconds are know to be
expensive.
Current thinking is to re-register much less often, but to use
ping packets
to 'qualify' the link, which is more like SIP's standard method.
Why are the registrations expensive ?
Does that suggest a bug in asterisk in handling registrations?
Can this code be made more efficient?
Actually - there is a denial of service attack. I will adjust the
iax2 to
send a registration every second, not every 30 seconds.
A couple of calls doing that will make the server quite busy.
Derek.
--
Derek Smithies Ph.D.
IndraNet Technologies Ltd.
Email: [EMAIL PROTECTED]
ph +64 3 365 6485
Web: http://www.indranet-technologies.com/
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
