[jitsi-dev] Anyone using Microsoft Edge 40 with any Jitsi products?


#1

I'm having issues with ice4j and Edge and I wonder if anyone else is using
it successfully with the latest WebRTC 1.0 compliant Edge release (Edge 40
with edgeHTML 15)? The symptom is that all my connections for ICE timeout
and theres very little info to go on..

Apr 22, 2017 1:00:52 PM org.ice4j.util.Logger log
INFO: timeout for pair: 192.168.86.110:49152/udp/host ->
192.168.86.110:58390/udp/host (media-0.RTP), failing.

All my testing is on my local network with the firewalls disabled.

Paul


#2

Are you using this is a project of yours or with Jitsi Meet? Edge's WebRTC
1.0 support is not fully compliant (no multi-stream support, for one) so we
are working on a ORTC shim. So far ICE connects successfully and we should
have RTP flowing soon, but AFAIK no issues were observed on the ICE side so
far.

Cheers,

···

On Sat, Apr 22, 2017 at 10:06 PM, Mondain <mondain@gmail.com> wrote:

I'm having issues with ice4j and Edge and I wonder if anyone else is using
it successfully with the latest WebRTC 1.0 compliant Edge release (Edge 40
with edgeHTML 15)? The symptom is that all my connections for ICE timeout
and theres very little info to go on..

Apr 22, 2017 1:00:52 PM org.ice4j.util.Logger log
INFO: timeout for pair: 192.168.86.110:49152/udp/host ->
192.168.86.110:58390/udp/host (media-0.RTP), failing.

All my testing is on my local network with the firewalls disabled.

Paul

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

--
Saúl


#3

Its a custom project using Ice4j for the connectivity layer which works
with all browsers less Edge. I got this result this morning and its marked
"suspicious"? I suppose I'll dig into the ice checks in the library.

May 17, 2017 7:45:14 AM org.ice4j.util.Logger log
INFO: CheckList will failed in a few seconds if nosucceeded checks come
May 17, 2017 7:45:19 AM org.ice4j.util.Logger log
INFO: CheckList for stream media-0 FAILED
May 17, 2017 7:45:19 AM org.ice4j.util.Logger log
*INFO: Suspicious ICE connectivity failure. Checks failed but the remote
end was able to reach us.*
May 17, 2017 7:45:19 AM org.ice4j.util.Logger log
INFO: ICE state is FAILED
May 17, 2017 7:45:19 AM org.ice4j.util.Logger log
INFO: ICE state changed from Running to Failed. Local ufrag 92rkt1bgbdt6b4

···

On Wed, May 3, 2017 at 3:09 AM Saúl Ibarra Corretgé <scorretge@atlassian.com> wrote:

Are you using this is a project of yours or with Jitsi Meet? Edge's WebRTC
1.0 support is not fully compliant (no multi-stream support, for one) so we
are working on a ORTC shim. So far ICE connects successfully and we should
have RTP flowing soon, but AFAIK no issues were observed on the ICE side so
far.

Cheers,

On Sat, Apr 22, 2017 at 10:06 PM, Mondain <mondain@gmail.com> wrote:

I'm having issues with ice4j and Edge and I wonder if anyone else is
using it successfully with the latest WebRTC 1.0 compliant Edge release
(Edge 40 with edgeHTML 15)? The symptom is that all my connections for ICE
timeout and theres very little info to go on..

Apr 22, 2017 1:00:52 PM org.ice4j.util.Logger log
INFO: timeout for pair: 192.168.86.110:49152/udp/host ->
192.168.86.110:58390/udp/host (media-0.RTP), failing.

All my testing is on my local network with the firewalls disabled.

Paul

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

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


#4

How is this related to Jitsi at all?

···

El 17/5/2017 17:00, "Mondain" <mondain@gmail.com> escribió:

Its a custom project using Ice4j for the connectivity layer which works
with all browsers less Edge. I got this result this morning and its marked
"suspicious"? I suppose I'll dig into the ice checks in the library.

