[sip-comm-dev] No Hungup audio and video stream no stop


#1

Hi

I've reported few time an issue that i'm continue having also on latest releases of SC which i was hoping could be resolved in one of the latest build.
The problem is a missing hung-up during jingle calls that happen very often, one of the two parties involved in the call press the hung-up button, the call window is closed but the audio and video stream don't stop, the camera stay on and audio continue to playback. After such event, there is no way to make new calls and the only solution is to shutdown the app or kill via task manager.

Please let me know if any one has experienced this kind of issue, i remember that in some threads some one was talking about a rtp stream that is not close properly all the time?

If can help, in attach the log and cap of the client that supposes to hung-up.

Thanks
Fabio Galdi

Inizio messaggio inoltrato:

log.zip (30 KB)

···

Da: <fabio@telme.sg>
Data: 08 gennaio 2011 18.30.36 GMT+01.00
A: <fabio@telme.sg>
Oggetto: no hungup


#2

Hi Fabio,

I'm currently doing some latency tests with my Asterisk SIP- Echo. And it happened to me once or twice as well. The window closes - but the call is still open. I might have provoced that kind of behaviour by just closing the audio/video windows without pressing the hang up key before.

If I do that- the only way to end the call is to iniciate a new one and hang up. But then for the rest of the run of SC latency is nuts.

Conrad

-------- Original-Nachricht --------

···

Datum: Sat, 8 Jan 2011 18:37:19 +0100
Von: Fabio Telme <fabio@telme.sg>
An: dev@sip-communicator.dev.java.net
Betreff: [sip-comm-dev] No Hungup audio and video stream no stop

Hi

I've reported few time an issue that i'm continue having also on latest
releases of SC which i was hoping could be resolved in one of the latest
build.
The problem is a missing hung-up during jingle calls that happen very
often, one of the two parties involved in the call press the hung-up button,
the call window is closed but the audio and video stream don't stop, the
camera stay on and audio continue to playback. After such event, there is no
way to make new calls and the only solution is to shutdown the app or kill
via task manager.

Please let me know if any one has experienced this kind of issue, i
remember that in some threads some one was talking about a rtp stream that is not
close properly all the time?

If can help, in attach the log and cap of the client that supposes to
hung-up.

Thanks
Fabio Galdi

Inizio messaggio inoltrato:

> Da: <fabio@telme.sg>
> Data: 08 gennaio 2011 18.30.36 GMT+01.00
> A: <fabio@telme.sg>
> Oggetto: no hungup
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

Hi Conrad,

yes it's true if someone accidentally close the call window there is no way to hungup the call. i think the windows close command should execute also the hung-up function.
To avoid the call that don't hung-up correctly don't you think that the hung-up command should execute some harder closure of all the processes instead of sending only the hung-up signal ? may be this is not the correct approach but at least it can make sure that the next call will be possible and there will be not process left open behind. It's just an idea :slight_smile:

Regards
Fabio

···

Il giorno 09/gen/2011, alle ore 16.22, Conrad Beckert ha scritto:

Hi Fabio,

I'm currently doing some latency tests with my Asterisk SIP- Echo. And it happened to me once or twice as well. The window closes - but the call is still open. I might have provoced that kind of behaviour by just closing the audio/video windows without pressing the hang up key before.

If I do that- the only way to end the call is to iniciate a new one and hang up. But then for the rest of the run of SC latency is nuts.

Conrad

-------- Original-Nachricht --------

Datum: Sat, 8 Jan 2011 18:37:19 +0100
Von: Fabio Telme <fabio@telme.sg>
An: dev@sip-communicator.dev.java.net
Betreff: [sip-comm-dev] No Hungup audio and video stream no stop

Hi

I've reported few time an issue that i'm continue having also on latest
releases of SC which i was hoping could be resolved in one of the latest
build.
The problem is a missing hung-up during jingle calls that happen very
often, one of the two parties involved in the call press the hung-up button,
the call window is closed but the audio and video stream don't stop, the
camera stay on and audio continue to playback. After such event, there is no
way to make new calls and the only solution is to shutdown the app or kill
via task manager.

