Filter
Top Products
3-13
Cisco H.323 Signaling Interface User Guide
OL-4806-01 Rev. A14
Chapter 3 Provisioning the Cisco HSI
H.323 Stack Configuration
RAS Parameters
The parameters in Table 3-8 are required for RAS stack initialization. To modify the RAS parameters,
use the ras MML name variable for the prov-add, prov-dlt, and prov-ed commands.
In the following example, the prov-add command sets the RAS parameter maxfail to the value 3.
Example
prov-add:name=ras,maxfail=3
The array index [i] in some of the parameter names in the first column of Table 3-8 must be replaced
with a valid braced index from 1 to 20, and must be continuous and unique (that is, it must contain no
duplicates).
The Update Type column in Table 3-8 shows when the change to a parameter takes effect after it is
modified:
• Immediate means that the effect of the change is immediate.
• Start means that the application needs to be restarted for the change to take effect.
• Next Call means that the next call has the new parameter set.
Note Immediate and next call update types are dynamic system data.
Note The RAS parameter overlappedSending is not available here because it has been combined with the
Q.931 overlappedSending parameter. If you set the Q.931 overlappedSending parameter, you also set the
the RAS overlappedSending parameter.
Note The asterisk (*) after a parameter name in the first column of Table 3-8 denotes a mandatory RADVision
parameter with an inbuilt default value that will be used if the value is not set in provisioning.
Table 3-8 RAS Parameters
Parameter Name Description Type Example Update Type
manualRAS If this parameter is present,
the stack does not perform
automatic RAS procedures
(it waits to be driven by the
application).
NULL — Start
responseTimeOut* The time (in seconds) that
the stack waits until it
notifies the application that
the called party has failed to
respond to a transaction.
INTEGER(1, 200) 10 Immediate
maxFail* Maximum number of retry
gatekeeper registration
attempts.
INTEGER(1, 200) 3 Immediate