The downside to SIP is that if you leave a SIP server open on the Internet
which allows calls without authenticated registration (even by accident)
you will find dozens of systems trying to proxy long-distance &
international telephone calls through it. If they can get through,
thousands of
This looks interesting, but I would prefer to stick with SIP
Reason:
1. It is extremely scalable from running on tiny openWRT routers to big
servers
2. It is supported by a large number of free/open clients on ALL platforms.
There is also a webRTC socket for it.
The only current drawback of
Following from:
http://www.en.voipforo.com/IAX/IAXvsSIP.php
*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
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 wrote:
> What server/service are you using? Look at IAX2 as well. Usually IAX2 does
>
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.
Sameer
On Oct 14, 2016 4:48 AM, "Anish Mangal" wrote:
> Hi,
>
> A SIP server on the XSCE will allow
I think it's a good idea. Are you thinking Asterix? Does it change networking
or just sit on top?
Sent from my Samsung Galaxy smartphone.
Original message
From: Anish Mangal
Date: 10/14/16 1:48 AM (GMT-08:00)
To: xsce-devel ,
Hi,
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.