Description: This object must only be set via the CM configuration file during the provisioning process. After CM is operational, this object can not be set via SNMP. MTA provisioning modes: 0: MTA follows the PacketCable provisioning specifications and supports BASIC, HYBRID and SECURE flows. 1: MTA will provision using only the CM config file. VoIP parameters MUST be included in the CM config file as VSIFs. This option will become obsolete. 2: MTA will learn the MTA config file name and location from the MTA DHCP OFFER. If the filename or location is missing, MTA will switch to mode 3. 3: MTA will learn the MTA config file name and location via SNMP. The MTA will send an SNMP inform to the provisioning server specified in DHCP option 122.3 or 177.3, depending on saCmMtaDhcpPktcOption (note: MTA will not provision if saCmMtaDhcpPktcOption = requireNone(1) and no option 122.3 or 177.3 is specified). 4: MTA will learn the MTA config file name and location and the MTA host name from the MTA DHCP OFFER/ACK. If the filename is missing in the DHCP OFFER/ACK, the MTA will request a config file name based on the MTA mac address (example: 000f21c4e145.bin). If the MTA host name is missing in the DHCP OFFER/ACK the MTA will use a host name of MAC_ADDR (example: 000f21c4e145). 5: MTA will request a config file name based on the MTA mac address (example: 000f21c4e145.bin). MTA will learn the MTA config file location via DHCP. MTA will use a host name of MAC_ADDR (example: 000f21c4e145). MTA will NOT use the file name and host name in the DHCP ACK even if the parameters are present. 6: Web page provisioning. Parameters from a web page will be used rather than from config file. All the web page parameters are stored in non-vol. Base provisioning method is 2 above. For modes other than 0, MTA DHCP options 122, 177 are not required. Note: This object can be set via the CM configuration file ONLY.