April 14, 2022
Improved
New logging was added related to Java operations, including initialization and screening.
Fixed
The application was unable to retry initialization if it failed.
If a Service Provider was not found in the settings cache during a call, the application did not add them.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart Platform on each AS.
February 22, 2022
Fixed
Existing Service Providers did not have the default timeout values for the Audio Captcha screening rule after an upgrade.
Calls to the Audio Captcha screening rule resulted in error log messages.
Dialed digits were detected during audio prompts for the Audio Captcha and Recorded Greeting screening rules, causing incorrect call handling.
The inter-digit timeout for the Audio Captcha screening rule did not work as expected.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart pcs.xml in Console on each AS.
February 17, 2022
New
- Added new configuration options to the web UI and API for the Audio Captcha screening rule.
The pass and fail treatments have custom audio options that will play after the digits have been processed.
There are settings for the first digit timeout, interdigit timeout, and number of retries allowed.
Fixed
The country code was incorrectly being removed when building the calling number in AIN.
The pcs-refresh-cdrs script would not complete successfully due to an existing pid lock file without a matching process.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart pcs.xml in Console on each AS.
February 9, 2022
Fixed
The Recorded Greeting screening rule did not screen the called number of an AIN call properly.
General improvements to the layout of the Screening Rules page.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart pcs.xml in Console on each AS.
February 7, 2022
Fixed
If more than one country code or SIP IP address was added for Service Selection Criteria, the list could then not be cleared completely.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart pcs.xml in Console on each AS.
February 2, 2022
Improved
Reduced the Recorded Greeting screening rule menu timeout to 5 seconds.
Fixed
The default Recorded Greeting screening rule menu continued to play after the called party dialed ‘1’ to continue.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart Platform on each AS.
January 28, 2022
Fixed
The Drop Anonymous Calls setting could not be set using the API.
Changes to Service Provider settings were not always saved and applied.
After upgrading, configured point code and SIP address block settings were not migrated to Service Selection Criteria.
Changing a single Service Selection Criteria parameter with the API deleted other existing parameters.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart pcs.xml in Console on each AS.
January 18, 2022
Fixed
Leaving the point code range fields blank caused an error when attempting to save Service Selection Criteria.
The Retain Trunk Group ID setting was not applied to AIN call.
An AIN call from an anonymous caller showed errors in the AS log, and the call was not screened.
With an AIN call configured to have a ‘1’ added as a country code, when the call goes to the Audio Captcha screening rule, the Refer-To contained the original called number with a ‘1’ appended, but no ‘+’.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart pcs.xml in Console on each AS.
January 7, 2022
Fixed
There was a screening engine error during AIN calls caused by the source_ips being included when the value was an empty string.
The source_ips was incorrectly evaluated when provisioned as a single IP address.
There was a conflicting token use issue with the migration for Subscriber permissions.
The permissions check included Subscribers with entity entries for the pcs_view_screening_rule permission that were already correct.
Editing a Service Provider reset the screening rules to the default values.
Changes to Subscriber override settings could not be saved.
Calls were not dropped with the Drop Anonymous Calls setting enabled.
After an error from an invalid entry on the Service Selection Criteria page, valid point code entries were deleted. Now, any entries in the current criteria after the one that fails will not be saved, while the ones before it will. Also, criteria before the error will be updated, while criteria after will remain the same.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart Platform on each AS.
Restart pcs.xml in Console on each AS.
December 17, 2021
Fixed
There were some general issues with AIN number extraction.
Determining the number of screening rules to sort during a call did not work properly.
A Subscriber could not be created in the web UI when one or more screening rules were disabled.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart Platform on each AS.
Restart pcs.xml in Console on each AS.
December 15, 2021
Improved
A new migration adds screening rules to drop anonymous calls for existing Service Providers.
General improvements to AIN number extraction.
Fixed
Service Providers could not always be created after a fresh installation.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart pcs.xml in Console on each AS.
December 14, 2021
New
Added the service_selection_criteria endpoint to the API.
Improved
General improvements to the web UI for Service Selection Criteria.
Fixed
Service Providers could not be provisioned.
Issues with AIN number extraction prevented the application from starting successfully.
The delete rules created during migrations were using the wrong group name.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart Platform on each AS.
December 10, 2021
New
Added support for provisioning Service Selection Criteria which are used when there is no matching called number already provisioned.
- Added support for AIN number extract.
National numbers will have a country code of 1 added to the number object.
International numbers will have an E.164 country code removed from the digits and added to the number object as a country code.
Improved
The Drop Anonymous Calls setting is now treated like a screening rule during call flow.
Termination_Attempts to the application now go through number extraction to parse the country code.
The CDR Materialized View is now created in a migration, removing the need to run the script as part of installation.
Fixed
Values for Calling and Called Number were not consistent in CDRs.
Subscribers could not override screening rules.
Subscribers could not be created if the override field was included.
Subscribers with numbers could not be restored.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart Platform on each AS.
December 3, 2021
Improved
General improvements to how the call flow checks for a whitelist or blacklist match.
The leading + is now explicitly removed from the digits field of the number object passed into the Screen function.
Fixed
There was an issue with the audio prompt for Voicemail treatment after Recorded Greeting.
Upgrade Procedure Notes
After upgrade installation, you will need to restart pcs.xml in Console on each AS.
December 2, 2021
Fixed
There was an issue with the install script.
Upgrade Procedure Notes
After upgrade installation, you will need to run the following command on both NIUs:
clear-web-cache pcs
December 2, 2021
Improved
Added script and cron task to clean media directories.
Restored functionality to parse Subscriber override value when provisioned as string/unicode.
Fixed
Called numbers without a country code returned an error instead of an empty treatment.
Upgrade Procedure Notes
After upgrade installation, you will need to run the following command on both NIUs:
clear-web-cache pcs
December 2, 2021
Fixed
There was an issue with Subscriber permission migration attempting to restore an archived permission to an active Subscriber.
December 1, 2021
Fixed
The Recorded Greeting screening rule menu failed for the called party.
There were issues with Subscriber permissions, resulting in incorrectly denied access to the application.
Identifying successful list matches was not working properly.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart Platform on each AS.
December 1, 2021
Fixed
Restore was not set to false when deleting archived orphan data during migration.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart Platform on each AS.
November 30, 2021
Improved
Updated internal components.
November 30, 2021
There was an issue when upgrading with possible blocked migrations.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart Platform on each AS.
November 30, 2021
There was an issue when upgrading with possible blocked migrations.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart Platform on each AS.
November 30, 2021
Fixed
There was an issue when upgrading with possible blocked migrations.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart Platform on each AS.
November 30, 2021
Improved
Numbers must now be provisioned with country codes.
- The following improvements were made to screening group provisioning:
Screening groups can now have a parent group set that screening rules are inherited from.
Subscribers can now add a delete rule to their screening group to deactivate parent rules.
Screening groups can now be determined using an originating point code or source IP address.
Fixed
There were issues with the Recorded Greeting screening rule playing incorrect or missing audio prompts.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart Platform on each AS.
November 22, 2021
Fixed
There were general issues found related to uploading and managing custom audio files.
There were errors when setting up menus for the Recorded Greeting screening rule.
Upgrade Procedure Notes
After upgrade installation, you will need to restart Platform on each AS.
November 18, 2021
Improved
Added default prompts that will be heard when there is an error with a custom audio file.
Upgrade Procedure Notes
After upgrade installation, you will need to restart Platform on each AS.
November 17, 2021
New
Added support for uploading and managing custom audio prompts to apply to the Audio Captcha and Recorded Greeting screening rules.
Fixed
If records had the same name, they were not restore or purged properly.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart Platform on each AS.
October 29, 2021
Fixed
When an IN/CAMEL call had the Recorded Greeting or Audio Captcha screening rule enabled, the INVITE/REFER was sent to the incorrect number.
When multiple IP/hosts were listed in the Database Address field of the TNS Call Guardian screening rule, a call did not advance to the next IP after receiving a “No Route from Host” error.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart pcs.xml in Console on each AS.
July 20, 2021
Fixed
Updated internal components to address issues with orphan data when deleting whitelist/blacklist entries.
Additional Data is now stored separately for each rule in the rule tables to address an issue where cascading to the additional data table was removing entries incorrectly.
Upgrade Procedure Notes
After upgrade installation, you will need to run the following command on both NIUs:
clear-web-cache pcs
June 22, 2021
Fixed
Settings could not be saved when Use Contact Header was enabled.
The user part of the Contact header was incorrectly populated when a number could not be extracted from an INVITE.
Updated internal components to address issues with orphan data, not checking for Service Provider status when deleting a Subscriber, and the cleanup script running when no loggers had been configured or not completing.
Upgrade Procedure Notes
After upgrade installation, you will need to run the following command on both NIUs:
clear-web-cache pcs
June 14, 2021
Fixed
Updated internal components to fix migration issue preventing upgrades from some previous versions.
Upgrade Procedure Notes
After upgrade installation, you will need to run the following command on both NIUs:
clear-web-cache pcs
June 7, 2021
New
When a called number contains a country code, PCS will now prepend a plus (+) before the country code for outbound invites and redirects/refers.
When a routing prefix is set, it will be prepended before the plus (+) and to Request URI’s user part in a proxied INVITE.
Improved
General improvements to the web UI for consistency of information.
Made improvements to performance on systems configured for SSL.
Settings for all Service Providers are now gathered and cached when starting up the app on the AS, and settings cached on the AS are only updated when they are changed.
Multiple versions of the same record can now exist in the archive database.
Added several additional timeouts to Java calls to avoid consuming connections when the application has already moved on.
Media endpoints that are no longer used during a call are deleted.
PCS now handles all cascading Delete operations in the database.
The Egress Route setting is now run through simple validation to check that it is formatted correctly as a SIP URI without a user part.
CAPTCHA will now evaluate as soon as the correct number of digits are entered instead of waiting for a timeout.
The silence before playing the Recorded Greeting prompt has been reduced to 1 second.
Java files are now placed in a directory at /usr/sipxpress/apps/pcs/ rather than being bundled into a single .jar file.
PCS now follows redirects when proxying originating calls.
- Originating calls are now proxied based on the Route header.
If no Route header is present, PCS will use the Egress Route or Contact Header.
The new setting “Strict Router” will treat the Egress Route as a strict router, populating the Request URI based on the Called Number and Egress Route.
The new setting “Always Use Egress Route as Next Hop” will use the Egress Route as the next destination before any destinations in the Route header.
Fixed
There was an error with loading post-processing rules on the Settings page.
Changes to Called Source settings in the web UI had to be saved twice to apply to every AS.
Attempting to populate some settings generated an error.
The audio prompt during Recorded Greeting did not use a valid index.
There was an issue with the refresh-cdrs script properly closing lock files.
PCS did not correctly handle “archive” and “restore” parameters in URI if was explicitly set to false.
All relevant databases were not archived, purged, or restored in the same transaction, causing orphaned data.
Archiving a Service Provider did not also archive the Subscribers owned by that account.
Restoring or purging a Service Provider or Subscriber sometimes cascaded incorrectly.
There was an issue with the installation of refresh-cdrs cronjob, which prevented the job from running correctly.
Whitelist and blacklist weren’t evaluated if there were no entries for that list type.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart Platform on each AS.
February 2, 2021
New
A Service Enabled status column was added in the Subscribers table and is indicated by a green check mark or a red “X”.
Added “#” as a terminating digit for the Audio CAPTCHA rule, allowing a way to indicate dial complete other than waiting for the timeout.
When adding an Administrator in the web UI, usernames are restricted to lowercase characters.
Improved
The Tomcat references and configuration were unused and have therefore been removed.
Adding better error handling for screen responses.
The “pcs-refresh-cdrs” script now checks if the script is already running and if it is being run on the active NIU.
PCS now responds with 180 Ringing first when an INVITE is received.
Attempting to save an Origination Source with an empty Number Mask field will now correctly result in an error.
After saving an Administrator, the user will not be automatically returned to the Administrators table.
Fixed
There was an issue with importing numbers and saving Called Number Source settings.
When a Subscriber was imported, the Service Enabled status was set incorrectly.
Exporting Origination Sources resulted in an error.
If no valid Called Number Source was found, the To header was incorrectly used by default. PCS now logs an error to the CDRs and uses the Request URI to continue the call.
With the Drop Anonymous Calls setting enabled, an anonymous call would terminate correctly, but the CDR events did not show “TERMINATE” as the last event.
After modifying Called Number Source settings in the web UI, the Save Changes button had to be clicked twice for the changes to apply.
Adding Subscribers and Service Providers would result in a hang on the loading screen if there was an error encountered and the error message could not be seen.
Importing Subscribers and Service Providers without an optional whitelist/blacklist was unsuccessful.
The Nickname column on the Numbers table could not be sorted and filtered properly.
With “Require Signature Present and Valid” enabled on a list rule, the rule would result in an error when evaluated during a call and the calling number did not match the list.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart Platform on each AS.
January 14, 2021
Fixed
There was an issue preventing CDR synchronization.
Upgrade Procedure Notes
After upgrade installation, you will need to run the following command on both NIUs:
clear-web-cache pcs
January 11, 2021
Improved
The Warning header was changed to 480 responses when unable to retrieve settings.
Fixed
There was an issue with the synchronize script entering a state of infinite looping.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart pcs.xml in Console on each AS.
January 8, 2021
Fixed
The Secure Keystore (SKS) was not updated to the latest version after an install.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart Platform on each AS.
January 8, 2021
Fixed
The shaken value in the Identity header was not surrounded by quotation marks.
Auth User processing was completed in the incorrect order, causing users to be provisioned with incorrect permissions.
There were issues with Postgres repository access.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart Platform on each AS.
January 7, 2021
New
Added support for handling CANCEL messages.
Added timeouts to all Drop-to-Java PACs.
Added more logging for errors in some PACs.
Fixed
Screen Java call was performed even if PCS had not determined that the call was terminating.
The terminate dialog PAC was being incorrectly used before the dialog was created.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart Platform on each AS.
November 11, 2020
Fixed
New numbers could not be added.
The Created and Last Modified columns on the Numbers page were not displaying the correct dates.
The Created By and Last Modified By columns on the Numbers page were not displaying the correct username.
Upgrade Procedure Notes
After upgrade installation, you will need to run the following command on both NIUs:
clear-web-cache pcs
November 5, 2020
Improved
The imsworkx-editor.js file was unused and has therefore been removed.
General improvements to the web UI for Called Number Source configuration.
Fixed
Called Number Sources configuration was incorrectly checked at the beginning of every call.
Prepending the country code was attempted even if one was not defined.
November 4, 2020
New
Number normalization configuration can now be done through the web UI using the new Called Number Source settings.
Improved
Error handling during provisioning to the screening engine.
Improvements to cache clearing for settings.
Fixed
PCS did not preserve From and To headers when making outbound calls.
October 13, 2020
Fixed
PCS failed to validate signatures returned by the SKS during STIR/SHAKEN termination when the signing request included decimals.
Known Issues
The SKS does not update to the latest version after an install.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart Platform on each AS.
October 13, 2020
Improved
Added specific error information to CDRs for invalid STIR/SHAKEN verification.
Fixed
Timestamp format when generating signature was incorrect, causing a mismatch.
Known Issues
The SKS does not update to the latest version after an install.
The SKS config-properties file is not preserved after an install.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart Platform on each AS.
September 28, 2020
Improved
Improved implementation of Certificate field behavior when waiting for SKS response.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Restart Platform on both NIUs.
Restart pcs.xml in Console on each AS.
September 23, 2020
Improved
ReINVITEs with no SDP can now be properly handled.
Upgrade Procedure Notes
After upgrade installation, you will need to restart pcs.xml in Console on each AS.
September 16, 2020
Improved
The Identity header was reformatted.
The Certificate ID column was added to Origination Sources table.
Minor edits were made to the help text on Origination Source page to improve clarity.
An error message is now shown when invalid characters are entered in the Origination Source Name field.
Origination Number Masks can now be deleted without error.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart pcs.xml in Console on each AS.
September 11, 2020
New
Supports array format for dest tn field in SHAKEN tokens.
Fixed
The SKS returned the full token in the signature field of the signing_request. Now, only the signature is returned.
SHAKEN CDRs were not correctly associated with the Service Provider, making them viewable by the Platform Owner only.
When functioning as an originating network, there was an error in the response message.
An origination source was not saved if the attestation level was set to “None - No Default Attestation”.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart Platform on each AS.
September 4, 2020
Note
This is a maintenance build that must be upgraded from PCS version 20.7-x or earlier.
Improved
Improvements to Screening Rules editor display for easier access to Save function.
Fixed
ReINVITEs sent by the called party before a B2BUA was established were incorrectly sent to the calling party.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart pcs.xml in Console on each AS.
September 3, 2020
Fixed
There was an issue with certificate info retrieval for origination sources.
Response code and attestation level were not returned to PCS.
Calls made using an origination source did not appear in the CDRs in the web UI. CDRs are now generated for successful signing and continue unsigned callflow behaviors.
September 1, 2020
Fixed
Testing for null variables with the SHAKEN screening query did not work as expected. The exception name is now included with exception message after signing errors.
The incorrect JSON was in the SHAKEN token payload.
The INFO parameter was parsed incorrectly.
There was an ID mismatch in the Certificate field when adding a Number Mask to an Origination Source.
B2BUA reINVITE variables were incorrect and the reINVITE was sent back to itself instead of to the far end of the call.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart Platform on each AS.
August 27, 2020
Fixed
Changes to the Keystore URL field were not saved.
Changes to the Number Mask field when adding an origination source were not saved.
Attempting to query origination sources during a call did not work properly.
Changes to screening rules, such as disabling, enabling, or reordering, were not saved.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart Platform on each AS.
August 25, 2020
Improved
Improvements to the overall display of Screening Rules and Origination Source Editor.
Keystore settings could now be managed independently of the Platform Owner.
The Certificate field for origination sources is now a dropdown menu that is automatically populated by the names of available certificates from the SKS if one is configured. Manual certificate entry is still supported as well.
Fixed
There were multiple issues causing the SKS to not work as expected.
The Number Mask field did not accept “x” as a wildcard.
Provisioning two ends of a range of origination IP addresses did not have full functionality and was therefore temporarily removed.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart Platform on each AS.
August 12, 2020
Fixed
Attempting to start the SKS via the
start-skscommand would result in the following error: “Could not find or load main class jar”.
- The following issues with origination callflow were addressed:
The Shaken Values query when determining origination was not working correctly.
CDRs did not contain attestation level information for origination calls when signing or error codes and exceptions when signing errors occurred.
- The following issues with origination provisioning were addressed:
Existing sources did not populate correctly in the UI.
Updating edited sources resulted in errors.
The provisioning UI did not check required fields or prevent the user from changing the name of an existing source.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart Platform on each AS.
August 3, 2020
New
Initial support for provisioning of Origination Sources.
Known Issue
The development for Origination Sources is not complete, and there are multiple issues with basic functionality that must still be addressed and support that still must be added.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart pcs.xml in Console on each AS.
Restart Platform on each AS.
July 24, 2020
Fixed
When the Recorded Greeting screening rule was enabled, reINVITEs did not work properly, which resulted in the call was disconnected.
Upgrade Procedure Notes
After upgrade installation, you will need to restart pcs.xml in Console on each AS.
July 23, 2020
New
Rebranded the web UI to reflect Evolve branding.
Fixed
Re-INVITES during a B2BUA were handled incorrectly.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart pcs.xml in Console on each AS.
June 19, 2020
Fixed
Python dependencies were not correctly installed on both NIUs, causing a failed software install.
Running materialized view script during installation did not start a temporary Postgres instance if the Platform was down.
The
imsworkx-pcscommand (a variant of theclear-web-cachecommand) was unused and therefore is no longer installed.The incorrect RPM was installed in pcs-callflow role. Now, the installer adds a local PCS repository which is used to correctly install callflow RPM.
Upgrade Procedure Notes
After upgrade installation, you will need to restart pcs.xml in Console on each AS.
June 17, 2020
Fixed
The pcs.dbconfig file was not being updated.
Upgrade Procedure Notes
After upgrade installation, you will need to restart pcs.xml in Console on each AS.
June 16, 2020
Improved
Made general improvements to the installation process.
Fixed
Archiving or purging would sometimes result in a permission error or orphaned data.
An attempt to save settings may have resulted in an error.
Upgrade Procedure Notes
After upgrade installation, you will need to run the following command on both NIUs:
clear-web-cache pcs
June 11, 2020
Fixed
Due to orphaned data, a Subscriber could not be edited if they were previously provisioned under a different Service Provider.
The routing prefix was added to the number in the To header of an outbound INVITE and caused routing issues.
Upgrade Procedure Notes
After upgrade installation, you will need to do the following:
Run the following command on both NIUs:
clear-web-cache pcs
Restart pcs.xml in Console on each AS.
May 6, 2020
Fixed
There were issues with certain Yum repositories.
Upgrade Procedure Notes
If upgrading from a version of PCS earlier than 20.2-1, you will need to run the following command:
rm -rf /usr/lib/python2.7/site-packages/virtualenv*
March 10, 2020
New
Added a setting to determine whether the primary Trunk Group ID is retained when a call is forwarded.
Improved
Removed scroll select for screening rule fields with dropdown menus.
- Updated the db-init procedure to match other applications. This update includes the following:
Jinja2 will now be installed on the secondary NIU to avoid errors with some cron tasks.
Installation will now start a temporary postgres when inserting default config to prevent installation failures.
Fixed
When logged in as a Platform Owner, the Maximum Inactive Days for Records and Minimum Password Length fields always displayed the default values even after being changed and saved.
Archiving and purging a single number caused orphaned data, preventing that number from being recreated and archived.
There was an issue with being unable to complete calls due to a connection failure.
February 19, 2020
New
Added internal DELETE endpoints in the Screening Engine to facilitate cascading of subscriber-owned data.
Improved
Updated the Apache configuration files and SSL configuration scripts and files.
Fixed
Archiving, purging, or restoring a Subscriber did not correctly perform the same operation on all of the associated numbers.
The Numbers screen did not display the total number of records in the table.
A number mask with optional digits did not process correctly.
November 12, 2019
Fixed
Upgrade installations were failing.
October 21, 2019
Fixed
Reversed changes related to imsworkx_apache_configuration.py made in PCS version 1.2-30.
October 18, 2019
Improved
Made improvements to database replication handling with customized data services implementation.
Dependencies
This software version must be installed with the Application Server version 4.5.35 or later. This version of the Application Server include improvements to HA.
Required ps_master_config.xml file changes in this release relative to releases using the 1.1.8 version of the Database Access Component.
October 15, 2019
Fixed
When extra lines have been added to the pcs-ssl.conf configuration file, the installation script imsworkx_apache_configuration.py for several Ansible roles and its components would fail.
October 10, 2019
Improved
After an update, exported CSV files are now preserved.
After the initial SSL configuration, the script no longer needs to be run again.
Archiving a number caused orphaned data, preventing that number from being re-provisioned and archived.
Using the point code or SIP address to determine the Service Provider was always being used even if a number was provisioned.
With a new installation of PCS, a Subscriber cannot be added from the UI or API and a “Permission check failed” message is given.
Updating from PCS version 1.2-19 fails. To fix this failure, the refresh-cdrs script is no longer run on the secondary NIU during install.
September 3, 2019
Improved
Screening Engine permissions have been removed.
Fixed
Service Providers could not be imported if they had empty point code or SIP address fields.
Attempts to import Subscribers did not complete successfully.
Updating from PCS version 1.2-19 required Platform on the primary and secondary NIUs to be restarted.
August 30, 2019
Fixed
Settings were incorrectly retrieved after a redirect from IN to SIP.
August 29, 2019
New
Added support for database connection pooling.
August 23, 2019
Fixed
After settings were saved in the UI, screening rules were reset to the default settings.
When determining the Service Provider based on the SIP Address, not all Via headers were checked for a match.
The default screening number was shown in the UI for newly provisioned Service Providers. This number is now hidden.
Administrators were not being saved to the database, resulting in newly created Service Providers being unable to log in.
Service Provider settings were incorrectly retrieved after a redirect from IN to SIP.
August 22, 2019
Improved
Added error messages when point code or SIP address settings are formatted incorrectly.
Fixed
Java processing of an IP address was using the wrong number to match for the Service Provider.
August 21, 2019
Improved
The origination table now uses bigint datatype for point code and SIP address range columns.
Made improvements to blank global whitelist and blacklist detection.
August 21, 2019
Improved
Added a tooltip describing the accepted formats for the Calling SIP Address Block field.
Fixed
Errors occurred in non-SIP cases due to the empty string. These cases are now populated with a default SIP address value to prevent these errors.
August 21, 2019
Improved
If the called number is provisioned under a Service Provider different than the matching one, the call will now be rejected with a “480 Temporarily Unavailable” response and a message in the Warning header indicating that there was a mismatch.
Fixed
Missing point code data was incorrectly provisioned as 0 instead of null.
Origination entries for existing Service Providers were not correctly provisioned.
August 20, 2019
Improved
- Service Provider screening behavior can now be determined based on a provisioned calling point code range or SIP address block with the following parameters:
If a Service Provider does not match, settings will be based on the called number.
If the called number is provisioned under a Service Provider different than the matching one, the call will be rejected with a “400 Bad Request” response.
If there is no match and the called number is not provisioned, Platform Owner settings will be used.
July 19, 2019
Fixed
Attempts to upgrade from PCS version 1.2-17 produced an error message based on migration issues in the Screening Engine.
July 18, 2019
Improved
Made improvements to the performance of provisioning Subscribers and numbers.
- The following improvements were made to the CDR Materialized View cron job:
The lock file is now stored in the /var/run directory.
Added flags to the curl command to navigate SSL redirect.
Fixed
The Call Guardian function was not called in the CAMEL path.
June 14, 2019
Improved
When configuring multiple database addresses for the TNS Call Guardian screening rule, spaces within the comma-separated list will now be ignored.
Fixed
A screening rule that was configured with the “Next Rule” treatment option and required a valid signature was not evaluated correctly.
June 5, 2019
Improved
- The following improvements were made to the TNS Call Guardian screening rule:
Added a configurable timeout.
Added the ability to list multiple database addresses. Addresses should be a comma-separated list in the order that they should be attempted.
Made improvements to the display of additional CDR data.
Fixed
The CDR table cannot be filtered the ID or End Time columns.
The total number of CDR records was incorrect because the role and filter conditions were not considered.
- There were the following issues when importing or exporting the Job Logs table data:
Jobs were not always listed in the correct order. They are now always sorted by created time, with the newest job first.
Only ten jobs were displayed in the log. Now all jobs are listed.
The Export Raw button was unnecessary and was therefore removed.
Call Guardian queries did not prepend 1 to a calling number as needed.
The exported file of an administrator shows “cc” instead of “pcs” in the permission field. Note that existing administrators will continue to have this incorrect permission until they are re-saved.
May 7, 2019
Fixed
Archiving Service Providers caused orphaned data if there was no subscriber_name.
May 6, 2019
Fixed
Archiving numbers caused orphaned data in the database when archived alone.
April 29, 2019
Fixed
The
refresh-cdrsscript was not using the virtual environment configuration, and there was an unused requests import.
April 26, 2019
Improved
Added more automation to SSL configuration.
Fixed
Archiving numbers caused orphaned data.
The implementation of certificates in the API was not correct.
There was too much time before a STIR/SHAKEN signature could be considered invalid or stale.
March 26, 2019
Improved
Made improvements to the CDR view including filtering and sorting, paging, and additional data population.
Added CAMEL timeouts.
Fixed
The cron job used global instance of RESTWorkX, which may not have always existed. Now, the application-specific instance is used.
The Clean function in the Screening Engine was not working properly. As part of the fix for this issue, the Screening Engine audit logs will now be saved to /var/opt/xpressworkx/app-manager/pcs/logs/audit-logs.
- There were the following issues with STIR/SHAKEN processing:
Errors in processing that identify the signature as invalid now return “invalid” instead of just throwing the error.
PCS now correctly parses the Identity header and determines if it contains a STIR/SHAKEN signature.
Now evaluates all relevant claims for validity.
February 20, 2019
Fixed
Call Guardian in IN was not being processed correctly.
February 20, 2019
Fixed
There were issues with the indexing of screening rules that affected media forwarding.
February 19, 2019
Fixed
There were issues with IN and CAMEL regarding redirect to SIP for media.
February 15, 2019
New
Added support for CAMEL Initial DP triggers.
Added manual ACK messages when establishing a connection between two existing SIP dialogs.
February 14, 2019
Fixed
P-Asserted-Identity was not parsed correctly.
ReINVITEs did not include the correct dialog SDP information.
February 12, 2019
Fixed
The Allow Subscriber Override option was missing from the STIR/SHAKEN screening rule.
The Recorded Greeting screening rule option to terminate with a solicitor message did not play the correct message.
When logged in as a Subscriber, edits to whitelists and blacklists were not saved.
There was unnecessary data in the Screening Engine when subscribers or numbers were deleted.
Redirect processing would sometimes result in an error message instead of a Forward_Call.
February 11, 2019
Fixed
The REFER path had missing variables.
The parsing of redirect information from Menu Builder was incorrect.
February 11, 2019
Fixed
The screening rules did not load properly when using Internet Explorer ®.
February 8, 2019
Improved
During call processing, log information now shows when a service is disabled.
Fixed
Some pages did not load properly when using Internet Explorer.
Calls that required media but did not get to Recorded Greeting were using the incorrect method of connecting to the called party. Now, REFER is used instead of B2BUA.
February 7, 2019
Fixed
The Global Whitelist was not displayed in the web UI.
When a personal whitelist or blacklist was disabled, it could not be properly reenabled.
February 6, 2019
New
Added STIR/SHAKEN signature validation as a screening rule.
Added the initial implementation for CAMEL.
Improved
The TNS Call Guardian screening rule can now have treatments specified per user.
Made improvements to Internet Explorer support.
Made improvements to the reINVITE callflow.
Made improvements to the handling of anonymous numbers.
Added migration support to the fix role_update function.
Added support for Levenshtein edit distance filtering.
Dependencies
This software version must be installed with Platform version 4.5.
August 15, 2018
Fixed
A Subscriber’s screening rules were followed even if their service was disabled.
The specified treatment for “If not matching” was not always followed for Whitelist or Blacklist screening rules.
When whitelists or blacklists are globally disabled, the Service Provider Settings screen would not load.
Text entered in the Content fields for Email Settings would not be saved.
Voice mail treatment did not function properly with REFER.
The Audio CAPTCHA screening rule would sometimes cause the application to send two INVITE messages to the called party.
Security settings configured in override.py did not accommodate null values.
April 26, 2018
Improved
Added support to handling numbers with a leading “+”.
April 23, 2018
Fixed
The Routing Prefix was not being used in outbound INVITE messages.
March 21, 2018
New
Added support for anonymous call detection and the ability to automatically drop calls from an anonymous number.
March 14, 2018
Improved
Updated CDR view queries.
March 12, 2018
Fixed
CDR synchronization did not work properly when used in conjunction with applications that use a previous version of CDR Service.
March 5, 2018
Fixed
The TNS Call Guardian screening rule was not functioning properly.
Platform Owners could not see all calls in the CDRs.
When the Reject With Media system setting was enabled, calls were terminated based on the screening rules but audio did not play.
The minimum length requirement for numbers did not allow numbers less than 10 digits long. This length requirement has been removed to accommodate international numbers.
When a number was purged and then recreated, it could not be archived.
Dependencies
The following is a new RPM dependency that must be installed:
postgresql94-contrib
January 22, 2018
Fixed
- There were the following issues related to CDR:
Users saw all records even when they were configured not to.
Exporting records did not work.
SIP calls were recorded incorrectly.
When calls failed the Audio CAPTCHA screening rule or did not match the Whitelist screening rule, they would continue even if the rule was set to terminate the call.
Archive pages did not have the options to purge or restore.
Redirects incorrectly returned a “301 Moved Permanently” message instead of a “302 Moved Temporarily” message.
January 18, 2018
New
Added support for SSL configuration.
Fixed
IN calling was not correctly screened and would default to authorize_termination.
SIP redirects from IN were not successful.
The Subscriber Number Lists did not display correctly based on the override setting.
The description of the TNS Call Guardian screening rule was not accurate in the UI.
January 12, 2018
New
Added CDR service and additional event logging throughout a call.
Added email configuration to the Platform Owner Settings, allowing them to use email messages for account activation or reset.
Improved
Made UI improvements for all objects with screening data attached.
Enhanced the ability of Subscribers to edit their personal number lists.
Added the Allow Service Provider Override option to more settings and made overall improvements to the settings screen.
Numbers and screening rules are no longer stored in a PCS database. Now, they are retrieved from the Screening Engine database.
Changed cache invalidation so that an application no longer needs to be restarted to apply changes made to settings.
Fixed
There was unnecessary duplication of data.
The failure rules of the Screening Engine would ignore the configuration for failure cases in the Whitelist and Blacklist screening rules.