SIP INVITE session plans
Some session plans can be executed on an INVITE.
|
Details on how they are selected can be found in the documentation for the DetermineVoltePlanId feature. |
The session plans are:
Plan ID |
Executed by |
mmtel-orig |
MMTel AS serving the originating user |
mmtel-term |
MMTel AS serving the terminating user |
mmtel-conf |
MMTel AS providing conferencing (MMTelCONF) functionality |
scc-orig |
SCC AS serving the originating user |
scc-term |
SCC AS serving the terminating user |
scc-term-anchor |
SCC AS serving the terminating user but only executing access transfer functions |
scc-term-tads |
SCC AS serving the terminating user but only executing T-ADS functions |
scc-access-transfer |
SCC AS on receiving an access transfer request |
scc-reorigination |
SCC AS on receiving a reorigination request |
SIP REGISTER session plans
The Registrar uses the session type and plan ID portion of the selection key in order to simplify the feature execution scripts that run for different types of third-party registration.
The main two features that do this are:
-
VolteDetermineRegistrationSessionType — sets the session type to one of
eSRVCCRegistrationorRegular3rdPartyRegistration -
DetermineRegistrationActionType — sets the plan ID to one of
register,re-register, orde-register.
| Session type | Plan ID | Executed by |
|---|---|---|
Regular3rdPartyRegistration |
register |
MMTel AS with third-party registrar |
Regular3rdPartyRegistration |
re-register |
MMTel AS with third-party registrar |
Regular3rdPartyRegistration |
de-register |
MMTel AS with third-party registrar |
eSRVCCRegistration |
register |
SCC AS with third-party registrar |
eSRVCCRegistration |
re-register |
SCC AS with third-party registrar |
eSRVCCRegistration |
de-register |
SCC AS with third-party registrar |
Registration session plans for register and re-register distinguish the features that they execute.
The register session plans are intended to execution upon Initial Registration into the IMS, whereas re-register corresponds to registration refreshes.
Examples of features that should run on Initial Registration but not registration refresh are FetchCMSISDN, or ESRVCCRegistration
IN session plan
Sentinel VoLTE uses minimal feature execution scripts for IN call processing — they exist purely for the purpose of IMS service centralization. This will result in the call being connected to an IP Multimedia Routing Number (IMRN) and the TCAP dialog being closed; no online charging request will be made as part of InitialDP processing.
These feature execution scripts run in the SS7 sessions initiated via the CAMEL IDP session plan. For more information refer to Service Centralisation Features.
Viewing session plans
The list of execution points and their associated feature scripts can be viewed through REM by selecting the Management→Profiles menu, then selecting the ${PLATFORM_OPERATOR_NAME}_FeatureExecutionScriptTable table.
Here the variable ${PLATFORM_OPERATOR_NAME} is replaced by the Platform Operator Name chosen at installation time. So if the Platform Operator Name was set to "Rocket" the table name would be "Rocket_FeatureExecutionScriptTable".
To view the same information from the rhino console, view the list of execution scripts by running listprofiles ${PLATFORM_OPERATOR_NAME}_FeatureExecutionScriptTable.
To view an individual script use listprofileattributes ${PLATFORM_OPERATOR_NAME}_FeatureExecutionScriptTable ${SCRIPT_NAME}.
To view the Feature Execution Script name that is invoked for a particular Plan ID’s execution point, use listprofileattributes ${PLATFORM_OPERATOR_NAME}_FeatureExecutionPointTable ${EXECUTION_POINT}.
For more information related to Feature Execution Points, Feature Execution Scripts and Plan IDs refer to Session Plans
