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

<< < (3/3)

OZOi:
I've just tried "stun.xten.com" and it works well with OBi100 v.1.3.0.2532 for me.
There is no delay for both outgoing and incoming calls and OBi used correct WAN IP.

AndyJ:
That's one of the many STUN servers that I've tried. I'll try it on the OBi110, and experience the STUN failure, and then immediately try it on another device on the same LAN, and see success on that device. There's something peculiar to the OBi110 that is causing it to fail in my environment.

Maybe if I have a chance, I'll set up a STUN server on my LAN and point the OBi110 to it. Of course, it will not give correct results, but I could at least trace the traffic to see if there's anything odd in the OBi110's request.

OZOi:
If you'll find a STUN server, which is very lite on resources and running on Windows platform (preferably as service, so it'll be restarted by OS itself) - let me know. I'll install and check it too. I need to see what's going on here too.

I presume the cause of the problem is in different implementations of the STUN protocol spec. Those servers, that do not work with OBi, may "talk slightly different dialect", which is not understood or rejected by OBI... Other devices, that work fine, are perhaps just less fastidious...

To get proper results, you have to run STUN server on a public IP, which is different from IP of SIP server and from OBI device.

AndyJ:
ARGH! After all this time, I've found the problem.

If an outbound proxy is defined in an ITSP profile, then the STUN server DOES NOT WORK if "op=s" is specified in a voice gateway using that profile. I'm guessing that the STUN request is being sent to the outbound proxy instead of directly to the STUN server. The provider I'm using requires registration requests to be sent to the outbound proxy server, so I don't need the STUN server for that. However, I have voice gateways defined with the "op=s" (use STUN) option. If the outbound proxy is enabled, the STUN request times out. If I remove the outbound proxy, then STUN works! (But, in that case, I cannot register with the ITSP anymore, since they require use of the outbound proxy for registration).

I found this by setting up a STUN server on my LAN (stund under Linux). As I mentioned earlier, it obviously wouldn't give the correct results, but would at least help to see what the OBi110 is doing. When I had the OutboundProxy defined, and made a call with VG1 (with op=s), the local STUN server DID NOT receive any request, but I still saw the 40 second delay before the call started, typical of the STUN failure. So, it seems like the OBi110 made a STUN request, but not to the local STUN server. After I removed the OutboundProxy and made the same call with VG1, I saw the OBi110 make the request to the local STUN server and continue with the call.

Navigation

[0] Message Index

[*] Previous page