- 04 Feb 2021
- 11 Minuten zu lesen
Release Notes 64.0
- Aktualisiert am 04 Feb 2021
- 11 Minuten zu lesen
Version 64 comes with a major update to the Android app. The app now uses the app notification framework to notify users about incoming calls.
New interface. The app now has a completely revamped new interface that is much more functional, intuitive and sleek. The presence page is now front and center.
Wake up. To preserve battery apps are put in sleep or killed when in background. The app can now be woken up for incoming calls when it is not running or in sleep.
Proximity sensor. The app now uses the proximity sensor to turn off the screen when talking in handset mode to prevent against most inadvertent screen touches.
QR code login. Users can find the PBX and login to the app with the QR code of your user web portal or desktop app. This dramatically simplifies the signup procedure.
Google login. Users can now login with Google email accounts, as long as it is their email was set up on their PBX extension.
Bluetooth support. Users can use Bluetooth headsets for the app.
The PBX user interface is now also available as a standalone Windows application.
The PBX user interface is now also available as a standalone MAC application.
The PBX user interface is now also available as a standalone Linux application.
Completely revamped Android app with modern UI and updated notifications.
SMS and MMS support. Version 64 comes with support for SMS and MMS through the web frontend and through the Windows and Mac applications. Currently providers bandwidth, Telnyx and Inteliquent are supported.
Login. Login is a user state now. ACD management now has to make a decision who is currently agent of the queue; agents can make the decision whether they are taking calls or not. We might refine this in later versions, e.g. give control to the agent to what ACD they are logged in.
ACD manager. Extensions now has the attribute whether that extension can manage ACD. This replaces the listing in the ACD itself, which was considered hard to manage. There is already another flag if the extension has the permission to listen to recordings. It is envisioned that we will add another flag if the extension has the permission to manage the domain address book.
Zoho support. We have added support for the latest Zoho API. We are now waiting for Zoho to release the new software with the API.
Hunt groups. We have added a flag that tells the PBX to follow the redirect all settings of the agents. By default this setting is off to avoid confusion why extensions are receiving calls for a group where they are not agents. However there are situations when such redirects are desired.
ACD groups. Now it is easy to ask callers to leave a call rating at the end of the call. The login procedure for agents was brought more in line with call center software. Additional reasons and conditions are available to include additional agents for example when callers are waiting too long or too many calls are active.
Room cleanup code. The room cleanup code can now contain additional hints e.g. that the room needs an inspection.
Department field. We have added a field for the department, similar to the position. This field can be used to further describe where the account belongs to. The field is used to sort the account count on the domain status page.
OpenWRT MIPS support. We have added another target for the PBX. The PBX can now run on affordable routers.
Do not call. A do not call feature was added to the address book. This is useful e.g. in the European Union where customers can demand that they are not being called.
Disabling device types. It is now possible to disable calls depending on the device type. The PBX differentiates between app, mobile phone and desk phone. This will help avoiding unwanted and confusing call waiting on the same device, e.g. when the call arrives on the app and on the mobile phone as well and gives the user more control e.g. when traveling.
Video calls. Especially when using complex SDP with multiple video codecs the PBX could get confused about what ports to use. The new version passes the information through to the according media entry. RTCP ports are changed accordingly.
P-Preferred-Identity pass-through. Similar to the already existing setting for P-Asserted-Identity the PBX can now also pass the P-Preferred-Identity header through for internal calls.
Yealink DM. Yealink offers a new API that can store the passwords for the devices. Using this API, there is no need to open the account for provisioning any more; the device can be plugged in at any time. The new API requires that users obtain an API key from the Yealink web site.
Emails. The daily emails about the resource usage of the PBX was updated to use improved graphs. Some email servers were sending large responses that could break the SMTP client on the PBX; this has been fixed.
Software updates. On slow connections, software updates could fail because of timeouts even though the file download was still progressing.
DNS Server. We added a setting for the DNS server that will override the setting on the operating system.
Email. Emails are not put into an internal database, so that a restart of the system will not delete them. It also helps to reduce the memory for large systems with a lot of pending emails.
Swiss numbers. Added better support for Swiss numbers. Also it is possible to use tel.search.ch for looking up numbers on inbound calls.
Australian numbers. The support for Australian numbers was also improved.
New Zealand numbers. The support for New Zealand numbers was also improved.
Brazilian time zone. We have added the Brazilian times zones and worked on some translations for a better localization.
Call review. The audio prompts for the call recording review were producing confusing output which was corrected in version 64.
CSTA. SwitchingFunctionDevices was always using the first domain it found on the system, making this difficult in multi-domain environments.
Call recordings. There was a bug that could cause phone calls for hotel rooms to be recorded.
Blind transfer. A blind transfer into an extension that cannot accept more calls is now being rejected.
Vodia IOP. We have added a way to factory reset Vodia IOP through a specially prepared USB stick. This is useful when the administrator password was lost and SSH was not enabled. Also after a longer time of experimentation is seems that enabling the SSH access now works reliably.
Location database. Version 64 can either keep the location database local or sync it with the bandwidth API. The PBX can now use the PIDF-LO format.
Support for OpenCNAM. The PBX can nuw use the OpenCNAM to lookup the CNAM caller-ID of the caller.
FritzBox trunk. We have added a trunk for the FritzBox that avoids codec and other setup problems with the device.
CDR reporting. Many CDR values have been improved where times sometimes conflicted.
CDR details. When clicking on the CDR record in the domain view, the PBX now presents more details about the call. This includes the stages that the call went through, e.g. how the call was transferred. Also call recordings can be played back from the CDR interface.
Extension cleanup. There are now multiple options how an extension should be cleaned up, including resetting passwords, cleaning up voicemail, call history and resetting devices. This should make it easier to handle cases when employees leave the company.
Status graph. The graph now includes more details on the memory usage.
RPS synchronization. In the previous version refreshing the RPS server was all-or-nothing. This was not only causing a tremendous load on the system but made it virtually impossible to debug problems. In version 64, this can be done on per-domain bases (in the domain list view) and on extension level (in the page where the provisioning data is shown).
DID management. The DID management was moved into the trunk area. When a new trunk is set up, DID can be associated with the trunk now. There is a new page where domain administrators can easily assign numbers to accounts.
Service flag times. The web frontend can now better deal with unexpected input, e.g. missing years and times that end at midnight.
Queue (ACD) management. The new user portal has a revamped ACD management, with a lot more data shown for the queue as well as agents in more intuitive form, including graphs. Also more control and management of the queues.
New user portal. The new user portal is revamped to be more intuitive and functional. It also has many more features. Also a new CDR mechanism makes it much faster to report on all the data more quickly and efficiently.
Address book. Added user setting to allow write/edit permissions to the Domain level address book is being reflected in the Agent portal with appropriate tags.
Logo. The PBX can now provision the background image for most phone models. The web front end to upload the logo can now generate images for dark and light themes and it places the logo in the appropriate position for the used phone model. The logo can use a single color background or a background wallpaper image.
Syslog. The PBX can now try to provision the settings to have the phone send syslog messages to the PBX. These will be shown in the extension registration tab. This works mostly in the LAN where it is clear from what IP address the packets are coming. Syslog messages can help troubleshooting problems with devices without having to log in to the phones.
Dialog state refresh. It seems that several phones expect the PBX to send a NOTIFY after every refresh of the subscription. If that refresh is missing, some phones even turn set the BLF state to “off”. Although this causes additional and potentially a lot of traffic, the PBX now refreshes those BLF subscriptions.
Fanvil. The support for Fanvil phones was significantly improved. The PBX supports the new Fanvil models using XML templates and the older models using TXT files. BMP images are generated automatically for the background images. For most models, the button map was updated. Support for Fanvil provisioning was added, including provisioning of the usernames and password that eliminate the need to pair the devices manually. The LAN provisioning uses a new way to pair the devices making it possible to provision Fanvil phones in the LAN without having to touch the devices even in environments where no DHCP option 66 is available.
Yealink. We have added the DECT base station Yealink W80B and other models e.g. T23P.
Snom. The XML menu for the phones was broken and is working again in this version.
Grandstream. Grandstream has added a new MAC address range which is now included in the PBX. This should only be relevant when using the Grandstream cloud provisioning service. There were some additional fixes for the Grandstream remote provisioning tool.
Gigaset. The Gigaset RPS server also supports putting username and password into the server, avoiding the need to pair the device when it is plugged into the network. Auto-answer for the Maxwell phones was added.
Poly. When there is no line key, the phones would not register with the PBX. Because of this we will automatically add a line key to avoid this hard to find problem. Also we keep the name “Polycom” for now because changing the name would have a lot of side effects throughout the PBX.
Panasonic. We have added support for some Panasonic phones (KX-UT113, KX-UT123, KX-UT133, KX-UT136, KX-UT248, KX-UT670, KX-UTG200B and KX-UTG300B). Automatic provisioning and BLF is supported for those devices.
Additional Release Notes for 64.0.2
ACD: ACD was not reporting a missed call for agents that did not pick up the phone when redirect-after-timeout redirected the call.
Yealink: The new remote provisioning server API had trouble finding the right server. This was causing problems not on the first call, but on subsequent calls. It might be necessary to review the server list on the dm.yealink.com site to make sure that old servers are not cluttering the database.
Email client: There was a change in the TLS client that would send a client certificate when requested. Unfortunately for the Microsoft Office 365 email server, it did request a client certificate however in most cases it would not accept the PBX certificate and rejects the connection. In this new version, the PBX does not send a client certificate in this case.
Polycom: The Polycom VVX501 was somehow not on the list of supported devices and has now been put back on the list.
SIP tags: Some devices were not able to handle the way the PBX was using the tags in SIP dialogs. This was changed and should now work with most of the devices that support RFC3261.
Fanvil: The domain name was not provisioned for all devices. This was no problem in single tenant deployments, however it was causing problems in multi-tenant deployments.
SPAM detection: There was a problem with the Tellows API that was causing incoming calls to get rejected.
Websocket: The ping/pong message exchange was not very efficient and could cause problems with the Android app.
Grandstream: The new GRP26xx devices were missing a model and the provisioning of the credentials was improved.
User front end: The internal text messaging could under certain circumstances not work properly.