@wildix/wilma-voice-client 0.0.51 → 0.0.53

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -73,12 +73,11 @@ export interface WilmaVoice {
73
73
  * (engine, instructions, capabilities and channels.voice settings). This is a runtime only: there
74
74
  * is no agent/bot CRUD here — agents are authored and versioned in wilma-agents.
75
75
  *
76
- * On the WebSocket (transport host `wilma-voice-ws.wildix.com`), PBX clients transcribe caller
77
- * speech themselves and send `transcription` / `reply` text, while web/app clients connect with
78
- * inputMode=AUDIO and push raw caller `audio` chunks that the service transcribes server-side;
79
- * the service returns `say` / `play` / `stop` / `hangup` / `transfer`. On the PBX media socket
80
- * (`/v2/voice/media/ws`, subprotocol `wilma-media-v2`), the PBX sends raw caller audio and the
81
- * service answers with audio and the text frames listed under DescribeVoiceProtocol `media`.
76
+ * On the WebSocket (transport host `wilma-voice-ws.wildix.com`), the PBX transcribes caller
77
+ * speech itself and sends `transcription` / `reply` text; the service returns `say` / `play` /
78
+ * `stop` / `hangup` / `transfer`. On the call socket
79
+ * (`/v2/voice/calls/ws`), the PBX sends raw caller audio and the
80
+ * service answers with audio and the text frames listed under DescribeVoiceProtocol `callSocket`.
82
81
  * Every WebSocket message shape (connect params, events and commands) is declared as a structure
83
82
  * and enumerated by DescribeVoiceProtocol so the generated SDKs carry the types and
84
83
  * (de)serializers; the WebSocket transport itself is hand-coded. The HTTP Send* operations push
@@ -164,12 +164,11 @@ export interface WilmaVoiceClientResolvedConfig extends WilmaVoiceClientResolved
164
164
  * (engine, instructions, capabilities and channels.voice settings). This is a runtime only: there
165
165
  * is no agent/bot CRUD here — agents are authored and versioned in wilma-agents.
166
166
  *
167
- * On the WebSocket (transport host `wilma-voice-ws.wildix.com`), PBX clients transcribe caller
168
- * speech themselves and send `transcription` / `reply` text, while web/app clients connect with
169
- * inputMode=AUDIO and push raw caller `audio` chunks that the service transcribes server-side;
170
- * the service returns `say` / `play` / `stop` / `hangup` / `transfer`. On the PBX media socket
171
- * (`/v2/voice/media/ws`, subprotocol `wilma-media-v2`), the PBX sends raw caller audio and the
172
- * service answers with audio and the text frames listed under DescribeVoiceProtocol `media`.
167
+ * On the WebSocket (transport host `wilma-voice-ws.wildix.com`), the PBX transcribes caller
168
+ * speech itself and sends `transcription` / `reply` text; the service returns `say` / `play` /
169
+ * `stop` / `hangup` / `transfer`. On the call socket
170
+ * (`/v2/voice/calls/ws`), the PBX sends raw caller audio and the
171
+ * service answers with audio and the text frames listed under DescribeVoiceProtocol `callSocket`.
173
172
  * Every WebSocket message shape (connect params, events and commands) is declared as a structure
174
173
  * and enumerated by DescribeVoiceProtocol so the generated SDKs carry the types and
175
174
  * (de)serializers; the WebSocket transport itself is hand-coded. The HTTP Send* operations push