Reference11r1:PBX/Config/Import: Difference between revisions
Jump to navigation
Jump to search
(New page: With the import function a file containing PBX objects can be uploaded. With the XML format, the complete information of the PBX objects can be provided, with CSV only a subset of the comp...) |
mNo edit summary |
||
Line 1: | Line 1: | ||
With the import function a file containing PBX objects can be uploaded. With the XML format, the complete information of the PBX objects can be provided, with CSV only a subset of the complete | With the import function a file containing PBX objects can be uploaded. With the XML format, the complete information of the PBX objects can be provided, with CSV only a subset of the complete configuration is possible. | ||
== CSV == | == CSV == |
Revision as of 10:58, 15 August 2014
With the import function a file containing PBX objects can be uploaded. With the XML format, the complete information of the PBX objects can be provided, with CSV only a subset of the complete configuration is possible.
CSV
If a row starts with '&' in the first field, it is assumed, that this is a row, which defines the content of the columns of the following rows. The following definitions are available.
- &n
- Long Name
- &h323
- Name
- &e164
- Number
- &dn
- Display name
- &node
- Node
- &pbx
- PBX
- &config
- Config Template Name
- pseudo/&type
- Type of a pseudo object (e.g. trunk)
- &pwd
- Password
- grp/&name
- Group name
- grp/&mode
- Group mode
- device/&hw
- Device hardware id
- device/&text
- Device text
By default, the following definution is used:
&cn; &h323; &e164; &config; &node; &pbx; pseudo/&type; &pwd; grp/&name; grp/&mode; device/&hw; device/&text