wardmundy
Nerd Uno
- Joined
- Oct 12, 2007
- Messages
- 20,217
- Reaction score
- 5,974
Good ideas and I like the idea with the same interface in both locations cloud and local, that is asterisk based. Haven't read the TOS for 3CX but I guess a 3CX cloud server for each trunk would work but my 18 trunks would be a little complex with 18 cloud servers. Besides the issue of two different interfaces, the time to keep this working makes it less reliable. The past year I've rebuilt several systems and seem to be using one of my backups to make and receive calls and have to adjust to limited functions.
Just desire a rock solid system with all the bells and whistles and free![]()
You only need one 3CX server. Just manipulate the dial string for outbound calls on the Raspberry Pi side. For example, incoming calls with numbers like 843XXXXXXX go out the Vitelity trunk and numbers like 800XXXXXXX go out the XYZ trunk, etc.