3cx google cloud not connecting with SIP server.

[Terry PC Solution]

Hi guys, not sure what's happening here, I'm on myrepublic internet and I wanted to add myrepublic sip line to my 3cx server.

I was able to add SIP line sip.myrepublic.com.au to my on premise 3cx and that's able to register however my myrepublic modem (sagemcom "wifi halo") was having all sort of issues with passing firewall tests (Builtin SIP ALG that cannot be turned off, as well as builtin 5060 occupied by wifi halo)

I now have just signed up 3cx free 3months google cloud service which will have compatible firewall services, however when i'm adding sip.myrepublic.com.au, comes up with the following error which unable to register.

11/17/2018 6:17:24 PM - [CM504005]: Registration failed for: Lc:10000(@MyRepublic Limited[<sip:[email protected]:5060>]); Cause: Cause: 403 Domain not served here/REGISTER from 45.248.196.11:5060

If anyone is able to provide some info on why it doesn't work on the cloud that would be great.

I've already tested using terminal in cloud 3cx and it's able to ping.

 

[cobaltit]

So it looks like you are getting a response from myrepublic so you are probably better off asking them why it's not working. If their SIP service is designed to run over their internet they may not allow connections from Google Cloud.

 

[Terry PC Solution]

it's strange, because I also tried to install the 3cx pbx on a separate windows 10 machine after reading that 3cx best not to be installed under core server with DNS role etc, and then the windows 10 in my local network was not able to connect to SIP server.

the error msg i'm getting is:
11/18/2018 4:40:46 PM - [CM504005]: Registration failed for: Lc:10000(@MyRepublic Limited[<sip:[email protected]:5060>]); Cause: Cause: 408 Request Timeout/REGISTER from local

ID: 12293
Registration at MyRepublic Limited has failed. Destination (sip:[email protected]:5060) is not reachable, DNS error resolving FQDN, or service is not available.

 

[YiannisH_3CX]

Hello @Terry PC Solution

Make sure that you can resolve "sip.myrepublic.com.au" from the 3CX machine and try again. Since myrepublic only seems to have one A record you can also try connecting using their IP (45.248.196.11) as registrar to see if this is actually a DNS error.

 

[Terry PC Solution]

this is what I get from the terminal nslookup, i'm not sure if there's any problem with DNS resolve. It looks okay to me :S

nslookup sip.myrepublic.com.au
Server: 169.254.169.254
Address: 169.254.169.254#53
Non-authoritative answer:
Name: sip.myrepublic.com.au
Address: 45.248.196.11

 

[Terry PC Solution]

I'm not too sure what non-authoritative answer means...

 

[StefanW]

the answer you've received is essentially a cached or forwarded response from your local DNS server. Basically, a non-authoritative name server is one that does not contain the records for the zone being queried; your local DNS is likely not going to have Google's name records, for example.

https://serverfault.com/questions/4...s-the-meaning-of-the-non-authoritative-answer

 

[Terry PC Solution]

Hi Stefan, the above NS lookup was from my google cloud 3cx host. it's not my local dns server.

Would that be the google cloud's local dns server's cached response?