[jitsi-dev] NullPointerException on Jigasi outgoing calls


#1

Hi, Damian/Jitsi team.

I was doing some tests with outgoing calls. There are times where the
call is made and the participants can interact with each other, but
sometimes the call is taken but there is no audio, and at other times
the call is taken and after a few seconds it is hung.

I have seen in the logs some messages with NullPointerException which
perhaps could be related to this. I attached them.

Please let me know.

Kind regards,
Daniel

jigasi-outbound-call_1.asc (34 KB)

jigasi-outbound-call_2.asc (18.6 KB)


#2

Hi, Damian/Jitsi team.

Hi again.

I was doing some tests with outgoing calls. There are times where the
call is made and the participants can interact with each other, but
sometimes the call is taken but there is no audio, and at other times
the call is taken and after a few seconds it is hung.

I have seen in the logs some messages with NullPointerException which
perhaps could be related to this. I attached them.

Please let me know.

If you can comment on this, I would appreciate it.

Thanks in advance.

Kind regards,
Daniel

···

On 08/05/17 12:39, Daniel Bareiro wrote:


#3

Hi,

In the first log I see:

2017-05-08 09:52:42.089 INFO: [18027]
org.jitsi.jigasi.JvbConference.memberPresenceChanged().714 Member
presence change: ChatRoomMemberPresenceChangeEvent[type=MemberLeft
sourceRoom=net.java.sip.communicator.impl.protocol.jabber.ChatRoomJabberImpl@2644c15a
member=net.java.sip.communicator.impl.protocol.jabber.ChatRoomMemberJabberImpl@6bf20f56]
2017-05-08 09:52:42.089 INFO: [18027]
org.jitsi.jigasi.JvbConference.memberPresenceChanged().733 Member left
: OWNER focus
2017-05-08 09:52:42.089 INFO: [18027]
org.jitsi.jigasi.JvbConference.memberPresenceChanged().740 Focus

It is not normal the focus to leave the conference, in such cases the
UI automatically show a notification and start a reload countdown and
so is jigasi, stops the call.

You should check why is this happening by checking jicofo logs.

The second NPE I have seen it in other logs you sent and I'm not sure
why it happens, I suspect the early media SIP 183 and some race
condition ... but I'm not sure for that.
Can you check the pcap file (/var/log/jitsi/jigasi/log/) whether SIP
183 has SDP in its body?

Regards
damencho

···

On Thu, May 11, 2017 at 8:16 AM, Daniel Bareiro <daniel-listas@gmx.net> wrote:

On 08/05/17 12:39, Daniel Bareiro wrote:

Hi, Damian/Jitsi team.

Hi again.

I was doing some tests with outgoing calls. There are times where the
call is made and the participants can interact with each other, but
sometimes the call is taken but there is no audio, and at other times
the call is taken and after a few seconds it is hung.

I have seen in the logs some messages with NullPointerException which
perhaps could be related to this. I attached them.

Please let me know.

If you can comment on this, I would appreciate it.

Thanks in advance.

Kind regards,
Daniel

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#4

Hi,

Hi, Damian.

In the first log I see:

2017-05-08 09:52:42.089 INFO: [18027]
org.jitsi.jigasi.JvbConference.memberPresenceChanged().714 Member
presence change: ChatRoomMemberPresenceChangeEvent[type=MemberLeft
sourceRoom=net.java.sip.communicator.impl.protocol.jabber.ChatRoomJabberImpl@2644c15a
member=net.java.sip.communicator.impl.protocol.jabber.ChatRoomMemberJabberImpl@6bf20f56]
2017-05-08 09:52:42.089 INFO: [18027]
org.jitsi.jigasi.JvbConference.memberPresenceChanged().733 Member left
: OWNER focus
2017-05-08 09:52:42.089 INFO: [18027]
org.jitsi.jigasi.JvbConference.memberPresenceChanged().740 Focus

