Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"h323MultipleRegGkDiscoveryMode",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"automatic",
"(",
"0",
")",
",",
"manual",
"(",
"1",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"The gatekeeper discovery method used by the line. This variable only applies to unit of type terminal. AUTOMATIC GATEKEEPER DISCOVERY METHOD The line follows these steps until it registers successfully. step 1 : the line sends a gatekeeperRequest message on the well-known Discovery Multicast Address. Every gatekeeper on the same network (as the line) receives the gatekeeperRequest message. step 2 : a gatekeeper that accepts the gatekeeper request sends a gatekeeperConfirm message to the line. The line then sends a registrationRequest message to that gatekeeper. The gatekeeper responds with a registrationConfirm message. The line is now registered. If several gatekeepers accept the gatekeeper request, the line registers with the first gatekeeper that accepted the gatekeeper request (i.e. the gatekeeper that sent the first gatekeeperConfirm message received by the line). step 3 : a gatekeeper that rejects the gatekeeper request sends a gatekeeperReject message to the line. The line does not initiate any action upon receipt of a gatekeeperReject message. step 4 : if no gatekeeperConfirm message is received within a time-out, the line starts again at step 1. The calculation of the time-out starts as soon as the first gatekeeperRequest message is sent. note : after sending a gatekeeperRequest message, the line only considers the first answer (the first gatekeeperConfirm message or the first gatekeeperReject message). If the first answer to be received is a gatekeeperReject message, the line sends another gatekeeperRequest message. MANUAL GATEKEEPER DISCOVERY METHOD The unit is configured with a list of gatekeeper IP addresses. Each line uses the same list of gatekeeper IP addresses. The line follows these steps as long as it does not register successfully. step 1 : the line sends a registrationRequest message to the first gatekeeper IP address of the list. step 2 : if the gatekeeper accepts the registration request, i.e. the gatekeeper sends a registrationConfirm message to the line, the line is now registered. step 3 : if the gatekeeper rejects the registration request, i.e. the gatekeeper sends a registrationReject message to the line, the line sends a registrationRequest message to the next gatekeeper IP address of the list. step 4 : if the registration request times-out, i.e. there is no answer from the gatekeeper, the line sends a registrationRequest message to the next gatekeeper IP address of the list. step 5 : If the line reaches the end of the list without registering successfully, the line waits before starting again at step 1. During this waiting period, the line does not send any registrationRequest message.\"",
"DEFVAL",
"{",
"manual",
"}",
"::=",
"{",
"h323RegistrationMultipleRegistrationIfEntry",
"15",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"automatic",
0
],
[
"manual",
1
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The gatekeeper discovery method used by the line. This variable only applies to unit of type terminal. AUTOMATIC GATEKEEPER DISCOVERY METHOD The line follows these steps until it registers successfully. step 1 : the line sends a gatekeeperRequest message on the well-known Discovery Multicast Address. Every gatekeeper on the same network (as the line) receives the gatekeeperRequest message. step 2 : a gatekeeper that accepts the gatekeeper request sends a gatekeeperConfirm message to the line. The line then sends a registrationRequest message to that gatekeeper. The gatekeeper responds with a registrationConfirm message. The line is now registered. If several gatekeepers accept the gatekeeper request, the line registers with the first gatekeeper that accepted the gatekeeper request (i.e. the gatekeeper that sent the first gatekeeperConfirm message received by the line). step 3 : a gatekeeper that rejects the gatekeeper request sends a gatekeeperReject message to the line. The line does not initiate any action upon receipt of a gatekeeperReject message. step 4 : if no gatekeeperConfirm message is received within a time-out, the line starts again at step 1. The calculation of the time-out starts as soon as the first gatekeeperRequest message is sent. note : after sending a gatekeeperRequest message, the line only considers the first answer (the first gatekeeperConfirm message or the first gatekeeperReject message). If the first answer to be received is a gatekeeperReject message, the line sends another gatekeeperRequest message. MANUAL GATEKEEPER DISCOVERY METHOD The unit is configured with a list of gatekeeper IP addresses. Each line uses the same list of gatekeeper IP addresses. The line follows these steps as long as it does not register successfully. step 1 : the line sends a registrationRequest message to the first gatekeeper IP address of the list. step 2 : if the gatekeeper accepts the registration request, i.e. the gatekeeper sends a registrationConfirm message to the line, the line is now registered. step 3 : if the gatekeeper rejects the registration request, i.e. the gatekeeper sends a registrationReject message to the line, the line sends a registrationRequest message to the next gatekeeper IP address of the list. step 4 : if the registration request times-out, i.e. there is no answer from the gatekeeper, the line sends a registrationRequest message to the next gatekeeper IP address of the list. step 5 : If the line reaches the end of the list without registering successfully, the line waits before starting again at step 1. During this waiting period, the line does not send any registrationRequest message."
],
null,
null,
null,
[
"DEFVAL",
"manual"
]
]
}