- 20 Sep, 2008 1 commit
-
-
Youness Alaoui authored
-
- 18 Sep, 2008 8 commits
-
-
Youness Alaoui authored
-
Youness Alaoui authored
Add support sending the correct channelbind/set-active-candidate/options when we want to get a lock on a peer
-
Youness Alaoui authored
-
Youness Alaoui authored
-
Youness Alaoui authored
-
Youness Alaoui authored
-
Youness Alaoui authored
-
Youness Alaoui authored
-
- 17 Sep, 2008 6 commits
-
-
Youness Alaoui authored
-
Youness Alaoui authored
A google/msn data indication is 0x0115 which is contrary to the rfc3489bis which states that 8th and 12th bits are for the class and that 0x01 is for indications... So 0x0115 is reported as a "connect error response", while it should be a data indication, which message type should actually be 0x0017 This should fix the issue, and it's considered safe since the "connect" method doesn't exist anymore
-
Youness Alaoui authored
-
Youness Alaoui authored
We should not free the username/password used for authenticating until the candidate discovery is also freed, otherwise we can't authenticate the response
-
Youness Alaoui authored
-
Youness Alaoui authored
-
- 16 Sep, 2008 10 commits
-
-
Youness Alaoui authored
-
Youness Alaoui authored
Receiving a message from the turn server should set the udp_socket to the relayed one so answers can be wrapped too
-
Youness Alaoui authored
-
Youness Alaoui authored
-
Youness Alaoui authored
-
Youness Alaoui authored
-
Youness Alaoui authored
Correctly check for errors when processing TURN response and support long term credentials unauthorized message correctly
-
Youness Alaoui authored
-
Youness Alaoui authored
-
Youness Alaoui authored
-
- 15 Sep, 2008 2 commits
-
-
Youness Alaoui authored
-
Youness Alaoui authored
-
- 12 Sep, 2008 2 commits
-
-
Youness Alaoui authored
Correctly check for the username/password. Only check the start for our own username and do not check for the semicolon. Also makes the code cleaner and fixes possible compat issue with msn for peer reflexive candidates
-
Youness Alaoui authored
When we unfreeze a conncheck, we must make sure the timer will keep running. The conncheck gets unfrozen from state FROZEN to WAITING. If there are no other IN_PROGRESS connchecks, then the timer will stop and the WAITING conncheck will never go into IN_PROGRESS state. This can cause a lock because the state of the stream will be never be READY/FAILED as there will be one conncheck in WAITING state remaining
-
- 11 Sep, 2008 3 commits
-
-
Youness Alaoui authored
Fix checking for the remote candidate using the username, and correctly create the remote peer reflexive candidate
-
Youness Alaoui authored
Fix verification of username/password, as specified in the RFC. This should fix problems with delayed SDP responses
-
Youness Alaoui authored
-
- 10 Sep, 2008 8 commits
-
-
Youness Alaoui authored
-
Youness Alaoui authored
-
Youness Alaoui authored
-
Youness Alaoui authored
-
Youness Alaoui authored
-
Youness Alaoui authored
-
Youness Alaoui authored
-
Youness Alaoui authored
-