From 3a770a6538231dc9144cd3b6e9eadde6912d011e Mon Sep 17 00:00:00 2001 From: Matt Van Horn Date: Thu, 2 Jul 2026 08:41:11 -0700 Subject: [PATCH] docs: clarify Asterisk ARI websocket_client.conf URI and why /ws/ari 403s when tested directly (#490) Co-authored-by: Matt Van Horn <455140+mvanhorn@users.noreply.github.com> --- docs/integrations/telephony/asterisk-ari.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/integrations/telephony/asterisk-ari.mdx b/docs/integrations/telephony/asterisk-ari.mdx index 7bd69f16..cffb21e6 100644 --- a/docs/integrations/telephony/asterisk-ari.mdx +++ b/docs/integrations/telephony/asterisk-ari.mdx @@ -106,6 +106,10 @@ Dograh uses Asterisk's external media streaming to send and receive audio over W The section name (e.g., `dograh`) is the **WebSocket Client Name** you'll enter in the Dograh telephony configuration. This name tells Asterisk which WebSocket connection to use for external media streaming during calls. + +Configure the `uri` as a base URL only, without a query string. During each call, Dograh asks Asterisk to create an `externalMedia` channel and Asterisk appends `workflow_id`, `user_id`, and `workflow_run_id` through the `v()` transport data for that call. Opening `/api/v1/telephony/ws/ari` directly in a browser or with `wscat` can return HTTP 403 because those routing parameters are missing; that is expected and does not indicate a `websocket_client.conf` misconfiguration. + + Dograh's external media channel uses **G.711 μ-law (`ulaw`)**. Make sure any PJSIP endpoint or SIP trunk that places or receives calls through Dograh allows `ulaw` (e.g. `allow=ulaw` in the endpoint config).