| Attributes |
integerKeyString
key
mandatory
noNotification
restricted |
-
vtasSubsData
-
This attribute defines the primary key of VtasSubsData and this section describes the VtasSubsData attributes.
|
OperState |
-
vtasSubsDataCacheContactData
=
ENABLED
-
This attribute defines whether to enable or disable caching contact data for device handling in MTAS. If enabled, the contact data will be fetched from extended 3rd-party REGISTER request. If no cached data is available for a given subscriber at an initial INVITE, the contact data will be downloaded from S-CSCF with one-time subscription to the "reg"event. This CM attribute should specifically be enabled in SCC AS deployments (mtasSccAdministrativeState=1) and for MMTel AS using Flexible Communication Distribution to Primary User's devices (vtasFcdDistributeToPrimaryUserDevices=1). In order for caching contact data to work properly, Initial Filtering Criteria (iFC) for S-CSCF must be configured to send 3rd-party REGISTER request to MTAS extended with a MIME body containing the original REGISTER request and the 200 OK response as "message/sip"parts. If iFC are not configured for extended 3rd-party registration but this setting is enabled, MTAS will behave differently depending on deployment configuration. SCC AS (standalone or collocated with MMTel AS) will reject the third-party REGISTER with a SIP 400 Bad Request response with the Warning header set to 399: "MIME body message/sip content not sufficient". MMTel AS standalone will try to fetch the Contact Data from S-CSCF using one time subscription for "reg" event. SUBSCRIBE will be sent on receipt of each 3rd-party REGISTER. In order to avoid these superfluous messages in MMTel AS deployments where caching contact data is not needed, this setting must be disabled manually.
Dependencies: This setting should specifically be enabled in SCC AS deployments (mtasSccAdministrativeState=1) and for MMTel AS using FCD to Primary User's devices (vtasFcdDistributeToPrimaryUserDevices=1). In order for caching contact data to work properly, Initial Filtering Criteria (iFC) for S-CSCF must be configured to send 3rd-party REGISTER request to MTAS extended with a MIME body containing the original REGISTER request and the 200 OK response as "message/sip" parts. vtasSubsDataCacheContactData can not be Disabled if vtasSubsDataCachePani is Enabled.
Takes effect: New session
|
MtasSubsDataCachePaniDT |
-
vtasSubsDataCachePani
=
CACHEPANI_DISABLED
-
This attribute defines whether to enable or disable caching PANI header in MTAS. If set to "0" then function is disabled. If set to "1" then PANI header is cached from SIP messages during call-setup, at registration, at re-registration and when access change is reported during active session. If set to "2" then the PANI header is cached from SIP messages at registration, at re-registration and when access change is reported during active session.
Dependencies: It must not be possible to enable vtasSubsDataCachePani when vtasSubsDataCacheContactData is disabled. vtasSubsDataCacheContactData can not be Disabled if vtasSubsDataCachePani is Enabled, vtasSubsDataCachePani should be Disabled first.
Takes effect: New session
|
MtasTimerMin00001to032000DT |
-
vtasSubsDataDefaultRegTimer
=
21600
-
This attribute defines what is used for registration
timer when no third party registration was received before session initiation. The value
is larger than or equal to the typical registration lifetime in the S-CSCF to allow
receiving a reregistration before the expiry of the timer.
Dependencies: The value of this timer must be greater than or equal to vtasCcbsT3ServiceDurationTimer.
Takes effect: New session
|
MtasTimerMin00000to001000DT |
-
vtasSubsDataDeregTimer
=
360
-
This attribute defines the duration of the deregistration timer. This timer
defines how long subscriber data remains in the cache following termination of the last session for
an unregistered subscriber. It is started when the last call for the unregistered subscriber is
completed. It is stopped when a new session is initiated for the subscriber.
Takes effect: Session tear down
|
VtasDropBackDT |
-
vtasSubsDataDropBack
=
USE_OTP_VALUES
-
This attribute defines whether this virtual operator wishes to use the values in VtasSubsData or the values in MtasSubsData.
Takes effect: New registration
|
MtasSubsDataMobileClassificationDT[0..10] nonUnique |
-
vtasSubsDataMobileClassification
-
This attribute defines the basis for device classification as "mobile" at the registration and the "reg" event notification. It is a list of strings where each string represents one Contact header parameter (feature tag) and its value identifying a mobile device. A feature tag name and value match is case insensitive. A feature tag name and value match is not exact, i.e. when a given substring is found in a respective feature tag value then the match is successful. A feature tag value is optional. A feature tag without value denotes just presence of a given feature tag. The keyword "false" set as a feature tag value denotes absence of a given feature tag. The list is evaluated top down. Evaluation is abandoned on the first match. A device will be classified as "mobile" if at least one feature tag condition is fulfilled. Otherwise it will be classified as "fixed". If this setting contains at least one entry, the classification will be done based on feature tags only, without taking P-Access-Network-Info header into account. Otherwise, i.e. if this setting is empty (default value), a device will be classified as "mobile" based on the P-Access-Network-Info header indicating GERAN, UTRAN or E-UTRAN access, and if P-Access-Network-Info header is absent - based on presence of +g.3gpp.ics="server" or +g.3gpp.accesstype="cellular" feature tag. If none of the above conditions is fulfilled, a device will be classified as "fixed" by default. Note: mtasSubsDataCacheContactData must be enabled for this setting to take effect. Examples: +sip.instance="urn:gsma:imei", +g.gsma.rcs.ipcall=false.
Dependencies: Individual entries must be different from each other and cannot be mutually exclusive. mtasSubsDataCacheContactData must be enabled for this setting to take effect.
Specification: Each item in the list is a string of at minimum 1 and maximum 255 characters, in the following format: <parameter>[=<value>]
Takes effect: New session
|
MtasSubsDataPINFormatDT |
-
vtasSubsDataPINFormat
=
PLAINTEXT
-
This attribute defines whether the MTAS stores the new PIN code value in MD5 hashed format or in plain text,
when a user requests modification of the PIN using an SSC command.
The format is based on the mtasSubsDataPINFormat configuration parameter.
If the value of the parameter is 0, the storing format is to be plain text.
If the value of the parameter is 1, the storing format is to be MD5 hashed.
This is independent of the current storing format
Takes effect: New session
|