- Joined
- Sep 30, 2017
- Messages
- 5
- Reaction score
- 0
Hi:
I realize much of the 3CX documentation assumes a local on-site install of 3CX, but that's not how I'm using the software PBX.
I'm very surprised there's no documentation on what should be a common configuration where 3CX runs on a Linux Debian 8 VPS on a cloud service provider.
I got 3CX running on Debian 8 Linux VPS no problems. Now this is where the confusion starts.
These instructions to configure the Cisco 79XX (I have the 7960G) IP phones to use with the 3CX assume the 3CX install is done locally. https://www.3cx.com/sip-phones/cisco-7940g-7960g/
Are there instructions to setup the Cisco 79XX phones with a 3CX Debian 8 VPS configuration (using a cloud service provider)? For example it says set up that TFTP server? But do I set that TFTP server up exactly? Do I set up the TFTP server on the same cloud service Debian 8 VPS as 3CX is running on? Do I use one of the computers on my own local network (which I don't want to do really) for the TFTP service? These instructions don't say. They're written assuming everything is on the same local LAN.
The user manual doesn't address my specific setup needs. Does someone have an up-to-date set up instructions to set up the TFTP server with a 3CX software PBX running on Debian 8 VPS on a cloud service provider? And then have the TFTP Server convert my phones to the 3CX 8.5.4 firmware and provision my phones with the proper extension information via the 3CX software PBX running on the Debian 8 VPS? This configuration has to have some documentation for it. It should be a common configuration out there.
Let me know. Thanks for your help and time.
Once I can get the TFTP server figured out and the Cisco 7960G information such that I can update the firmware on the 7960G's properly for a 3CX SIP interface and provisioned for the extensions with the 3CX PBX running on a Debian VPS (remotely, on a cloud service provider), I should be able to figure the rest out myself. But I don't want to walk into this important step without the proper documentation.
Thanks.
I realize much of the 3CX documentation assumes a local on-site install of 3CX, but that's not how I'm using the software PBX.
I'm very surprised there's no documentation on what should be a common configuration where 3CX runs on a Linux Debian 8 VPS on a cloud service provider.
I got 3CX running on Debian 8 Linux VPS no problems. Now this is where the confusion starts.
These instructions to configure the Cisco 79XX (I have the 7960G) IP phones to use with the 3CX assume the 3CX install is done locally. https://www.3cx.com/sip-phones/cisco-7940g-7960g/
Are there instructions to setup the Cisco 79XX phones with a 3CX Debian 8 VPS configuration (using a cloud service provider)? For example it says set up that TFTP server? But do I set that TFTP server up exactly? Do I set up the TFTP server on the same cloud service Debian 8 VPS as 3CX is running on? Do I use one of the computers on my own local network (which I don't want to do really) for the TFTP service? These instructions don't say. They're written assuming everything is on the same local LAN.
The user manual doesn't address my specific setup needs. Does someone have an up-to-date set up instructions to set up the TFTP server with a 3CX software PBX running on Debian 8 VPS on a cloud service provider? And then have the TFTP Server convert my phones to the 3CX 8.5.4 firmware and provision my phones with the proper extension information via the 3CX software PBX running on the Debian 8 VPS? This configuration has to have some documentation for it. It should be a common configuration out there.
Let me know. Thanks for your help and time.
Once I can get the TFTP server figured out and the Cisco 7960G information such that I can update the firmware on the 7960G's properly for a 3CX SIP interface and provisioned for the extensions with the 3CX PBX running on a Debian VPS (remotely, on a cloud service provider), I should be able to figure the rest out myself. But I don't want to walk into this important step without the proper documentation.
Thanks.