Upload a file using the upload token id, returns an error on failure (an exception will be thrown when using one of the Kaltura clients)
Chunks can be uploaded in parallel and they will be appended according to their resumeAt position.
A parallel upload session should have three stages:
A single upload with resume=false and finalChunk=false
Parallel upload requests each with resume=true,finalChunk=false and the expected resumetAt position.
If a chunk fails to upload it can be re-uploaded.
with resume=true, finalChunk=true and the expected resumeAt position. In case an UPLOAD_TOKEN_CANNOT_MATCH_EXPECTED_SIZE exception
has been returned (indicating not all of the chunks were appended yet) the final request can be retried.
object:KalturaUploadToken autoFinalize:integerEnum: NULL_VALUE [-1], FALSE_VALUE , TRUE_VALUE 
autoFinalize - Should the upload be finalized once the file size on disk matches the file size reproted when adding the upload token.
Creation date as Unix timestamp (In seconds)
Name of the file for the upload token, can be empty when the upload token is created and will be updated internally after the file is uploaded
File size in bytes, can be empty when the upload token is created and will be updated internally after the file is uploaded
Upload token unique ID
Partner ID of the upload token
status:integerEnum: PENDING , PARTIAL_UPLOAD , FULL_UPLOAD , CLOSED , TIMED_OUT , DELETED 
Status of the upload token
Last update date as Unix timestamp (In seconds)
Upload url - to explicitly determine to which domain to adress the uploadToken->upload call
Uploaded file size in bytes, can be used to identify how many bytes were uploaded before resuming
User id for the upload token