cDVR Quick Start Guide, Release 1.4

Transcription

cDVR Quick Start Guide, Release 1.4
This Guide
The cDVR Quick Start Guide provides end to end setup steps for Release 1.4 of Imagine Communications’ cDVR solution.
What is cDVR?
Imagine Communications’ cloud DVR (cDVR) solution is a software based, cloud enabled system that provides end-to-end video
recording delivery using the service provider’s own data center or a hosted private cloud. Key features of cDVR Release 1.4 include: event based recordings, continuous record; private asset and shared asset copy; operator or user scheduling of recordings;
support for Catch-up TV, Time-shift, Hot Record; and support for fast-forward, resume, and sliding window playback modes.
Terminology
Below is a list of terminology used for cDVR in general and acronyms used in this guide.
cDVR — Network Digital or Personal Video Recording; allows a subscriber to create personal recordings in the network or cloud
StartOver — Allows a subscriber to view a current broadcast event from the beginning
TimeShift — Allows a subscriber to scroll back in time to view an event that occurred some hours (usually 6 to 8) prior
CatchUp — Allows a subscriber to watch content that has already aired and has been marked by the operator as hot content
Acronyms
CR — Continuous Record
JITP/Stitcher — JITP with Stitcher capability
EBR — Event Based Recording
RM — Telurio Recording Manager
EPG — Electronic Programming Guide
TAP — Telurio Packager
JITP — Just in time Packaging
VM — Virtual Machine
Imagine Communications’ cDVR Components
Three components comprise the cDVR 1.4 solution:

TelurioTM Recording Manager — a GUI-based application that provides a RESTful set of APIs in order for middleware to
schedule and playback recordings;

TelurioTM Packager as Recorder — a TAP licensed for recording MBR IDR aligned streams, which creates HLSv4 mezzanine
format for delivery to a JITP-ready TAP;

TelurioTM Packager as JITP (and Stitcher) — a TAP licensed for JITP and, in the case of continuous recording, manifest
stitching. The JITP server creates ABR-ready chunks for either event based or continuous recording. For CR, the Stitcher
function then creates virtual assets by producing a manifest/playlist from the correct set of fragmented CR files.
Additional components not provided in the Imagine Communications’ cDVR solution, but required for cDVR in general are described on the next page.
Network Architecture
Installation Overview
Additional Equipment
To deploy the cDVR solution in your network, you should have the following equipment in addition to Imagine Communications’
cDVR components:






