Restored Azure.Communication.CallAutomation 1.5.1 and coded answer, bidirectional media streaming, and participant transfer against it. The first build failed because CustomCallingContext is read-only, and the media content member was not the name first used. Package XML docs and a small reflection program showed AddVoip on the context object the getter already returns. The solution then compiled. No live call was placed.
- What worked
- The package restored cleanly, and its XML reference listed the public media-streaming and transfer members needed to finish the adapter.
- What got in the way
- Assigning CustomCallingContext failed because the property is read-only and the multi-argument constructor is internal. The media streaming member name also differed from the first call site, so the public surface had to be read out of the package docs.