This repository was archived by the owner on Nov 29, 2023. It is now read-only.
VAPI-1390: Real-Time Transcription Doc Proposal #992
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1 similar comment
tmoney-bw
reviewed
Apr 12, 2023
nashley
commented
Apr 17, 2023
nashley
force-pushed
the
vapi-1390-real-time-transcription
branch
from
72f46d3 to
7bcfda2
Compare
CatexB
reviewed
Jun 7, 2023
CatexB
reviewed
Jun 8, 2023
CatexB
reviewed
Jun 8, 2023
CatexB
reviewed
Jun 8, 2023
| | callUrl | The URL of the call associated with the event | | ||
| | cause | The reason the real-time transcription was rejected, can be one of `connection-error`, `duplicate`, `error` or `track-limit` | | ||
| | direction | The direction of the call. Either `inbound` or `outbound`. The direction of a call never changes. | | ||
| | enqueuedTime | (optional) If [call queueing](/apis/voice#operation/createCall/) is enabled and this is an outbound call, time the call was queued, in ISO 8601 format. | |
There was a problem hiding this comment.
Suggested change
| | enqueuedTime | (optional) If [call queueing](/apis/voice#operation/createCall/) is enabled and this is an outbound call, time the call was queued, in ISO 8601 format. | | |
| | enqueuedTime | (optional) If [call queueing](/apis/voice#operation/createCall/) is enabled and this is an outbound call, time the call was queued, in ISO 8601 format. Else, this field is omitted. | |
There was a problem hiding this comment.
Got this in all other callbacks, thx!
CatexB
reviewed
Jun 8, 2023
| @@ -4197,9 +4197,7 @@ paths: | |||
| description: >- | |||
There was a problem hiding this comment.
I can't comment on the line above this, but maybe we should rename the summary to Get Recording Transcription?
Co-authored-by: Catherine <31828886+CatexB@users.noreply.github.com>
…thub.com:Bandwidth/api-docs into vapi-1390-real-time-transcription
tmoney-bw
previously approved these changes
Jun 29, 2023
CatexB
reviewed
Jun 29, 2023
| title: Start Transcription | ||
| slug: /voice/bxml/startTranscription | ||
| description: A general overview of Bandwidth's startTranscription BXML Verb | ||
| keywords: |
There was a problem hiding this comment.
small but transcription should be here probably
There was a problem hiding this comment.
same for the other places ig
There was a problem hiding this comment.
It has "transcribing"
CatexB
reviewed
Jun 29, 2023
| This event may be sent to the url specified when sending a [`<StartTranscription>`][1] verb. This event will be sent if the real-time transcription requested in the `<StartTranscription>` verb was not started. | ||
|
|
||
| ## Request Parameters | ||
| TODO `s/originalTranscription/originalRealtimeTranscription`? |
tmoney-bw
approved these changes
Jun 29, 2023
CatexB
approved these changes
Jun 29, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
All spec changes should be done in the api-specs repository.
Please follow the Guide for contributing to our developer documentation.
Spec PR here
Has a lot of loose ends to tie up. For example:
StartTranscriptionto about, overview, etcStartTranscriptionStopTranscriptionto about, overview, etcStopTranscriptionrealtimeTranscriptiontostartTranscription?