Action Nodes
In the figure below, is a portion of a call processing record fully expanded to illustrate the decision-making process from the top-level to the actions. In this case, a call received from a LATA identifier contained in the "values" field (820, 871, 884, 888) would result in following the next level node associated with this branch. In this case, the next-level node would be the “action” node. In the case of the “action” node, the values are no longer routing criteria. Rather, this field contains one or more actions to be taken given this route resolution. The example above shows that the route here would result in returning a set final treatment action to play an out-of-band announcement would be returned to the calling entity.
The following table contains all of the potential action node tags and a brief description of each.
| Action Type | |
| Action Type | Action Value |
| set_carrier | Carrier code |
| set_final_treatment |
Values:
|
| set_local_service_office | The Local Serving Office (LSO) is represented by NPA-NXX |
| set_network_management_class | Indicates the network management class threshold |
| set_routing | 10-digit routing number |
| npa_nxx_xxxx | 10-digit ANI (NPA-NXX-XXXX) |