Configuration CSV Files

The Oracle® Enterprise Session Border Controller (E-SBC) import feature uses the import and export SPL plug-in. You must use a spreadsheet application, such as MS-Excel, that supports .csv files.

The following rules apply when entering configuration data into the .csv file.

CSV Configuration Import Rules
Empty lines are ignored
The first non-empty line must be the keyword “object:”, followed by the configuration object name that is being configured (shown below as sip-interface).
Example: object:sip-interface
The second non-empty line must be the parameter names of the objects to be configured, each parameter name in its own column. This row defines the labels for each column for the subsequent rows. Only the attributes that you want defined need to be present. You can specify the parameter names in any order, but the data in subsequent rows must be consistent with the labels that you define in this row.
Example: state,realm-id,description
The third non-empty rows define values for the configuration object, each instance in its own column. In the following example, the third line defines a new sip-interface with state “enabled”, realm-id “public”, and description “public SIP interface”. These values are based on the labels defined in the second row.
Example: enabled,public,public SIP interface
Note that the Description field displays all text as one continuous line, unless you insert line breaks. When you want to insert line breaks in the Description field, for example between sentences that you want displayed on separate lines, do the following:
  • From the GUI, in the Description field of a Configuration object, add Line1 to the end of the line where you want the first break to occur. Add Line2 to the end of the next line where you want a break to occur, and so on.
  • In a .csv configuration file, add \010 to the end of the line where you want the first break to occur. Add \010 to the end of the next line where you want a break to occur.
On all subsequent rows, you can define any number of instances.
The next row with an “object” keyword selects a new configuration object that is based on the previous object. You continue to input the data for this object according to the rules stated above. The following example shows a “sip-port” object added that is related to the sip-interface object.
Example: object:sip-port
         address,port,transport-protocol 
         192.168.1.1,5060,UDP 
         192.168.1.1,5061,TCP 

In the example above, “sip-port” is a sub-object of “sip-interface” and would create new sip-ports off of the last sip-interface instance (of realm-id public).