Skip to content
Skylark Media Server

One media server.From VoLTE to voice AI.

A subscriber calls your service. They hear an announcement, choose an IVR option or speak to an assistant. Behind each step, your network needs the right media, in the codec negotiated for that call.

Skylark Media Server brings announcements, conferencing, encrypted recording and speech-engine integration into one platform. In IMS, it provides the Media Resource Function while your application server controls the service.

IMS MRFEVS / AMR-WBSIP / RTPEncrypted recordingVoice AIKubernetes / VNF
The service behind the call

Give each call the media it needs

Start with the services your subscribers use today. Add recording or speech processing where the call flow needs them, on the same media platform.

Run your voice services

Play announcements, collect DTMF and connect conferences. Your IMS application server controls the media through SIP, NETANN, MSML or VoiceXML.

Keep service logic in your application server.

Record both sides securely

Capture each call side on its own channel. Skylark encrypts audio in memory and sends recordings to encrypted storage, without writing an unencrypted copy to disk.

Preserve separate channels for downstream review.

Bring speech into the call

Fork media to recognition while the call continues. Return synthesised speech in the negotiated call codec, using native or external speech engines.

Add voice AI through the network media path.

Build it around the way your voice services run

  • How your application server requests media
  • Which codecs your call routes need to support
  • Where a keypad choice takes the caller next
  • How each recorded call side reaches storage
  • Which calls connect to your speech engines
  • How you migrate services and retain a rollback route
Inside your IMS network

Connect service decisions to call media

Skylark provides the Media Resource Function (MRF), including MRFC and MRFP. SIP carries media-control requests on Mr and Mr′; RTP carries the call media on Mb.

Negotiate media at call setup
SIP uses SDP offer/answer to establish the media format for the session. Skylark works with that negotiated codec and converts it when a service needs another format.
Open the speech path when needed
For an active AI service, Skylark converts audio to PCM for speech engines over WebSocket. Other calls keep their ordinary media path.
Build on your service logic
Use Skylark with your IMS application server, or as the media layer in OVOO Trinity, alongside Service Engine call control and Cortex AI reasoning.
Skylark in the IMS media pathThe IMS application server controls Skylark over SIP on Mr and Mr-prime. Skylark provides MRFC and MRFP functions. RTP on Mb carries call media in both directions. For an active AI service, PCM audio connects to speech engines over WebSocket. Recordings go to encrypted storage.IMS APPLICATION SERVERService logic + media controlSIP · Mr / Mr′SKYLARKIMS MRF · MRFC + MRFPRTP · MbPCMWebSocketEncryptedaudioCALL MEDIANegotiated call codecSPEECH ENGINESActive AI servicesRECORDINGEncrypted storage
IMS application serverService logic + media control
SIP · Mr / Mr′
SKYLARKIMS MRF · MRFC + MRFP
RTP · Mb
Call mediaNegotiated call codec
PCM · WebSocket
Speech enginesActive AI services
Encrypted audio
RecordingEncrypted storage
One call, four media steps

Follow the media in one call

A subscriber calls your care service. Follow the prompt, their keypad choice and the speech path behind the conversation.

Operator careCustomer supportCalling…MuteKeypadSpeakerHoldAdd callBluetooth

The call stages play automatically while the phone is visible. Drag or use arrow keys to rotate the phone. Enter or Space continues the call flow. On the keypad, press 1 to select account support. R, Home or a double click resets the view.

Connecting the call. Your application server requests media over SIP. Skylark establishes the RTP path.

From call flow to integration

Make each media step part of the service

A call moves between network routes, service prompts and the people or applications behind them. Skylark handles the media at each step, while your teams control how the service runs.

Match call audio to your service

A call arrives in EVS or AMR-WB, but the service needs another format. Skylark transcodes between the negotiated call codec and that service format, keeping media processing aligned with the call.

Bring your applications onto Skylark

Existing services depend on specific media controls and scripts. Skylark supports VoiceXML 2.0/2.1; map each application’s dependencies and test the operations and responses it needs before cutover.

Support the calls beyond an IVR menu

Some services need a conference or a fax session beyond an IVR menu. Skylark provides conferencing and T.38 fax; test those paths with the actual endpoints and routes your service will use.

Carry more than the voice conversation

Video brings its own codec requirements into a call. Skylark supports H.264 and H.265, plus VP8/VP9 for WebRTC, so those paths can be included alongside voice in your service acceptance tests.

Let subscribers speak to the service

A caller can speak instead of choosing from a keypad menu. Skylark handles the media for recognition and synthesis; AI reasoning and call treatment remain with the service controlling the conversation.

Give operations a view of the media

When a media problem reaches the NOC, the team needs operational evidence. Skylark exposes SNMPv2/3 and Prometheus/Grafana metrics, bringing media visibility into your existing OAM tools.

A subscriber service

Handle the conversation behind call screening

A call-screening service can ask an unfamiliar caller for the context of their call. That exchange needs media in both directions: the caller's response goes to recognition, and the next spoken prompt returns to the same voice session.

Skylark provides that audio path. The application server and AI layer determine the call treatment, so the media exchange remains separate from the decision about how the call should proceed.

