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

Profile Rules

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 55 highlights

Creating Provisioning Scripts Using Provisioning Parameters 2 In this example, the IP Telephony Device periodically resyncs every two hours. In case of a resync failure, the device retries in 30 minutes, then again in 1 more hour, then after two more hours, and then after four more hours, continuing at four-hour intervals until it successfully resyncs. The following is another example: Resync_Periodic = 3600+600 Resync_Error_Retry_Delay = 1800+300,3600+600,7200+900 In this example, the device periodically resyncs every hour (plus an additional random delay of up to 10 minutes). In case of resync failure, the device retries in 30 minutes (plus up to five minutes more). If it fails again, it waits an additional hour (plus up to 10 minutes). If again unsuccessful, it waits two more hours (plus up to 15 minutes), and so also thereafter, until it successfully resyncs. The following is another example: Upgrade_Error_Retry_Delay = 1800,3600,7200,14400+3600 In this example, if a remote upgrade attempt fails, the device retries the upgrade in 30 minutes, then again after one more hour, then in two hours. If it still fails, it subsequently retries every four to five hours, until it succeeds. Profile Rules The IP Telephony Device provides multiple remote configuration profile parameters (Profile_Rule*). This means that each resync operation can retrieve multiple files, potentially managed by different servers. In the simplest scenario, the device resyncs periodically to a single profile on a central server, which updates all pertinent internal parameters. Alternatively, the profile can be split between different files. One file is common for all the IP Telephony Devices in a deployment, while a separate file is provided that is unique for each account. Encryption keys and certificate information could be supplied by still another profile, stored on a separate server. Whenever a resync operation is due, the IP Telephony Device evaluates the four Profile_Rule* parameters in sequence: 1. Profile_Rule 2. Profile_Rule_B Cisco Small Business IP Telephony Devices Provisioning Guide 53

  • 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
53
2
In this example, the IP Telephony Device periodically resyncs every two hours. In
case of a resync failure, the device retries in 30 minutes, then again in 1 more hour,
then after two more hours, and then after four more hours, continuing at four-hour
intervals until it successfully resyncs.
The following is another example:
Resync_Periodic
=
3600+600
Resync_Error_Retry_Delay
=
1800+300,3600+600,7200+900
In this example, the device periodically resyncs every hour (plus an additional
random delay of up to 10 minutes). In case of resync failure, the device retries in 30
minutes (plus up to five minutes more).
If it fails again, it waits an additional hour (plus up to 10 minutes). If again
unsuccessful, it waits two more hours (plus up to 15 minutes), and so also
thereafter, until it successfully resyncs.
The following is another example:
Upgrade_Error_Retry_Delay
=
1800,3600,7200,14400+3600
In this example, if a remote upgrade attempt fails, the device retries the upgrade in
30 minutes, then again after one more hour, then in two hours. If it still fails, it
subsequently retries every four to five hours, until it succeeds.
Profile Rules
The IP Telephony Device provides multiple remote configuration profile
parameters (Profile_Rule*). This means that each resync operation can retrieve
multiple files, potentially managed by different servers.
In the simplest scenario, the device resyncs periodically to a single profile on a
central server, which updates all pertinent internal parameters. Alternatively, the
profile can be split between different files. One file is common for all the IP
Telephony Devices in a deployment, while a separate file is provided that is unique
for each account. Encryption keys and certificate information could be supplied by
still another profile, stored on a separate server.
Whenever a resync operation is due, the IP Telephony Device evaluates the four
Profile_Rule* parameters in sequence:
1.
Profile_Rule
2.
Profile_Rule_B