Thanks for your reply.
I worked on the ICE project. The implementation of the ICE protocol is not
fully completed yet.
There are still some development to be done (I'll be working on it)
There will be a new project called ice4j, which will include the code I
developed so far
This project will then later be used to integrate the ICE feature to
Awesome! I'll be one of the first testers then
From what I understood by going through the issue 435, I don't think there
will be a conflict.
The problem comes from not using a STUN server (I'm behind a NAT). I
checked with another SIP client and I get the same 406 "Not available"
error with ekiga.net when I disable the STUN (otherwise it works).
ICE is used for connectivity checks between two client programs.
In this issue (435), its a connection failure to a SIP proxy. So I don't
think we need to go
for a complete ICE connectivity check to establish a connection with a SIP
So I think you would be OK.
From what I understood (you might correct me, I'm new to
SIP/STUN/ICE), ICE is basically about determining if nothing, STUN or
TURN should be used. I know I have to use STUN and I want to enable it
(it failed for now but I didn't take the time to look further). Will
ice4j rely on stun4j for STUN?
On Fri, Aug 22, 2008 at 5:51 AM, Namal Senarathne <email@example.com> wrote: