OAUTH_SCOPE_MISMATCH in Google Speech to Text in V16 Beta 1

Status
Not open for further replies.

dmoorenot

Customer
Joined
Mar 8, 2019
Messages
14
Reaction score
2
I found this in my logs after turning on voicemail transcription. It appears that transcription is not only happening for voice mails but for call recordings also, though I see no mention of this here:

https://www.3cx.com/docs/voicemail-transcription/

It is clearly visible in the logs that it is transcribing the call, not the voice mail as this log was only for a call and did not include any voice mail.

Logs:

2019/03/08 19:31:22.727|882|0042|Info|CHR: Starting transcription of /var/lib/3cxpbx/Instance1/Data/Recordings/103/[Smith, Bob]_713-555-1212-921_20190309013112(11).wav

2019/03/08 19:31:23.732|882|0042|Erro|Exception during call reporting: Server returned a non successful status code - HTTPStatusCode=Unauthorized - Reason= - Content={"code":" OAUTH_SCOPE_MISMATCH ","details":{},"message":"invalid oauth scope to access this URL","status":"error"}



2019/03/08 19:31:24.143|882|0005|Verb|Enqueue Updated.REGISTRATION.64

2019/03/08 19:31:24.144|882|0013|Verb|Dequeue Updated.REGISTRATION.64

2019/03/08 19:31:25.493|882|0042|Verb|Transcribe recognized speech to: Hello, this is Bob Smith. I am doing a test of the translation.

2019/03/08 19:31:25.499|882|0005|Verb|Enqueue Updated.REGISTRATION.65

QUESTIONS: Is the plan in 16 to offer recordings (which also seemed to have changed format?) that include audio along with a full transcript but that functionality just has not been enabled in the UI? My other question is - why am I getting the OAUTH SCOPE MISMATCH error and is this a problem?

Here are my google API key details:
9763
 
What logs are you seeing this in? I just enabled recording for my extension and placed a call and I don't see any of that. Is that logging on the Google side?
 
What logs are you seeing this in? I just enabled recording for my extension and placed a call and I don't see any of that. Is that logging on the Google side?

\instance\3cxSystemService.log

Are you on 16 Beta 1?

Clearly the log is showing recording of the call, not just the voice mail:

2019/03/08 19:31:25.493|882|0042|Verb|Transcribe recognized speech to: Hello, this is Bob Smith. I am doing a test of the translation.

I personally would love this functionality. The ability to have a complete call transcribed, even if not perfect and then have that data inside CRM would provide an even broader view of customer interactions.
 
Yep... on v16 beta... Would have to be for Google Transcription :). Was looking in the activity log.. I'll check the service log.
 
So I do see the transcription attempt on the recording but no OAUTH error. Your error does say call reporting though so it might be an issue with another integration like CRM and have nothing to do with the transcription part.
 
Status
Not open for further replies.

Forum statistics

Threads
111,916
Messages
589,717
Members
164,785
Latest member
Texas Clay -