May 17, 2017 7:45:14 AM org.ice4j.util.Logger log
INFO: CheckList will failed in a few seconds if nosucceeded checks come
May 17, 2017 7:45:19 AM org.ice4j.util.Logger log
INFO: CheckList for stream media-0 FAILED
May 17, 2017 7:45:19 AM org.ice4j.util.Logger log
*INFO: Suspicious ICE connectivity failure. Checks failed but the remote
end was able to reach us.*
May 17, 2017 7:45:19 AM org.ice4j.util.Logger log
INFO: ICE state is FAILED
May 17, 2017 7:45:19 AM org.ice4j.util.Logger log
INFO: ICE state changed from Running to Failed. Local ufrag 92rkt1bgbdt6b4

On Wed, May 3, 2017 at 3:09 AM Saúl Ibarra Corretgé < > scorretge@atlassian.com> wrote:

Are you using this is a project of yours or with Jitsi Meet? Edge's
WebRTC 1.0 support is not fully compliant (no multi-stream support, for
one) so we are working on a ORTC shim. So far ICE connects successfully and
we should have RTP flowing soon, but AFAIK no issues were observed on the
ICE side so far.

Cheers,

On Sat, Apr 22, 2017 at 10:06 PM, Mondain <mondain@gmail.com> wrote:

I'm having issues with ice4j and Edge and I wonder if anyone else is
using it successfully with the latest WebRTC 1.0 compliant Edge release
(Edge 40 with edgeHTML 15)? The symptom is that all my connections for ICE
timeout and theres very little info to go on..

Apr 22, 2017 1:00:52 PM org.ice4j.util.Logger log
INFO: timeout for pair: 192.168.86.110:49152/udp/host ->
192.168.86.110:58390/udp/host (media-0.RTP), failing.

All my testing is on my local network with the firewalls disabled.

Paul

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

--
Saúl
_______________________________________________
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


#5

Jitsi maintains ice4j and has experience with Edge.

···

On Wed, May 17, 2017 at 8:52 AM Iñaki Baz Castillo <ibc@aliax.net> wrote:

How is this related to Jitsi at all?

El 17/5/2017 17:00, "Mondain" <mondain@gmail.com> escribió:

Its a custom project using Ice4j for the connectivity layer which works
with all browsers less Edge. I got this result this morning and its marked
"suspicious"? I suppose I'll dig into the ice checks in the library.

May 17, 2017 7:45:14 AM org.ice4j.util.Logger log
INFO: CheckList will failed in a few seconds if nosucceeded checks come
May 17, 2017 7:45:19 AM org.ice4j.util.Logger log
INFO: CheckList for stream media-0 FAILED
May 17, 2017 7:45:19 AM org.ice4j.util.Logger log
*INFO: Suspicious ICE connectivity failure. Checks failed but the remote
end was able to reach us.*
May 17, 2017 7:45:19 AM org.ice4j.util.Logger log
INFO: ICE state is FAILED
May 17, 2017 7:45:19 AM org.ice4j.util.Logger log
INFO: ICE state changed from Running to Failed. Local ufrag 92rkt1bgbdt6b4

On Wed, May 3, 2017 at 3:09 AM Saúl Ibarra Corretgé < >> scorretge@atlassian.com> wrote:

Are you using this is a project of yours or with Jitsi Meet? Edge's
WebRTC 1.0 support is not fully compliant (no multi-stream support, for
one) so we are working on a ORTC shim. So far ICE connects successfully and
we should have RTP flowing soon, but AFAIK no issues were observed on the
ICE side so far.

Cheers,

On Sat, Apr 22, 2017 at 10:06 PM, Mondain <mondain@gmail.com> wrote:

I'm having issues with ice4j and Edge and I wonder if anyone else is
using it successfully with the latest WebRTC 1.0 compliant Edge release
(Edge 40 with edgeHTML 15)? The symptom is that all my connections for ICE
timeout and theres very little info to go on..

