3cx Firewall Checker - working ok?

[rspb_chriswells]

Anyone else tried a 3cx firewall test today? Can you confirm that the Firewall Checker is working properly?

We are trying to diagnose an failure we are getting with the 3cx firewall checker for a new implementation. We are getting: -

testing 3CX SIP Server... failed
testing port 5060... full cone test failed

We have done traces on our firewall and we can see CLASSIC-STUN requests and CLASSIC-STUN responses for the first test - there the ip and port are not changed.
When testing port 5060 we can then see the CLASSIC-STUN requests go out but never see any responses come back - when the IP address and port are changed in the response.

When it moves onto testing ports 9002 an upwards - we can see both CLASSIC-STUN requests and responses for both the test with no change to ip address and ports and the later test where the ip address and port are changed.

The 5060 test responses are not being blocked or dropped by our firewalll the responses are never reaching our firewall. We can see the requests reaching the firewall and going out successfully.

Not sure what else we can try if the responses never reach us.

 

[complex1]

Just run the firewall checker on my system without issues.

 

[rspb_chriswells]

Thanks.

Are you running v16.0.493 Professional?

 

[complex1]

Yes.

 

[cobaltit]

If you are running the firewall test and it's not hitting your firewall then the issue is upstream, likely the provider equipment.

 

[Alphabetic]

Is it cloud hosted? Probably provider issue as mentioned. I’ve had firewall issues before, couldn’t figure it out! Didn’t make a single change and it was the network my ded server was on.

 

[ECOM GROUP (Mauritius)]

Anyone else tried a 3cx firewall test today? Can you confirm that the Firewall Checker is working properly?

We are trying to diagnose an failure we are getting with the 3cx firewall checker for a new implementation. We are getting: -

testing 3CX SIP Server... failed
testing port 5060... full cone test failed

We have done traces on our firewall and we can see CLASSIC-STUN requests and CLASSIC-STUN responses for the first test - there the ip and port are not changed.
When testing port 5060 we can then see the CLASSIC-STUN requests go out but never see any responses come back - when the IP address and port are changed in the response.

When it moves onto testing ports 9002 an upwards - we can see both CLASSIC-STUN requests and responses for both the test with no change to ip address and ports and the later test where the ip address and port are changed.

The 5060 test responses are not being blocked or dropped by our firewalll the responses are never reaching our firewall. We can see the requests reaching the firewall and going out successfully.

Not sure what else we can try if the responses never reach us.

i confirm i am having same issue, even the softphone is not being registered via fqdn.. but only with local ip it registered.

All of my port keep showing mapping does not match

• testing port 9138... Mapping does not match 9138. Mapping is 1240. (How to resolve?)
• testing port 9140... Mapping does not match 9140. Mapping is 1238. (How to resolve?)
• testing port 9142... Mapping does not match 9142. Mapping is 1242. (How to resolve?)
• testing port 9144... Mapping does not match 9144. Mapping is 1244. (How to resolve?)
• testing port 9146... Mapping does not match 9146. Mapping is 1246. (How to resolve?)
• testing port 9148... Mapping does not match 9148. Mapping is 1248. (How to resolve?)
• testing port 9150... Mapping does not match 9150. Mapping is 1250. (How to resolve?)
• testing port 9152... Mapping does not match 9152. Mapping is 1252. (How to resolve?)
• testing port 9154... Mapping does not match 9154. Mapping is 1256. (How to resolve?)
• testing port 9156... Mapping does not match 9156. Mapping is 1254. (How to resolve?)
• testing port 9158... Mapping does not match 9158. Mapping is 1258. (How to resolve?)
• testing port 9160... Mapping does not match 9160. Mapping is 1260. (How to resolve?)
• testing port 9162... Mapping does not match 9162. Mapping is 1262. (How to resolve?)
• testing port 9164... Mapping does not match 9164. Mapping is 1264. (How to resolve?)
• testing port 9166... Mapping does not match 9166. Mapping is 1266. (How to resolve?)
• testing port 9168... Mapping does not match 9168. Mapping is 1268. (How to resolve?)
• testing port 9170... Mapping does not match 9170. Mapping is 1270. (How to resolve?)
• testing port 9172... Mapping does not match 9172. Mapping is 1272. (How to resolve?)
• testing port 9174... Mapping does not match 9174. Mapping is 1274. (How to resolve?)

let me know if you have been able to find a solution

 

[Clément Rousseau]

@ Ecom Group, unless I do a mistake, shouldn't 3cx refuse port mapping ? then what you see seems normal