Middleware Scheduler—application (3rd party) that sits between EPG and RM. Uses RM API to manage user initiated schedules.
Digital Rights Management (DRM) server—encrypts streams for secure delivery.
Video Transcoder—ingests content, prepares audio and video assets for segmentation; can be SelenioTM VMG, TAT, or 3rd party.
Mezzanine Storage—Storage server for HLS mezzanine files generated by Recorder. Can be NFS, GPFS or Object Storage format.
Content Delivery Network (CDN)—aggregation of storage and cache servers that contains content for video providers.
Clients—end user device that subscribes to and receives video content via set-top box, computer, or mobile device.
Requirements
For installation and setup, you should be familiar with VM partitioning and you should understand how to use Linux tools.
cDVR Hardware
cDVR Software
The hardware on which cDVR software runs should comply to
or exceed these standards for each virtualized instance:
The following software is included in your order and required
for installation. Please contact Imagine Communications if any
component is missing:
CPU Core
3 Cores per VM
CentOS 6.6 (25456)
Available on DVD or ISO
TA RM (1+1)
64 GB HD / 10 GB RAM
Recording Mgr.
RM 1.4 .rampx executable file
TAP Recorder (1+1)
Recorder (Packager)
TAP 5.7 .rampx executable file
TAP JITP/Stitcher (1+n)
JIT Packager
TAP 5.7 .rampx executable file
Steps at a Glance
x2
Install CentOS
Install
Teluriotm RM
xn
x2
Install JITP
(Teluriotm Packager)
Install Recorder
(Teluriotm Packager)
*OS, RM, & Packager software images available via ftp download from Imagine Communications Customer Support
© 2015 Imagine Communications Corp. | All Rights reserved
250-0340-01, Rev A | cDVR Quick Start, Release 1.4 | printed 05-18-2015
2
http://www.imaginecommunications.com
Support Tel: 877-RGB-NETW
Setup Steps - Installation
1 Install CentOS on all VMs
The RM, Recorder, & JITP run on CentOS* 6.6 as shown in Table 1.
Table 1: CentOS Installation
a)
Obtain the CentOS ISO image; it will be named as shown in
Table 1.
CentOS ISO File Name:
b)
Burn the ISO image to a DVD
–or–
Mount the ISO image to a drive accessible by the VM.
c)
Install automatically begins when the DVD is inserted or the
ISO is mounted.
d)
Use Linux tools to configure a static IP address, subnet mask,
DNS, default gateway, and host name.
e)
Repeat c) and d) for each RM, Recorder, and JITP.
osdvd-5.0-CENTOS66-25456.iso
*Note: If you are using another Linux-based OS besides CentOS (such as RHEL),
please contact Imagine Communications Customer Support for additional help.
2
Install RM Application
CentOS must be running on the target RM VM (see Step #1).
a)
Obtain the RM .rampx executable named as shown in Table 2.
Table 2: RM Installation
b)
Log in as root.
c)
Copy the .rampx file to the target RM VM.
RM File
Name*:
rm-1.4.x-yyyyyzzzzz.rgb.x86_64.rampx
chmod
command
chmod +x [filename].rampx
You may copy the file to any location except
the /tmp/ramp or /tmp/ruf directories.
d)
Change the .rampx file permissions to make it executable as
shown in Table 2.
e)
Execute the .rampx file as shown in Table 2.
f)
Repeat b) through d) for the redundant RM (if applicable).
3
Execute
./[filename].rampx
command:
*Where x,y,z = the version and build number of software
Install Recorder Application
CentOS must be running on the Recorder VM (see Step #1).
a)
b)
Obtain the TAP .rampx executable named as shown in Table 3.
Log in as root.
c)
Copy the .rampx file to the target Recorder VM.
You may copy the file to any location except
the /tmp/ramp or /tmp/ruf directories.
d)
Change the .rampx permissions to make it executable.
e)
Execute the .rampx file as shown in Table 3.
f)
Repeat b) through e) for every Recorder instance.
Table 3: Recorder & JITP Installation
Recorder
ripcode-packager-5.7-xxxxx& JITP
xxxxx.rgb.x86_64.rampx
File Name:
chmod
command
4 Install JITP Application
Execute
./[filename].rampx
command:
CentOS must be running on the JITP VM (see Step #1). The JITP installation uses the same .rampx file as the Recorder.
a)
b)
c)
d)
chmod +x [filename].rampx
*Where x,y,z = the version and build number of software
Go to Step #3.
Perform steps a) through d)
Install the software on the JITP(s).
Repeat the above steps for every JITP instance.
3
Setup Steps - Licensing cDVR Components
Perform steps 5-10 via the GUI of each cDVR component as described on this page.
Prerequisite alert: You must have received and installed valid cDVR license keys (for both RMs & TAPs) for your cluster from Customer Services.
5 Log in to JITP GUI
a)
Open a web browser from a management computer that has
access to the JITP (which is a Packager).
b)
Navigate to the physical IP address of JITP.
c)
Log in with the credentials: admin/ripcode!
6 Set & Test JITP License
Step #6: a) - d)
a)
Click the System tab.
b)
Click through to the sysconfig >> license >> server >> set tree.
c)
Enter “localhost” as the license Server Address to use.
d)
Click Submit to save the license server information.
e)
Enter your license key (copy & paste) in the License File URL field
in the sysconfig >> license >> update menu; click Submit to save.
f)
Test the license server by clicking through the
sysconfig >> license >> test, tree, selecting acquire-release, and
clicking Submit.
g)
Repeat steps a) through f) for each additional JITP server in the
cDVR cluster, logging into the GUI of each server’s IP address.
Step #6: e)
Step #6: f)
7 Log in to Recorder GUI
Perform steps a) through c) as described in Step #5 above
using Recorder’s IP address instead of JITP/Stitcher.
8 Set & Test Recorder License Server
Perform steps a) through g) as described in Step #6 above using
Recorder’s IP address and credentials instead of JITP.
9 Log in to Recording Manager GUI
a)
Open a Chrome web browser with access to the RM.
b)
Navigate to the physical IP address of the RM.
c)
10 Set RM License
a)
Click the SYSTEM tab.
b)
Click through to the Licensing > Server menu tree.
c)
Click
d)
Enter the IP address of your license server (or use “localhost”)
under Active Server and click Submit to save server information.
e)
Click through to the Licensing > Update menu tree.
f)
Click
g)
Enter your license key (copy & paste) in the URL field and click
Submit to save.
to modify the license server.
to modify the license key.
For Redundancy, complete these additional steps:
e)
Login to standby RM’s IP address as described in Step #9.
a)
Repeat steps a) through e) of this Step #10 for the backup RM.
Step #10: e) - g)
*Note: When configuring redundant RM’s to use localhost for their license server, the
Primary RM’s IP should be configured as the active server on the primary RM, and the
Backup RM’s IP should be configured on the backup RM. The software will do the rest.
4
Setup Steps - RM Redundancy
Step Requirement: The steps on this page are only required if you are using RM Redundancy.
Alert! Perform steps 11-14 via the GUI of only the Primary RM.
Note: The sample IP addresses listed in Table 4 are used to illustrate these steps.
Table 4: Sample IP addresses
10.32.128.216
Primary RM Physical IP
Standby RM Physical IP
10.32.128.217
Virtual IP used for RMs
10.32.128.215
11 Log in to Desired Primary RM GUI
a)
Open a Chrome web browser from a management computer
that has access to the Recording Manager.
b)
Navigate to the physical IP address of the RM that will start
as the primary.
c)
12 Configure Redundancy Group Details
a)
Click the SYSTEM tab.
b)
Click through to the Redundancy > Group menu tree.
c)
Click
to modify the redundancy group details.
The Group Type & Product Type fields will be preselected with
1+1 and RAPS respectively.
e)
Enter the Virtual IP address that will be assigned to both the
Primary and Standby RMs.
f)
Click Submit to save and add the redundancy group.
g)
Confirm the Connection Status icon in the top right corner of the
GUI changes from red
to green
(response time should be
less than a minute).
13 Add Standby Host
a)
Click through to the Redundancy > Hosts menu tree.
b)
Click
to add the Standby host (the Primary host entry will
already be present).
c)
Enter the Standby’s physical Host IP address.
d)
Select Standby as the Host Type.
e)
Click Submit to save and add the Standby RM to the redundancy
group*.
*Note: The Host State on the Standby RM will start out in “Recovery” mode, but
after a few moments it will switch to “Idle.”
14 Verify Redundancy
a)
Click through to the Redundancy > Group menu tree.
b)
Verify the host_type and host_state for the Primary RM show
Active/Active as their entries.
c)
Verify the host_type and host_state for the Standby RM show
Standby/Idle as their entries.
Note: Once you have configured and verified redundancy,
all further RM configuration should be performed from the
Virtual IP address of the redundant pair.
5
Setup Steps - Recording Manager
Perform these steps via the Configuration tab of the RM GUI
(log in described in Step #9). If using redundancy, log in using
the Virtual IP. This release supports a Chrome web browser.
Organization of the GUI is in a tab-to-container fashion where
main tabs drill down to sub-categories.
15 Add Transcoder(s)
a)
Click the NODES tab.
b)
Click the Transcoders container to expand.
c)
Click the plus (“+”) icon to add a new transcoder.
d)
Enter a desired Name for the transcoder that cDVR will use.
e)
Enter the IP Address of the transcoder.
f)
Choose whether the transcoder is a VMG, SelenioTAT, or
Other from the Type drop-down menu.
g)
Click Submit to save and add the transcoder.
h)
Click “+” to add additional transcoders.
Transcoder ingests content, prepares
audio and video assets for segmentation
Result
16 Add JITP Server(s)
a)
b)
Click the JIT Packagers container to expand.
c)
Click the plus (“+”) icon to add a new JITP.
d)
Enter a desired Name for the Packager that cDVR will use for
JITP (and Stitcher for CR).
e)
Enter the IP Address of the JITP.
f)
Click Submit to save and add the JITP*.
g)
Click “+” to add additional JITP(s).
JITP creates ABR-ready chunks for event
based or CR. When stitching is used, it creates a manifest/playlist from the fragmented
chunks for CR only.
Result
*Note: When saving a new JITP/Stitcher, the RM will cause the JITP to reset its
database. This process may take a few minutes.
16a
Configure JITP for HLSv4 (optional)
JITP uses HLSv2 as its default output HLS format. To use HLSv4
on the JITP, proceed as follows:
a)
Login to the GUI of the JITP server(s). (Step #5)
b)
Click the Configuration tab and click through to:
configuration >> output >> format >> hls >> modify.
c)
Select 4 as the Version.
d)
Click Submit to save changes.
e)
Go back to the RM GUI and proceed to the next step.
17 Add Storage Server(s)
a)
b)
Click the Storage Mounts container to expand.
c)
Click the plus (“+”) icon to add a new storage mount.
d)
Enter a desired Name to use for mezzanine storage.
Storage Mounts
1.
For NFS, enter the URL (the Hostname/IP and Share Name
Path) where cDVR will create its mezzanine directory.
2.
For NFS HTTP access, enter the Origin Base URL .
-ORFor NFS Direct access, leave the Origin Base URL blank.
e)
Choose whether to use NFS or GPFS* as the Storage Type.
f)
Click Submit to save and add the Storage Mount.
g)
Click “+” to add additional Storage Mounts.
An NFS, GPFS, or object storage server is
where the HLS mezzanine files generated by
Recorder are stored.
Result
*Note: For GPFS, refer to the cDVR User Guide for additional CLI procedures on the RM.
6
Setup Steps - Recording Manager (Cont’d)
18 Add Recorder(s)
a)
b)
Click the Recorders container to expand.
c)
Click plus (“+”) icon to add a new Recorder.
d)
Enter a desired Name for the Recorder that RM will use.
e)
Select a mezzanine Storage server (as configured in Step #17)
from the drop-down list.
f)
Select HLSv4 as the HLS Version to use.
g)
Enter the Primary IP Address of the Recorder.
h)
Optionally enter the Redundant IP Address of a Recorder that
will provide redundancy protection* for mezzanine output.
i)
Click Submit to save and add the Recorder entry.
j)
Click “+” to add additional Recorder entries.
Recorder captures source streams and creates
the TAP mezzanine format for delivery to a
JITP-ready TAP.
Result
*Note: In the event of a Recorder failure, the backup Recorder begins to create
mezzanine output. Only one output at a time is delivered to the JITP server; the
redundant Recorders do not create duplicate mezzanine outputs at the same time.
19 Configure JITP & Recorder Key Server(s), optional
a)
Click the JITP/Recorder tab.
b)
Click the Key Server container to expand.
c)
Click plus (“+”) icon to add a new Key Server.
d)
Select the desired Key Server Vendor to be configured on the
JITP & Recorders from the drop-down menu.
e)
Enter the Key Server URL where the key server is running (for
Verimatrix HLS, Nagra, Verimatrix PlayReady, and KPN only).
f)
Enter the TCP Port Number on which the Key Server is running
(for Verimatrix HLS, Nagra, Verimatrix PlayReady, PlayReady
Leaf, and KPN only).
–or–
Leave the TCP Port Number set at the default of 0 if you are
using standard ports for http or https.
g)
Enter the User Name and Password to use (for KPN only).
h)
Enter the Client Key Request URL that the client players will use
to request encryption keys (for Internal PlayReady & PlayReady
Leaf only).
i)
Enter the Client Certificate that the client players will use (for
PlayReady Leaf only).
j)
Enter the Client Key that the client players will use (for PlayReady Leaf only).
k)
Enter the Client Key Password that the client players will use
(for PlayReady Leaf only).
l)
Enter the PlayReady Key Seed (for Internal PlayReady only).
A Key Server is used to encrypt packages between the JITP and the client players. This
setting is saved to all JITPs in the RM.
Result
m) Click Submit to save and add the Key Server.
n)
Click “+” to add additional Key Servers.
7
Setup Steps - Recording Manager (Cont’d)
20 Configure JITP & Recorder Audio Map(s)
a)
Click the JITP/RECORDER tab.
b)
Click the Audio Map container to expand.
c)
Click the plus (“+”) icon to add a new Audio Map.
d)
Enter a Name for the audio map template and click Submit.
e)
Click “+” for the desired Name to add a new audio map rule.
f)
Select the Priority position in which this rule will be run.
g)
Select the input Audio Codec to which this rule will apply.
h)
Select the input Audio Channel to which this rule will apply.
i)
Enter, in the Bitrate Low field, the required minimum bitrate of
the input audio to which this rule will apply.
j)
Enter, in the Bitrate High field, the maximum bitrate of the input audio to which this rule will apply.
k)
Enter the 3-letter Language acronym of the input audio to
which this rule will apply (any is a valid option).
l)
Select the output Publishing Type action* that will occur if this
rule is met.
An Audio Map template consists of a set of
rules that specify how input audio tracks will
be handled in the output.
Result
Result
m) Click Submit to save and add the audio map rule.
n)
Click “+” under the audio map Name to add additional rules.
o)
Click “+” under the Audio Map container to add additional
audio map templates.
*Note: For a detailed description of audio map Publishing Type outputs for various
players, refer to the cDVR User Guide.
Upon saving, the Audio Map settings specified here are pushed to each JITP
and Recorder being managed by this RM.
21 Configure JITP Profile(s)
a)
Click the JITP/RECORDER tab.
b)
Click the Profile container to expand.
c)
Click the plus (“+”) icon to add a new JITP profile.
d)
Enter a Name for the JITP profile.
e)
Enter the number of seconds that each video/audio Segment
Duration will be for each player Type.
f)
Select the applicable Key Server to use for each player.
g)
Enter the Key Rotation (in minutes), which will define how often
the encryption key will be renewed. Optional setting.
h)
Select the Audio Map template that will be applied for each
player.
i)
Select the true option under the Allowed column next to each
player based on whether JIT packaging will be performed.
j)
Click Submit to save the new profile template to all JITP servers.
k)
Click “+” to add additional JITP profile templates.
8
A JITP Profile is used to specify whether the JIT packager will support a
particular player and how that player handles the output format.
Result
Setup Steps - Recording Manager
22 Configure JITP Source Server
a)
Click the JITP/Recorders tab.
b)
Click the Source Server container to expand.
c)
Click the plus (“+”) icon to add a new JITP source server.
d)
Enter a source server Pattern* that will map to the valid hostname or directory of the source server.
e)
Select the JITP Profile to use for this source server.
f)
Select the mezzanine Storage server to use (for EBR and unique
recording only).
g)
Select which Recording Type this source server will use
(Continuous, Event Based, or Unique Asset).
h)
Click Submit to save source server settings to all JITP servers.
i)
Click “+” to add additional JITP source servers.
Configuring a JITP Source Server maps the
JITP server to a Storage Mount.
Result
*Note: Do not enter the JITP’s management hostname or IP address.
23 Create Channels
a)
Click the Channels tab.
b)
Click the plus (“+”) icon to add a new channel.
c)
Enter a desired channel Name.
d)
Select the Transcoder on which this channel exists.
e)
Enter the MBR/Group ID of the Transcoder. Optional setting.
f)
Click Submit to save and add the channel.
g)
Click the Streams button to open the Streams menu.
h)
Click “+” to add a new stream, and then:
Creating a channel sets the recording path
from the RM to the channel origin.
1.
Enter the IP Address of the stream.
2.
Enter the Port Number over which the stream is being sent.
3.
Enter the Published Video Bitrate of the stream. An entry of
0 will autodetect the bitrate.
4.
Select True to indicate the stream is Enabled.
5.
Click Submit to save and add the stream.
i)
Repeat step h) for each additional stream to be added to the
channel.
j)
Click the Close button to close the Streams menu.
k)
Repeat steps b) - j) to add additional channels and streams.
Step #23 a) - g)
Step h) #’s 1-5
24 Schedule a Recording
a)
Click the SCHEDULES tab.
b)
Click the plus (“+”) icon to add a new recording schedule.
c)
Select whether to use a Channel (UDP-based) stream or a URL
(HLS v2-based) stream as the Input Type.
d)
Select a Channel or Input URL to use for the recording.
e)
Select the Recorder that will create the mezzanine format for
delivery to the JITP/Stitcher.
9
The Scheduler allows you to create scheduling for both Continuous and
Event based recording.
Scheduling Steps - Recording Manager
(Continued from previous section)
f)
Enter the Name (path) of the directory and path to create on
the mezzanine storage server linked to the Recorder.
g)
Select the output Package Type to schedule. For CR, select Continuous Record; for Event Based, select a desired output
format.
h)
Select a desired Audio Map to use for the output.
i)
Click in the Start Time field to bring up a calendar, or enter a
date and time in this format: mm/dd/yyyy hh:mm:ss.
Leave field blank for recording to start immediately.
TIP: Click the highlighted date to automatically enter the current time.
j)
Click in the End Time field to bring up a calendar, or enter a
date and time in this format: mm/dd/yyyy hh:mm:ss.
Leave field blank to record indefinitely.
k)
Enter the desired number of minutes for each recorded segment directory in the Segment Dir Size* field.
l)
Enter how many days the recording will be kept if no corresponding assets have been created in the Max. Unreferenced
Storage (days)* field.
m) Enter a Content ID for the schedule (optional).
n)
Select a Key Server Vendor to use for encrypting this channel.
Optional setting.
o)
Enter the Key Rotation (in minutes), which will define how often
the encryption key will be renewed. Optional setting.
p)
Click Submit to save the schedule configuration.
q)
Click “+” to schedule additional recordings.
Result
*Note: This field applies to CR only. To use global defaults, leave blank.
25 Create an Asset (Required for CR Only)
a)
Click the ASSETS tab.
b)
Click the plus (“+”) icon to add a new asset.
c)
Enter an Asset Key name for the asset you wish to create.
d)
Select the Schedule from which the asset will be created.
e)
Click in the Start Time field to bring up a scheduling calendar
and enter a date in the format as described in Step 24.
In order for the JITP server to create a manifest for continuous recording, an
TIP: Click the highlighted date to automatically enter the current time.
f)
Click in the End Time field to bring up a scheduling calendar
and enter a date in the format as described in Step 24.
g)
Enter the Content ID for the keyserver tied to the channel, if
applicable (some keyservers require this).
h)
Select whether the Asset Type will be SHARED or UNIQUE.
i)
Enter, in the Asset Max Age field, the number of days the asset
will be stored on the server.
j)
Click Submit to save the asset configuration.
k)
Click “+” to create additional assets.
10
Result
Viewing Recordings - Recording Manager
HTTP Access
26 View Event Based Recordings
a)
Click the Event Based Recordings tab.
b)
Use the link provided:
These links can be copied and pasted directly (as long as no Mezzanine encryption is used), or the links can be played through the JITP
server as shown below.
 For links with HTTP
