Solved Password reset has reset everything.

[Phil1975]

Hello everybody and thank you in advance for any assistance you can provide.

Very new to 3CX; set up the basics about a month ago and has all been working, 1 yealink phone (below) and 3CX App on 1 x iPad and 2 x Andoids. This is all for my own business and although a live environment, it's primarily for my learning purposes at this point. I haven't had a chance to get back to it, and yesterday morning I put my own modem into bridge mode to install a UNIFI USG.

I noticed later in the day that my phone app was showing 'Warning Invalid Password' and although I can still receive calls, I can't make them. Physical yealink phone displays 'Line Forbidden' when trying to dial number or extension.

I have included logs (and system details) below; but from what I am aware the following has happened.

• Unable to log in
• IP Blocked
• Used phone hotspot to reset password and successfully logged in.
• Deleted blacklisted IP (Not my external IP - perhaps something to do with USG?)
• Left my external IP which shows as always allow
• No phones, sip trunks, dids, rules etc... like the entire portal has been reset to factory settings.
• Restored backup from 05/08/2022 (Today is 05/10/2022 in my time Zone - Time Zone settings are correct in portal and logs)
• Still nothing.

I can't log into Yealink with default user and pass, and from memory this is changed during provisioning.

Any ideas before I start all over again? Which wouldn't be the end of the world and probably some good practice; but then solving the issue would also teach me a few things I'm sure.

LOGS

• Service started
  SIP ServerID: 409705/10/2022 10:18:01 PM
• Trunk L:90000(WebMeeting bridge) has changed status to registered.
  SIP ServerID: 410005/10/2022 10:18:01 PM
• Service got signal to stop: stop service
  SIP ServerID: 409805/10/2022 10:17:58 PM
• Service got signal to stop: 15
  SIP ServerID: 409805/10/2022 10:17:58 PM
• Service started
  SIP ServerID: 409705/10/2022 9:02:46 PM
• Trunk L:90000(WebMeeting bridge) has changed status to registered.
  SIP ServerID: 410005/10/2022 9:02:46 PM
• Service got signal to stop: stop service
  SIP ServerID: 409805/10/2022 9:02:18 PM
• Service got signal to stop: 15
  SIP ServerID: 409805/10/2022 9:02:18 PM
• The IP 1.132.31.142 has been blacklisted for 86400 sec. (Expires at: 2022-05-11 20:59:20). Reason: 3CX Clients / Softphones blocked - 3CX API Component
  3CX Clients / SoftphonesID: 1229005/10/2022 8:59:20 PM
• The IP 1.128.22.109 has been blacklisted for 86400 sec. (Expires at: 2022-05-11 13:33:22). Reason: 3CX Clients / Softphones blocked - 3CX API Component
  3CX Clients / SoftphonesID: 1229005/10/2022 1:33:22 PM
• SIP request (REGISTER) from 89.252.132.22 was rejected. Reason: Block WAN requests is ON. Message: REGISTER sip:3.26.201.126 SIP/2.0 Via: SIP/2.0/UDP 10.124.186.8:51846;branch=z9hG4bK1314591839;received=89.252.132.22 Max-Forwards: 70 Contact: <sip:[email protected]:51846> To: <sip:[email protected]> From: <sip:[email protected]>;tag=621140583 Call-ID: 356357332-2146313917-1365738067 CSeq: 2 REGISTER Proxy-Authorization: Digest username="700",uri="sip:3.26.201.126",algorithm=MD5,realm="3CXPhoneSystem",nonce="414d53596278396768:60942bed267da78713ea619f87fb9f43",response="9457166c23ac073cf705fb32e8e1a414" User-Agent: Asterisk PBX Content-Length: 0
  SIP ServerID: 1229105/09/2022 7:43:04 AM
• SIP request (REGISTER) from 89.252.132.22 was rejected. Reason: Block WAN requests is ON. Message: REGISTER sip:3.26.201.126 SIP/2.0 Via: SIP/2.0/UDP 10.124.186.8:52580;branch=z9hG4bK498025868;received=89.252.132.22 Max-Forwards: 70 Contact: <sip:[email protected]:52580> To: <sip:[email protected]> From: <sip:[email protected]>;tag=1665861381 Call-ID: 1377231837-1104319841-2035566293 CSeq: 2 REGISTER Proxy-Authorization: Digest username="700",uri="sip:3.26.201.126",algorithm=MD5,realm="3CXPhoneSystem",nonce="414d53596277fd8a01:1133839b1f97ed81402dee3fa444eb3c",response="4c604354c7283919c6b73916bae2aae8" User-Agent: Asterisk PBX Content-Length: 0
  SIP ServerID: 1229105/09/2022 3:27:38 AM
• 3CX logs and temporary files were deleted to conserve disk space.
  Event Notification ManagerID: 1002505/09/2022 12:45:18 AM
