FAQ

Using PBX is strongly recommended but not obligatory, SDK can make direct calls with other SIP clients.

Simply append to domain name colon and port number . Example: 'server:port'.

Yes, SDK has these features.

As long as you need.

Yes, SDK allow to use encrypted SIP signaling over TLS and encrypted audio/video over SRTP.

Yes, source code of example applications is available in public repositories on GitHub

Yes, SDK allows making outgoing calls without registration

Yes, SDK allows to make direct calls.

SDK is based on the 'reSIProcate' and 'webrtc'.

Yes, SDK will work good in LAN without Internet, but this mode requires more efforts when required push notifications for iOS/Android.

No, current version can't work without audio devices. Working on update which resolves that.

As many as required.

Yes, SDK provides ability to send push token with REGISTER request and also updates registration when application has been woken up by push.

Yes, SDK provides methods for activate/deactivate audio session as requires CallKit and also provides ready to use implementation as part of example app.

SDK built as native library and doesn't depend on the version of .net.

Depends on the programming language and platform, it's bundled into compiled application or requires to copy 1 or 2 binary files along with application files.

Yes, we provide iOS SDK build for x64, arm64 for device and emulator.

Any language/IDE which allows to use platform native libraries (dll/framework/so).

No, SDK for Windows can be deployed on clients’ computers by just copy 2 dll files.

SDK doesn't have limitation for the number of calls. It depends on the network bandwidth, CPU power, etc.