[jitsi-dev] Might be some bug in ICE4J.


#1

Hi all
     I am now analyzing ice4j these days. Some questions make me confusing. I doubt there is some bug there.

1. In Agent.java in function checkListStatesUpdated(),
     See below code fragment:
          if(compatibilityMode == CompatibilityMode.GTALK
                            && stunKeepAliveThread == null)
                    {
                        // schedule STUN checks for selected candidates
                        scheduleSTUNKeepAlive();
                    }
                    else
                    {
                        scheduleTermination();
                    }

       I think scheduleSTUNKeepAlive should be called for both cases. Why terminate the agent?
2. PaceMaker.run(), will never exit , until the stack shutdown. I have confirmed this by the log.

   Anybody can give me some explanation?
   Besides, I'd like to know the maturity of ice4j, I want to use it in my project, but not sure whether it does work .

Thanks and Regards,
Haiming Wang


#2

Hi,

Le 22/08/11 11:28, haiming.2.wang@nokia.com a �crit :

Hi all
     I am now analyzing ice4j these days. Some questions make me confusing. I doubt there is some bug there.

1. In Agent.java in function checkListStatesUpdated(),

See below code fragment:
*if*(compatibilityMode== CompatibilityMode./GTALK/
&& stunKeepAliveThread == *null*)
                    {
// schedule STUN checks for selected candidates
                        scheduleSTUNKeepAlive();
                    }
*else*
                    {
                        scheduleTermination();
                    }
  I think scheduleSTUNKeepAliveshould be called for both cases. Why terminate the agent?

Yes you are right, standard ICE agent have to send keep alive. Except that it has to send Binding Indication instead of Binding request. We will add this feature ASAP.

2. PaceMaker.run(), will never exit , until the stack shutdown. I
    have confirmed this by the log.

OK, we will look at it when time permits.

   Anybody can give me some explanation?
   Besides, I'd like to know the maturity of ice4j, I want to use it in my project, but not sure whether it does work .

Jitsi uses Ice4j for XMPP call. And we make several XMPP calls every days... so it is stable and it works.

Regards,

···

--
Seb

Thanks and Regards,
Haiming Wang


#3

first I am VERY happy with the progress of the jitsi project
(using/watching/participating now since few years already) !
Really great software (stable, very good audio & video quality;
encryption works; no need to use Skype anymore...)

I have a little issue with the automatic signing into my IPTEL account
(same issue has been described also some time ago in the forum):

after restarting jitsi (now version 3625 on MacBook Pro 2011, MacOS
10.6.8) the iptel account asks again for the password (although stored).
The window usually pops up two times, password has to be provided 2x,
then the login is fine.
This happens quite often (but not after each new start) with IPTEL, but
never with IPPI (my 2nd SIP account; jabber accounts work nicely)
(if the IPTEL service is responsible itself for this, then sorry for the
inconvenience)

kind regards, Mr. Smith


#4

Hey there,

На 22.08.11 16:01, Mr.Smith написа:

first I am VERY happy with the progress of the jitsi project
(using/watching/participating now since few years already) !
Really great software (stable, very good audio & video quality;
encryption works; no need to use Skype anymore...)

Thank you for the kind words and very happy to know we're being helpful.
It's also been nice to have you around for a few years :slight_smile:

I have a little issue with the automatic signing into my IPTEL account
(same issue has been described also some time ago in the forum):

after restarting jitsi (now version 3625 on MacBook Pro 2011, MacOS
10.6.8) the iptel account asks again for the password (although stored).
The window usually pops up two times, password has to be provided 2x,
then the login is fine.
This happens quite often (but not after each new start) with IPTEL, but
never with IPPI (my 2nd SIP account; jabber accounts work nicely)
(if the IPTEL service is responsible itself for this, then sorry for the
inconvenience)

Yup. I've also been seeing this one for quite a while now but
unfortunately haven't had the time to look into it. Real bummer!

It would basically happen almost every time I connect and sometimes I
would need to enter my password several times.

To me this only happens to me with iptel.org accounts.

Emil