OneContact PBX 3.1.0

Release Details

Release Date

June 25, 2018

Deprecated versions

3.0.0

 

Enhancements

Issues

 

Enhancement Details

Enhancement #53890

Title
Inactivate clients

Component
Service

Detailed Information
Cloud portal can set a flag to inactivate a client.
This should prevent any user from registering in OneContactPBX and inbound calls should be rejected.

Product Changes
OneContactPBX API can now activate or deactivate a client.

Enhancement #92198

Title
Support IVR with multiple DDIs

Component
Service

Detailed Information
It should be possible to associate several DDIs to an IVR extension. Currently, each IVR extension can only have a single DDI associated with it.

Product Changes
Each IVR can have multiple DDIs associated.

Enhancement #92199

Title
Control the number of calls in IVR extensions

Component
Service

Detailed Information
Make it possible to configure a maximum number of concurrent calls in each IVR extension.

Product Changes
Each IVR can have a property MaxCalls that limit the number of concurrent calls that can be made to that IVR.

Enhancement #93391

Title
Support Voicemail using balanced OneMedias with different storages.

Component
Service

Detailed Information
Voicemail does not support balanced OneMedia's with different storages. It should be changed so that it starts supporting.

Product Changes
Voicemail supports different OneMedia's with storages in different physical locations.

Enhancement #19423

Title
Contacts Directory should be available in Hard Phones

Component
OnePBX

Detailed Information
Make it possible to auto provision contacts (phonebook) in hard phones.

Product Changes
Some hardphones (AudioCodes, Cisco, Htek, SNOM and Yealink) can now autoprovision phonebooks. The templates for were modified.

 

Issue Details

Issue #94534

Title
Extension exception numbers don't work

Component
OnePBX

Detailed Information
When having all calls to extA being forwarded to extB and placing an exception number (extC) the calls from extC to extA should ring in extA. This call does not occur (neither in extA nor in extB).

Reproduction Steps
1. Hive/Users&Teams/Users/extension/Forwarding
2. Go to User Unconditional Forward card and select "Forward all calls to destination number"
3. Establish the destination number (extB) below
4. In Exception Numbers card set a number (extC)
5. Placing a call from extC to extA: ext A is not ringing

Severity
High

Resolution
OneContactPBX now applies the exception numbers. If extA forwards all calls to extB and has an exception number extC, the calls made by extC to extA will be delivered to extA by OneContactPBX.

Version Detected
3.1.0

Issue #93298

Title
Not possible to forward a call from a sequential HG to another group via schedule

Component
Service

Detailed Information
OneContactPBX is failing to apply the forward rule of a sequential Hunting Group's schedule when the target number belongs to another sequential group.

Reproduction Steps
1. Go to PBX portal
2. Have two sequential hunting groups created: A and B
3. In group A, define a schedule rule to forward to hunting group B
4. The call is not established

Severity
High

Resolution
OneContactPBX now correctly forwards the call to the number configured in the schedule rule.

Version Detected
2.2.8.3

Issue #82605

Title
Pending calls are always delivered to mobile Apps if push notification fails

Component
Service

Detailed Information
If a call is made to a mobile App which is in the background, OneContactPBX sends a push notification to alert the App of the incoming call. However, if this push notification fails to be sent, the App is not alerted and some time later, when the user brings the App to the foreground, OneContactPBX will deliver the pending call, even if the caller already cancelled it.

Reproduction Steps
1. Create an extension (A) of type "Mobile App"
2. Make sure that push notifications are not working (e.g. remove the certificate)
3. Login in A and then put the App in the background
4. Make a call to A. Nothing should happen in A because the push notification failed to be sent
5. Cancel the call
6. Bring the App to the foreground and verify that it starts ringing with a call from the number which made the call in step 4

Severity
Medium

Resolution
The program can now catch the exceptions thrown and thus does not add the notification. When the App is brought to the foreground, the call will appear in the history as a "missing call" and will not ring.

Version Detected
2.2.5.0