Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"h323GroupAliasesConfigured",
"OBJECT-TYPE",
"SYNTAX",
"OCTET",
"STRING",
"(",
"SIZE",
"(",
"0",
".",
".",
"63",
")",
")",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"The aliases that uniquely identify a group of lines. These are the configured aliases. Each group must be configured with unique aliases. A group can be configured with zero, one or two aliases. A group can be configured with two aliases of the same type or two aliases of different types. A group can be configured with E.164 aliases, H.323 ID aliases and party number aliases. Transport ID aliases (IP addresses) are not allowed. The local IP address of the unit is configured through ipAddressConfigLocalHost. The configured aliases are included in the terminalAlias field of the gatekeeperRequest and registrationRequest messages. If the unit is a H.323 gateway, the E.164 aliases (considered as voice supported prefixes) are also included in the supportedPrefixes field of the gatekeeperRequest and registrationRequest messages. As an example, a group is configured with two aliases, '3460707' as E.164 alias and 'user1' as H.323 ID alias. The following string is used to describe these aliases: E164=3460707;H323ID=user1 Each group must have at least one current alias (either configured or confirmed). If a group has no alias, the unit locks the lines associated with that group. When a line is locked, no call can be made/received from/to this line. Refer to the administrator documentation for the description of the aliases syntax. Refer to the administrator documentation for the description of the configured, confirmed and current aliases.\"",
"DEFVAL",
"{",
[
"literal",
"2222"
],
"}",
"::=",
"{",
"h323AliasesGroupAliasesEntry",
"5",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OCTET STRING",
[
"octetStringSubType",
[
[
0,
63
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The aliases that uniquely identify a group of lines. These are the configured aliases. Each group must be configured with unique aliases. A group can be configured with zero, one or two aliases. A group can be configured with two aliases of the same type or two aliases of different types. A group can be configured with E.164 aliases, H.323 ID aliases and party number aliases. Transport ID aliases (IP addresses) are not allowed. The local IP address of the unit is configured through ipAddressConfigLocalHost. The configured aliases are included in the terminalAlias field of the gatekeeperRequest and registrationRequest messages. If the unit is a H.323 gateway, the E.164 aliases (considered as voice supported prefixes) are also included in the supportedPrefixes field of the gatekeeperRequest and registrationRequest messages. As an example, a group is configured with two aliases, '3460707' as E.164 alias and 'user1' as H.323 ID alias. The following string is used to describe these aliases: E164=3460707;H323ID=user1 Each group must have at least one current alias (either configured or confirmed). If a group has no alias, the unit locks the lines associated with that group. When a line is locked, no call can be made/received from/to this line. Refer to the administrator documentation for the description of the aliases syntax. Refer to the administrator documentation for the description of the configured, confirmed and current aliases."
],
null,
null,
null,
[
"DEFVAL",
"\"\""
]
]
}