OneContact PBX 3.2.0

Release Details

Release Date

June 29, 2018

Deprecated versions

3.1.0

 

Enhancements

Issues

 

Enhancement Details

Enhancement #94875

Title
Adapt Physical Sites to OneContact 3.5

Component
Service

Detailed Information
OneContact's reporting database has changed in version 3.5, which requires changes in OneContactPBX. OneContactPBX should have a new configuration to set the version of the OneContact being used, in order to adapt to any version.

Product Changes
A new parameter has been added to the advanced settings, OneContactVersion, which should be configured with the version of the OneContact being used by OneContactPBX (e.g. "3.5"). If this parameter is not set, OneContactPBX's physical sites may be used up to OneContact v3.4.

Enhancement #94876

Title
IM Reporting

Component
Service

Detailed Information
IM Server shall start recording reports of all messages sent. The report should contain the sender, receiver, message ID and date.

Product Changes
IM Server now logs all messages sent to the new table IMLogs. The report contains the transaction ID, sender, receiver, client and date.

Enhancement #95397

Title
Store caller's Asserted Identity in CDRs

Component
Service

Detailed Information
Start storing the caller's asserted identity in the CDRs, contained in the P-Asserted-Identity header, when the call comes from a trusted source.

Product Changes
Two new columns have been added to the CDR table - FromAssertedUser and FromAssertedHost. They shall be filled with the user and host of the caller's PAI header, respectively, when the call is received from a trusted gateway.

Enhancement #94878

Title
Missed calls notifications for HGs

Component
Service

Detailed Information
OneContactPBX shall notify all users belonging to a HG when a call to their group is missed. Notifications might be sent via SMS and/or email.

Product Changes
It is now possible to configure groups to be notified when a call is missed. The notification can be sent via SMS and/or email to all members of the group.
In order for this feature to work, it is necessary to configure a new advanced parameter - MissedCallsNotifierApiAddress - with the address of the web service responsible for sending emails and SMS.

Enhancement #94603

Title
URL encode filename

Component
Service

Detailed Information
URL encode filename when inviting OneMedia.

Product Changes
Added parameter "EncodeRecordingFilename" to configurations (advanced settings).
If this parameter has value false then OneContactPBX does not encode the filename when inviting OneMedia.
In any other case, OneContactPBX encodes the filename when inviting OneMedia.

Enhancement #93100

Title
Internal number (short number) in IVRs

Component
Service

Detailed Information
The client desires to have IVRs with internal numbers. This is useful, for example, to build a more complex IVR where one option delivers to another IVR.

Product Changes
Added column "IvrNumber" in IVR table in Provisioning database.
IVRs can be reached by that short number from an internal extension.

 

Issue Details

Issue #93822

Title
Routing profile: voicemail in transfer not working

Component
Service

Detailed Information
Routing profile: voicemail in transfer not working. Call is not delivered in any phone but in origin it seems to be correctly calling. After some time, call is disconnected.

Reproduction Steps
1. Access hive portal
2. Define routing profile "always to ExtensionB" in extensionA
3. Define routing profile "always to voicemail" in extensionB
4. Make a call to extensionA
5. Call should be redirected to voicemail but this is not happening

Severity
High

Resolution
OneContactPBX redirects call to the correct voicemail.

Version Detected
3.0.1

Issue #93118

Title
Unable to blind transfer a recorded call to an external number with early media

Component
Service

Detailed Information
An Object reference not set to an instance of an object exception occurs while blind transferring a call from extension A to PSTN. The call had been established between A and B, and A had recording.

Reproduction Steps
1. A and B are OneContactUC
2. Enable recording in extension A
3. Call is established between A and B
4. Extension A blind transfers to PSTN
5. Call in B incorrectly terminates

Severity
High

Resolution
Each Session Progress response was firing a new call to the target. OneContactPBX is now processing Session Progress responses correctly during recorded transfers.

Version Detected
2.2.8.3

Issue #94686

Title
Unable to have a failover to an extension that has a "always forward"

Component
Service

Detailed Information
If an extension has a "failover forward" to another extension with a "always forward" to another extension the call is delivered in the correct extension multiple times.

Reproduction Steps
1. Access hive portal
2. Define routing profile "fail to extensionB" in extensionA
3. Define routing profile "always to extensionC" in extensionB
4. Make sure extensionA is not registered so the call fails
5. Call extensionA
6. Call should be redirected to extensionC one time but the call is delivered multiple times

Severity
Low

Resolution
OneContactPBX only redirects the call one time to the correct extension.

Version Detected
3.0.1