DSP Settings main window 146
Access Server Administrators’ Reference Guide 11 • Digital Signal Processing (DSP)
• booting(3)—The DSP has just been loaded with code and we are now waiting for an indication from the
DSP that the code loaded properly and is running.
• hwReseted(4)—The DSP is reset.
• swLoaded(5)—Software is downloaded to the DSP or DSP group.
• waitForGroup(6)—DSP has responded to start command. DSP is now waiting for other DSPs in the group
to respond.
• unavailable(7)—The instance is fully operational and could be used to take a call except that the adminis-
trator has indicated that this instance should not be used.
• reserved(8)—The instance is fully operational and could be used to take a call. But, another DSP in the
same boot group as this one is pendingBoot. Therefore we are not to use this until the reboot occurs. This
state only appears where the PCB version is 1 or less (for information on displaying the version, refer to sec
-
tion “PCB Revision (boxManufacturePcbRevision)” on page 233).
• suspect(9)—The instance is operational and could be used to take a call. But, we have seen a number of
consecutive failures so it will not be used until no other available instances can be found. A successful call
will place this instance back into the available state.
• available(10)—The instance is fully operational and can be used to take a call
Instance #1 Use (dspUsefirst)
Identifies whether the first instance of the DSP is in use or free.
Instance #2 State (dspStateSecond)
Identifies the current state of the second instance of the DSP. See “Instance #1 State (dspStatefirst)” for param-
eter values.
Instance #2 Use (dspUseSecond)
Identifies whether the second instance of the DSP is in use or free.
Figure 60. DSP Memory Capture and DSP PCM Capture settings