Filter
Top Products
12-11
Cisco Broadband Access Center 3.8 Administrator Guide
OL-27172-01
Chapter 12 Configuring CWMP Service
Connection Request Service
Configuring Reachability
Reachability plays an important role in configuring connection requests. In earlier versions of Cisco
BAC, connection requests were refused if a device's reported IP address and its source IP address did not
match. This was because this implies that the device used the NAT standard, and therefore, configuration
requests did not normally succeed. You could change this behavior from the administrator user interface
or the API.
Cisco BAC supports a new standalone STUN server to handle the UDP connection requests feature. A
UDP based connection request mechanism defined in TR069 Annex G, allows Cisco BAC to initiate a
session with a CPE that is operating behind a NAT gateway. STUN Service can be run on Solaris or
Linux.
By using the API, set the property
IPDeviceKeys.FORCE_ROUTABLE_IP_ADDRESS to true to allow TCP
based connection requests regardless of a mismatch in the device source IP address.
From the administrator user interface:
Step 1 Choose Devices > Manage Devices.
Step 2 Use one of these methods:
• Add a device record. To do this:
Click the Add button. The Add Device page appears.
• Search for a device record. To do this,
a. Specify a Search Type and enter values for the screen components that are unique to the search type
that you select.
A list of devices appears.
b. Click the Identifier link corresponding to the desired device.
The Modify Device page appears.
Step 3 From the Property Value drop-down list, select /IPDevice/forceRouteIPAddress, and set a property
value.
The API constant for /IPDevice/forceRouteIPAddress is
IPDeviceKeys.FORCE_ROUTABLE_IP_ADDRESS.
Step 4 Click Add.
Note You can specify this property anywhere on the device's hierarchy.
Discovering Data from Devices
This section describes the Discovery of Data feature, which you use to retrieve a predefined set of
parameters from the device, and store these parameters in the RDU for future use.
You can use this discovered data to manage device firmware and device configurations by providing
some key attributes of the device and its current configuration. Discovered parameters are updated at the
RDU any time their values change on the device.