subscription number management with aliases
In a previous thread I posted a question regarding managing MSISDN/Call number management in BRM 7.4. Most answers indicate that this should be managed with service login and aliases. However, there is a use case scenario that troubles me.
Assume that a customer has three Call numbers. This can be translated to one login and two aliases. Should the customer decide to stop using the two Call numbers, then only one primary login will remain to the service. So as to provision this, I use opcode PCM_OP_CUST_UPDATE_SERVICES.
If this happens on June 3 rd 12:00, then all CDRs with timestamp prior to this date should be rated normally by Batch Pipeline and all CDRs with timestamp after this date should be discarded. However, Batch Pipeline discards all CDRs immediately after the provisioning action occurs, with message <CUSTOMER_LOGIN_NOT_VALID_FOR_TIME>, even if the CDR has start timestamp prior to June 3