complexType UpdateDeviceDefaultsReq

diagram
namespace	http://www.cisco.com/AXL/API/15.0
type	extension of axlapi:APIRequest
properties	base  axlapi:APIRequest
children	uuid Model Protocol LoadInformation InactiveLoadInformation DevicePoolName PhoneButtonTemplate VersionStamp PreferActCodeOverAutoReg
used by	element  updateDeviceDefaults
attributes	Name   Type   Use   Default   Fixed   Annotation sequence   xsd:unsignedLong   optional
source	<xsd:complexType name="UpdateDeviceDefaultsReq">   <xsd:complexContent>     <xsd:extension base="axlapi:APIRequest">       <xsd:sequence>         <xsd:choice>           <xsd:element name="uuid" type="axlapi:XUUID"/>           <xsd:sequence>             <xsd:element name="Model" type="axlapi:XModel" nillable="false" minOccurs="1" maxOccurs="1">               <xsd:annotation>                 <xsd:documentation>String indicating the Device / Phone Model to which these default settings apply.  Read Only.</xsd:documentation>               </xsd:annotation>             </xsd:element>             <xsd:element name="Protocol" type="axlapi:XDeviceProtocol" nillable="false" minOccurs="1" maxOccurs="1">               <xsd:annotation>                 <xsd:documentation>String indicating the Device / Phone Protocol for which these default settings for this Model apply.  Read Only.</xsd:documentation>               </xsd:annotation>             </xsd:element>           </xsd:sequence>         </xsd:choice>         <xsd:element name="LoadInformation" type="axlapi:XLoadInformation" nillable="false" minOccurs="0" maxOccurs="1">           <xsd:annotation>             <xsd:documentation>The filename of the firmware load that is used with a particular type of hardware device model. The file is fed to the phones via TFTP. This can be overridden at the device level.  If not overridden, then all devices of this model will use this firmware load file.</xsd:documentation>           </xsd:annotation>         </xsd:element>         <xsd:element name="InactiveLoadInformation" type="axlapi:XLoadInformation" nillable="false" minOccurs="0" maxOccurs="1">           <xsd:annotation>             <xsd:documentation>The filename of the inactive firmware load that is used with phone models that support dual-bank firmware (background download). The file is fed to the phones via TFTP but is not active.  This can be overridden at the device level. If not overridden, then all devices of this model will download this firmware load file as the inactive load.</xsd:documentation>           </xsd:annotation>         </xsd:element>         <xsd:element name="DevicePoolName" type="axlapi:XFkType" nillable="true" minOccurs="0" maxOccurs="1">           <xsd:annotation>             <xsd:documentation>The name of the Device Pool, (which defines common Device / Phone characteristics), to be assigned, by default, to Devices / Phones with this Model and Protocol.  This can, of course, be overridden at the device level. If not overridden, then all devices of this model and protocol will be assigned to this same Device Pool.</xsd:documentation>           </xsd:annotation>         </xsd:element>         <xsd:element name="PhoneButtonTemplate" type="axlapi:XFkType" nillable="true" minOccurs="0" maxOccurs="1">           <xsd:annotation>             <xsd:documentation>The name of the Phone Button Template, (which defines the line and feature button related characteristics of a Device or Phone ), which may be shared by multiple phones and which will be assigned, by default, to Devices / Phones with this Model and Protocol.  This can, of course, be overridden at the device level. If not overridden, then all devices of this model and protocol will be associated with this same Phone Button Template.</xsd:documentation>           </xsd:annotation>         </xsd:element>         <xsd:element name="VersionStamp" type="axlapi:String128" nillable="true" minOccurs="0" maxOccurs="1">           <xsd:annotation>             <xsd:documentation>UUID changed each time device is updated</xsd:documentation>           </xsd:annotation>         </xsd:element>         <xsd:element name="PreferActCodeOverAutoReg" type="axlapi:boolean" nillable="false" minOccurs="0" maxOccurs="1">           <xsd:annotation>             <xsd:documentation>This boolean setting, when TRUE and unless overridden for specific Phones / Devices of this Model and Protocol, indicates a preferred use of activation code based registrations rather than basic auto-registration.  This can, of course, be overridden at the device level. If not overridden, then all devices of this model and protocol will, when created be initially marked to use this registratin mode.</xsd:documentation>           </xsd:annotation>         </xsd:element>       </xsd:sequence>     </xsd:extension>   </xsd:complexContent> </xsd:complexType>

