Now if your also wanting it to run on the ARM based QNAP and Synology devices, might as well throw even more complexity in because that would most likely require them to completely re-compile 3CX as those CPUs do not run the same architecture, and there are yet more differences in the stack they would have to run, not to mention the processing power deficit those ARM based NAS Devices also suffer from. But having worked these kind of situations before coming into situations where internal teams did something that was a bad idea to save money or time, i can attest, it is better to do it the simpler, supported, right way the first time. Is saving a couple hundred bucks, worth hours of troubleshooting down the road? If it is by all means continue down this path, more power too you.
#Installing asterisk on synology nas software
But even if there were no socket/network conflicts period, all the other software on the qnap could "potentially" cause a troubleshooting nightmare if not at least unpredictable function. 3CX uses a number of socket connections on localhost for its various services to talk to each other, and these also, would have issues if any of those sockets were conflicted as well. QNAP is proprietary, non open source, with lots of open source mixed in.ģCX Support and Engineering themselves insists that a server used for 3CX not be used for anything else, and this is because 3CX has a lot of moving parts, and it can become very hard to diagnose and troubleshoot issues, when there are a lot more systems running in the background, and using various sockets all over the place. The issue would most likely be in the software stack itself. The OSI model asside and having little to do with the problem, ""network wise"", 3CX should function perfectly running from a QNAP, virtualized or not. And from that background, not trying to brag here, and with the knowledge i have garnered working with, building out, and troubleshooting 3CX for 3 years straight now, there are significant complexities involved in what your asking for. Ive also been developing on Linux and BSD for about 15 years now, so thats my background. OK, so my credentials include CCNA(Expired), CISSO, CVA, Computer Forensics, Network+, Security+, Linux+, etc.
IT inherently invites more places for potential problems with conflicts and compatibility to happen. Just because theoretically you could finagle 3CX to run on a NAS among all the other internal processes, does not stand to reason that you should. All in a box that you can hold in one hand. There are other options as well, such as the Embedded Network Infrastructure boxes, i have debian running on a number of them just fine, and they are available with mSATA SSDs, up to Intel I5 CPUs, and up to 16-32 GB of RAM.
#Installing asterisk on synology nas full
These distros are linux, but very stripped down, and often chop shopped for space savings, and packed full of other services running in the background, using up ports, etc.Ī virtualized environment, on a NAS that supports virtualization, such as a QNAP X86-64 variant would produce the best results, with the least additional complexity of having to make 3cx work with all the other software on the nas without conflicting in unexpected ways. You would not want to have 3CX running in the native environment of a NAS, you would want it virtualized.
0 kommentar(er)