Apr 22, 2017 1:00:52 PM org.ice4j.util.Logger log
INFO: timeout for pair: 192.168.86.110:49152/udp/host ->
192.168.86.110:58390/udp/host (media-0.RTP), failing.

All my testing is on my local network with the firewalls disabled.

Paul

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

--
Saúl
_______________________________________________
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

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


#6

Can you get some ICE traces with Wireshark? I'm doing the RTCPeerConnection
shim for Edge in lib-jitsi-meet and sometimes ICE doesn't connect. I
suspect it's due to ICE role conflicts but won't be able to make traces
until next week.

···

El 17/5/2017 17:55, "Mondain" <mondain@gmail.com> escribió:

Jitsi maintains ice4j and has experience with Edge.

On Wed, May 17, 2017 at 8:52 AM Iñaki Baz Castillo <ibc@aliax.net> wrote:

How is this related to Jitsi at all?

El 17/5/2017 17:00, "Mondain" <mondain@gmail.com> escribió:

Its a custom project using Ice4j for the connectivity layer which works
with all browsers less Edge. I got this result this morning and its marked
"suspicious"? I suppose I'll dig into the ice checks in the library.

May 17, 2017 7:45:14 AM org.ice4j.util.Logger log
INFO: CheckList will failed in a few seconds if nosucceeded checks come
May 17, 2017 7:45:19 AM org.ice4j.util.Logger log
INFO: CheckList for stream media-0 FAILED
May 17, 2017 7:45:19 AM org.ice4j.util.Logger log
*INFO: Suspicious ICE connectivity failure. Checks failed but the remote
end was able to reach us.*
May 17, 2017 7:45:19 AM org.ice4j.util.Logger log
INFO: ICE state is FAILED
May 17, 2017 7:45:19 AM org.ice4j.util.Logger log
INFO: ICE state changed from Running to Failed. Local ufrag
92rkt1bgbdt6b4

On Wed, May 3, 2017 at 3:09 AM Saúl Ibarra Corretgé < >>> scorretge@atlassian.com> wrote:

Are you using this is a project of yours or with Jitsi Meet? Edge's
WebRTC 1.0 support is not fully compliant (no multi-stream support, for
one) so we are working on a ORTC shim. So far ICE connects successfully and
we should have RTP flowing soon, but AFAIK no issues were observed on the
ICE side so far.

Cheers,

On Sat, Apr 22, 2017 at 10:06 PM, Mondain <mondain@gmail.com> wrote:

I'm having issues with ice4j and Edge and I wonder if anyone else is
using it successfully with the latest WebRTC 1.0 compliant Edge release
(Edge 40 with edgeHTML 15)? The symptom is that all my connections for ICE
timeout and theres very little info to go on..

Apr 22, 2017 1:00:52 PM org.ice4j.util.Logger log
INFO: timeout for pair: 192.168.86.110:49152/udp/host ->
192.168.86.110:58390/udp/host (media-0.RTP), failing.

All my testing is on my local network with the firewalls disabled.

Paul

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

--
Saúl
_______________________________________________
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

_______________________________________________
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


#7

Yes, I should be able to collect some traces this week and I'll share them.

···

On Wed, May 17, 2017 at 9:11 AM Iñaki Baz Castillo <ibc@aliax.net> wrote:

Can you get some ICE traces with Wireshark? I'm doing the
RTCPeerConnection shim for Edge in lib-jitsi-meet and sometimes ICE doesn't
connect. I suspect it's due to ICE role conflicts but won't be able to make
traces until next week.

El 17/5/2017 17:55, "Mondain" <mondain@gmail.com> escribió:

Jitsi maintains ice4j and has experience with Edge.

On Wed, May 17, 2017 at 8:52 AM Iñaki Baz Castillo <ibc@aliax.net> wrote:

How is this related to Jitsi at all?

El 17/5/2017 17:00, "Mondain" <mondain@gmail.com> escribió:

