Jump to: navigation, search

Billing Data Server Release Notes

Billing Data Server is part of 9.x starting in
Release Date Release Type Restrictions AIX Linux Solaris Windows
03/31/20 Update X

Helpful Links

Releases Info

Product Documentation

Genesys Products

What's New

This release contains the following new features and enhancements:

  • Enhanced agent location tracking — BDS now leverages functionality introduced in Genesys Info Mart release to more accurately associate agent seat counts with regions. BDS now compares values that correspond to an agent session in the Genesys Info Mart AGENT_LOCATION table with values in the dc_aliases lists of locations defined in the BDS configuration. If any of the values match, the agent session is attributed to the region to which the location belongs. If this method is not successful, BDS assigns a location based on the switch names and default locations, as it did in earlier releases. For more information, see the Billing Data Server Deployment Guide. (CBILL-3075)
  • Control Utility enhancements — The BDS Control utility (Brsctl.py) now supports deletion of metrics defined in the BDS configuration. For more information, see Billing Data Server User's Guide. (CBILL-3286)
  • Enhanced error checking — In scenarios where BDS detects that a Data Center (DC) alias encountered in a dataset is not present in any of dc_aliases lists of locations defined in the BDS configuration, BDS now stops processing the current metric and logs an error. (GCXI-3458)
  • Miscellaneous enhancements — The BDS container now runs Python 3.6. Previous releases ran Python 2.7. (CBILL-3249)

Resolved Issues

This release contains the following resolved issues:

When counting peak values, BDS now includes only results that occurred on the target date. Previously, when sessions began on one day and ended on another, peaks were sometimes associated with the wrong day. (CBILL-3312)

BDS now derives country information from a new mandatory parameter, country, which is defined for each location present in the BDS configuration. The parameter accepts country code values in the ISO 3166-1 alpha-2 format. Previously, BDS derived a country value from a subset of hard-coded values, which did not permit new countries to be added to the configuration, and produced a runtime error similar to the following:

 2019-12-17 18:40:16,221 ERROR    139948824983296 | brs.transform.gvp.process_gvp - <date=2019-12-14;tenant_id=1;tenant=Environment> GVP transform exception
 Traceback (most recent call last):
   File "/vagrant/brs/transform/gvp.py", line 73, in process_gvp
   File "/vagrant/brs/logging_facilities.py", line 238, in wrapper
     res = func(*args, **kwargs)
   File "/vagrant/brs/transform/gvp.py", line 961, in transform_gvp
     event_list, total_calls, total_duration = self.get_csv_call_events_for_day()
   File "/vagrant/brs/transform/gvp.py", line 664, in get_csv_call_events_for_day
     csv_file_paths, ivr_profiles, stats)
   File "/vagrant/brs/transform/gvp.py", line 616, in process_cdrs_for_tenant
     event_list_all.extend(self._get_event_list(cdr_data, test_sessions, stats))
   File "/vagrant/brs/transform/gvp.py", line 507, in _get_event_list
     valid_dn, remote_dn = self.e123_format(call['remote_party'], self.region)
   File "/vagrant/brs/transform/transform_utils.py", line 424, in e123_format
     dn_info = phonenumbers.parse(dialed_number, PHONE_REGION_MAP[region])


Upgrade Notes

No special procedure is required to upgrade to release

This page was last edited on March 31, 2020, at 22:06.
Comments or questions about this documentation? Contact us for support!