Model just released has 802.11b/g/n with 2 external antennas, but yes
includes VoIP.
I don't see a user guide on the Cambium website. I may have to order one
and play with it. We currently use Cisco ATAs in bridge mode ahead of the
customer router and give them a private IP completely separate from the
router. I'm not clear on whether this device will work in a similar manner.
Also our managed CPE routers are all Mikrotik and remotely managed via
Winbox, I assume this is probably OpenWRT based, we have had nothing but bad
experiences with every brand of home routers and I would approach any new
device with skepticism. You often don’t know you've deployed a bunch of
crap routers for a year or more when they start failing.
That said, consolidating the POE, router and ATA functions in one box would
simplify the rats nest of wires. And the industry is moving toward ISPs
providing a WiFi router, DSL and cable is pretty much all that way.
If everything else was good, and the price was right, I guess I wouldn't
sweat every customer having a phone jack on their "modem" even if 95% didn't
use it. Could save a future truck roll. Assuming remote management.
Depends on how much cost it adds.
-----Original Message-----
From: Matt
Sent: Friday, June 05, 2015 11:43 AM
To: [email protected]
Subject: Re: [AFMUG] Cambium discontinuing the traditional wall wart
powersupply
Mark, I guess you could look at the C3VOIP200 since it includes
Canopy/ePMP
compatible POE on the WAN port.
I so wish they made a version of it with WIFI and without VOIP.
"Find the thin wire coming off the 1” block and follow that to the power
supply."
9/10 times, the customer will argue with me that it doesn't run to
anything because they can't find it in their mess of wires. Or that it
runs to their router (because the Router power cord looks the same size)
On 6/5/2015 10:27 AM, Mark Radabaugh wrote:
Interesting. I always found it pretty easy to troubleshoot.
On the back of the router find the 3” long flat black cable that goes
into
a 1” square black box. Is it plugged into the WAN port on the router?
Oh -
you plugged that flat black cord into the wall jack? Swap the ends - the
flat black cord goes in the router. Find the cord plugged into the 1”
box
and follow that to the wall jack. Is it plugged in securely at both
ends?
Find the thin wire coming off the 1” block and follow that to the power
supply. Is it plugged in and the green light on? No? Plug it in. If
the
green light is on unplug the power supply and tell me if the light goes
out
right away. It fades away slowly? Then there is a break in the wire
between the power supply and the equipment outside? Oh - your husband
wacked that wire with his hedge trimmer? Yeah - that might possibly be
the
problem.
Mark
On Jun 5, 2015, at 11:10 AM, Nate Burke <[email protected]> wrote:
We've been using the Tycon's for quite a while as well. We found it
next
to impossible to trouble shoot the Cambium power supply with a customer.
They could never comprehend what it was, and always tried to plug in a
PC to
the POE Jumper. The Tycon's are nice, because you can describe the
white
box, with 2 plugs on one side (AC and LAN), and one plug on the other
(poe).
Is there a yellow or green light, The Cable from outside plugs into the
end
with only 1 plug.
On 6/5/2015 9:50 AM, Ken Hohhof wrote:
I never used it anyway, prefer Tycon POE-24iR-CI. And yes, a patch
cord, but those come in various lengths and colors rather than the
short
little stub which is limiting.
-----Original Message----- From: Mark Radabaugh
Sent: Friday, June 05, 2015 9:37 AM
To: [email protected]
Subject: [AFMUG] Cambium discontinuing the traditional wall wart power
supply
So is anyone else unhappy with Cambium’s decision to EOL the
traditional
power supply?
The replacement part is a Ubiquiti or ePMP brick style. It costs
more,
does not include the power cord, and requires an additional CAT5 jumper
cable.
While the current supply has it’s issues (hard to plug into a power
strip) it’s simple to troubleshoot over the phone with a customer with
limited ways to screw it up. I think this is going to create more
‘miswire’ service calls.
Mark