routeStatusExpressionCriteria
MX-CROUT-MIB ·
.0.1750.1.100.300.1.400
Object
column
OctetString
Criteria Rule
The expression part of the criteria used to determine if the
route can be applied or not. The other part of the criteria
is the call property defined in the
RouteStatus.PropertiesCriteria parameter.
The expression syntax is related to the selected criteria
properties or can be a special tag:
* CalledE164: Regular expression
* CallingE164: Regular expression
* CalledName: Regular expression
* CallingName: Regular expression
* CalledTon: 'unknown', 'international', 'national',
'network', 'subscriber', or 'abbreviated'
* CallingTon: 'unknown', 'international', 'national',
'network', 'subscriber', or 'abbreviated'
* CalledNpi: 'unknown', 'isdn', 'data', 'telex',
'national', or 'private'
* CallingNpi: 'unknown', 'isdn', 'data', 'telex',
'national', or 'private'
* CalledHost: Regular expression. The format is 'Fqdn
[:port]'. If the '[:port]' is not present, the table uses
the well-known port of the signaling protocol.
* CallingHost: Regular expression. The format is 'Fqdn
[:port]'. If the '[:port]' is not present, the table uses
the well-known port of the signaling protocol.
* CallingPi: 'allowed', 'restricted', or 'interworking'
* CallingSi: 'not-screened', 'passed', 'failed', or
'network'
* CallingItc: 'speech', 'unrestricted', 'restricted',
'3.1Khz', 'udi-ta', or 'video'
* CalledUri: Regular expression
* CallingUri: Regular expression
* DateTime: Day of week and time period and/or date and
time period
* CalledPhoneContext: Regular expression
* CallingPhoneContext: Regular expression
* CalledSipUsername: Regular expression
* CallingSipUsername: Regular expression
* CalledBearerChannel: Regular expression
* CallingBearerChannel: Regular expression
* CallingSipPrivacy: 'disabled', 'none', or 'id'
Special tags:
* <undefined>: Matches if the property is not defined for
the call.
* <default>: Always matches. Generally used to set a
default route if the previous criteria did not match.
Accepted DateTime formats:
Date/Time Period format:
* 'DD.MM.YYYY/HH:MM:SS-DD.MM.YYYY/HH:MM:SS'
* 'DD.MM.YYYY/HH:MM:SS-HH:MM:SS'
* 'DD.MM.YYYY-DD.MM.YYYY'
* 'DD.MM.YYYY'
* 'HH:MM:SS-HH:MM:SS'
Week Day/Time period format:
* 'DDD'
* 'DDD,DDD...'
* 'DDD/HH:MM:SS-HH:MM:SS'
* 'DDD,DDD.../HH:MM:SS-HH:MM:SS'
where DDD must be one of: SUN, MON, TUE, WED, THU, FRI, or
SAT.
Several of the previous formats can be concatenated to form
one expression. They must be separated by |. Example:
25.12.2006 | SUN
Note: Whitespace at the end of a regular expression is
ignored.
See RouteStatus.PropertiesCriteria.
Context
- MIB
- MX-CROUT-MIB
- OID
.0.1750.1.100.300.1.400- Type
- column
- Access
- readonly
- Status
- current
- Parent
- routeStatusEntry
Syntax
OctetString
Values & Constraints
No enumerated values or constraints recorded.