Its a custom project using Ice4j for the connectivity layer which works
with all browsers less Edge. I got this result this morning and its marked
"suspicious"? I suppose I'll dig into the ice checks in the library.

May 17, 2017 7:45:14 AM org.ice4j.util.Logger log
INFO: CheckList will failed in a few seconds if nosucceeded checks come
May 17, 2017 7:45:19 AM org.ice4j.util.Logger log
INFO: CheckList for stream media-0 FAILED
May 17, 2017 7:45:19 AM org.ice4j.util.Logger log
*INFO: Suspicious ICE connectivity failure. Checks failed but the
remote end was able to reach us.*
May 17, 2017 7:45:19 AM org.ice4j.util.Logger log
INFO: ICE state is FAILED
May 17, 2017 7:45:19 AM org.ice4j.util.Logger log
INFO: ICE state changed from Running to Failed. Local ufrag
92rkt1bgbdt6b4

On Wed, May 3, 2017 at 3:09 AM Saúl Ibarra Corretgé < >>>> scorretge@atlassian.com> wrote:

Are you using this is a project of yours or with Jitsi Meet? Edge's
WebRTC 1.0 support is not fully compliant (no multi-stream support, for
one) so we are working on a ORTC shim. So far ICE connects successfully and
we should have RTP flowing soon, but AFAIK no issues were observed on the
ICE side so far.

Cheers,

On Sat, Apr 22, 2017 at 10:06 PM, Mondain <mondain@gmail.com> wrote:

I'm having issues with ice4j and Edge and I wonder if anyone else is
using it successfully with the latest WebRTC 1.0 compliant Edge release
(Edge 40 with edgeHTML 15)? The symptom is that all my connections for ICE
timeout and theres very little info to go on..

Apr 22, 2017 1:00:52 PM org.ice4j.util.Logger log
INFO: timeout for pair: 192.168.86.110:49152/udp/host ->
192.168.86.110:58390/udp/host (media-0.RTP), failing.

All my testing is on my local network with the firewalls disabled.

Paul

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

--
Saúl
_______________________________________________
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

_______________________________________________
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

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


#8

Great. Please check if you see any 487 (Role Conflict) STUN response
from Edge or from ice4j.

···

2017-05-17 18:33 GMT+02:00 Mondain <mondain@gmail.com>:

Yes, I should be able to collect some traces this week and I'll share them.

--
Iñaki Baz Castillo
<ibc@aliax.net>


#9

In my wireshark dump i see ICMP errors and this shows on my console:

May 31, 2017 12:42:06 PM org.ice4j.util.Logger log
INFO: Failed to send BINDING-RESPONSE(0x101)[attrib.count=3 len=60] through
192.168.0.171:49152/udp
org.ice4j.StunException: The transaction specified in the response
(tid=0xA08BDC2252AB1ACA6C631D7F) has already seen a previous response.
Response was:
BINDING-ERROR-RESPONSE(0x111)[attrib.count=4 len=68
tranID=0xA08BDC2252AB1ACA6C631D7F]
        at org.ice4j.stack.StunStack.sendResponse(StunStack.java:767)
        at
org.ice4j.ice.ConnectivityCheckServer.processRequest(ConnectivityCheckServer.java:214)
        at
org.ice4j.stack.EventDispatcher$RequestListenerMessageEventHandler.handleMessageEvent(EventDispatcher.java:511)
        at
org.ice4j.stack.EventDispatcher.fireMessageEvent(EventDispatcher.java:268)
        at org.ice4j.stack.StunStack.handleMessageEvent(StunStack.java:987)
        at org.ice4j.stack.MessageProcessor.run(MessageProcessor.java:171)
        at java.lang.Thread.run(Thread.java:745)

May 31, 2017 12:42:06 PM org.ice4j.stack.StunStack handleMessageEvent
INFO: Received an invalid request.
java.lang.RuntimeException: Failed to send a response
        at
org.ice4j.ice.ConnectivityCheckServer.processRequest(ConnectivityCheckServer.java:226)
        at
