[CUWiN-Dev] Re: VoIP Test In Ghana

[John Atkinson]

Brandon,

On 6/30/06, Brandon Bowersox <brandon at ojctech.com> wrote:
> John,
> 
> This is wonderful!  A few questions:
> 1. Are you using SJPhone direct to SJPhone on the other end, or is  
> there a server such as asterisk running in between (which could  
> provide voicemail, etc)?

Yeah, SJphone to SJphone direct, but the server with voicemail sounds interesting, I'll look into it.

> 2. Will users dial each other directly by IP address?

Yeah, that's the way it works.  I don't want it to be like that, but I don't want traffic from VoIP using the already saturated Internet connection.  I heard of a way to hack Skype around to work on a corporate LAN, but I haven't tried anything.  I'm guessing that if we used something like asterisk somewhere on the mesh then IP would be translated into Names at a database there; so much more user friendly.  SJphone isn't horrible though, it has a phonebook which can equate IP's to Names, and it has some feature called "neighborhood" which tries to automatically detect other SJphone hosts nearby.

-John

> 
> Brandon
> 
> On Jun 30, 2006, at 5:51 AM, John Atkinson wrote:
> 
> > Ran some VoIP stuff last night using headphone/mic setups and a
> > shareware app branded SJPhone.  We did it on a ~6km link that has
> > about 500kbit/s throughput.  The only mods to the CuWinWare were
> > acknowledgement and clear-to-send timeouts:
> >
> > # sysctl -w hw.ath0.acktimeout=100
> > hw.ath0.acktimeout: 48 -> 100
> > #sysctl -w hw.ath0.ctstimeout=100
> > hw.ath0.acktimeout: 48 -> 100
> >
> > I put those commands in rc.conf so my CD booting nodes boot with them
> > by default (or almost default).
> >
> > We also changed from SIP to H323 on the SJphone app.  I didn't get a
> > chance to go back to SIP, but I will.
> >
> > The voice was perfect, better than a cellphone, err, at least a
> > Ghanaian cellphone conversation.  But it was nightime, so no
> > equatorial heat to burn the wifi throughput, and there wasn't much
> > traffic on the network to compete against.  Also, the connection was a
> > one-hop, no repeater nodes involved.
> >
> > We'll start rolling these out to anyone that wants to buy a headset
> > and until any problems arise.  Not even close to enough satellite
> > Internet bandwidth to start making calls outside of the mesh (which
> > will bring in an automatic latency of at least 400ms), but you gotta
> > start somewhere.
> >
> > -John
> > _______________________________________________
> > CU-Wireless-Dev mailing list
> > CU-Wireless-Dev at lists.cuwireless.net
> > http://lists.chambana.net/cgi-bin/listinfo/cu-wireless-dev
> 
>