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

Remote Endpoint Control, Communication Encryption, Provisioning Cisco Small Business VoIP Devices - nat

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

Provisioning Cisco Small Business VoIP Devices Residential Deployment Provisioning Requirements 1 Device configuration varies according to the individual customer and with the same customer over a period of time. The IP Telephony Device must be configured to match the account service parameters for the individual customer. Also, the configuration may need to be modified because of new service provider features, modifications in the service provider network, or firmware upgrades in the endpoint. This customized, ongoing configuration is supported by the following features: • Reliable remote control of the endpoint • Encryption of the communication controlling the endpoint • Streamlined endpoint account binding Remote Endpoint Control The service provider must be able to modify the configuration parameters in the IP Telephony Device after the unit has been deployed to the customer premises. The service provider must also be able to upgrade the firmware remotely, and both of these operations must be reliable. In a residential deployment, the end IP Telephony Device is typically connected to a local network. The device accesses the Internet through a router using network address translation (NAT). For enhanced security, the router may attempt to block unauthorized incoming packets by implementing symmetric NAT, a packet filtering strategy which severely restricts the packets that are allowed to enter the protected network from the Internet. Communication Encryption The configuration parameters communicated to the IP Telephony Device may contain authorization codes or other information that need to be protected from unauthorized access. It is in the service provider's interest to prevent unauthorized activity by the customer, and in the customer's interest to prevent from unauthorized use of the account by other persons. For this reason, the service provider may wish to encrypt the configuration profile communication between the provisioning server and the IP Telephony Device, in addition to restricting access to the administration web server for the device. Cisco Small Business IP Telephony Devices Provisioning Guide 11

  • 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 Cisco Small Business VoIP Devices
Residential Deployment Provisioning Requirements
Cisco Small Business IP Telephony Devices Provisioning Guide
11
1
Device configuration varies according to the individual customer and with the
same customer over a period of time. The IP Telephony Device must be
configured to match the account service parameters for the individual customer.
Also, the configuration may need to be modified because of new service provider
features, modifications in the service provider network, or firmware upgrades in
the endpoint.
This customized, ongoing configuration is supported by the following features:
•
Reliable remote control of the endpoint
•
Encryption of the communication controlling the endpoint
•
Streamlined endpoint account binding
Remote Endpoint Control
The service provider must be able to modify the configuration parameters in the IP
Telephony Device after the unit has been deployed to the customer premises. The
service provider must also be able to upgrade the firmware remotely, and both of
these operations must be reliable.
In a residential deployment, the end IP Telephony Device is typically connected to
a local network. The device accesses the Internet through a router using network
address translation (NAT). For enhanced security, the router may attempt to block
unauthorized incoming packets by implementing symmetric NAT, a packet filtering
strategy which severely restricts the packets that are allowed to enter the
protected network from the Internet.
Communication Encryption
The configuration parameters communicated to the IP Telephony Device may
contain authorization codes or other information that need to be protected from
unauthorized access. It is in the service provider’s interest to prevent unauthorized
activity by the customer, and in the customer’s interest to prevent from
unauthorized use of the account by other persons. For this reason, the service
provider may wish to encrypt the configuration profile communication between
the provisioning server and the IP Telephony Device, in addition to restricting
access to the administration web server for the device.