Nathaniel, It really needs to be an analysis of "how that branch" functions. Depending on the role the branch serves within the organization in the event of any "natural disaster", especially for intra-office communication, relying on a T1 to call down the hall, upstairs, downstairs, etc, is perhaps "nonsensical".
A local PSTN gateway for inbound calls to be redirected for a main number, and for emergency outbound calling pretty well insulates it. With forty or so workers, 1 T1 only goes so far when it comes to calls:bandwidth. Of course, for branches with enough users, I always stick with a dedicated system per branch as I like a higher level of functionality when something goes down. For instance, if the T1 goes down and they can no longer make enterprise calls to other branches, they can dial the published number via a "copper rule" for dialing out via PSTN on a local gateway (as well as 911). Ultimately there has to be a "weight" to gauge what needs to be available, and how efficient and connected the branch stays in an outage. With a separate system the users can: 1. Continue t have their phones register. 2. Call each other. 3. Check voicemail. 4. Dial around to call out via alternate gateway (analog/siptrunk). 5. Call from their desk to bug you to ask you why you haven't fixed it yet. 6. Call other branches via their PSTN published number. Calling patterns, roles and survivability are all factors. On Thu, Jul 1, 2010 at 2:26 AM, maybelater <maybela...@gmx.de> wrote: > I might not be able to configure sipx the way I want, but been working in > sales and system-consulting for 4 years now. > > -breakdown of business telephony is major business killer > -according to Murphy your T1 WILL break down as soon as you rely on it too > much > -rerouting to mobile is great, but what about outbound calls ? > -need of local PSTN-Gateways is totally dependent on the task your > coworkers > on the remote site are doing, the availability they need for their > telephony > > I am a strong believer in centralization, thus I would just configure them > on the central PBX, but there are (of course) scenarios where the customer > Or the situation demands the best possible availability > > > -----Ursprüngliche Nachricht----- > Von: sipx-users-boun...@list.sipfoundry.org > [mailto:sipx-users-boun...@list.sipfoundry.org] Im Auftrag von > sipx-users-requ...@list.sipfoundry.org > Gesendet: Donnerstag, 1. Juli 2010 05:10 > An: sipx-users@list.sipfoundry.org > Betreff: sipx-users Digest, Vol 76, Issue 154 > > Send sipx-users mailing list submissions to > sipx-users@list.sipfoundry.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://list.sipfoundry.org/mailman/listinfo/sipx-users > or, via email, send a message with subject or body 'help' to > sipx-users-requ...@list.sipfoundry.org > > You can reach the person managing the list at > sipx-users-ow...@list.sipfoundry.org > > When replying, please edit your Subject line so it is more specific than > "Re: Contents of sipx-users digest..." > > _______________________________________________ > sipx-users mailing list sipx-users@list.sipfoundry.org > 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/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: tgrazi...@voice.myitdepartment.net Fax: 434.984.8431 Email: tgrazi...@myitdepartment.net LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: helpd...@voice.myitdepartment.net Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org 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/
