another cool thing we found out in a disaster is the fortinet phones (which I believe are just branded 3coms) can pretty easily be configures to take your sip trunk if your pbx has failed. A good example of this being handy is a fire, the customer can take the fortivoice phone wherever they have internet and plug it in to get minimal voice back up. We had a customer with a firewall mishap that broke their sip so while the firewall was being addressed with their pbx vendor, we put a fortivoice phone in to handle their customer trunk.
On Wed, Nov 18, 2015 at 4:33 PM, That One Guy /sarcasm < [email protected]> wrote: > we do fortinet only > You can do it without a problem > its a good system as long as you realize is a voip pbx in a box, its not > as configurable as some, but thats the beauty, you have a clear line of can > do and cannot do > Its designed to be an end user system as in you sell it to a customer and > they manage it through their support contract with fortinet > We have one customer who did that, he has had good success with self > management, and hes a dolt at times. > They bought Talkswitch so its actually a rebranded but seasoned system > The virtual pbx is more scalable, but without conversion hardware it > doesnt do pots > > > On Mon, Nov 16, 2015 at 3:56 PM, Matt <[email protected]> wrote: > >> We are looking at upgrading our phone system. Looking at Fortinet. >> We have two locations now with separate phone numbers. Wanting to >> link the systems over Internet so we can help each other out when one >> location or other has too many lines ringing. >> >> What is everyone else using for a phone system and how do they like it? >> > > > > -- > If you only see yourself as part of the team but you don't see your team > as part of yourself you have already failed as part of the team. > -- If you only see yourself as part of the team but you don't see your team as part of yourself you have already failed as part of the team.
