Differences in Derived Data Types of

Managed Object Model (MOM)

0

Configuration Management XML MOM

0

Contents

derivedDataType BlacklistingThresholdIntervalDestDT

derivedDataType BlacklistingThresholdIntervalDT

derivedDataType CscfLockedBehaviorDT

derivedDataType ExtNetSelInitialTransitTableNameDT

derivedDataType DateTime

description

Represents the international standard for the representation of date and time ( ISO 8601). 8601). The string format is "YYYY-MM-DDThh:mm:ss.SSSZ" (excluding quotes). quotes). A DateTime string consists of a date part, a time part, and an optional time zone information part. The time zone part may be a "Z", representing the Coordinated Universal Time (UTC) time zone (equals to +00) or a time zone offset (for example, +02:00). +02:00). If the time zone part is not present, the DateTime value represents local time. time. The following pattern describes the DateTime format: YYYY-MM-DDThh:mm:ss[.S+][Z|+-hh:mm] Where: format: YYYY-MM-DDThh:mm:ss[.S+][Z|+-hh:mm] Where: YYYY = Four digit year year MM = Two digit month (01=January, and so on) on) DD = Two digit day of month (01 through 31) 31) T = Time designator (shows start of time component) component) hh = Two digits of hour (00 through 23, AM/PM not allowed) allowed) mm = Two digits of minute (00 through 59) 59) ss = Two digits of second (00 through 59, leap second not allowed) allowed) S+ = One or more digits of decimal fraction of a second second Z = Time is UTC UTC +- = + or - character indicating positive or negative offset to UTC DateTime values are compliant with ISO 8601 "Representation of dates and times" but are restricted according to RFC 3339 "Date and Time on the Internet: Timestamps". The DateTime format is further restricted as follows: follows: - T and Z designators are upper case. case. - . (dot) is used to indicate start of fractions of seconds (ISO 8601 also allows comma) comma)

domainExtension

derivedDataType DateTime

description

Represents the international standard for the representation of date and time ( ISO 8601). 8601). The string format is "YYYY-MM-DDThh:mm:ss.SSSZ" (excluding quotes). quotes). A DateTime string consists of a date part, a time part, and an optional time zone information part. The time zone part may be a "Z", representing the Coordinated Universal Time (UTC) time zone (equals to +00) or a time zone offset (for example, +02:00). +02:00). If the time zone part is not present, the DateTime value represents local time. time. The following pattern describes the DateTime format: YYYY-MM-DDThh:mm:ss[.S+][Z|+-hh:mm] Where: format: YYYY-MM-DDThh:mm:ss[.S+][Z|+-hh:mm] Where: YYYY = Four digit year year MM = Two digit month (01=January, and so on) on) DD = Two digit day of month (01 through 31) 31) T = Time designator (shows start of time component) component) hh = Two digits of hour (00 through 23, AM/PM not allowed) allowed) mm = Two digits of minute (00 through 59) 59) ss = Two digits of second (00 through 59, leap second not allowed) allowed) S+ = One or more digits of decimal fraction of a second second Z = Time is UTC UTC +- = + or - character indicating positive or negative offset to UTC DateTime values are compliant with ISO 8601 "Representation of dates and times" but are restricted according to RFC 3339 "Date and Time on the Internet: Timestamps". The DateTime format is further restricted as follows: follows: - T and Z designators are upper case. case. - . (dot) is used to indicate start of fractions of seconds (ISO 8601 also allows comma) comma)

derivedDataType ProcessBehaviourDT

description

EcimDerivedString with length constraint (9..9) (7..9) and pattern restriction. Currently this parameter is restricted to only one possible value. IMMEDIATE restriction. DELAYED = CSCF application processes will get some extra time up to 55 seconds to be terminated directly. This behavior is preferable in case of gracefully. IMMEDIATE = CSCF SW upgrade as it application processes will reduce the upgrade time. It should however be noted that terminated directly. SIP session that has not yet been established (when reconfiguration happens) will fail as CSCF will lose SIP state information due to the terminated processes. processes.

baseType

string

lengthRange

min

old:		9
new:		7

stringLength

subrange

min

old:		9
new:		7

validValues

old:		IMMEDIATE
new:		DELAYED|IMMEDIATE

validationRules

rule Pattern Constraint