It is not normal the focus to leave the conference, in such cases the
UI automatically show a notification and start a reload countdown and
so is jigasi, stops the call.

You should check why is this happening by checking jicofo logs.

The second NPE I have seen it in other logs you sent and I'm not sure
why it happens, I suspect the early media SIP 183 and some race
condition ... but I'm not sure for that.
Can you check the pcap file (/var/log/jitsi/jigasi/log/) whether SIP
183 has SDP in its body?

Thanks for your reply.

I've been doing some more testing with outgoing calls and I've
encountered another issue. That's why I'm generating this sub thread.

For some reason, it seems that when I make a call and hang up, there are
still open connections. I'm not sure if this is so, but I see that the
bandwidth used goes up enormously:

https://ibin.co/3MZa4LbsQ9uh.jpg

Note: I have blotted my public IP. This is a screenshot made with iftop
in the virtual machine with Jitsi Meet and Jigasi where there is an
outgoing traffic of something more than 13 Mbps.

Traffic taken from Cacti:

https://ibin.co/3MZaKtYgRH27.jpg

Interestingly, when I close the conference from the web, the traffic
returns to normal.

Please tell me if I can provide any more information. But this time I
think I have not seen NPE in the Jigasi logs.

Thanks.

Kind regards,
Daniel

···

On 11/05/17 10:51, Damian Minkov wrote:


#5

Hi Daniel,

Are you still hitting the one-way audio?
Can you test with latest jigasi (build 141) and add the following
property to your config:
org.jitsi.jigasi.xmpp.acc.VIDEO_CALLING_DISABLED=true

Thanks
damencho

···

On Thu, May 11, 2017 at 8:51 AM, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

In the first log I see:

2017-05-08 09:52:42.089 INFO: [18027]
org.jitsi.jigasi.JvbConference.memberPresenceChanged().714 Member
presence change: ChatRoomMemberPresenceChangeEvent[type=MemberLeft
sourceRoom=net.java.sip.communicator.impl.protocol.jabber.ChatRoomJabberImpl@2644c15a
member=net.java.sip.communicator.impl.protocol.jabber.ChatRoomMemberJabberImpl@6bf20f56]
2017-05-08 09:52:42.089 INFO: [18027]
org.jitsi.jigasi.JvbConference.memberPresenceChanged().733 Member left
: OWNER focus
2017-05-08 09:52:42.089 INFO: [18027]
org.jitsi.jigasi.JvbConference.memberPresenceChanged().740 Focus

It is not normal the focus to leave the conference, in such cases the
UI automatically show a notification and start a reload countdown and
so is jigasi, stops the call.

You should check why is this happening by checking jicofo logs.

The second NPE I have seen it in other logs you sent and I'm not sure
why it happens, I suspect the early media SIP 183 and some race
condition ... but I'm not sure for that.
Can you check the pcap file (/var/log/jitsi/jigasi/log/) whether SIP
183 has SDP in its body?

Regards
damencho

On Thu, May 11, 2017 at 8:16 AM, Daniel Bareiro <daniel-listas@gmx.net> wrote:

On 08/05/17 12:39, Daniel Bareiro wrote:

Hi, Damian/Jitsi team.

Hi again.

I was doing some tests with outgoing calls. There are times where the
call is made and the participants can interact with each other, but
sometimes the call is taken but there is no audio, and at other times
the call is taken and after a few seconds it is hung.

I have seen in the logs some messages with NullPointerException which
perhaps could be related to this. I attached them.

Please let me know.

If you can comment on this, I would appreciate it.

Thanks in advance.

Kind regards,
Daniel

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#6

And one more update, use jigasi 142, a new fix had been pushed which
we think solves the issue.

···

On Mon, May 22, 2017 at 5:49 PM, Damian Minkov <damencho@jitsi.org> wrote:

Hi Daniel,

Are you still hitting the one-way audio?
Can you test with latest jigasi (build 141) and add the following
property to your config:
org.jitsi.jigasi.xmpp.acc.VIDEO_CALLING_DISABLED=true

