Applications running on network elements that terminate SIP traffic,
such as those that answer incoming phone calls, can collect and add to the
information present in the P-Charging-Vector headers.
Before you begin
Your application should accept and use the correct Inter Operator
Identifier (IOI), as a configuration parameter.
About this task
SIP border and privacy proxy elements can create call accounting
records using the P-Charging-Vector information provided by the originating
and terminating elements. The headers typically include the following data:
- The name of the host that created the header
- The IMS Charging Identifier (ICID)
- The originating network IOI
- A terminating network IOI
Note: The charge header support vector is a utility class for handling
the SIP messaging for charging interactions.
The following steps
describe the process by which your application can handle P-Charging-Vector
headers in inbound SIP requests and responses:
- The application receives an initial incoming SipServletRequest.
- The application invokes thePChargingVector.piggybackOnto(...) method
using the incoming SipServletRequest.
Note: You must provide an
IOI to the method. This IOI will be used as the terminating IOI
- The application generates a SipServletResponse to
the SipServletRequest.
- The application invokes the PChargingVector.piggybackOnto(...) method
on the newly generated SipServletResponse.
- The application sends the SipServletResponse.
- The application invokes the PChargingVector.piggybackOnto(...) on
all further SipServletRequests, or SipServletResponses received or generated
by the application.
Note: The application must use the Java thread
synchronization mechanisms to ensure that the PChargingVector.piggybackOnto(...) is
not invoked on two different messages in the same SIP dialog at the same time.
Locking on the SipServletMessages SipSession prior
to calling PChargingVector.piggybackOnto(...), is sufficient.