You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After update to the latest licode from develop, (including commit Refactor websocket reconnections to ack messages (#1619)) I started to see strange messages in signaling process:
...
431[]
432[]
....
Here is a screen-shot of all signaling:
Is it done in purpose or bug?
The text was updated successfully, but these errors were encountered:
Thanks for quick answer.
I see ACK messages - it is OK.
But I meant messages "431[]", "432[]", ...
Are they also a part of ACK messages ? Should clients react on them somehow or just ignore?
After update to the latest licode from develop, (including commit Refactor websocket reconnections to ack messages (#1619)) I started to see strange messages in signaling process:
...
431[]
432[]
....
Here is a screen-shot of all signaling:
Is it done in purpose or bug?
The text was updated successfully, but these errors were encountered: