IMG 1010 - Vocabulary Index Entry

Description:

This pane is used to add announcement entries to a Vocabulary Index File.

Accessing this Pane

Dialogic IMG EMS-> Routing Configuration-> New Vocabulary Index Files-> New Vocabulary Index File -> New Vocabulary Index File Entry

Maximum Objects:

1,024 per VIF

Related Procedure

IMG 1010 - Configuring an NFS Server

IMG 1010 - Vocabulary Index File

ClientView Pane:

Field Descriptions:

File Id:

This field is automatically populated with the next available number. The ID can be changed by selecting a different ID from drop down menu. Values range from 0-1023.

File Description:

Enter a Precise description of the file. This description will be used to identify the file in other clientview panes. Click in the File Description field and enter a Description Name.

Primary Server Id:

The Primary NFS Server that the announcement is stored on. Select from drop down list all the NFS servers configured in ClientView. The server will be identified by its ID.

Secondary Server Id:

The Secondary NFS Server that the announcement is stored on. Select from drop down list all the NFS servers configured in ClientView. The server will be identified by its ID.

File Name:

Enter a name that identifies the filename of the announcement.

File Format:

Select from drop down list the format of the announcement. See list below:

  • Raw Data Format

  • .Wav File Format

  • .VOX File Format

File Encoding:

  • G711 Alaw

  • G711 ulaw

  • G726 32 Kbps ADPCM

  • 32 Kbps OKI ADPCM

  • 24 Kbps OKI ADPCM

  • 16 bit linear (11025 Khz mono)

  • 8 bit linear (11025 Khz mono)

Start Offset for File:

An offset can be added to start playing from a particular location within a file. The offset is configured in bytes starting at the beginning of the file. The Offset is represented in bytes so the application is responsible for managing the different encoding formats, and for how bytes should represent time.

File Length to be played:

Specify in bytes how long the file should play so it doesn't have to play to the end. The Offset is represented in bytes so the application is responsible for managing the different encoding formats, and for how bytes should represent time.

Return to Documentation Home I Return to Sangoma Support