org.ice4j.stack.EventDispatcher$RequestListenerMessageEventHandler.handleMessageEvent(EventDispatcher.java:511)
        at
org.ice4j.stack.EventDispatcher.fireMessageEvent(EventDispatcher.java:268)
        at org.ice4j.stack.StunStack.handleMessageEvent(StunStack.java:987)
        at org.ice4j.stack.MessageProcessor.run(MessageProcessor.java:171)
        at java.lang.Thread.run(Thread.java:745)
Caused by: org.ice4j.StunException: The transaction specified in the
response (tid=0xA08BDC2252AB1ACA6C631D7F) has already seen a previous
response. Response was:
BINDING-ERROR-RESPONSE(0x111)[attrib.count=4 len=68
tranID=0xA08BDC2252AB1ACA6C631D7F]
        at org.ice4j.stack.StunStack.sendResponse(StunStack.java:767)
        at
org.ice4j.ice.ConnectivityCheckServer.processRequest(ConnectivityCheckServer.java:214)
        ... 5 more

I'm all local / private network based for my test and I'm not sure what to
make of these errors.

···

On Wed, May 17, 2017 at 9:40 AM Iñaki Baz Castillo <ibc@aliax.net> wrote:

2017-05-17 18:33 GMT+02:00 Mondain <mondain@gmail.com>:
> Yes, I should be able to collect some traces this week and I'll share
them.

Great. Please check if you see any 487 (Role Conflict) STUN response
from Edge or from ice4j.

--
Iñaki Baz Castillo
<ibc@aliax.net>

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


#10

Response below:

···

2017-05-31 22:29 GMT+02:00 Mondain <mondain@gmail.com>:

In my wireshark dump i see ICMP errors and this shows on my console:

May 31, 2017 12:42:06 PM org.ice4j.util.Logger log
INFO: Failed to send BINDING-RESPONSE(0x101)[attrib.count=3 len=60] through
192.168.0.171:49152/udp
org.ice4j.StunException: The transaction specified in the response
(tid=0xA08BDC2252AB1ACA6C631D7F) has already seen a previous response.
Response was:
BINDING-ERROR-RESPONSE(0x111)[attrib.count=4 len=68
tranID=0xA08BDC2252AB1ACA6C631D7F]
        at org.ice4j.stack.StunStack.sendResponse(StunStack.java:767)
        at
org.ice4j.ice.ConnectivityCheckServer.processRequest(ConnectivityCheckServer.java:214)
        at
org.ice4j.stack.EventDispatcher$RequestListenerMessageEventHandler.handleMessageEvent(EventDispatcher.java:511)
        at
org.ice4j.stack.EventDispatcher.fireMessageEvent(EventDispatcher.java:268)
        at org.ice4j.stack.StunStack.handleMessageEvent(StunStack.java:987)
        at org.ice4j.stack.MessageProcessor.run(MessageProcessor.java:171)
        at java.lang.Thread.run(Thread.java:745)

May 31, 2017 12:42:06 PM org.ice4j.stack.StunStack handleMessageEvent
INFO: Received an invalid request.
java.lang.RuntimeException: Failed to send a response
        at
org.ice4j.ice.ConnectivityCheckServer.processRequest(ConnectivityCheckServer.java:226)
        at
org.ice4j.stack.EventDispatcher$RequestListenerMessageEventHandler.handleMessageEvent(EventDispatcher.java:511)
        at
org.ice4j.stack.EventDispatcher.fireMessageEvent(EventDispatcher.java:268)
        at org.ice4j.stack.StunStack.handleMessageEvent(StunStack.java:987)
        at org.ice4j.stack.MessageProcessor.run(MessageProcessor.java:171)
        at java.lang.Thread.run(Thread.java:745)
Caused by: org.ice4j.StunException: The transaction specified in the
response (tid=0xA08BDC2252AB1ACA6C631D7F) has already seen a previous
response. Response was:
BINDING-ERROR-RESPONSE(0x111)[attrib.count=4 len=68
tranID=0xA08BDC2252AB1ACA6C631D7F]
        at org.ice4j.stack.StunStack.sendResponse(StunStack.java:767)
        at
