Note:
Make sure to download the exported file in the web interface without log out the CLI system.
Once log out the CLI system, the file will be deleted.
Note:
For importing data, the system only adds the new records or updates the existed records. If
there is any dependency error, the import action will stop and go back to the original status.
Note:
When exporting data, admin in User, UG_DEF in Usergroup and RG_DEF in Routgroup will not
be exported.
Style for CSV file
This section displays the CSV file style that can import to CLI system. Each item will have two
paragraphs. The first paragraph is field name, and the second one is an example. Note that
comma (,) is required at the end of each line, and it is suggested to use UNIX text file format.
Note:
As comma (,) is used for separating each data, avoid using comma including comma
within quotation (“,”) in each data.
Note:
When importing, Route and Routegroup will be imported together. As a consequence,
they must be in the same CSV file. The same situation also applies to IP phone and
extension of IP phone.
Note:
Some items are related to others, such as Reachable Usergroup in Usergroup, Usergroup
in User and so on. When importing an item that the related items do not exist in the
system, the system will show the error message and the imported item will be incomplete.
User
#Tag,UserID,Name,Password,Usergroup,Attach,Description,Email,
$User,user_01,AAA,111,UG_01,yes,I am user_01,[email protected],
Usergroup
#Tag,GroupID,Features,RouteGroup;Trunk;GroupID;Weight,ReachableUG,Desc
ription,PassEnable,Passcode,
$UG_Data,UG_01,mm,3301g;7710;1;1|3301g;7710;1;2,UG_10|UG_09,ThisisUG_01,
Route
#Tag,Route_ID,Description,Number_Pattern,Stripped_Digits,Prefix,
$Route_s,331,331_out,331Z,4,3310,
120
