Too many retries error when trying to start a recording

[dleewo]

This issue is for a: (mark with an x)

- [x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Using the sample app, I set the ConnectionString in config.properties and tried to start a recording. It always fails with the error "Retry attempts have been exhausted"

I know the connection string is fine and the passed in serverCallId is valid because if I try to start a recording after the meeting is ended, I get a different error.

Here is the section of code where the failure occurring in the last line:

serverCallLocator = new ServerCallLocator(serverCallId);

StartRecordingOptions recordingOptions = new StartRecordingOptions(serverCallLocator);
recordingOptions.setRecordingContent(RecordingContent.AUDIO_VIDEO);
recordingOptions.setRecordingChannel(RecordingChannel.MIXED);
recordingOptions.setRecordingFormat(RecordingFormat.MP4);

logger.log(Level.INFO, "Getting call recording") ;
CallRecording callRecording = this.callAutomationClient.getCallRecording() ;
logger.log(Level.INFO, "Starting recording") ;
Response<RecordingStateResult> response = callRecording.startRecordingWithResponse(recordingOptions, null);

Any log messages given by the failure

Here is the error and exception:

2023-01-13 11:40:08.275  INFO 14195 --- [r-http-kqueue-1] com.azure.core.http.policy.RetryPolicy   : {"az.sdk.message":"Retry attempts have been exhausted.","tryCount":3}
com.azure.communication.callautomation.models.CallingServerErrorException: Status code 500, "{"error":{"code":"9999","message":"Unknown internal server error."}}"
	at com.azure.communication.callautomation.models.CallingServerErrorException$1.create(CallingServerErrorException.java:65)

Expected/desired behavior

The recording should start without any error

OS and Version?

Mac OS X 12.6.2

Versions

1.0.0-beta.1. but I also built 1.0.0-beta.2 from the GitHub as of today and that fails too.

Mention any other details that might be useful