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.
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.
-mel beckman
On May 5, 2020, at 5:06 AM, Baldur Norddahl <baldur.norddahl@gmail.com> wrote:
Thinking out of the box, why not implement a WISP setup using wifi? This kind of gear is more accessible to normal IT staff.
Voice can be implemented by VoIP using Wifi too.
Regards
Baldur
The huts or cabins whatever you want to call them, are right behind
the admin building at entrance, so first is about 300 meters and the
furtherest is just under 1 mile
Cost will be an issue, Im sure I will have no problems if I have to
install a full rack of gateways and another full of dslams if it costs
150K, over something 1/5th the size in one rack that will cost 200k -
since the company is not charging them for internet or voice.
On 5/2/20, Jeremy Austin <jhaustin@gmail.com> wrote:
> What’s the average loop length? Grandstream is probably OK to 5+ kfeet but
> you will lose CID before that.
>
> As the low cost option don’t expect them to be trouble-free (or have
> particularly good vendor support), but they might work in your application
> if cheap is what makes sense.
>
> My $.02
>
> Jeremy Austin
>
> On Fri, May 1, 2020 at 10:11 PM Andrey Slastenov <a.slastenov@gmail.com>
> wrote:
>
>> Look at MSAN solution. Like Huawei UA5000 or similar solutions from other
>> vendors.
>>
>>
>> Regards,
>> Andrey
>>
>> > 2 мая 2020 г., в 07:21, Nick Edwards <nick.z.edwards@gmail.com>
>> написал(а):
>> >
>> > I'm looking at a new sister company we just took over, their remote
>> > village has 1700 analogue phone lines to the workers huts, but they go
>> > nowhere past the MDF.
>> >
>> > The office runs voip, now i'm told i have to get phones to the workers
>> > because the <lots of explicit words> AKA previous owners of that
>> > business stopped the build when they ran into financial problems.
>> >
>> > So my plan is to utilize the existing many miles worth of copper pairs.
>> >
>> > I'm looking at throwing them into Versa Dslams that use pppoe pass
>> > through, throw in a mikoTik 1036 as pppoe server, and we got spare
>> > R710 i can use as radius server, and by my limited knowledge this
>> > works.
>> >
>> > OK data done, but... now all those pots out lines need to go somewhere
>> > that can handle 1700 or more lines, I am looking at either grandstream
>> > 48 port FXS gateways or sangoma vega 50 ports (which Ill use as 48 so
>> > theres a 1:1 match with dslams) the vega 3050 probably wont be used
>> > because they are more than twice the price of grandstream.
>> >
>> > But this all results in a sh1te load of 48 port gateways (power is not
>> > a concern), but wondering if there is another solution that is more
>> > cost effective? Seems the regular NEC's Siemens and so on might have
>> > an option but I can imagine it will be far more expensive than a bunch
>> > of individual gateways.
>> >
>> > This project is in my mind workable, but i've not done such a thing on
>> > a large scale.
>> > Those who have experience in this field care to chime in? is my method
>> > acceptable or not for such a project size?
>> >
>> > most pbx's I've done are only few hundred analogue lines where
>> > gateways are more suited and definitely more cost effective, at all
>> > our locations we use freepbx which works perfectly, and we know the
>> > beefyness of the box we'll need to install to handle this load, thats
>> > not a problem if we go down the gateway method.
>> >
>> > thoughts?
>>
> --
> Jeremy Austin
> jhaustin@gmail.com
>