set gathering to FALSE before signaling the candidate-gathering-done, so we can set_remote_candidates in the signal handler

do not send an error response in case the username check failed for gtalk compatibility. we should just drop it like libjingle does.. if the remote candidates weren't added yet, then we'd send the error response which would make the other client match the id, but also fail with integrity check (since the error response has no username in it), and all retransmissions will fail with unmatched_response.

Use the correct size for sockaddr_storage, otherwise it won't work on mac os x. Also use some cleaner code

remove the traffic_after_tick check because it caused problems with jingle. we need a tick every 25 seconds, but with that, the conncheck happens at 0s, and when the keepalive gets called @25s, it gets skipped and we only send our first keepalive after 50seconds... which means that jingle which stops processing if it doesn't receive a ping after 30 seconds, will stop playing our audio from 30 seconds to 50 seconds...

use a different port for the relay to make sure we don't confuse the google relay server between an internal and external connection

race condition where the whole thing finishes up before g_main_loop_run(error_loop) gets called, so it gets stuck.. so we need to delay all threads by a little...

use a dedicated stun agent for stun binding discovery because we'll need to be compatible with rfc 3489

a peer reflexive candidate must store the username and password from its parent candidate when in google mode

do not reset a connectivity check to 'in progress' when we get a triggered check on it and we're already done