Skip to main content

Custom encryption

The public APIs exported through NexconnCall.h do not currently expose a dedicated configuration object or registration method for custom media encryption or decryption.

Facts confirmed by the current public API​

  • NCCallEngine exposes a local video frame capture callback through setVideoFrameCaptureDelegate:.
  • NCCallEngine exposes a local audio frame capture callback through setAudioFrameCaptureDelegate:.
  • NCCallGroupStatusMessage includes an encryption-related status field, but it is not a public encryption API that the app layer can configure directly.

Current documentation guidance​

If your goal is to inspect locally captured frames, use the capture delegates:

Objective C
[[NCCallEngine sharedInstance] setVideoFrameCaptureDelegate:self];
[[NCCallEngine sharedInstance] setAudioFrameCaptureDelegate:self];

These callbacks are useful for debugging, observation, or custom data processing, but they do not mean that the current Call SDK publicly supports configurable custom encryption.

The current public headers do not directly confirm:

  • How to register a custom encryptor or decryptor through the public NCCall API
  • Whether different encryption strategies are supported for audio and video
  • Which RTC server-side capabilities are affected after encryption is enabled
Last updated on