Reference11r1:PBX/Config/Import: Difference between revisions
(→XML) |
(→CSV) |
||
Line 15: | Line 15: | ||
File should be saved in format utf-8 (BOM should be present) or latin-1. | File should be saved in format utf-8 (BOM should be present) or latin-1. | ||
;& | ;&n: Long Name | ||
;&h323: Name | ;&h323: Name | ||
;&e164: Number | ;&e164: Number |
Revision as of 16:55, 24 May 2017
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.
XML
Any imported XML file needs to contain xml header plus data must be inside the tags <info></info>, often when we edit exported XML files this is deleted and then the import fails.
<?xml version="1.0" encoding="utf-8"?><info> <user cn="BYU_Fax_223" e164="**28223" h323="BYU_Fax_223" text="Umleitung Faxbox zu Fax Service" loc="PBX-Bayreuth" node="PBX-Bayreuth" hide="true"><pseudo type="map"><match><dest e164="226"/></match></pseudo></user> </info>
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.
File should be saved in format utf-8 (BOM should be present) or latin-1.
- &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 definition is used:
&cn; &h323; &e164; &config; &node; &pbx; pseudo/&type; &pwd; grp/&name; grp/&mode; device/&hw; device/&text