Copyright 2010-2015 Obihai Technology, Inc.
123
Phone Book Pictures
These are pictures to associate with each phone book entry. They are stored in the internal folder
/people/
. Supported
formats are JPEG, PNG, GIF, and BMP. Recommended pixel dimension is no larger than 100Wx100H. Note that the
pictures may be shown on the phone screen as part of caller-ID when the peer’s number matches an entry in the phone
book.
Ring Tones
Ring tone is one of the data types included in the phone customization data package. They are stored in the internal
folder
/ringtones/
. Ringtone filenames must be ended with the “.wav” extension.
Phone Customization Data Package
Customizable data must be wrapped into one single data package in order to upload onto the phone. The final
uploadable data package is a
tar file
that may be optionally gzipped. The size of tar file must be no bigger than 30
MBytes. Inside the tar file, the data should be organized with the same folder structure as the way they are stored in
the phone internal storage:
/backgnd
Wall paper (background pictures) and logo.raw (splash screen)
/dict
Dictionary files
/fonts
Text font files
/ringtones
Ring tone files
/people
Phone book contact pictures
As an example, create a directory
/home/test/obiphone-data
on a linux machine that constains a folder structure as
described above. Copy all the data files to be uploaded to the phone in the corresponding folders in this directory, and
issue the following command lines to create the target tar file:
%
cd /home/test/obiphone-data
%
tar –zcvf ../obiphone-data.tar.gz *
Note that the tar command must be issued inside of the working directory
obiphone-data
, as OBi Phone will NOT strip
the first level in the tar file.
In addition, you can use the following command line to generate the MD5 checksum of the target tar file after it is
created:
%
md5sum obiphone-data.tar.gz
The MD5 checksum will be used as the version of the target customization data package and it must be configured on
the phones also in order to trigger them to download a different version of the package if the currently installed
package has a different MD5 checksum from the configured MD5 checksum. This is explained further in the following
section.
Uploading Customization Data Package to the Phone
After the tar file of the customization data package is created, it must be placed on a server to be uploaded to the
phones when the file is requested from the server by the phones. On the phone side, the downloading of the
customization data package from a server is controlled by a number of configuration parameters as described in the
table below, not unlike the way phone firmware is updated. As you can tell quickly that these parameters have the
same meaning as those similarly named parameters for downloading of firmware.
Note that the phone will attempt downloading of customization data package from the server after firmware update
and configuration parameter provisioning are completed. If the MD5 checksum of the downloaded data packages does
not match the configured value, the package will be dropped and no data update will be performed. Otherwise, the
phone install the downloaded data files into the corresponding folders and then restarts (warm reboot).