Import and Export Restrictions

The following table lists the restrictions that the system enforces when importing and exporting the Oracle® Enterprise Session Border Controller (E-SBC) configuration.

Import and Export Restrictions
Files are read/written to the volatile directory of the file system on the E-SBC.
Import and export occurs to and from the editing configuration.
The system displays all error messages on the screen where the command was issued and provides line numbers with the error, when possible. The system does not allow you to set objects and attributes to inappropriate values. For example, you cannot set an IP address to "enabled". Parsing continues as normal after this error. If the system cannot write an object, for example, when the key field is missing, the system discards the object and parsing continues as normal. The import is additive. Each object that is imported is expected to be new to the configuration. If there is already an object with the same key present, the system generates the 409 error and discards the object. Parsing continues as normal after the error.

Files are read/written to the volatile directory of the file system on the E-SBC.

Import and export occurs to and from the editing configuration.

The system displays all error messages on the screen where the command was issued and provides line numbers with the error, when possible.

The system does not allow you to set objects and attributes to inappropriate values. For example, you cannot set an IP address to "enabled". Parsing continues as normal after this error.

If the system cannot write an object, for example, when the key field is missing, the system discards the object and parsing continues as normal.

The import is additive. Each object that is imported is expected to be new to the configuration. If there is already an object with the same key present, the system generates the 409 error and discards the object. Parsing continues as normal after the error.