You are here: CSP Developer’s Guide: Overview > 9 Configuring the DSP-ONE Card > Single Message Deletion

Single Message Deletion

You can delete a single Recorded Announcement (RAN) without erasing all the RANs on a logical VRA SIMM.

RANs are stored in flash memory on logical VRA SIMMs that reside on the DSP-ONE card. When a RAN is downloaded to a logical VRA SIMM, the host assigns an ID to it.

Limitation

VRA SIMM flash memory file system Revision 0 does not allow Single Message Deletion. VRA SIMM flash memory file system Revision 1 is required. This revision is included in software release 8.20 (CI) or higher. However, even if you are using software release 8.20 (CI) or higher, you must still use the Recorded Announcement File System Convert (0x0118) message to change the file system.

DSP SIMM Alarms

The following alarms are documented in Chapter 1 of the API Reference, within the Alarm (0x00B9) message:

• Recorded Announcement File System Conversion Success (0x07)

• Recorded Announcement File System Conversion Failure (0x08)

• Recorded Announcement File System Timeout (0x09)

• Recorded Announcement Defragmentation Success (0x0B)

• Recorded Announcement Defragmentation Failure (0x0C)

• Recorded Announcement Single Deletion Complete (0x0D)

• Recorded Announcements Need Defragmentation (0x0E)

Invoking Single Message Deletion

To enable the Single Message Deletion feature, you must first convert the flash memory file system on each logical VRA SIMM to Revision 1. You must perform the conversion once for each logical VRA SIMM.

You must take the logical VRA SIMM out of service before converting the file system. Any RANs that are on the logical VRA SIMM at the time of conversion are saved to the new file system format. The conversion normally takes about three to five minutes, but will be faster if no RANs are on the logical VRA SIMM. An alarm is sent to indicate when the conversion is complete.

If the VRA SIMM flash file system has not been converted to the new Revision 1, the Recorded Announcement Single Delete (0x0117) message is NACKed (unless the RAN ID field is 0xFFFF). You can mix the new and the old flash file systems on a single DSP-ONE card, but only the VRA SIMMs with the new system will allow single message deletion.

Sequence

The order of the API messages to delete single messages is as follows. You need to perform this procedure only once for each SIMM:

Determine and change the file system:

1. Determine the flash file system Revision on a VRA SIMM by using Recorded Announcement File System Query (0x0102) to generate a Recorded Announcement File System Report (0x0119).

2. Take the VRA SIMM out of service with Service State Configure (0x0A).

3. Convert the flash to file system Revision 1 by using Recorded Announcement File System Convert (0x0118).

4. Wait three to five minutes for the VRA SIMM alarm Recorded Announcement File System Conversion Success (0x07).

5. If necessary, download more RANs using Recorded Announcement Download Initiate (0x53) and Recorded Announcement Download (0x52).

6. Bring the VRA SIMM in service with Service State Configure (0x0A).

7. Play the RANs as needed.

Edit RAN ID 0x0002:

1. Delete RAN ID 0x0002 using Recorded Announcement Single Delete (0x0117). Wait for the alarm, Recorded Announcement Single Delete Complete (0x0D).

2. Download the new RAN ID 0x0002 using Recorded Announcement Download Initiate (0x53) and Recorded Announcement Download (0x52).

3. When enough RANs have been deleted to make it worthwhile to recover the unused memory, take the VRA SIMM out of service with Service State Configure (0x0A). You can query the amount of dirty memory using Recorded Announcement File System Query (0x0102).

4. Recover the memory used by the deleted RANs with Recorded Announcement File System Defragment (0x0103).

5. Wait for the alarm, Recorded Announcement Defragmentation Success (0x0B).

6. Bring the VRA SIMM in service with Service State Configure (0x0A).

See Recorded Announcements.
Digital Signal Processor
See Controlled Introduction.
RAN. Recorded messages provided to callers for various reasons.
The condition of a component at a given instant. The current "context" of a PPL object, such as Idle, Seizing, Answered. In PPL files, a State is represented by a circle.