STUN support problem
OZOi:
RonR, I think you're right. I've tried stun01.sipphone.com and it produced the same results as you've reported (40 sec delay and LAN IP after that). At this time I guess we have a problem with that particular STUN server.
I've checked my OBi again with followed two servers and both are working well now:
stun.ideasip.com
stun.counterpath.com
They have exhibited 40 sec problems with v.1.2.1 though...
Try one of the servers mentioned above and let us know your experience.
RonR:
This particular problem is with a STUN server that's not responding. The OBi has a timeout of 40 seconds, which is utterly ridiculous. A PAP2, for example, times out in approximately 1 second if the STUN server doesn't respond.
stun01.sipphone.com was the Gizmo5 STUN server and worked fine until it was taken down when Gizmo5 shut down. When I finally figured out the huge delays I was experiencing was due to stun01.sipphone.com being down, I switched to stun.ideasip.com and have been using it since.
OZOi:
I agree. The right solution in a situation, when STUN server is not responding, is not to delay receiving/making call for 40 sec, but rather to send error to SIP server as soon as the problem is recognized. Trying to continue call with sending LAN IP after 40 sec delay is plain futile. There will be no audio anyway.
Navigation
[0] Message Index
[*] Previous page