Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

3cx Random lightsail rambom disconnections Dns error resolving FQDN -

0

block voip traffic. we get rambon disconnections from our 3cx our ip is 18.153.219.4

and we are trying to comminicate to 66.165.168.107 and we get dns error resolving. we have dns 8.8.8.8

Warning 12293 07/09/2024 6:26 PM SIP Server Registration at Columbia OUTBOUND has failed. Destination (sip:66.165.168.107:9000;lr) is not reachable, DNS error resolving FQDN, or service is not available. Warning 12293 07/09/2024 6:26 PM SIP Server Registration at LarsenNicolasUW has failed. Destination (sip:66.165.168.107;lr) is not reachable, DNS error resolving FQDN, or service is not available. Warning 12293 07/09/2024 6:26 PM SIP Server Registration at Vietam new has failed. Destination (sip:66.165.168.107:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available. Warning 12293 07/09/2024 6:25 PM SIP Server Registration at Taiwan Outbound has failed. Destination (sip:66.165.168.107:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available. Warning 12293 07/09/2024 6:25 PM SIP Server Registration at CHILE OUTBOUND has failed. Destination (sip:66.165.168.107:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available. Warning 12293 07/09/2024 6:25 PM SIP Server Registration at Jose Nieto UK UW has failed. Destination (sip:66.165.168.107;lr) is not reachable, DNS error resolving FQDN, or service is not available. Warning 12293 07/09/2024 6:25 PM SIP Server Registration at Columbia OUTBOUND has failed. Destination (sip:66.165.168.107:9000;lr) is not reachable, DNS error resolving FQDN, or service is not available. Warning 12293 07/09/2024 6:24 PM SIP Server Registration at BRAZIL has failed. Destination (sip:66.165.168.107:5060;lr) is not reachable, DNS error resolving FQDN, or ser

  • Max Clements EXPERT
    2 years ago

    What is the FQDN you are trying to resolve, your errors only have IPs (sip:66.165.168.107:9000;lr) these are not using DNS?

Topics
Compute
Tags
Amazon Lightsail
Language
English
asked 2 years ago577 views
1 Answer
2
  • To resolve the VoIP traffic and DNS errors for your 3CX system, verify DNS settings are correctly configured using reliable DNS servers like Google’s (8.8.8.8) and test DNS resolution for 66.165.168.107 from your 3CX server using nslookup or dig.
  • After that I would inspect network connectivity between your 3CX server and 66.165.168.107 using ping, traceroute, or telnet to ensure no blocks, ensure firewalls are not blocking SIP traffic and disable SIP ALG if enabled.
  • Then review 3CX logs for detailed error messages to identify the cause of the failed registrations, ensure 3CX and network devices are up to date with the latest firmware and software updates, and if issues persist, contact your ISP to check for network blocks or issues affecting VoIP traffic.
EXPERT
answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content