Please let me know if any one has experienced this kind of issue, i
remember that in some threads some one was talking about a rtp stream that is not
close properly all the time?

If can help, in attach the log and cap of the client that supposes to
hung-up.

Thanks
Fabio Galdi

Inizio messaggio inoltrato:

Da: <fabio@telme.sg>
Data: 08 gennaio 2011 18.30.36 GMT+01.00
A: <fabio@telme.sg>
Oggetto: no hungup

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#4

Hey folks,

Indeed, closing the call dialog doesn't seem to end the call any more.
We'll take care of this.

Cheers,
Emil

P.S. In case anyone ever feels like it, patches are more than welcome in
such cases, since we currently have a lot on our hands and waiting on us
(and by us I mean BlueJimp) to handle all issues would probably take a
while.

На 11.01.11 00:19, Fabio Telme написа:

···

Hi Conrad,

yes it's true if someone accidentally close the call window there is no way to hungup the call. i think the windows close command should execute also the hung-up function.
To avoid the call that don't hung-up correctly don't you think that the hung-up command should execute some harder closure of all the processes instead of sending only the hung-up signal ? may be this is not the correct approach but at least it can make sure that the next call will be possible and there will be not process left open behind. It's just an idea :slight_smile:

Regards
Fabio

Il giorno 09/gen/2011, alle ore 16.22, Conrad Beckert ha scritto:

Hi Fabio,

I'm currently doing some latency tests with my Asterisk SIP- Echo. And it happened to me once or twice as well. The window closes - but the call is still open. I might have provoced that kind of behaviour by just closing the audio/video windows without pressing the hang up key before.

If I do that- the only way to end the call is to iniciate a new one and hang up. But then for the rest of the run of SC latency is nuts.

Conrad

-------- Original-Nachricht --------

Datum: Sat, 8 Jan 2011 18:37:19 +0100
Von: Fabio Telme <fabio@telme.sg>
An: dev@sip-communicator.dev.java.net
Betreff: [sip-comm-dev] No Hungup audio and video stream no stop

Hi

I've reported few time an issue that i'm continue having also on latest
releases of SC which i was hoping could be resolved in one of the latest
build.
The problem is a missing hung-up during jingle calls that happen very
often, one of the two parties involved in the call press the hung-up button,
the call window is closed but the audio and video stream don't stop, the
camera stay on and audio continue to playback. After such event, there is no
way to make new calls and the only solution is to shutdown the app or kill
via task manager.

Please let me know if any one has experienced this kind of issue, i
remember that in some threads some one was talking about a rtp stream that is not
close properly all the time?

If can help, in attach the log and cap of the client that supposes to
hung-up.

Thanks
Fabio Galdi

Inizio messaggio inoltrato:

Da: <fabio@telme.sg>
Data: 08 gennaio 2011 18.30.36 GMT+01.00
A: <fabio@telme.sg>
Oggetto: no hungup

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org PHONE: +33.1.77.62.43.30
http://sip-communicator.org FAX: +33.1.77.62.47.31

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#5

Hi Conrad, Fabio,

Thanks for reporting the issue! I'm currently working on fixing it.

I'll let you know as soon as we have a build that contains the fix.

Cheers,
Yana

···

On Jan 11, 2011, at 12:50 PM, Emil Ivov wrote:

Hey folks,

Indeed, closing the call dialog doesn't seem to end the call any more.
We'll take care of this.

Cheers,
Emil

P.S. In case anyone ever feels like it, patches are more than welcome in
such cases, since we currently have a lot on our hands and waiting on us
(and by us I mean BlueJimp) to handle all issues would probably take a
while.

На 11.01.11 00:19, Fabio Telme написа:

Hi Conrad,

yes it's true if someone accidentally close the call window there is no way to hungup the call. i think the windows close command should execute also the hung-up function.
To avoid the call that don't hung-up correctly don't you think that the hung-up command should execute some harder closure of all the processes instead of sending only the hung-up signal ? may be this is not the correct approach but at least it can make sure that the next call will be possible and there will be not process left open behind. It's just an idea :slight_smile:

