STUN Problem in Local LAN

[sebastian.rojas]

Hello

i have a problem with some extension, because when a try to call them, i have no answer and after 32 Seg
the call is dropped, but in th 3cx logs it says that is still active and viewing the logs it triggers to the STUN servers
and the host are located in the LAN segment and the 3CX server it is also in the LAN but in another VLAN

Because i believe that i do not need a STUN server to communicate in the LAN... or it's also need it?

-Firewall Checker it was unsuccessful because i have a Sonicwall 2400 that doesn't support the static port forwarding
so i can not use this feature until i get the new firewalls

-It's just in some users happens this problem, with users with DHCP configured and MAC binding :O

LOGS:

; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
31-may-2016 12:54:32.212 [CM504001]: Endpoint Extn:9413: new contact is registered. Contact(s): [sip:[email protected]:5062 / 9413,sip:[email protected]:62143 / 9413,sip:[email protected]:5488 / 9413]
31-may-2016 12:54:31.707 [CM503007]: Call(C:1): Extn:9419 has joined, contact <sip:[email protected]:58239>
31-may-2016 12:54:31.705 [CM503007]: Call(C:1): Extn:9428 has joined, contact <sip:[email protected]:5062>
31-may-2016 12:54:31.702 L:1.2[Extn] has joined to L:1.1[Extn]
31-may-2016 12:54:31.702 NAT/ALG check:L:1.2[Extn] RESPONSE 200 on 'INVITE' - basic check passed. No information for extended checks
31-may-2016 12:54:31.649 [MS205001] C:1.2 RTCP: Party address changed from 0.0.0.0:0 to 130.0.10.81:42009
31-may-2016 12:54:29.132 [CM504001]: Endpoint Extn:9403: new contact is registered. Contact(s): [sip:[email protected]:5488 / 9403,sip:[email protected]:61843 / 9403]
31-may-2016 12:54:28.865 [CM504001]: Endpoint Extn:1001: new contact is registered. Contact(s): [sip:[email protected]:51493 / 1001]
31-may-2016 12:54:26.608 [CM503025]: Call(C:1): Calling T:Extn:9419@[Dev:sip:[email protected]:58239;rinstance=0-6f4dedbc8d2749acbb757b2f7f4975b1;ob] for L:1.1[Extn]
31-may-2016 12:54:26.606 [MS101003] C:1.2: Possible firewall problem. Address mapping failed on STUN server 198.50.247.220:3478 for local address ":9000"
31-may-2016 12:54:26.606 [MS201000] Use STUN server 'stun.3cx.com:3478'
31-may-2016 12:54:26.605 [MS101005] STUN request failed for ports 9000,9001 on STUN server 'stun3.3cx.com:3478'
31-may-2016 12:54:26.464 [MS201000] Use STUN server 'stun3.3cx.com:3478'
31-may-2016 12:54:26.430 [MS101005] STUN request failed for ports 9000,9001 on STUN server 'stun2.3cx.com:3478'
31-may-2016 12:54:26.214 [MS201000] Use STUN server 'stun2.3cx.com:3478'
31-may-2016 12:54:26.195 [MS101005] STUN request failed for ports 9000,9001 on STUN server 'stun.3cx.com:3478'
31-may-2016 12:54:26.028 [CM503027]: Call(C:1): From: Extn:9428 ("Sebastian Rojas" <sip:[email protected]:5060>) to T:Extn:9419@[Dev:sip:[email protected]:58239;rinstance=0-6f4dedbc8d2749acbb757b2f7f4975b1;ob]
31-may-2016 12:54:26.028 [CM503004]: Call(C:1): Route 1: from L:1.1[Extn] to T:Extn:9419@[Dev:sip:[email protected]:58239;rinstance=0-6f4dedbc8d2749acbb757b2f7f4975b1;ob]
31-may-2016 12:54:25.984 [CM503001]: Call(C:1): Incoming call from Extn:9428 to <sip:[email protected]:5060>
31-may-2016 12:54:25.984 NAT/ALG check:L:1.1[Extn] REQUEST 'INVITE' - basic check passed. No information for extended checks


Thanks for your time
Best Regards

 

[lneblett]

The issue appears to likely be related to you using 130.xxx.xxx.xxx. this is not a valid local subnet and as a result 3cx understands it to be public; hence the reason stun is attempted.

 

[sebastian.rojas]

Hi,

yes in some way you are right, but when i call to a extension in the LAN with the same range of ip address 130.x.x.x
it doesn't trigger the STUN server:

this is the log from a call between the ip address.