Explore OVOO Trinity
A spoken exchange during call screeningThe service asks for the reason for a call. The caller replies, providing context for the service decision.CALLERSCREENING PROMPTWhat is your call about?SERVICECALLER RESPONSEA delivery for Alex.
Media server comparison

See what each media platform brings to your network

Skylark combines IMS media with a native speech option and Kubernetes scaling. Compare the capabilities and the integration work around them.

Comparison of selected IMS media-server capabilities
Decision areaDialogic PowerMedia XMSRadisys Engage Media ServerSkylark Media Server
Speech-engine ownershipThird-party ASR/TTSExternal speech provider to integrateBuilt-in keyword detectionFull ASR/TTS uses third-party enginesNative or external ASR/TTSRun speech within Skylark, or use your engine
Live speech integrationMRCP / cloud providersGoogle/Amazon STT: file-basedMRCP v1 / v2Third-party speech-engine endpointLive PCM over WebSocketSame Skylark interface across engines
Scale-out operationsVMs / containers / cloudAdditional MRB for pooled scale and HAKubernetes CNF / VM VNFContainer or VM deploymentKubernetes CNF / VNFReplicas follow call and session load
Recording protectionStereo WAV captureEncrypted WebM / MKV formatsEncrypted recording / playbackPer-side; encrypted in memoryNo plaintext copy written to disk
VoLTE audioEVS / AMR-WB; transcodingEVS / AMR-WB; transcodingEVS / AMR-WB; transcoding
Application controlMSML / NETANN / VoiceXML / RESTMSML / NETANN / VoiceXML / H.248MSML / NETANN / VoiceXMLReuse your IMS application control model
Operate and migrate

Move services at your network's pace

Deploy Skylark as a Kubernetes CNF or a VNF. For the CNF, scale replicas to call and session load, and drain sessions during planned updates. Native Rust code runs without a garbage collector.

Start with one service on the existing application server. Validate its media controls and codec paths, then move further services with a defined rollback route.

The next service layer

Plan an in-call screen alongside voice

For an IMS Data Channel integration, Skylark is designed to take the Media Function role in the NG-RTC architecture, linking Data Channel media with call audio for services such as live captions.

An in-call screen needs a compatible handset and IMS integration. Your voice AI service can run over VoLTE or VoNR without Data Channel support in the handset.

FAQ

What network teams ask before cutover

How do we cut over an existing service and keep a rollback path?

Move one service at a time. Agree the call flow, codec combinations and media controls, then validate those flows on Skylark before moving further services. Keep a defined rollback route to the existing media server. Include application-server routing and treatment of active sessions in the cutover plan.

What should we check before moving MSML or VoiceXML applications?

Check the MSML packages used by each application rather than treating protocol support as full application compatibility. Skylark supports VoiceXML 2.0 and 2.1, alongside SIP and NETANN control. Test your actual announcements, DTMF collection and conference operations with the application server, and confirm the required MSML package coverage before cutover.

How should we size capacity when transcoding and voice AI share the platform?

Size against your traffic profile: simultaneous sessions, codec pairs, conferencing, recording and the share of calls using speech engines. Validate that combination under representative load. Skylark scales replicas within configured limits, with a SIP distribution layer spreading calls across pods. Agree capacity and headroom for the service mix you intend to run.

Where is the integration boundary with our speech engines?

Your integration has two boundaries: Skylark exchanges audio with the selected speech engine, while call control determines which sessions use AI and how the service continues. For acceptance, test recognition and synthesis in one end-to-end call, including the codec negotiated on the network route and the PCM/WebSocket handoff.

What must our recording integration preserve for downstream replay and review?

Agree how the two call channels are correlated with the call record, transferred to encrypted storage and made available to authorised downstream consumers. Validate replay and access through that storage integration as part of acceptance. This is separate from Skylark’s capture and in-memory encryption of the audio.

What is the difference between graceful draining and pod failure?

During a planned update, a drained pod closes after its last session ends or the configured time limit is reached. If a pod fails, Kubernetes restarts it and its sessions are released. Set the drain window around your call durations and test application-server treatment of interrupted sessions separately from rolling updates.

What should operations plan for a CNF or VNF deployment?

Define responsibility for SIP call distribution, replica limits, monitoring and the recording or speech integrations around the media server. Kubernetes handles CNF pod replacement, but service recovery also depends on how the application server treats released sessions. For a VNF, agree the corresponding capacity and recovery procedures.

Which media paths belong in interconnect acceptance testing?

Skylark supports EVS, AMR-WB, AMR-NB, G.711, G.722, G.729 and Opus. Test the codec pairs negotiated on your actual routes and transcoding to each service format. Cover video and T.38 fax separately. For voice AI, include both call audio to recognition and synthesised speech back to the caller.

Can we launch voice AI before introducing IMS Data Channel?

Yes. Voice AI can run over VoLTE or VoNR without Data Channel support in the handset. An in-call screen needs a compatible terminal and the Data Channel integration. Plan that separately, including Skylark's Media Function role, DC2 media-resource control and the connections to the Data Channel signalling and application functions.

Your IMS media service

Start with a call flow your network needs to run

Bring your call flow, codecs and application-server interfaces. Together we can map the media path, agree recording and speech-engine integration, and plan a service-by-service migration.

Discuss Skylark
Discuss Skylark