Re: [Iaxclient-devel] Crash w/ IAXComm talking to another IAXComm

[Nathan S. <iax...@np...>]

Michael Van Donselaar wrote:

> 
>
>  
>
>>-----Original Message-----
>>From: iax...@li... 
>>[mailto:iax...@li...] On 
>>Behalf Of Nathan Sharp
>>Sent: Tuesday, November 09, 2004 11:06 AM
>>To: mi...@va...
>>Cc: iax...@li...
>>Subject: Re: [Iaxclient-devel] Crash w/ IAXComm talking to 
>>another IAXComm
>>
>>Michael,
>>  Thanks so much for the quick reply!  To answer your 
>>questions, I am calling through an Asterisk 1.0.1 server 
>>(with Speex disabled).  I am not using the echo cancellation 
>>feature.  
>>
>>  Could this be the same problem?
>>http://sourceforge.net/mailarchive/forum.php?thread_id=5836576
>>&forum_id=29380
>>
>>    
>>
>
>I'm really not totally sure, but I think there's still a problem with codec
>negotiation.
>
>Could you try calling peer to peer and see what you get?
>  
>
Sure enough, I did just find something that works based on that comment:
disallow=all
allow=gsm

in the iax.conf setting for this client.  I can now dial to FWD fine (I 
can't try the RH8 box until I get home).  As an aside, I tried 
allow=ulaw first (so my asterisk box wouldn't have to convert when 
connecting to FWD), and it crashed as well.  Thanks for the hint!  That 
will get me running for now (although I await a better version soon!)

>I am also going to post new binaries tonite or tomorrow compiled on RH9 and
>WinXP.  They will have CVS updates for iaxclient, and be set to prefer iLBC.
>
>  
>
>>  Only the existence of NAT or not doesn't seem to matter for 
>>me.  I have hooked up my asterisk server to a FWD account 
>>using iax2.fwdnet.net and I've found that the client crashes 
>>also if I try to connect to FWD through my asterisk server.   
>>
>>Feature Requests?  My top priorities, in order:
>>1) Secure against malicious incoming packets
>>    
>>
>
>I don't know what to do here
>  
>
Code review and time will find these.  It is a small target for malware 
writers right now too.

>  
>
>>2) Low Latency (10-2004 version seems much better than the 
>>earlier version, when it doesn't crash). 
>>    
>>
>
>See Steve Kann's comments about this.  I'll recompile with a lower latency,
>and see how it works.
>  
>
Yea, I found some stuff on the environment variable.  The Linux version 
seems much better than the Windows version.  I mention it because it 
makes the most difference to the "naturalness" of phone conversations.  
It is one of the main reasons I don't use a cell phone.  I appreciate 
that the software has gotten better and that you guys are still working 
on it :-)

>  
>
>>3) Reliable.  The earlier version has never crashed yet on 
>>me, it just has much higher latency.
>>    
>>
>
>That's a feature everyone can use!
>
>  
>
>>4) Easy to install/use (so I can hand it out to family and 
>>friends).  You are pretty close on this front already.  There 
>>are a couple of minor GUI issues which could be cleaned up.
>>    
>>
>
>You shoulda seen the earlier versions!  I think I've got the install down to
>the easiest I can without going to the point of using an installer:  a
>single file that you can run from anywhere.
>  
>
Good Work!

>Quick hint that I should put in the QUICKSTART:  I trim down the registry
>and export the HKEY/CU/Software/iaxcomm node and ship my family the binary
>and the reg key. "Double click the .reg file then double click the phone."
>  
>
Great idea!

>Since this list is for all iaxclient stuff, email me off list with your GUI
>ideas.
>  
>
Will do.

>  
>
>>5) Control over the encoding format
>>    
>>
>
>Yes, I need to add controls to override the defaults.
> 
>  
>
>>And as an aside for later: Some type of network level 
>>encryption would be great (if it didn't make latency bad).
>>    
>>
>
>Any ideas on this, guys?
>
>I know just enough about encryption to know that ROT-13 ing the encoded
>payload is probably not the route to take.
>  
>
This is somewhat of a pipe dream, I think.  I dream of software that 
makes encryption so easy to use that I can use it with my mother.  I 
have no expectations of the such anytime soon.  I just saw the tunneling 
idea on the listserve and that will work for the time being.