Comms Release Log

From Taridium

(Difference between revisions)
Jump to: navigation, search
Line 31: Line 31:
This release provides initial support for a pass-through proxy. This allows for better scalability and NAT qualification handling. On the web side this release is primarily an UI upgrade with some minor component bugfixes.
This release provides initial support for a pass-through proxy. This allows for better scalability and NAT qualification handling. On the web side this release is primarily an UI upgrade with some minor component bugfixes.
 +
 +
== Release 3.0-e (Falernum) ==
 +
 +
{| class="wikitable" style="background-color:#ffffcc; text-align:left;"
 +
|-
 +
|Type
 +
|maintenance/zero downtime
 +
|-
 +
|Date
 +
|2017-02-03
 +
|-
 +
|Configuration Database Tag
 +
|5104
 +
|-
 +
|CDR Database Tag
 +
|5006
 +
|-
 +
|Released by
 +
|bdept@taridium.com
 +
|}
 +
 +
*; Security
 +
** Comprehensive SQL escaping has been expanded to authenticated pages including the administrator interface.
 +
 +
*; Admin
 +
** Fixes updates of music on hold directories when renaming an enterprise ID.
 +
 +
*; Enterprise
 +
** New Enterprise Contacts Feature. See Features > Contacts. Also supports CSV and vCard uploads. This directory is automatically added to End User and Phone directories. Caller ID names are also looked up on inbound calls.
 +
** Fixes conference name check and prevents duplicates. Duplicate conference room names could cause DIDs to become orphaned.
 +
** Fixes CDR export function when using a specific date range.
 +
** Support for enterprise CDR tables. Use $cfg['CDREntRecord'] and $cfg['CDREntDisplay'] to enable individual recording and/or display off the cdr tables. The CDR tables are named cdr_[enterprise ID]. Tables will have to be added for each existing enterprise and the 'comms' user will need CREATE TABLE permissions for new tables to be created when adding new enterprises.
 +
** Duplicate MAC address warnings now indicate where the MAC address is to be found when logging in as an ITSP user. Previously this would only be visible to admin users. Other users were only shown a generic duplicate warning. Only MAC address from enterprises within the same reseller will show and the user has to have ITSP login permissions.
 +
 +
*; End User Panel
 +
** New support for user supplied photo. See Voicemail > Settings. This photo will be used in phone directories where supported (currently Polycom only). Supported format 128x128 pixel GIF, JPG or PNG image.
 +
 +
*; ITSP
 +
** The ITSP panel now also shows the device list - if a restricted login is used (for example a reseller) then only relevant devices will be displayed. See Maintenance > Devices.
 +
 +
*; Switch
 +
** New star code: internal access to voicemail (direct to INBOX). This star code skips the folder selection and goes straight to the INBOX. PIN skipping and or mailbox+PIN requirements are the same as for the standard star code.
 +
 +
*; Polycom Provisioning
 +
** A dynamic 000000000000-directory.xml was added to the /ent/xml directory. This provides a simple Polycom XML directory that is dynamically created based on the IP address of the requesting phone. It can be specified in 000000000000.cfg like such: CONTACTS_DIRECTORY="http(s)://[server]/ent/xml/" Note that the phone needs to be registered prior to requesting the directory, or else an empty directory will be created.
 +
== Release 3.0-e (Elf) ==
== Release 3.0-e (Elf) ==

Revision as of 15:28, 3 February 2017

Comms-box.png

Versions apply to to core comms, switch comms-switch and web server comms-web RPM packages. Always check the current database release tags and run the database update with comms-config for both configuration and CDR databases.

Contents

Taridium comms 3.0

Version and support information:

Type major
Official Public Release 3.0-b (Bravo)
Date 2016-12-01
Supported Operating Systems RHEL/CentOS 5 (limited) & RHEL/CentOS 6
Supported Asterisk Versions 1.8 (limited) & 11
Supported Database Backends MySQL 5.5+ & MariaDB 5.5+
Expected EOL Q4 2018

This release provides initial support for a pass-through proxy. This allows for better scalability and NAT qualification handling. On the web side this release is primarily an UI upgrade with some minor component bugfixes.

Release 3.0-e (Falernum)

Type maintenance/zero downtime
Date 2017-02-03
Configuration Database Tag 5104
CDR Database Tag 5006
Released by bdept@taridium.com


Release 3.0-e (Elf)

Type maintenance/zero downtime
Date 2017-01-13
Configuration Database Tag 5103
CDR Database Tag 5006
Released by bdept@taridium.com


Release 3.0-d (Duncan)

Type maintenance/zero downtime
Date 2016-12-17
Configuration Database Tag 5102
CDR Database Tag 5006
Released by bdept@taridium.com


Release 3.0-c (Caligula)

Type maintenance/zero downtime
Date 2016-12-09
Configuration Database Tag 5101
CDR Database Tag 5006
Released by bdept@taridium.com

Release 3.0-b (Bravo)

