Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section
Panel
titleColor#F85404
titleBGColor#F0F0F0
titleIntroduction

You can start provisioning via :

  • Handset procedure
    • Normal provisioning
    • Easy provisioning
    • Diagnostic provisioning
  • Automatic within a defined time frame, configured via auto-provisioning
Panel
titleColor#F85404
titleBGColor#F0F0F0
titleNormal provisioning

This mode starts normal provisioning.

  1. Open the handset menu <Center key>
  2. *#provstart#  or *#776878278#
Panel
titleColor#F85404
titleBGColor#F0F0F0
titleEasy provisioning

From software version 11, we have implemented an easy provisioning method that can be used for testing provisioning.

  1. Open the handset menu <Center key>
  2. *#provskon#  or *#77687566#
  3. The Right Softkey will now show Prov. by pressing this key provisioning will be started
  4. Softkey will disappear after device restart (off -> on)
Panel
titleColor#F85404
titleBGColor#F0F0F0
titleDiagnostic provisioning

This mode allows to list errors seen during provisioning.

  1. Open the handset menu <Center key>
  2. *#provstartdiag#  or *#7768782783424#

Format of the error presented on the screen: error_line#error_nr,

  • error_line - the line in XML file where the error occurred
  • error_nr - error code, see Table_1.

During the search, errors are displayed on the screen on the fly. Softkeys are not visible. Process will stop if the next error does not fit on the display. In this case,  softkey "Continue" will appear, which resumes process. After process is finished, SK "OK" appear which leads to main menu. Provisioning procedure may be aborted by long-press on end key. In headline file number is visible, which can be helpful during nested provisioning procedure.

Display_1

Note
titleRemark

Whenever xml-syntax recognized (errors: 1-14) provisioning is stopped and no data will be written to the HS.
Content errors (nr 20-23) may selectively affect data writing to the HS.

Table_1
#error_nrDescriptionExamples
Syntax errors
1xml parsing interrupted (critical failure in configuration)-
2unexpected tag close

<nvm> </nmv>
</bad>

3exceeded declared count of opened tags (max 16)<tag1><tag2><tag3><tag4><tag5><tag6>...<tag16><tag17>
4incorrect close bracket

<root><a/root>
<root/a>

5unrecognized file content (not XML file)load not xml file (e.g. cmd.com)
6incorrect tag name or unexpected character in tag name

<
<tag_not_closed
<#tag></#tag>

7invalid atribute (wrong character in name or value, missing '=')

<nvm atr '123' />
<nvm atr = '<123>' />
<nvm at&r='123' />
<root value="25<7"></root>
<nvm atr '123' /> ='123' />

8quotation mark not found in argument value

<nvm atr=123 />
<nvm atr=123' />
<nvm atr= '123   />
<nvm atr='123

9buffer for value too small (supported max 255 characters)<argument='12345678902354o63894675983465983465893469....' />
10unexpected end of file

<!-- not ended comments

11the file ends without closing all tags

<root>example
<nvm> <entry arg='123' />
<root> <nvm> <args>

12

invalid UTF-8 character coding in argument value

If UTF-8 syntax error ocures in e.g. tag name, argument name, command  the bug will not be reported

-
13Unrecognized command (no DOCTYPE, no CDATA)<!UNKNOWN >
<!HELLO WORLD=""><root></root></HELLO>
14Duplicated argmument name<param name="volume" name="volume" />
Content errors
20unrecognized tag<incorrect_tag></incorrect_tag>
21unrecognized argument<nvm name='unrecognized_name' value='123' />
22incorrect argument value (e.g. out of range)<nvm name='telephony_visible' value='123' />
23entry not saved (insufficient amount of data)<lists><list list_name="contacts"><entry surname="Peter" /></list></lists>
Panel
titleColor#F85404
titleBGColor#F0F0F0
titleAutomatically within a defined time frame.

This can be set via auto-provisioning

Parametervalue
provisioning_time_frame_beginTime (in format HHMM)
provisioning_time_frame_endTime (in format HHMM)
provisioning_selected_days
  • "monday,friday,wednesday,daily"
  • Days as strings: "monday", "tuesday", "wednesday", "thursday", "friday", "saturday", "sunday", "daily".

Days names may be separated only by single comma ','. No other character is allowed. Any incorrect character causes value rejection. Comma ',' cannot start or end string. Day name may occur only once in a string.;

Example:

<?xml version="1.0" encoding="UTF-8"?>
<provisioning version="1.1" productID="Gsdecthx">
<nvm>

<param name="provisioning_time_frame_begin" value="15:101510" />
<param name="provisioning_time_frame_end" value="15:401540" />
<param name="provisioning_selected_days" value="daily" />

</nvm >

</provisioning>