Cannot get STUN to work... works on other devices

(1/3) > >>

AndyJ:
I can't get STUN to work on the OBi110. When I enable STUN, I get the 40 second timeout before the call is connected. If I run a STUN client from other devices on the same LAN, using the same STUN server, it works fine:

stunc stun.xten.com:3478 -b
assign_socket: local socket is bound to 0.0.0.0:44395
stunc_bind_cb: stun_discovery_done
stunc_bind_cb: local address NATed as xxx.xxx.xxx.xxx:44395

I've tried various STUN servers, and the result is the same - they all fail on the OBi110, but work fine on other devices. The NAT is a Port Restricted Cone NAT:

stunc stun.xten.com:3478 -n
assign_socket: local socket is bound to 0.0.0.0:58819
stunc_nattype_cb: stun_discovery_done
stunc_nattype_cb: NAT type determined to be 'Port Restricted Cone NAT (endpoint independent mapping)' (6).

RonR:
There is a known problem in the OBi that's never been fixed where the timeout on a non-existent STUN server is 40 seconds.

I'm not having any problems using stun.ideasip.com

I avoid xten's STUN server as it's frequently problematic.

AndyJ:
This works fine for other devices on the same LAN, so I don't know why it's not working on the OBi110, regardless of the server used. Every server that I've tried works on other clients, but fails on the OBi110. Perhaps it has something to do with the type of NAT.

RonR:
If you've got a couple you'd like me to test here, I'd be happy to do so.

AndyJ:
I tried the stun.ideasip.com server that you suggested - same issue... works on my PC (almost instant response), but fails on the OBi110. I also just tried stun.ekiga.net, with similar results. It looks like the OBi110 is having trouble dealing with my NAT.

Navigation

[0] Message Index

[#] Next page