Webmeeting : Portal not found

[Paul Otter]

Hi,
When I log into the 3CX Web client and select "WebMeeting" from the left hand side menu I see a message which reads :
"Portal not found: "MYCOMPANY-uk.3cx.net" , so I'm unable to log in and use the webmeeting.

This did previously work, and has stopped sometime in the last 6 weeks or so.

I'm the admin for two 3CX systems, one works, one doesn't.
I've compared the WEBMEETING_FQDN parameter in each, and they both follow the same format ("MYCOMPANY-uk.3cx.net" ) where the value for MYCOMPANY differs and is the same as the following part of the URL for my dashboard.

https://MYCOMPANY.3cx.co.uk:5001/#/app/system_status/all

Both systems WEBMEETING_FQDN URL's resolve to 35.242.241.239 which is a Google IP address.

In addition, the system that gives the error has the WEBMEETING_BEST_MCU parameter set to eu006-lon.3cx.net which resolves to 78.129.229.5

I'm wondering if there's a record missing on 3cX's server for my company.

Both systems are running Debian, and I've tried re-booting out of hours, but it made no difference.

I've tried in Chrome Version 71.0.3578.98 in both a standard window and also an incognito window.

Any suggestions appreciated.

Paul

 

[LeonidasG_3CX]

Could you please send me the license key for the affected system? It may be that your maintenance has expired.

 

[LeonidasG_3CX]

Thanks, i've taken a look around and as starters i'm not seeing any communication from your PBX to webmeeting.3cx.net for the past week(our data retention period) for the license key you provided.

Could you add a temporary iptables firewall rule to allow 2 way communication between your PBX and webmeeting.3cx.net, restart the 3CX System service and re-check if WebMeeting starts working? Also could you check if you can contact webmeeting.3cx.net directly from your PBX's terminal?

As a last step, if the above fails, please go to your Management Console > Dashboard > Activity Log > Settings > and set this to Verbose. Perform a 3CX System Service restart and then from the same Activity Log section, go to Logs > Instance1 and PM me a copy of the systemservice.log for further checking.

 

[Paul Otter]

Hi,
Could you clarify exactly what the record needs to be in iptables ?
I'm not great with Linux, but I think IP addresses have to be specified, rather than URL's.

I've attached a screenshot from our terminal below which shows that we can ping the url webmeeting.3cx.net

Its very inconvenient for me to perform a 3CX System Service restart, as our PBX is in use for 18 hours a day, so anything else we can check before I do this would be better.

Thanks

Paul

 

[LeonidasG_3CX]

According to the image you sent, it looks like webmeeting.3cx.net is reachable by the PBX. It's likely there's some issue with your 3CX System Service. Unfortunately i really would need to take a look at the 3CX System Service log to be able to tell you more.

 

[Paul Otter]

Hi Leonidas,
I managed to get the system rebooted this morning 5 times until eventually webmeeting is now accessible, however there is still an underlying issue.

Our PBX host (Debian from the iso) has eth0 (LAN) and eth1(WAN).
eth1 connects to its own dedicated router / internet connection with nothing else connected.

Through the 3cx console the network always (after each reboot) appears correctly configured, so Settings - > Network Default Gateway = eth1 (showing 192.168.0.XXX) address
Static public = the correct external IP (which also resolves to our XXXX.3cx.co.uk hostname).

Phones are set to connect on the eth0 IP address 10.10.XX.XX but via our dns server, so they connect to an internal hostname voip.ourdomain.net that reolves to the eth0 (LAN) address.

PBX DNS is set to 8.8.8.8. and 8.8.4.4. in resolv.conf

Here's what we experienced.

Reboot 1
All external extensions (people using the App) are up, they work, and the trunks are up and running, but internal extensions don't work.
Customers can call in and hear auto attendant etc.

Run the following script so the PBX knows when to use eth0 and eth1:
root@3cx:~# cat /etc/network/interfaces.d/vlanScript
ip route flush table admin
ip route flush cache

ip route add 10.10.9.0/16 dev eth0 src 10.10.9.10 table admin
ip route add default via 10.10.9.1 dev eth0 table admin

ip rule add from 10.10.9.10/32 table admin
ip rule add to 10.10.9.10/16 table admin
ip rule add to 192.168.250.4/24 table admin
ip rule add to 192.168.51.0/16 table admin

ip route flush cache

Still doesn't work.

Reboot 2
All internal handsets work, but external trunks are down, and the App isn't accessible to remote workers.

Run the same script from Reboot 1: Still doesn't work.

Reboot 3
Same as reboot 2

Reboot 4
Same as reboot 1

Reboot 5
External extensions work, internal don't.
The LAN address isn't accessible from a PC.

Connect a laptop the the WAN router, and run the same script from Reboot 1: Everything is working fine.

Internal and external extensions are up, as well as trunks.

I haven't turned verbose logging on, and because of the unreliability I dare not reboot again.

Do yo have any suggestions on how I can make the system reliably recover after a restart ?

The attachment may answer other questions you may have.

Thank you for your help

Paul