Regards
Fabio

Il giorno 09/gen/2011, alle ore 16.22, Conrad Beckert ha scritto:

Hi Fabio,

I'm currently doing some latency tests with my Asterisk SIP- Echo. And it happened to me once or twice as well. The window closes - but the call is still open. I might have provoced that kind of behaviour by just closing the audio/video windows without pressing the hang up key before.

If I do that- the only way to end the call is to iniciate a new one and hang up. But then for the rest of the run of SC latency is nuts.

Conrad

-------- Original-Nachricht --------

Datum: Sat, 8 Jan 2011 18:37:19 +0100
Von: Fabio Telme <fabio@telme.sg>
An: dev@sip-communicator.dev.java.net
Betreff: [sip-comm-dev] No Hungup audio and video stream no stop

Hi

I've reported few time an issue that i'm continue having also on latest
releases of SC which i was hoping could be resolved in one of the latest
build.
The problem is a missing hung-up during jingle calls that happen very
often, one of the two parties involved in the call press the hung-up button,
the call window is closed but the audio and video stream don't stop, the
camera stay on and audio continue to playback. After such event, there is no
way to make new calls and the only solution is to shutdown the app or kill
via task manager.

Please let me know if any one has experienced this kind of issue, i
remember that in some threads some one was talking about a rtp stream that is not
close properly all the time?

If can help, in attach the log and cap of the client that supposes to
hung-up.

Thanks
Fabio Galdi

Inizio messaggio inoltrato:

Da: <fabio@telme.sg>
Data: 08 gennaio 2011 18.30.36 GMT+01.00
A: <fabio@telme.sg>
Oggetto: no hungup

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org PHONE: +33.1.77.62.43.30
http://sip-communicator.org FAX: +33.1.77.62.47.31

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#6

For the record,

Yana has just committed a fix for this one that should be available with
build 3221 and all following.

Cheers,
Emil

На 11.01.11 13:45, Yana Stamcheva написа:

···

Hi Conrad, Fabio,

Thanks for reporting the issue! I'm currently working on fixing it.

I'll let you know as soon as we have a build that contains the fix.

Cheers,
Yana

On Jan 11, 2011, at 12:50 PM, Emil Ivov wrote:

Hey folks,

Indeed, closing the call dialog doesn't seem to end the call any more.
We'll take care of this.

Cheers,
Emil

P.S. In case anyone ever feels like it, patches are more than welcome in
such cases, since we currently have a lot on our hands and waiting on us
(and by us I mean BlueJimp) to handle all issues would probably take a
while.

На 11.01.11 00:19, Fabio Telme написа:

Hi Conrad,

yes it's true if someone accidentally close the call window there is no way to hungup the call. i think the windows close command should execute also the hung-up function.
To avoid the call that don't hung-up correctly don't you think that the hung-up command should execute some harder closure of all the processes instead of sending only the hung-up signal ? may be this is not the correct approach but at least it can make sure that the next call will be possible and there will be not process left open behind. It's just an idea :slight_smile:

Regards
Fabio

Il giorno 09/gen/2011, alle ore 16.22, Conrad Beckert ha scritto:

Hi Fabio,

I'm currently doing some latency tests with my Asterisk SIP- Echo. And it happened to me once or twice as well. The window closes - but the call is still open. I might have provoced that kind of behaviour by just closing the audio/video windows without pressing the hang up key before.

If I do that- the only way to end the call is to iniciate a new one and hang up. But then for the rest of the run of SC latency is nuts.

Conrad

-------- Original-Nachricht --------

Datum: Sat, 8 Jan 2011 18:37:19 +0100
Von: Fabio Telme <fabio@telme.sg>
An: dev@sip-communicator.dev.java.net
Betreff: [sip-comm-dev] No Hungup audio and video stream no stop

Hi

I've reported few time an issue that i'm continue having also on latest
releases of SC which i was hoping could be resolved in one of the latest
build.
The problem is a missing hung-up during jingle calls that happen very
often, one of the two parties involved in the call press the hung-up button,
the call window is closed but the audio and video stream don't stop, the
camera stay on and audio continue to playback. After such event, there is no
way to make new calls and the only solution is to shutdown the app or kill
via task manager.

