© 2003 - 2005 Sipura Technology, Inc
Proprietary (See Copyright Notice on Page 2)
24
spc –-aes –-hex-key 8d23fe7...a5c29 spa2000.txt spa2000.cfg
A CFG file can be both targeted and key encrypted, as suggested by the following example:
spc –-target 000e08aaa010 –-aes –-hex-key 9a20...eb47 a.txt a.cfg
The status messages printed by spc can be suppressed with the “--quiet” command line option. Or
they can be redirected to a file, with the “--log file_name” command line option. In the latter case, the
spc command line invocation itself is also printed in the log file, preceded by a timestamp.
spc –-quiet . . .
spc –-log prov.log . . .
An alternative profile syntax using XML is described in the Sipura SPA Provisioning Guide. XML
profiles can be fed to the SPA in a resync operation without the need to compile them first into a
binary object.
3.1.3. Provisioning
Parameters
The parameters described in this section represent a basic subset of all parameters available to
control provisioning and remote upgrades. Please refer to the Sipura SPA Provisioning Guide for a
comprehensive description of all available parameters.
Provisioning is controlled by the following parameters (firmware upgrades are discussed in a later
section).
•
Provision_Enable
•
Resync_On_Reset
•
Resync_Random_Delay
•
Resync_Periodic
•
Resync_Error_Retry_Delay
•
Resync_From_SIP
•
Profile_Rule
•
Log_Resync_Request_Msg
•
Log_Resync_Success_Msg
•
Log_Resync_Failure_Msg
•
GPP_A
•
GPP_B
•
GPP_C
•
GPP_D
•
GPP_SA
•
GPP_SB
•
GPP_SC
•
GPP_SD
Provision Enable:
ParName: Provision_Enable