Thanks
damencho

On Thu, May 11, 2017 at 8:51 AM, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

In the first log I see:

2017-05-08 09:52:42.089 INFO: [18027]
org.jitsi.jigasi.JvbConference.memberPresenceChanged().714 Member
presence change: ChatRoomMemberPresenceChangeEvent[type=MemberLeft
sourceRoom=net.java.sip.communicator.impl.protocol.jabber.ChatRoomJabberImpl@2644c15a
member=net.java.sip.communicator.impl.protocol.jabber.ChatRoomMemberJabberImpl@6bf20f56]
2017-05-08 09:52:42.089 INFO: [18027]
org.jitsi.jigasi.JvbConference.memberPresenceChanged().733 Member left
: OWNER focus
2017-05-08 09:52:42.089 INFO: [18027]
org.jitsi.jigasi.JvbConference.memberPresenceChanged().740 Focus

It is not normal the focus to leave the conference, in such cases the
UI automatically show a notification and start a reload countdown and
so is jigasi, stops the call.

You should check why is this happening by checking jicofo logs.

The second NPE I have seen it in other logs you sent and I'm not sure
why it happens, I suspect the early media SIP 183 and some race
condition ... but I'm not sure for that.
Can you check the pcap file (/var/log/jitsi/jigasi/log/) whether SIP
183 has SDP in its body?

Regards
damencho

On Thu, May 11, 2017 at 8:16 AM, Daniel Bareiro <daniel-listas@gmx.net> wrote:

On 08/05/17 12:39, Daniel Bareiro wrote:

Hi, Damian/Jitsi team.

Hi again.

I was doing some tests with outgoing calls. There are times where the
call is made and the participants can interact with each other, but
sometimes the call is taken but there is no audio, and at other times
the call is taken and after a few seconds it is hung.

I have seen in the logs some messages with NullPointerException which
perhaps could be related to this. I attached them.

Please let me know.

If you can comment on this, I would appreciate it.

Thanks in advance.

Kind regards,
Daniel

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#7

Hey Daniel,

Can you set:
org.jitsi.jigasi.xmpp.acc.VIDEO_CALLING_DISABLED=true
and update jigasi to 142 and try again, I think the situation should
be greatly improved.

Regards
damencho

···

On Mon, May 15, 2017 at 12:17 PM, Daniel Bareiro <daniel-listas@gmx.net> wrote:

On 11/05/17 10:51, Damian Minkov wrote:

Hi,

Hi, Damian.

In the first log I see:

2017-05-08 09:52:42.089 INFO: [18027]
org.jitsi.jigasi.JvbConference.memberPresenceChanged().714 Member
presence change: ChatRoomMemberPresenceChangeEvent[type=MemberLeft
sourceRoom=net.java.sip.communicator.impl.protocol.jabber.ChatRoomJabberImpl@2644c15a
member=net.java.sip.communicator.impl.protocol.jabber.ChatRoomMemberJabberImpl@6bf20f56]
2017-05-08 09:52:42.089 INFO: [18027]
org.jitsi.jigasi.JvbConference.memberPresenceChanged().733 Member left
: OWNER focus
2017-05-08 09:52:42.089 INFO: [18027]
org.jitsi.jigasi.JvbConference.memberPresenceChanged().740 Focus

It is not normal the focus to leave the conference, in such cases the
UI automatically show a notification and start a reload countdown and
so is jigasi, stops the call.

You should check why is this happening by checking jicofo logs.

The second NPE I have seen it in other logs you sent and I'm not sure
why it happens, I suspect the early media SIP 183 and some race
condition ... but I'm not sure for that.
Can you check the pcap file (/var/log/jitsi/jigasi/log/) whether SIP
183 has SDP in its body?

Thanks for your reply.

I've been doing some more testing with outgoing calls and I've
encountered another issue. That's why I'm generating this sub thread.

