Skip to main content
Asterisk integrates with Rapida using two transport methods. Choose based on your Asterisk version and network topology.

Transport Comparison


AudioSocket

1

Configure env vars

assistant-api binds a TCP AudioSocket server on AUDIOSOCKET__PORT at startup.
2

Verify the module is loaded

If not loaded, add to /etc/asterisk/modules.conf:
3

Configure the dialplan

CHANNEL(audioreadformat)=slin and CHANNEL(audiowriteformat)=slin are required. AudioSocket expects SLIN (signed linear PCM) — without this Asterisk will not convert the audio format.
4

Reload and test

Outbound via ARI (AudioSocket)

For outbound calls, Rapida uses Asterisk’s ARI to originate the channel. The RAPIDA_CONTEXT_ID channel variable is injected by Rapida ARI automatically:
ARI vault credential keys (store in Rapida vault, provider type Asterisk):

WebSocket

1

Configure env vars

2

Verify the module is loaded

If not loaded, add to /etc/asterisk/modules.conf:
3

Configure the dialplan

4

Reload and test

Outbound via ARI (WebSocket)

Same ARI vault credentials apply — see the AudioSocket section.

Production URLs

For Rapida SaaS:

SIP

Built-in SIP server for direct SIP connectivity

Configure Your Own

Add a new telephony provider

Configuration

AUDIOSOCKET env vars reference

Telephony Overview

All providers comparison