I have a debian instance setup and running a 3CX environment in AWS. My 3CX fqdn that was setup by 3CX automatically during the build out looks like companytest.3cx.east.us and in AWS I have a route setup in route 53 that points the public IP of the 3cx instance to a custom domain (3cx.comany.com). Instead of having users use the 3CX provided fqn to setup their phones, the idea is to use the route that I setup in AWS that points to the elasticIP to connect their phones.
When they use 3cx.company.com (AWS route), the phones connect just fine, but out of nowhere could only receive calls. When trying to make a call it fails when having the AWS Route as the SIP URL, but they can receive all the calls they want. Is there a way to allow this to work?
When they use 3cx.company.com (AWS route), the phones connect just fine, but out of nowhere could only receive calls. When trying to make a call it fails when having the AWS Route as the SIP URL, but they can receive all the calls they want. Is there a way to allow this to work?
