When configuring extension points under Initial Blueprint for Policy Reporting:
Based on the
extension point used for configuration, the results may differ.
For example, in
cases of session termination, the conditions depending on the presence of a
session are not satisfied.
If
A Diameter
Gx TGPP Session exists is configured in the
Conditions pane under
Send
outbound messages, it captures CDRs for all messages including
CCR-T message.
But if
A Diameter Gx TGPP Session exists is configured for
Post
outbound message policies, it can capture blank CDRs for CCR-T
message. This is due to the session being deleted once the CCR-T message is
sent.
As mentioned
above, since post outbound message policy is executed after the outbound
message is sent across by the CPS, the condition
A Diameter
Gx TGPP Session exists does not hold true for CCR-T message,
resulting in blank CDRs being captured.
To define a policy in the Policy Builder, add the required fields in the Policy CDR using the data fields available in the
Policy Reporting field category.
Note
|
The CDR in the reporting database should be load balanced across the session managers. If high CDR (approx. 8k) is reported
on primary reporting replica-set member, there is a chance of getting an issue "Secondary replica lagging behind the Primary replica" which leads to the diagnostics output in the hang state. So, the load balancing has to be done as a policy change and can
be configured based on the customer environment. For more information, contact your Cisco Account representative.
|