element UpdateDeviceDefaultsReq/uuid

diagram
type	axlapi:XUUID
properties	content  simple
facets	Kind  Value  Annotation pattern  \{........-....-....-....-............\}
source	<xsd:element name="uuid" type="axlapi:XUUID"/>

element UpdateDeviceDefaultsReq/Model

diagram
type	axlapi:XModel
properties	content  simple nillable  false
annotation	documentation String indicating the Device / Phone Model to which these default settings apply.  Read Only.
source	<xsd:element name="Model" type="axlapi:XModel" nillable="false" minOccurs="1" maxOccurs="1">   <xsd:annotation>     <xsd:documentation>String indicating the Device / Phone Model to which these default settings apply.  Read Only.</xsd:documentation>   </xsd:annotation> </xsd:element>

element UpdateDeviceDefaultsReq/Protocol

diagram
type	axlapi:XDeviceProtocol
properties	content  simple nillable  false
annotation	documentation String indicating the Device / Phone Protocol for which these default settings for this Model apply.  Read Only.
source	<xsd:element name="Protocol" type="axlapi:XDeviceProtocol" nillable="false" minOccurs="1" maxOccurs="1">   <xsd:annotation>     <xsd:documentation>String indicating the Device / Phone Protocol for which these default settings for this Model apply.  Read Only.</xsd:documentation>   </xsd:annotation> </xsd:element>

element UpdateDeviceDefaultsReq/LoadInformation

diagram
type	axlapi:XLoadInformation
properties	minOcc  0 maxOcc  1 content  complex nillable  false
attributes	Name   Type   Use   Default   Fixed   Annotation special   axlapi:boolean
annotation	documentation The filename of the firmware load that is used with a particular type of hardware device model. The file is fed to the phones via TFTP. This can be overridden at the device level.  If not overridden, then all devices of this model will use this firmware load file.
source	<xsd:element name="LoadInformation" type="axlapi:XLoadInformation" nillable="false" minOccurs="0" maxOccurs="1">   <xsd:annotation>     <xsd:documentation>The filename of the firmware load that is used with a particular type of hardware device model. The file is fed to the phones via TFTP. This can be overridden at the device level.  If not overridden, then all devices of this model will use this firmware load file.</xsd:documentation>   </xsd:annotation> </xsd:element>

element UpdateDeviceDefaultsReq/InactiveLoadInformation

diagram
type	axlapi:XLoadInformation
properties	minOcc  0 maxOcc  1 content  complex nillable  false
attributes	Name   Type   Use   Default   Fixed   Annotation special   axlapi:boolean
annotation	documentation The filename of the inactive firmware load that is used with phone models that support dual-bank firmware (background download). The file is fed to the phones via TFTP but is not active.  This can be overridden at the device level. If not overridden, then all devices of this model will download this firmware load file as the inactive load.
source	<xsd:element name="InactiveLoadInformation" type="axlapi:XLoadInformation" nillable="false" minOccurs="0" maxOccurs="1">   <xsd:annotation>     <xsd:documentation>The filename of the inactive firmware load that is used with phone models that support dual-bank firmware (background download). The file is fed to the phones via TFTP but is not active.  This can be overridden at the device level. If not overridden, then all devices of this model will download this firmware load file as the inactive load.</xsd:documentation>   </xsd:annotation> </xsd:element>

element UpdateDeviceDefaultsReq/DevicePoolName

