## Web Browsers

WebRTC APIs are only available in [secure contexts](https://developer.mozilla.org/en-US/docs/Web/Security/Secure_Contexts) such as HTTPS or `localhost`. Ensure your application is served over HTTPS in production.

| Browser | Minimum Version |
| --- | --- |
| Chrome | 93+ |
| Firefox | 92+ |
| Safari | 15.4+ |
| Edge | 93+ (Chromium-based) |

## Mobile Browsers

Mobile browsers may have stricter autoplay policies for audio. Ensure that calls are initiated by a user gesture, for example, a button tap, to avoid audio playback issues.

| Browser | Platform |
| --- | --- |
| Chrome for Android | Android 93+ |
| Safari for iOS | iOS 15.4+ |
| Firefox for Android | Android 92+ |

## Runtime Detection

Use [`checkWebRTCSupport()`](https://docs.cognigy.com/click-to-call/sdk/api-reference/check-click-to-call-support) to verify browser compatibility at runtime before creating a client:

```
import { checkWebRTCSupport } from '@cognigy/click-to-call-sdk';

const support = checkWebRTCSupport();
if (!support.supported) {
  console.error('Missing WebRTC features:', support.missing);
} else {
  console.log('WebRTC is fully supported');
}
```

## More Information

- [checkWebRTCSupport](https://docs.cognigy.com/click-to-call/sdk/api-reference/check-click-to-call-support)
- [Security](https://docs.cognigy.com/click-to-call/sdk/security)
- [Troubleshooting — Click To Call Not Supported](https://docs.cognigy.com/click-to-call/sdk/troubleshooting#click-to-call-not-supported)