Update 3 Final: Wake Up with PUSH for the Web Client & PWA

Although we have already starting testing in this direction, for the time being a good alternative you could consider for your RPi installations to keep them up to date could be Hosted with 3CX.
if I try to place PBX Hosted with 3CX, he writes that it is not available in our country (Russia)
 
This might actually take a while as V18 U3 will not have support for RPi.
Unless something changes, we might have to hold off on Raspberry Pi support until the 3CX software is fully tested on Deb11 (Bullseye).

Although we have already starting testing in this direction, for the time being a good alternative you could consider for your RPi installations to keep them up to date could be Hosted with 3CX.
Will we see the SBC support Bullseye on RPi before 3CX? We only use RPi for SBC for our customers, never the PBX. I'd imagine certifying the SBC on Bullseye would be far less complicated than entire PBX.
 
Will we see the SBC support Bullseye on RPi before 3CX? We only use RPi for SBC for our customers, never the PBX. I'd imagine certifying the SBC on Bullseye would be far less complicated than entire PBX.
Can't say for sure if this will be the case yet but for now the 3CX SBC will continue to be supported on Buster and can still be deployed using the image found in our guide.
 
  • Like
Reactions: CentrexJ
"Ability to deploy via AD Group Policy Object"
Please also investigate the ability to deploy via Intune as well where the users have no ability to install the desktpo app at all.
 
Please also investigate the ability to deploy via Intune as well where the users have no ability to install the desktpo app at all.
We have not tested deployment with Intune but there is a thread where it was discussed a bit. I'm not sure if you'll find the information in it useful as I don't know exactly what deploying via Intune entails but you might want to have a look: https://www.3cx.com/community/threads/3cx-client-and-intune.84144/#post-404793
 
We have not tested deployment with Intune but there is a thread where it was discussed a bit. I'm not sure if you'll find the information in it useful as I don't know exactly what deploying via Intune entails but you might want to have a look: https://www.3cx.com/community/threads/3cx-client-and-intune.84144/#post-404793
Yes, I wrote in there as well and I already had a ticket open, but nobody, nor Microsoft seems to make it work.
Intune is some kind of gpo-domain thingy when you control the devices from the cloud. So you don't have any servers needed anymore. But the user has no administrator privileges and we can deploy apps from within intune to the devices. But the 3CX apps are installed in the c:\users\USER\appdata\local.... instead of to the programfiles.... and perhaps there is the catch.
 
Hi,

I was told that when searching for users, all internal users will be displayed at the top of the search list like it was on V16 in this new V18 v3 update. I can't see anything in the change logs, could anyone confirm please?
 
Hi,

I was told that when searching for users, all internal users will be displayed at the top of the search list like it was on V16 in this new V18 v3 update. I can't see anything in the change logs, could anyone confirm please?
Looks like it for me
 
  • Like
Reactions: ChrisC_3CX
I was told that when searching for users, all internal users will be displayed at the top of the search list like it was on V16 in this new V18 v3 update. I can't see anything in the change logs, could anyone confirm please?
Yes they will, provided that "Sort extensions by number" is enabled:

1646213025576.png
 
Hi,
I see the point to harden the 3cx environment, but to replace the source.list is a bit to much. There are customers like us, who have a need to have 3CX running self-hosted. From now on when ever there was an update of 3cx we need to add the entries again to keep the packages up-to-date we need besides, e.g. for the monitoring agent. I assume with every update you'll replace the source.list again, right?

Best,
m.jeu
 
Hi,
I see the point to harden the 3cx environment, but to replace the source.list is a bit to much. There are customers like us, who have a need to have 3CX running self-hosted. From now on when ever there was an update of 3cx we need to add the entries again to keep the packages up-to-date we need besides, e.g. for the monitoring agent. I assume with every update you'll replace the source.list again, right?

Best,
m.jeu
Hi!

Yes, this is correct, on every update this will be replaced.
We have done this to avoid all the issues that have happened over the years where Debian releases a package update that might "break" your 3CX installation (like what happened with IOS PUSH last year...) and to avoid issues for package versions not existing after some time, if you have old systems and you try to upgrade them.

