Contents
1 Introduction
This Network Impact Report (NIR) describes how the Virtual Multimedia Telephony Application Server (vMTAS) 1.10 with new and enhanced features affects the vMTAS 1.9. 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
- Alternative Presentation Number for UK Market
- Support for FQDN as PAI in SIP SUBSCRIBE to CSCF
- SIP P-Early-Media Header Support and Early Delivery of the SDP Answer
- Support Change of Payload Type Number in a Session
- AS Interworking Filtering of SIP 181
- PC: Extension to Feature Assume Positive on Ro
- PC: Generic Test Call Announcement Service
- Robust Handling of re-INVITE Requests
- CC Recall Without Answer Captured in Charging
- Subscription-ID AVP without MSISDN and IMSI in Charging
- MTAS NPLI Query at Session Release
- Call Return service based on From Header.
- Re-Invite/ACK Race Condition Handling when Acting as UAS
- NW Level Licensing, Capacity for vMTAS
- Multi-Sim Phase-2 Single IRS Support in MTAS
- National Dialing Plan
- Increase Size of CDiv Blacklist
- Support for 2nd External MRFC FQDN
- "etc” Hardened Overlay
- SCTP Support for Diameter
Enhanced Features
- Alignment of MTAS Call Return with PSTN
- Latest Location Info in Charging
- Reporting PLMN ID in S8HR
- MTAS Selection Between MMTel AS and SCC AS
- Reporting Ro Failure over Rf
- Selective Validation of XDMS Documents
- SSC Announcement Handling for OCB Operations
- Improved Early Dialog Handling in CDIV
For more information on the changed features, see Section 5 Impact on MTAS Features.
2 General Impact
This section describes the general impact owing to the introduction of the vMTAS 1.10.
2.1 Backward Compatibility
The vMTAS 1.10 is backward compatible and unless stated otherwise, legacy behavior is preserved.
2.1.1 Interoperable Network Elements
The interoperable Network Elements for vMTAS 1.10 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. |
|
7.0 CP2 | |
|
15B | |
|
ENM |
vMTAS Lifecycle Management requires 17.15(-3.6.8) version of VNF-LCM; therefore use the 18A release of ENM. |
2.2 Capacity and Performance
2.2.1 Subscriber Capacity
The subscriber capacity is not affected by the introduction of the vMTAS 1.10.
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
The in-service network performance and traffic capacity is slightly affected by the introduction of the vMTAS 1.10. The network performance and traffic capacity is degrading around 1-2% compared to vMTAS 1.9 on small setups (2+2). On larger setups the degradation is even smaller.
3 Licenses
This section lists the new and changed license codes added in vMTAS 1.10. For a list of (v)MTAS licenses, refer to MTAS Licenses,
3.1 New Licenses
|
Name |
Identity |
Version |
|---|---|---|
|
vMtasSTBaseCapacity |
CXC 401 2234 |
1.0 |
|
vMtasNWCommIwfBaseCapacity |
CXC 401 2235 |
1.0 |
3.2 Changed Licenses
There are no changed licenses.
3.3 Deleted Licenses
The deleted licenses are listed in Table 3
|
Name |
Identity |
Version |
|---|---|---|
|
vMtasSTBase |
CXC 401 2189 |
- |
|
vMtasNWCommIwfBase |
CXC 401 2190 |
- |
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 4.
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 Change Compared to vMTAS 1.9 |
|---|---|---|---|
|
No Impact |
Application constraint updated from: "Failed to meet an application constraint: Flexible Identity Presentation Failure: Activate without FIP identity/MSN FIP identity or previously stored FIP identity/MSN FIP identity is not allowed" to "Failed to meet an application constraint: Flexible Identity Presentation Failure: Activation without at least one of fip-identity, msn-fip-identity, fip-use-default-impu-identity, or fip-alternative-user-identity is not allowed". | ||
|
Rf |
DIAMETER |
No Impact |
New SSID "FIP Alternative User Identity" added. Will be populated when From header of the INVITE is updated with provisioned “fip-alternative-user-identity” |
|
Ro, Rf |
DIAMETER |
Minor impact |
CM mtasChargingProfileMultiDeviceMode is introduced to replace legacy CM mtasChargingProfileMultiDevice in HV95839. Legacy CM will be phased out in future release. The new CM attribute defines if multi-device charging is applied or not. If applied, then specific per device information will be provided to CCF (offline charging) and/or ECF (online charging). When multi-device online charging is applied, fixed devices are handled separately from mobile devices in that CCR is sent even if “out of credit” response was received for the mobile. Possible Values: 0, 1, 2, or 3.
|
|
No Impact |
It is possible to use FQDN identity for MTAS in From and PAI headers in SUBSCRIBE messages for Reg Event packages sent to I/S-CSCF On MTAS 4.9/1.9 the FQDN address can be set by mtasSystemConstantSC ID 4. It is controlled by mtasFunctionFqdn CM parameter. | ||
|
Minor Impact |
The new CM mtasSdsPaniPolicy is introduced and defines the PANI Policy being used in O-SDS service for ICS MO calls. With value 0, always create a network-provided PANI based on the location information in CAP IDP and replace incoming PANI (if any). With value 1, use the network-provided PANI in the incoming INVITE if it is present and with a valid cell id. If the incoming PANI is network-provided but invalid, use its access-type and the location information in the CAP IDP to create a PANI. If no incoming network-provided PANI, create one based only on the CAP IDP. | ||
|
No Impact |
New option to let MTAS handle early dialog BYE in a transparent way. For a complete description of the mtasSipTransparentEarlyBye attribute, refer to [3] | ||
|
No Impact |
For early UPDATE containing dynamic codec mapping, MTAS generates dummy SDP answer in accordance with RFC 3264. | ||
|
No Impact |
A new CM mtasMmtReInviteRetryAfterSupport is introduced and it enables the feature of retrying re-INVITE request on final response 500 with Retry-After header. The feature is used when re-INVITE is sent by an MMTel service for session renegotiation after B-party answer. Another related new CM mtasMmtReInviteRetryAfterTimeMax is introduced and it sets the maximum value of the re-INVITE retry time. The received Retry-After value is truncated to the upper limit if exceeds. MMTel AS supports Retry-After header in final response 500 requests both in received and sent directions. The support is service dependent. | ||
|
No Impact |
The AS Interworking filtering of SIP 181 responses from the terminating network (mtasAsIw181Filtering). | ||
|
Rf |
DIAMETER |
No Impact |
New SSI AVP value added. Will be populated in the ACR Event messages on the TA service invocation when the TA service is enabled. |
|
No Impact |
Due to TR HW30669, MTAS provides a new option of handling its own created TCP connections towards to the peer node. By configuring mtasSystemConstant SC 97 to 1, the new behavior will be applied, that is, MTAS can create one TCP connection towards to the same peer (same peer IP address and same destination port) per PL at maximum. The legacy behavior is MTAS can create one TCP connection towards to the same peer per vCPU for the same session case at maximum. | ||
|
Ut |
No Impact |
Application constraint updated from: "Failed to meet an application constraint: Flexible Identity Presentation Failure: Activate without fip identity or previously stored fip identity is not allowed." to: "Failed to meet an application constraint: Flexible Identity Presentation Failure: Activation without at least one of fip-identity, msn-fip-identity, fip-use-default-impu-identity or fip-alternative-user-identity is not allowed" | |
|
Ro,Rf |
DIAMETER |
No Impact |
The new CM mtasCcChargEventOnCcRecallFailure is introduced to trigger an ACR(Event)/CCR(Event) for unsuccessful Communication Completion Recall. Possible Values: 0,1,2.
|
|
Major Impact |
After TR HW28585, MTAS starts to correctly form the to-tag and from-tag in the Replaces header for the REFER SIP message, that is, to follow the rule in RFC3891, chapter 3 | ||
|
TCP/UDP |
Major Impact |
After TR HW42483, Retry-After header is removed in reply when MTAS is graceful shutting down. | |
|
TCP/UDP |
Major Impact |
After TR HW50409, default value of AS parameter in B line (SDP) is set to 96kbit/sec instead of 64kbit/sec. | |
|
TCP/UDP |
Minor Impact |
After TR HV11525, if a 491 Request Pending is received MTAS will resend the reInvite according to RFC 3261, section 14.1 | |
|
Ro |
DIAMETER |
No Impact |
The new CM mtasChargingProfileSuppressRoMsisdnImsiSubscriptionId AVP is introduced to suppress reporting MSISDN and IMSI in the SubscriptionId AVP in online charging (CCR event). Possible Values: TRUE, FALSE. FALSE (DISABLED) - When this attribute is set to FALSE then MSISDN and IMSI will be reported in subscriptionID AVP if value is available. TRUE (ENABLED)- When this attribute is set to TRUE then MSISDN and IMSI not will be reported in subscriptionID AVP even if value is available. |
|
Rf |
DIAMETER |
No Impact |
The new CM mtasChargingProfileSuppressRfMsisdnImsiSubscriptionId AVP is introduced to suppress reporting MSISDN and IMSI in SubscriptionId AVP in offline charging (ACR event). Possible Values: TRUE, FALSE. FALSE (DISABLED) - When this attribute is set to FALSE, then MSISDN and IMSI is reported in subscriptionID AVP if value is available. TRUE (ENABLED)- When this attribute is set to TRUE, then MSISDN and IMSI is be reported in the subscriptionID AVP even if value is available. |
|
Minor impact |
TR HW14048 impact: MTAS chooses transport protocol according to configuration of CMs mtasSipDisableLargeMsgCheck and mtasSipProtocolMtasOrigCall. The first one disables switching of protocol when large message received. The second one defines transport protocol to use, when normal message is received. For a complete description of the CM attributes, refer to MTAS Parameter Description | ||
|
No Impact |
TR HW21125 impact: Request will be rejected with "Failed to meet an application constraint: Communication Distribution Failure: Rule id="<rule-id>", identity is not SIP or TEL URI in "one"", if identity is not a valid SIP or TEL URI.(1) | ||
|
Ut |
No Impact |
TR HW21125 impact: Request will be rejected with "Failed to meet an application constraint: Communication Distribution Failure: Rule id="<rule-id>", identity is not SIP or TEL URI in "one"", if identity is not a valid SIP or TEL URI. | |
|
SS7CAF Configuration |
SCTP, FEIF |
Minor impact |
One configuration file/object for SCTP and FEIF is used for all instances (PLs). Old configuration version for ECM will be migrated to new version automatically during upgrade. |
|
Mp |
H.248 |
No impact |
New variable types supported are int(ordinal) and month |
|
Minor Impact |
A 500 final response which includes the Retry-After header is sent by the originating MMTel AS if a re-INVITE request is received followed by ACK for the initial INVITE. This behavior is configured by the mtasSipRetryAfterSupport and mtasSipRetryAfterTime CM attributes. | ||
|
Sh |
Diameter |
No impact |
TR HW41809 impact: for CAI3G Create/Set/Get/Delete requests on MMTel document, when CM parameter mtasXdmsCai3gIrsDefaultImpuUsage set to: · ‘0’, (default) MTAS/XDMS uses the received IMPU to do the provisioning towards HSS · ‘1’: MTAS/XDMS first query HSS for the IRS, then retrieves the default IMPU from the IRS and uses that IMPU to do the provisioning |
|
Ro and Rf |
Diameter |
Major impact |
MTAS reports Access-Network-Information and 3GPP-MS-TimeZone AVPs taken from PANI header in BYE or BYE response to Ro and Rf. When CM attribute mtasChargingProfileReportAtDisconnection is set to 1, charging termination is triggered at BYE response when session release is sent by the remote side. In this case, in ACR Stop/CCR Terminate, ANI AVP contains information retrieved from PANI Header in BYE response from the served user; in addition, SIP-Response-Timestamp AVP is reported in Timestamps (group AVP) in ACR Stop/CCR Terminate; SIP-Response-Timestamp-Fraction AVP is also reported if Rf/Ro version is 3GPP release 9 or higher. When ANI AVP is collected from PANI header in BYE or BYE response from the served user, it is reported in ACR Stop/CCR Terminate regardless of having been reported in previous charging messages or not. |
|
Rf |
Diameter |
No impact |
When OCS failure detected existing Ro-Information AVP may contain also Event-Time, CC-Time and Result-Code AVPs. Embedded AVPs are by default added to mtasChargingProfileOmitAcr MO therefore will be sent only when removed from the omit list. New values introduced in Ro-Status enumeration which can be sent in Ro-Information AVP when OCS failure detected. |
|
Minor impact |
Support of <pvni> XML element in Extended RegInfo, which is part of the “Extended Registration Event Notification Support” procedure. It used to fetch contact data from S-CSCF after a MTAS failover. The Extended RegInfo is an Ericsson proprietary extension to RegInfo event package specified in RFC 3860. | ||
|
Minor impact |
MMTel AS and SCC AS supports the P-Visited-Network-ID header format containing VPLMN ID as per GSMA IR.65 v25.0. | ||
|
Ro and Rf |
Diameter |
Minor impact |
MMTel AS reports IMS-Visited-Network-Identifier AVP to Ro and Rf. IMS-Visited-Network-Identifier AVP contains the contents of the SIP P-header "P-Visited-Network-ID". |
|
Rf |
Diameter |
Minor impact |
SCC AS reports IMS-Visited-Network-Identifier AVP to Rf. IMS-Visited-Network-Identifier AVP contains the contents of the SIP P-header "P-Visited-Network-ID". |
|
Ro and Rf |
Diameter |
No Impact |
MMTel AS reports 3GPP-MS-TimeZone AVP with Time Zone information taken from the network provided PANI header to Ro and Rf. |
|
Rf |
Diameter |
No Impact |
SCC AS reports 3GPP-MS-TimeZone AVP with Time Zone information taken from the network provided PANI header to Rf. |
|
No Impact |
MMTel AS adds a predefined caller preference (ps_wlan) in case served user has an active Roaming condition and is currently on WiFi access. This caller preference value is used by the TADS function of SCC AS, forcing to hunt the user on WiFi access only. | ||
|
Ro and Rf |
Diameter |
No Impact |
MMTel AS reports new value INCOMING_COMMUNICATION_ALLOWED_ON_WIFI code in Supplementary-Service-Identity to Ro and Rf. |
|
Ro |
Diameter |
Major impact |
Supplementary-Service-Information AVP is reported in CCR-U instead of CCR-T by ICB for media barring decision when SDP offer from B is sent in final response. |
|
Mr |
Major impact |
In any case, when a new resource is to be allocated on an external MRFC, the allocation fails, a second external MRFC will be contacted with the same request, based on the mtasMrfcNode MOC configuration. | |
|
Mr |
Major impact |
The configuration of an External MRFC Node with mtasMrControllerName is deprecated. If the configuration is still needed, a new mtasMrfcNode MOC should be created in the following way: Create one new instance and copy the value of ‘mtasMrControllerName’ to its ‘mtasMrfcNodeHostName’ attribute and set ‘mtasMrfcNodeAdministrativeState’ to UNLOCKED if the Node is to be used. This configuration change will be done automatically in the case, when no mtasMrfcNode MOC is configured. In this case the ‘mtasMrfcNodeHostName’ attribute will be “DEFAULT_MRF”. | |
|
ISC, Ma |
Major impact |
MMTel AS and SCC AS is starting to use the AS generic SIP port instead of using dedicated SIP ports for each session case and registration state. The use of the AS generic SIP port requires that the Application server trigger in HSS includes the AS name in the trigger. The AS name is added in the Route header in the ‘as=’ parameter. Route:< sip:mtas.operator.net; as=MMTelAS; lr > Route:< sip:mtas.operator.net; as=SCCAS; lr > To be able to determine the session case and reg state the P-Served-User header must be included in the SIP request. The AS generic SIP port is also handling the PSI functionality over the MA interface. In this case the AS name must not be included in the Route header. The currently used AS choosing algorithm, based on the configured ports, is deprecated now. | |
|
ISC, Ma |
No impact |
If CM attribute mtasSipRetryAfterSupport is set to retryAfterSupportUasEnabled, then, on receipt of re-INVITE followed by ACK for 200 OK (INVITE or re-INVITE), MTAS responses 500 Internal Server Error including a Retry-After header, indicating the time (mtasSipRetryAfterTime second) which the resend re-INVITE should be delayed. | |
|
Sh/Dh |
DIAMETER |
No impact |
If CM attribute mtasSipRetryAfterSupport is set to retryAfterSupportUasEnabled, then, on receipt of re-INVITE followed by ACK for 200 OK (INVITE or re-INVITE), MTAS responses 500 Internal Server Error including a Retry-After header, indicating the time (mtasSipRetryAfterTime second) which the resend re-INVITE should be delayed. |
|
Ro/Rf |
DIAMETER |
No impact |
vMTAS supports Multi-Homing transport for SCTP for Diameter over Ro/Rf interfaces as vMTAS reference connectivity profile 2 shall be default profile. This is changed from previous profile where TCP was used for Diameter. |
|
DIAMETER |
No impact |
vMTAS supports Multi-Homing transport for SCTP for Diameter over CDS interface as vMTAS reference connectivity profile 2 shall be default profile. This is changed from previous profile where TCP was used for Diameter. | |
|
SIGTRAN |
No impact |
vMTAS supports Multi-Homing transport for SCTP for SIGTRAN as vMTAS reference connectivity profile 2 shall be default profile. This is changed from previous profile where multi-homing for SCTP was not used. | |
|
SIGTRAN |
No impact |
vMTAS supports Multi-Homing transport for SCTP for SIGTRAN as vMTAS reference connectivity profile 2 shall be default profile This is changed from previous profile where multi-homing for SCTP was not used. |
(1) This message already exists in the IWD “MTAS
CAI3G interface”.
4.2 Operation and Maintenance
This section describes changes to attributes, alarms, events and notifications, triggers, and counters.
4.2.1 Provisioning
There are no deleted attributes.
4.2.1.1 New Attributes
The new attributes are listed in Table 5.
|
Interface |
Protocol |
Impact |
Description of Change Compared to vMTAS 1.9 |
|---|---|---|---|
|
No Impact |
Service "Flexible-Identity-Presentation" introduces a new element: <fip-alternative-user-identity> | ||
|
Ut |
No Impact |
Service "Flexible-Identity-Presentation" introduces a new element: <fip-alternative-user-identity> | |
|
Sh |
DIAMETER |
No Impact |
Service "Flexible-Identity-Presentation" introduces a new element: <fip-alternative-user-identity> |
4.2.1.2 Changed Attributes
|
Interface |
Protocol |
Impact |
Description of Changes |
|---|---|---|---|
|
No Impact |
Service "Flexible-Identity-Presentation" extends the existing element: <fip-identity> to support nil operation. | ||
4.2.2 Configuration
This section describes changed, deprecated, obsolete, and new attributes.
For more information on attributes and parameters, refer to vMTAS Master Parameter Value List.
4.2.2.1 Changed Attributes
4.2.2.2 Deleted Attributes
4.2.2.3 Deprecated Attributes
|
Attribute Name |
Description |
|---|---|
|
mtasCcInbandInvocationTimer |
Deprecated but still used in the release |
|
mtasCrFirstDigitTimeout |
Deprecated but still used in the release |
|
mtasCrInterDigitTimeout |
Deprecated but still used in the release |
|
mtasMrControllerName |
From now on ‘mtasMrfcNode’ will be used instead of ‘mtasMrControllerName’ on the following way: So far mtasMrControllerName was used as a default MRF to contact, in the case of no UNLOCKED mtasMrfcNode was configured. From now on, instead of the mtasMrControllerName, a new mtasMrfcNode should be configured if needed. |
|
mtasSipTrafficOrigIpPort |
|
|
mtasSipTrafficOrigUnregIpPort |
|
|
mtasSipTrafficTermIpPort |
|
|
mtasSipTrafficTermUnregIpPort |
|
|
mtasSipSccOrigPort |
|
|
mtasSipSccOrigUnregPort |
|
|
mtasSipSccTermPort |
|
|
mtasSipSccTermUnregPort |
|
|
mtasSipPsiPort |
Will not be used when AS generic SIP port is used for the MA interface |
|
mtasMrControllerName |
Deprecated, but can be used in this release |
4.2.2.4 Obsolete Attributes
|
Attribute Name |
|---|
|
mtasChargingProfileReportPani |
4.2.2.5 New Attributes
The new attributes are listed in Table 9.
|
Attribute Name |
Description |
|---|---|
|
mtasAsIw181Filtering |
Added and supported |
|
mtasCcChargEventOnCcRecallFailure |
Now supported |
|
mtasChargingProfileTermCcaUpdateEvaluation |
Added but not supported |
|
mtasChargingMrfUserInputErrorHandlingProfile |
Added but not supported |
|
mtasChargingProfileOrigCcaUpdateEvaluation |
Added but not supported |
|
mtasChargingProfileReleaseReason |
Added but not supported |
|
mtasChargingProfileMultiDeviceMode |
Now supported |
|
mtasChargingProfileSuppressRfMsisdnImsiSubscriptionIdAVP |
Now supported |
|
mtasChargingProfileSuppressRoMsisdnImsiSubscriptionIdAVP |
Now supported |
|
mtasChargingTimeZoneSource |
Now supported |
|
mtasChargingProfileReportAtDisconnection |
Now supported |
|
mtasConfMrfUserInputErrorHandlingProfile |
Added but not supported |
|
mtasChargingProfileAssumePositiveDefaultCcfh |
Now supported |
|
mtasIcbRoamingCallerPreferenceWifi |
Now supported |
|
mtasGmPemRemoval |
Now supported |
|
mtasMmtAsName |
Added but not supported in this release, default value MMTelAS used |
|
mtasMmtRoamingCheckMode |
Now supported |
|
MtasMmtNoSubscription |
Added and supported |
|
mtasMmtReInviteDelayTime |
Now supported |
|
mtasMmtReInviteRetryAfterSupport |
Now supported |
|
mtasMmtReInviteRetryAfterTimeMax |
Now supported |
|
mtasMmtNpliOriginatingOnSessionRelease |
Now supported |
|
mtasMmtNpliTerminatingOnSessionRelease |
Now supported |
|
mtasMrControllerMrfcNodeRecoveryTimer |
Now supported |
|
mtasMrfcNodeOperationalState |
Now supported |
|
mtasPemIwfAdministrativeState |
Now supported |
|
mtasSccAsName |
Added but not supported in this release, default value SCCAS used |
|
mtasSccNpliOriginatingOnSessionRelease |
Now supported |
|
mtasSccNpliTerminatingOnSessionRelease |
Now supported |
|
mtasSdsCreatePvni |
Now supported |
|
mtasSipTransparentEarlyBye |
Added and supported |
|
mtasSscCdivTargetNumberDenorm |
Now supportedd |
|
mtasPemIwf199SupportedIndication |
Added and supported |
|
mtasSrvccR12Charging |
Added and supported |
|
mtasSdsPaniPolicy |
Added and supported |
|
mtasStodCallPullPolicyRoaming |
Now supported |
|
MtasTa |
Now supported |
|
mtasTaAdministrativeState |
Now supported |
|
MtasTestAnnNumbers |
Now supported |
|
mtasTestAnnNumbersGa |
Now supported |
|
mtasTestAnnNumbersNum |
Now supported |
|
mtasXdmsCai3gIrsDefaultImpuUsage |
Now supported |
|
vtasCcChargEventOnCcRecallFailure |
Now supported |
|
vtasSscCdivTargetNumberDenorm |
Now supported |
|
mtasCcMrfUserInputErrorHandlingProfile |
Added but not supported |
|
mtasFcdMrfUserInputErrorHandlingProfile |
Added but not supported |
|
mtasCrMrfUserInputErrorHandlingProfile |
Added but not supported |
|
mtasCrCallingPartyDenorm |
Now supported |
|
mtasCrPrivacyCallSavedTodayAnnName |
Now supported |
|
mtasCrPrivacyCallSavedYesterdayAnnName |
Now supported |
|
mtasCrPrivacyCallSavedDayAndMonthAnnName |
Now supported |
|
mtasCrPromptTodayAnnName |
Added but not supported |
|
mtasCrPromptYesterdayAnnName |
Now supported |
|
mtasCrPromptDayAndMonthAnnName |
Now supported |
|
mtasCrPlayCollectFailureAnnName |
Now supported |
|
mtasCrUnavailableSavedAnnName |
Now upported |
|
mtasCrUseFromHeader |
Added but not supported |
|
vtasCcMrfUserInputErrorHandlingProfile |
Added but not supported |
|
vtasConfMrfUserInputErrorHandlingProfile |
Added but not supported |
|
vtasCrMrfUserInputErrorHandlingProfile |
Added but not supported |
|
vtasFcdMrfUserInputErrorHandlingProfile |
Added but not supported |
|
vtasCrCallingPartyDenorm |
Added but not supported |
|
vtasCrPrivacyCallSavedTodayAnnName |
Added but not supported |
|
vtasCrPrivacyCallSavedYesterdayAnnName |
Added but not supported |
|
vtasCrPrivacyCallSavedDayAndMonthAnnName |
Added but not supported |
|
vtasCrPromptTodayAnnName |
Added but not supported |
|
vtasCrPromptYesterdayAnnName |
Added but not supported |
|
vtasCrPromptDayAndMonthAnnName |
Added but not supported |
|
vtasCrPlayCollectFailureAnnName |
Added but not supported |
|
vtasCrUnavailableSavedAnnName |
Added but not supported |
|
vtasIcbRoamingCallerPreferenceWifi |
Added but not supported |
|
vtasMmtRoamingCheckMode |
Added but not supported |
|
vtasCrUseFromHeader |
Added but not supported |
|
VtasSscOcbBpGroups |
Added but not yet supported |
|
MtasSscOcbBpGroup |
Added but not yet supported |
|
mtasSscOcbBpGroupAnnAct |
Added but not yet supported |
|
mtasSscOcbBpGroupAnnDeact |
Added but not yet supported |
|
mtasSscOcbBpGroupAnnInt |
Added but not yet supported |
|
VtasSscOcbBpGroup |
Added but not yet supported |
|
vtasSscOcbBpGroupAnnAct |
Added but not yet supported |
|
vtasSscOcbBpGroupAnnDeact |
Added but not yet supported |
|
vtasSscOcbBpGroupAnnInt |
Added but not yet supported |
|
mtasCrCallUnavailableSavedDayAndMonthAnnName |
Added but not yet supported |
|
mtasCrCallUnavailableSavedTodayAnnName |
Added but not yet supported |
|
mtasCrCallUnavailableSavedYesterdayAnnName |
Now supported |
|
mtasSscOcbDetailedAnn |
Now supported |
|
vtasCrCallUnavailableSavedDayAndMonthAnnName |
Now supported |
|
vtasCrCallUnavailableSavedTodayAnnName |
Now supported |
|
vtasCrCallUnavailableSavedYesterdayAnnName |
Now supported |
|
vtasSscOcbDetailedAnn |
Added but not yet supported |
|
vtasSscOcbDetailedAnn |
Added but not yet supported |
|
mtasSipRetryAfterSupport |
Added and supported |
|
mtasSipRetryAfterTime |
Added and supported |
|
mtasConfVersion |
Added and supported |
|
vtasConfVersion |
Added and supported |
|
mtasSrvccReleaseReason |
Added and supported |
|
mtasSscRejectFailedServiceCodeCommand |
Added and supported |
|
vtasSscRejectFailedServiceCodeCommand |
Added and supported |
|
mtasSscMinLenOfNdNum |
Now supported |
4.2.3 Fault Management
This section describes changed, new, and removed alarms.
4.2.3.1 Changed Alarms
The changed alarms are listed in Table 10.
|
Alarm |
Description |
|---|---|
|
MtasSip, Failed to Open Port |
Two new causes are added for this alarm: |
|
MtasMmt, BL Voice Base License Absent |
Changed to "MtasMmt, Business Line AS Base License Absent" |
|
MtasLicenses, BL Voice Base License Capacity Exceeded |
Changed to "MtasLicenses, Business Line AS Base License Capacity Exceeded" |
|
Changed to "MtasLicenses, BL Service Exposure License Absent" | |
|
Changed to "MtasLicenses, BL Location Services License Absent" | |
|
Changed to "MtasLicenses, BL Legacy IN reuse License Absent" | |
|
Changed to "MtasLicenses, BL Multimedia License Absent" | |
|
MtasLicenses, UC Routing License Absent |
Changed to "MtasLicenses, BL UC/PBX ReRouting License Absent" |
|
Changed to "MtasLicenses, BL Ad-hoc Group Call License Capacity Exceeded" |
4.2.3.2 New Alarms
There are no new alarms for 1.10
4.2.3.3 Deleted Alarms
The deleted alarms are listed in the table.
|
Alarm |
Description |
|---|---|
|
MtasAoc, AOC License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasApLdmnp, Address Policing License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasMmt, AS Controlled Forking License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasCc, Communication Completion License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasCpc, Calling Party Category License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasCps, Carrier Select/Pre-select License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasCs, Carrier Select/Pre-select License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasCpsRn, Carrier Select/Pre-select License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasCsRn, Carrier Select/Pre-select License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasCharging, Offline Charging License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasCharging, Online Charging License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasCharging, Subscriber Credit Notification License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasDtm, DTM License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasEct, Explicit Communication Transfer License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasGm, GM License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasGCac, Communication Admission Control License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasIdPres, Calling Name Identity Presentation License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasLicenses, Conference Capacity License Exceeded |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasLicenses, MMTel Capacity License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasLicenses, MMTel Capacity License Exceeded |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasLicenses, Mobile Services Capacity License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasLicenses, Mobile Services Capacity License Exceeded |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasMmt, MMTel License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasMrfc, External MRFC License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasMrfc, Multiple Language Support License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasNa, Network Announcement License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasSnd, Short Number Dialing License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasPriorityCall, Priority Call License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasLicenses, MMTel Service Profile License Invalid |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasUCac, Communication Admission Control License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasXdms, Access of User service data via Ut-interface License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasNp, Number Portability License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasLicenses, MMTel Extended License Invalid |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasCat, Cat License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasLicenses, Flexible AVP License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasHotline, Hotline License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasIdPres, Originating Calling Name Identity Presentation License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasCr, Call Return License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasLicenses, Wholesale License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasCug, Closed User Group License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasIdPres, Multi Subscriber Number License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasDr, Distinctive Ring License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasJc, Japanese Charging License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasExtPowerSystem, Fault in External Power System |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasLicenses, Scc Capacity License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasLicenses, Scc Capacity License Exceeded |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasScc, SCC AS without interface to HSS(IMS) License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasSds, Service Domain Selection License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasTads, Terminating Access Domain Selection License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasLicenses, FCD Capacity License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasLicenses, FCD Capacity License Exceeded |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasStod, Session Transfer To Own Device License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasVideoFB, CSVideoFallback License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasLicenses, Parlay X Capacity License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasLicenses, Parlay X Capacity License Exceeded |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasFsfs, Flexible Service Format Selection License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. | |
|
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. | |
|
MtasDnm, Location Based Number Translation License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasCsi, IM-SSF License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasLicenses, IM-SSF Capacity License Exceeded |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasRs, Redirect Server License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasLicenses, NW AS Communication IWF Capacity License Exceeded |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
|
MtasLicenses, NW AS Communication IWF Capacity License Absent |
Due to Introduction of NELS based License Support and Concept of Base and Value Pack Licenses in vMTAS the individual Service based license absent Alarms are no longer used in vMTAS. |
4.2.4 Events and Notifications
There are no changed, deleted, or new events and notifications.
4.2.5 IFC Triggers
A new terminating trigger is introduced for business users. This is needed to route the VoLTE mobile terminated calls to the MMTel-AS for business line in the UC Mobility solution.
IF ( Method=INVITE AND SessionCase=”Terminating” AND NOT (header=” Ericsson-UCMobility-UC-Ext”) )
THEN
Add the following route header:
Route: sip:mmtel.domain.net;sc=term-trunk
|
Reason |
IFC |
|---|---|
|
New IFC will be configured to route request to Terminating SCC-AS if cscapable attribute is present with any value (true/false) in Accept-Contact Header of incoming INVITE. |
Trigger the SCC AS on the terminating port (mtasSipSccTermPort). Method="INVITE" AND SessionCase="Terminating" AND (header=”Accept-Contact” (Content=”*;cscapable=true” OR Content=”*;cscapable=false” ) ) |
|
For MMTel and SCC AS using AS generic SIP port the iFC trigger must contain AS name. It will be possible to use FQDN in iFC triggers enabling Dynamic AS allocation/AS instance caching in S-CSCF with load balancing using srv records in DNS lookup. Example for MMTel AS: sip:mtas.operator.net; as=MMTelAS; lr and for SCC AS: sip:mtas.operator.net; as=SCCAS; lr Requires that the AS generic SIP port is used in the DNS configuration for mtas.operator.net . | |
|
Road Test Announcement calls to subdomain port in MMTelAS |
Each fictive global number corresponding to a dialed test call number will be provisioned as a distinct PSI in the HSS |
4.2.6 Counters
This section lists changed and new counters.
For more information on counter description, refer to MTAS Performance Measurements.
There are no deleted, or obsolete counters.
4.2.6.1 Changed Counters
The changed counters are listed in Table 13.
|
Counter Name |
Description of Change |
|---|---|
|
MtasChargingTermAca |
Corrected KeyTypeNames ; SipResponse to ResultCode SipReason to Reason |
|
MtasChargingTermCca |
Corrected KeyTypeNames ; SipResponse to ResultCode SipReason to Reason |
|
MtasChargingOrigAca |
Corrected KeyTypeNames ; SipResponse to ResultCode SipReason to Reason |
|
MtasChargingOrigCca |
Corrected KeyTypeNames ; SipResponse to ResultCode SipReason to Reason |
|
MtasCdivNumberOfCdivNotOk |
Corrected KeyTypeNames ; SipResponse to ResultCode SipReason to Reason |
4.2.6.2 New Counters
The new counters are listed in Table 14.
|
Counter Name |
Description |
|---|---|
|
MtasTaInvNOkE |
Now supported |
|
MtasTaInvNOkI |
Now supported |
|
MtasTaInvOk |
Now supported |
|
MtasXdmsCai3gConflict |
Added but not supported |
|
MtasMmtSip<Orig|OrigUnreg|Term|TermUnreg>RequestIn |
Now supported |
|
MtasMmtSip<Orig|OrigUnreg|Term|TermUnreg>RequestOut |
Now supported |
|
MtasMmtSip<Orig|OrigUnreg|Term|TermUnreg>ResponseIn |
Now supported |
|
MtasMmtSip<Orig|OrigUnreg|Term|TermUnreg>ResponseOut |
Now supported |
|
MtasSccSip<Orig|OrigUnreg|Term|TermUnreg>RequestIn |
Now supported |
|
MtasSccSip<Orig|OrigUnreg|Term|TermUnreg>RequestOut |
Now supported |
|
MtasSccSip<Orig|OrigUnreg|Term|TermUnreg>ResponseIn |
Now supported |
|
MtasSccSip<Orig|OrigUnreg|Term|TermUnreg>ResponseOut |
Now supported |
|
mtasFuncSipRequestOverloadRej |
Now supported |
4.3 Other Interface Impacts
4.3.1 User Services
All MTAS nodes in the network must be upgraded before taking new services in operation.
The changes to existing user services are described in Table 15.
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 |
Service Name |
Impact |
Description of Change Compared to vMTAS 1.9 |
|---|---|---|---|
|
More robust handling of re-INVITE requests |
No Impact |
Change in the SIP signaling of the indicated services: -Delayed sending of re-INVITE request when the service triggers session renegotiation to the called party (Related CM: mtasMmtReInviteDelayTime) -Re-INVITE retry for the final response 500 with Retry-After header received from the called party (Related CMs: mtasMmtReInviteRetryAfterSupport, mtasMmtReInviteRetryAfterTimeMax) | |
|
Generic test call announcement service |
Test Announcement |
No Impact |
New terminating endpoint service |
|
Update UE Terminal Type and Access Domain determination |
SubscriberDataService |
No Impact |
Change in UE Terminal Type and Access Domain determination. UE access node is "MME" if PANI indicates "3GPP-E-UTRAN, else if PANI indicates "3GPP-GERAN" or "3GPP-UTRAN" access node is "SGSN". If PANI not present UE access node remains Unknown. |
|
CC Recall without answer captured in charging |
Communication Completion |
No Impact |
Introduction of optional configuration based behaviour for originating MMTel AS to generate ACR(Event)/ CCR(Event) with Supplementary-Service-Information AVP indicating the usage of the CC service type (CCBS or CCNR or CCNL) when CC Recall to user A is unsuccessful. New CM Attribute mtasCcChargEventOnCcRecallFailure is introduced to configure this behavior. |
|
Multi Mobile Device in Single IRS support in MTAS iteration-3 |
ChargingDataCollectorService |
No Impact |
Introduction of optional configuration based behaviour for SSC and MMTel AS to report ACR(Event)/ CCR(Event) with Subscription-ID with or without MSISDN, IMSI. New CM Attribute and mtasChargingProfileSuppressRfMsisdnImsiSubscriptionIdAVP and mtasChargingProfileSuppressRoMsisdnImsiSubscriptionIdAVP are introduced to configure this behavior. |
|
Multi Mobile Device in Single IRS support in MTAS iteration-3 |
IncomingCallBarring |
No Impact |
Multi Mobile Subscriber incoming Barring Due to Roaming. ICB service executed in MTAS. B’s incoming communication barring rules is evaluated if subscriber is a multi-mobile subscriber then ICB request location of default subscription from HSS. ICB reject the communication if default subscription is roaming. |
|
Multi Mobile Device in Single IRS support in MTAS iteration-3 |
UserLocationService |
No Impact |
Multi Mobile Subscriber’s NPLI retrieval from HSS. MMTel retrieves network provided location information from HSS for all the provisioned Multi Mobile Subscriber. |
|
MTAS NPLI query at session release |
UserLocationService |
No Impact |
When NPLI retrieval on session release is configured, there is an extra query to HSS for location information on BYE / 200 OK for BYE. By default, the retrieval on session release is disabled. |
|
Alignment of MTAS Call Return with PSTN |
H.248 |
No Impact |
If CM attribute mtasCrLastInfoCallType is set to new value= “2”, and CR invocation is done at least 2 days after last incoming call was saved, voice variables “int(ordinal)” and “month” voice variables types are requested via h.248 to be played in prompt or privacy announcement. |
|
Call Return based on FROM header |
H.248 |
No Impact |
If CM attribute mtasCrLastInfoCallType is set to new value = “2”, and CR invocation is done at least 2 days after last incoming call was saved, voice variables “int(ordinal)” and “month” voice variables types are requested via h.248 to be played in “No classification” announcement. |
|
Reporting Ro interface failure over Rf |
Charging |
Minor impact |
The feature reports Ro interface failure over Rf when offline charging configured for the SIP session and Rf connection established. |
|
Multi-Sim Phase-2 Single IRS support in MTAS |
No Impact |
When new mobile behaviour is enabled and mobile-subscription list is provisioned, - FCD will assume below 5 CM setting from Reference configuration and distribute calls in parallel to provisioned mobile subscriptions. - mtasFcdDistributeToPrimaryUserDevices: 1 (Unlocked) - mtasFcdDistributeToPrimaryUserDevicesBehavior: 1 (EXPLICIT_PRIMARY_USER_DEVICE_DISTRIBUTION) - mtasFcdToPrimaryUserSubscription: 1 (SUBSCRIPTION_NEEDED) - mtasCbVersion: 2(VERSION 2) - mtasFcdVersion:2 (BUSYEVERYWHERE_ENDUSER) | |
|
Call Pull |
No Impact |
When new mobile behaviour is enabled, mobile-subscription list is provisioned and mtasStodCallPullPolicyRoaming is set to SAME-COUNTRY(1), Call Pull Service will reject the request, if pulling device and device with existing session is not in same country. Fixed devices will always pull call when mtasStodCallPullPolicyRoaming is set to SAME_COUNTRY_FIXED_EXCEPTION(2). Call Push is restricted for Multi Mobile Subscribers | |
|
Call Admission Control |
No Impact |
For MultiMobile Subscriber, Number of mobile session control and simultaneous mobile device usage control is added. | |
|
Comminucation Waiting |
No Impact |
For MultiMobile Subscriber, CW will be device aware | |
|
No Impact |
For multiple mobile subscriptions, support for SRVCC is added. | ||
|
Communication Barring |
Major Impact |
Supplementary-Service-Information AVP is reported in CCR-U instead of CCR-T by ICB for media barring decision when SDP offer from B is sent in final response. | |
|
Release reason header addition when terminating PS session |
No Impact |
After a successful SRVCC access transfer, when SRVCC terminates the PS session and sends BYE/CANCEL/404 (depending on call state and serving MTAS role) the outgoing message is sent with a new reason header if mtasSrvccReleaseReason is set to 1: Reason: SIP;cause=487;text="Terminating PS access after successful transfer" | |
|
National dialing plan format in announcements for CR and CD services in MMTel AS |
Call Return |
No Impact |
New option to Call Return service added to trigger last calling number denormalization for segmented announcement |
|
National dialing plan format in announcements for CR and CD services in MMTel AS |
SSC, Communication Diversion |
No impact |
New option added to trigger CDiv target number denormalization for segmented announcement |
|
Call Return service based on FROM header |
Call Return |
No impact |
New option to trigger Call Return service based on FROM header. |
|
Call Return service based on FROM header |
SSC, Communication Diversion |
No impact |
New option added to trigger CR segmented announcement for call type “No classification” |
|
MTAS Improvements to S8HR roaming |
No impact |
The O-SDS service of SCC AS can add PVNI header to INVITE for ICS mobile originating calls using location information received in CAP IDP, if PVNI header is not present in incoming INVITE. | |
|
MTAS Improvements to S8HR roaming |
No impact |
ICB service of MMTel AS adds a predefined caller preference in case served user has an active Roaming condition and is currently on WiFi access. | |
|
MTAS Improvements to S8HR roaming |
TADS |
Minor impact |
T-ADS service of SCC AS can terminate the call on WiFi access only if a specific caller preference feature tag is present in incoming INVITE. |
|
MTAS Improvements to S8HR roaming |
No impact |
OCB service of MMTel AS can use the PLMN ID from PVNI header in incoming INVITE as additional input to roaming state check. | |
|
MTAS Improvements to S8HR roaming |
No impact |
ICB service of MMTel AS can use the PLMN ID from stored PVNI as additional input to roaming state check. | |
|
MTAS Improvements to S8HR roaming |
Charging |
No impact |
Online charging service of MMTel AS can use the PLMN ID from PVNI as additional input to disable Ro signalling towards charging system if the terminating call ends with UE located in HPLMN |
|
MTAS Improvements to S8HR roaming |
Northbound Call Control |
No impact |
Northbound Call Control service of MMTel AS can use the PLMN ID from PVNI as additional input to disable CAP T-CSI invocation towards SCF system if the terminating user is located in HPLMN. |
|
Minor impact |
Enhancement to the SSC service which allows playing the detailed announcements on OCB BP activation, deactivation and interrogation alternatively to the existing announcements in the design base. |
4.3.2 Other Interface Impacts
All vMTAS nodes in the network must be upgraded before taking new services in operation. The changes to other user services are described in Table 16.
|
Source of Change |
Service |
Interface |
Impact |
Description of Changes |
|---|---|---|---|---|
|
TR HW33693 |
ISC, Ma |
Major impact |
If Rel12 charging correlation is enabled (mtasSrvccR12Charging = 1), SCC AS will Store P-Charging-Vector's “icid” and “icid-generated-at” parameters on the source access leg and use them in PCV's “related-icid” and “related-icid-generated-at” that's sent in responses to AT-INVITE. | |
|
HW29736 |
NorthboundCallControlService |
ISC, Ma |
Major impact |
After the call has been established, when NCC receives a ReleaseCall from SCP and generates the TERMINATE_SESSION event, it should only set the 'iQ850RejectReason' parameter as empty string, set 'iRejectReason' as zero, set 'warningString' as empty string. In this way SIPSFW will only put Q850 reason in the Reason header when translate TERMINATE_SESSION event to SIP BYE message |
|
HW39603 |
SSC Service |
ISC, Ma |
No impact |
SDP with port set to “0” will be included in 200 OK from MTAS for INVITE when external MRF does not respond on request for playing announcement and when Gateway Model is unlocked |
|
HW23213 |
Priority Service |
ISC, Ma |
Major impact |
MTAS changes the RPH header handling if the Resource Priority service is enabled. The new behavior is for the both SIP responses and requests originating from MTAS will include an RPH header if it was included in the initial INVITE. Otherwise, RPH header contains if and as it was included in the latest received request on this dialog |
|
HV97228 |
Number Normalization |
ISC, Ma |
Major impact |
The behaviour is corrected to use Default Context in case no context is found for profile in Number Normalization. Although it is not recommended, but still if faulty legacy behavior is needed, it can be achieved using the ENV variable. |
|
SIP P-Early-Media Header Support and early delivery of the SDP answer |
Gateway Model Service |
ISC, Ma |
No Impact |
New option added to keep P-Early-Media header support capability of served user |
|
SIP P-Early-Media Header Support and early delivery of the SDP answer |
PEM Interworking service |
ISC, Ma |
No Impact |
New P-Early-Media Interworking service added |
|
HW44703 |
Mp |
No Impact |
Prior to this version CAP to Megaco mapping of Interruptable announcement was incorrect. Now the Boolean is negated (as it should have been done before) | |
|
HW31458 |
Gateway Model Service |
ISC, Ma |
Minor Impact |
If the MMTel AS is operating in non-transparent mode and initial INVITE is received with Request-Disposition: no-fork, Gateway Model service accept early UPDATE. |
|
HW53307 |
CDIVService |
ISC, Ma |
Mino impactr |
Initial INVITE can contain multiple feature tags in Contact header. Perviously during the preparation of the forwarding INVITE CDIVService checked the Contact header feature tag extensions found in the initial INVITE and removed all except for 3 predefined ones (video, audio and isFocus tags). CDIVService doesn’t remove any feature tags. Example: Contact header in initial INVITE: Contact: <sip:+16692481015@[fc00:0:12:1284:d45e:bc27:2d43:4d4b]:5060>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";video;+sip.instance="<urn:gsma:imei:99000704-145023-0>" Contact header in forwarding INVITE : Contact: <sip:p65548t1513024309m979584c101381s1@[2607:f160:0:1152::2000:3]:5060;transport=udp>;video Contac header in forwarding INVITE : Contact: <sip:p65548t1513024309m979584c101381s1@[2607:f160:0:1152::2000:3]:5060;transport=udp>;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel";video;+sip.instance="<urn:gsma:imei:99000704-145023-0>" |
|
HW50536 |
Adhoc Conference |
- |
Minor impact |
When vtas/mtasConfVersion is zero, partial notification to CC is not delayed. This setup could cause race condition between explicit and implicit notifications towards conference creator. If CM parameter is set to 1 (default) partial notify will be delayed with 1 sec. |
|
HW56944 |
SSC Service |
- |
No impact |
A failed supplementary service code command, when early media is not allowed (mtasSSCodesPlayEarlyMedia == false), will be responded. If mtasSscRejectFailedServiceCodeCommand is false (default value), the INVITE will be responded with 200 OK and a negative announcement will be played. If attribute is true, the INVITE will be responded with 3xx/4xx (REJECT) and no announcement will be played. |
|
HW62511 |
OIR and FIP |
- |
Minor impact |
Because of an earlier fault, when OIR and FIP services were both invoked for the very same call, the Privacy=history parameter in History-Info headers were duplicated. Now that error is fixed, so in these cases only one will be sent. |
|
HW64049 |
- |
No impact |
Previously it might happen, that with special configuration DNM and SSC codes might overlap, and maybe not the wanted behavior was taken place. Since in our service chain SSC Service is before DNM Service, in overlapping cases always SSC was triggered. Now there is a new possibility to configure a minimum length for the ND part of the SSC calls, which is triggering SSC. If the minimum length is not reached DNM Service will have also a chance to be triggered. See mtasSscMinLenOfNdNum. | |
|
HW12803 |
CDiv and CPC services |
- |
Minor impact |
Because of an earlier fault, Supplementary-Service-Identity was not included in ACR start for CPC service, if CDiv service was also triggered. Now it is added. |
|
HW63921 |
- |
Minor impact |
When configured to update the number and the display-name, privacy header in the incoming SIP INVITE and Address Presentation Restricted indicator in CAPv2 CON message is checked. Only in case of both privacy settings are “allowed”, updating PAI and FROM headers are performed. The updates are done regardless a new destination number is received in CON or not. | |
|
HW66668 |
TelSessionService |
- |
No Impact |
Because of an earlier fault MtasMmtInit*SessNOkService counter was stepped every time the call has been rejected due to internal reasons. Now with this fault fixed, changed counter measurements might be seen. |
|
HW38622 |
Charging |
UC Mobility |
- |
2 New AVPs have been introduced for the UC mobility feature in the Charging Subsystem: UC-Mobility-Call-Leg and Subscriber-Type. Both of them are added to the default omit lists. |
5 Impact on MTAS Features
This section describes the impact on the vMTAS 1.10 features when the feature is turned on.
5.1 Auto Healing Work Flow Feature
This functionality will auto heal single PL failure or multiple PLs failure but it does not support unhealable PLs (PL-3, PL4) and System Controllers (SCs).
A VNF can be healed from a computer resource or neutron port failure using the VNF-LCM in two ways:
- Manually from the VNF-LCM User Interface (UI)
- Automatically triggered on the reception of the "CLM Cluster Node Unavailable" alarm from the VNF instance
Impact
No impact on capacity, performance, network elements, and operation.
5.2 Alternative Presentation Number for UK Market
MMTel AS use provisioned network verified user identity fip-alternative-user-identity in the From header at outgoing calls of the subscriber.
Impact
No impact on capacity, performance, network elements, and operation.
5.3 Support for FQDN as PAI in SIP SUBSCRIBE to CSCF
With Support for FQDN as PAI in SIP SUBSCRIBE to CSCF it will be possible to use FQDN identity in subscription for Reg Event packages in case of INVITE based registrations with caching contact data enabled.
Impact
No impact on capacity, performance, network elements, and operation.
5.4 SIP P-Early-Media Header Support and Early Delivery of the SDP Answer
The P-Early-Media (PEM) Interworking Service allows an operator to solve interoperability problems when calling VoLTE devices do not support the SIP P-Early-Media header and associated functions.
Impact
No impact on capacity, performance, network elements, and operation.
5.5 Support Change of Payload Type Number in a Session
With support of this feature, terminating MTAS reads rtp mapping for each codec listed in early UPDATE from B (offer) and consider any dynamic codec mapping in UPDATE answer to B in accordance with RFC 3264.
Impact
No impact on capacity, performance, network elements, and operation.
5.6 AS Interworking Filtering of SIP 181
With support of this feature, the originating MTAS is able to filter the 181 Call is being forwarded responses from the terminating network.
Impact
No impact on capacity, performance, network elements, and operation.
5.7 PC: Extension to Feature Assume Positive on Ro
The extension to the already implemented feature “Assume Positive on Ro” Verizon Online Charging Control feature is realized by linking of an MMTel Charging Profile to a user. Charging Prepaid parameter is used to provide separate Charging Profiles for prepaid and non-prepaid subscribers using Ro.
Impact
No impact on capacity, performance, network elements, and operation.
5.8 PC: Generic Test Call Announcement Service
Test Announcement service allows an end user to receive a long duration announcement on an established session.
Impact
No impact on capacity, performance, network elements, and operation.
5.9 Robust Handling of re-INVITE Requests
Handling of 500 with Retry-After response to reINVITE
The initiator service of the re-Invite is Retrying re-INVITE upon reception of 500 (Server Internal Error) response with Retry-After header (0 - 10 seconds), honoring the Retry-After value (can be 0 as well).
Delaying reINVITE
When a service has to send re-INVITE immediately after sending the ACK of initial invite, the service needs to support configurable timer to control interval between ACK and re-INVITE. The recommended range of timer value is 0-100ms.
This feature enhancement can be controlled by the following CM attributes: mtasMmtReInviteDelayTime, mtasMmtReInviteRetryAfterSupport, mtasMmtReInviteRetryAfterTimeMax
Impact
No impact on capacity, performance, network elements, and operation.
5.10 CC Recall Without Answer Captured in Charging
MMTel AS generates ACR(event)/CCR(Event) with Supplementary-Service-Information AVP indicating the usage of the CC service type (CCBS or CCNR or CCNL) when CC Recall to user A is unsuccessful.
The feature can be controlled with the new CM mtasCcChargEventOnCcRecallFailure.
Impact
No impact until activated.
5.11 Subscription-ID AVP without MSISDN and IMSI in Charging
SSC and MMTel AS to report ACR(Event)/ CCR(Event) with Subscription-ID with or without MSISDN, IMSI. The new CM attributes mtasChargingProfileSuppressRfMsisdnImsiSubscriptionIdAVP and mtasChargingProfileSuppressRoMsisdnImsiSubscriptionIdAVP are introduced to configure this behavior.
Impact
No impact on capacity, performance, network elements, and operation.
5.12 MTAS NPLI Query at Session Release
The feature is mainly to find the up-to-date location information of the served user during session release. When the feature is enabled, during session release MTAS is able to trigger NPLI retrieval on served user message (BYE/200 OK for BYE) if the message does not contain a valid P-Access-Network-Info header or the header does not contain a valid location.
The feature can be enabled or disabled respectively for originating MMTel AS, terminating MMTel AS, originating SCC AS and terminating SCC AS with the following 4 CMs:
- mtasMmtNpliOriginatingOnSessionRelease
- mtasMmtNpliTerminatingOnSessionRelease
- mtasSccNpliOriginatingOnSessionRelease
- mtasSccNpliTerminatingOnSessionRelease
Impact
When the feature is enabled, there could be an extra location information query to HSS during session release, dependent on whether or not the messages (BYE/200 OK for BYE) from served users contain valid location information in P-Access-Network-Info header.
5.13 National Dialing Plan
For Call Return service it shall be possible to announce the last calling number in national dialling plan format. For Supplementary Service Codes service it shall be possible to announce the Communication Diversion target number according to the national dialling plan format. This feature can be controlled with the following CM attributes: mtasCrCallingPartyDenorm , mtasSscCdivTargetNumberDenorm, vtasCrCallingPartyDenorm, vtasSscCdivTargetNumberDenorm.
Impact
No impact on capacity, performance, network elements, and operation.
5.14 Increase Size of CDiv Blacklist
The size of CDIV Blacklists in MMTel and BL AS shall be increased from 255 to 2048.
Impact
Using more than 255 entries for the Blacklist might cause a small capacity degradation. An improvement is planned for the next releases to address this issue.
5.15 Support for 2nd External MRFC FQDN
The MMTel AS is supporting a second External MRFC Node which is used if a first External MRFC Node fails. SRV query is allowed for both first and second External MRFC Node. If all the MRFCs returned for the first External MRFC Node fails, then the MMTel AS is querying the second External MRFC Node and use the MRFCs returned by DNS for this query.
The second External MRFC Node is chosen in the same way as the first External MRFCNode from the defined External MRFC pool.
Impact
No impact on capacity, performance, network elements, and operation.
5.16 Reporting Ro failure over Rf
The feature implements a mechanism which handles fault scenarios in online charging by leveraging on the offline charging when the call continues, to avoid revenue loss. The Ro failure information is reported over Rf using properitary Ro-Information AVP.
Impact
No impact on capacity, performance, network elements, and operation.
5.17 NW Level Licensing, capacity
New capacity license supervision implemented for vMTAS. Integration unlock period default value 30 days will be set.
Two new vMTAS capacity licenses: vMtasSTBaseCapacity and vMtasNWCommIwfBaseCapacity
New Alarms are implemented for Missing/invalid/expired license.
Impact
No impact on capacity, performance, network elements, and operation.
5.18 Selective validation of XDMS documents
It is now possible to configure whether, upon reception of a received request via CAI3G, MMTel AS shall exclude from document validation any item in the initial user document/service profile related to IR.92 feature set.
The following configuration options are possible:
(0) = Check complete document
(1) = Check only the received request via CAI3G
The following PM Counter is connected to this feature enhancement: MtasXdmsCai3gConflict.
Impact
No impact on capacity, performance, network elements, and operation.
5.19 etc Hardened Overlay
Hardened Etc overlay is used for hardening configuration files. Where the configurations must be applied in a non-dynamic fashion in order to prevent damaged configuration files.
With HEO RPM in place, vMTAS will introduce below functionality:
- Default Umask 027
- Legal Warning at Login
- Inactivity Timer for Login
- Inactivity timer for User Accounts
- Strong Password
- Auditing
Impact
vMTAS will be more secure and hardened from security prospective.
5.20 SCTP Support for DIAMETER
The purpose of this feature to introduce Profile 2 of vMTAS reference connectivity. vMTAS reference connectivity has defined evolution steps toward achieving traffic separation profile goals.
The following are introduced as part of this feature:
- Introduction of Multi-Homing for SIGTRAN-
- Introduction of SCTP for DIAMETER and multi-homing SCTP support.
Impact
Minor impact on capacity, performance due to memory and CPU use by SCTP on multiple interfaces.
5.21 MTAS selection between MMTel AS and SCC AS
MMTel AS and SCC AS is starting to use the AS generic SIP port instead of using dedicated SIP ports for each session case and registration state. The use of the AS generic SIP port requires that the Application server trigger in HSS includes the AS name in the trigger. The AS name is added in the Route header in the ‘as=’ parameter.
Example: Route:<sip:mtas.operator.net; as=mmt; lr>
To be able to determine the session case and reg state, the P-Served-User header must be included in the SIP request. The AS generic SIP port is also handling the PSI functionality over the MA interface. MMTel and SCC AS is adding the P-Ericsson.Invocation-History header to outgoing SIP requests and responses.
Impact
No impact on capacity, performance, network elements, and operation.
5.22 Reporting PLMN ID in S8HR
Access to the PANI header and report timezone information to charging, if available. Improvement in MMTel-AS and SCC-AS to use PLMN for charging and roaming status of UE for S8 Home Routing (S8HR) architecture. This new feature can be controlled with the following CM attributes: mtasChargingTimeZoneSource, mtasIcbRoamingCallerPreferenceWifi, mtasMmtRoamingCheckMode, mtasSdsCreatePvni, vtasIcbRoamingCallerPreferenceWifi, vtasMmtRoamingCheckMode.
Impact
No impact on capacity, performance, network elements, and operation.
5.23 Re-INVITE/ACK Race Condition Handling When Acting as UAS
When mtasSipRetryAfterSupport is set to retryAfterSupportUasEnabled and originating MMTel AS receives a re-INVITE request while still waiting for the ACK for the initial INVITE transaction, MMTel AS rejects the re-INVITE request using 500 final response with Retry-After, whose value is configurable via mtasSipRetryAfterTime.
Impact
Minor impact on capacity, performance, network elements, and operation.
5.24 Multi-Sim Phase-2 Single IRS support in MTAS
To support multiple sim devices for one subscriber under single IRS. Following functionality is introduced:
- Multiple mobiles can be used for originating call.
- MTAS will terminate call on multiple mobile devices.
- Online and offline Charging support for multiple mobile devices, reporting subscription ID information for each devices.
- Call admission control for multisim subscriber.
- Device aware call barring.
- Device aware call PULL
Impact
No impact on capacity, performance, network elements, and operation.
5.25 Alignment of MTAS Call Return with PSTN
Call Return service based on From header feature offers the new functions:
- Possibility to use announcement with “Today”, “Yesterday” and Day and Month at CR invocation for “No classification” announcement.
- Possibility for CR invocation based on ‘From’ header.
Impact
No impact on capacity, performance, network elements, and operation.
5.26 Latest Location Info in Charging
When CM attribute mtasChargingProfileReportAtDisconnection is set to 1 and session is terminated by the remote user, ACR Stop/CCR Terminated is triggered on BYE response and report PANI from the BYE response in ANI AVP when applicable. . This feature enhancement is controlled by the following configuration parameters: mtasChargingProfileReportAtDisconnection.
5.27 SSC Announcement Handling for OCB Operations
Enhancement to the SSC service which allows playing the detailed announcements on OCB BP activation, deactivation and interrogation alternatively to the existing announcements in the design base.
This feature enhancement can be controlled with the following CM attributes: mtasSscOcbBpGroup, mtasSscOcbBpGroupAnnAct, mtasSscOcbBpGroupAnnDeact, mtasSscOcbBpGroupAnnInt, mtasSscOcbDetailedAnn.
Impact
No impact on capacity, performance, network elements, and operation.
5.28 Improved Early Dialog Handling in CDIV
CDIV service is extended to act as a B2BUA to be able to intercept UPDATE messages from caller and send UPDATE_ACCEPT messages to caller on more than one early dialogs on behalf of the callee. CDIV service sends UPDATE_ACCEPT in case UPDATE arrives from caller to callee after INVITE_REJECT is received from callee or in case UPDATE from caller is sent out to callee but callee sends INVITE_REJECT before it receives the UPDATE (race condition).
CDIV service is extended with early dialog termination functionality. All early dialogs that are not terminated by other services (with the exception of the early dialog of initial INVITE) are terminated by CDIV service with SIP 199 message before forwarding the call. CDIV service terminates the early dialogs if 199 is supported in the initial INVITE message, and the configuration parameter mtasMmt199Generation is unlocked.
Impact
No impact on capacity, performance, network elements, and operation.