Features

Introduction

The DSP Series 2 offers a comprehensive set of features to support media processing and management for CSP-based solutions. Highlights include:

Announcement Processing

The system supports NFS based announcements, with on-board cache for voice file storage. Multiple NFS servers can be supported; the system manages the location of files through an ASCII file.

Dynamic Voice Recording and Playback

DSP Series 2 supports on-board temporary recording storage as well as external disk-based long term storage.

High Density Tone Receivers

Depending on the receiver type, the system supports up to 512 tone receivers per DSP.

Large Conferencing Capability

The system supports up to 256 conferees per DSP, and 128 conferees per conference bridge.

• The user can adjust gain and speed, and skip forward and backward. The DSP Series 2 supports configurable beep tones, configurable silence parameters, and two-way call recording without using conference ports

• The direct interface between the DSP card and the file server uses a 100 mbps I/O interface, off loading CPU processing, which in turn reduces overhead and improves performance.

Echo Cancellation

The DSP Series 2 card Echo Canceller removes echoes caused by signal leakage at hybrid telephone line interfaces. You may want to implement an Echo Canceller for tandem calls on trunks with echo, or to clean an incoming signal before connecting to a media resource, such as a Voice Response Unit or Answering Machine Detection.

Positive Voice Detection/Answering Machine Detection

You can configure the CSP to analyze incoming PCM data and detect voice or an answering machine. You can set PVD/AMD parameters for a DSP Series 2 card and for an individual channel.

Media Streaming over RTP

RTP, the real-time transport protocol, provides end-to-end network transport functions suitable for applications transmitting real-time data, such as audio, video or simulation data, over multicast or unicast network services. RTP does not address resource reservation and does not guarantee quality-of- service for real-time services.

Chip Monitoring

This feature provides the Chip Monitoring function that monitors the state of the DSP chips on the DSP Series 2 card.

At startup, the Chip Monitoring function constantly polls all the DSP chips to make sure they are operating. If a DSP chip does not respond to three consecutive poll messages, the Chip Monitoring function tries to reset the chip and sends a DSP Alarm (DSP Chip Reset 0x08) to the host. If the chip activates after being reset, the DSP Chip Reset alarm is cleared. If the chip does not activate after three attempts to reset it, then the chip is designated as out of service and the DSP Alarm (DSP Out of Service 0x01) is sent to the host. The Stop Monitoring Event is sent to the chip whenever the host takes that chip out of service.

The Alarm (0x00B9) message, 0x06 DSP Alarms, enables the DSP Chip Reset (0x08) alarm. This alarm indicates that the DSP chip has been reset internally after an error occurred. This alarm is cleared when the DSP chip resumes operation after reset.

Frequency Shift Keying

The Frequency Shift Keying (FSK) feature, supported by the DSP Series 2 card, involves the transmitting and receiving of FSK modulated signals. FSK is a modulation technique used by modems in which two different frequencies are used to represent the binary state of 1s and 0s as tones across telephone lines. This feature supports both European Telecom (ETSI) and China Telecom (CTSI) SMS protocols and Caller ID.

Receiving FSK

The Receiving FSK feature uses the Resource Connect (0x0127) and Resource Information Notify (0x0141) messages that allow the host to receive FSK data from an off-hook channel.

Currently, the CSP supports sending Frequency Shift Keying (FSK) data containing On-hook Caller ID in the Outseize Control (0x002C) message and Off-hook Caller ID in the Resource Connect (0x0127) message. It also supports sending and receiving FSK data containing SMS DLL messages that comply with ETSI and CTSI (China Telecom) call flows.

Refer to Frequency Shift Keying, for detailed information modified API messages and TLVs. Also refer to the detailed information in the API Reference for the modified APIs and TLVs.