ConnectionFailure with Speech Synthesis

[brandom-msft]

hi,
my Speech SDK version is 1.13.1
I get this error:
SpeechSynthesisResult {
privResultId: '13F4195BBBC34EB0A4A73670E2F41EAA',
privReason: 1,
privAudioData: undefined,
privErrorDetails: 'Unable to contact server. StatusCode: 1006, undefined Reason: Failed to obtain OCSP response: 504',
privProperties: PropertyCollection {
privKeys: [ 'CancellationErrorCode' ],
privValues: [ 'ConnectionFailure' ]
}
}

Originally posted by @Cincan in #157 (comment)

[brandom-msft]

@Cincan can you provide more information about your setup/environment?

Also any information you can share about how this manifests. Is this issue intermittent or does it fail 100%?

[Cincan]

many time it works well, and this issue is intermittent happens.

[AdamGustavsson]

This issue occured for me on the 27 Feb 2021 at 23.00 CET. I used the westeurope region. the issue was present for 5-10 minutes. I call the service from AWS lambda (eu-west) using node 10.
I use version 1.15.1 of the SDK

[AdamGustavsson]

The caching of the OCSP response does not work in a serverless context as neither the in memory cache nor the disk cache will share any cached items between calls. At least not with a cold start.
A feature request would be let the developer provide a cache function to be used. For AWS Lambda Elasticache, S3 or DynamoDb could be used instead.

[lowki]

Hello there.
I've just bumped into the exact same error in a similar context (Lambda in a node 12 runtime)
Our service was running flawlessly for several months now.

[chschrae]

Thanks for your continued input!

We have added some connection retry logic to make the connections more robust and mitigate this issue. The changes will be released in 1.17

[glharper]

Closing this as the reconnection logic has been added.