Skip to main content

Need Help Using Spok Knowledge? 

Spok

Vocab Table and VRU

Overview

The Smart Suite ATMS.VOCAB table and how it relates to the VRU.

Resolution/Topic

With the Smart Suite VRU, there are two different ways for the channels to relay the sounds a person hears as prompts.  The file type typically used here has a .prp extension (which is just a .vox file with the name changed).  The amcom.vox file (~amcom/vru/speak) is one large collected file of audio data.  There is also a lesser-known site.vox, which is like amcom.vox, but this is generally not used, so we will only describe amcom.vox here.  The different node options in the VRU are PLAY and SPEAK.  With PLAY, the VRU executable actually plays the sound file (.prp file) as VLC Player / Media Player / Audacity would.  With SPEAK, it "speaks" (plays a specific section out of the amcom.vox file) the "PHRASE" as defined in the ATMS.VOCAB table.  You can see in a VRU initialization file (such as main_analog.ini) which ones might be set to SPEAK and which ones might be set to PLAY.

The Smart Suite VOCAB table has four columns (you can also see this by describing the table): PHRASE, POSITION, PHRASE LENGTH, and FILE_NUMBER.  PHRASE is the name of the section that is defined as the block from the amcom.vox file and should ideally match what was loaded into the amcom.vox file.  The POSITION is the position in the amcom.vox file at which the PHRASE begins.  The PHRASE_LENGTH is how long the PHRASE is.  FILE_NUMBER can be 0 or 1 depending on which .vox file is used, and this is set by default when adding phrases.  0 is used for the amcom.vox.

Just because a value in the PHRASE column is set to one thing doesn't mean that's what is in the VOCAB table at that start point.  That's just the name given to that section.  You could create a PHRASE of "Banana" but the sound file you loaded in at that point (with that name) could be "Please answer the phone".  The default amcom.vox is set up a specific way, but customers do have their vocab changed now and then.  If copying the amcom.vox from one site to another, you may run into just such an issue -- vocab phrase "x" plays (speaks) something entirely different.


KB28082