Build - the name of the maintenance release build the change was introduced in.

Service - the name of the service/services which is/are affected.

Method - the name of the method/methods which is/are affected.

Message - the message that explains what was changed.

Schema changed - shows whether it is required to rebuild WSDL/XSD-generated stubs for .net, Java and other static typing languages.

TT - a link to a ticket related to the change.


BuildServiceMethodMessageSchema changedBackward compatibleTTResolution for system update
MR78-0Customer

*

Field 'i_moh' from 'CustomerInfo' structure was marked as deprecatedNoNoYT:BA-21947

Overview: 
In the scope of improving the UI performance, the 'i_moh' value is going to be removed from the "CustomerInfo" structure. Starting from MR78-0 it is marked as deprecated in the API guide, and starting from MR81-0, the 'i_moh' value is removed. There are alternative API methods that are used for retrieving these data: 'get_callqueue_moh_file', 'get_moh_list_info'.

Symptoms/Impact:
No impact.

Actions: 
If there is a task to get the 'i_moh' value for a particular customer, it is recommended to use 'get_moh_list_info' instead.

MR78-0Customerget_customer_xdrsAdd flag to check the total amount of handled data before processing XDRsYesYesYT:BA-21442
MR78-0Accountget_xdr_listAdd flag to check the total amount of handled data before processing XDRsYesYesYT:BA-21442
MR78-0DIDget_customer_numbersAdd 'get_total' flag to return the total amount of records. Default value is set to 1YesYesYT:BA-19383
MR78-0CallControloriginate_callDeprecate method originate_call (use originate_advanced_call instead). To enable method use option [API]AllowObsoleteMethods=YNoYesYT:BA-22444
MR78-0Rate*Added 'inter_intra_state_enabled' filedt into RateInfo structureYesYesYT:BA-22265
MR78-0Accountget_account_list

Added 'expand_alias' flag to enable for aliases returning data from the corresponding master accounts

YesYesYT:BA-22454
MR78-0DIDget_number_infoAdded 'vendor_name' to the method's responseNoYesYT:BA-21929
MR78-0DIDget_owner_batch_listList of allowed values for 'order_by' was extended with 'total_dids_free' and 'total_dids_used'YesYesYT:BA-19640
MR78-0Customerget_batch_list

GetCustomerBatchList structure was extended with the 'limit', 'offset', 'get_total' and 'check_usage' fields. Default value for 'check_usage' is 1 for backward compatibility

Added 'total' field to the GetCustomerBatchListResponse structure (present if the 'get_total' was passed in request)

YesYesYT:BA-22139
MR78-0DIDget_number_listEstimatedDIDNumberPricingParameterInfo structure was extended with the 'name' field - the name of the customer/reseller for whom the price is estimatedYesYesYT:BA-21273
MR78-0Account

get_account_info

get_account_list

The methods will return the 'i_vd_plan' inherited from the sponsorNoYesYT:BA-22074
MR78-0Accountget_account_listThe 'GetAccountListRequest' structure was extended with the 'email' and 'subscriber_email' fields YesYesYT:BA-21266
MR78-0Account

get_account_info

get_account_list

For beneficiary accounts, the response will contain  the 'master_i_billing_model' field - the billing model of the sponsorYesYesYT:BA-22211
MR78-0CallControl

ring_call

progress_call

Added two method into the Call Control Service reflecting the latest changes in the PortaSIP Call Control JSON API
YesYesYT:BA-22494
MR78-0Customerget_customer_infoAdded "rt_server_url" field to the "rt_auth_info" section in case of specifying "get_rt_auth_info" flagYesYesYT:BA-19883
MR78-1DiscountPlanadd_topup_optionMade 'topup_amount' field to be mandatory in the mentioned method requestYesNoYT:BA-20201

Overview

The topup_amount parameter is mandatory for the add_topup_option method. More details about the parameter in the PortaBilling XML / JSON API Reference Guide at https://www.portaone.com/docs/pb/mr78/PortaBilling_API_MR78.html#VDTopupOptionInfo