For some reason, it seems that when I make a call and hang up, there are
still open connections. I'm not sure if this is so, but I see that the
bandwidth used goes up enormously:

https://ibin.co/3MZa4LbsQ9uh.jpg

Note: I have blotted my public IP. This is a screenshot made with iftop
in the virtual machine with Jitsi Meet and Jigasi where there is an
outgoing traffic of something more than 13 Mbps.

Traffic taken from Cacti:

https://ibin.co/3MZaKtYgRH27.jpg

Interestingly, when I close the conference from the web, the traffic
returns to normal.

Please tell me if I can provide any more information. But this time I
think I have not seen NPE in the Jigasi logs.

Thanks.

Kind regards,
Daniel

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#8

Damencho,

This change will not send hole punch from Jigasi to JVB and SIP peer, right?

Thanks,

/Kaiduan

···

On Tue, May 23, 2017 at 4:16 PM, Damian Minkov <damencho@jitsi.org> wrote:

And one more update, use jigasi 142, a new fix had been pushed which
we think solves the issue.

On Mon, May 22, 2017 at 5:49 PM, Damian Minkov <damencho@jitsi.org> wrote:
> Hi Daniel,
>
> Are you still hitting the one-way audio?
> Can you test with latest jigasi (build 141) and add the following
> property to your config:
> org.jitsi.jigasi.xmpp.acc.VIDEO_CALLING_DISABLED=true
>
> Thanks
> damencho
>
>
> On Thu, May 11, 2017 at 8:51 AM, Damian Minkov <damencho@jitsi.org> > wrote:
>> Hi,
>>
>> In the first log I see:
>>
>> 2017-05-08 09:52:42.089 INFO: [18027]
>> org.jitsi.jigasi.JvbConference.memberPresenceChanged().714 Member
>> presence change: ChatRoomMemberPresenceChangeEvent[type=MemberLeft
>> sourceRoom=net.java.sip.communicator.impl.protocol.
jabber.ChatRoomJabberImpl@2644c15a
>> member=net.java.sip.communicator.impl.protocol.jabber.
ChatRoomMemberJabberImpl@6bf20f56]
>> 2017-05-08 09:52:42.089 INFO: [18027]
>> org.jitsi.jigasi.JvbConference.memberPresenceChanged().733 Member left
>> : OWNER focus
>> 2017-05-08 09:52:42.089 INFO: [18027]
>> org.jitsi.jigasi.JvbConference.memberPresenceChanged().740 Focus
>>
>> It is not normal the focus to leave the conference, in such cases the
>> UI automatically show a notification and start a reload countdown and
>> so is jigasi, stops the call.
>>
>> You should check why is this happening by checking jicofo logs.
>>
>> The second NPE I have seen it in other logs you sent and I'm not sure
>> why it happens, I suspect the early media SIP 183 and some race
>> condition ... but I'm not sure for that.
>> Can you check the pcap file (/var/log/jitsi/jigasi/log/) whether SIP
>> 183 has SDP in its body?
>>
>> Regards
>> damencho
>>
>>
>>
>> On Thu, May 11, 2017 at 8:16 AM, Daniel Bareiro <daniel-listas@gmx.net> > wrote:
>>>
>>> On 08/05/17 12:39, Daniel Bareiro wrote:
>>>
>>>> Hi, Damian/Jitsi team.
>>>
>>> Hi again.
>>>
>>>> I was doing some tests with outgoing calls. There are times where the
>>>> call is made and the participants can interact with each other, but
>>>> sometimes the call is taken but there is no audio, and at other times
>>>> the call is taken and after a few seconds it is hung.
>>>>
>>>> I have seen in the logs some messages with NullPointerException which
>>>> perhaps could be related to this. I attached them.
>>>>
>>>> Please let me know.
>>>
>>> If you can comment on this, I would appreciate it.
>>>
>>>
>>> Thanks in advance.
>>>
>>> Kind regards,
>>> Daniel
>>>
>>>
>>> _______________________________________________
>>> dev mailing list
>>> dev@jitsi.org
>>> Unsubscribe instructions and other list options:
>>> http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
Founder of Goodstartsoft
https://www.goodstartsoft.com


