Call Server: Invalid Path or File Name

From DocWiki

Revision as of 18:53, 18 December 2009 by Docwikibot (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Invalid Path or File Name

Problem Summary Note: This is a Call Server issue that is found within the Video Media Server (VMS), which is a part of the Call Server.

Sometimes, a file is read from the VMS movies directory with a name that does not validate to the standard accepted character set. These files are marked with the "File could not be read" status.

Error Message File could not properly be read from the file system.
Possible Cause An invalid status for a media file stating that the "file could not be read", generally implies that the file has an invalid path or file name.
Recommended Action Verify and correct the path or file name.
Release Release 7.0(2)
Associated CDETS # None.
Possible Cause An invalid status for a video media file (that is a 3gp or an XML file) stating that the "file could not be properly read", generally implies that the file has an invalid file name or presents within an invalid path.
Recommended Action Verify and correct the path or file name.

The file names can contain alphanumeric characters, underscore, spaces, and the following special characters: !$&().,'-;@[]^_`{}~+=. File names cannot lead with a period (.) or a space.

Only path names with alphabetical, numeric, spaces, and !$&().,'-;@[]^_`{}~+= characters are permitted; path names cannot lead or end with a period (.) or a space.

Release Release 7.0(2)
Associated CDETS # None.

Rating: 0.0/5 (0 votes cast)

Personal tools