An error occured while sending request to (own fqdn:5001 )

[nitishh]

New to 3cx and learning so any help is appreciated.

we get this error while inviting attendees using web meetings. we are using custom fqdn. any ideas

 

[mixig]

Is 3cx behind NAT? If yes did you made port forward? Cloud based or on prem installation? Firewall checker is passing?

Also same problem (search the forum by your eror), reason was users firewall

 

[nitishh]

@mixig Thank you for your reply. Yes, the 3Cx is behind a NAT -: Yes Cloud-based -: Yes Firewall Checker passes -:

I must agree at this time it does look like an FW issue. When I see that copying the link and sending it via mail the Video conferencing works it's just for sending the email. I really want to know what are the components involved in sending the email. Is it the client (who is initiating the video meeting ) the one who is sending the requestor and thus failing or is it being sent by a 3cx server.

 

[mixig]

Does 3cx has cinfigured with the real public ip, in 3cx portal does your domain is bind with that ip address?

 

[nitishh]

yes, the 3cx is bound with a real IP. and yes 3cx portal does bind with that ip address.

i just whitelisted a couple of IP addresses from 3CX (35.242.241.239,216.239.34.21 ) and it still did not work.
Then I opened up the rule to fqdn with a 0/0 and it worked. so yes its the FW but i still do not understand which component is sending the request so that we could lock it down

 

[JohnS_3CX]

Hi,

Your fqdn needs to be reachable on the HTTPS port configured (usually 5001), this is incoming traffic

The PBX must also be able to reach the 3CX servers to inform them of the scheduled meeting, this is outgoing traffic via 443

Finally, the PBX needs to be able to send the email notifications.
This can be tested from Settings > Email > Test button


The 3CX MCUs may change from time to time so if you are looking for something to whitelist, you can look here https://www.3cx.com/community/threads/status-monitor-info.72678/

 

[nitishh]

@JohnS_3CX sorry for the late response . I agree with your comments as much as i agree with @mixig.
and i am doing my best to understand the required communication so that i can put the required controls in place .
we are all saying the same but unfortunately we cannot answer the required items because it has not been documented or I am not aware of the documentation and hence the confusion .

Q1: fqdn needs to be reachable on the HTTPS port configured (usually 5001), :
A1 :yes it is . but for what source address does this need to allowed for . I can reach it to administer it : But does it need to be reachable in the sense that open it for 0.0.0.0/0 (for lack of better terms)

Q2: The PBX must also be able to reach the 3CX servers to inform them of the scheduled meeting, this is outgoing traffic via 443 .
A2 : Yes the PBX is able to reach to the 3CX servers: If i copy the link and send it to my invitees we are able to have the meeting . The error does not mean that meeting cannot take place.

Q3 :
inally, the PBX needs to be able to send the email notifications. This can be tested from Settings > Email > Test button .

A3: Yes i tested this the first time I saw the error. I remember testing this multiple times because when i was provisioning my extension I realized that i had not gotten an email and then went on to identify the issues . so in short this correctley configure but yet I do get the error .

The solution was to open the internet to the pbx at port 5001 and that seemed to have fixed it. Do i know why nope i dont know why .

not sure if this helps

thanks

 

[JohnS_3CX]

Our list of ports and explanations can be found here https://www.3cx.com/docs/ports/

You might want to also take a look at this post here regarding locking it down:
https://www.3cx.com/community/threads/ports-required-to-connect-mcu-webmeeting.73303/

 

[nitishh]

@JohnS_3CX thank you for the response . I will follow the document and update this thread .