in the URL (and no Mezzanine encryption), the URL provided in the tab can be used as is.
 For links with NFS
in the URL (or with Mezzanine encryption),
the URL can be viewed from the JITP server, and the link must
be modified as follows:
The Event Based Recordings tab shows only EBRs, not CR.
http://cDVR221-ebrweb.cslab.rgbnetworks.com/ebr-http/index.m3u8
http://[JITP Source Server Pattern]/[schedule
name]/index.[manifest type]*
c)
View the content in a compatible player.
d)
Be happy.
*Note: when using MSS as an output format, a “/Manifest” must be
Direct NFS Access
added to the “index.ism” portion as follows: index.ism/Manifest
This link (and any HTTP link using Mezzanine
encryption) must be modified as shown below
http://cDVR-jitp3.lab.ripcode.com/dec22/testeb1/index.m3u8
27 View CR Recordings
a)
Click the ASSETS tab.
b)
Use the link provided to formulate a playback link using the options below:
 For links where no Mezzanine encryption is used and HLS is
the desired output format, one of two options is available:
Click the relevant link as shown in the ASSETS tab*
-Orhttp://[JITP Source Server Pattern]/[Asset
Key].[manifest type]
 For links where Mezzanine encryption is used, the following
format must be used:
The ASSETS tab shows information about Continuous Record assets, not EBR.
To view the “NewAsset2” asset (no Mezzanine encryption), the link would look like one of
these:
http://<Stitcher IP address>/stitcher.fcgi/cr-test.m3u8
-orhttp://cDVR-stitcher3.lab.ripcode.com/NewAsset2.m3u8
http://[JITP Source Server Pattern]/[Asset
Key].[manifest type]**
c)
View the content in a compatible player.
d)
Be happy.
*Note: when content is recorded using direct NFS access instead of HTTP
access, you must formulate the link using the JITP source server pattern.
**Note: when using MSS as an output format, a “/Manifest” must be
added to the “index.ism” portion as follows: index.ism/Manifest
11

cDVR Quick Start Guide, Release 1.4

Transcription

Similar documents

Between Graduation and Orientation:

AVR 8345

Marantz Modification

BP125 Time Recorder

Monster Jobs - by Carpe Data

Biography Kulayd - hotspotentertainmentstudios

13/08/2012

1. Go to ezlm.adp.com and click the

Brochure - Commercial Systems Group

Manual - Deluxe Stitcher

Lamerholm RD298 ShockLog User Manual