True, but if he's only talking about 12 or 13 users, at most you would expect 4 to be on the phone at once.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Robert Joly Sent: Friday, August 21, 2009 11:03 AM To: Alan McKay; sipx-users Subject: Re: [sipx-users] architecture decisions for new install > Hey folks, > > I want to set up a SipX server for my new employer, and I > have a few decisions to make on where to put it. > > Most of our employees are here at the main office in Ottawa - > about 15 or 16 of us. > > We also have a half dozen remote workers in the US and Asia. > > Coming into our office we have a DSL and a Cable modem connection - > not the best. About a year ago (before my time here) they tried a > VOIP provider and dumped it. Though nobody has details on > exactly what solution they were using, I gather that a large > part of the problem was with trunking, which suggests that > setting up the SipX server here in the office may not be a good idea. > > If I were to put it here, it would be behind a Clark Connect > firewall, on a private IP. I did some searching on the list > and see that Clark Connect seems to be able to handle this > properly, is that right? In my case I could assign a public > IP to my SipX server, with 1:1 NAT back to the actual private IP. > > My other option is to put the SipX server into our data > center. I prefer the option because it is a Class A data > center with full security, UPS backup and so on. Back in the > big North American blackout of 2003, our data center just > kept right on humming with their diesel backups. It also has > several major backbones coming into it, so bandwidth should > not be an issue. One element to consider with the data center approach is that it will potentially put more strain on your Ottawa office DSL and cable modem connections. More specifically, every call from a local Ottawa user to either Voicemail, Auto-attendant, ACD queue or a conference bridge will cause media streams to be established between your Ottawa site and the data center. These media steams would stay local to your Ottawa private LAN if you were to have the sipXecs deployed there (but of course the flip side of this is that calls to Voicemail, Auto-attendant, ACD queue or a conference bridge from a remote user would now consume bandwidth at the Ottawa site which is not the case if sipXecs was in a data center). 8< _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
