Voice Integrations
The Oracle® Intelligent Communications Orchestration Network cloud service supports integration with voice networks and services to enable high-quality, real-time calling experiences. Following voice integration is available from the Oracle® Intelligent Communications Orchestration Network cloud service.
- Generic SIPREC
Generic Media Stream
The Oracle® Intelligent Communications Orchestration Network cloud service’s Media Stream capability for SIP trunk voice services enables real-time voice integrations by establishing an outbound secure WebSocket (wss://) connection to a customer-provided endpoint and streaming call audio directly to their application. Over the same WebSocket session, the Oracle® Intelligent Communications Orchestration Network cloud service delivers both stream state/control messages and media messages, supporting near real-time processing use cases. This capability is specifically focused on enabling a generic media stream integration on a SIP trunk.
Working of Generic Media Stream
- The Oracle® Intelligent Communications Orchestration Network cloud service initiates an outbound secure WebSocket (WSS) connection to the configured endpoint (your wss://... URL).
- Once the WebSocket connection is established, Oracle® Intelligent Communications Orchestration Network cloud service sends stream lifecycle and context messages—such as connect, start, and metadata—to indicate the stream state and provide call-related context.
- The Oracle® Intelligent Communications Orchestration Network cloud service then begins streaming audio as a sequence of WebSocket messages.
- Each media message includes:
- A base64-encoded audio payload
- Identifiers that indicate which channel/participant the audio is associated with (for example, to distinguish caller vs. callee, or multiple participants where applicable).
- When the interaction ends or the stream is stopped, the Oracle® Intelligent Communications Orchestration Network cloud service sends a close message to indicate stream termination.
WebSocket Message Types
Over the WebSocket connection, the Oracle® Intelligent Communications Orchestration Network cloud service sends a standard set of message types to manage the stream and deliver audio:
- connect - indicates that the media stream session has successfully connected to the WebSocket endpoint specified by the WSS URL in the configuration profile.
- start - indicates that the media stream session is ready and will begin streaming media to the WebSocket endpoint.
- metadata - indicates that new metadata has become available during the call and must be relayed to the WebSocket endpoint.
- dtmf - indicates that a DTMF tone was received from a call participant and must be relayed to the WebSocket endpoint.
- media - relays audio from one of the call participants to the WebSocket endpoint, delivering Base64-encoded audio frames along with channel and participant indicators.
- close - indicates that the media stream session has ended, provides the reason for ending, and signals that the WebSocket connection will be closed.
Add a Generic Media Stream Integration
Before You Begin
- Purchase the Voice Integration SKU.
- Configure a SIP trunk to the voice service you want to connect by way of Generic Media Stream.
Procedure
Generic SIPREC
You can add a generic SIPREC integration to a voice service to record calls. You can add the integration to an existing voice service or configure it in the workflow while connecting a newly selected voice service to the Oracle® Intelligent Communications Orchestration Network Cloud Service.
Note:
Generic SIPREC integration is not supported for Voice Gateways and Carrier service.Add a Generic SIPREC Integration to a Voice Service
Session Initiation Protocol Recording (SIPREC) facilitates capturing and recording multimedia sessions, such as voice calls and video conferences, in real-time over IP networks. You can use Oracle® Intelligent Communications Orchestration Network cloud service to send your media to SIPREC-based service.
- Purchase the Voice Integration SKU.
- Configure a SIP trunk to the voice service where you want to enable SIP recording.
In the following procedure, configure a SIP trunk to the voice service that you want to connect by way of SIPREC. You have the option to add up to 5 custom x-headers to capture additional information for call control, feature signaling, or integration with external systems to extend capabilities beyond standard SIP headers.
Add SIP X-headers to a SIPREC Integration
Use the following procedure to add optional, custom x-headers to a SIPREC integration with the Oracle® Intelligent Communications Orchestration Network cloud service. You can add up to 5 custom x-headers to capture additional information for call control, feature signaling, or integration with external systems to extend capabilities beyond standard SIP headers.