Countries:

Professional Services » Knowledgebase » Release Notes 3.4.0

	Release Notes 3.4.0

Article

V3.4 Release Notes

Agent Group

There was a common complaint that the PBX would disconnect the call if a ringing agent does not pick up the call within a minute. The reason for this was that the PBX automatically detects an unconnected call and treats this as error condition or the endpoint itself would stop ringing and disconnect the call. The new approach ignores such events and calls the agent again. This will make it possible to keep the phone for a long time, e.g. two hours.

When none of the agents are registered (e.g. because of a disconnected Internet line for hosted customers), the PBX would keep the callers in the queue until at least one agent registers again. There is now a new code for a service flag that turns on when none of the agents is registered, so that the agent group can trigger a redirection to an external number, for example a cell phone for emergency service.

We also added a new feature code that is able to set the redirection of the agent group from a phone. The "redirect all" feature was already available for regular extensions; however it was not possible to redirect all calls for group. This new feature code essentially set the night mode destination for a service flag with the name "#t" (true). Because this is a star code, it can be called from the mailbox account for users that are outside of the VoIP network, for example from the cell phone.

The CDR got confused when an agent performs an attended transfer. The call would not show up in the call statistics for the agent group.

Auto Attendant

The input fields in the direct destinations were not adjusted to the country code style. That made it difficult to enter the redirection number.

When calling from a cell phone, the user can now also receive a callback. This makes it possible to minimize the cost for the cell phone calls. This is important when the cell phone belongs to the employee and not the company and it also has benefits in certain countries where making cell phone calls are more expensive than receiving cell phone calls.

Extensions

The hot desking could mix the different account types up. This was a problem in the database search, where the PBX did not verify that the search result was an extension. The behavior could be that a call to a hunt group would also call extensions that are not related to the called destination number.

Administration

We added more flags that control what permission the domain administrator has. This is essential for the self-administration in hosted environments, where the provider wants to control what features the domain administrator can see. These features include the possibility to edit trunks, edit the dial plan or delete or create accounts.

The web interface backup was originally designed for the backup of small embedded devices where file system access is difficult. However, it became an important tool for moving domains. We experienced a problem when the domains became too big. There was a hardcoded limit of 16 MB for web-based up- and downloads. We made this limit a soft limit that can be changed in the configuration file.

Linux systems reports a "file size exceeded" by sending a signal to the PBX process. This typically happens when the PBX would write large log files, especially when the log rotation is not being used. The default handler would create a core dump and terminate the process. This is not appropriate for a PBX service, so we added code that tells the operating system to ignore such an event and continue processing.

The recording locations were buggy. There was confusion in the file name about incoming or outgoing calls.

On the CS410, there was a mix of IPv4 and IPv6 addresses for NTP that could result in the loose of the time (the CS410 operating system actually does not support IPv6 yet).

The new version contains a setting under the domain to match the last 7 digits of the cell phone. By default, this feature is not used. But if you choose to use it, you should be aware that PBX could match 7 digits from a different area code also, resulting in unwanted behavior.

The issue of huge tar file has been fixed in the new version. We introduced a new global setting (‘max_tcp_length’) to take care of this issue.

Buttons

The buttons for a specific user can now also be changed by the domain administrator. This makes it a lot easier to make changes for a specific end user, without the need to log in as user.

We added a new redirect button mode, where the office user can redirect all calls to a preprogrammed destination by just one button click. This is a popular secretary-boss known from legacy PBX systems.

The DND button mode was buggy. It could happen that the display of the DND state was not working properly.

Trunks and Dial Plans

There are trunks that require DTMF transcoding, where the PBX needs to detect the DTMF tone and send it as out of band DTMF. This is for special devices like external voicemail systems that are not able to detect inband tones. We added a setting to the trunk that turns this behavior on.

For outbound calls in the ROW mode there was a bug in the number representation that could result in a "0" as the destination.

The "call extension" mode in the dial plan can now actually also call other accounts, for example hunt groups.

Provisioning

The provisioning of the tone scheme was buggy and should be fixed now.

The transport layer provisioning for the snom phones wasn’t working properly and is fixed now.

Web Interface

It is now possible to log in with the DID number. That makes it possible for hosted customers to log in without knowing their domain name. It is also possible to log in with the company's main number and the extension number.

For upgrade licenses, the PBX now shows the upgrade date in the web interface.

The CS410 web interface has a problem with the replication of the IP address settings into the operating system files. This is an important fix for CS410 users.

Issue saving the codec preference under the admin->settings->ports page is fixed.

Media Subsystem

The length indication in the WAV recording file could be wrong. Although most tools were able to play back the files, some tools were complaining about it.

DTMF tone recording could be buggy ("farting tones"). Although we were not able to 100 % track down the problem, we did some improvements in this area.