This file will serve as a reference point for upcoming announcements, both of the temporal nature (this library will be deprecated in 6 months) and version-specific (upgrading from X to Y will require A, B, and C).
To upgrade to Kazoo-FreeSWITCH 1.4.26+ or FreeSWITCH 1.6+ you must set the system_config/ecallmgr parameter use_kazoo_dptools to TRUE. Failure to do so may cause inconsistent channel information among eCallMgr nodes connected to the same FreeSWITCH instance. If you are using Kazoo-FreeSWITCH 1.4.x builds prior to .26 this parameter should be left as its default, FALSE.
The enabled Monster UI applications were moved from an object on the account document to its own document with the id apps_store. When you run sup whapps_maintenance migrate this will automatically preform this operation but until it is complete users logging into Monster UI may not see their previously enabled applications. Once the migration is complete the change should be transparent to end-users.
If you plan to support the new API to download the company directory as a PDF you will need to install 'htmldoc' on any server running crossbar.
The default ports that Kamailio listens to for the WebRTC websocket have changed, this was due to a port conflict on all-in-one installs with TLS enabled Kazoo APIs. The standard HTTP websocket port was 8080 and is now 5064. The TLS HTTP websocket port was 8443 and is now 5065. If you would like to continue using the old ports please update "/etc/kazoo/kamailio/local.cfg" after an update to kazoo-configs 3.22.12+
Starting with Kazoo 4.0 Erlang support will target 18+ and will not be backward compatible with prior Erlang versions.
Upgrading to 4.0 will shift number management from core/whistle_number_manager to core/kazoo_number_manager.
The upgrade process should be seamless from the user's perspective, with some exceptions:
- API calls for attachments and port requests all go to
cb_port_requests
Upgrading will change the way Kazoo interacts with CouchDB (including deprecating using BigCouch and recommending CouchDB!). For most operations, nothing will be noticeably different.
currently, inbound calls from carriers don't have a Authorizing-ID but if the device has a redirection the CDR will have the Authorizing-ID header. this will change in version 4 as we believe the inbound leg should not have the Authorizing-ID set, so the CDR for inbound call (leg a) will not have the Authorizing-ID. The b-leg will have the Authorizing-ID set to the device that redirect the call. Restrictions will still be applied based on the device that redirected the call.
Most operations have been moved to the Cowboy or Cowlib projects. We will formally remove mochiweb from deps/. If you maintain code apart from Kazoo that uses mochiweb, please either covert to equivalent functionality with Cowboy/Cowlib or plan how you'll build your custom code with your own dependency of mochiweb.
exmpp library has problems restarting. it will be replaced by deps/escalus
ibrowse will be replaced by core/whistle_web/kz_http which is using Erlang httpc. kz_http is the new HTTP client module now and the previous kz_http module is renamed to kz_http_util.
If you maintain code apart from Kazoo that uses ibrowse, please either covert to equivalent functionality with kz_http/httpc or plan how you’ll build your custom code with your own dependency of ibrowse.