Accessing local (Craft) procedures
Note:
In addition to the procedures listed here, the administrator may allow access to only the VPN
procedure, by setting the VPNPSWD parameter in the settings file. For more information on
access to VPN-only Local Administrative Options, see the VPN Setup Guide for 9600 Series
IP Telephones (Document 16-602968).
As of Release 1.5, when PROCSTAT is “0” (full access to local Craft procedures) you can
invoke local craft procedures during initialization whenever this message displays:
* to program
or at any other time the initialization process can support a processing interrupt. If PROCSTAT
is set to “1” (access allowed only to the VIEW craft procedure for debugging purposes), you
can invoke local Craft procedures only when the “* to program” message displays during
initialization.
Note:
The “* to program” message is supported even if the value of PROCSTAT is “1” when the
messages “Address conflict,” “Subnet conflict,” “Bad router?” and “Bad FileSv
address” display. Allowing Craft procedure access in response to these messages prevents
situations in which input is required but not allowed.
For earlier software releases, PROCSTAT must be zero to invoke craft access (Release 1.2).
For Releases 1.0 and 1.1, PROCSTAT must be equal to “0” plus PROCPSWD must be null.
Note:
The factory-set default Craft Access Code (PROCPSWD) is 27238.
Using Local Administrative (Craft) Options
34 H.323 Installation & Maintenance Guide R6.1 May 2011
To Next Page
Loading...
