This feature is used to populate the session state TADSCircuitRoutes with the primary and companion device CS routes.

Feature Cheat Sheet

B2BUA Instance SAS Support Originating / Terminating Point(s) in Session Plan Network Operator Data Subscriber Data Stateful or Stateless POJO Feature or SBB Feature Other notes

SCC

Yes

Terminating

SipAccess_SubscriberCheck SipAccess_PartyResponse

Yes

No

Stateless

POJO

Prerequisite Features

Session Input Variables

Session state variable name Type Comments
RoutingMode

TADSRoutingMode (Enum)

Determines whether CS and/or PS routing is enabled and the preferred attempt order.

CircuitRoutesAlreadyDetermined

boolean

Set to true when circuit routes have already been set.

HasCompanionDeviceCSRNs

boolean

Set to true when companion CSRNs have been identified by the FetchCMSISDN/FetchMRSN features.

CompanionDeviceCSRNs

Queue<String>

Contains companion device CSRNs.

HasCSRN

boolean

Set to true when a primary CSRN has been identified by the FetchCMSISDN/FetchMRSN features.

CSRN

String

Contains the primary device CSRN.

TADSEndSessionWhenNoValidRouteFound

boolean

Set to true by SCCTADSDataLookup feature if configuration EndSessionWhenNoValidRouteFound is true and no PacketRoutes are found.

Session Output Variables

Session state variable name Type Comments
CircuitRoutesAlreadyDetermined

boolean

Set to true when circuit routes have already been set.

TADSCurrentLegRoute

String

Contains a CSRN or URI that is used by SCCTADSRouting and SCCTADSParallelRouting features to setup a new CS/PS leg.

TADSCircuitRoutes

Queue<String>

Contains valid primary and companion CS routes (CSRNs).

Statistics

Statistics are tracked by the sentinel.volte SBB and can be found under the following parameter set in REM:
SLEE-Usage → sentinel.volte service → sentinel.volte SBB → feature → SCCTADSDetermineCircuitRoutes
or with rhino-stats:
"SLEE-Usage.Services.ServiceID[name=sentinel.volte,vendor=OpenCloud,version=4.1].SbbID[name=sentinel.volte,vendor=OpenCloud,version=4.1].feature.SCCTADSDetermineCircuitRoutes"

Name Type Description
Started

Counter

Incremented when the feature is triggered.

FailedToStart

Counter

Incremented when the feature fails to start.

FailedDuringExecution

Counter

Incremented when the feature fails while executing.

IssuedWarning

Counter

Incremented when the feature issues a warning.

TimedOut

Counter

Incremented when the feature times out during execution.

FoundValidCSRoute

Counter

Incremented when a route is added to the queue.

TriggeredEndSession

Counter

Incremented when the feature ends the session.

Behaviour

Determining CS Routes

The feature adds primary and companion CS routes (CSRNs) that are present in session state CSRN and CompanionDeviceCSRNs into the session state TADSCircuitRoutes. The session state TADSCircuitRoutes is then used by SCCTADSRouting and SCCTADSParallelRouting features to setup the appropriate CS legs.

Note The Circuit Switched Routing Number (CSRN) is made up of the CMSISDN, MSRN, or TLDN. The value is fetched by either FetchCMSISDN, FetchMSRN or CDMAFetchTLDN depending on configuration in VolteServiceConfigProfileTable and SCCTADSDataLookUpConfigProfileTable.
Previous page Next page
Sentinel VoLTE Version 4.1