Oh, there are such things as private MPLS networks, which is what i
suggested. That would beat the pants off a T1 or DS3, directly connecting
layers 2&3 while giving a layer 2 experience. It might be different if it
were an "internet port also", but while that is a choice, MPLS "labels"
things like voice ingress/egress, and prioritizes it, so I would beg to
differ with the assumption that it would "add latency" unless it was not
properly designed or configured.

On Thu, Jul 1, 2010 at 12:33 PM, Tony Graziano <tgrazi...@myitdepartment.net
> wrote:

> A private mpls network would introduce very minimal latency. But I think
> I'm done on this thread. the fact that he has that many users on a T1 is
> going to introduce latency when it is heavily used. MPLS may not be an
> option for him depending on how many sites he has like this. I recall
> Nathaniel likes vvx's, introduce on of them and ten calls and what happens
> to a T1?
>
>
> On Thu, Jul 1, 2010 at 12:30 PM, Todd Hodgen <thod...@verizon.net> wrote:
>
>>  I think the T-1 will give him a better network choice, as you won’t have
>> to deal with the added latency of MPLS.  A simple router can provide
>> adequate QOS for Voice and Data connections, and the cost of a dedicated T-1
>> from the Teleco in most areas is very affordable these days, especially for
>> Government.
>>
>>
>>
>> *From:* sipx-users-boun...@list.sipfoundry.org [mailto:
>> sipx-users-boun...@list.sipfoundry.org] *On Behalf Of *Tony Graziano
>> *Sent:* Thursday, July 01, 2010 6:17 AM
>> *To:* Josh Patten
>>
>> *Cc:* sipx-users@list.sipfoundry.org
>> *Subject:* Re: [sipx-users] Remote Location - 45 phones - separate server
>> or not?
>>
>>
>>
>> Might I suggest a private MPLS cloud instead of the T1's with tagging for
>> voice... this way he can use VVX's out on the fringe and we all know how
>> fond of those he is.
>>
>> On Thu, Jul 1, 2010 at 9:15 AM, Josh Patten <jpat...@co.brazos.tx.us>
>> wrote:
>>
>> Might I suggest putting a redundant proxy out at the remote location and
>> configuring your DNS like this:
>> http://wiki.sipfoundry.org/display/xecsuser/Location+based+DNS+views+for+sipXecs+using+BINDso
>>  all phones at that location register to that redundant proxy.
>>
>> >From experience I would get a second point-to-point data T1 to that
>> location dedicated to voice. Having that many users chewing up your T1 PLUS
>> phones is just asking for trouble.
>>
>>  Josh Patten
>>
>> Assistant Network Administrator
>>
>> Brazos County IT Dept.
>>
>> (979) 361-4676
>>
>>
>> On 7/1/2010 7:08 AM, Nathaniel Watkins wrote:
>>
>> The remote contains these offices (I’m not sure what some of these offices
>> due – some are State/Federal offices):
>>
>> Public Utilities
>>
>> Permits & Inspections
>>
>> Extension Office
>>
>> NRCS & GSCD
>>
>> Farm Service Agency
>>
>> Rural Development
>>
>> Election Board
>>
>>
>>
>> I totally agree that putting all your eggs in one T1 basket sounds like
>> crazy talk – however…
>>
>>
>>
>> Here are thoughts/concerns with a totally separate sipXecs install:
>>
>> 1)      Manageability
>>
>> a.       Patton will require additional routing rules for base
>> functionality
>>
>> b.      Additional dialing rules to route between sipxósipxóNECóetc.
>>
>> c.       Greatly complicates the overall design
>>
>> 2)      Functionality
>>
>> a.       End users are expecting the capability to plug their phones in
>> and just work (at any county location) – if we are routing DID’s to the
>> remote – and they plug their phones in at our Emergency Operations Center –
>> it needs to just ring there
>>
>> 3)      Costs
>>
>> a.       One of the driving factors is reducing costs – having a ‘server’
>> (granted could be an inexpensive one), plus failover trunks (handful of POTS
>> lines), plus additional analog gatways.  We are then looking at $2,000
>> capital costs and $1,000 annual operating costs.  This greatly drives down
>> the ROI and it seems hard to justify those costs coupled with the added
>> complexity of managing separate servers (plus having multiple DNS/DHCP
>> scopes).  All to work around a potential 2% business interruption
>> (considering a potential 1 week down time hazard).
>>
>>
>>
>> A HA install could be a compromise, but that introduces its own issues -
>> Perhaps a good compromise of a unified system and failover would be to have
>> a second route between sites;  i.e. have a site to site vpn over the
>> internet that would be a backup link.  In the event of a T1 failure, we
>> could route traffic over said connection?
>>
>>
>>
>> In a perfect world, I’d love to have a single, simple to manage phone
>> system.  Not 5 separate systems that I have to link together and have
>> equipment all over the place that I have to keep tabs on.  Of course, I’d
>> also like to not get fired for killing all of our phones J
>>
>>
>>
>>
>>
>> Nathaniel Watkins
>> IT Director
>> Garrett County Government
>> 203 South 4th Street, Room 210
>> Oakland, MD  21550
>> Telephone: 301-334-5001
>> Fax: 301-334-5021
>> E-mail: nwatk...@garrettcounty.org
>>
>>
>>
>> *From:* sipx-users-boun...@list.sipfoundry.org [
>> mailto:sipx-users-boun...@list.sipfoundry.org<sipx-users-boun...@list.sipfoundry.org>]
>> *On Behalf Of *Tony Graziano
>> *Sent:* Thursday, July 01, 2010 3:01 AM
>> *To:* maybelater
>> *Cc:* sipx-users@list.sipfoundry.org
>> *Subject:* Re: [sipx-users] sipx-users Digest, Vol 76, Issue 154
>>
>>
>>
>> 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.
>>
>>
>>  ------------------------------
>>
>> This message and any files transmitted with it are intended only for the
>> individual(s) or entity named. If you are not the intended individual(s) or
>> entity named you are hereby notified that any disclosure, copying,
>> distribution or reliance upon its contents is strictly prohibited. If you
>> have received this in error, please notify the sender, delete the original,
>> and destroy all copies. Email transmissions cannot be guaranteed to be
>> secure or error-free as information could be intercepted, corrupted, lost,
>> destroyed, arrive late or incomplete, or contain viruses. Garrett County
>> Government therefore does not accept any liability for any errors or
>> omissions in the contents of this message, which arise as a result of email
>> transmission.
>>
>>
>> Garrett County Government,
>> 203 South Fourth Street, Courthouse, Oakland, Maryland 21550
>> www.garrettcounty.org
>>
>>
>>
>> _______________________________________________
>>
>> 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/
>>
>>
>> _______________________________________________
>> 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.
>>
>
>
>
> --
> ======================
> 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.
>
>


-- 
======================
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/

Reply via email to