Release Notes 5.2.1

User documentation
2018-06-14

Release Notes For Release 5.2.1¶

Initialization procedure was changed so that setConfiguration() always sends onSipStarted() to let the developer know when it is safe to call dial() and/or registerAccount(). See the Mobile Developer Guide for more details.

#864 General: in some use cases, calling dial() didn't perform the call as the SIP stack was not ready.
#603, #605 Android: allow to call setConfig() even with the SDK not initialized properly yet.
#780 iOS: Don't crash if the application uses Apple Reachability sample code.
#909 General: don't crash if the application uses invalid characters in login or password.

SDK cannot be initialized on an IPv6-only network with no IPv4 support and no NAT64
#426 - On Android, SDK cannot use NAT64 networks. This is a limitation of the operating system. Use dual-stack SIP servers to support IPv6 only clients.
#365 - WiFi to WiFi handoff can cause call to disconnect if the handoff is too slow (~30 seconds), especially using TLS transport.
#135 - DNS SRV isn't supported.

#368, #370, #509 - Some issues with handling hold/unhold state after a 2nd or 3rd concurrent call is hung up.
#482 - App does not implement ringing tone for the caller.
#443, #464 - When switching from registration to Registration-Free mode, application does not manage the registration state correctly. Restart application after changing registration mode to workaround the problem.
#346 - Reference application can't receive calls while settings menu is open.