Participant Invite timeout does not get processed by the CommunicationsClient

Describe the issue
The “CommunicationsClient” stops processing “InviteParticipantsOperation” on “OnNotificationProcessed” after 30 seconds. This is a problem for us because it can happen that an Invite to a Teams user can take more than 30 seconds to reject if that user desires so. Be it that the user waits longer to reject the invite or that the user does nothing at all and the Invite fails automatically after 60 seconds.

The scenario is a follows:

1. PSTN phone calls our Teams Bot
2. Call is established
3. Graph/Bot notifies our Callback URL about the established call
4. Our application invites a Teams user to the call
5. Invite operation becomes running
6. Wait 30 seconds
7. Exception from OperationManager.cs:245
   a. System.TimeoutException: Timed out while waiting for the operation with context [OperationId] to complete.
8. Wait another 30 seconds
9. Graph/Bot sends InviteParticipantsOperation failed for the invited participant (It timed-out)
10. Warning from OperationManager.cs:305
    a. Operation with context [OperationId] is not found. Ignoring request.

Expected behavior
Using JetBrains DotPeek we were able to see that de participants InviteAsync function has a hardcoded timeout of 30 seconds that we cannot configure/influence. The OperationManager also gets a default timeout of 30 seconds that we cannot influence.

It would help us significantly if we where able to configure the timeout as it would enable us to process failed invitations correctly.

Graph SDK (please complete the following information):
We are using the Microsoft.Graph.Communications.Calls (1.2.0.1702) NuGet package.

Review OperationManager.cs around lines 245 and 305 and the participant InviteAsync timeout described in the issue. Determine whether the sample can expose or configure the timeout, or whether the limitation is in Microsoft.Graph.Communications.Calls 1.2.0.1702; done means delayed invitation failures are processed rather than ignored.