[Asterisk-Dev] IAXtel Status

[Whisker, Peter]

A possible way of managing large numbers of IAX streams is to have a very
efficient high-speed splitter box which understands IAX trunking and is
capable of splitting and combining trunks and individual channels to route
packets to parallel Asterisk servers. A gigabit data switch should be able
to handle the traffic from this splitter to multiple asterisk servers. Apart
from separating and combining channel streams, the splitter would need to
have some rules to decide on the server to allocate the traffic to - eg
based on IP address masking of the remote or how busy the servers are.

This kind of thing is used to split, combine and resource-level across
servers the billions of text messages sent every day.

Peter

-----Original Message-----
From: Daniel Pocock [mailto:daniel at readytechnology.co.uk]
Sent: 29 November 2004 19:05
To: Asterisk Developers Mailing List
Subject: Re: [Asterisk-Dev] IAXtel Status



Mark Spencer wrote:

> The Asterisk+SER combination does seem to be very commonly deployed in 
> SIP environments although I haven't messed with it myself.  Obviously 
> SER does not support IAX and in any case, I think we should be trying 
> to solve this problem with Asterisk and really taking the time to 
> explore what Asterisk's performance limitations are and why.
>
> Mark
>

The big difference between SIP and IAX is that SIP handles just the 
signalling, and the audio (and video) is sent in separate RTP streams.  
SER doesn't handle the RTP streams, so naturally SER is much more 
scalable.  Therefore, I'm not sure that SER supporting IAX would be 
appropriate.  There is the possibility of creating a pure IAX equivalent 
of SER (perhaps a cut down Asterisk that just does IAX, no transcoding 
or media processing, etc).

Furthermore, SER doesn't have to worry about timing - it just forwards 
requests as soon as they arrive.  Asterisk does have to worry about 
timing, whereas a pure IAX-IAX switch could possibly forget about timing 
and leave it to the end-points to worry about.

IAX combines the media streams and signalling into the same packets (the 
RTP packets NEVER go through SER).  The benefits to this are a) trunking 
and b) easier NAT traversal.  I think the downside is that having all 
this extra stuff in the protocol will inevitably put a limit to the 
number of live sessions the NIC can support concurrently.

This doesn't mean that IAX is somehow bad and SIP/SER is good - it just 
means they fill very different needs in the marketplace.  Eg companies 
wanting to trunk calls between remote offices over satellite links would 
find IAX much more cost efficient than SIP.


_______________________________________________
Asterisk-Dev mailing list
Asterisk-Dev at lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.