NCast PR-HD - Manual (Page 48)

NCast Presentation Recorder Reference Manual
5.11.10. Set Port Number
Enter the server port number for the protocol in use.
5.11.11. Enable Anonymous Login
For FTP transfer the use of anonymous login does not require any credentials.
5.11.12. Set Username
The user account for the server.
5.11.13. Set Password
The password required for the user account
5.11.14. Set Upload Directory
The name of the directory where archives will be placed, which may be an absolute or relative name (from
the home directory of the account).
5.11.15. Upload Directory – Special Parameter
The upload directory name may include a special codes (%n) which will modify the directory name based on
the Channel number. For example, if the FTP upload directory path is written as:
pr-hd/Class-%n/archives
then for files completing a Channel 1 session the effective upload directory will be
pr-hd/Class-001/archives
and for files completing a Channel 2 session the effective upload directory will be
pr-hd/Class-002/archives
This provides for automatic placement of uploaded files into directories based on the channel number which
was used for recording. Changing directories based on Channel number may help ease the administration of
many incoming files being recorded and uploaded by a single Presentation Recorder.
Directory based access rights will automatically restrict viewers rights to the directory/channel for which they
are entitled.
5.11.16. Secure File Transfer Protocol
Secure FTP (SFTP) is supported with password and private key authorization. It will first try to use private
key and if it fails password authorization is used. Only SSH-2 protocol is supported. The private key should
be in Open SSH's SSH-2 format or PuTTY's SSH-2 format or ssh.com's SSH-2 format and can't be
password protected.
Use the “Upload Private Key” button to install the private key for this unit.
Secure retrieval of files is also possible through use of the HTTPS SSL encrypted interface, utilizing either
the standard web page or the scripts documented in Section 12.3 of the HTTP interface.
NCast Corporation Revision 2.2
Page 48