The SIP Third Party Charging feature creates the SCUR charging instance, maps initial SIP INVITE message to a session counter address, and makes the credit reservation.

The SIP INVITE message used is the message created by the SIP Third Party HTTP Trigger Feature from the incoming HTTP request.

Since the SIP Third Party Charging feature only creates the charging instance and makes credit reservation, the rest of the charging process must be handled by the B2BUA SCUR Features.

Details

Feature name

SipThirdPartyCharging

Applicable contexts

SIP service

SAS Support

No

Prerequisite features

SIP Third Party HTTP Trigger Feature

Related features

B2BUA SCUR Features

Typical feature execution points

SipThirdPartyAccess_SubscriberCheck

Feature responses

Response Reason

featureHasFinished

feature has finished

Session State inputs and outputs

Outputs

Name Type Format Description

B2BUAChargingCounterAddress

com.opencloud.sentinel.charging.sessioncounters.SessionCounterAddress

Session counter address

Session counter address mapped from the initial INVITE message

Mappers

This feature uses a mapper to convert the SIP request to a SessionCounterAddress. The default implementation is SipRequestToSessionCounterAddress:

// a mapper that takes a {{SipRequest}} and generates a {{SessionCounterAddress}}.
final Mapper<SentinelSipSessionState> mapper = getMapperLibrary().findMapper(
        getSessionState().getSentinelSelectionKey(),
        SipRequest.class,
        SessionCounterAddress.class,
        mappingPoint);

Configuration

The feature is not configurable.

Previous page Next page
Sentinel Express Version 2.9.0