*If SIP is using a server* signaling messages always pass through the
server but *audio messages (RTP flow) can travel end to end without passing
through the server. In IAX, signaling and data must pass always through IAX
server. *This increases the bandwidth need by the IAX servers when there
are many simultaneous calls.
This is a big drawback of IAX it seems, especially in a mesh setup, where
in many cases, the available bandwidth between clients may be higher via
direct node routes compared with the bandwidth via the server route. It
seems SIP will utilize the network more efficiently in a mesh topology.
Yesterday we were testing this on the server, and two nodes with three
client. The data was being sent directly client -- node -- node -- client,
and virtually no bandwidth was being used on the server. :)
On Sat, Oct 15, 2016 at 5:07 AM, Anish Mangal <anis...@umich.edu> wrote:
> Will look into IAX2. Is it supported by apps on different clients? For
> SIP, there are usually many client options available on various platforms.
> On Fri, Oct 14, 2016 at 9:22 PM, Sameer Verma <sve...@sfsu.edu> wrote:
>> What server/service are you using? Look at IAX2 as well. Usually IAX2
>> does better on networks because unlike SIP, session initiation and voice
>> call happen on the same port.
>> On Oct 14, 2016 4:48 AM, "Anish Mangal" <anis...@umich.edu> wrote:
>>> A SIP server on the XSCE will allow for VOIP services (audio, video,
>>> text). There are numerous SIP clients on various platforms so it seems a
>>> good protocol and standard to build upon.
>>> I have already included a SIP server in the upcoming deployment of XSCE
>>> and mesh in Spiti, north India.
Server-devel mailing list