STUN Issues- Still

Status
Not open for further replies.

dyntech

Free User
Joined
Mar 28, 2007
Messages
162
Reaction score
0
Server logs report:
18:15:50.618 CallMgr::failResolveExtIp [CM200001] Failed to resolve external IP!
18:15:50.618 StunClient::process [CM215001] STUN failed to resolve external IP using server 192.245.12.229
18:15:47.555 StunClient::process [CM215001] STUN failed to resolve external IP using server 80.239.235.209
18:15:44.493 StunClient::process [CM115001] Send initial STUN request to 80.239.235.209
18:15:44.383 StunClient::process [CM215001] STUN failed to resolve external IP using server 192.245.12.229
18:15:41.321 StunClient::process [CM215001] STUN failed to resolve external IP using server 80.239.235.209
18:15:38.258 StunClient::process [CM115001] Send initial STUN request to 80.239.235.209
18:15:38.149 StunClient::process [CM215001] STUN failed to resolve external IP using server 192.245.12.229
18:15:35.086 StunClient::process [CM215001] STUN failed to resolve external IP using server 80.239.235.209
18:15:32.024 StunClient::process [CM115001] Send initial STUN request to 80.239.235.209
18:15:31.914 StunClient::process [CM215001] STUN failed to resolve external IP using server 192.245.12.229
18:15:28.852 StunClient::process [CM215001] STUN failed to resolve external IP using server 80.239.235.209
18:15:25.789 StunClient::process [CM115001] Send initial STUN request to 80.239.235.209


Yet WinStun reports:
Nat with Independend Mapping and Port Dependent Filter - VoIP will work with STUN
Does not preserve port number
Does not supports hairpin of media
Public IP address: xxx.xxx.xxx.xxx <---- changed by me.


I have ports 3478-3479 open on the firewall for Stun.
This is currently BETA ver. 3.1 but it has never worked with any version.

Using stun.3cx.com and stunserver.org
 
Have you opened port 5060 for outbound?
 
Please try the trace route for the stun server. To see it can be reach or not from your ISP.

If cannot try the other public stun server:
stun.voipcheap.com
stun.fwdnet.net
 
My ISP unable to reach the stun server of stun.3cx.com. My trace route log as below:

C:\Documents and Settings\cxadmin>tracert stun.3cx.com

Tracing route to stun.voipbuster.com [80.239.235.209]
over a maximum of 30 hops:

1 4 ms 4 ms 2 ms 210.245.148.1
2 8 ms 11 ms 3 ms 203.98.180.245
3 3 ms 3 ms 3 ms g4-0.cr12-1.oxf.nwtgigalink.com [203.98.131.25]

4 5 ms 3 ms 3 ms sr2-0.cr12-2.wpc.nwtgigalink.com [203.98.130.17]

5 8 ms 6 ms 30 ms 203.98.161.81
6 6 ms 8 ms 4 ms 203.98.161.19
7 174 ms 175 ms 177 ms tbr2.la2ca.ip.att.net [12.123.199.114]
8 171 ms 178 ms 171 ms ggr2.la2ca.ip.att.net [12.123.222.45]
9 182 ms 171 ms 182 ms ar2-a300s2.wswdc.ip.att.net [192.205.34.14]
10 249 ms * 236 ms nyk-bb2-link.telia.net [213.248.80.10]
11 308 ms 310 ms * prs-bb1-link.telia.net [80.91.251.99]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
 
5qg4 Try this one:

stun.fwdnet.net

Should work,

Best to do a search in your country for STUN servers, in general you will find a few public ones. No need to be bound to the stun.3cx.com

My philosophy is that you make most calls in your country of origin so might aswell use a stun server in that area, shorter pops and routes means less latency.

and yes the stun.3cx.com times out again it is a rouer issue on cw.net not so much the 3cx.com network it is a gateway before that.
 
Hi itfarmer,

Thanks. In my country stun.3cx.com always time out. I am now using stun.fwdnet.com for PBX and stun.voipcheap.com for remote test. Both are OK in asia.
 
Problem solved. My Sonicwall Intrusion Prevention Service was the culprit in the "Stun not resolving external IP" problem. Turned it off and it works great.
 
Good to hear ! Thanks for following up with the cause of the problem !
 
Status
Not open for further replies.

Forum statistics

Threads
111,913
Messages
589,706
Members
164,783
Latest member
GothamUser