The identity element is a grouping element for conditions which are based on a user's identity. The condition is satisfied if any of the one or many elements within it is matched. The one element specifies an individual identity to be matched. The one element is a sub-MO allowing multiple instances with "id" as the unique key. The many element specifies a match for a set of identities. The many element is a sub-MO allowing multiple instances with "domain" as the unique key The number-match element specifies a match for a set of numerical identities. The number-match element is a sub-MO allowing multiple instances with "starts-with" as the unique key. The individual identity to be matched. For all uses except incoming communication barring user rules, this takes the form of a sip: or tel: URI. For use within incoming communication barring user rules, this takes the form of a sip: or tel: or hidden: URI. Each tel: URI and sip: URI that was converted from a tel: URI according to section 19.1.6 of RFC 3261 contains a normalized number. This must be present on the creation of a one element. The individual domain to be matched. A many element with an explicit domain value matches all identities within that domain. A many element with the special wildcard value "*" matches all identities. This must be present on the creation of a many element. An individual domain to be excluded from a many with special value "*" that would otherwise match all identities. The except-domain element is a sub-MO allowing multiple instances with "domain" as the unique key. An individual identity to be excluded from the identities matching the enclosing many. The except-id element is a sub-MO allowing multiple instances with "id" as the unique key. The individual identity to be excluded from the match. If this is within a many element with a specific domain then the excluded identity must be a sip: URI within that domain. If this is within a many element with the special wildcard value of "*", then it can be a sip: or tel: URI. Each tel: URI and sip: URI that was converted from a tel: URI according to section 19.1.6 of RFC 3261 contains a normalized number. This must be present on the creation of an except-id element. The individual domain to be excluded from the match. This must be present on the creation of an except-domain element. The first few characters of the normalised form of the number to be matched. This must be present on the creation of a number-match element. The validity element is a grouping element for time periods (intervals) within which the rule is valid. The interval element specifies a date and time period within which the validity condition is satisfied. The interval element is a sub-MO allowing multiple instances with "from" as the unique key The validity element is a grouping element for time periods (intervals) within which the rule is NOT valid. The intervals element specifies a date and time periods within which the invalidity condition is NOT satisfied. The interval element is a sub-MO allowing multiple instances with "from" as the unique key The date and time that specifies the start of the valid interval. It is a standard dateTime value e.g. "2008-11-27T20:00:00Z" for a UTC time or "2008-10-12T20:00:00-08:00" for a time with 8 hours offset from UTC. This must be present on the creation of an interval element. The date and time that specifies the end of the valid interval. It is a standard dateTime value e.g. "2008-11-27T20:00:00Z" for a UTC time or "2008-10-12T20:00:00-08:00" for a time with 8 hours offset from UTC. This must be present on the creation of an interval element. The allow element has values "true" or "false". If set to "false" then any communications satisfying the corresponding conditions will be barred unless overridden by another rule with allow set to "true". If set to "true" then any communications satisfying the corresponding conditions will be allowed i.e. not barred. This must be present on the creation of a communication barring rule. The allow-true-action element has values "activated" or "deactivated". When set to "activated" it allows the subscriber to use the allow action with the value of "true" in the associated communication barring rules to explicitly allow communications that match the associated conditions. With this absent or set to "deactivated" the subscriber is only permitted to use the allow action with the value of "false" to bar communications. The valid-periods element is a grouping element for recurring time periods (intervals) within which the rule is valid. In order for the valid-periods condition to be satisfied the current date/time must match one of the valid-days if present and one of the valid-times if present. The utc-offset element specifies the offset to be taken from UTC when determining times of day and when each day starts and ends. If utc-offset is omitted then days and times are based on UTC The valid-days element specifies each of the days on which the condition would match, subject to also meeting other subconditions if present. If valid-days is omitted then the condition applies to all days of the week. The valid-times specifies periods of the day in which the condition would match, subject to also meeting other subconditions, if present. If valid-times is omitted then the condition applies to all times of the day. The valid-times condition must contain at least one interval. The valid-months element specifies each of the months on which the condition would match, subject to also meeting other sub-conditions if present. If valid-months is omitted then it applies to all months of the year. The valid-weeks element specifies each of the weeks on which the condition would match, subject to also meeting other sub-conditions if present. If valid-weeks is omitted then it applies to all weeks of the year. The repeat-daily element specifies start day and repetition interval for the days on which the condition would match, subject to also meeting other sub-conditions if present. If repeat-daily is omitted then it applies to all days of the year The repeat-weekly element specifies start week and repetition interval for the weeks on which the condition would match, subject to also meeting other sub-conditions if present. If repeat-weekly is omitted then it applies to all weeks of the year The repeat-monthly element specifies start month and repetition interval for the months on which the condition would match, subject to also meeting other sub-conditions if present. If repeat-monthly is omitted then it applies to all months of the year The valid-monthdays element specifies each of the days on which the condition would match, subject to also meeting other sub-conditions if present. If valid-monthdays is omitted then the condition applies to all days of the month. The except-holidays element specifies that if the current day matches to the holidays provisioned for the user, then the valid-periods condition is evaluated to false. The day of the week. This is a multi-value parameter. A time interval. The interval element is a sub-MO allowing multiple instances with "from" as the unique key. The time of day at which the interval starts. The format is HH:MM in the 24 hour clock. This must be present on the creation of an interval element. The time of day at which the interval ends. The format is HH:MM in the 24 hour clock. The interval applies until the end of the specified minute. This must be present on the creation of an interval element. The month of the year. The format is integer of the month number. This is a multi-value parameter. The week of the year. The format is integer of the week number. This is a multi-value parameter. The start day of the repetition. The format is YYYY-MM-DD. The repetition interval in days. The format is integer. The start day of the repetition. The format is YYYY-MM-DD. The repetition interval in weeks. The format is integer. The start day of the repetition. The format is YYYY-MM-DD. The repetition interval in months. The format is integer. The day of the month. Allowed formats:1..31, -1..-31, [-1..-5|1..5][Monday..Sunday] This is a multi-value parameter. A list of all of the related targets that can be included in communication distribution rules in addition to the PRIMARY number itself i.e. that of the served user. Up to 10 entries can be included. If fixed-targets is set to "true" then the target identities are set by the operator and cannot be changed by the user. The target element is a sub-MO allowing multiple instances with "name" as the unique key. The name for the distribution target. This is the name by which distribution rules refer to targets. This must be present on the creation of a target element. The id is the identity of the target. It is a sip: or tel: URI. Each tel: URI and sip: URI that was converted from a tel: URI according to section 19.1.6 of RFC 3261 contains a normalized number, or a number that can be normalized after removing a dynamic ad-hoc presentation supplementary service code and/or a carrier select code. This must be present on the creation of a target element. The parallel-distribution element is a grouping element with details of the targets to which the communication should be distributed in parallel. The maximum time period for which the targets shall be left ringing in parallel without an answer. The target element is a sub-MO allowing multiple instances with "name" as the unique key. It is a reference by name to a target identity to which the communication should be distributed. At least one target must be present on creation of a parallel-distribution element. The serial-distribution element is a grouping element with details of the targets to which the communication should be distributed in series. The target element is a sub-MO allowing multiple instances with "name" as the unique key. It is a reference by name to a target identity to which the communication should be distributed. At least one target must be present on creation of a serial-distribution element. The flexible-distribution element is a grouping element with details of the targets to which the communication should be distributed in a flexible way. The target element is a sub-MO allowing multiple instances. It is a reference by name to a target identity to which the communication should be distributed. At least one target must be present on creation of a flexible-distribution element. A target element with the same name cannot be present more than once in the same parallel group. (There is always one member in a serial group.) The name of a target identity. The name must be one of the following: the name of a target defined in user-common-data; the name of a target-device defined in user-common-data; the special value PRIMARY for all of the user’s devices or, in the case of communication distribution the name of a target defined in the target-list within that service. The name must be present on the creation of a target element. The name of a target identity. The name must be one of the following: the name of a target defined in user-common-data; the name of a target-device defined in user-common-data; the special value PRIMARY for all of the user’s devices or, in the case of communication distribution the name of a target defined in the target-list within that service. The name must be present on the creation of a target element. The maximum time period for which this target shall be left ringing in without an answer before switching to the next target. The name of a target identity. The name must be one of the following: the name of a target defined in user-common-data; the name of a target-device defined in user-common-data; the special value PRIMARY for all of the user\u2019s devices or, in the case of communication distribution the name of a target defined in the target-list within that service. The name must be present on the creation of a target element. The ring mode type - serial or parallel - that is to be used within the flexible distribution. The maximum time period for which this target shall be left ringing in without an answer before switching to the next target. The target element specifies the identity to which the communication should be diverted. This takes the form of a sip: or tel: URI or "voicemail:internal" for forwarding to voice mail. Each tel: URI and sip: URI that was converted from a tel: URI according to section 19.1.6 of RFC 3261 contains a normalized number, or a number that can be normalized after removing a dynamic ad-hoc presentation SSC and/or a CSC. This must be present on the creation of a cdiv-rule. The notify-caller element has values "true" or "false". It controls whether the caller is notified that the call is being forwarded. If it is not included then the default behaviour is to notify the caller (true). The reveal-identity-to-caller element has values "true" or "false". It controls whether the caller being notified that the call is being forwarded receives the target's identity information. If it is not included then the default behaviour is to reveal the target's identity to the caller (true). The notify-served-user element has values "true" or "false". It controls whether the served user is notified that the call is being forwarded. If it is not included then the default behaviour is not to notify the served user (false). The notify-served-user-on-outbound-call element has values true or false. It controls whether the served user is notified that calls are being forwarded when he makes a call attempt. If it is not included then the default behaviour is not to notify the served user on outbound calls (false). The reveal-identity-to-target element has values "true" and "false". It controls whether the diverted-to party receives identity information of the diverting party. If it is not included then the default behaviour is to reveal the diverting party's identity to the target (true). The name of the announcement to be played. This must be present on the creation of a play-segmented-announcement element. The announcement variable to be embedded into the announcement. It's use is optional, i.e. a segmented announcement may or may not contain any variable segment. Maximum 32 announcement variables can be embedded into a segmented announcement. A keyed "announcement-variable" element with the "variable-name" attribute can be deleted from the list of announcement variables by setting the "xs:nil" attribute to true. The name of the announcement variable to be embedded. This must be present on the creation of an announcement-variable element inside a play-segmented-announcement element. The variable value is defined in the variable-value child element of the announcement-variable element. According to H.248.9, the allowed characters in place of a variable value are ASCII 0x09, 0x20-0x7E.