Contents
1 Introduction
This Network Impact Report (NIR) describes how vMTAS 1.14.0, with new and enhanced features and corrections, affects vMTAS 1.11.0. The NIR also describes the impact on the overall network, including all affected products and functions.
This document covers the following new and enhanced features:
New Features
- VMware Instantiation and Termination Workflow
- Forking Interworking Function (F-IWF)
- vMTAS, Tool for Faster and Easier Handling of Subscriber and Software Trace
- Announcement according to Reason header
- Communication Event Logging
- vMTAS Workflow enhancement when used with Ericsson Orchestrator
Enhanced Features
- Support of External MRFC node failover in MMTel AS (drop 2)
- Identity Presentation Enhancement for Enterprise Customers
- Enhancement of Hotline Service
- VoLTE for Unified Communication Non-UC Routing Numbers
- Interaction between CAT and MobileCommunicationWaiting
- Support of IMRN in National Format for SDS
- Network-based Handling of Non-authorized International Calls
- vMTAS, Improved Serviceability Success Rate During In-service Scaling
- Adding Date to Call Return Announcement for Calls Older Than Two Days
- Communication-barring Enhancements
- Mid-call Renegotiation Request Retry
- Call Type Validation for the Destination Number Provisioned for Abbreviated Dialing
- Network Announcement Triggered by Specific SIP Header
- Support of Originating Identity Presentation Restriction Service for Priority Calls in MMTel AS
- Ro Announcement for errors without Announcement AVP
- Graceful locking from vMRF
- Increased number of Rating Centers in Number Analysis
- EM-driven instantiation
- EM-driven scaling
- Time-based auto-scale
- Improved Number Table Handling
- Realignment of TCO: Health check output
- Support for ANSI network (CAP)
- vMTAS improved resilience to network disturbances
For more information on the changed features, see Section 5 Impact on MTAS Features.
1.1 Terms of Phasing Out Features
The following terms are used when phasing out and removing features from the product:
Deprecated
A feature that is deprecated means that the feature is still there and usable, but is now substituted by another feature, and is subject to be made obsolete or be deleted after one year. During the time from deprecation to making a feature obsolete or deleted, all use of the deprecated feature needs to be migrated to the new feature.
Obsolete
Making a feature obsolete means, that the feature or parts of it might be still part of the product (for technical reasons) but are not supported anymore. Use of these features is not possible.
Deleted
Deletion means that the feature is deleted as such, it is not visible and there is no way to use it any more, from the current Release and onwards.
2 General Impact
This section describes the general impact owing to the introduction of vMTAS 1.14.0.
2.1 Backward Compatibility
vMTAS 1.14.0 is backward compatible and unless stated otherwise, legacy behavior is preserved.
2.1.1 Interoperable Network Elements
The interoperable Network Elements for vMTAS 1.14.0 are described in Table 1.
|
Network Element |
Earliest Supported Versions |
|---|---|
|
MRS |
14A |
|
14A | |
|
14A | |
|
OSS-RC |
O16A: Upgrade for OSS-RC is only needed when new parameters and counters are introduced in MTAS and are to be used. Up to O18B: The vMTAS 1.14 is backward compatible except synchronizing Number Normalization, Number Analysis and Carrier Select configuration. The same function level exists, but the method for synchronizing the configuration is changed. Respective Table EditAction and CommitAction commands need to be executed before and after the configuration change. |
|
7.0 CP2 | |
|
15B | |
|
vENM |
vMTAS Lifecycle Management requires 17.15(-3.6.8) version of VNF-LCM; therefore use the 18A release of ENM. Up to ENM 19.1: The vMTAS 1.14 is backward compatible except synchronizing Number Normalization, Number Analysis and Carrier Select configuration. The same function level exists, but the method for synchronizing the configuration is changed. Respective Table EditAction and CommitAction commands need to be executed before and after the configuration change. |
2.2 Capacity and Performance
2.2.1 Subscriber Capacity
The subscriber capacity is not affected by the introduction of vMTAS 1.14.0.
The number of half call establishments and releases per second determines the need of processing resources. Processing capacity is the limiting factor for the MMTel, SCC, Conf, NW, and SIP Trunking AS.
2.2.2 Network Performance and Traffic Capacity
Between vMTAS release 1.11.0 and 1.12.0, there is approximately a 1–7% capacity degradation.
Between release 1.12.0 and 1.13.0, the following degradations are applicable, according to our measurements:
|
AS |
HW Concept |
PLs |
vCPUs |
RefCap Delta |
|---|---|---|---|---|
|
GEP5 |
2 |
4 |
-25.0 | |
|
GEP5 |
2 |
8 |
-16.9 | |
|
GEP5 |
2 |
16 |
-10.7 | |
|
GEP5 |
10 |
16 |
-10.8 | |
|
GEP7 |
10 |
24 |
-5.8 | |
|
GEP7 |
22 |
24 |
-5.7 | |
|
GEP5 |
2 |
16 |
-13.4 | |
|
GEP7 |
10 |
24 |
-9.8 |
Between vMTAS release 1.13.0 and 1.14.0, there is approximately a 5–7% capacity improvement.
This leads to the overall capacity change between release 1.11.0 and 1.14.0 being the sum of the above changes.
2.2.3 License Handling
It is mandatory to use Network License Server (NeLS) product with vMTAS 1.14.0.
For more information, refer to MTAS Licenses.
3 Licenses
This section lists the new and changed license codes added in vMTAS 1.14.0. For a list of (v)MTAS licenses, refer to MTAS Licenses.
3.1 New Licenses
The new licenses are shown in Table 2.
|
Name |
Identity |
Version |
|---|---|---|
|
Forking Interworking Function |
vMtasForkingIwf |
CXC 401 2293 |
|
Multi-Persona |
vMtasMultiPersona |
CXC 401 2309 |
3.2 Changed Licenses
The changed licenses are shown in Table 3.
|
Name |
Description of Changes |
|---|---|
|
- |
- |
3.3 Deprecated Licenses
The deprecated licenses are shown in Table 4.
|
Name |
Description of Changes |
|---|---|
|
- |
- |
3.4 Deleted Licenses
The deleted licenses are shown in Table 5.
|
Name |
Description of Changes |
|---|---|
|
- |
- |
4 Interfaces
This section describes interface changes between the existing and new revisions of the product.
4.1 Inter-Node Interfaces
The changes to the inter-node interfaces are described in Table 6.
The description of impact is as follows:
- No Impact - New version can be installed without affecting other nodes.
- Minor Impact – There are changes, but with extra configuration the previous behavior can be kept.
- Major Impact – The change has made an interface backward incompatible.
- New Interface – The interface did not exist in the previous revision.
- Obsolete – The interface no longer exists.
|
Interface |
Protocol |
Impact |
Description of Changes |
|---|---|---|---|
|
No impact |
Retry of relayed mid-dialog renegotiation request on receiving 500 error response with retry-after header. This enhancement can be controlled with the mtasMmtMidCallRenegotiationRetryAfterSupport CM attribute. | ||
|
No Impact |
A new CM parameter mtasIdPresCnipAddIdParam is introduced. If this is set to TRUE, it enables MMTel AS to support adding the id parameter to the Event header after calling-name for SIP queries over the Calling Name Server (CNS) interface. | ||
|
No Impact |
The parsing of the Call-ID header has changed. Until this release MTAS produced a CA and dropped the call if the Call-ID in any SIP message contained certain string literals, for example, "M:". Now this behavior is corrected. See TR HW98411. | ||
|
ISC, Ma |
No Impact |
When a reliable provisional response is received after the final response, MTAS will send PRACK for it and handle the subsequent PRACK ACCEPT accordingly. See HW92831. | |
|
ISC, Ma |
Minor Impact |
Owing to TR HW72712, MTAS needs to support overlapping reliable provisional response transaction. MTAS now stops and saves new reliable provision responses before finishing the transaction of the previous reliable provisional response, then handles the saved message after previous transaction is finished. | |
|
Mr |
No Impact |
When MMTel AS identifies an External MRFC node as non-working because of no response to a request, then it is possible to avoid selecting this node for new requests during a configurable recovery period. | |
|
OAM MIP |
Major Impact |
New firewall rules have been introduced. Some of these rules are responsible to protect SCs against flood attack with limiting the maximum number of TCP sessions toward the OAM MIP. If this limit is exceeding from an IP then that IP will be banned. In normal usage this limit won’t be exceed but if a scripted machine to machine communication is in place then it is possible to activate this protection mechanism. In this case it is highly recommended to revise the communication and if it is possible reduce the number of used sessions. If this is not possible then the firewall rules need to be changed accordingly. For this, please refer to the MTAS Security Guide. See HW42027. | |
|
Major Impact |
When MTAS sends in-dialog SIP message to the node which is in the blacklist, then this message will not be sent out and additionally this specific session will be terminated by MTAS | ||
|
Minor Impact |
New CM parameters mtasUCRoutingSuppressServiceNumbers and vtasUCRoutingSuppressServiceNumbers. When above parameter is 1, UC Routing service will suppress routing the call towards UC system when Business UC user dials a non UC (service number like OSN/NSN/TollFree/ShortCode) number. | ||
|
CEL |
No Impact |
New “Communication Event Logging (CEL)” I/F is introduced where communication event is reported through PUBLISH message for a successful or unsuccessful call attempts. A PUBLISH Request is sent with “call-event-info” XML to event server whose address is configured in mtasCelEventServerName. | |
|
H248 |
No Impact |
MTAS supports new service change method: graceful reason: 908. After the arrival of the service change, new connections will not be allowed, but the established connections are not affected. New CM has been introduced to represent this state, called mtasMrfpNodeOperState. | |
|
Rf |
DIAMETER |
No impact |
New Supplementary-Service-Identity AVP value added – UNSUCCESSFUL_MP_CS_SELECTION. This AVP will be populated by Multi-Persona service in Originating Call with Multi-Persona on CS Access use case, when MPCN from incoming INVITE could not be recognized by the service, what leads to unsuccessful call setup. |
|
No impact |
The following new cases of SIP MESSAGE usage are added: MESSAGE received outside an existing dialog carrying application specific information on an established SIP Control Channel (e.g. MCMP) MESSAGE is sent as an acknowledgement of reception and processing of the request from the previous paragraph on an established SIP Control Channel (e.g. MCMP) MESSAGE is sent as a result of an application specific condition on an established SIP Control Channel (e.g. MCMP). MTAS is rejecting not expected MESSAGE events with 606 Not Acceptable and Warning string “Not Acceptable Here | ||
|
SIPCC |
New interface |
New control channel interface between MMTel AS and the VoLTE UE used for persona selection when being attached to CS. | |
|
Minor impact |
One-time SUBSCRIBE message includes P-Charging-Vector header if the REGISTER or the initial INVITE contains it. See HX29660. | ||
|
M3-IETF |
Minor impact |
Default retransmit behavior in M3-IETF is changed. Applications that use zero values (default values) of retransmit buffer and retransmit timer in M3-IETF configuration should be prepared to new M3-IETF behavior. The new behavior is that there will be no data retransmit between M3-IETF and SCTP layers in congestion situation. The reason is to prevent a retransmit loop of the same message causing high CPU load. To have a more stable retransmit handling the parameters should have other values than zero. | |
|
No impact |
When multiple AS roles are invoked that is controlled by IFC configuration: One ISC triggering can invoke the co-located roles in MTAS for SIP signaling on AS generic SIP port. The order of invoked AS roles is specified in the Route header “as=” parameter in the initial SIP request from S-CSCF to MTAS. The invoked AS name is added to P-Ericsson.Invocation-History header of related SIP requests and responses for trouble shooting. | ||
|
No impact |
Previously ITU standard and Global Title was hardcoded for the CAP interface. Now support for configuration of standard (ITU or ANSI) used on the CAP signaling network is added. Configuration can be done with the mtasCsiCapSccpStandard CM attribute. | ||
|
COM |
Major Impact |
The vMTAS 1.14 is backward compatible except synchronizing Number Normalization, Number Analysis and Carrier Select configuration. The same function level exists, but the method for synchronizing the configuration is changed. Respective Table EditAction and CommitAction commands need to be executed before and after the configuration change. |
4.2 Operation and Maintenance
This section describes changes to attributes, alarms, triggers, and performance measurement counters.
4.2.1 Provisioning
This section describes new, changed, deprecated, obsolete and deleted provisioning attributes.
4.2.1.1 New Provisioning Attributes
The new provisioning attributes are listed in Table 7.
|
Interface |
Protocol |
Description of Changes |
|---|---|---|
|
Operator will have the option to provision user with Whitelist Conditional Hotline New elements in <hotline-operator-configuration> are (example): <whitelist-condition>
<activated>true</mc:activated>
<hotline-number>tel:+1234500000</mc:hotline-number>
</whitelist-condition>
| ||
|
New service element "communication-event-logging" is added in MTAS for CAI3G information model |
4.2.1.2 Changed Provisioning Attributes
The changed provisioning attributes are listed in Table 8.
|
Interface |
Protocol |
Impact |
Description of Changes |
|---|---|---|---|
|
No Impact |
Application constraint check between element ad-hoc-temporary-presentation-not-restricted and restriction has been removed (HW96647). Originating Identity Restriction Failure: Element restriction cannot be present when value ad-hoc-temporary-presentation-not-restricted is set. |
4.2.1.3 Deprecated Provisioning Attributes
The deprecated provisioning attributes are listed in Table 9.
|
Interface |
Protocol |
Description of Changes |
|---|---|---|
|
- |
- |
- |
4.2.1.4 Obsolete Provisioning Attributes
The obsolete provisioning attributes are listed in Table 10.
|
Interface |
Protocol |
Description of Changes |
|---|---|---|
|
- |
- |
- |
4.2.1.5 Deleted Provisioning Attributes
The deleted provisioning attributes are listed in Table 11.
|
Interface |
Protocol |
Description of Changes |
|---|---|---|
|
- |
- |
- |
4.2.2 Configuration
This section describes new, changed, deprecated, obsolete, and deleted configuration attributes.
For more information on attributes and parameters, refer to vMTAS Master Parameter Value List.
4.2.2.1 New Configuration Attributes
The new configuration attributes are listed in Table 12.
|
Attribute Name |
Description |
|---|---|
|
CarSelCarrierTableSyncState |
Added and supported |
|
carSelDialedStringAnalysisTableSyncState |
Added and supported |
|
genericThresholdAlarmEnable |
Added and supported |
|
interval_timeout |
Added and supported |
|
mtasAbDialCallTypeValidation |
Now supported |
|
MtasCel |
Now supported |
|
mtasCelAdministrativeState |
Now supported |
|
mtasCelEventServerName |
Now supported |
|
mtasCelReportingFilterList |
Now supported |
|
mtasCelReportingHeaderFilter |
Now supported |
|
mtasChargingProfileEnhancedReportRoFailureOverRf |
Added, but not supported |
|
mtasChargingProfileReportAccessChange |
Added, but not supported |
|
mtasChargingProfileReportServedPersona |
Added, but not supported |
|
MtasChargingProfileRoReject |
Added, but not supported |
|
mtasChargingProfileRoReject |
Added, but not supported |
|
mtasChargingProfileRoRejectAnn |
Added and supported |
|
mtasChargingProfileRoRejectDefaultAnnRemoteUser |
Now supported |
|
mtasChargingProfileRoRejectDefaultAnnServedUser |
Now supported |
|
mtasChargingProfileRoRejectGa |
Added, but not supported |
|
MtasComCcmMccDestinationMapping |
Added and supported |
|
mtasComCcmMccDestinationMappingMappedValue |
Added and supported |
|
MtasComCcmMccMnc |
Added and supported |
|
mtasComCcmMccMncHome |
Added and supported |
|
mtasConfLastMovedParticipantRemovalEnabled |
Added and supported |
|
MtasCsiCap |
Added and supported |
|
mtasCsiCapCdEs |
Added and supported |
|
mtasCsiCapCdGti |
Added and supported |
|
mtasCsiCapCdNai |
Added and supported |
|
mtasCsiCapCdNp |
Added and supported |
|
mtasCsiCapCdTt |
Added and supported |
|
mtasCsiCapCgEs |
Added and supported |
|
mtasCsiCapCgGti |
Added and supported |
|
mtasCsiCapCgNai |
Added and supported |
|
mtasCsiCapCgNp |
Added and supported |
|
mtasCsiCapCgTt |
Added and supported |
|
mtasCsiCapSccpStandard |
Added and supported |
|
mtasCsiRelayScfAddress |
Added, but not supported |
|
mtasCsiRelayScfSubsystemNumber |
Added, but not supported |
|
mtasCwVersion |
Added, but not supported |
|
mtasDenVersion |
Added and supported |
|
MtasFoIw |
Added, but not supported |
|
mtasFoIwAdministrativeState |
Now supported |
|
mtasFoIwInvocationHeaderHandling |
Now supported |
|
mtasFoIwInvocationHeaderName |
Now supported |
|
mtasFoIwInvocationHeaderValue |
Now supported |
|
mtasFoIwMode |
Now supported |
|
mtasFunctionMmtAsName |
Added and supported |
|
mtasFunctionNwFoIwAsName |
Added and supported |
|
mtasFunctionNwPrIwAsName |
Added and supported |
|
mtasFunctionScalingTerminateWaitTime |
Added and supported |
|
mtasFunctionSccAsName |
Added and supported |
|
mtasGaAnnSessionProgressReason |
Added and supported |
|
mtasIdPresCnipAddIdParam |
Now supported |
|
mtasIdPresOipDisplayNameFiltering |
Added, but not supported |
|
mtasMmtDomesticRoaming |
Added, but not supported |
|
mtasMmtMidCallRenegotiationRetryAfterSupport |
Added and supported |
|
mtasMmtNpliOriginatingCSLocationInformation |
Added and supported |
|
mtasMmtSipccIdentification |
Now supported |
|
mtasMmtVersion |
Added, but not supported |
|
mtasMrfpNodeOperState |
Now supported |
|
mtasMultiPersonaAdministrativeState |
Now supported |
|
mtasMultiPersonaCapableFeatureTag |
Added, but not supported |
|
mtasMultiPersonaEnhancement |
Now supported |
|
mtasMultiPersonaInviteDelay |
Now supported |
|
mtasMultiPersonaMpcnMaxLifetime |
Added and supported |
|
MtasMultiPersonaMpcnRange |
Added and supported |
|
mtasMultiPersonaMpcnRangeFirst |
Added and supported |
|
mtasMultiPersonaMpcnRangeLast |
Added and supported |
|
mtasMultiPersonaOrigPolicyRejectionAnnName |
Added, but not supported |
|
MtasNaAnnCauseT |
Added and supported |
|
mtasNaAnnCauseTAnnName |
Added and supported |
|
mtasNaAnnCauseTRejectCode |
Added and supported |
|
mtasNaAnnCauseTRejectReason |
Added and supported |
|
MtasNaRaSipHeader |
Added and supported |
|
mtasNaRaSipHeaderGaAnnId |
Added and supported |
|
mtasNaRaSipHeaderName |
Added and supported |
|
mtasNaRaSipHeaderRejectCode |
Added and supported |
|
mtasNaRaSipHeaderRejectReason |
Added and supported |
|
mtasNaRaSipHeaderValue |
Added and supported |
|
mtasNwFoIwAsName |
Added, but not supported |
|
mtasNwPrIwAsName |
Added, but not supported |
|
MtasScaling |
Added and supported |
|
mtasScalingScaleIn |
Added and supported |
|
mtasScalingScaleOut |
Added and supported |
|
mtasScalingTimeBasedScalingEnabled |
Added and supported |
|
mtasSdsConditionalServiceKeys |
Added, but not supported |
|
mtasSdsConditionalTermCall |
Added, but not supported |
|
mtasSdsImrnNai |
Added and supported |
|
mtasSrvccAlertAckFallbackTime |
Added and supported |
|
mtasSrvccPreconditionTime |
Added and supported |
|
MtasSscMultiPersona |
Added, but not supported |
|
mtasSscMultiPersonaEnforceSscSubscribe |
Added, but not supported |
|
mtasSscMultiPersonaNegInvAnnPersonaSel |
Added, but not supported |
|
mtasSscMultiPersonaSyntInvPersonaSel |
Added, but not supported |
|
numAnaLocalCallTableSyncState |
Added and supported |
|
numberNormalisationTableSyncState |
Added and supported |
|
shutdown_timeout |
Added and supported |
|
VtasCel |
Now supported |
|
vtasCelAdministrativeState |
Now supported |
|
vtasCelDropBack |
Now supported |
|
vtasCelEventServerName |
Now supported |
|
vtasCelReportingFilterList |
Now supported |
|
vtasCelReportingHeaderFilter |
Now supported |
|
vtasConfLastMovedParticipantRemovalEnabled |
Added and supported |
|
vtasCwVersion |
Added, but not supported |
|
vtasGaAnnSessionProgressReason |
Added and supported |
|
vtasIdPresOipDisplayNameFiltering |
Added, but not supported |
|
vtasMmtDomesticRoaming |
Added, but not supported |
|
vtasMmtMidCallRenegotiationRetryAfterSupport |
Added and supported |
|
vtasMmtSipccIdentification |
Now supported |
|
vtasMmtVersion |
Added, but not supported |
|
vtasMultiPersonaAdministrativeState |
Now supported |
|
vtasMultiPersonaCapableFeatureTag |
Added, but not supported |
|
vtasMultiPersonaEnhancement |
Now supported |
|
vtasMultiPersonaInviteDelay |
Now supported |
|
vtasMultiPersonaMpcnMaxLifetime |
Added and supported |
|
VtasMultiPersonaMpcnRange |
Added and supported |
|
vtasMultiPersonaMpcnRange |
Now supported |
|
vtasMultiPersonaMpcnRangeFirst |
Added and supported |
|
vtasMultiPersonaMpcnRangeLast |
Added and supported |
|
vtasMultiPersonaOrigPolicyRejectionAnnName |
Added, but not supported |
|
VtasNaAnnCauseT |
Added and supported |
|
vtasNaAnnCauseTAnnName |
Added and supported |
|
vtasNaAnnCauseTRejectCode |
Added and supported |
|
vtasNaAnnCauseTRejectReason |
Added and supported |
|
VtasNaRaSipHeader |
Added and supported |
|
vtasNaRaSipHeaderGaAnnId |
Added and supported |
|
vtasNaRaSipHeaderName |
Added and supported |
|
vtasNaRaSipHeaderRejectCode |
Added and supported |
|
vtasNaRaSipHeaderRejectReason |
Added and supported |
|
vtasNaRaSipHeaderValue |
Added and supported |
|
VtasSscMultiPersona |
Added, but not supported |
|
vtasSscMultiPersonaEnforceSscSubscribe |
Added, but not supported |
|
vtasSscMultiPersonaNegInvAnnPersonaSel |
Added, but not supported |
|
vtasSscMultiPersonaSyntInvPersonaSel |
Added, but not supported |
|
watchdog_timeout |
Added and supported |
4.2.2.2 Changed Configuration Attributes
The changed configuration attributes are shown in Table 13.
|
Attribute Name |
Description of Changes |
|---|---|
|
DN mmasMemoryMonitoringId=1,mmasMonitoringId=1,mmasId=1 “enabled” |
"enabled" is set to false. For more information, see section Deleted Alarms. |
|
mtasCbVersion |
ENUM 3 = VERSION_3. When it is set to 3 (VERSION_3), Outgoing Communication Barring service reports 141 (INTERNATIONAL_TOLL_RESTRICTION) in charging event when call is barred because of International or International-exHC condition in barring rules. |
|
mtasCrLastCallInfoType |
New enum value 3: INDEPENDENT_OF_INTERROGATION_TIME_RELATIVE_FULL_DATE |
|
mtasCsiMapSccpStandard |
Corrected the dependency statement to “Can be set to ANSI (0) if mtasCsiMapCdGti and mtasCsiMapCgGti are NO_GT (0), GT_TT (2) or GT_TT_NP_ES (3) and if mtasCsiMapCdTt and mtasCsiMapCgTt is less than 255”. See HX37396. |
|
mtasFsfServiceFormatSuppressedServices |
New usable formats: Cr, Csa |
|
mtasFsfsServiceFormatSuppressedServices |
New usable formats: Cr, Csa |
|
mtasImrnRangeFirst |
Can be in national format. |
|
mtasImrnRangeLast |
Can be in national format. |
|
mtasMmtAsName |
The default value for this attribute will be corrected, when coming from MTAS 1.9. |
|
mtasMmtAsName |
The attribute default value is changed from "MMTelAS" to "mmt". |
|
mtasMmtSuppressEarlyMediaHeader |
Cardinality changed to 0-1 and pattern string updated to accept empty values. |
|
mtasMrControllerMrfcNodeRecoveryTimer |
Range changed from 10–7200 to 0–7200. 0 means that the timer is not started, and the MrfcNode is not put to blacklist at all. See HX52510. Value 0 is not yet supported. |
|
MtasNaAnnCause |
Changed Description to indicate, that the configuration is for the originating side. |
|
mtasNaAnnCauseAnnName |
Changed Description to indicate, that the configuration is for the originating side. |
|
mtasNaAnnCauseRejectCode |
Changed Description to indicate, that the configuration is for the originating side. |
|
mtasNaAnnCauseRejectReason |
Changed Description to indicate, that the configuration is for the originating side. |
|
mtasSccAsName |
The default value for this attribute will be corrected, when coming from MTAS 1.9. |
|
mtasSccAsName |
The attribute default value is changed from "SCCAS" to "scc". |
|
mtasSipOcDefIncrStep |
The recommended value is changed from 12 to 2. The default value is not changed. |
|
mtasStodCallPullPolicyRoaming |
There is a new possible enum value: 3=SAME_NETWORK. |
|
vDicosLogRecordSize |
Based on MTASNC-4430 the vDicos variable defined with the value of 0 to avoid extra spaces from MTASApplogs. |
|
vtasCbVersion |
ENUM 3 = VERSION_3. When it is set to 3 (VERSION_3), Outgoing Communication Barring service reports 141 (INTERNATIONAL_TOLL_RESTRICTION) in charging event when call is barred because of International or International-exHC condition in barring rules. |
|
vtasCrLastCallInfoType |
New enum value INDEPENDENT_OF_INTERROGATION_TIME_RELATIVE_FULL_DATE |
|
vtasFsfServiceFormatSuppressedServices |
New usable formats: Cr, Csa |
|
vtasFsfsServiceFormatSuppressedServices |
New usable formats: Cr, Csa |
|
vtasMmtSuppressEarlyMediaHeader |
Cardinality changed to 0-1 and pattern string updated to accept empty values. |
|
VtasNaAnnCause |
Changed Description to indicate, that the configuration is for the originating side. |
|
vtasNaAnnCauseAnnName |
Changed Description to indicate, that the configuration is for the originating side. |
|
vtasNaAnnCauseRejectCode |
Changed Description to indicate, that the configuration is for the originating side. |
|
vtasNaAnnCauseRejectReason |
Changed Description to indicate, that the configuration is for the originating side. |
4.2.2.3 Deprecated Configuration Attributes
The deprecated configuration attributes are listed in Table 14.
|
Attribute Name |
Description of Changes |
|---|---|
|
MtasChargingProfileRoReject |
Was never supported |
|
mtasChargingProfileRoRejectGa |
Was never supported |
|
mtasFunctionMmtAsName |
Upgrade from previous release – mtasMmtAsName value is copied to mtasFunctionMmtAsName. See HX31452. |
|
mtasFunctionSccAsName |
Upgrade from previous release – mtasSccAsName value is copied to mtasFunctionSccAsName. See HX31452. |
|
mtasGaAnnCauseValue |
Use mtasGaAnnSessionProgressReason instead. |
|
mtasMmtAsName |
Replaced with mtasFunctionMmtAsName |
|
mtasMrfpNodeOperationalState |
The CM is deprecated with mtasMrfpNodeOperState |
|
mtasMultiPersonaImrnLifetime |
Deprecated because IMRN acronym was changed for MPCN for readability and new CMs were introduced |
|
mtasMultiPersonaImrnRange |
Deprecated because IMRN acronym was changed for MPCN for readability and new CMs were introduced |
|
mtasMultiPersonaImrnRangeFirst |
Deprecated because IMRN acronym was changed for MPCN for readability and new CMs were introduced |
|
mtasMultiPersonaImrnRangeLast |
Deprecated because IMRN acronym was changed for MPCN for readability and new CMs were introduced |
|
mtasNwAsName |
The CM is deprecated with mtasNwPrIwAsName. During upgrade, the value of mtasNwAsName is migrated automatically to mtasNwPrIwAsName. |
|
mtasNwFoIwAsName |
Replaced with mtasFunctionNwFoIwAsName |
|
mtasSccAsName |
Replaced with mtasFunctionSccAsName |
|
SC114 and SC115 |
Deprecated |
|
vtasGaAnnCauseValue |
Use vtasGaAnnSessionProgressReason instead. |
|
vtasMultiPersonaImrnLifetime |
Deprecated because IMRN acronym was changed for MPCN for readability and new CMs were introduced |
|
vtasMultiPersonaImrnRange |
Deprecated because IMRN acronym was changed for MPCN for readability and new CMs were introduced |
|
vtasMultiPersonaImrnRangeFirst |
Deprecated because IMRN acronym was changed for MPCN for readability and new CMs were introduced |
|
vtasMultiPersonaImrnRangeLast |
Deprecated because IMRN acronym was changed for MPCN for readability and new CMs were introduced |
4.2.2.4 Obsolete Configuration Attributes
The configuration MOCs and attributes made obsolete are shown in Table 15.
|
Attribute Name |
Description of Changes |
|---|---|
|
mtasMrfpNodeOperationalState |
Not supported, obsolete, mtasMrfpNodeOperState has taken over the role of this CM |
|
mtasMrfpNodeOperationalState |
Not supported, obsolete, mtasMrfpNodeOperState has taken over the role of this CM |
|
carSelDialedStringAnalysisTableSynchronization |
CMCO – Carrier Select – made obsolete and replaced by carSelDialedStringAnalysisTableSyncState |
|
carSelCarrierTableSynchronization |
CMCO – Carrier Select – made obsolete and replaced by CarSelCarrierTableSyncState |
|
numAnaLocalCallTableSynchronization |
CMCO – Number Analysis – made obsolete and replaced by numAnaLocalCallTableSyncState |
|
numberNormalisationTableSync |
CMCO Number Normalization – made obsolete and replaced by numberNormalisationTableSyncState |
4.2.2.5 Deleted Configuration Attributes
The deleted configuration attributes are shown in Table 16.
|
Attribute Name |
Description |
|---|---|
|
This is deleted. For more information, see section Deleted Alarms. |
4.2.3 Fault Management
This section describes changed, new, and removed alarms.
4.2.3.1 New Alarms
The new alarms are shown in Table 17.
|
Alarm Name |
Description |
|---|---|
|
Forking Interworking Function License Absent |
The alarm is raised when mtasFoIwAdministrativeState is unlocked and Forking Interworking Function license is absent, expired or invalid, and snoozed when a valid license is installed. |
|
MultiPersona Service License Absent |
The alarm is raised when mtasMultiPersonaAdministrativeState is unlocked and MultiPersona Service license is absent, expired or invalid, and snoozed when a valid license is installed. |
|
MTAS Time Based Scaling |
This alarm will be raised at a specific time configured on the VNF, and is used for triggering the time based scaling feature. |
|
SRM Alarm System Resources High Usage |
This threshold-based alarm is raised when one or more system resources are above the configured limits and genericThresholdAlarmEnable is set to 1. |
|
SRM Alarm System Resources Low Usage |
This threshold-based alarm is raised when one or more system resources are below the configured limits and genericThresholdAlarmEnable is set to 1. |
4.2.3.2 Changed Alarms
The changed alarms are shown in Table 18.
|
Alarm Name |
Description of Changes |
|---|---|
|
- |
- |
4.2.3.3 Deleted Alarms
The deleted alarms are shown in Table 19.
|
Alarm Name |
Description |
|---|---|
|
MMAS, Heap Memory Load Limit Exceeded |
The alarm was raised by the Multimedia Application Server (MMAS) as part of overload protection when the heap memory load exceeds a configured threshold value. The reason to delete the alarm is because the behavior of standard Java raise the alarm, when the memory is allocated, and cease the alarm, when the garbage collection is executed. This result was a flaky alarm, without traffic impact. See HW61234. |
4.2.4 IFC Triggers
The new IFC triggers are listed in Table 20.
|
Reason |
IFC |
|---|---|
|
To trigger Forking Interworking Function on NW AS |
The Forking IWF service can be invoked by 2 levels: iFC and CM parameters within MTAS. On iFC level, the top most route header must have an ‘‘as’’ parameter with a value set to the configured CM attribute mtasNwFoIwAsName, if the generic port functionality is used. When the iFC has no condition in the rule (always adds ”as” to trigger the FoIwf AS) then additional condition can be used in MTAS with the mtasFoIwMode CM attribute to trigger FoIw functionality. |
|
The device will send a SIP MESSAGE with its own IMPU as destination. This MESSAGE should reach the MMTel AS |
Trigger the MMTel AS on either the generic SIP port or on the originating port (mtasSipTrafficOriginatingIpPort) when Method=”MESSAGE” AND SessionCase=”ORIGINATING_REGISTERED” AND Header=”Content-Type” Content=”application/vnd.call-id-info+xml” |
The changed IFC triggers are listed in Table 21
|
Reason |
IFC |
|---|---|
|
For multiple AS invocation in co-location MTAS on AS generic SIP port, the IFC triggers must contain the AS roles. Example for originating MTAS: Trigger2ApplicationServers: xxx: sip:<mtas.operator.net>; as=”scc,foiwf,mmt,priwf” The order of AS roles is specified in the Route Header “as=” |
4.2.5 Performance Measurement
This section lists new and changed, deprecated, obsolete, and deleted Performance Measurement (PM) counters.
For more information on counter description, refer to MTAS Performance Measurements.
4.2.5.1 New PM Counters
The new PM counters are listed in Table 22.
|
Counter Name |
Description |
|---|---|
|
MtasCBOCBBarredType |
Added and supported |
|
MtasCBOCBNotBarredType |
Added and supported |
|
MtasCelNOkE |
Now Supported |
|
MtasCelNOkI |
Now Supported |
|
MtasCelOk |
Now Supported |
|
MtasFoIwNOkE |
Now supported |
|
MtasFoIwNOkI |
Now supported |
|
MtasFoIwOk |
Now supported |
|
MtasMmtInitOrigPlmnSessNOkNet |
Added, but not supported |
|
MtasMmtInitOrigPlmnSessNOkService |
Added, but not supported |
|
MtasMmtInitOrigPlmnSessNOkSupportNode |
Added, but not supported |
|
MtasMmtInitOrigPlmnSessNOkUser |
Added, but not supported |
|
MtasMmtInitOrigPlmnUnregSessNOkNet |
Added, but not supported |
|
MtasMmtInitOrigPlmnUnregSessNOkService |
Added, but not supported |
|
MtasMmtInitOrigPlmnUnregSessNOkSupportNode |
Added, but not supported |
|
MtasMmtInitOrigPlmnUnregSessNOkUser |
Added, but not supported |
|
MtasMmtInitTermPlmnSessNOkNet |
Added, but not supported |
|
MtasMmtInitTermPlmnSessNOkService |
Added, but not supported |
|
MtasMmtInitTermPlmnSessNOkSupportNode |
Added, but not supported |
|
MtasMmtInitTermPlmnSessNOkUser |
Added, but not supported |
|
MtasMmtInitTermPlmnUnregSessNOkNet |
Added, but not supported |
|
MtasMmtInitTermPlmnUnregSessNOkService |
Added, but not supported |
|
MtasMmtInitTermPlmnUnregSessNOkSupportNode |
Added, but not supported |
|
MtasMmtInitTermPlmnUnregSessNOkUser |
Added, but not supported |
|
MtasMmtOrigPlmnNetworkSuccessSessionEstablish |
Added, but not supported |
|
MtasMmtOrigPlmnUnregNetworkSuccessSessionEstablish |
Added, but not supported |
|
MtasMmtTermOrigPlmnSessNOk |
Added, but not supported |
|
MtasMmtTermOrigPlmnSessNOkECause |
Added, but not supported |
|
MtasMmtTermOrigPlmnSessNOkServiceCause |
Added, but not supported |
|
MtasMmtTermOrigPlmnSessOk |
Added, but not supported |
|
MtasMmtTermOrigPlmnUnregSessNOk |
Added, but not supported |
|
MtasMmtTermOrigPlmnUnregSessNOkECause |
Added, but not supported |
|
MtasMmtTermOrigPlmnUnregSessNOkServiceCause |
Added, but not supported |
|
MtasMmtTermOrigPlmnUnregSessOk |
Added, but not supported |
|
MtasMmtTermPlmnNetworkSuccessSessionEstablish |
Added, but not supported |
|
MtasMmtTermPlmnUnregNetworkSuccessSessionEstablish |
Added, but not supported |
|
MtasMmtTermTermPlmnSessNOk |
Added, but not supported |
|
MtasMmtTermTermPlmnSessNOkECause |
Added, but not supported |
|
MtasMmtTermTermPlmnSessNOkServiceCause |
Added, but not supported |
|
MtasMmtTermTermPlmnSessOk |
Added, but not supported |
|
MtasMmtTermTermPlmnUnregSessNOk |
Added, but not supported |
|
MtasMmtTermTermPlmnUnregSessNOkECause |
Added, but not supported |
|
MtasMmtTermTermPlmnUnregSessNOkServiceCause |
Added, but not supported |
|
MtasMmtTermTermPlmnUnregSessOk |
Added, but not supported |
|
MtasMultiPersonaOrigSelAttempts |
Now supported |
|
MtasMultiPersonaOrigSelectionsNOkE |
Now supported |
|
MtasMultiPersonaOrigSelectionsNOkI |
Now supported |
|
MtasMultiPersonaOrigSelectionsOk |
Now supported |
|
MtasMultiPersonaTermSelAttempts |
Now supported |
|
MtasMultiPersonaTermSelectionsNOkE |
Now supported |
|
MtasMultiPersonaTermSelectionsNOkI |
Now supported |
|
MtasMultiPersonaTermSelectionsOk |
Now supported |
|
MtasSccInitOrigCsPlmnSessAttempts |
Added, but not supported |
|
MtasSccInitOrigCsPlmnSessNOkNet |
Added, but not supported |
|
MtasSccInitOrigCsPlmnSessNOkUser |
Added, but not supported |
|
MtasSccInitOrigCsPlmnSessOk |
Added, but not supported |
|
MtasSccInitTermCsPlmnSessAttempts |
Added, but not supported |
|
MtasSccInitTermCsPlmnSessNOkNet |
Added, but not supported |
|
MtasSccInitTermCsPlmnSessNOkUser |
Added, but not supported |
|
MtasSccInitTermCsPlmnSessOk |
Added, but not supported |
|
MtasSccTermOrigCsPlmnSessCompletionAttempts |
Added, but not supported |
|
MtasSccTermOrigCsPlmnSessNOk |
Added, but not supported |
|
MtasSccTermOrigCsPlmnSessOk |
Added, but not supported |
|
MtasSccTermTermCsPlmnSessCompletionAttempts |
Added, but not supported |
|
MtasSccTermTermCsPlmnSessNOk |
Added, but not supported |
|
MtasSccTermTermCsPlmnSessOk |
Added, but not supported |
|
MtasSdsCapInitDPRelayAttempt |
Added, but not supported |
|
MtasSdsPlmnCapInitDPOrigPlmnNOkE |
Added, but not supported |
|
MtasSdsPlmnCapInitDPOrigPlmnNOkI |
Added, but not supported |
|
MtasSdsPlmnCapInitDPOrigPlmnOk |
Added, but not supported |
|
MtasSdsPlmnImrnNOkE |
Added, but not supported |
|
MtasSdsPlmnImrnNOkI |
Added, but not supported |
|
MtasSdsPlmnImrnOk |
Added, but not supported |
4.2.5.2 Changed PM Counters
The changed PM counters are listed in Table 23.
|
Counter Name |
Description of Changes |
|---|---|
|
MtasSubsReregOk |
Fixed no increment in common scenario when mtasSubsDataInitRegHSSFetchDelay=3. See HW90791. |
4.2.5.3 Deprecated PM Counters
The deprecated PM counters are listed in Table 24.
|
Counter Name |
Description of Changes |
|---|---|
|
- |
- |
4.2.5.4 Obsolete PM Counters
The obsolete PM counters are listed in Table 25.
|
Counter Name |
Description of Changes |
|---|---|
|
- |
- |
4.2.5.5 Deleted PM Counters
The deleted PM counters are shown in Table 26.
|
Counter Name |
Description of Changes |
|---|---|
|
- |
- |
4.3 Impacts to Continuous Delivery Machinery
This section summarizes the impacts to the Continuous Delivery Machinery, which can need changes based on the listed items.
A summary of impacts is shown in Table 27.
The description of impact is as follows:
- No Impact – This change has a very low chance to have an impact on any CD Machinery or can be activated with additional configuration.
- Minor Impact – This change has a medium chance to have an impact on any CD Machinery.
- Major Impact – This change is having an impact on CD Machinery with high probability.
|
Service |
Impact |
Description of Changes |
|---|---|---|
|
Deployment |
Major |
The impact is given as major because of change in HOT files delivered with the product, but vMTAS can be deployed with previous HOT files as well. The changes are as follows:
|
|
Health Check |
Minor Impact |
Minor NBC changes on interface of Health Check triggering script: XML format report changed because of schema changes. HTML report is unchanged. |
|
Health Check |
Minor Impact |
‘SoftwareVersions’ check functionality is extended to verify if R-states of all MTAS components are the same. |
|
SS7 trace |
Minor impact |
The ss7trace.log file has changed permission to prevent others than users with root privileges to read it. Also permissions for the ss7caf-collect-info script is changed to only allow users with root privileges to execute it. This means that if still root user executes it there is no impact. If a user is belonging to system-ts group is used, a password will be required to access the script. No other users are allowed to execute. |
|
- |
- |
- |
4.4 Summary of Impacts per Feature
All MTAS nodes in the network must be upgraded before taking new services in operation. This section summarizes the impact per feature when the feature is turned on. A summary of impacts per feature is shown in Table 28.
The description of impact is as follows:
- No Impact – This change has very low chance to have an impact or can be activated with additional configuration.
- Minor Impact – This change has medium chance to have an impact.
- Major Impact – This change has an impact with a high probability.
|
Feature |
Service |
Impact |
Description of Changes |
|
CS Interworking/SDS |
No impact |
New option in the SDS function to return the destinationRoutingAddress/IMRN in CAP CONNECT in National format, without the country code, and with the NAI set to 3 (national). Configured by CM parameter mtasSdsImrnNai. | |
|
Call type validation for the destination number provisioned for abbreviated dialing |
Abbreviated Dialing |
No impact |
If call type validation for the destination number provisioned for abbreviated dialing is needed on the CAI3G interface, the CM parameter mtasAbDialCallTypeValidation must be activated. |
|
Adding date to call return announcement for calls older than two days |
Call Return |
No Impact |
Call Return service is enhanced to provide a new option for mtasCrLastCallInfoType to present relative day and date. This feature enhancement is controlled with the following CM attribute: mtasCrLastCallInfoType enum value 3. |
|
Call type validation for the destination number provisioned for abbreviated dialing |
CDiv, Abbreviated Dialing |
No impact |
If call type validation for the destination number provisioned for abbreviated dialing is needed on the Ut interface, the CM parameter mtasAbDialCallTypeValidation must be activated |
|
Communication barring enhancements |
No Impact |
ICB service of MMTel AS will support domestic roaming and can bar the calls on detecting network level roaming after the country level roaming is detected. This feature can be configured with the following CM attributes: mtasComCcmMccDestinationMapping, mtasComCcmMccDestinationMappingMappedValue, mtasComCcmMccMnc, mtasComCcmMccMncHome | |
|
Network announcement triggered by specific SIP header |
Network Announcement Service |
No Impact |
This feature is to enable MTAS to recognize a customer specific SIP header in initial INVITE, reject the call setup and play an announcement to the user. This feature is controlled with the following CM attributes: mtasNaRaSipHeaderName, mtasNaRaSipHeaderValue, mtasNaRaSipHeaderGaAnnId, mtasNaRaRejectCode, mtasNaRaRejectReason, mtasGaAnnSessionProgressReason, vtasNaRaSipHeaderName, vtasNaRaSipHeaderValue, vtasNaRaSipHeaderGaAnnId, vtasNaRaRejectCode, vtasNaRaRejectReason, vtasGaAnnSessionProgressReason. |
|
Communication barring enhancements |
No Impact |
OCB service of MMTel AS will support domestic roaming and can bar the calls on detecting network level roaming after the country level roaming is detected. This feature can be configured with the following CM attributes: mtasComCcmMccDestinationMapping, mtasComCcmMccDestinationMappingMappedValue, mtasComCcmMccMnc, mtasComCcmMccMncHome | |
|
Communication barring enhancements |
No Impact |
OCB service of MMTel AS will allow calls to additional destination country when international and internation-exHC conditions are applied. This feature can be configured with the following CM attributes: mtasComCcmMccDestinationMapping, mtasComCcmMccDestinationMappingMappedValue, mtasComCcmMccMnc, mtasComCcmMccMncHome | |
|
Network based handling of non-authorized international calls |
Outgoing Communication Barring |
No Impact |
Outgoing Communication Barring service enhanced to report new CB counters are introduced to measure number of failed calls because of barring and number of successful calls (not barred) with key as call type. The following counters are supported now: MtasCBOCBBarredType, MtasCBOCBNotBarredType. If the parameter is set and already existing user document settings are generating reject messages, the parameter mtasXdmsUtValidation can be set to (1) and selective validation is supported. In this case MMTel AS validates the received Ut request together with the user document but for CDIV and/or Abbreviated Dialing services and the validation constraints are applied only on the received request. If CDIV and/or Abbreviated Dialing services are not part of the Ut request, then the validation of those services in the user document is skipped. |
|
Announcement according to Reason header |
Network Announcement |
No impact |
Instances of the new CMs parameters will not exist after the upgrade and accordingly the new function will be disabled by default. In terminating case an announcement can be played based on combination of SIP error status code + Q.850/SIP cause code and SIP error response can be configurable, the same way as it works for originating. This is controlled by a new MOC MtasNaAnnCauseT, or for Wholesale VtasNaAnnCauseT, and its attributes. |
|
Communication Barring Service is enhanced to report SSID 141 for International or International-exHC condition in barring rules. |
Communication Barring |
No Impact |
When mtasCbVersion is set to 3 (VERSION_3), Outgoing Communication Barring service reports SSID value 141 (INTERNATIONAL_TOLL_RESTRICTION) in charging event when call is barred because of International or International-exHC condition in barring rules. |
|
Communication Barring Service is enhanced to report SSID 141 for International or International-exHC condition in barring rules. |
Communication Barring |
No Impact |
When mtasCbVersion is set to 3 (VERSION_3), Outgoing Communication Barring service reports SSID value 141 (INTERNATIONAL_TOLL_RESTRICTION) in charging event when call is barred because of International or International-exHC condition in barring rules. |
|
Ro Announcement for errors without Announcement AVP |
Online Charging |
No Impact |
MTAS can play Ro reject announcement in case any CCA-I or CCA-U message contains command or service level error code or Experimental-Result-Code AVP, even when the CCA does not contain Announcement-Instructions AVP, if CCFH action is set to TERMINATE and it is configured through CM parameters. Generic announcement will be played, if the result code entry in mtasChargingProfileRoRejectAnn matches the error result code (3xxx/4xxx/5xxx) returned in the CCA message by the OCS, or if that is not true, when mtasChargingProfileRoRejectDefaultAnnRemoteUser and/or mtasChargingProfileRoRejectDefaultAnnServedUser is configured. The generic announcement to be played is configurable through the CM parameters. The above CM parameters are configurable per charging profile. There can be multiple instaces (0–32) of mtasChargingProfileRoRejectAnn, but only a single instance of the latter two parameters. |
|
Multi-Persona on CS |
MultiPersonaService |
Minor Impact |
Multi persona selection when VoLTE UE attached to CS. See section Impact on MTAS Features. |
|
Time-based auto-scale |
VNF-LCM |
No Impact |
Time-based auto-scaling feature triggered by a preconfigured time-based alarm |
|
EM-driven instantiation |
VNF-LCM |
No Impact |
VNFs instantiated on VNF-LCM are now visible on EO (Ericsson Orchestrator) |
|
EM-driven scale |
VNF-LCM |
No Impact |
VNFs scaled on VNF-LCM are now updated on EO (Ericsson Orchestrator) |
|
Identity Presentation Enhancement for Enterprise Customers |
No Impact |
If mtasIdPresCnipAddIdParam is set to TRUE MMTel AS shall support adding the "id" parameter to the Event header after calling-name for SIP queries over the Calling Name Server (CNS) interface. |
4.5 Other Interface Impacts
All MTAS nodes in the network must be upgraded before taking new services in operation.
The changes to existing services are described in Table 29.
The description of impact is as follows:
- No Impact – New version can be installed without affecting other nodes.
- Minor Impact – There are changes, but with extra configuration the previous behavior can be kept.
- Major Impact – The change has made an interface backward incompatible.
- New Interface – The interface did not exist in the previous revision.
- Obsolete – The interface no longer exists.
|
Source of Change |
Service |
Impact |
Description of Changes |
|---|---|---|---|
|
HW82344 |
Ad-Hoc conference |
Minor Impact |
When a user is moved into the conference, ACR(start)/CCR(I) will contain User-Equipment-Info AVP. |
|
HW76654 |
SIP Upstream Overload Control |
No Impact |
Because of TR HW76654, the algorithm for calculating the SIP Upstream Overload Control oc value is changed on CBA track, since CBA platform (vDicos and CoreMW) has delay to collect the RUI value. To adapt the platform delay, two delays(5s and 7s by default) at application level are introduced which can avoid the traffic fluctuation. Beside the two application level delays, the recommended value for mtasSipOcDefIncrStep and mtasSipOcDefDecrStep are changed. For mtasSipOcDefIncrStep, it is changed from 12 to 2. For mtasSipOcDefDecrStep, it is changed from 8 to 1. |
|
HW75114 |
Scc As |
No Impact |
When mtasSccMobileBehaviour is enabled, MtasSccTermPsSuccAttempt counter is not incremented for PS access termination attempt for normal mobile subscribers. This issue has been corrected in this release. |
|
HW83145 |
NW AS |
No Impact |
The counter MtasPrIwOrigSuccess was incremented incorrectly twice for each successful session established. This is corrected in this release to be incremented only once. |
|
HW50758 |
Minor impact |
Until now, rules (CDIV and CB) and routes (SIP Trunking Control) in ST AS were not keeping the order during evaluation as were set in CAI3G Create/Set request. Now this fault has been corrected. | |
|
HX10219 |
Ad Hoc conference service |
No Impact |
Before, when the conference creator wanted to remove a non-existing participant from the conference (for example, the CP has already left), the last moved-in participant was kicked out. This behavior can be turned off from now. When this function is disabled and the specified CP is not in the conference, the REFER message is rejected. New CM attribute: mtasConfLastMovedParticipantRemovalEnabled is introduced to control this behavior. |
|
HX13418 |
No impact |
There is a possibility to use VLR-number in LocationInformation from HSS as alternative to CGI to get current location MCC. Prerequisites - configure MMTel AS NPLI to use VLR/MSC number in addition to CGI when building np PANI, terminating case. (mtasMmtNpliCSLocationInformation=1) - VLR/MSC number to be added to PANI should also be applied for originating MMTel NPLI case. This behavior can be controlled with CM mtasMmtNpliOriginatingCSLocationInformation=1; =0 legacy behavior (only CGI considered for PANI; =1 consider also VLR number or MSC number, or both, if available (same behavior as for mtasMmtNpliCSLocationInformation). | |
|
HX14241 |
DEN |
No impact |
The order of <remote> and <local> tag in XML NOTIFY body is now according to RFC 4235, Ch 4.4. The XML tag order can be configured by a new CM attribute mtasDenVersion. When set to 0 (INITIAL_VERSION), legacy behavior of the service is active. When set to 1 (VERSION_1), the <local> and <remote> tag is sent in correct order. |
|
HX19883 |
Minor impact |
When IMRN INVITE reaches O-SDS on the PSI port and the service decides to update the PANI header based on InitialDP’s location information, the service will remove incoming network-provided PANI from all further SIP messages coming from the served user during session establishment. | |
|
TR HW19418 |
No Impact |
Separated XDMS application logs: The log events generated by different applications (CAI3G, Ut/XCAP, CAI3G for SIP Trunk, GenSSC, CCMP) are recorded into different log files. The original log file “catalina.log” only records other non-application related events. For more information, refer to MTAS Troubleshooting Guideline | |
|
TR HX29166 |
No Impact |
Introduced XDMS log files retention policy: For each log type (access log, application log, Catalina log, and so on.), XDMS keeps additional 10 old archived log files based on the age, older files are removed For more information, refer to MTAS Troubleshooting Guideline | |
|
HX35573 |
No Impact |
When a new CM attribute (mtasSrvccPreconditionTime) is set to a value greater than 0, SRVCC pre-alerting access transfer INVITE will be delayed by SCC AS if there’s an early dialog that does not have QoS parameters negotiated (if preconditions are required) | |
|
HW67604 |
Alarms |
Minor Impact |
Because of an earlier fault NeLS Alarms might not be cleared even if the related features are disabled in MTAS. Now this fault is fixed, so the alarms will be ceased in this case. |
|
HX34278 |
No impact |
The new mtasSrvccAlertAckFallbackTime timer is started on ACK and fallback can then happen until it expires. If the mtasSrvccAlertAckFallbackTime time > 0, then fallback can also happen after the legacy fallback timer expires and before the new one is started (on ACK). | |
|
HX25597 |
Minor |
CDIV in MTAS is now putting "privacy=history" into the History-Info header for 180/181/183/200OK SIP messages from UE_C if reveal-identity-to-caller=false. This is to prevent C-number to be exposed to A. | |
|
HX14490 |
Ad Hoc conference |
Minor |
Ad-Hoc conference service is now sending partial notification about CP joining into the conference, when conference created using uri list and answer confirmation is enabled. Until now, nothing was sent, because of a fault. |
|
HX19590 |
PRIW |
Minor |
PRIW service is adding confirm-status attribute into the SDP of 183 session progress message sent from NWAS, requesting resource reservation confirmation from user. |
|
HX34376 |
Online Charging |
Minor Impact |
When OCS orders call termination in CCA-U (response code is 4010 with Announcement-Instruction) after call establishment, then terminating MTAS rejects the SIP session with 480 Temporarily Unavailable. |
|
HX34377 |
Online Charging |
Minor Impact |
When OCS orders call termination in CCA-I/CCA-U (response code is 4010 with Announcement-Instruction), then originating MTAS rejects the SIP session with 403 Forbidden. |
|
HX34278 |
Minor impact |
Before this update there was no possibility of PS fallback after the call was answered if the SRVCC transfer was done in alerting state. Now, if mtasSrvccAlertAckFallbackTime > 0, a (second) fallback timer is started at reception of ACK for 200OK on INVITE if the transfer was started in alerting state. A PS fallback can then occur until this timer expires. | |
|
HX45973 |
Japanese Charging |
Minor Impact |
Until now, because of an earlier fault "MtasJc ICBS Data Not Found" alarm was not raised. Now the alarm can be raised again. |
|
HX26776 |
Number Portability |
No Impact |
MTAS Number Portability Service will support replacement based on regular expressions in NAPTR response for ENUM query. |
|
HX34278 |
No Impact |
Added support for mtasSrvccAlertAckFallbackTime. The new alertAckFallback timer for SRVCC alerting is started on ACK and fallback can then happen until it expires. If the alertAckFallback time > 0, then fallback can also happen after the legacy fallback timer expires and before the new one is started (on ACK). | |
|
HX35299 |
Minor Impact |
Added a check if preconditions exist in media stream, if they are present then add the precondition tag to Require header in the provisional response to access transfer INVITE. | |
|
HX32907 |
Short Number Dialing |
Minor |
With this fix when a SND user creates an Ad-Hoc conference with uri list, the From header of the dialout INVITEs will be updated. |
|
HX38859 |
MTAS Awareness after IS recovery |
Minor Impact |
The checking of the 'initialselection' tag in top most Route header was changed to case-insensitive for MTAS Awareness after IS recovery invocation |
5 Impact on MTAS Features
This section describes the impact on vMTAS 1.14.0 features when the feature is turned on.
5.1 Enhancement of Hotline Service
New Whitelist conditional Hotline type introduced for Hotline Service No new CM parameters. The feature can be controlled with the existing Hotline Administrative state CM, and through provisioning.
Impact
No impact on capacity, performance, network elements, and operation.
5.2 VoLTE for Unified Communication Non-UC Routing Numbers
A list of specific numbers/addresses (service numbers like OSN/NSN/TollFree/ShortCode) in Business Line AS (BLAS) such that when a Business UC User dials one of these addresses, calls are not routed to the UC System.
CM parameters that control the behavior:
- mtasUCRoutingSuppressServiceNumbers = 0 (DISABLED), Legacy behavior; 1 (ENABLED), WP behavior.
- vtasUCRoutingSuppressServiceNumbers = 0 (DISABLED), Legacy behavior; 1 (ENABLED), WP behavior.
Impact
No impact on capacity, performance, network elements, and operation.
5.3 Support of External MRFC Node Failover in MMTel AS (Drop 2)
The drop 1 of the feature has been delivered into the previous release (4.10.0 and 1.10.0). In drop 1, MTAS tried to connect other MRFC Nodes, if the communication was not successful for the first candidate.
In this release, MTAS marks the non-responding nodes (mtasMrfcNodeOperationalState attribute) with the value MARKED_NOT_RESPONDING. After the configured time (specified in mtasMrControllerMrfcNodeRecoveryTimer) expires, MTAS marks that MRFC node as working again (MARKED_OK).
The duration of this timer can be controlled through the value of the mtasMrControllerMrfcNodeRecoveryTimer attribute.
Impact
No impact on capacity, performance, network elements, or operation.
5.4 VMware Instantiation and Termination Workflow
It is now possible to deploy MTAS with a 2+2 configuration on a VMware based cloud using instantiation workflow scripts. It is possible to terminate graceful and forceful MTAS using the termination workflow scripts.
Impact
No impact on capacity, performance, network elements, or operation.
5.5 New PM Job Names
The following new PM job names have been added:
PmJob=NOOSSCONTROL_MtasSla_OSProcessingUnit PmJob=NOOSSCONTROL_MtasSla_OSProcessingLogicalUnit PmJob=NOOSSCONTROL_MtasSla_OsmDevice
Impact
No impact on capacity, performance, network elements, or operation.
5.6 Identity Presentation Enhancement for Enterprise Customers
With support of this feature MMTel AS shall support adding the "id" parameter to the Event header after calling-name for SIP queries over the Calling Name Server (CNS) interface.
Impact
No impact on capacity, performance, network elements, and operation.
5.7 Support of IMRN in national format for SDS
When CM parameter mtasSdsImrnNai is set to National(1),
- T-SDS return IMRN in National format when responding in Connect message, regardless of received NAI of calledPartyNumber in IDP,
- O-SDS return IMRN in National format when responding in Connect message.
In both cases, the NAI of IMRN are set to National(3). When CM parameter mtasSdsImrnNai is set to Legacy(0), legacy behavior is applied.
Impact
No impact.
5.8 Scaling Workflows for VMware
It is now possible to execute the scaling workflows on a VMware based cloud.
Impact
No impact.
5.9 Forking Interworking Function (F-IWF)
The Forking Interworking function (F-IWF) is an interworking function provided by the Network Application Server (NW AS).
The F-IWF provides interworking between a caller device lacking support of multiple early dialogs and the IMS network.
It aggregates multiple early dialogues to a single dialogue, keeps track of the media state on multiple-dialog-side, and maps the authorized media towards the single dialog.
F-IWF can be configured to be executed on all traffic, or have a flexible invocation mechanism to trigger its execution based on the presence of a SIP header or an attribute in a SIP header in the initial INVITE.
This new feature can be configured with the following CM attributes: mtasNwFoIwAsName, mtasFoIwAdministrativeState, mtasFoIwMode, mtasFoIwInvocationHeaderName, mtasFoIwInvocationHeaderValue, mtasFoIwInvocationHeaderHandling.
The following PM counters are increased by this new feature: MtasFoIwOk, MtasFoIwNOkE, MtasFoIwNOkI.
Impact
No impact on capacity, performance, network elements, and operation.
5.10 Communication-barring Enhancements
MMTel AS takes it into consideration the additional destination country for mobile user, when international and international-exHC conditions are evaluated.
MMTel AS to bar the call based on configurations when mobile served user is calling from another carrier network in the home country.
This feature enhancement can be configured with the following CM attributes: mtasComCcmMccDestinationMapping, mtasComCcmMccDestinationMappingMappedValue, mtasComCcmMccMnc, and mtasComCcmMccMncHome.
Impact
No impact.
5.11 Mid-call Renegotiation Request Retry
MMTel AS can receive 500 error response with retry-after header for a relayed mid-dialog renegotiate request triggered by either re-INVITE or UPDATE. In such a scenario, MMTel AS retries the renegotiation request after the delay time indicated in the received retry-after header or mtasMmtReInviteRetryAfterTimeMax, whichever is less.
The function is controlled with CM mtasMmtMidCallRenegotiationRetryAfterSupport.
Impact
No impact on capacity, performance, network elements, and operation.
5.12 Network-based Handling of Non-Authorized International Calls
New CB counters are introduced to measure number of failed calls because of barring and number of successful calls (not barred) with key as call type.
The new PM counters are: MtasCBOCBBarredType, MtasCBOCBNotBarredType.
Impact
No impact.
5.13 vMTAS, Improved Serviceability Success Rate during In-service Scaling
Serviceability success rate during in service scaling of vMTAS is improved significantly. vMTAS continues to serve those ongoing transactions during scaling by not terminating the application processes which are handling those transactions.
Serviceability success rate is improved but varies depending on the CPU load when the scaling is triggered and scenarios ongoing at that time. Overload rejections and other failures observed as the CPU load increases beyond 35–40% during scaling.
This feature enhancement can be controlled with the following CM attribute: mtasFunctionScalingTerminateWaitTime.
Impact
No impact on capacity, performance, network elements, and operation.
5.14 Network Announcement Triggered by Specific SIP Header
The purpose of this feature is to enable MTAS to recognize a customer-specific call barring scenario and play an announcement to the user. The recognition is done based on checking SIP headers in the incoming initial INVITE messages.
This feature is controlled with the following CM attributes:
- mtasNaRaSipHeaderName
- mtasNaRaSipHeaderValue
- mtasNaRaSipHeaderGaAnnId
- mtasNaRaRejectCode
- mtasNaRaRejectReason
- mtasGaAnnSessionProgressReason
- vtasNaRaSipHeaderName
- vtasNaRaSipHeaderValue
- vtasNaRaSipHeaderGaAnnId
- vtasNaRaRejectCode
- vtasNaRaRejectReason
- vtasGaAnnSessionProgressReason
Impact
No impact on capacity, performance, network elements, and operation.
5.15 vMTAS, Tool for Faster and Easier Handling of Subscriber and Software Trace
The MtasTrace tool makes it possible to manage subscriber or software trace in vMTAS system in a faster and more efficient way. The tool supports easy configuration, start and stop of trace session. Generated trace messages can be tailed to new files to avoid information loss because of log rotation. CPU load monitoring and automatic deactivation of the trace session protects against system overload.
Impact
No impact on capacity, performance, network elements, and operation.
5.16 Adding Date to Call Return Announcement for Calls Older Than Two Days
MTAS is now adding date in announcement for CR invocation, if the interrogation happens after 2 days of saving last incoming call.
This feature enhancement is controlled with the following CM attribute: mtasCrLastCallInfoType enum value 3.
Impact
No impact.
5.17 Call Type Validation for the Destination Number Provisioned for Abbreviated Dialing
If call type validation for the destination number provisioned for abbreviated dialing is needed on the Ut interface, the CM parameter mtasAbDialCallTypeValidation must be activated If the parameter is set and already existing user document settings are generating reject messages, the parameter mtasXdmsUtValidation can be set to (1) and selective validation is supported. In this case, MMTel AS validates the received Ut request together with the user document, but for CDIV or Abbreviated Dialing, services and the validation constraints are applied only on the received request. If CDIV or Abbreviated Dialing, or both services are not part of the Ut request, then the validation of those services in the user document is skipped.
If call type validation for the destination number provisioned for abbreviated dialing is needed on the CAI3G interface, the CM parameter mtasAbDialCallTypeValidation must be activated.
Impact
No impact.
5.18 Support of Originating Identity Presentation Restriction Service for Priority Calls in MMTel AS
Existing privacy settings can be overridden for priority calls if the user is provisioned with override parameter and priority Originating Identity Presentation restriction. Operator will have possibility to configure via CAI3G Originating Identity Presentation Restriction for Priority Call.
A new <priority-restriction> element is introduced in the operator part of <originating-identitypresentation-restriction>.
Impact
No impact.
5.19 Interaction between CAT and MobileCommunicationWaiting
The CW service checks the provisional responses and if 180 Ringing with CWU is received it plays the CW announcement if no other announcement is playing.
CAT announcement may be suppressed if the value of mtasCatEarlyMediaInteractionTimer is bigger than zero and the following preconditions are met:
- mtasMmtTransparentMode is enabled
- mtasCwOperateMode is set to 4 (Mobile CW mode) or 5 (Mobile CW Alternate mode 1)
The CAT service starts the mtasCatEarlyMediaInteractionTimer timer on the first provisional response with the configured amount of time. When the timer expires the CAT service plays the announcement if no other announcements are being played.
The feature is controlled with the following configuration parameter:
- mtasCatEarlyMediaInteractionTimer: Sets the time-range form 0–3200 in millisecond resolution. Setting the parameter to 0 means that CAT is played on SIP 180 Ringing response (legacy behavior).
Impact
No impact.
5.20 Announcement According to Reason Header
Network Announcement service is enhanced. In terminating case an announcement can be played based on combination of SIP error status code + Q.850/SIP cause code and SIP error response can be configurable, the same way as it works for originating. This is controlled by a new MOC MtasNaAnnCauseT, or for Wholesale VtasNaAnnCauseT, and its attributes.
Impact
No impact.
5.21 Communication Event Logging
The new communication event logging function is a Rf based MMTel AS service, sending notifications about served user session communication to an external server.
Communication events will be sent to the external logging server whenever there is a communication attempt from/towards served user. The event includes information about type of session state event, time, calling party, called party, subscription information, and so on.
The feature is controlled by the new mtasCel MOC.
It is possible to provision this service both individually per subscriber and per groups of subscribers (Service Profile) and per MMTel context (Multi-Persona).
Impact
There is minor impact on capacity and performance when feature is enabled and provisioned.
5.22 vMTAS Workflow Enhancement When Used with Ericsson Orchestrator
The Ericsson Orchestrator (EO) is enhanced in a way that if an instance is successfully terminated in the VNF Life Cycle Manager (VNF-LCM), then it will be removed from the EO too.
Impact
No additional impact.
5.23 Ro Announcement for Errors Without Announcement AVP
MTAS plays Ro reject announcement in case any CCA message contains command or service level error code or Experimental-Result-Code AVP, even when the CCA does not contain an Announcement-Instructions AVP, if CCFH action is set to TERMINATE.
It can be configured and controlled through the following CM parameters:
The mtasChargingProfileRoRejectAnn CM parameter determines the announcement package to be played in case of a specific reject code. Announcement played to the served user, when the reject result code in the CCA-I on originating side, or in the CCA-U on both sides matches the result code configured in the CM parameter.
Example: mtasChargingProfileRoRejectAnn = "4012|RoRejectAnnouncement". If the reject code in the CCA message is 4012, then the RoRejectAnnouncement keyed Generic announcement will be played to the served user.
The mtasChargingProfileRoRejectDefaultAnnRemoteUser CM parameter determines the announcement package to be played for call termination to the remote user when CCR-I rejected on the terminating side.
The mtasChargingProfileRoRejectDefaultAnnServedUser CM parameter determines the announcement package to be played for call termination to the served user, when CCR-I rejected on the originating side, or, when CCR-U rejected on both sides.
Example: mtasChargingProfileRoRejectDefaultAnnServedUser = "DefaultRoRejectAnnouncement". If the reject code in the CCA message not matches the entries configured in mtasChargingProfileRoRejectAnn or mtasChargingProfileRoRejectAnn is not configured, then the DefaultRoRejectAnnouncement keyed Generic announcement will be played to the served user.
If both mtasChargingProfileRoRejectDefaultAnnServedUser and mtasChargingProfileRoRejectAnn CM parameters are configured and the reject code in the CCA message matches an entry in mtasChargingProfileRoRejectAnn, then the latter takes precedence.
These CM parameters are configurable per charging profile. There can be multiple instaces (0–32) of mtasChargingProfileRoRejectAnn, but only a single instance of mtasChargingProfileRoRejectDefaultAnnRemoteUser and mtasChargingProfileRoRejectDefaultAnnServedUser per charging profile.
Impact
By default, there is no impact. There can be additional strain on MRF resources, when the feature is enabled and configured by the CM parameters (announcement will be ordered from the MRF by MTAS for CCA messages containing error response), depending on the details of the configuration.
5.24 Graceful locking from vMRF
New service change method graceful reason 908 is supported, this triggers graceful shutdown. After receiving this service change new connections will not be allowed (no more add message allowed), but ongoing transactions will not be affected. After all connection has been gracefully subtracted, operationalState will be linkDown (previously disabled, this means SCTP link is down).
A new CM parameter is introduced to indicate this state. The CM parameter is called mtasMrfpNodeOperState. The following states are represented with this CM:
- linkDown := 0 (SCTP link is down)
- linkUp := 1 (SCTP link is up)
- linkShuttingDown := 2 (SCTP link is up, but we do not allow new connections)
The state linkShuttingDown represents the new function, graceful locking.
Impact
No impact.
5.25 Multi-Persona on CS
The Multi-Persona service enables a mobile subscriber to use different personas (identities) at incoming and outgoing communication. Multi persona selection when originating VoLTE UE attached to CS. Multi persona indication when terminating VoLTE UE attached to CS . For more information refer to Multi-Persona Service in MTAS.
This feature can be controlled with the following CM attributes:.
- mtasMmtSipccIdentification
- mtasMultiPersonaAdministrativeState
- mtasMultiPersonaEnhancement
- mtasMultiPersonaInviteDelay
- mtasMultiPersonaMpcnMaxLifetime
- mtasMultiPersonaMpcnRange
- mtasMultiPersonaMpcnRangeFirst
- mtasMultiPersonaMpcnRangeLast
This feature requires a license to work: MtasMultiPersona or vMtasMultiPersona.
This feature uses the following counters for Performance Measurement:
- MtasMultiPersonaOrigSelAttempts
- MtasMultiPersonaOrigSelectionsNOkE
- MtasMultiPersonaOrigSelectionsNOkI
- MtasMultiPersonaOrigSelectionsOk
- MtasMultiPersonaTermSelAttempts
- MtasMultiPersonaTermSelectionsNOkE
- MtasMultiPersonaTermSelectionsNOkI
- MtasMultiPersonaTermSelectionsOk
This feature may raise the following new alarm: MultiPersona Service License Absent.
Impact
No impact on capacity, performance, network elements, and operation.
Minor impact. For backward compatibility with legacy behavior during upgrade the CM mtasMultiPersonaAdministrativeState is to be set to UNLOCKED.
5.26 Increased Number of Rating Centers in Number Analysis
The cardinality of CM attribute NumAnaRatingCenter is increased from the present 5000 to 7000.
Impact
No impact on capacity, performance, network elements, and operation.
5.27 Support for ANSI network (CAP)
Previously ITU standard and Global Title was hardcoded for the CAP interface.
Now support for configuration of standard (ITU or ANSI) used on the CAP signaling network is added. Configuration can be done with the mtasCsiCapSccpStandard CM attribute.
Support for configuration of Global Title is added. This feature can be configured with the following attributes:
- mtasCsiCapCdGti
- mtasCsiCapCdNai
- mtasCsiCapCdNp
- mtasCsiCapCdTt
- mtasCsiCapCdEs
- mtasCsiCapCgGti
- mtasCsiCapCgNai
- mtasCsiCapCgNp
- mtasCsiCapCgTt
- mtasCsiCapCgEs
Impact
No impact.
5.28 Removal of Multiple AS Invocation in Co-Location Scenarios
When multiple AS roles are co-located, MTAS supports to invoke these AS roles by one ISC triggering on generic SIP port. The invoked AS order is specified in the top Route header “as=”, as the following example:
Route:sip:mtas.operator.net; as="scc,foiwf,mmt,priwf"
Impact
No impact on capacity, performance, network elements and operation.
5.29 Time-Based Auto-Scale
The customer can now configure an auto scaling operation (by configuring a timestamp and a scaling type – in/out – with additional scaling information via ECLI). The scale-out and scale-in workflows can be triggered automatically based on alarms which will be raised at the specific time configured on the VNF. The ENM triggers a scale workflow on VNF-LCM based on the alarm from the VNF.
Newly introduced alarm: MTAS Time Based Scaling
Newly introduced MOC: MtasScaling MOC
Impact
Scaling is a deliberate operation with direct impact on the capacity of the VNF. No impact on network elements and operation.
5.30 EM-Driven Instantiation
After a successful instantiation operation, started from the VNF-LCM, has been finished successfully, a newly created virtual application belonging to the newly instantiated VNF is available in the EO (Ericsson Orchestrator) as well.
Impact
No impact on capacity, performance, network elements and operation.
5.31 EM-Driven Scaling
If an instance has been deployed from the EO (Ericsson Orchestrator), then after a successful scaling operation, started from the VNF-LCM, has been finished successfully, the newly updated stack-related information (number of virtual machines, IDs of VMs, and so on.) are available in the EO as well.
Impact
Scaling is a deliberate operation with direct impact on the capacity of the VNF. No impact on network elements and operation.
5.32 Support Hardware Watchdog for Intel 6300 ESB
vMTAS now supports the lde-watchdogd function that LDE provides as a CSM (CBA system model) component. lde-watchdogd provides a configurable watchdog daemon which periodically resets the watchdog timer by writing to /dev/watchdog.
The watchdog device can be real hardware, or emulated hardware, (for example, by a KVM hypervisor), or fully implemented in software as a kernel module.
In case of a hardware watchdog device, the LDE agent watchdog daemon relies that its driver (kernel module) is loaded. This is determined by checking for the existence of /dev/watchdog. If this file is not there when the LDE agent watchdog service is started, the service will attempt to load a software watchdog (softdog). This will result in /dev/watchdog appearing albeit backed by a software implemented "device".
The watchdog configuration used by the LDE watchdogd component is set using the following parameters (provided in the CSM component configuration file lde-agents-watchdogd.yaml):
- watchdog_timeout: Time frame from the last received ping until the watchdog device triggers
- interval_timeout: Every interval_timeout a ping is sent to the watchdog device by the watchdog daemon
- shutdown_timeout: When the watchdog daemon is stopped, the time that watchdog device waits is set to shutdown_timeout value. It is used to ensure watchdog device triggers if a reboot hangs for any reason.
Impact
No impact on capacity, performance, network elements and operation.
5.33 vMTAS Improved Resilience to Network Disturbances
To make vMTAS more resilient to network disturbances, the time-out value has been increased from 1500 milliseconds to 5000 milliseconds on the internal network interface (TIPC).
Impact
No impact on capacity, performance, network elements and operation.