Symptoms/Impact:

The add_topup_option method does not perform a top up in a service wallet. The API reply contains "Client.DiscountPlan.mandatory_field_missed.topup_option_info.topup_amount" error.

Actions

Make sure that the topup_amount parameter is sent in the add_topup_option API call.

MR78-1TraceSessionget_log_infoFields 'start_time', 'end_time' were added to 'SessionLogMetaInfo' structureYesYesYT:BA-12456
MR78-1Genericget_extended_data_listThe method is enabled to use by the users for whom personal info is maskedNoYesYT:BA-22462
MR78-1TaxationPluginget_tax_transaction_code_list

The 'check_usage' parameter was added to check whether the tax transaction codes are in use.

YesYesYT:BA-22693
MR78-1Customerget_rt_requestor_listAdded Customer.get_rt_requestor_list API method that allows to obtain a list of RT requestorsYesYesYT:BA-22722
MR78-1Rateget_rate_listThe 'combined_status' parameter was added to enable combined status check based on 'discontinued', 'forbidden' and 'hidden' fieldsYesYesYT:BA-20436
MR78-1Rate

add_rate,

add_rate_group,

batch_add_rate,

update_rate,

update_rate_group

NULL values are set to the rate parameters op_route_category, op_preference, op_huntstop when they are not given for the add methods. Update methods will not change the previously set data values

YesNoYT:BA-22519

Overview: 

Starting From MR75-3, the op_route_category, op_preference, op_huntstop rate parameters don't inherit the values from the route_category, preference, huntstop parameters and are set to NULL in case they are not sent using the add or update rate methods.
Please see more details about the methods in the PortaBilling XML / JSON API Reference Guide at MR75
https://www.portaone.com/docs/pb/mr75/PortaBilling_API_MR75.html#serviceRate

Symptoms/Impact:

NULL values are set for the op_route_category, op_preference, op_huntstop rate parameters if they are not stated via the add methods.
Update methods don't change the previously set data values if they are not provided.

Actions:

Make sure that the op_route_category, op_preference, op_huntstop rate parameters are sent in the add_rate, add_rate_group, batch_add_rate methods in case they need to be different from NULL.

Make sure that the op_route_category, op_preference, op_huntstop rate parameters are sent in the update_rate, update_rate_group methods in case they they need to be changed.

MR78-1Customerget_rt_tickets_listAdded "priority" attribute to the method response. Implemented optional filtering by the following fields: "id", "created", "last_updated", "status", "subject", "priority"YesYesYT:BA-22721
MR78-1Productupdate_groupWhen the 'depailed_response' flag is set, the included products will be returned in the responseNoYesYT:BA-19879
MR78-1Vendorget_vendor_listWhen the 'limit' isn't passed in the request, all the vendors will be returnedNoYesYT:BA-22830
NR78-1Service

add_service

get_service_info

get_service_list

The 'invoice_group' property has been added to the ServiceInfo structureYesYesYT:BA-22914
MR78-1Account

get_account_info

get_account_list

get_service_features

get_service_features_metainfo

The methods which return service features now  correctly inherit the value of the features from the sponsor's addon configurationNoYesYT:BA-22222
MR78-1TraceSessionget_log_infoExtend meta_info with cli, cld, source_ip and user_name for BE logs from ESYesYesYT:BA-21483
MR78-1Customerget_customer_xdrsAdded show_hidden parameter to include hidden XDRs in the result (works for the Admin realm only, default value is 1)YesYesYT:BA-23474
MR78-1DIDget_number_listA new i_ivr_an parameter was added to the response protocol to show that the IVR access number is assigned to the DIDYesYesYT:BA-23080
MR78-1CommissionPlan

add_commission_plan

update_commission_plan

The maximum value of the fields:

CPPeriodInfo.commission 

CommissionPlanInfo.default_commission

CPSubscriptionInfo.one_time_commission

has been increased to the maximum value allowed to store in the database

YesYesYT:BA-23632



  • No labels