Linksys SPA921 Cisco Small Business IP Telephony Devices Provisioning Guide - Page 57

Report Rule, Resync_Fails_On_FNF. If Resync_Fails_On_FNF is set to No, then the device - default password

Get Linksys SPA921 - Cisco - IP Phone PDF manuals and user guides
UPC - 745883570799
View all Linksys SPA921 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 57 highlights

Creating Provisioning Scripts Using Provisioning Parameters 2 In the following 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, transmitting the contents of the macro expanded GPP_A (which may provide additional information on the state of the device). ($REGTMR1 eq 0)? http://p.tel.com/has-reg.cfg | [--post a] http://p.tel.com/lost-reg? In the following example, the device resyncs to the same server, but 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 In the following 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/initprov | https://p.tel.com/configs In the following example, the profile returned by the server is assumed to contain XML element tags that need to be remapped to proper parameter names by the aliases map stored in GPP_B. [--alias b] https://p.tel.com/account/spa$MA.xml A resync is typically considered unsuccessful if a requested profile is not received from the server. This default behavior can be overridden by the parameter Resync_Fails_On_FNF. If Resync_Fails_On_FNF is set to No, then 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. Report Rule The IP Telephony Device provides a mechanism for reporting its current internal configuration to the provisioning server. This is useful for development and debugging. The report syntax is similar to the XML profile. All provisionable parameters are included, except for the values of passwords, keys, and the GPP_SA to GPP_SD parameters, which are not shown. Cisco Small Business IP Telephony Devices Provisioning Guide 55

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
Creating Provisioning Scripts
Using Provisioning Parameters
Cisco Small Business IP Telephony Devices Provisioning Guide
55
2
In the following 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, transmitting the contents of the macro expanded
GPP_A (which may provide additional information on the state of the device).
In the following example, the device resyncs to the same server, but 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?
In the following 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
In the following example, the profile returned by the server is assumed to contain
XML element tags that need to be remapped to proper parameter names by the
aliases map stored in GPP_B.
A resync is typically considered unsuccessful if a requested profile is not received
from the server. This default behavior can be overridden by the parameter
Resync_Fails_On_FNF. If Resync_Fails_On_FNF is set to No, then 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.
Report Rule
The IP Telephony Device provides a mechanism for reporting its current internal
configuration to the provisioning server. This is useful for development and
debugging. The report syntax is similar to the XML profile. All provisionable
parameters are included, except for the values of passwords, keys, and the
GPP_SA to GPP_SD parameters, which are not shown.