As of January 2019 Far South Networks began shipping all Wanderbox products featuring the latest Com.X Revision 1.5 software (rev. 1.5).
While we have tried our best to maintain consistency between rev. 1.4 and rev. 1.5 platforms, the new rev. 1.5 software offers many additional benefits to PBX system administrators and new features to PBX users. There are a few notable changes to some features that were already present in rev. 1.4 software.
The section below captures all new rev. 1.5 software features and changes.
This section is highly recommended reading for all certified PBX technicians having previously completed Level 1, Level 2 or XCT technical training on Com.X Revision 1.4 software based PBX products.
Rev. 1.5 sees the introduction of the comma-healthcare suit. Comma-healthcare is a tool provided to allow recovery and re-installation of Wanderbox devices . Through comma-healthcare, administrators are able to:
The backup and restore tool has undergone significant changes in the release of rev. 1.5. The system now automatically creates small daily backups, containing only the changes from the previous backup, as well as allowing for the creation of manual backups.
Daily backups are small in size, and can be used to restore a unit's configuration to a previous state. They can not be transferred off of the unit, or used on replacement devices. These backups contain only configuration, no CDR or logging data.
Manual backups can be exported, and restored on to replacement systems. Manual backups allow for the backing up of :
The addition of license file and log file backups in particular can be of great use in reducing turn around time on support cases.
Wanderboxes now allow console access on one of the external USB ports. This enables technicians to connect to the device over USB using putty or a similar program.
Amongst other new features, rev. 1.5 sees the introduction of a calendar tool. Calendars can be configured to control call flow, directing calls to different destinations depending on whether or not an event is scheduled at the time of the call.
It is possible to configure a local calendar, or to configure the PBX to synchronise with an Outlook calendar, a Google calendar or an Apple Calendar.
Calendar Event Groups can be created, allowing for events from multiple calendars to be grouped together, and for calls to be directed based on the events scheduled in multiple calendars.
A calendar can be included in a time condition to control calls on an inbound route, or a calendar can be included in a user's Follow-me, enabling follow-me when an event is scheduled in the calendar and disabling follow me when no event is scheduled.
Time conditions can now be configured to synchronise with a calendar or a calendar event group, in order to direct calls differently when events are scheduled. Details on associating time conditions with calendars rather than time groups are provided in this article.
Outbound routes can now be associated with time groups. This allows for outbound routes to be time sensitive. Being enabled at certain times, and automatically deactivated at a particular time.
Details on using time groups to control outbound calls can be found in this article.
A user control panel is included in software rev 1.5. A user is able to log in using their extension number and voicemail pin. From the user control panel, a user is able to access several widgets, including:
From the contacts widget users are able to add and delete contacts. They are also able to group contacts, and indicate whether contacts are personal contacts, or whether they should be visible to all users.
The call recording behaviour has been adjusted. Call recording control is now available at each possible destination or feature. This allows for recording to be enabled or disabled at any point during the call flow. The default behaviour is identical to that in rev. 1.4, but a great deal more flexibility has been added.
A guide to using call recording on rev. 1.5 is available here.
The behaviour and configuration of queues has only undergone minor changes, the most significant of which being that dynamic agents now need to be defined. However, the layout of the queue configuration menu has changed, and where all options used to exist in one menu, the same options are now distributed over a few sub-menus.
It is recommended that technicians read over these changes to familiarise themselves before needing to configure a queue on a rev. 1.5 device.