Information Technology Reference
In-Depth Information
example messages include File Not Found:SEP<mac address>.cnf.xml, TFTP Timeout:
SEP<mac address>.cnf.xml, and SEP<mac address>.cnf.xml.
CUCM registration problems:
The TFTP download file contains the IP address of
the CUCM server with which it is supposed to register. Check
Settings
>
Device
Configuration
>
Unified CM Configuration
to verify that the Unified CM IP address
listed is correct. There may be a backup and tertiary server IP listed, depending on
how the cluster is configured. Verify that the Cisco CallManager Service is running
on the server(s) listed; you may also need to verify that autoregistration is correctly
set up (only if you are actually using Autoregistration, of course).
■
If all the previous are verified as correct, there may be a problem with the phone itself;
that type of troubleshooting is beyond the scope of CCNA Voice.
Deleting Unassigned Directory Numbers Using the Route Plan Report
When using Autoregistration, one of the more common issues encountered is that the
phones fail to register, displaying “Error DB Config” or a similar message on the IP Phone
screen. The source of the problem is that the range of Directory Numbers (DNs) allocated
for Autoregistration has been used up; Autoregistration is working, but there are no more
DNs available to assign to the phones. This situation arises because it is normal practice to
change the DN of an autoregistered phone (which is assigned sequentially from the range
defined for Autoregistration) to its “real” production DN. An odd thing happens to the
Autoregistration-assigned DN: It is not released back to the available range, but instead is
marked as “Unassigned” and held in “database limbo.” Unassigned Autoregistration DNs
are not visible unless you go looking for them, so it is not obvious that they are the source
of your problem.
The fix is simple: Either add to the range of Autoregistration DNs, or use the following
steps to “reclaim” them so they can be re-used on newly-registering phones:
1.
Navigate to
System
>
Route Plan Report
.
2.
Set the first filter (the left-most field) to “
Unassigned DNs
.”
3.
Click
Find
.
4.
Delete all of the listed unassigned DNs. This can be done easily by selecting all the
listed DNs using the checkboxes to their left and then clicking
Delete Selected
.
The DNS are now released back to the Autoregistration range as available for assignment.
These steps are also used to “clean up” the database after modifications to your Partitions
design. Another interesting behavior of the CUCM database is that when a DN is assigned
to a different Partition, it still exists in the previous one but is flagged as unassigned.
These unassigned DNs can create confusion, because they
do
appear in lists as selectable
(for example, when building a Line Group)—but they do not function because they are
not assigned to any device.
You should be familiar with using the Route Plan Report to delete unassigned DNs as a
routine maintenance task.
