Asterisk can run on a RPi right now. A configuration for media passthrough mode would be the main question.
On Mar 16, 2013 4:36 PM, "David Sugar" <
address@hidden> wrote:
I had been away on a vision quest thinking about formal tribal enrollment.
One problem SIP always suffers from is that it does have to compute and
present information on completely unrelated (RTP) media ports, and this
is complex and uncertain of course when it has to do so for unrelated
RTP endpoints that also each face their own NAT issues.
One reason I did not do IAX is because the media would have to come to
the switch, rather than just pass through the endpoints. Originally I
had started sipwitch just from the idea of managing ZRTP endpoints.
While Asterisk decodes media because it needs to transcode for different
destinations, of course, one can also route/move/copy media traffic
without decoding it in a pure IAX switch. Of course if the switch
deamon can also be at the endpoint, the issue also becomes mute, and
this would then just mean the need to add an implementation of key hash
exchange in iax so one can do social verification, like with ZRTP.
IAX does not have "native" NAT transversal, it just greatly simplifies
the problem. If you can already communicate with an IAX endpoint, and
with one port that much is simpler, at least you don't have to then also
figure out an sdp to enable doing so for potentially completely
unrelated additional (RTP media) ports, and whether those are from a mix
of related or unrelated local or remote devices and networks.
We actually already build sipwitch for use on raspberrypi, and have our
own Debian repository and build system for this, among other things we
have also ported for it. Our http://www.gnutelephony/archive/wheezy
archive has armhf, which is specifically built armv6 (rather than
armv7), and from a rapsbian chroot builder using cape-chroot and qemu.
I would be happy to consider doing an iaxswitch project, and to have
sponsorship for a Raspberry PI to do so.
On 03/16/2013 07:18 AM, Earl wrote:
> The SIP protocol is by definition not world-wide P2P over IPv4 since
> it has no native NAT traversal capability.
>
> Even STUN, ICE, etc are only band-aids that are unsatisfactory.
>
> Even with the arrival of IPv6, normal end users will remain behind a
> NAT, and never see a native, non-tunneled IPv6, in my opinion. I do not
> see any ISP ever giving any customer a direct IPv6 connection.
>
> The *ONLY* P2P protocol that I know of that has native NAT traversal
> is IAX / IAX2.
>
> David Sugar, if you are reading this, I would very much appreciate it
> if you would code a software similar to SIPwitch, especially for IAX
> for example called IAXwitch. If available for Debian/Ubuntu it should be
> able to run on the Raspberry PI.
>
> David, if you would be willing to write IAXwitch for Raspberry Debian,
> I would sponsor a Raspberry PI for you.
>
> There is a program called YATE that has an IAX client and server in it,
> among many other things.
>
> In my opinion, to have a simple P2P, secure telecom that any end user
> can install and it just works, the only way is to use IAX protocol. I use
> FreePP, which used to be available for PC and can confirm that when
> traveling I have been able to telecommunicate over a triple-NAT as if
> the 3 NATs were not there. It always works with no kluges like STUN,
> ICE, and voice quality is excellent.
>
> The fact that IAX was originally written as an Asterisk trunking protocol
> does not matter; it has been used for P2P by Firefly, Verbiage, and
> FreePP.
> In the old modem days, people used IAX in places like Eygpt and
> Pakistan and always got their msgs through.
>
> David, if you really are interested in weaning people away from Skype
> to an open source equivalent, please, pleasse, pleasssse code a
> program IAXwitch.
>
> Regards, Earl