These features are neither MMTel specific nor SCC specific.
Feature | What it does |
---|---|
uses information from the incoming INVITE request to determine whether Ro Online charging should be applied to the session, |
|
uses the Leg Manager to get the names of the original SIP legs established during call set up, and saves the values |
|
uses information from an incoming |
|
reads Third Party Registration information stored in the HSS as Transparent Data, and writes it into session state. |
|
reads Third Party Registration information stored in the Cassandra Database, and writes it into session state. |
|
reads Third Party Registration information stored in the Cassandra Database, and writes it into session state. |
|
is responsible for reading data from the HSS and writing it into Sentinel session state fields. |
|
is responsible for reading data from the HSS and writing it into Sentinel session state variables fields. |
|
is responsible for reading subscriber data from the HLR and writing it into Sentinel session state variable fields. |
|
is responsible for building a Call Detail Record that reflects the actions taken whilst processing a session. |
|
is a system feature which prevents SDP-change initiated CDRs from being written by the |
|
is a system feature that is responsible for writing interim Call Detail Records and/or Diameter Accounting Requests (ACRs) throughout the session. |
|
sets values for the Feature-Caps header on outgoing messages based on data from the session’s FeatureCapsManager |
|
schedules configurable announcements to the subscriber based on indicators in OCS answers |
|
updates session state when a session’s held status changes |
|
This feature gathers the information required to allow the session tracking system to be used for access transfer procedures. |