Cisco Cisco Unified Provisioning Manager 8.5 白書

Page 57 of 71

If directory numbers can be random within the entire domain, the directory number pool can be added to each

service area. The directory number allocation in Cisco Unified Provisioning Manager will check whether the

directory number it would be picking out of a block has been used, so the first service area to pick a directory

number will get it and the other service area will then skip it to get the next one. In this design, subscribers get the

next available number in the pool.

You may also allocate directory number blocks based on the calling search spaces setup or how many users are

expected within a service area. In this case, some network planning needs to be done to decide how to allocate

directory numbers. This option may be useful if each service area is to use certain ranges of directory numbers.

For example building 1 is in SA1 and has extensions with 1xxxx, and building 2 is in SA2 and has extensions with

2xxxx.

In either case, you can have multiple directory number blocks per service area to fine-tune how the numbers get

allocated.

Working with TAPS

The Tool for Auto-Registered Phones Support (TAPS) feature is supported on Communications Manager 4.x, 5.x,

and 6.x. So far it is suggested to be used in conjunction with the Bulk Administration Tool (BAT) to provide two

features:

●

Update MAC addresses and download predefined configuration for new phones.

●

Reload configuration for replacement phones.

When new phones are added to Cisco Communications Manager, TAPS works in conjunction with BAT to update

phones that were added to BAT using dummy MAC addresses. After BAT has been use to bulk-add the phones

with dummy MAC addresses to Cisco Communications Manager Administration, one can plug the phones into the

network. The user can dial a TAPS directory number that causes the phone to download its configuration. At the

same time, the phone gets updated in Cisco Communications Manager Administration with the correct MAC

address.

For the first case, instead of using BAT to provision the phones with dummy MAC addresses, Cisco Unified

Provisioning Manager is extended to be able to provision these phones. During phone order entry, a choice box is

presented to the user indicating whether this phone should use a dummy address (only available to users with

advanced assignment role). Possible values are “Y” and “N” (default). When the user chooses “Y”, the MAC

address field will be hidden (and anything previously entered in that field will be cleared) to prevent the user from

entering additional values. During order processing, Cisco Unified Provisioning Manager will generate a dummy

MAC address that is not currently used in the system. The dummy MAC address assigned by Cisco Unified

Provisioning Manager will be an internal MAC address that is not valid in the public domain. Cisco Unified

Provisioning Manager will use a specific prefix for the MAC address (first three octets).

For the second case, if Communications Manager TAPS is configured to “Allow Auto-Registered phones to reset

with any profile”, the user can switch to a new phone simply by using the TAPS feature. Cisco Unified Provisioning

Manager just needs to sync back the changes. If Communications Manager TAPS is configured to “Allow Auto-

Registered phones to reset with a profile with dummy MAC address”, the user can use Cisco Unified Provisioning

Manager to change the MAC address of the existing phone to a dummy MAC address and use the same

procedure to get the physical MAC address of the new phone updated in Communications Manager.