From 01878e46ad0b186f5fbd8bf817b96639e6241e15 Mon Sep 17 00:00:00 2001 From: Dave Horton Date: Tue, 19 Nov 2024 12:47:15 -0500 Subject: [PATCH] typo --- .../supporting-articles/controlling-media-path-during-call.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/markdown/docs/supporting-articles/controlling-media-path-during-call.md b/markdown/docs/supporting-articles/controlling-media-path-during-call.md index cf5c808..27e2aac 100644 --- a/markdown/docs/supporting-articles/controlling-media-path-during-call.md +++ b/markdown/docs/supporting-articles/controlling-media-path-during-call.md @@ -4,7 +4,7 @@ When using the [dial verb](/docs/webhooks/hangu) to create a bridged call there - **full media** - we call it "full media" if the audio continues to be routed through the feature server. From the perspective of the caller, their audio is routed to the jambonz SBC, through the feature server, and back out through the jambonz SBC on its outward path to the called party. This media path is necessary if an application wants to perform operations like transcribe, listen, or record the call. -- **partial media** - we call it "partial media" if the audio path for the bridged call is released from the featuer server and only traverses the SBC(s) on its journey from caller to called party. +- **partial media** - we call it "partial media" if the audio path for the bridged call is released from the feature server and only traverses the SBC(s) on its journey from caller to called party. - **no media** - we call if "no media" if the audio is completely released from jambonz. In this case, the audio path from the caller's SBC is directly to the far end SBC or SIP trunk.