SIP.US Registration

[tglasco]

I am having an issue getting my SIP.US account registered in the PBX. I have done this before with a different account, but now it will not register. The firewall checker is all green and I have talked to SIP.US. All of my settings appear to be correct, but nothing I do will register it on the PBX or on the provider's system.

SIP.US said that they have had numerous calls since the latest pfSense update. That is my firewall. Has anyone else seen this? Any help would be appreciated.

 

[accentlogic]

Are you on v16.5 and using a Windows server? If so there appears to be an issue affecting some of these installs and 3CX is looking into it.

If that is your case you can try changing your Outbound Proxy to use 65.254.44.194 and set the Registrar/Server/Gateway to use port 5060 instead of Auto Discovery.

In case that does not work and you have a static public IP you can have SIP.US change your trunk from User Authentication to IP.

 

[tglasco]

Yes. Latest version on Windows. I have tried what you suggested and it does not work except or changing the auth. Will try that with SIP.US.

 

[tglasco]

Changing the auth method did not work.

 

[BrenttG]

we are running with 16.0.5 behind many pfsense firewalls, and have not seen any issues with pfsense 2.4.5, and are not having any issues, The pfsense 3cx guide was recently updated, can you review it and confirm your system is setup exactly per the guide?
https://www.3cx.com/docs/pfsense-firewall/

Also what 3CX version did you upgrade from?

Also, our trunk provider is siptrunk.com which is the same company..... However all of our PBXs are linux also, none are windows.

 

[AWS2P]

Welcome to the club, join us here
https://www.3cx.com/community/threa...lving-since-updating-to-16-5-yesterday.72721/

 

[daveatgower]

thank you as I was pulling out my hair on this issue. I hope 3CX figures this out quickly as our system has been down all day.

Edit1: changing the DNS entry to IP address corrects the issue for now but not a good setup.

Edit2: Email from Provider after the temp fix. "Signaling via IP address is not a long term solution. You may have issues with inbound calls due to our system relying heavily on DNS NAPTR/SRV."

3CX please fix this soon...