Quote:
Originally Posted by Juste
Problem solved.
It turned out that stun.xten.com no longer works properly.
I replaced it with stun.voxalot.com:3478 and that fixed the issue.
Thanks everybody for helping.
|
Funny, I thought I suggested something to that effect but you dismissed it from consideration.
Take note people, weird global effects of suddenly not being able to call out or receive calls are most frequently related to NAT traversal problems, which for most of us are quite closely tied up with the STUN server we are using, rather than 'problems' with the providers itself.