diagram
type	axlapi:XFkType
properties	minOcc  0 maxOcc  1 content  complex nillable  true
attributes	Name   Type   Use   Default   Fixed   Annotation uuid   axlapi:XUUID   optional
annotation	documentation The name of the Device Pool, (which defines common Device / Phone characteristics), to be assigned, by default, to Devices / Phones with this Model and Protocol.  This can, of course, be overridden at the device level. If not overridden, then all devices of this model and protocol will be assigned to this same Device Pool.
source	<xsd:element name="DevicePoolName" type="axlapi:XFkType" nillable="true" minOccurs="0" maxOccurs="1">   <xsd:annotation>     <xsd:documentation>The name of the Device Pool, (which defines common Device / Phone characteristics), to be assigned, by default, to Devices / Phones with this Model and Protocol.  This can, of course, be overridden at the device level. If not overridden, then all devices of this model and protocol will be assigned to this same Device Pool.</xsd:documentation>   </xsd:annotation> </xsd:element>

element UpdateDeviceDefaultsReq/PhoneButtonTemplate

diagram
type	axlapi:XFkType
properties	minOcc  0 maxOcc  1 content  complex nillable  true
attributes	Name   Type   Use   Default   Fixed   Annotation uuid   axlapi:XUUID   optional
annotation	documentation The name of the Phone Button Template, (which defines the line and feature button related characteristics of a Device or Phone ), which may be shared by multiple phones and which will be assigned, by default, to Devices / Phones with this Model and Protocol.  This can, of course, be overridden at the device level. If not overridden, then all devices of this model and protocol will be associated with this same Phone Button Template.
source	<xsd:element name="PhoneButtonTemplate" type="axlapi:XFkType" nillable="true" minOccurs="0" maxOccurs="1">   <xsd:annotation>     <xsd:documentation>The name of the Phone Button Template, (which defines the line and feature button related characteristics of a Device or Phone ), which may be shared by multiple phones and which will be assigned, by default, to Devices / Phones with this Model and Protocol.  This can, of course, be overridden at the device level. If not overridden, then all devices of this model and protocol will be associated with this same Phone Button Template.</xsd:documentation>   </xsd:annotation> </xsd:element>

element UpdateDeviceDefaultsReq/VersionStamp

diagram
type	axlapi:String128
properties	minOcc  0 maxOcc  1 content  simple nillable  true
facets	Kind  Value  Annotation maxLength  128
annotation	documentation UUID changed each time device is updated
source	<xsd:element name="VersionStamp" type="axlapi:String128" nillable="true" minOccurs="0" maxOccurs="1">   <xsd:annotation>     <xsd:documentation>UUID changed each time device is updated</xsd:documentation>   </xsd:annotation> </xsd:element>

element UpdateDeviceDefaultsReq/PreferActCodeOverAutoReg

diagram
type	axlapi:boolean
properties	minOcc  0 maxOcc  1 content  simple nillable  false
facets	Kind  Value  Annotation pattern  (t)|(f)|(true)|(false)|(0)|(1)
annotation	documentation This boolean setting, when TRUE and unless overridden for specific Phones / Devices of this Model and Protocol, indicates a preferred use of activation code based registrations rather than basic auto-registration.  This can, of course, be overridden at the device level. If not overridden, then all devices of this model and protocol will, when created be initially marked to use this registratin mode.
source	<xsd:element name="PreferActCodeOverAutoReg" type="axlapi:boolean" nillable="false" minOccurs="0" maxOccurs="1">   <xsd:annotation>     <xsd:documentation>This boolean setting, when TRUE and unless overridden for specific Phones / Devices of this Model and Protocol, indicates a preferred use of activation code based registrations rather than basic auto-registration.  This can, of course, be overridden at the device level. If not overridden, then all devices of this model and protocol will, when created be initially marked to use this registratin mode.</xsd:documentation>   </xsd:annotation> </xsd:element>

XML Schema documentation generated by XMLSpy Schema Editor http://www.altova.com/xmlspy