<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
I’ve implemented these kinds of systems both ways, and in my experience, unless the existing copper is in bad condition, it’s always a cheaper, faster, and more reliable solution.
<div><br>
</div>
<div>Construction costs to hang outdoor radios and run cables is significant. The installation labor for a wireless deployment is intensive. The primary reason WISPs exist is to give people Internet who otherwise don’t have cheap copper connections available.
Line-of-site, growing trees, mobile obstructions, and rooftop cable entry are all potential failure points.
<div><br>
</div>
<div>An in-place copper plant with short runs below a mile can support 20-30 Mbps per user with a DSLAM, and 100+ Mbps using Ethernet-over-Copper, all with no construction costs, and virtually maintenance-free.<br>
<br>
<div dir="ltr"> -mel beckman</div>
<div dir="ltr"><br>
<blockquote type="cite">On May 5, 2020, at 5:06 AM, Baldur Norddahl <baldur.norddahl@gmail.com> wrote:<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="auto">
<div>Thinking out of the box, why not implement a WISP setup using wifi? This kind of gear is more accessible to normal IT staff. </div>
<div dir="auto"><br>
</div>
<div dir="auto">Voice can be implemented by VoIP using Wifi too.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Regards </div>
<div dir="auto">Baldur </div>
<div dir="auto"><br>
<br>
<div class="gmail_quote" dir="auto">
<div dir="ltr" class="gmail_attr">søn. 3. maj 2020 07.22 skrev Nick Edwards <<a href="mailto:nick.z.edwards@gmail.com">nick.z.edwards@gmail.com</a>>:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The huts or cabins whatever you want to call them, are right behind<br>
the admin building at entrance, so first is about 300 meters and the<br>
furtherest is just under 1 mile<br>
<br>
Cost will be an issue, Im sure I will have no problems if I have to<br>
install a full rack of gateways and another full of dslams if it costs<br>
150K, over something 1/5th the size in one rack that will cost 200k -<br>
since the company is not charging them for internet or voice.<br>
<br>
On 5/2/20, Jeremy Austin <<a href="mailto:jhaustin@gmail.com" target="_blank" rel="noreferrer">jhaustin@gmail.com</a>> wrote:<br>
> What’s the average loop length? Grandstream is probably OK to 5+ kfeet but<br>
> you will lose CID before that.<br>
><br>
> As the low cost option don’t expect them to be trouble-free (or have<br>
> particularly good vendor support), but they might work in your application<br>
> if cheap is what makes sense.<br>
><br>
> My $.02<br>
><br>
> Jeremy Austin<br>
><br>
> On Fri, May 1, 2020 at 10:11 PM Andrey Slastenov <<a href="mailto:a.slastenov@gmail.com" target="_blank" rel="noreferrer">a.slastenov@gmail.com</a>><br>
> wrote:<br>
><br>
>> Look at MSAN solution. Like Huawei UA5000 or similar solutions from other<br>
>> vendors.<br>
>><br>
>><br>
>> Regards,<br>
>> Andrey<br>
>><br>
>> > 2 мая 2020 г., в 07:21, Nick Edwards <<a href="mailto:nick.z.edwards@gmail.com" target="_blank" rel="noreferrer">nick.z.edwards@gmail.com</a>><br>
>> написал(а):<br>
>> ><br>
>> > I'm looking at a new sister company we just took over, their remote<br>
>> > village has 1700 analogue phone lines to the workers huts, but they go<br>
>> > nowhere past the MDF.<br>
>> ><br>
>> > The office runs voip, now i'm told i have to get phones to the workers<br>
>> > because the <lots of explicit words> AKA previous owners of that<br>
>> > business stopped the build when they ran into financial problems.<br>
>> ><br>
>> > So my plan is to utilize the existing many miles worth of copper pairs.<br>
>> ><br>
>> > I'm looking at throwing them into Versa Dslams that use pppoe pass<br>
>> > through, throw in a mikoTik 1036 as pppoe server, and we got spare<br>
>> > R710 i can use as radius server, and by my limited knowledge this<br>
>> > works.<br>
>> ><br>
>> > OK data done, but... now all those pots out lines need to go somewhere<br>
>> > that can handle 1700 or more lines, I am looking at either grandstream<br>
>> > 48 port FXS gateways or sangoma vega 50 ports (which Ill use as 48 so<br>
>> > theres a 1:1 match with dslams) the vega 3050 probably wont be used<br>
>> > because they are more than twice the price of grandstream.<br>
>> ><br>
>> > But this all results in a sh1te load of 48 port gateways (power is not<br>
>> > a concern), but wondering if there is another solution that is more<br>
>> > cost effective? Seems the regular NEC's Siemens and so on might have<br>
>> > an option but I can imagine it will be far more expensive than a bunch<br>
>> > of individual gateways.<br>
>> ><br>
>> > This project is in my mind workable, but i've not done such a thing on<br>
>> > a large scale.<br>
>> > Those who have experience in this field care to chime in? is my method<br>
>> > acceptable or not for such a project size?<br>
>> ><br>
>> > most pbx's I've done are only few hundred analogue lines where<br>
>> > gateways are more suited and definitely more cost effective, at all<br>
>> > our locations we use freepbx which works perfectly, and we know the<br>
>> > beefyness of the box we'll need to install to handle this load, thats<br>
>> > not a problem if we go down the gateway method.<br>
>> ><br>
>> > thoughts?<br>
>><br>
> --<br>
> Jeremy Austin<br>
> <a href="mailto:jhaustin@gmail.com" target="_blank" rel="noreferrer">jhaustin@gmail.com</a><br>
><br>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</body>
</html>