Q: 3cx PBX ssh access (VM deployed to OVH public cloud via 'pbx express') ?

Status
Not open for further replies.

fortech

Bronze Partner
Joined
Jan 18, 2011
Messages
159
Reaction score
45
Hi, I am curious if anyone can comment. I'm trying to get ssh access onto a 3cx instance I setup for a client a few weeks ago. It was deployed to "OVH Canada Public Cloud" using the 3cx "PBX Express" deployment tool. I've got web based admin access no problem, using the admin user which was setup at time of install / password that was setup at this time.

From what I can tell, reading the forums, there are some different variants on what user name is to be used for ssh access, depending on how the host was deployed.

ie, ISO Debian manual install - you have to pick user-pass manually; in theory you know then if you know how to write :)
deployed onto Azure, it has one stock username
deployed onto Amazon EC2 it has different username
etc.

I tried various 'stock usernames' I found in forums and so far it is not working. I'm mindful that this is fools errand trying to guess the proper username. Wondering if someone who has does this before / or is involved with 3cx devel team can comment what is proper user I should expect to be able to use in this case ?

Thanks!


Tim

(Context piece: I'm trying to do this. Not because I want to break and customize things under hood. But because I want to do a bit of command-line debug testing of access between my 3cx instance and my voip carrier SIP trunk server. Weird thing here is that about 4x per week, for about 3 minutes, my sip trunk from this 3cx instance to my sip trunk provider - voip.ms - simply drops to unregistered. Then goes back to 'registered' and all happy - after 1-3 minutes approx. I put in ticket with OVH and they confirm 'we see no network problems at times you reference'. they suggest I test connectivity between 3cx and sip server. I am mindful trying to 'catch' this is probably a fools errand. It is just weird; I have other 3cx VMs deployed on the OVH Public cloud, also talking to VoipMS sip trunk server, and there is no problem like this ever. So just weird/annoying. I guess maybe I can change my voipMS Config to use a different server - montreal7 instead of montreal8 or something like that. But . Sigh. Annyoing.). Anyhow. too much info. Thanks.
 
From the 3CX Management Console you can do a packet capture which will show you whats happening at the network level from the PBX. No need for command line to do this.

Also, in a Debian deployment, you can access the terminal from the Terminal button in the dashboard.

This will allow you to perform some basic command line functions like traceroute or ping to your provider from the PBX server, without needing SSH access.

1595849838737.png

1595849870706.png

Just note this is NOT root access.
 
Status
Not open for further replies.

Forum statistics

Threads
111,954
Messages
589,924
Members
164,852
Latest member
priya