Skip to main content
Five9 VoiceStream can deliver call audio and events to an external system. That receiving path is different from transferring a caller to an interactive agent. Threetone does not provide a released Five9 receiver or active call adapter.

​
Before you begin

Identify the Five9 domain and region, administrator, intended use of the audio, and the system responsible for receiving it. Review access and retention requirements before preparing a stream subscription. Five9’s VoiceStream developer guide describes SIP and gRPC audio delivery, with call events and stream-status events handled separately. Do not assume it uses the same contract as a generic WebSocket audio service.

​
Prepare the receiving design

1

Choose observation or interaction

For observation, define what the receiving system may analyze or retain. For an interactive agent, identify a separate supported call-control and return-audio design; receiving a stream alone does not establish one.
2

Choose the protocol

Review SIP or gRPC receiver requirements, authentication, certificates, and network access with the infrastructure owner. Use the current provider requirements rather than adapting a WebSocket URL by name.
3

Separate the destinations

Document the audio destination, CTI Call Event Destination, and StreamStatus Event Destination. Correlate their identifiers so a stream failure is not confused with the call ending.
4

Prepare release checks

Require a supported receiver before activating a subscription. Include missing events, duplicate events, audio disconnect, receiver restart, and subscription pause in the acceptance plan.
Use Five9’s subscription administration guide to review provider-side subscription and destination settings with the account owner.

​
Failure handling

If events arrive without audio, inspect the media destination and protocol independently. If audio arrives without call metadata, inspect event delivery and correlation. Preserve the contact center’s existing call path while investigating an observation failure.

​
Frequently asked questions

This guide does not establish a return-audio or call-control integration. Those capabilities need an explicitly supported design.
No released Five9 receiver is documented. Do not configure a guessed API or WebSocket destination.