• Database maintenance task has been finished.
  3CX System ServiceID: 1002705/08/2022 2:00:06 AM
• Service started
  SIP ServerID: 409705/07/2022 12:44:17 PM
• Trunk L:90000(WebMeeting bridge) has changed status to registered.
  SIP ServerID: 410005/07/2022 12:44:17 PM
• Service got signal to stop: stop service
  SIP ServerID: 409805/07/2022 12:43:39 PM
• Service got signal to stop: 15
  SIP ServerID: 409805/07/2022 12:43:39 PM
• 3CX logs and temporary files were deleted to conserve disk space.
  Event Notification ManagerID: 1002505/07/2022 12:51:35 AM
• 3CX logs and temporary files were deleted to conserve disk space.
  Event Notification ManagerID: 1002505/05/2022 12:50:58 AM
• 3CX logs and temporary files were deleted to conserve disk space.

System Details

• 3CX Version, e.g. Standard Annual 16.0.2.910 - (Enterprise Annual V18)
• Server OS, e.g. Debian 9 / Windows Server 2012 R2 / Raspberry Pi - (Debian 9)
• Is the 3CX Server Hosted and where? e.g. On-premises / Hosted in [AWS/Google/Azure/by 3CX] - (Hosted by AWS)
• IP Phone Make/Model/Firmware version, e.g. Yealink T46U version 108.86.0.20 - Yealink W52P - Unsure
• Provisioning Method: Local / VPN / STUN / SBC ? - SBC I'm sure
• Trunk Provider or VoIP Gateway Make/Model, e.g. AT&T SIP-Trunk / Grandstream GXW-4104 - Not sure
• Has the Firewall Checker passed: YES / NO ? - Was all working - Yes, but problems started (IP Was Blocked) when installing a UNIFI USG at my premises.
• Are custom Phone Templates being used: YES / NO ? - No

 

[Alphabetic]

SIP request (REGISTER) from 89.252.132.22 was rejected. Reason: Block WAN requests is ON.

You need to uncheck "allow use outside of LAN" which is used for STUN under ext settings.

rerun the firewall test and make sure you have 100% pass.

sounds like you pressed regenerate which would have reset all passwords for your phone/app etc.

 

[Phil1975]

Thanks for your quick response. I can't find that setting, and to be clear; I don't have any extensions listed. Everything has disappeared. Firewall already has 100% pass. The only other thing I've done is refreshed the license on the recommendation of chat support.

 

[Alphabetic]

Give your instance a reboot, try clearing cache on your browser and try running in private mode.

 

[Phil1975]

Update - I did all this following a YouTube video and have actually created 2 instances in AWS (which I had also never used before this). Apparently my FQDN 'suddenly' started pointing towards the other instance... or AWS suddenly swapped them. Upon discovering the other instance I was able to open it's public IP and log in using my original credentials.

Everything seems to be there except my phones... and I'm now going through the process of changing the public IP within the management portal as per support chat instructions.

Hoping that once this is done and has taken effect phones will be able to communicate and will 'magically re-appear'.

Thank for all the suggestions, and I will update in the morning.

 

[Phil1975]

Phones have already re-appeared 'magically' and all looks good. Phones appear to be working again, although at 1:57am I'm inclined not to start calling people to test... lol

 

[Phil1975]

I guess my big question is... how did this all happen simply by putting the modem to bridge mode and installing the USG?

 

[Alphabetic]

Sounds like you duplicated your 3CX VPS somehow. Question for AWS really.

 

[Phil1975]

Yes it all came down to having two instances, but my question is - why did the 3cx FQDN suddenly start redirecting to the other instance at the same time that I installed the USG and put the modem into bridge mode.

As far as the two instances go; I think I did that at the initial setup.

 

[NickD_3CX]

why did the 3cx FQDN suddenly start redirecting to the other instance at the same time that I installed the USG and put the modem into bridge mode.

I don't think it has anything to do with the USG, but if you have installed 3CX multiple times with the same License Key, this will happen.
Each time a service is restarted or the server, that specific 3CX installation goes and changes the FQDN to it's own Public IP Address.
Of course though, so if you're using the FQDN to access, then you will "magically" be taken to the last installation that restarted.

Solution:
Find everywhere where you have installed 3CX with this license key and delete all instances except the one you actually want to keep.
Then finally for the instance you are keeping, in Settings --> Network set "Dynamic", wait 20-30 minutes, restart all 3CX Services, then go back and change it back to "Static" (if indeed your Public IP is a Static one).

 

[Phil1975]

Thank you... this all makes perfect sense as they would have both had the same license key I'm sure. I can now sleep easily with at least one less mystery to ponder...lol.

 

[NickD_3CX]

I'll mark this as 'Solved' as you seem to have got to the bottom of it, feel free though to open another thread.