This aside, remember that the 3CX Instance is supposed to have ONLY the 3CX software, nothing extra. I understand the point you make on monitoring software, but we have found that a lot of times 3rd-party software, sometimes even including monitoring software, can affect the installation as a whole.

I would highly suggest you don't add additional repositories.

At the very minimum, if you add a repository for whatever reason, e.g. to install a package, immediately remove it afterwards so that 3CX does not view packages from there. This would likely still render your system "unsupported", but at least reduces the chances of breaking something.
 
  • Like
Reactions: ChrisC_3CX
Hi Nick,

Thanks for the extended reply. I get the point why you're doing this, but as long as 3CX does not provide an api or snmp connection to integrate the instances into an external monitoring system, there is a need for extra packages to be installed besides. We'll test the temp. adjustment of the source.list file and see what happens.

Nevertheless, changes like this should be part of the release announcements.

Best,
m.jeu
 
  • Like
Reactions: Anaphylaxis
Looking at the repository situation from different angle - after recent changes, are we now able to install 3CX service pack updates by apt update / apt upgrade via CLI instead of initiating it via management console?
Previously, this approach wasn't recommended / supported for obvious reasons.
 
  • Like
Reactions: m.jeu
no problem. but is sad that we have apple silicon hardware for over a year and 3CX have issue with universal binaries
Please do complaint to Apple about Arch change, I mean we can't run any existing windows virtual machines, or so many other things that used to work just fine ;)
 
  • Like
Reactions: Evolute IT
Looking at the repository situation from different angle - after recent changes, are we now able to install 3CX service pack updates by apt update / apt upgrade via CLI instead of initiating it via management console?
Previously, this approach wasn't recommended / supported for obvious reasons.
It still isn't and there is no intention of being so, but we plan on having a different repo for each major version and update version, so theoretically this would be relatively safe if you force installed the 3CX version that matches the repo version you place.

Let's stick to "It still isn't and there is no intention of being so" though because still things can go wrong, this is not something that will be tested, so unpredictable things may happen.
 
  • Like
Reactions: Evolute IT
It still isn't and there is no intention of being so, but we plan on having a different repo for each major version and update version, so theoretically this would be relatively safe if you force installed the 3CX version that matches the repo version you place.

Let's stick to "It still isn't and there is no intention of being so" though because still things can go wrong, this is not something that will be tested, so unpredictable things may happen.
Thanks. I get the point.
So basically at the moment, the primary intention of overwriting sources.list is to treat 3CX installation as an appliance as much as possible (regardless if it is installed from ISO, installed in a supported cloud provider or self-hosted).

When the rest API which has been spoken about for some time gets released, would it support triggering updates? Going via management console for 150+ setups is bit tedious (about the only time when we are not happy about the fast phase of feature additions :-) )
 
Looking at the repository situation from different angle - after recent changes, are we now able to install 3CX service pack updates by apt update / apt upgrade via CLI instead of initiating it via management console?
Previously, this approach wasn't recommended / supported for obvious reasons.

There was an issue that occured about a year ago that was caused by a package conflict if the client used apt upgrade to update debian.

I like to think of 3cx as an "appliance" rather than a traditional VM. If you ran cisco UCCM for example, you would have 8 vm's which are all locked down and unable to have any changes done.

I know there is a Idea's post for snmp monitoring, and I would reccomend upvoting that so we can hopefully get it implemented by 3cx.

Currently, I would suggest the following sensors

ping and port tests on any ports you use in your setup. I know our monitoring system (PRTG) can also simulate a full page load as well. While that is heavier than a nicely integrated SNMP integration. it at least can give you a bit of informaiton.
 
via management console for 150+ setups is bit tedious
It would be nice if we could enable or disable automatic updates via Instance Manager.
 
  • Like
Reactions: Anaphylaxis

Forum statistics

Threads
111,974
Messages
590,083
Members
164,901
Latest member
Silent_Guru