Suppressed Nodes

Suppressed Nodes

N2FE will adhere to the nodes that are configured in the users assigned node feature groups. Any nodes that a user does not have access to will not be shown in the editor.

In some cases there are nodes that may be assigned to a customer that should not be shown in any situation, to aid with this N2FE allows for the configuration of suppressed nodes. Suppressed nodes will always be disabled regardless of their feature set assignment.

N2FE also supports the suppression of nodes at the CPE parsing level. This will outright disable node parsing and allow the fall back to other nodes that may support the same underlying CPE node.

N2FE Service Configuration

To suppress nodes N2FE must be configured to do so. In the main N2FE configuration file /etc/jarvis/n2fe.xml, within the suppressed_nodes parameter of the available-customer-feature-nodes plugin. Multiple suppressed nodes can be configured by comma separating the values.

<plugin
    dataset="available-customer-feature-nodes"
    access="__AdminRead,__AcsCustomerUser,__SnUser"
    module="GetCustomerFeatureNodes"
    add_headers="yes"
>
    <parameter
        name="suppressed_nodes"
        value="BreakoutDialing,SpeedDial"
    />
</plugin>

The suppressed nodes parameter must be provided. If left blank no nodes will be suppressed.

To support nodes at the CPE parsing level the CPE options can be altered:

<!-- CPE Parsing options. -->
<cpe_parse>
    ...
    <suppressed_nodes>
        <node>SuburbRouting</node>
    </suppressed_nodes>
    ...
</cpe_parse>

In the above example the SuburbRouting node will not be used when parsing a TableLookup node. Instead all TableLookup nodes will be parsed as the TableLookup node.

Nodes

The following nodes can be suppressed using their configuration value. The following values are allowed:

For information on the use of each of these nodes, please see the user guide.