Solved Migrated to google cloud

Status
Not open for further replies.

voice11

Bronze Partner
Basic Certified
Joined
Jul 15, 2016
Messages
78
Reaction score
2
Hello All,
Back again with another question :). I had originally installed 3CX Pro license (V15.5) Debian on VmWare workstation 14 Pro (14.1.0), running on WIN7 pro SP1. Now after using it for couple months & trying my hand on it, I migrated it to google cloud tonight. Looks like everything went well in theory because I see license information, FDQN confirmation etc in final steps. I however can't login to management console, meaning domain "https://company.3cx.com" doesn't open. Does anyone know why that is.
I have turned off my existing computer where old 3CX (same license) was residing & working ok, thinking that it could cause issues with console login (because same address, company.3cx.com) & also possible license usage violation. I am sure if I turn computer back on, PBX & phones will come online again....but I rather want to have cloud PBX working instead. Can anyone suggest what might I have done wrong.
 
From the provided logs i can see that the tunnel is disconnecting due to packet loss. A known reason for this is the machine hosting the PBX is under powered. What are the specifications of the machine? Could that be the reason the tunnel is disconnecting?
That shouldn't be @YiannisH_3CX. Because its I5, 4GB ram, brand-new computer I just bought a week ago. And computer has only & only SBC on it. My internet speed is pretty ok too, 50mbp down & 10up for just under 8 extensions... besides I have been using on-prem 3CX with 6 local and couple stun extension from remote sites without an issue. There gotta be something else. Thank you in advance.
 

Attachments

  • PC.PNG
    PC.PNG
    38.8 KB · Views: 2
I meant the machine hosting the PBX in the cloud. What is the size of the instance?
 
I meant the machine hosting the PBX in the cloud. What is the size of the instance?
Oh... that. It very well could be. Its shared G1 (1 above micro) with 1.7 GB memory. please let me know if that is the reason.
g1-small (1 vCPU, 1.7 GB memory)
 
Any input from anyone please? I am in Tuesday, middle of work week with just windows and apple soft clients working. None of the physical phones work with exception to one STUN extension (Yealink T48S)
 
I would reboot the VM and see if it fixes it up. Takes you down for 5 or so minutes which isn't ideal during the day. If that doesn't help then try increasing to 4gb ram which unfortunately if you do it during the day will also take your system down for 5 minutes or more.
 
Any input from anyone please? I am in Tuesday, middle of work week with just windows and apple soft clients working. None of the physical phones work with exception to one STUN extension (Yealink T48S)
Interesting that the clients are working on the same site. The reason i am saying this is because a client that is using the tunnel (I am assuming they are) is basically using the same service as the SBC if the SBC is not using encryption.
With that in mind i would search for the cause at the remote site where the SBC is located. Just as a test can you try a linux SBC if a spare machine is available for that ? It will be a good information to have. It could be something on the Windows machine causing this like A/V or the firewall.
If the issue persists with a linux SBC as well i would then recommend creating a ticket with out support department as they will need to go through the PBX and SBC logs to determine exactly what is causing this
 
Hey everyone. So the problem with my config was that after setting up my brand new computer, I enabled SBC & plugged it in to a switch with Cat5. Problem is, it was still connected with WiFi at the same time. Hence making it two network cards active at the same time, which is prohibited in BOLD for SBC lol. I troubleshooted pretty much every other step, except for this. Be mindful of that in your install. Thank you everyone & good luck.
 
Glad to see the issue is resolved and thank you for updating the thread with your solution.
 
Status
Not open for further replies.