#9

Nope, this change just disables the hole punch to the videobridge.
Hole punch packets to the sip side will be sent, as the sip side may
be latching.

···

On Tue, May 23, 2017 at 3:39 PM, Kaiduan Xie <kaiduanx@gmail.com> wrote:

Damencho,

This change will not send hole punch from Jigasi to JVB and SIP peer, right?

Thanks,

/Kaiduan

On Tue, May 23, 2017 at 4:16 PM, Damian Minkov <damencho@jitsi.org> wrote:

And one more update, use jigasi 142, a new fix had been pushed which
we think solves the issue.

On Mon, May 22, 2017 at 5:49 PM, Damian Minkov <damencho@jitsi.org> wrote:
> Hi Daniel,
>
> Are you still hitting the one-way audio?
> Can you test with latest jigasi (build 141) and add the following
> property to your config:
> org.jitsi.jigasi.xmpp.acc.VIDEO_CALLING_DISABLED=true
>
> Thanks
> damencho
>
>
> On Thu, May 11, 2017 at 8:51 AM, Damian Minkov <damencho@jitsi.org> >> > wrote:
>> Hi,
>>
>> In the first log I see:
>>
>> 2017-05-08 09:52:42.089 INFO: [18027]
>> org.jitsi.jigasi.JvbConference.memberPresenceChanged().714 Member
>> presence change: ChatRoomMemberPresenceChangeEvent[type=MemberLeft
>>
>> sourceRoom=net.java.sip.communicator.impl.protocol.jabber.ChatRoomJabberImpl@2644c15a
>>
>> member=net.java.sip.communicator.impl.protocol.jabber.ChatRoomMemberJabberImpl@6bf20f56]
>> 2017-05-08 09:52:42.089 INFO: [18027]
>> org.jitsi.jigasi.JvbConference.memberPresenceChanged().733 Member left
>> : OWNER focus
>> 2017-05-08 09:52:42.089 INFO: [18027]
>> org.jitsi.jigasi.JvbConference.memberPresenceChanged().740 Focus
>>
>> It is not normal the focus to leave the conference, in such cases the
>> UI automatically show a notification and start a reload countdown and
>> so is jigasi, stops the call.
>>
>> You should check why is this happening by checking jicofo logs.
>>
>> The second NPE I have seen it in other logs you sent and I'm not sure
>> why it happens, I suspect the early media SIP 183 and some race
>> condition ... but I'm not sure for that.
>> Can you check the pcap file (/var/log/jitsi/jigasi/log/) whether SIP
>> 183 has SDP in its body?
>>
>> Regards
>> damencho
>>
>>
>>
>> On Thu, May 11, 2017 at 8:16 AM, Daniel Bareiro <daniel-listas@gmx.net> >> >> wrote:
>>>
>>> On 08/05/17 12:39, Daniel Bareiro wrote:
>>>
>>>> Hi, Damian/Jitsi team.
>>>
>>> Hi again.
>>>
>>>> I was doing some tests with outgoing calls. There are times where the
>>>> call is made and the participants can interact with each other, but
>>>> sometimes the call is taken but there is no audio, and at other times
>>>> the call is taken and after a few seconds it is hung.
>>>>
>>>> I have seen in the logs some messages with NullPointerException which
>>>> perhaps could be related to this. I attached them.
>>>>
>>>> Please let me know.
>>>
>>> If you can comment on this, I would appreciate it.
>>>
>>>
>>> Thanks in advance.
>>>
>>> Kind regards,
>>> Daniel
>>>
>>>
>>> _______________________________________________
>>> dev mailing list
>>> dev@jitsi.org
>>> Unsubscribe instructions and other list options:
>>> http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
Founder of Goodstartsoft
https://www.goodstartsoft.com

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev