VoIP DDF File
4/8/2010
This topic shows the Device Description Framework (DDF) file for the VoIP Configuration Service Provider. Open Mobile Alliance Device Management (OMA DM) DDF files and the example in this topic are used only for OMA DM provisioning. For more information, see OMA Device Management.
Note
The first line of the DDF is the namespace reference for Microsoft custom properties. For more information, see Managing Microsoft Custom Properties (OMA DM).
<MgmtTree xmlns:MSFT="https://schemas.microsoft.com/MobileDevice/DM">
<VerDTD>1.2</VerDTD>
<Node>
<NodeName>VoIP</NodeName>
<Path>./Vendor/MSFT</Path>
<DFProperties>
<AccessType>
<Get />
</AccessType>
<DFFormat>
<node />
</DFFormat>
<Occurrence>
<One />
</Occurrence>
<Scope>
<Permanent />
</Scope>
<MSFT:AccessRole>8</MSFT:AccessRole>
<MSFT:RWAccess>1</MSFT:RWAccess>
<DFType>
<DDFName></DDFName>
</DFType>
<Description>The root node for VoIP CSP.</Description>
</DFProperties>
<Node>
<NodeName>SIPSettings</NodeName>
<DFProperties>
<AccessType>
<Add />
<Get />
<Delete />
<Replace />
</AccessType>
<DFFormat>
<chr />
</DFFormat>
<Occurrence>
<ZeroOrOne />
</Occurrence>
<Scope>
<Dynamic />
</Scope>
<MSFT:AccessRole>8</MSFT:AccessRole>
<MSFT:RWAccess>3</MSFT:RWAccess>
<DFType>
<MIME>text/plain</MIME>
</DFType>
<Description>The XML string that is used to provision the main SIP server. It shold comply with RTCClient API XML schema. It contains sensitive information such as 'UserName', 'ServerName' or 'Password' etc.</Description>
</DFProperties>
</Node>
<Node>
<NodeName>VoicemailSettings</NodeName>
<DFProperties>
<AccessType>
<Add />
<Get />
<Delete />
<Replace />
</AccessType>
<DFFormat>
<chr />
</DFFormat>
<Occurrence>
<ZeroOrOne />
</Occurrence>
<Scope>
<Dynamic />
</Scope>
<MSFT:AccessRole>8</MSFT:AccessRole>
<MSFT:RWAccess>3</MSFT:RWAccess>
<DFType>
<MIME>text/plain</MIME>
</DFType>
<Description>The XML string that is used to subscribe the voicemail server. It should comply with RTC Client API XML schema. It might contain sensitive informaiton such as 'UserName', 'ServerName' or 'Password' etc.</Description>
</DFProperties>
</Node>
<Node>
<NodeName>VoicemailNumber</NodeName>
<DFProperties>
<AccessType>
<Add />
<Get />
<Delete />
<Replace />
</AccessType>
<DFFormat>
<chr />
</DFFormat>
<Occurrence>
<ZeroOrOne />
</Occurrence>
<Scope>
<Dynamic />
</Scope>
<MSFT:AccessRole>8</MSFT:AccessRole>
<MSFT:RWAccess>3</MSFT:RWAccess>
<DFType>
<MIME>text/plain</MIME>
</DFType>
<Description>The access number that is used to retrieve the VoIP voicemail.</Description>
</DFProperties>
</Node>
<Node>
<NodeName>BackupSIPSettings</NodeName>
<DFProperties>
<AccessType>
<Add />
<Get />
<Delete />
<Replace />
</AccessType>
<DFFormat>
<chr />
</DFFormat>
<Occurrence>
<ZeroOrOne />
</Occurrence>
<Scope>
<Dynamic />
</Scope>
<MSFT:AccessRole>8</MSFT:AccessRole>
<MSFT:RWAccess>3</MSFT:RWAccess>
<DFType>
<MIME>text/plain</MIME>
</DFType>
<Description>The XML string that is used to provision the backup SIP server. It should comply with RTC Client API schema. It might contain sensitive information such as 'UserName', 'ServerName' or 'Password'.</Description>
</DFProperties>
</Node>
<Node>
<NodeName>DialPlan</NodeName>
<DFProperties>
<AccessType>
<Add />
<Get />
<Delete />
<Replace />
</AccessType>
<DFFormat>
<chr />
</DFFormat>
<Occurrence>
<ZeroOrOne />
</Occurrence>
<Scope>
<Dynamic />
</Scope>
<MSFT:AccessRole>8</MSFT:AccessRole>
<MSFT:RWAccess>3</MSFT:RWAccess>
<DFType>
<MIME>text/plain</MIME>
</DFType>
<Description>The XML string that is used to specify the dial plan. It should comply with Dial Plan XML schema.</Description>
</DFProperties>
</Node>
</Node>
</MgmtTree>