Exporting

The SIP manipulation configuration contains an export command. When you use it, the Oracle® Enterprise Session Border Controller sends the configuration you have selected to a designated file. The contents are the same information you see when you use the ACLI show command in XML format; it includes the selected configuration and any changes that have been made. Because you can only export one SIP manipulation configuration at a time, you must export each one-by-one if you need more than one.

The file name can be any you selected, and would be most useful if it were to identify its contents in some way. If the file already exists, then the export fails and informs you the file already exists. A successfully-executed export simply returns you to the system prompt.

The system writes exported files to /code/imports, a new location that will be created to avoid overlap with existing backup files. The files will carry the extension .gz to show that they have been compressed with gzip.

Your export data will look like this sample:

<?xml version='1.0' standalone='yes'?>
<sipManipulation
        name='manip'
        description=''
        lastModifiedBy='admin@console'
        lastModifiedDate='2009-10-16 14:16:29'>
        <headerRule
                headerName='Foo'
                msgType='any'
                name='headerRule'
                action='manipulate'
                cmpType='boolean'
                matchValue='$REGEX("[bB][A-Za-z]{2}")'
                newValue='foo'
                methods='INVITE'>
        </headerRule>
</sipManipulation>

To avoid conflict with other objects on the system, key and object ID are not included as part of the exported XML.