<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Baldur,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
According to Nick Edwards, the OP, the main application is voice, which most any DSLAM will handle easily, and solve his IP PBX line consolidation problem. Instead of physical lines into the PBX, he can use the integrated DSLAM SIP calling capability as the
IP PBX interface. Given that only some of the 1700 lines will be in use simultaneously, that amounts to very little bandwidth.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Data capacity of 10 or 20 Mbps in this environment would be pure gravy, and 100 Mbps is almost certainly not expected, or needed, for "worker huts". I'm assuming the workers are not all tele-surgeons
<span id="🙂">.🙂</span><br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
-mel<br>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> NANOG <nanog-bounces@nanog.org> on behalf of Baldur Norddahl <baldur.norddahl@gmail.com><br>
<b>Sent:</b> Thursday, May 7, 2020 12:55 PM<br>
<b>To:</b> nanog@nanog.org <nanog@nanog.org><br>
<b>Subject:</b> Re: alternative to voip gateways</font>
<div> </div>
</div>
<div>
<div dir="ltr">
<div dir="ltr"><br>
</div>
<br>
<div class="x_gmail_quote">
<div dir="ltr" class="x_gmail_attr">On Thu, May 7, 2020 at 9:05 PM Brandon Martin <<a href="mailto:lists.nanog@monmotha.net">lists.nanog@monmotha.net</a>> wrote:<br>
</div>
<blockquote class="x_gmail_quote" style="margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-left:1ex">
On 5/7/20 12:03 PM, Mel Beckman wrote:<br>
> In the OP’s case however, the copper plant is private, and wholly owned and already in operation. So surely in that situation fiber would be much more expensive to dig and trench.
<br>
<br>
Indeed, I was responding to Ohta's comments regarding copper vs. fiber. In this case, using DSL over the existing plant seems like a slam dunk unless very high speeds are needed or the plant is in very poor condition. Modern VDSL/2 DSLAMs are relatively inexpensive
and will push 100Mbps over surprising distances with essentially seamless fallback to ADSL2+ at ~24Mbps for long-reach situations.<br>
-- <br>
</blockquote>
<div><br>
</div>
<div>Actually we are told the distances are between 300 meters and 1600 meters. 1700 loops all from a single point. That is going to suck. There will be no vectoring and VDSL speeds starts to drop fast after 500 meters. There is going to be a ton of crosstalk.</div>
<div><br>
</div>
<div>If you want to deliver 100 Mbps you will need to rebuild the copper plant such that you isolate bundles of 192 loops in nearby cabinets. You need to build fiber and power out there. You need to invest in multiple decentral DSLAMs.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Baldur</div>
<div><br>
</div>
<div> </div>
</div>
</div>
</div>
</body>
</html>