Possible problem with stun.3cx.com ?

[Cjay]

failed to resolve external IP using server 194.221.62.209

This IP is still stun.3cx.com - what happens if you change to stunserver.org? By the way you can also specify a stun server in Manage Lines / VoIP Provider / Show Advanced Options - not sure which takes priority - this or the value set in General / General Settings.

 

[dyntech]

Yes, I have tried several other stun server: stunserver.org, stun.xten.org, etc. I also have made the changes in both locations each time hoping the system would not get confused.

Each time I got the same results as using stun.3cx.com.

 

[Cjay]

Not sure what is going on here. If it were mine I would be inclined to do a packet capture with Ethereal to see exactly which stun server / IP is being used by 3cx and whether it is responding correctly.

 

[3CXsupport]

Yes, spot on

We are working on introducing a list of STUN servers as opposed to a single entry for failover.

 

[silentfun]

Perfect choice - This is the difference from some usual developers to a dreamteam - they analyze and act fast - 100 points from germany for the 3CX Dreamteam !

i think stun in "Edit VOIP Provider" have priority - is that right ?

 

[3CXsupport]

Many Thanks for the positive feedback ! It's great to hear such encouraging comments

That is correct, VoIP providers have a higher 'priority' than the general config. If that field is left empty the server assumes the 'General' STUN server.

 

[Anonymous]

For those still having problems with the STUN, try this server stun.fwdnet.net

It appears reasonable reliable.

Actually what i found with the stun missing was that a lot of other bits and pieces went funny.

I cold not even receive calls via my DID anymore and lost some sound channels. Weird.

 

[silentfun]

yes i have had a UK DID that was green on the old install and when the stun issues beginn i installed the system on a other server where it is always red but still working - i don

 

[ipSkillz]

Stun Server component seems fried...

I have removed the default stun.3cx.org as it was failing, I have edited and added two working stun servers but to no avail.

All walls are down and the router is forwarding nicely..

I'm losing time here, are there any more suggestions available?

Here is my log, thanks in advance for any updates on the matter.

20:45:54.881 ExtLine::Register [CM010002] Line DN='10000' device='BusinessLine' can not be registered. External IP isn't resolved.
20:45:54.881 ExtLine::Register [CM110001] Use External IP for device line registration DN='10000' device='BusinessLine'
20:45:54.291 CallMgr::failResolveExtIp [CM200001] Failed to resolve external IP!
20:45:54.291 StunClient:rocess [CM215001] STUN failed to resolve external IP using server 192.245.12.229
20:45:51.276 StunClient:rocess [CM215001] STUN failed to resolve external IP using server 69.90.168.14
20:45:48.272 StunClient:rocess [CM115001] Send initial STUN request to 69.90.168.14
20:45:48.172 StunClient:rocess [CM215001] STUN failed to resolve external IP using server 192.245.12.229
20:45:45.168 StunClient:rocess [CM215001] STUN failed to resolve external IP using server 69.90.168.14
20:45:42.163 StunClient:rocess [CM115001] Send initial STUN request to 69.90.168.14
20:45:42.063 StunClient:rocess [CM215001] STUN failed to resolve external IP using server 192.245.12.229
20:45:39.059 StunClient:rocess [CM215001] STUN failed to resolve external IP using server 69.90.168.14
20:45:36.054 StunClient:rocess [CM115001] Send initial STUN request to 69.90.168.14
20:45:35.954 StunClient:rocess [CM215001] STUN failed to resolve external IP using server 192.245.12.229
20:45:32.950 StunClient:rocess [CM215001] STUN failed to resolve external IP using server 69.90.168.14
20:45:29.946 StunClient:rocess [CM115001] Send initial STUN request to 69.90.168.14
20:45:29.845 CallMgr::Stack::thread [CM106001] ** Enter Stack Loop **
20:45:28.303 CallMgr:umThread::thread [CM100004] ** Enter DUM Thread **
20:45:27.973 DBA [CM109000] ** Database connection Ok **
20:45:27.853 CallMgr::Stack::Initialize [CM106000] ** Adding transports **
20:45:27.833 CallMgr::Initialize [CM100003] ** Initializing SIP stack **

 

[SY]

In log: Response from both servers didn't arrive during 3 sec. You can try to setup longer timeout, but there is small probability that STUN server wasn't able to make response in 3 sec.

check connection to servers with ping and tracert.

Anyway, both STUN server are working at least at the time when I'm writing this post.

