Diversion Header Not Conserved When SRP Is Involved In Call (Doc ID 2856760.1)

Last updated on MARCH 18, 2022

Applies to:

Symptoms

On Oracle Communications Network Charging and Control (NCC), 4.4.1 version, Session IF,

ACTUAL BEHAVIOR
--------------------------

When an Specialized Resource Function (SRP) is involved in a call, it is observed that the Diversion header information is not being conserved, when the last INVITE is sent by the Service Logic Controller (SLC) for the final answer point/destination.

In this specific scenario, the first INVITE is send from the Softswitch Platform to the SLC, which has the "Diversion header" information. The next INVITE is the call to the SRP and this INVITE to the SRP still contains the "Diversion header". But the the final INVITE sent after completing the SRP interaction is missing the "Diversion header" information. Below is a sample snoop trace of the final INVITE, where the Diversion Header information is missing.

Sample Trace:

The Diversion header information is not being conserved in calls and this is causing problems with downstream billing systems/Billing operational issues.

EXPECTED BEHAVIOR
-----------------------
The Session Control Agent (SCA) Function should conserve the Diversion header for the final INVITE.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. On NCC 4.4.1 SLC, initiate an SRP interaction call by sending an INVITE message to the SCA with Diversion header information.
2. Pass this INVITE to the SRP
3. After the SRP interaction is completed, forward the INVITE to a final answer Point.
4. Check whether this final INVITE message is having the "Diversion Header" information.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.