org.ice4j.ice.ConnectivityCheckServer.processRequest(ConnectivityCheckServer.java:214)
        ... 5 more

I'm all local / private network based for my test and I'm not sure what to
make of these errors.

I don't think any of the above logs indicate any issue. Probably you
would get the same logs after a successful ICE connection, have you
checked that?

BTW, here my report: https://github.com/jitsi/lib-jitsi-meet/issues/498

--
Iñaki Baz Castillo
<ibc@aliax.net>


#11

I only see this with Edge, but I will verify that on my windows server with
Chrome just to be on the safe side.

···

On Thu, Jun 1, 2017 at 3:48 PM Iñaki Baz Castillo <ibc@aliax.net> wrote:

Response below:

2017-05-31 22:29 GMT+02:00 Mondain <mondain@gmail.com>:
> In my wireshark dump i see ICMP errors and this shows on my console:
>
> May 31, 2017 12:42:06 PM org.ice4j.util.Logger log
> INFO: Failed to send BINDING-RESPONSE(0x101)[attrib.count=3 len=60]
through
> 192.168.0.171:49152/udp
> org.ice4j.StunException: The transaction specified in the response
> (tid=0xA08BDC2252AB1ACA6C631D7F) has already seen a previous response.
> Response was:
> BINDING-ERROR-RESPONSE(0x111)[attrib.count=4 len=68
> tranID=0xA08BDC2252AB1ACA6C631D7F]
> at org.ice4j.stack.StunStack.sendResponse(StunStack.java:767)
> at
>
org.ice4j.ice.ConnectivityCheckServer.processRequest(ConnectivityCheckServer.java:214)
> at
>
org.ice4j.stack.EventDispatcher$RequestListenerMessageEventHandler.handleMessageEvent(EventDispatcher.java:511)
> at
>
org.ice4j.stack.EventDispatcher.fireMessageEvent(EventDispatcher.java:268)
> at
org.ice4j.stack.StunStack.handleMessageEvent(StunStack.java:987)
> at
org.ice4j.stack.MessageProcessor.run(MessageProcessor.java:171)
> at java.lang.Thread.run(Thread.java:745)
>
> May 31, 2017 12:42:06 PM org.ice4j.stack.StunStack handleMessageEvent
> INFO: Received an invalid request.
> java.lang.RuntimeException: Failed to send a response
> at
>
org.ice4j.ice.ConnectivityCheckServer.processRequest(ConnectivityCheckServer.java:226)
> at
>
org.ice4j.stack.EventDispatcher$RequestListenerMessageEventHandler.handleMessageEvent(EventDispatcher.java:511)
> at
>
org.ice4j.stack.EventDispatcher.fireMessageEvent(EventDispatcher.java:268)
> at
org.ice4j.stack.StunStack.handleMessageEvent(StunStack.java:987)
> at
org.ice4j.stack.MessageProcessor.run(MessageProcessor.java:171)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.ice4j.StunException: The transaction specified in the
> response (tid=0xA08BDC2252AB1ACA6C631D7F) has already seen a previous
> response. Response was:
> BINDING-ERROR-RESPONSE(0x111)[attrib.count=4 len=68
> tranID=0xA08BDC2252AB1ACA6C631D7F]
> at org.ice4j.stack.StunStack.sendResponse(StunStack.java:767)
> at
>
org.ice4j.ice.ConnectivityCheckServer.processRequest(ConnectivityCheckServer.java:214)
> ... 5 more
>
> I'm all local / private network based for my test and I'm not sure what
to
> make of these errors.

I don't think any of the above logs indicate any issue. Probably you
would get the same logs after a successful ICE connection, have you
checked that?

BTW, here my report: https://github.com/jitsi/lib-jitsi-meet/issues/498

--
Iñaki Baz Castillo
<ibc@aliax.net>

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