- Joined
- Mar 10, 2021
- Messages
- 1
- Reaction score
- 0
I've been climbing this hill for a few days now: Remote Yealink T54w will not connect to 3cx enterprise server hosted on aws
Have a user in New Hampshire (I'm in TX so long drive for support) attempting to use a t54w over a starlink internet connection. I configured the phone locally here in TX and connected to a couple of different networks that do not have sbc to double check that the phone would connect to my 3cx instance hosted remotely on AWS. All was wonderful and I've done this with a few phones and have never had them fail when connected at their ultimate service location. At the remote location they have connected the phone to their local network via both wifi and ethernet with same result.
The remote IP address is not blacklisted and I've tried whitelisting it just because.
Any thoughts would be greatly appreciated.
Further info
Just got this message on 3cx
This IP Address XXX.XXX.XXX.XXX has made numerous attempts to authenticate with 3CX using invalid credentials. In response, 3CX has blacklisted this IP and denied any further requests.
I can obviously remove the blacklist entry, but don't understand the cause of the invalid credentials.
Have a user in New Hampshire (I'm in TX so long drive for support) attempting to use a t54w over a starlink internet connection. I configured the phone locally here in TX and connected to a couple of different networks that do not have sbc to double check that the phone would connect to my 3cx instance hosted remotely on AWS. All was wonderful and I've done this with a few phones and have never had them fail when connected at their ultimate service location. At the remote location they have connected the phone to their local network via both wifi and ethernet with same result.
The remote IP address is not blacklisted and I've tried whitelisting it just because.
Any thoughts would be greatly appreciated.
Further info
Just got this message on 3cx
This IP Address XXX.XXX.XXX.XXX has made numerous attempts to authenticate with 3CX using invalid credentials. In response, 3CX has blacklisted this IP and denied any further requests.
I can obviously remove the blacklist entry, but don't understand the cause of the invalid credentials.
