Cisco 8800 Series, Manual

Page: 112 / 544

Example 1
This example resyncs unconditionally to the profile at the specified URL, and performs an HTTP GET request
to the remote provisioning server:
http://remote.server.com/cisco/$MA.cfg
Example 2
In this example, the device resyncs to two different URLs, depending on the registration state of Line 1. In
case of lost registration, the device performs an HTTP POST to a CGI script. The device sends the contents
of the macro expanded GPP_A, which may provide additional information on the device state:
($PRVTMR ge 600)? http://p.tel.com/has-reg.cfg
| [--post a] http://p.tel.com/lost-reg?
Example 3
In this example, the device resyncs to the same server. The device provides additional information if a certificate
is not installed in the unit (for legacy pre-2.0 units):
(“$CCERT” eq “Installed”)? https://p.tel.com/config?
| https://p.tel.com/config?cisco$MAU
Example 4
In this example, Line 1 is disabled until GPP_A is set equal to Provisioned through the first URL. Afterwards,
it resyncs to the second URL:
(“$A” ne “Provisioned”)? (Line_Enable_1_ = “No”;)! https://p.tel.com/init-prov
| https://p.tel.com/configs
Example 5
In this example, the profile that the server returns is assumed to contain XML element tags. These tags must
be remapped to proper parameter names by the aliases map stored in GPP_B:
[--alias b] https://p.tel.com/account/$PN$MA.xml
A resync is typically considered unsuccessful if a requested profile is not received from the server. The
Resync_Fails_On_FNF parameter can override this default behavior. If Resync_Fails_On_FNF is set to No,
the device accepts a file-not-found response from the server as a successful resync. The default value for
Resync_Fails_On_FNF is Yes.
Upgrade Rule
Upgrade rule is to tell the device to activate to a new load and from where to get the load, if necessary. If the
load is already on the device, it will not try to get the load. So, validity of the load location does not matter
when the desired load is in the inactive partition.
Cisco IP Phone 8800 Series Multiplatform Phone Administration Guide for Release 11.3(1) and Later
92
Cisco IP Phone Provisioning
Upgrade Rule