WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Originating (initiating) the SIP request

Applications running on network elements that originate SIP traffic, such as creating new and outbound phone calls, can add P-Charging-Vector headers to their outbound SIP requests and responses.

Before you begin
Your application should accept and use the correct IOI (Inter Operator Identifier) as a configuration parameter.
About this task
The following steps describe the process by which an application adds P-Charging-Vector headers to outbound SIP requests and responses:
  1. The application receives the initial incoming SipServletRequest.
  2. The application invokes the PChargingVector.piggybackOnto(...) method, using the incoming SipServletRequest.
    Note: You must supply an Inter Operator Identifier (IOI) to the method. The IOI will be used as the terminating IOI.
  3. The application generates a SipServletResponse to the SipServletRequest.
  4. The application invokes the PChargingVector.piggybackOnto(...) method, on the newly generated SipServletResponse.
  5. The application sends the SipServletResponse.
  6. 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™ standard locking 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.



Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.