Unexpected IncomingCalls behaviour....More of a question

Describe the issue
When making a Teams call between two users where one of the users has the recording policy applied, it appear that the graph framework sends multiple messages to the PlatformCallController on the “api/calling” endpoint. The call IDs of the calls all differ within every received message.
This behaviour results in multiple firing of the CallsOnUpdated() within bot.cs whereby callhandlers are instantiated (and disposed) for what appears to be phantom calls.

Code Snippet
N/A

Expected behavior
When receiving a incoming call notification I expect ALL messages to pertain to a single call. Meaning that the call ID and other info is identical in all subsequent resends. Therefore meaning the repeated resends are done with a perspective as being synonymous with a ringing phone, i.e. happens for approx. 15 seconds before forwarding to voicemail..

So the question…………why am I seeing this behaviour? What’s the significance of the changing call ID’s from the series of incoming call requests?

Start with the PlatformCallController handling of the api/calling endpoint and follow how incoming notifications reach CallsOnUpdated() in bot.cs. Compare the received call IDs and their handling to determine whether the repeated messages represent separate calls; done means explaining the changing IDs and the resulting handler lifecycle.