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

[Steve K. <st...@st...>]

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?
>  
>
It could be another problem in native transfer, though, like the one we 
fixed a couple of weeks ago (Are you binaries from past that date?).  I 
think this is the problem referred to in that post.  I fixed that on 10/29.



>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
>  
>
This, and encryption below, seem to be libiax2 and IAX2 protocol 
issues.  There's a bug in digium's CVS discussing IAX2 encryption.

Of course, if you control both endpoints, you could always run IAX2 (and 
iaxclient) through an encrypted tunnel.  I will probably offer an API in 
iaxclient so that you can integrate something like this at the code 
level soon, but even without that, you can tunnel easily because IAX2 is 
so nat-friendly.

I.e. you run like this:  [iaxclient] <localhost interface> [tunnel 
program] <encrypted tunneled link over internet] <tunnel program> 
[localhost interface] <asterisk>.

You'd make calls, register, etc via a localhost URL, I.e. dial 
foo:bar@localhost:port/extension.

This all works fine.  I think zebedee is a program that could do the 
tunneling for you.

[...]

>
>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.
>  
>

See above, and bugs.digium.com for info..

-SteveK