Please let me know if any one has experienced this kind of issue, i
remember that in some threads some one was talking about a rtp stream that is not
close properly all the time?

If can help, in attach the log and cap of the client that supposes to
hung-up.

Thanks
Fabio Galdi

Inizio messaggio inoltrato:

Da: <fabio@telme.sg>
Data: 08 gennaio 2011 18.30.36 GMT+01.00
A: <fabio@telme.sg>
Oggetto: no hungup

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org PHONE: +33.1.77.62.43.30
http://sip-communicator.org FAX: +33.1.77.62.47.31

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org PHONE: +33.1.77.62.43.30
http://sip-communicator.org FAX: +33.1.77.62.47.31

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#7

Hi

Yes, i'm already using it and it works fine !!!

Thanks Yana.

Regards
Fabio

···

Il giorno 11/gen/2011, alle ore 17.58, Emil Ivov ha scritto:

For the record,

Yana has just committed a fix for this one that should be available with
build 3221 and all following.

Cheers,
Emil

На 11.01.11 13:45, Yana Stamcheva написа:

Hi Conrad, Fabio,

Thanks for reporting the issue! I'm currently working on fixing it.

I'll let you know as soon as we have a build that contains the fix.

Cheers,
Yana

On Jan 11, 2011, at 12:50 PM, Emil Ivov wrote:

Hey folks,

Indeed, closing the call dialog doesn't seem to end the call any more.
We'll take care of this.

Cheers,
Emil

P.S. In case anyone ever feels like it, patches are more than welcome in
such cases, since we currently have a lot on our hands and waiting on us
(and by us I mean BlueJimp) to handle all issues would probably take a
while.

На 11.01.11 00:19, Fabio Telme написа:

Hi Conrad,

yes it's true if someone accidentally close the call window there is no way to hungup the call. i think the windows close command should execute also the hung-up function.
To avoid the call that don't hung-up correctly don't you think that the hung-up command should execute some harder closure of all the processes instead of sending only the hung-up signal ? may be this is not the correct approach but at least it can make sure that the next call will be possible and there will be not process left open behind. It's just an idea :slight_smile:

Regards
Fabio

Il giorno 09/gen/2011, alle ore 16.22, Conrad Beckert ha scritto:

Hi Fabio,

I'm currently doing some latency tests with my Asterisk SIP- Echo. And it happened to me once or twice as well. The window closes - but the call is still open. I might have provoced that kind of behaviour by just closing the audio/video windows without pressing the hang up key before.

If I do that- the only way to end the call is to iniciate a new one and hang up. But then for the rest of the run of SC latency is nuts.

Conrad

-------- Original-Nachricht --------

Datum: Sat, 8 Jan 2011 18:37:19 +0100
Von: Fabio Telme <fabio@telme.sg>
An: dev@sip-communicator.dev.java.net
Betreff: [sip-comm-dev] No Hungup audio and video stream no stop

Hi

I've reported few time an issue that i'm continue having also on latest
releases of SC which i was hoping could be resolved in one of the latest
build.
The problem is a missing hung-up during jingle calls that happen very
often, one of the two parties involved in the call press the hung-up button,
the call window is closed but the audio and video stream don't stop, the
camera stay on and audio continue to playback. After such event, there is no
way to make new calls and the only solution is to shutdown the app or kill
via task manager.

Please let me know if any one has experienced this kind of issue, i
remember that in some threads some one was talking about a rtp stream that is not
close properly all the time?

If can help, in attach the log and cap of the client that supposes to
hung-up.

Thanks
Fabio Galdi

Inizio messaggio inoltrato:

Da: <fabio@telme.sg>
Data: 08 gennaio 2011 18.30.36 GMT+01.00
A: <fabio@telme.sg>
Oggetto: no hungup

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org PHONE: +33.1.77.62.43.30
http://sip-communicator.org FAX: +33.1.77.62.47.31

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org PHONE: +33.1.77.62.43.30
http://sip-communicator.org FAX: +33.1.77.62.47.31

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net