[jitsi-dev] Autoanswer CallPanel not opening


#1

While testing the Auto Answer feature I have found a possible race
condition on opening the CallPanel. The first call works without a
problem but if the call is ended then made a second time the
PreCallDialog is opened but the CallPanel is not. I am testing with an
Asterisk server with 2 nodes with node A calling B both times. Tracing
through the code I found that the callStateChanged() event listener
(line 110 in CallManger.java) is not getting hit. From what I can tell
the event is triggered by the following code path. MediaAwareCall.java
peerStateChanged() calls super.setCallState() in Call.java which calls
fireCallChangeEvent().

I am running Windows and have had this occur on both the 1.0 binary and
with the 1.0 and nightly source code built with Netbeans.

Has anyone experienced this behavior?

Thanks,

Michael


#2

Hey,

strange I was testing this and cannot reproduce it. Making calls and
hanging up, making second call and still the call dialog is shown as
expected. I tested with iptel and an asterisk server.
Do you reproduce it on every call?
The PreCallDialog is closed and nothing happens after this on the second call?

Thanks
damencho

···

On Sat, Apr 14, 2012 at 4:51 AM, <jmichael.carter@l-3com.com> wrote:

While testing the Auto Answer feature I have found a possible race condition
on opening the CallPanel. The first call works without a problem but if the
call is ended then made a second time the PreCallDialog is opened but the
CallPanel is not. I am testing with an Asterisk server with 2 nodes with
node A calling B both times. Tracing through the code I found that the
callStateChanged() event listener (line 110 in CallManger.java) is not
getting hit. From what I can tell the event is triggered by the following
code path. MediaAwareCall.java peerStateChanged() calls
super.setCallState() in Call.java which calls fireCallChangeEvent().

I am running Windows and have had this occur on both the 1.0 binary and with
the 1.0 and nightly source code built with Netbeans.

Has anyone experienced this behavior?

Thanks,

Michael


#3

I have been having problems getting the Windows installer to be built
using the steps I have found here:

http://java.net/projects/jitsi/lists/dev/archive/2012-03/message/48

I get the following after performing ant rebuild and then running ant
build-installation-wix. Does anyone have any insight to why.

$ ant build-installation-wix
Buildfile: D:\jitsi\build.xml

-pre-version:

version:
    [javac] D:\jitsi\build.xml:466: warning: 'includeantruntime' was not
set, defaulting to build.sysclasspath=last; set to false for repeatable
builds
    [javac] Compiling 3 source files to D:\jitsi\classes
     [echo] Jitsi version 1.1.0-0.build.by.SVN

load-properties:

build-installation-wix:

clean-install-windows:
    [mkdir] Created dir: D:\jitsi\release\windows
    [mkdir] Created dir: D:\jitsi\release\windows\tmp

build-installation-wix-base:
[propertyfile] Creating new property file:
D:\jitsi\release\windows\versionupdate.properties
    [mkdir] Created dir: D:\jitsi\release\windows\tmp\light
     [exec] rm.exe -f ../../../../resources/install/windows/config.h
     [exec] echo.exe -e '#define PRODUCTNAME "Jitsi"' >
/cygdrive/d/jitsi/release/windows/tmp/light/config.h
     [exec] C:/mingw/x86/bin/windres.exe
-I../../../../resources/install/windows
-ID:/jitsi/release/windows/tmp/light run.rc -O coff -o
D:/jitsi/release/windows/tmp/light/run.res
     [exec] Makefile:51: recipe for target
`/cygdrive/d/jitsi/release/windows/tmp/light/run.res' failed
     [exec] C:\mingw\x86\bin\windres.exe: preprocessing failed.
     [exec] make: ***
[/cygdrive/d/jitsi/release/windows/tmp/light/run.res] Error 1

BUILD FAILED
D:\jitsi\resources\install\build.xml:302: The following error occurred
while executing this line:
D:\jitsi\resources\install\build.xml:403: exec returned: 2

Total time: 3 seconds

Thanks,

Michael


#4

Damencho

I have only been able to reliably reproduce this when testing with a 1Gb managed switch. Once a bit of latency was introduced this problem stopped occurring. If you have not been able to reliably reproduce the error I will assume that it is an artifact of my current test environment that contributed to the error. I will continue to test and if I can isolate more data I will report back.

Michael

···

-----Original Message-----

From: damencho@damencho.com [mailto:damencho@damencho.com] On Behalf Of Damian Minkov

Sent: Wednesday, April 25, 2012 3:42 AM
To: dev@jitsi.java.net
Subject: [jitsi-dev] Re: Autoanswer CallPanel not opening

Hey,

strange I was testing this and cannot reproduce it. Making calls and hanging up, making second call and still the call dialog is shown as expected. I tested with iptel and an asterisk server.
Do you reproduce it on every call?
The PreCallDialog is closed and nothing happens after this on the second call?

Thanks
damencho

On Sat, Apr 14, 2012 at 4:51 AM, <jmichael.carter@l-3com.com> wrote:

While testing the Auto Answer feature I have found a possible race
condition on opening the CallPanel. The first call works without a
problem but if the call is ended then made a second time the
PreCallDialog is opened but the CallPanel is not. I am testing with
an Asterisk server with 2 nodes with node A calling B both times.
Tracing through the code I found that the
callStateChanged() event listener (line 110 in CallManger.java) is not
getting hit. From what I can tell the event is triggered by the
following code path. MediaAwareCall.java peerStateChanged() calls
super.setCallState() in Call.java which calls fireCallChangeEvent().

I am running Windows and have had this occur on both the 1.0 binary
and with the 1.0 and nightly source code built with Netbeans.

Has anyone experienced this behavior?

Thanks,

Michael