3CX System not working

[UNVT-IT]

What do I have to do?
Review your network access rules and ensure that you allow connectivity to activate.3cx.com. Outbound TCP:443 must be allowed to activate.3cx.com. Due to the nature of our service clusters, we cannot provide you with a fixed IP list.

Ensure that you update your 3CX PBX by the 28th February 2022 to v18 Update 2. Alternatively ensure that version 16 Update 8a is installed, however this will be a short-term fix - until November 2022.

I received the following email and do not know if this is related to the issue I am having. I am hosting the 3cx system on AWS EC2 instance. Within AWS, I can connect to it from the public IP address. I see the system and everything looked good. It is running version 18.0 Update 2. but I am not able to make calls or call the 888 number. I log in to the portal.3cx.com and when I try going to click on web client or console, they both time out with the following error " The site cant be reached."

Is this a DNS issue?

What do I need to check or configure to get the system working again?
Any help would be appreciated.
Thank you

 

[Saqqara]

This has nothing to do with the activate.3cx.com changes

Have you setup another 3cx server using the same fqdn and license key

You say you can connect to the 3cx server via IP address and not the fqdn - is this correct. If so does your aws server have a fixed IP address ?

If you do not have a fixed IP address, log into you 3cx console via IP address - goto settings - network and change the wan address to be dynamic. This change can take 6hrs to replicate across the internet before you can access the console via fqdn.

If you have a aws fixed IP address, make sure the wan static matches the aws IP address

When this is working, you can look into why you can not make calls - probably down to fqdn not pointing to correct ip address

 

[UNVT-IT]

1. I have not set up another 3cx server.
2. From within AWS > ec2 > instances > open with Public IPv4 address. this allows me to connect to 3cx system.
when I go to the network settings > manage IP address > looks like they are fixed IPs. I can't change them but can assign new IPs.
3. in the 3cx system > network settings> Public IP > select Network Card Interface > this IP matches the AWS private IP.
I scroll down to > External IP Configuration > 3cx static IP and AWS Public IP do not match.

Is that the place where I need to change to match the AW Public IP?

 

[Saqqara]

Yes, you need to change wan IP address within 3cx

If you have a static aws wan IP address, set the external ip to your fixed Ip address

If you do not have a static wan IP address, set the external ip to dynamic

After making the changes, std and pro licenses it can take 6hrs for the fqdn to be updated , enterprise is 5 mins

 

[UNVT-IT]

Ok, I am now able to get into the web client and log in. I am also able to receive calls but I still have an issue making calls.

 

[VasilisV_3CX]

Hi @UNVT-IT,

Glad to hear that you're able to receive calls. When making calls, do internal (ext A to ext B) calls work?

 

[UNVT-IT]

yes, internal calls work.

 

[Saqqara]

Check the activity log, to see why outbound calls are not working

 

[UNVT-IT]

when I try 10 digits xxx.xxx.xxxx i get the following: [Flow] target endpoint for xxx.xxx.xxxx can not be built!

when I try with +1 and 10 digits I get the following: Call to <sip:+1xxx.xxx.xxxx.voiceconnector.chime.aws:0> has failed; cause 403 Forbidden/invite from Public IP:5060

 

[Saqqara]

Have you been able to make outbound calls before ?

Error message 1 - you do not have a outbound rule that can be matched.

Info on outbound rules - https://www.3cx.com/blog/voip-howto/outbound-rules-a-complete-example/

Seeing you are using Chime - as your wan ip address has changed have you updated the info in Chime portal (allow host list) ?

https://www.3cx.com/docs/amazon-chime-voice-connector-sip-trunk/

 

[UNVT-IT]

I have an outbound call rule:

calls to numbers starting with prefix: 9
calls from extension: blank
calls to numbers with a length of: blank

Make outbound calls on:
route1 amazon chime strip digits:1 prepend:+1 outbound caller id: blank

You were correct, I needed to update the new wan IP on the (Allow host list). thank you for this. now able to make outbound calls from