3CXPBX Detected. Aborting installation.

[Boschko]

Hello forum,

Im trying to install a 3cx sbc on debian 9 which has / is runing an already installed 3cx pbx. I wget the sbc.zip -o- | sudo bash and i get the nice "3CXPBX Detected. Aborting installation" why is this? Does 3cx not want us to be able to run both a sbc and their pbx on the same physical server? this is weird to me and somewhat frustrating. any insight would be great.

 

[nub]

why would you install a sbc on the 3cx server? whatever is local to that server can just connect direct to the server.

 

[Boschko]

basically we can have two accounts registered to a sip phone. account 1 would route through the sbc and account 2 on the same phone would route through the 3cx solution we have in place. both the scb and 3cx pbx would be on the same debian server. we want to basically not have to purchase a raspberrypi since we have a server might as well make good use of it, its a cleaner solution to offer to clients.

 

[leejor]

I can't see why this would be supported. If you require an SBC you will probably have to spend some money on a Raspberry Pi. The 3CX server and SBC would probably have some port conflicts, attempting to operate on the same IP.

 

[nub]

basically we can have two accounts registered to a sip phone, so setup account 1 to route to sbc and account 2 would route through the 3cx solution we have in place. we want to basically not have to purchase a raspberrypi since we have a server might as well make good use of it, its a cleaner solution to offer to clients.

2 account on the same phone connected to the same server? or 2 account 1 to that server and the second to another using the sbc server?


edit: removed "server"

 

[Boschko]

I can't see why this would be supported. If you require an SBC you will probably have to spend some money on a Raspberry Pi. The 3CX server and SBC would probably have some port conflicts, attempting to operate on the same IP.

I dont see why it would "not" be supported. Im assuming there must be port conflicts if they've got preventive measures in place to prevent this install method ( im still not sure if thats what it actually is ) but lets say you have a client with 15 sites I dont know many people who would want to manage virtual sbc's. So it seams like something that should be supported especially since 3cx is running within the debian OS so i should still be able to do as I please with my debian install.

What port conflicts do you imagine could arrive?

Moreover if we purchase a server why shouldn't we be able to run both the pbx and sbc on the same machine? why should we have to go out and purchase a PI when we've got a perfect debian based server?

 

[Boschko]

2 account on the same phone connected to the same server? or 2 account 1 to that server and the second to another using the sbc server?


edit: removed "server"

I've made the edits its 1 phone with 2 profiles connecting to one server that server would connect to the PSTN.....etc,

 

[nub]

you can manually provision 2 or more lines on most phones, maybe you would not need the sbc then.

 

[Boschko]

you can manually provision 2 or more lines on most phones, maybe you would not need the sbc then.

Yeah good point, but unfortunately we still would want to achieve this.

 

[cobaltit]

There are definitely port conflicts. If you insist on trying to install the SBC on the same box, use DOCKER or a VM to separate the two (with unique IP addresses).

 

[leejor]

if they've got preventive measures in place to prevent this install method ( im still not sure if thats what it actually is ) but lets say you have a client with 15 sites I dont know many people who would want to manage virtual sbc's. So it seams like something that should be supported especially since 3cx is running within the debian OS so i should still be able to do as I please with my debian install.

The issue you are running into may not be specific to attempting to add an SBC to a machine with the 3CX server already installed. It may be the result of 3CX preventing a second attempted installation of the PBX itself. the check that is made, insuring this doesn't happen, may be finding a file common to both he PBX and the SBC, thus blocking the install.

Allowing someone to "do as i please" with any software be it an install, or making unsupported modifications, simply creates the possibility of "another call to support" because something went horribly wrong. You may own the hardware, but you don't actually own the software unless you wrote it, so you have to accept the limitations put on it, usually for a good reason.

 

[Boschko]

There are definitely port conflicts. If you insist on trying to install the SBC on the same box, use DOCKER or a VM to separate the two (with unique IP addresses).

I was under the impression that docker environments were not supported by 3CX has this changed?

 

[Boschko]

There are definitely port conflicts. If you insist on trying to install the SBC on the same box, use DOCKER or a VM to separate the two (with unique IP addresses).

Soz I couldn't add to eddit.

But if my server has 2 NIC's then I really should be running into any IP conflicts

 

[cobaltit]

Correct, but it looks like there are either conflicting packages or simply a sanity check where they don't want 3CX and the SBC in the same environment. And I don't believe 3CX supports docker but they also don't support 3CX and SBC on the same environment yet you are trying to do that . But yes officially it needs to be a KVM based VM I believe.