Destination Not Found and Port Mapping Does Not Match

[corradojeff]

Hi, I am a new user and I am having trouble making outbound calls. My dialer client displays "Destination not found". When I run the firewall checker get the below-pasted results (All ports say done except the 9 listed below). For the sake of testing, I have the firewalls disabled and all recommended ports forwarded (443, 5000, 5001, 5060, 5061, 5080, 5090, 9000-10999).

If there is any more information I can provide, please let me know. Thank you in advance for any help you can provide.

• resolving 'stun-us.3cx.com'... done
• resolving 'stun2.3cx.com'... done
• resolving 'stun3.3cx.com'... done
• resolving 'sip-alg-detector.3cx.com'... done
• testing 3CX SIP Server... done
  • stopping service... done
  • detecting SIP ALG... not detected
  • testing port 5060... done
  • starting service... done
• testing 3CX Tunneling Proxy... done
  • stopping service... done
  • testing port 5090... done
  • starting service... done
• testing 3CX Media Server... failed (How to resolve?)
  • stopping service... done
  • testing ports [9000..9398]... failed (How to resolve?)
    • testing port 9000... done
    • .......................................
    • testing port 9034... done
    • The rest of the ports say "done" except the following.....
    • testing port 9036... Mapping does not match 9036. Mapping is 9006.
    • testing port 9118... Mapping does not match 9118. Mapping is 9116.
    • testing port 9358... Mapping does not match 9358. Mapping is 9362.
    • testing port 10678... Mapping does not match 10678. Mapping is 10680.
    • testing port 10732... Mapping does not match 10732. Mapping is 10734.
    • testing port 10780... Mapping does not match 10780. Mapping is 10778.
    • testing port 10786... Mapping does not match 10786. Mapping is 10784.
      testing port 10816... Mapping does not match 10816. Mapping is 10814.
    • testing port 10818... Mapping does not match 10818. Mapping is 10820.
    • 
      

 

[Saqqara]

What firewall are you using.

Have you click on ‘how to resolve’ to see if this points you in the right direction to resolve

Have you setup outbound rules https://www.3cx.com/docs/manual/sip-trunks/#h.3evqdta9sabf

 

[eddv123]

I would deal with this as 2 separate issues. Most firewalls will allow outbound traffic as standard so the fact that your firewall checker fails may have no bearing on the outbound call issue. so:

* Check you have an outbound rule in place which is sufficient for your provider and region you are in:
https://www.3cx.com/blog/voip-howto/outbound-rules-a-complete-example/ You can check the logging to see why your call is failing also.

* Your firewall checker (as stated above) will tell you how to resolve this issue, it looks to me like you need to change your NAT mappings - FYI 3CX requires a Full Cone NAT setup.

 

[corradojeff]

Thank you both for your responses. I really appreciate the help.

I did not have an outbound rule set up. I set up a basic outbound rule that is for default extensions and Route 1 to my SIP provider.

After I did this I was able to call out using the 3CX dialer client without getting the error "Destination not Found". I can call my SIP provider's Echo Test using the number 4443 and that works great but when I dial an actual external number it just rings and rings without the call connecting.

It is worth noting that set up a DID number to test receiving calls and I can receive calls from external numbers perfectly.

I do still get the "Mapping does not match" message for the same 9 ports as listed above when running the firewall checker. I have been through the "how to resolve" links a few times but I still have not been able to get it sorted out.

Would this mapping failure be why I can receive calls but not connect on an outbound dial?

I have disabled my windows firewall and made sure that all my port forwarding is correct but I am connected via Google WiFi and I don't see too many advanced options like firewall settings or NAT mappings.

Would it be an issue with my NAT mapping or Full Cone NAT if my Stun.3cx.com tests are resolving?

Thanks again for your help!

Jeff

 

[corradojeff]

An interesting addition:

I added a second extension and set up 3CX client on my Android. It sends and received calls on Wifi but not cellular. It appears that the outbound call issue is just with the 3CX dialer client on my windows computer (also my PBX/System Manager/Host)

 

[JohnS_3CX]

Hi @corradojeff and welcome to the community

The reason the firewall check fails is most likely because your firewall is automatically remapping the ports which can cause communication issues (think no audio) since these are the ports we use to transport the voice.

Depending on your model of firewall you will need to ensure you have full cone NAT to avoid these issues and pass the firewall test before spending time troubleshooting anything else, eliminating one thing at a time and avoiding compounding issues.

Once that's done, you can focus on the next part which is making successful calls via your provider. A good read below will explain why this is important:

https://www.3cx.com/docs/firewall-checker/