Configure Fraud Protection List Push Task Updates

You can add new Fraud Protection List (FPL) update tasks that are on-demand, scheduled, or automatic, and schedule a specific time to push them to associated southbound devices on which they are executed.

After an FPL push task is executed, it must be committed to unlock the targeted devices that are associated with the FPL push task. Only FPL push tasks with a status of Success, Failed, Aborted, AbortFailed, or CommitFailed can be committed. When an FPL push task is committed automatically or manually, all targeted devices associated with this FPL push task are unlocked and this FPL push task can no longer be modified or rolled back. You must create a new FPL push task to implement new changes.

Add a Fraud Protection List Push Task

You can schedule a specific time to push a Fraud Protection List (FPL) to its associated southbound devices by adding a push task.

1. Expand the Fraud Protection Manager slider and click Fraud protection list.
2. Click the Device association tab.
3. Below the FPL push tasks table, click Add.
4. In the Add FPL push task configuration pane, complete the following fields:

   Name field	The unique, user-specified name assigned to the push task that is an alpha-numeric value from 1 to 24 characters in length with no spaces.
   Task type drop-down list	Select from the following push task types: On demand— Start the task anytime. Schedule— Plan a specific time to start the task. Auto FDP—No user intervention required. FPL updates are pushed regularly to Oracle Communications Session Delivery Manager (SDM) from the Fraud Detection and Prevention (FDP) device. SDM reconciles these updates with the specified FPL and pushes the result after reconciliation to the device(s). If the reconciliation fails, then an error is logged. If the pass through status of the FPL push task is NotScheduled or Committed then the pass through push task is allowed to start immediately (the Start now status). If the pass through push task is running and FPL updates are sent to SDM at the same time, then SDM queues the FPL updates and waits until the push task is finished, at which time SDM reconciles with the queued FPL updates.
   FPL drop-down list	Select the Fraud Protection List (FPL) name that is applied to the device(s).
   Start date and time field	This option is available only if the Task type is Schedule. Select a start date for the push task is scheduled to start by clicking the calendar icon and specify time entries in the Time fields by selecting the hour, minute and second respectively by typing the numbers in the text box or using the arrows. Note: SDM validates the scheduled start time using server time. An error is displayed if the selected time is already past in the server time zone. SDM prevents scheduling less than 5 minutes from the current server time. You must account for time zone differences between the local (browser) time and the SDM server time when scheduling.
   Time zone info field	Displays the SDM server time zone. The Start Date and Time is interpreted based on this time zone, and the scheduled operation is executed accordingly.
   auto Commit checkbox	You can use this option if the Task type is On demand or Schedule only. If the Task type is set to Auto FDP, the auto commit function is on automatically and cannot be modified. When a push task completes, but is not committed, it retains a lock on all its targeted devices so that no other operations can be performed on them until the push task is successfully committed and its devices are unlocked. Check the check box to automatically commit the push task after the successful execution of the push task. If the check box is unchecked, you have to manually commit the push task. Refer to the Commit a Fraud Protection List Push Task Manually section for more information.

5. Below the Device group tasks table, click Manage.
6. In the Select Device dialog box, expand a device folder in the Managed devices table, select a device row, and click Add.

   The device, its network function and folder structure moves to the Targeted Devices table and the folder structure is collapsed.

   Note:

   A work order has the following limitations:

   • The device must be capable of using the telephony fraud feature.
   • A push task is limited to one platform and software version at a time.
   • In the case of an HA device pair, the FPL push task is applied to both devices.
   • All devices must have the same platform, software version, and same redundancy type (HA or standalone).

   Note:

   If you receive a Warning message that says the FPL file on the device you adding does not match the FPL that you are using for the push task, you must use Configuration Manager or the device ACLI to change the FPL file name on the device to match the FPL of your FPL push task in order for the FPL push task to be used with the device you are adding. Refer to the device documentation for more information about changing the FPL file name on the device.
7. Repeat the previous steps to add additional targeted devices. Up to twenty devices can be added to a push task.

   Note:

   Device filtering is applied after the first device is selected.
8. Click OK. The device(s) appear in the Device group tasks table, which displays the network function (NF) name and its device(s).
9. Click Apply.
10. In the success dialog box, click OK.
    The FPL push task that you specified appears in the FPL push tasks table.