- Joined
- Jul 10, 2015
- Messages
- 22
- Reaction score
- 2
I've just completed a fresh install of 16.0.619 (Pro Annual) on Windows 10 Pro, v2004, completely up-to-date.
I believe the firewall and port forwarding is configured correctly; the firewall check completes successfully.
This is the full error I receive when attempting to register:
I've spoken with the SIP provider, their service is online and we ran a test using PhonerLite. There doesn't seem to be any issue at their end.
When I ping the FQDN externally, it gives the correct IP address (which I've confirmed is still correct), however there are no actual pings. "Request timed out" x 4.
I took the semi-functional 3CX installation offline about 24hrs ago, formatted the Windows PC and reinstalled about 10hrs ago (not a restore from backup). Could this have caused propagation issues at the 3CX end, perhaps?
If it helps, the SIP provider is Internode (AU), who are not a certified provider but were 3CX-friendly before certification was a thing. End users don't want to switch
Internode had been working mostly OK until this reinstall. Just the odd dual-registration after Internet interruptions or blackouts.
All suggestions welcome!
I believe the firewall and port forwarding is configured correctly; the firewall check completes successfully.
This is the full error I receive when attempting to register:
Registration at [SIP Provider] has failed. Destination (sip:XXX.XXX.XXX.XXX:5060;transport=TCP;lr) is not reachable, DNS error resolving FQDN, or service is not available.
I've spoken with the SIP provider, their service is online and we ran a test using PhonerLite. There doesn't seem to be any issue at their end.
When I ping the FQDN externally, it gives the correct IP address (which I've confirmed is still correct), however there are no actual pings. "Request timed out" x 4.
I took the semi-functional 3CX installation offline about 24hrs ago, formatted the Windows PC and reinstalled about 10hrs ago (not a restore from backup). Could this have caused propagation issues at the 3CX end, perhaps?
If it helps, the SIP provider is Internode (AU), who are not a certified provider but were 3CX-friendly before certification was a thing. End users don't want to switch
Internode had been working mostly OK until this reinstall. Just the odd dual-registration after Internet interruptions or blackouts.
All suggestions welcome!
Last edited: