{"items":[{"type":"link","label":"Voice Stream","link":"/docs/voice-2.0/api-reference/stream","routeSlug":"/docs/voice-2.0/api-reference/stream"},{"label":"customer/defined","type":"group","link":"/docs/voice-2.0/api-reference/stream/channels/outboundstream","routeSlug":"/docs/voice-2.0/api-reference/stream/channels/outboundstream","httpVerb":"channel","badges":[],"metadata":{"seo":{"title":"customer/defined"}},"items":[{"label":"Connection initiated from the Sinch Platform","type":"link","link":"/docs/voice-2.0/api-reference/stream/channels/outboundstream/operations/connect","routeSlug":"/docs/voice-2.0/api-reference/stream/channels/outboundstream/operations/connect","httpVerb":"send","badges":[],"metadata":{"seo":{"title":"Connection initiated from the Sinch Platform","description":"This is the first message sent from the Sinch platform for all outgoing stream connections. This message carries information about the call, including call headers, the Call-ID, Application-ID, etc. Based on the information that this command carries, the customer can make a decision if the request should be accepted or not."}}},{"label":"Platform sends audio frames to the web-socket server (binary WebSocket messages)","type":"link","link":"/docs/voice-2.0/api-reference/stream/channels/outboundstream/operations/platformtoclientaudio","routeSlug":"/docs/voice-2.0/api-reference/stream/channels/outboundstream/operations/platformtoclientaudio","httpVerb":"send","badges":[],"metadata":{"seo":{"title":"Platform sends audio frames to the web-socket server (binary WebSocket messages)","description":"Once the server answers the call, audio can flow from the platform to the server as binary WebSocket frames."}}},{"label":"Client responds with answer/busy/reject command","type":"link","link":"/docs/voice-2.0/api-reference/stream/channels/outboundstream/operations/connectresponse","routeSlug":"/docs/voice-2.0/api-reference/stream/channels/outboundstream/operations/connectresponse","httpVerb":"receive","badges":[],"metadata":{"seo":{"title":"Client responds with answer/busy/reject command","description":"After receiving the ConnectRequest, the server must respond with one of three commands:"}}},{"label":"Client sends audio frames to the platform (binary WebSocket messages)","type":"link","link":"/docs/voice-2.0/api-reference/stream/channels/outboundstream/operations/servertoplatformaudio","routeSlug":"/docs/voice-2.0/api-reference/stream/channels/outboundstream/operations/servertoplatformaudio","httpVerb":"receive","badges":[],"metadata":{"seo":{"title":"Client sends audio frames to the platform (binary WebSocket messages)","description":"Once the server answers the call, audio can flow from the server to the platform as binary WebSocket frames."}}},{"label":"Client sends control messages to the platform.","type":"link","link":"/docs/voice-2.0/api-reference/stream/channels/outboundstream/operations/streamcommands","routeSlug":"/docs/voice-2.0/api-reference/stream/channels/outboundstream/operations/streamcommands","httpVerb":"receive","badges":[],"metadata":{"seo":{"title":"Client sends control messages to the platform.","description":"Client can send control commands to manage the audio stream during an active call.Supported commands:"}}}]}]}