Re-booted and now STUN fails

[touficjohn]

Hi,

A little while ago I restarted my 3cx box. For the last 2-3months its been working fine - and I haven't needed to restart the machine for 9months.

Tried to make an inbound call and realised nothing was coming through, logged into 3cx and under line status neither voiptalk or sipgate were registered.

Logs revealed the following:

00:57:27.984 ExtLine::Register [CM010002] Line DN='10001' device='Sipgate' can not be registered. External IP isn't resolved.
00:57:27.984 ExtLine::Register [CM110001] Use External IP for device line registration DN='10001' device='Sipgate'
00:57:27.984 ExtLine::Register [CM010002] Line DN='10000' device='VoipTalk' can not be registered. External IP isn't resolved.
00:57:27.984 ExtLine::Register [CM110001] Use External IP for device line registration DN='10000' device='VoipTalk'
00:57:27.890 CallMgr::failResolveExtIp [CM200001] Failed to resolve external IP!
00:57:27.890 StunClient:rocess [CM215001] STUN failed to resolve external IP using server 64.69.76.23
00:57:24.859 StunClient:rocess [CM215001] STUN failed to resolve external IP using server 64.69.76.23
00:57:21.843 StunClient:rocess [CM115001] Send initial STUN request to 64.69.76.23
00:57:21.750 StunClient:rocess [CM215001] STUN failed to resolve external IP using server 64.69.76.23
00:57:18.734 StunClient:rocess [CM215001] STUN failed to resolve external IP using server 64.69.76.23
00:57:15.703 StunClient:rocess [CM115001] Send initial STUN request to 64.69.76.23
00:57:15.609 StunClient:rocess [CM215001] STUN failed to resolve external IP using server 64.69.76.23
00:57:12.593 StunClient:rocess [CM215001] STUN failed to resolve external IP using server 64.69.76.23
00:57:09.578 StunClient:rocess [CM115001] Send initial STUN request to 64.69.76.23
00:57:09.468 StunClient:rocess [CM215001] STUN failed to resolve external IP using server 64.69.76.23
00:57:07.234 ListenConnect [CM114000] SL: connected server:0/VoiceBoxManagerService at [server]/VoiceBoxManagerService
00:57:06.453 StunClient:rocess [CM215001] STUN failed to resolve external IP using server 64.69.76.23
00:57:05.031 ListenConnect [CM114000] SL: connected server:0/PHPExtension_0 at [server]/PHPExtension_0
00:57:04.828 IVRConnected [CM111000] IVR Server is connected
00:57:04.828 ListenConnect [CM114000] SL: connected server:5483/IVRServer at [server]/IVRServer
00:57:03.437 StunClient:rocess [CM115001] Send initial STUN request to 64.69.76.23
00:57:03.328 CallMgr::Stack::thread [CM106001] ** Enter Stack Loop **
00:57:03.046 MediaServerConnected [CM112000] Media Server is connected
00:57:03.046 ListenConnect [CM114000] SL: connected server:0/MediaServer at [server]/MediaServer
00:57:02.718 CallMgr:umThread::thread [CM100004] ** Enter DUM Thread **
00:57:02.671 DBA [CM109000] ** Database connection Ok **
00:57:02.625 CallMgr::Stack::Initialize [CM106000] ** Adding transports **
00:57:02.625 CallMgr::Initialize [CM100003] ** Initializing SIP stack **
00:57:02.625 CallMgr::Initialize [CM100002] Default Local IP address: 192.168.0.1:5060
00:57:02.625 CallMgr::Initialize [CM100001] Version: 3.1.2434.0
00:57:02.625 CallMgr::Initialize [CM100000] Start 3CX PhoneSystem Call Manager
00:57:02.609 LoadLicenceInfo [CM100008] Licence loading error


I have never seen that License error before.
Furthermore, nothing on the box, network, or firewalls have changed.
There is virtually no traffic on the network.
I cannot for the life of me figure out why all of a sudden this could have stopped working?

I am also aware that there is another person on these forums with a similar problem.

Any help is appreciated!

 

[webguyz]

We downloaded and installed the freeware WINSTUN stun server and installed it on our 3CX server (using SRVANY). We did not want to have to depend on someone elses stun server being up. Don't think the 3.1 stun is flakey as we've never had a problem running our own stun server.

 

[touficjohn]

Hmmm
I'll re-install 3cx from scratch and see if that helps.
Problem is you never know how these things go, after re-install who knows maybe internal calls will stop altogether...
Computers are still too fragile...