class CSCF-Application

Attributes
`string key mandatory noNotification restricted`	`applicationName` The name of the application. The attribute name and value of is used in the applications RDN.
`DomainNameDT[0..] nonUnique ordered`	`bcfDomainNameEntry` This attribute is the domain name of the BCF. This is the fully qualified domain name of the BCF node, if one exists. It is possible to configure multiple domain names of the BCF. The purpose with this is to have the possibility to address the same BCF node with different names, used at, for example, load sharing or network redundancy. It shall be noted that outgoing messages from the BCF will always include the first configured domain name.
`boolean`	`bcfEnabled = false` Determines if the BCF application is available or not.
`OperState readOnly`	`bcfOperationalState = DISABLED` The attribute indicates the current operational state of the BCF. This operational state is based on the current configuration of the BCF and its ability to handle traffic. The following is required for BcfOperationalState to become ENABLED: - BcfEnabled = true. - One UDP instance of the BcfNetworkInterfaceEntry including all prerequisite information for that interface must be configured. - If a TCP instance of the BcfNetworkInterfaceEntry has been configured it must be configured with same IP-address and port as the UDP interface.
`String0to01024DT[0..] nonUnique ordered`	`cscfActiveUserMethod = ""` A multi-value configuration parameter that specifies which SIP method, for example, INVITE, MESSAGE, will result in incrementing the cscfActiveUsers counter. If the configuration parameter is not defined, that is, empty, then the function Active Users is not active, that is, default. This is valid for when the SIP methods are either sent or received by users.
`AdmState`	`cscfAdministrativeState = LOCKED` A short description of the behavior of CSCF at different states of CscfAdministrativeState is given here. Refer to "CSCF Configuration Management User Guide" for detailed description considering the different CSCF types and collocation aspects. When the node is in state: 0 (Locked), the CSCF is to be taken out of service as soon as possible. Established sessions except emergency sessions are released, users are deregistered and new SIP requests are rejected. When the node is in state: 1 (Unlocked), the CSCF node handles requests and performs functions normally. When the node is in state: 2 (Shutting down), the CSCF is gracefully taken out of service with minimal traffic disturbance. As long as users are registered, non-register traffic is processed as when in "Unlocked" state. Users are de-registered/re-distributed when handling registration traffic. When all users are de-registered/re-distributed and all sessions are terminated the CSCF will automatically transit from "Shutting down" to "Locked" state.
`AkaAlgorithmDT[6..6] nonUnique ordered`	`cscfAkaAlgorithmEntry = 1:hmac-md5-96,aes-cbc:enabled,2:hmac-sha-1-96,aes-cbc:enabled,3:hmac-md5-96,des-ede3-cbc:enabled,4:hmac-sha-1-96,des-ede3-cbc:enabled,5:hmac-md5-96,null:enabled,6:hmac-sha-1-96,null:enabled` This parameter let the user enable and disable specific AKA algorithm encryption-algorithm pairs and change the priority order for them. CSCF will always use the pair with the lowest priority number that match the UE supported list of algorithms.
`CicRoutingDT`	`cscfCicRoutingEnabled = DISABLED` This parameter controls how the S-CSCF shall invoke the External Network selection when the CIC (Carrier Identification Code) parameter is available.
`boolean`	`cscfCxAlwaysUseRealmBasedRouting = false` Determines whether CSCF should always use realm based diameter routing on the Cx/Dx interface.
`CxDestinationHostDT[0..1]`	`cscfCXDestinationHost = ""` This parameter identifies the Home Subscriber Server (HSS) that the Cx and/or Sh Diameter message is sent to. This value is used in the Destination-Host AVP. If the Subscriber Location Function (SLF) or an HSS redundant cluster is used, this parameter value must be set to "NotConfigured". In the SLF case only the SLF is defined as default route in the Diameter stack. In the HSS redundant cluster case all HSS in the cluster are defined as default routes in the Diameter stack.
`String0to00100DT[0..1]`	`cscfCXDestinationRealm = ""` This parameter identifies the realm the Cx and/or Sh Diameter message is to be routed to. The absence of the CscfCxDestinationHost will cause a message that is sent to any diameter server supporting the application within the realm specified in Destination-Realm AVP.
`String0to00100DT[0..1]`	`cscfCXOriginHost = ""` This parameter identifies the CSCF that originated the Cx and/or Sh Diameter message. This value is used in the Origin-Host AVP.
`String0to00100DT[0..1]`	`cscfCXOriginRealm = ""` This parameter identifies the realm of the CSCF of the Cx and/or Sh Diameter message. This value is used in the Origin-Realm AVP.
`DbSweeperTimeDT`	`cscfDatabaseSweeperTime = 03:00` This attribute defines the time when the CSCF database sweeper executes to purge stale data from the database.
`Fqdn0to1024orEmptyDT[0..] nonUnique ordered`	`cscfDomainAlias` Every entry in the list must be an FQDN. An FQDN is a string that starts with a letter and contains only letters, numbers, "-" (hyphens) or "." (dots). CscfDomainAlias is used to specify the Domain Name(s) that are applicable to the home network. This information is used by the P-CSCF, the S-CSCF and the I-CSCF functions. Note: If CscfDomainAlias is empty, all domains are considered to be applicable to the home network. CscfDomainAlias is used for the following functionality: · P-CSCF uses CscfDomainAlias to determine if the I-CSCF is colocated for initial REGISTER requests. P-CSCF compares the content of the request-URI, which contains the home domain name, with the domains configured in CscfDomainAlias. If a match is found, then the P-CSCF invokes the colocated I-CSCF function. Having CscfDomainAlias empty will always invoke the colocated I-CSCF function. · Originating S-CSCF uses CscfDomainAlias to determine if SIP-URI that contains a telephone number will be treated as telephone number or if the SIP-URI will be routed normally using the domain part. · I-CSCF uses CscfDomainAlias to determine if a non-REGISTER request should be redirected, when a 300, 301, 302 or 380 response is received.
`String1to01024DT[0..] nonUnique ordered`	`cscfDomainBasedPSIRoutingEntry` A list of subdomains expressed as regular expressions. In case an INVITE request is received and the requested domain is found in the CscfDomainBasedPSIRoutingEntry, but not found in the HSS, the CSCF will send the INVITE request to the subdomain using the Domain Name Server (DNS). An example of a regular expression is /^mrf.*\.ericsson\.com$/i. This would be a case insensitive search that matches domains starting with mrf and ending with ericsson.com
`boolean`	`cscfEnableGlobalNumberNormalization = false` Determines if number normalization will be performed on global (international) telephone numbers. Dependencies: CscfGlobalNumberNormalizationPhoneContext needs to be configured before CscfEnableGlobalNumberNormalization can be set to true.
`boolean`	`cscfEnableRecordRouteSubscribe = true` This parameter controls if S-CSCF shall record-route SUBSCRIBE requests or not. If set to true, the S-CSCF will add a Record-Route header in the initial SUBSCRIBE request in order to receive all subsequent messages within the dialog. If set to false, the S-CSCF will not add Record-Route header (to minimize network traffic) in SUBSCRIBE dialog. However, when the Public GRUU feature is enabled and GRUU routing is used to route a SUBSCRIBE request, the S-CSCF still Record-Route even if this parameter is set to false. P-CSCF always Record-Route SUBSCRIBE dialogs.
`boolean`	`cscfEnumForLocalNumbersEnabled = true` This attribute configures the behavior in originating S-CSCF when a non global number is returned from the number normalization.
`Fqdn0to1024orEmptyDT`	`cscfEnumTopDomain = e164.arpa` When CSCF is performing an ENUM lookup, CscfEnumTopDomain is used as top domain when performing ENUM queries.
`OnEnumPstnDT`	`cscfExtNetSelOnEnumPstn = Tel` This attribute configures the behavior in S-CSCF when an ENUM response indicates E2U+pstn.
`boolean`	`cscfExtNetSelOnRnBeforeEnum = false` This attribute configures the behavior in S-CSCF when an RN parameter is present in the request URI which contains a telephone number.
`ForkingTimerDT`	`cscfForkingTimer = 12` This attribute defines the number of seconds the CSCF will wait for an answer message (2XX). It attempts by forking a request in parallel. If the attempt fails then the CSCF attempts contacts with a lower q-value.
`TimerMin0to5DT`	`cscfGaugeInterval = 2` Defines the interval for how often the CSCF will send the number of sessions and registrations to the PMF for the gauges: - cscfPeakConcurrentRegistration - cscfConcurrentRegistrations - cscfPeakConcurrentSessions - cscfConcurrentSessions - cscfPeakConcurrentRegisteredUserProfiles - cscfConcurrentRegisteredUserProfiles - scscfConcurrentUnregisteredUserProfiles - scscfPeakConcurrentUnregisteredUserProfiles - eatfPeakConcurrentSessions - eatfConcurrentSessions If set to 0 the value will never be sent and the gauges will not be used. Example: If set to 2 it will send the current registrations and sessions every two minutes. For more information about CSCF counters, see the following document: CSCF Performance Management Parameters
`String0to01024DT[0..1]`	`cscfGlobalNumberNormalizationPhoneContext = ""` Phone context to use when performing number normalization on a global telephone number. CscfGlobalNumberNormalizationPhoneContext needs to be configured before CscfEnableGlobalNumberNormalization can be set to true.
`CscfBehaviorDT`	`cscfISPBehavior = ISP` This attribute determines the behavior of the P-, I-, and S-CSCF application. It can only be set if CscfAdministrativeState =LOCKED.
`OperState readOnly`	`cscfISPOperationalState = DISABLED` This attribute indicates the current operational state of the I,S and P- CSCF. This operational state is based on the current configuration of the node and its ability to handle traffic. Operational state prerequisites: I-CSCF operational state requirements (CscfISPBehavior = I_CSCF): - One UDP instance of the IcscfNetworkInterfaceEntry must be configured including all prerequisites. - If a TCP instance of the IcscfNetworkInterfaceEntry has been configured it must be configured with same IP-address and port as the UDP interface. - The parameters CscfCXOriginRealm, CscfCXOriginHost CscfCXDestinationRealm, and CscfCXDestinationHost must be configured. P-CSCF operational state requirements (CscfISPBehavior = P_CSCF): - Two UDP instance of the PcscfNetworkInterfaceEntry must be configured including all prerequisites. (One instance for Gm and one for Mw). - If a TCP PcscfNetworkInterfaceEntry has been configured it must be configured with same IP-address and port as the corresponding UDP interface. S-CSCF operational state requirements (CscfISPBehavior = S_CSCF): - One UDP instance of the ScscfNetworkInterfaceEntry instances must be configured including all prerequisites. - If a TCP ScscfNetworkInterfaceEntry has been configured it must be configured with same IP-address and port as the UDP interface. - Parameter CscfChargingInterOpId must be configured. IS-CSCF operational state requirements (CscfISPBehavior = IS): - One UDP instance of the IcscfNetworkInterfaceEntry must be configured including all prerequisites. - One UDP instance of the ScscfNetworkInterfaceEntry must be configured including all prerequisites. - If a TCP instance of the IcscfNetworkInterfaceEntry or ScscfNetworkInterfaceEntry has been configured it must be configured with same IP-address and port as the corresponding UDP interface. - Parameters CscfCXOriginRealm, CscfCXOriginHost, CscfCXDestinationRealm, CscfCXDestinationHost, and CscfChargingInterOpId must be configured. ISP-CSCF operational state requirements (CscfISPBehavior = ISP): - One UDP instance of the IcscfNetworkInterfaceEntry must be configured including all prerequisites. - One UDP instance of the ScscfNetworkInterfaceEntry must be configured including all prerequisites. - Two UDP instances of the PcscfNetworkInterfaceEntry must be configured including all prerequisite. (One instance for Gm and one for Mw). - If a TCP instance of the IcscfNetworkInterfaceEntry, ScscfNetworkInterfaceEntry or PcscfNetworkInterfaceEntry has been configured it must be configured with same IP-address and port as the corresponding UDP interface. - Parameters CscfCXOriginRealm, CscfCXOriginHost, CscfCXDestinationRealm, CscfCXDestinationHost and CscfChargingInterOpId must be configured. Note: If CscfISPBehavior = NONE then CscfISPOperationalState will be disabled.
`MaxNonSupervisedSessionDurationDT`	`cscfMaxNonSupervisedSessionDuration = 1440` The maximum allowed duration for a session in the CSCF that has been established without client support for session timers.
`boolean`	`cscfNumberPortabilityRejectOnFailedENUM = false` This parameter configures CSCF behavior when ENUM error response SERVFAIL is received.
`boolean`	`cscfOnwardRoutingEnabled = false` This parameter is used by the Number Portability Function. This parameter controls the availability of the breakout gateway control function for terminating calls for ported number.
`boolean`	`cscfOverrideDefaultContext = false` If this parameter is enabled, the P-CSCF overrides phone-context, if provided.
`String0to01024DT[0..1]`	`cscfPhoneContext = ""` This parameter specifies the phone-context. The phone-context shall be added to a SIP URI with a local number. P-CSCF adds the phone-context dependent on the above mentioned parameters. S-CSCF adds the phone-context if it is missing and if it is not provisioned in the user profile.
`boolean`	`cscfProvideDefaultContext = false` If this parameter is enabled, the P-CSCF will add a phone-context parameter to all originating SIP requests that have a SIP URI in the Request-URI with a local number, if the context is not already present.
`boolean`	`cscfReducedTransactionLifespan = false` This attribute defines if Timer H and Timer J must take the standard value 64T1 or use the configured value for. Timer H is used to supervise reception of ACK in the INVITE transaction (non-2xx) and Timer J defines the maximum waiting time for request retransmits for a non-INVITE request. It defines as well if the waiting time for ACK retransmits in a successful session setup must take the standard value 64T1 or use the configured value for .
`RegEventEnabledDT`	`cscfRegEventEnabled = disabled` The CscfRegEventEnabled parameter is used for enabling or disabling the registration event functionality in the CSCF node. Furthermore, in the enabled configuration, the CscfRegEventEnabled parameter indicates a particular enabled-mode for the registration event functionality. Deprecated:
`boolean`	`cscfRegEventFullStateNotification = true` This parameter specifies whether the registration information in the NOTIFY request will contain full state information or partial state information. Deprecated:
`RegEventMaxNotificationRateDT`	`cscfRegEventMaximumNotificationRate = 5` This parameter specifies the minimum time spent between subsequent notifications sent for the same public user identity. Deprecated:
`boolean`	`cscfRegEventNotifyOnResubscribe = false` This parameter specifies if the S-CSCF will send notifications or not as answer to a refreshment of the subscription. Deprecated:
`RegEventRefreshTimerDT`	`cscfRegEventRefreshMax = 60` This parameter is used to set the maximum refresh time for Registration Event requests. Any RegEvent request received with a refresh time greater than what is specified in this parameter will be reduced to this value in the 200 OK. The time is defined in minutes and must be greater than CscfRegEventRefreshMin. Deprecated:
`RegEventRefreshTimerDT`	`cscfRegEventRefreshMin = 15` This parameter is used to set the minimum refresh time for Registration Event requests. Any RegEvent request with a refresh time below this value is rejected. The time is defined in minutes and must be less than CscfRegEventRefreshMax. Deprecated:
`boolean`	`cscfRemoveDialogueOnNegativeNotifyResponse = true` This attribute defines if CSCF should remove the SUBSCRIBE dialog after a negative response on a NOTIFY request (except 5xx response with Retry-After header) is received, or no response is received during subscription initiation, subscription refreshment or event state change. true - The SUBSCRIBE dialog will be removed. false - The SUBSCRIBE dialog will be kept.
`ReplaceRequestUriDT`	`cscfReplaceRequestUriWithDefaultIMPU = Inactive` Activating this parameter will trigger the terminating S-CSCF to replace the public identity in the Request-URI with the default public user identity before sending the request to an application server. The logic will be applied only if the addressed user is part of an implicit registration set. The default value of the parameter is Inactive, which means that the terminating S-CSCF will not replace the Request-URI. Setting this parameter to ReplaceTelOnly will triggers the terminating S-CSCF to only change the Request-URI in case the Request-URI is of schema type TEL. No other URI schemas will be changed. Setting this parameter to AlwaysUseDefault will trigger the terminating S-CSCF to unconditionally replace the Request-URI. Setting this parameter to UseDefaultAsServedUser will trigger the terminating S-CSCF to always replace the Request-URI with the default public user identity and to use the default public user identity as served user. Terminating S-CSCF will invoke the service profile of the default public user identity and include the default public user identity in the P-Server-User header and in the Original Dialog Identifier. Setting this parameter to ReplaceTelAsServedUser will trigger the terminating S-CSCF to replace the Request-URI with the default public user identity if the received Request-URI contains a TEL-URI. Terminating S-CSCF will invoke the service profile of the default public user identity and include the default public user identity in the P-Server-User header and in the Original Dialog Identifier if the Request-URI was replaced. Note: 1. When a TEL-URI with uri-parameters is received by the terminating S-CSCF in the Request-URI, if the CscfReplaceRequestUriWithDefaultIMPU is configured to replace the Request-URI with the default public user identity, and the default public identity is in SIP-URI, the value of Request-URI is replaced by the default public user identity (in SIP-URI) concatenated with the associated uri-parameters received in the original TEL-URI. 2. When the CscfReplaceRequestUriWithDefaultIMPU is configured to replace the Request-URI with the default public user identity, after the value of Request-URI has been replaced successfully, the value of P-Called-Party-ID is also replaced with the default public user identity. However, the following exceptions apply: * The value of Request-URI received is with Globally Routable User Agent URI * IcscfDynamicUserIdentitySupportEnabled attribute is set to true Takes effect: ChangeTypeRuntimeType - Session
`boolean`	`cscfRequireUserEqualPhone = true` If this parameter is true, any SIP URI must have the user=phone parameter to be considered as a telephone number.
`TimerSec0to30DT`	`cscfScscfFailoverTimer = 7` cscfScscfFailoverTimer gives the time in seconds for which the I-CSCF will wait for an answer from an S-CSCF (via Mw interface), an AS (via Ma interface) or an EATF (via I5 interface) before trying another node instance. This parameter is only applicable for responses to INVITE and REGISTER requests. If this parameter is disabled (set to 0), cscfSipDefaultFailoverTimer will be used instead. Takes effect: ChangeTypeRuntimeType - Session / Registration
`boolean`	`cscfSendRequestUdpOnly = false` If set to true, all requests are sent using UDP independent of message size or explicit TCP transport indications. If set to false, the requests will be sent according to the rules in RFC3261 and RFC3263.
`ServedUserIdSelectionDT`	`cscfServedUserIdentitySelection = PPreferredId` This parameter specifies the procedure to be used for selecting the identity of the served user in the P-CSCF node.
`SessionRefreshTimerDT`	`cscfSessionRefreshDefault = 30` This attribute is the default session refresh time for the CSCF in minutes. The CSCF will use this time in cases when no session expires value is provided in the request and a default value is needed. This value can be between 1 and 1440 minutes but must be less than or equal to CscfSessionRefreshMax and greater or equal to CscfSessionRefreshMin.
`SessionRefreshTimerDT`	`cscfSessionRefreshMax = 60` This attribute is the maximum session refresh time allowed by the CSCF in minutes. Any session refresh time specified greater than this value is reduced to equal this value. This value can be between 1 and 1440 minutes but must be equal or greater than CscfSessionRefreshMin.
`SessionRefreshTimerDT`	`cscfSessionRefreshMin = 15` This attribute is the minimum session refresh time allowed by the CSCF in minutes. Any request with a refresh time below this value is rejected. This value can be between 1 and 1440 minutes but must be equal or less than CscfSessionRefreshMax.
`boolean`	`cscfSigCompEnabled = false` This attribute is OBSOLETE. It’s no longer possible to enable Signaling Compression function. This Boolean attribute used to control whether the P-CSCF enabled SigComp when sending messages to and receiving messages from a SigComp compatible client. Obsolete: This attribute is obsolete because the Signaling Compression functionality is disabled in CSCF.
`SipPmKeyDT[0..18] nonUnique ordered`	`cscfSipPMKey = ""` List of IP addresses that are used for the keyed Session Initiation Protocol (SIP) stack counters.
`SmpAuthorizationDT`	`cscfSmpAuthorization = Inactive` Disable or enable the Subscribed Media Profile (SMP) Authorization function.
`TimerMSec0to2000000000DT`	`cscfTimerBValue = 32000` The CscfTimerBValue is used to configure the value of the SIP B timer that is used to control the transmission of SIP messages. Timer B is the INVITE transaction time-out timer. Only used to the access side. If this parameter is disabled (set to 0), CscfSipDefaultFailoverTimer will be used instead.
`TimerMSec180000to600000DT`	`cscfTimerCValue = 180000` The CscfTimerCValue is used to configure the value of the SIP C timer that is used to control the transmission of SIP messages. Timer C is the proxy INVITE transaction time-out.
`TimerMSec32000to300000DT`	`cscfTimerDValue = 32000` The CscfTimerDValue is used to configure the value of the SIP D timer that is used to control the transmission of SIP messages. Timer D is the wait time for response retransmits. Only used to the access side otherwise the value recommended by the RFC is used (64*T1).
`TimerMSec0to2000000000DT`	`cscfTimerFValue = 32000` The CscfTimerFValue is used to configure the value of the SIP F timer that is used to control the transmission of SIP messages. Timer F is the non-INVITE transaction time-out timer. Only used to the access side. If this parameter is disabled (set to 0), CscfSipDefaultFailoverTimer will be used instead.
`TimerMSec1to180000DT`	`cscfTimerT1Value = 500` The CscfTimerT1Value is used to configure the value of the SIP T1 timer that is used to control the transmission of SIP messages. T1 is the Round Trip Time (RTT) in ms.
`TimerMSec1to180000DT`	`cscfTimerT2Value = 4000` The CscfTimerT2Value is used to configure the value of the SIP T2 timer that is used to control the transmission of SIP messages. T2 is the maximum retransmit interval for non-INVITE requests and INVITE responses.
`TimerMSec1to180000DT`	`cscfTimerT4Value = 5000` The CscfTimerT4Value is used to configure the value of the SIP T4 timer that is used to control the transmission of SIP messages. T4 is the Maximum duration a message will remain in the network.
`boolean`	`cscfTrustedNetwork = false` This attribute specifies if both headers P-Charging Vector (PCV) and the P-Charging-Function-Address (PCFA) should be removed or included in the outgoing SIP Signaling. Note: The P-Charging Vector header may not contain the IOI parameters due to the fact that the IOI parameters are removed by S-CSCF before forwarding to P-CSCF. CSCF supports Type 2 IOI parameter as per 3GPP TS 24.299 Standards.
`boolean`	`cscfUnallocatedRoutingEnabled = false` Enables or disables the CSCF unallocated routing functionality. Dependencies: CscfUnallocatedPublicServiceIdentity must be configured before CscfUnallocatedRoutingEnabled can be set to true. Before CscfUnallocatedRoutingEnabled can be set to false, CscfUnallocatedPublicServiceIdentity must have a different value than "empty".
`UsageStateDT readOnly`	`cscfUsageState = ACTIVE` This attribute indicates the current usage state of the CSCF. This usage state is based on the number of registrations and sessions maintained by the CSCF. If there is one ongoing session or one registration, the value is active. Otherwise, it is idle.
`DomainNameDT[0..] nonUnique ordered`	`icscfDomainNameEntry` This attribute is the domain name of the I-CSCF. This is the fully qualified domain name of the I-CSCF node, if one exists. It is possible to configure multiple domain names of the I-CSCF. The purpose with this is to have the possibility to address the same I-CSCF node with different names, used at, for example, load sharing or network redundancy. It shall be noted that outgoing messages from the I-CSCF will always include the first configured domain name.
`TimerSec0to30DT`	`icscfNonInviteFailoverTimer = 0` icscfNonInviteFailoverTimer gives the time in seconds for which the I-CSCF will wait for an answer from a S-CSCF (via Mw interface), or an AS (via Ma interface) before trying another node instance. The parameter is only applicable for responses to non-INVITE requests, except REGISTER. If this parameter is disabled (set to 0), cscfSipDefaultNonInviteFailoverTimer will be used instead. Takes effect: ChangeTypeRuntimeType - Session
`boolean`	`icscfTransitEnabled = false` This attribute configures the behavior in terminating I-CSCF when the user is not found in HSS and no other service initiates an alternative routing.
`DomainNameDT[0..] nonUnique ordered`	`pcscfDomainNameEntry` This attribute is the domain name of the P-CSCF. This is the fully qualified domain name of the P-CSCF node, if one exists. It is possible to configure multiple domain names of the P-CSCF. The purpose with this is to have the possibility to address the same P-CSCF node with different names, used at, for example, load sharing or network redundancy. It shall be noted that outgoing messages from the P-CSCF will always include the first configured domain name.
`boolean`	`scscfContactUriMatchingEnabled = false` true: Contact URI matching for the request is enabled. false: Contact URI matching for the request is disabled. This parameter enables and disables the usage of Contact-URI matching for identifying information of a registered contact for Originating Non-Register requests. When enabled, the Contact-URI in the received request is used to match with Contact-URI stored at registration. If the Contact URIs do not match or the Contact-URI is missing from the received request, the request is rejected.
`DomainNameDT[0..] nonUnique ordered`	`scscfDomainNameEntry` This attribute is the domain name of the S-CSCF. This is the fully qualified domain name of the S-CSCF node, if one exists.