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

Proprietary Profile Format

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

Provisioning Tutorial Profile Formats 3 STEP 5 Click Submit All Changes. When the IP Telephony Device resyncs, it receives the XML profile, remaps the elements, as indicated by the alias map, and populates the User_ID_1_ and Password_1_ parameters. STEP 6 View the Line 1 tab to verify the new configuration. NOTE The IP Telephony Device supports alias remapping of a limited number of parameters. It is not meant to rename all parameters in its configuration. Proprietary Profile Format Firmware releases prior to 2.0.6 do not recognize the XML-based profiles described so far in this chapter. Instead, the SIP Profiler Compiler tool (SPC) converts a text-based profile definition into a proprietary binary format understood by earlier versions of the firmware. The tool provides its own options for encrypting the resulting binary profile. The text-based profile understood by SPC uses a different syntax from the XML profile presented earlier. It consists of a list of parameter-value pairs, with the value in double quotes. Other minor syntax and parameter naming differences also apply. The following example specifies values for two Line 1 parameters:. Exercise STEP 1 Obtain the SPC utility from Cisco. Executables are available for the Windows Win32 environment, Linux ELF, and OpenBSD. STEP 2 Generate the text profile account.txt containing the two-line profile shown in the following example: User_ID[1] "17775551234" ; Password[1] "512835907884" ; Cisco Small Business IP Telephony Devices Provisioning Guide 81

  • 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
Provisioning Tutorial
Profile Formats
Cisco Small Business IP Telephony Devices Provisioning Guide
81
3
STEP 5
Click
Submit All Changes
.
When the IP Telephony Device resyncs, it receives the XML profile, remaps the
elements, as indicated by the alias map, and populates the User_ID_1_ and
Password_1_ parameters.
STEP 6
View the Line 1 tab to verify the new configuration.
NOTE
The IP Telephony Device supports alias remapping of a limited number of
parameters. It is not meant to rename all parameters in its configuration.
Proprietary Profile Format
Firmware releases prior to 2.0.6 do not recognize the XML-based profiles
described so far in this chapter. Instead, the SIP Profiler Compiler tool (SPC)
converts a text-based profile definition into a proprietary binary format
understood by earlier versions of the firmware. The tool provides its own options
for encrypting the resulting binary profile.
The text-based profile understood by SPC uses a different syntax from the XML
profile presented earlier. It consists of a list of parameter-value pairs, with the
value in double quotes. Other minor syntax and parameter naming differences also
apply. The following example specifies values for two Line 1 parameters:.
Exercise
STEP 1
Obtain the SPC utility from Cisco.
Executables are available for the Windows Win32 environment, Linux ELF, and
OpenBSD.
STEP 2
Generate the text profile account.txt containing the two-line profile shown in the
following example:
User_ID[1] “17775551234” ;
Password[1] “512835907884” ;