Release Notes For Release 5.2.14¶

New Features¶

New Workflows and Workflow Configuration¶

Starting with release 5.2.14, Cloudonix SDK allows the application to specify which of the supported voice communications workflows should be used.

A new RegistrationData field workflowType allows the application to specify one of the following workflow types to be used with the configured account:

• WORKFLOW_TYPE_AUTODETECT - automatically select between Classic SIP Registration and Cloudonix Registration-Free, as in previous releases. This is the default configuration.
• WORKFLOW_TYPE_REGISTRATION - use Classic SIP Registration, with active registration management.
• WORKFLOW_TYPE_REGISTRATION_FREE - use Cloudonix Registration-Free dialing and call reception using push notification and one-time call tokens.
• WORKFLOW_TYPE_REGISTRATION_LESS - use the new Registration-Less workflow, for classic SIP style dialing without active registration management and without being able to receive calls.

Issues Fixed¶

General¶

• #918: User name is not sent in Re-INVITE after a network change.
• #919: Setting a TURN server address with a specific port causes DNS resolution to fail.
• #1502: RTP/RTCP ports should use new high port numbers for each call.
• #1552, #1564, #1630: Network change handling improvements
• #1587: Support "Registration-less mode" for dialing without using registration.
• #1650: loss of audio when switching networks
• #1677, #1681: When callee in registration mode perform network switch, audio is lost due to failure to authenticate re-invite

iOS¶

• #285: Setting audio route to Bluetooth and back multiple time causes a crash.
• #562: Crash when omitting account configuration fields.

Android¶

• #466: Application calling addEventsListener() multiple times can lose events.
• #604: Crash during automatic audio route change.
• #913: Background service restarted periodically although not using registration.
• #915: Crash during service restart after idling.
• #1579: Support Android 8.1

Known Issues¶

Mobile SDK¶

• 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 the call to disconnect if the handoff is too slow (~30 seconds), especially using TLS transport.

• #135 - DNS SRV isn't supported.