[jitsi-dev] Some weird call behavior


#1

Hey

I had a bit a weird experience today when I connected to my SIP provider
from the office computer. It doesn't have a Mic connected, neither a webcam,
but a working sound output.
- An incoming call was rejected
- An outgoing call failed (not acceptable)
- Disabling all video codecs caused an exception when trying to start a call

I guess these were in the end all caused by the missing microphone, but we
definitely need to work on the error-handling...

Ingo


#2

totally agree!

···

Am 26.03.2013 20:37, schrieb Ingo Bauersachs:

Hey

I had a bit a weird experience today when I connected to my SIP provider
from the office computer. It doesn't have a Mic connected, neither a webcam,
but a working sound output.
- An incoming call was rejected
- An outgoing call failed (not acceptable)
- Disabling all video codecs caused an exception when trying to start a call

I guess these were in the end all caused by the missing microphone, but we
definitely need to work on the error-handling...

Ingo


#3

totally agree!

Hey

I had a bit a weird experience today when I connected to my SIP provider
from the office computer. It doesn't have a Mic connected, neither a webcam,
but a working sound output.
- An incoming call was rejected

This part shouldn't happen.

- An outgoing call failed (not acceptable)

Sounds like this was returned by the server so not much we could do
about it. Damencho, didn't you recently implement an option that shows
users a warning dialog when trying to make audio calls with no microphone?

- Disabling all video codecs caused an exception when trying to start a call

Nothing visible to the user then?

Emil

···

On 26.03.13, 23:28, Buddy Butterfly wrote:

Am 26.03.2013 20:37, schrieb Ingo Bauersachs:

I guess these were in the end all caused by the missing microphone, but we
definitely need to work on the error-handling...

Ingo

--
https://jitsi.org


#4

Hi,

we also discovered with a replace of Jitsi 1.1 with Jitsi 2
on a Windows XP system that we were not able to get sound working
at all. Reverted to 1.1 on this machine. Will try to replay it
and send logs...

···

Am 26.03.2013 23:34, schrieb Emil Ivov:

On 26.03.13, 23:28, Buddy Butterfly wrote:

totally agree!

Am 26.03.2013 20:37, schrieb Ingo Bauersachs:

Hey

I had a bit a weird experience today when I connected to my SIP provider
from the office computer. It doesn't have a Mic connected, neither a webcam,
but a working sound output.
- An incoming call was rejected

This part shouldn't happen.

- An outgoing call failed (not acceptable)

Sounds like this was returned by the server so not much we could do
about it. Damencho, didn't you recently implement an option that shows
users a warning dialog when trying to make audio calls with no microphone?

- Disabling all video codecs caused an exception when trying to start a call

Nothing visible to the user then?

Emil

I guess these were in the end all caused by the missing microphone, but we
definitely need to work on the error-handling...

Ingo


#5

I had a bit a weird experience today when I connected to my SIP
provider from the office computer. It doesn't have a Mic connected,
neither a webcam, but a working sound output.
- An incoming call was rejected

This part shouldn't happen.

Well, it might have something to do with the FritzBox that was registered at
the same time. The codecs shown in the pcap were only g.729 and tel-event.

- An outgoing call failed (not acceptable)

Sounds like this was returned by the server so not much we could do
about it. Damencho, didn't you recently implement an option that shows
users a warning dialog when trying to make audio calls with no microphone?

Was that before or after 2.0 stable?

- Disabling all video codecs caused an exception when trying to start a

call

Nothing visible to the user then?

The general exception dialog.

(I was talking about SIP btw.)

Emil

I guess these were in the end all caused by the missing microphone, but

we

definitely need to work on the error-handling...

Ingo

Ingo


#6

Yes (r10585), and should warn when no audio capture device is
configured or there are no audio codecs selected.

···

On Wed, Mar 27, 2013 at 12:34 AM, Emil Ivov <emcho@jitsi.org> wrote:

Sounds like this was returned by the server so not much we could do
about it. Damencho, didn't you recently implement an option that shows
users a warning dialog when trying to make audio calls with no microphone?


#7

We may also want to try the latest nightly.

Emil

···

On 26.03.13, 23:36, Buddy Butterfly wrote:

Hi,

we also discovered with a replace of Jitsi 1.1 with Jitsi 2
on a Windows XP system that we were not able to get sound working
at all. Reverted to 1.1 on this machine. Will try to replay it
and send logs...

Am 26.03.2013 23:34, schrieb Emil Ivov:

On 26.03.13, 23:28, Buddy Butterfly wrote:

totally agree!

Am 26.03.2013 20:37, schrieb Ingo Bauersachs:

Hey

I had a bit a weird experience today when I connected to my SIP provider
from the office computer. It doesn't have a Mic connected, neither a webcam,
but a working sound output.
- An incoming call was rejected

This part shouldn't happen.

- An outgoing call failed (not acceptable)

Sounds like this was returned by the server so not much we could do
about it. Damencho, didn't you recently implement an option that shows
users a warning dialog when trying to make audio calls with no microphone?

- Disabling all video codecs caused an exception when trying to start a call

Nothing visible to the user then?

Emil

I guess these were in the end all caused by the missing microphone, but we
definitely need to work on the error-handling...

Ingo

--
https://jitsi.org


#8

I had a bit a weird experience today when I connected to my SIP
provider from the office computer. It doesn't have a Mic connected,
neither a webcam, but a working sound output.
- An incoming call was rejected

This part shouldn't happen.

Well, it might have something to do with the FritzBox that was registered at
the same time. The codecs shown in the pcap were only g.729 and tel-event.

- An outgoing call failed (not acceptable)

Sounds like this was returned by the server so not much we could do
about it. Damencho, didn't you recently implement an option that shows
users a warning dialog when trying to make audio calls with no microphone?

Was that before or after 2.0 stable?

After. Last week I think.

- Disabling all video codecs caused an exception when trying to start a

call

Nothing visible to the user then?

The general exception dialog.

Sounds like this could be easily improved.

(I was talking about SIP btw.)

Yup got that.

Emil

···

On 26.03.13, 23:51, Ingo Bauersachs wrote:

Emil

I guess these were in the end all caused by the missing microphone, but

we

definitely need to work on the error-handling...

Ingo

Ingo

--
https://jitsi.org


#9

We may also want to try the latest nightly.

And of course I meant "_You_ may want to..."

Sorry about that.

Emil

···

On 26.03.13, 23:42, Emil Ivov wrote:

Emil

On 26.03.13, 23:36, Buddy Butterfly wrote:

Hi,

we also discovered with a replace of Jitsi 1.1 with Jitsi 2
on a Windows XP system that we were not able to get sound working
at all. Reverted to 1.1 on this machine. Will try to replay it
and send logs...

Am 26.03.2013 23:34, schrieb Emil Ivov:

On 26.03.13, 23:28, Buddy Butterfly wrote:

totally agree!

Am 26.03.2013 20:37, schrieb Ingo Bauersachs:

Hey

I had a bit a weird experience today when I connected to my SIP provider
from the office computer. It doesn't have a Mic connected, neither a webcam,
but a working sound output.
- An incoming call was rejected

This part shouldn't happen.

- An outgoing call failed (not acceptable)

Sounds like this was returned by the server so not much we could do
about it. Damencho, didn't you recently implement an option that shows
users a warning dialog when trying to make audio calls with no microphone?

- Disabling all video codecs caused an exception when trying to start a call

Nothing visible to the user then?

Emil

I guess these were in the end all caused by the missing microphone, but we
definitely need to work on the error-handling...

Ingo

--
https://jitsi.org