Type maintenance/zero downtime
Date 2016-12-02
Configuration Database Tag 5101
CDR Database Tag 5006
Released by bdept@taridium.com

Taridium comms 2.5

Version and support information:

Type major
Official Public Release 2.5-a (Alpha)
Date 2016-05-20
Supported Operating Systems RHEL/CentOS 5 & RHEL/CentOS 6
Supported Asterisk Versions 1.8 (limited) & 11
Supported Database Backends MySQL 5.5+ & MariaDB 5.5+
Expected EOL Q4 2017

Release 2.5-k (Kilo)

Type maintenance/zero downtime
Date 2016-10-30
Configuration Database Tag 5101
CDR Database Tag 5006
Released by bdept@taridium.com

Release 2.5-j (Juliet)

Type maintenance/zero downtime
Date 2016-10-21
Configuration Database Tag 5101
CDR Database Tag 5006
Released by bdept@taridium.com

Release 2.5-i (India)

Type maintenance/zero downtime
Date 2016-10-14
Configuration Database Tag 5100
CDR Database Tag 5006
Released by bdept@taridium.com

Release 2.5-h (Hilo)

Type maintenance/zero downtime
Date 2016-09-16
Configuration Database Tag 5100
CDR Database Tag 5006
Released by bdept@taridium.com

Release 2.5-g (Glengoolie)

Type maintenance/zero downtime
Date 2016-09-02
Configuration Database Tag 5099
CDR Database Tag 5006
Released by bdept@taridium.com

Release 2.5-f (Foxtrot)

Type maintenance/zero downtime
Date 2016-08-20
Configuration Database Tag 5098
CDR Database Tag 5006
Released by bdept@taridium.com

Release 2.5-e (Echo)

Type maintenance/zero downtime
Date 2016-08-07
Configuration Database Tag 5097
CDR Database Tag 5006
Released by bdept@taridium.com

Release 2.5-d (Delta)

Type maintenance/zero downtime
Date 2016-07-22
Configuration Database Tag 5096
CDR Database Tag 5005
Released by bdept@taridium.com

Release 2.5-c (Charlie)

Type maintenance/zero downtime
Date 2016-06-18
Configuration Database Tag 5096
CDR Database Tag 5005
Released by bdept@taridium.com

Release 2.5-b (Bravo)

Type maintenance/zero downtime
Date 2016-06-10
Configuration Database Tag 5095
CDR Database Tag 5005
Released by bdept@taridium.com

Release 2.5-a (Alpha)

Type maintenance/zero downtime
Date 2016-05-20
Configuration Database Tag 5095
CDR Database Tag 5005
Released by bdept@taridium.com

Taridium comms 2.4

Type major
Official Public Release 2.4-c (Charlie)
Date 2015-08-07
Supported Operating Systems RHEL/CentOS 5 & RHEL/CentOS 6
Supported Asterisk Versions 1.8 & 11
Supported Database Backends MySQL 5.5+ & MariaDB 5.5+
Expected EOL Q2 2017

Release 2.4-x (X-Ray)

Type maintenance/zero downtime
Date 2016-05-06
Configuration Database Tag 5094
CDR Database Tag 5005
Released by bdept@taridium.com

Release 2.4-w (Whisky)

Type maintenance/zero downtime
Date 2016-04-22
Configuration Database Tag 5093
CDR Database Tag 5005
Released by bdept@taridium.com

Release 2.4-v (Victor)

Type maintenance/zero downtime
Date 2016-04-15
Configuration Database Tag 5093
CDR Database Tag 5005
Released by bdept@taridium.com

Release 2.4-u (Uniform)

Type maintenance/zero downtime
Date 2016-04-09
Configuration Database Tag 5092
CDR Database Tag 5005
Released by bdept@taridium.com

Release 2.4-t (Tango)

Type maintenance/zero downtime
Date 2016-04-01
Configuration Database Tag 5092
CDR Database Tag 5005
Released by bdept@taridium.com

Release 2.4-s (Sierra)

Type maintenance/zero downtime
Date 2016-03-18
Configuration Database Tag 5091
CDR Database Tag 5005
Released by bdept@taridium.com

Release 2.4-r (Romeo)

Type maintenance/zero downtime
Date 2016-02-21
Configuration Database Tag 5090
CDR Database Tag 5004
Released by bdept@taridium.com


Release 2.4-q (Quebec)

Type maintenance/zero downtime
Date 2016-01-29
Configuration Database Tag 5089
CDR Database Tag 5004
Released by bdept@taridium.com


Release 2.4-p (Papa)

Type maintenance/zero downtime
Date 2016-01-24
Configuration Database Tag 5088
CDR Database Tag 5004
Released by bdept@taridium.com


Release 2.4-o (Oscar)

Type maintenance/zero downtime
Date 2016-01-09
Configuration Database Tag 5088
CDR Database Tag 5004
Released by bdept@taridium.com





For prior release information, please contact support@taridium.com.

Personal tools
Namespaces
Variants
Actions
Toolbox