192.245.12.229 - 19 hops ping stable ~280ms
69.90.168.14 - 9 hops ping stable ~200ms

both servers respond to 3CX PBX

Regards,
Stepan

P.S. I check it from Cyprus

 

[ipSkillz]

Thanks for the reply.

I've raised the timeout to 30 secs, but stun still fails. I can trace and ping the ip of stun.fwdnet.net fine.

Ive used winstun and the communication checks out.

Pinging stun.fwdnet.net [69.90.168.13] with 32 bytes of da

Reply from 69.90.168.13: bytes=32 time=253ms TTL=48
Reply from 69.90.168.13: bytes=32 time=254ms TTL=48
Reply from 69.90.168.13: bytes=32 time=252ms TTL=48
Reply from 69.90.168.13: bytes=32 time=255ms TTL=48
Reply from 69.90.168.13: bytes=32 time=254ms TTL=48
Reply from 69.90.168.13: bytes=32 time=252ms TTL=48
Reply from 69.90.168.13: bytes=32 time=255ms TTL=48
Reply from 69.90.168.13: bytes=32 time=253ms TTL=48
Reply from 69.90.168.13: bytes=32 time=254ms TTL=48
Reply from 69.90.168.13: bytes=32 time=254ms TTL=48
Reply from 69.90.168.13: bytes=32 time=252ms TTL=48
Reply from 69.90.168.13: bytes=32 time=255ms TTL=48
Reply from 69.90.168.13: bytes=32 time=254ms TTL=48
Reply from 69.90.168.13: bytes=32 time=252ms TTL=48
Reply from 69.90.168.13: bytes=32 time=255ms TTL=48
Reply from 69.90.168.13: bytes=32 time=252ms TTL=48
Reply from 69.90.168.13: bytes=32 time=252ms TTL=48
Reply from 69.90.168.13: bytes=32 time=254ms TTL=48
Reply from 69.90.168.13: bytes=32 time=253ms TTL=48

Ping statistics for 69.90.168.13:
Packets: Sent = 19, Received = 19, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 252ms, Maximum = 255ms, Average = 253ms
Control-C


Tracing route to stun.fwdnet.net [69.90.168.13]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.138
2 15 ms 13 ms 14 ms 202.173.144.37
3 14 ms 15 ms 14 ms 202.173.144.97
4 15 ms 47 ms 30 ms 59.154.17.17
5 181 ms 188 ms 180 ms 203.208.148.17
6 181 ms 181 ms 181 ms 208.172.44.137
7 180 ms 261 ms 180 ms 204.70.193.105
8 213 ms 212 ms 213 ms 204.70.192.137
9 254 ms 235 ms 252 ms 204.70.192.69
10 252 ms 266 ms 252 ms 204.70.197.1
11 254 ms 257 ms 245 ms 204.70.192.54
12 254 ms 253 ms 252 ms 204.70.192.10
13 255 ms 250 ms 255 ms 204.70.150.254
14 * 265 ms * 204.70.192.205
15 251 ms 253 ms * 204.70.193.97
16 253 ms 256 ms 258 ms 69.90.168.13

Trace complete.

Can anyone think of anything that might help?

Getting a little edgy lol...

Update: All stun requests are failing.

Iv'e run 3cx before quite well, that's why I chose to come back to it, however all stun requests are failing, I've even reverted the revision of the software down to 3cxsystem3.exe so it appears there could be a more detailed issue here, perhaps regarding the internet connection, although very strange.. as I can trace, ping and receive stun requests outside of this program.

I hope this issue can be touched on a bit more for all the people who have received this issue of late.

Kind regards.

 

[ipSkillz]

Forwarding 5082 seemed to do the trick for me.

 

[DaKhalli]

if you still have problems, you might want to try to add the stun adresses to your windows host file (so it skips dns lookup on those names)

the file can be located in: %systemroot%/system32/drivers/etc/ and is called "hosts" (no extension) edit it with notepad and you will see something like this:

127.0.0.1 localhost


and maybe more underneath,

first put in the ip (you get from pinging the host) and then tab and then put in the hostname.

Hope you dont need this info and it works already, but when it doesnt i hope its usefull somehow.

 

[Anonymous]

Just for get the stun.3cx.com one, and put another public stun server as your stun server.

the 3cx is been down for a while (well not up for longer than a few minutes that is) so try to use one within your country or within your ISP network. Makes things a lot smoother and faster.

No reason too only use stun.3cx.com it is not a fixed thing.