No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


CCF can not generate long duration call CDR every six hours as expected due to too many ACR sent by ATS

Publication Date:  2012-08-06 Views:  119 Downloads:  0
Issue Description
ATS version is V100R003C01SPC100. CCF version is V300R002C68SPC200.
Set “BC required CDRs merge timer  =  21600” via the command “ADD PROCESSOR”on CCF MML client, and CCF would generate one CDR every 6 hours (21600s) for the long duration call. Unexpectedly, CCF generated one CDR every five hours during the testing.

Alarm Information
Handling Process
Run “LST RFPARAM” on ATS MML client, we can see that the parameter "ITRMTM=180" by default.
Run “MOD RFPARAM: ITRMTM=300” to modify it to 300s. After that, ATS will send ACR to CCF every 300s(5 mins). So CCF will receive 72 ACR from ATS normally in six hours, not up to 100 ACR. In this case, CCF will generate CDR every 6 hours for the long duration call as customer expected.
Root Cause
There are two following cases where CCF would generate long duration call CDR.

1. ACR number is up to 100. This number is hardcoded and can not be modified. That means CCF will generate one CDR for the long duration call when it receives 100 ACR from ATS.
2.The timer fires. The timer value is set by the parameter "BC required CDRs merge timer"  in the command of ADD PROCESSOR, and it is 21600s (6 hours).

During the testing, CCF generates CDR every 5 hours for long duration call, so we can know that it receives 100 ACR from ATS in 5 hours. But it is required that CCF generates CDR every 6 hours from customer. In order for CCF not receive 100 ACR, we need to set the longer period that ATS sends ACR to CCF.