On Jan 13, 6:20 pm, Stefan Monnier <monn...@iro.umontreal.ca> wrote:
> > My Linux server is across the ocean, behind a firewall and I have to
> > provision some IP phones, so the *temporary* solution (until I get a
> > decent server as God intended) is to install an FTP server in my
> > Windows laptop.
>
> I have no idea what is "provisioning" nor why that requires an FTP
> server, but I have still have some suggestions which I hope you'll find
> useful:
High end IP phones, such as those made by Polycom, cannot work
properly by themselves. They need a "boot server" -for configuration,
firmware upgrades, logging, even to place a company logo in their
display- which can be:
FTP
FTP(S)
The first one is a piece of cake. Anyone can do plain text FTP
provisioning. Now I want to make sure that I can provision those
phones in a more secure (i.e., encrypted + certs) manner.
I am taking the letters "FTP(S)" verbatin from the IP phone display.
My first question is: "what exactly do they (Polycom engineers) mean
by "FTP(S)"?
Which of these protocols (or subvariations) are supported?
http://patriot.net/~ramon/Secure-FTPs.png
What port(s) are involved?
Eventually the boot server will be Linux, but for the time being I
just need a quick solution, which is to install an FTP in my Windows
laptop.
After trying several, I have decided to use FileZilla, with warts and
all.
-Ramon