Station
Station settings, voice and audio, browser checks, a two-way audio test, the telephony and relay integrations, and the edge kit setup.
Station
The names shown in the header and the phrase that starts a run.
Voice trigger
Start a run by saying the trigger phrase while the station is armed.
- In this browser
- Speech recognition is not available.
- Where speech is processed
- Checking speech recognition.
- Now
- This browser has no speech recognition.
The browser's speech recognition works while this page is open. It is not an unattended offline wake word. The Run sample scenario button and the typed phrase on the Console always work.
The edge kit has its own optional wake phrase: Vosk running offline on the kit, with the recogniser limited to the words of the trigger phrase. It is set in the kit's configuration file.
Audio devices
The microphone and speaker this browser uses.
Device names are hidden by the browser until this site may use the microphone.
Saved in this browser. Recording and the microphone tests use it, or the default microphone if it is unplugged. Spoken triggers use the browser's default microphone.
Speaker
This browser cannot send page audio to a chosen device. It plays through the system output.
Capability checks
What this browser supports, checked when the page opened.
Speech recognition: Checking
Checking speech recognition.
Microphone access: Checking
The browser asks before this site uses the microphone. Nothing listens until you turn it on.
Audio recording: Checking
Recordings are made in the first format this browser supports: WebM Opus, Ogg Opus, MP4 or WebM.
Audio playback: Checking
Audio starts after your first click on a button that plays sound.
WebRTC: Checking
Needed for the two-way audio test and the live connection in sample runs.
Output device selection: Checking
Page audio plays through the system output.
Local storage: Checking
The workspace, announcements and runs are kept in this browser.
Two-way audio test
Send audio both ways between two endpoints at the same time and measure what each receives.
This tests two WebRTC endpoints in this browser. It does not test a SIP trunk or a phone line.
Needs no permission. Verified when B receives about 440 Hz and A about 660 Hz in the same measurement, both with packets arriving.
Endpoint A
Sends: A 440 Hz tone
Receives: What B sends
- Packets received
- 0
- Bytes received
- 0
- Level
- No signal
- Strongest frequency
- None measured
Endpoint B
Sends: A 660 Hz tone
Receives: What A sends
- Packets received
- 0
- Bytes received
- 0
- Level
- No signal
- Strongest frequency
- None measured
No test has run in this tab yet.
Paired test
The same test between two tabs or two devices, through a room that expires.
No room open.
Integrations
How this workspace reaches a telephone system and a relay output.
Passwords and keys are never entered here. They live in the kit's environment file, /etc/voxstead/agent.env. The settings below are stored in this browser only and are not sent anywhere.
Line transport
SimulatedThis public workspace always uses the simulated line. No call leaves the browser and nothing is dialled.
Cloud telephony adapter
Not configuredOptional. The adapter contract is defined for a cloud telephony provider. This workspace has no settings for it.
Asterisk and SIP
Not configuredNo settings saved. Enter the non-secret settings for the kit's Asterisk. Verified is set only by running voxstead-agent check on the kit. This website cannot run it.
Relay output device
Not configuredNo settings saved. The simulator's output is simulated. Verified is set only by running voxstead-agent check on the kit. This website cannot run it.
Setup checklist
The steps for an edge kit, and an example configuration made from this workspace.
Nothing in this checklist has been run against real hardware by this website. Tick each item as you complete it on your kit. Ticks are kept in this browser.
0 of 19 done
Download example configuration
Made in this browser from the active route its destinations and operators, and the Asterisk and relay settings above. The files contain no password or key: they say where each secret goes on the kit.
Workspace data
Where this workspace is kept, and how to start again from the sample data.
The workspace is stored in this browser (IndexedDB). Other browsers and devices do not see it.