31-may-2016 15:44:00.899 Leg L:14.1[Extn] is terminated: Cause: BYE from PBX
31-may-2016 15:44:00.899 [CM503008]: Call(C:14): Call is terminated
31-may-2016 15:44:00.885 Leg L:14.3[Extn] is terminated: Cause: BYE from 130.0.20.177:5062
31-may-2016 15:43:53.919 [CM503007]: Call(C:14): Extn:9413 has joined, contact <sip:[email protected]:5062>
31-may-2016 15:43:53.917 [CM503007]: Call(C:14): Extn:9428 has joined, contact <sip:[email protected]:5062>
31-may-2016 15:43:53.915 L:14.3[Extn] has joined to L:14.1[Extn]
31-may-2016 15:43:53.915 NAT/ALG check:L:14.3[Extn] RESPONSE 200 on 'INVITE' - basic check passed. No information for extended checks
31-may-2016 15:43:51.809 Leg L:14.2[Extn] is terminated: Cause: 480 Temporarily Unavailable/INVITE from 127.0.0.1:5488
31-may-2016 15:43:51.807 Call to T:Extn:9413@[Dev:sip:[email protected]:5488;rinstance=3b7522293098a858,Dev:sip:[email protected]:5062] from L:14.1[Extn] failed, cause: Cause: 480 Temporarily Unavailable/INVITE from 127.0.0.1:5488
31-may-2016 15:43:51.807 [CM503003]: Call(C:14): Call to <sip:[email protected]:5060> has failed; Cause: 480 Temporarily Unavailable/INVITE from 127.0.0.1:5488
31-may-2016 15:43:51.484 Leg L:14.4[Extn] is terminated: Cause: 404 Not Found/INVITE from 130.0.10.69:62143
31-may-2016 15:43:51.484 Call to T:Extn:9413@[Dev:sip:[email protected]:5488;rinstance=3b7522293098a858,Dev:sip:[email protected]:5062,Dev:sip:[email protected]:62143;rinstance=0-81f6559315f549c2902e4df32ea88139;ob] from L:14.1[Extn] failed, cause: Cause: 404 Not Found/INVITE from 130.0.10.69:62143
31-may-2016 15:43:51.484 [CM503003]: Call(C:14): Call to <sip:[email protected]:5060> has failed; Cause: 404 Not Found/INVITE from 130.0.10.69:62143
31-may-2016 15:43:51.308 [CM503025]: Call(C:14): Calling T:Extn:9413@[Dev:sip:[email protected]:5488;rinstance=3b7522293098a858,Dev:sip:[email protected]:5062,Dev:sip:[email protected]:62143;rinstance=0-81f6559315f549c2902e4df32ea88139;ob] for L:14.1[Extn]
31-may-2016 15:43:51.060 [CM503025]: Call(C:14): Calling T:Extn:9413@[Dev:sip:[email protected]:5488;rinstance=3b7522293098a858,Dev:sip:[email protected]:5062,Dev:sip:[email protected]:62143;rinstance=0-81f6559315f549c2902e4df32ea88139;ob] for L:14.1[Extn]
31-may-2016 15:43:51.058 [CM503025]: Call(C:14): Calling T:Extn:9413@[Dev:sip:[email protected]:5488;rinstance=3b7522293098a858,Dev:sip:[email protected]:5062,Dev:sip:[email protected]:62143;rinstance=0-81f6559315f549c2902e4df32ea88139;ob] for L:14.1[Extn]
31-may-2016 15:43:51.005 [CM503027]: Call(C:14): From: Extn:9428 ("Sebastian Rojas" <sip:[email protected]:5060>) to T:Extn:9413@[Dev:sip:[email protected]:5488;rinstance=3b7522293098a858,Dev:sip:[email protected]:5062,Dev:sip:[email protected]:62143;rinstance=0-81f6559315f549c2902e4df32ea88139;ob]
31-may-2016 15:43:51.005 [CM503004]: Call(C:14): Route 1: from L:14.1[Extn] to T:Extn:9413@[Dev:sip:[email protected]:5488;rinstance=3b7522293098a858,Dev:sip:[email protected]:5062,Dev:sip:[email protected]:62143;rinstance=0-81f6559315f549c2902e4df32ea88139;ob]
31-may-2016 15:43:51.002 [CM503001]: Call(C:14): Incoming call from Extn:9428 to <sip:[email protected]:5060>




Best Regards

 

[lneblett]

STUN is not needed within the LAN, if the LAN is using what is accepted as private subnets. STUN is used to help traverse firewalls which,of course, is not a concern for the LAN. However, as 3CX does not understand your subnet to be an accepted private LAN subnet it may invoke STUN which as you point out..... it fails.

You can either change your subnet or you MIGHT be able to add the subnet into the existing subnet parameter section of 3CX. I have not tried this so am uncertain that it will work, but conceivably by adding the subnet the system may then consider it to be a local LAN and thereby avoid trying to use STUN altogher.

How is acts under your current scenario is something that I cannot answer.