Before an
installation technician can assign new extension numbers to phones, you must
complete the following tasks:
- Determine which extension
numbers will be assigned to the new phones and plan your configuration.
- Download the appropriate
Tcl script and associated audio prompt files and place them in the correct
directory.
- Configure the Cisco
Unified CME router to:
- Configure and load the
appropriate Tcl script.
- Specify the extension that
the installation technician calls to assign extension numbers.
- Optionally specify whether
the extension used to assign extension numbers is dialed automatically.
- Specify the password that
the installation technician enters to assign extension numbers.
- Configure the extension
assigner feature.
- Configure ephone-dns with
temporary extension numbers (applicable only for SCCP phones).
- Configure ephone-dns and
voice register dns with the extension numbers that the installation technician
can assign to phones.
- Configure ephones and voice
register pools with temporary MAC addresses for each phone that will be
assigned an extension number by the installation technician.
- Optionally configure the
router to automatically save your configuration.
Note
|
All
phone configurations such as dn and pool that are generated as part of the auto
registration process are persistent configurations(If the command
background save
interval is configured under telephony-service). These phone
configurations are available on Unified CME even after an event of router
reload.
|
- Provide the installation
technician with the information needed to assign extension numbers to the new
phones.
Before you can
configure this feature, you must understand how the extension assigner
application works and what information the installation technician needs to
assign extension numbers to phones.
Other information
you must provide to the installation technician involves the tasks that the
installation technician must perform. These tasks include:
- Dialing a configurable
extension number to access the extension assigner application.
- Entering a configurable
password.
- Entering a tag
(provision-tag for SIP phones, and ephone-tag or provision-tag for SCCP phones)
that identifies the extension number that will be assigned to the phone.
Therefore, you must
make the following decisions:
- Which extension number must
be dialed to access the extension assigner application.
- Whether the number is
dialed automatically when a phone goes off hook.
- What password the
installation technician must enter to access the extension assigner
application.
- What type of tag
(provision-tag for SIP phones, and ephone-tag or provision-tag for SCCP phones)
numbers to use to identify the extension number to assign to the phone.
- What specific tag numbers
to use to identify the extension number to assign to the phone.
The first three
decisions are straightforward, but the last two tag number decisions require
some knowledge of how the extension assigner feature works.
This feature is
implemented using a Tcl script and audio files. To run this script, the
installation technician plugs in the phone, waits for a random extension number
to be automatically assigned, and dials a specified extension assigner number
to invoke the extension assigner service.
After the phones
have registered and received their temporary extension numbers, the
installation technician can access extension assigner and enter a tag number.
This tag number is used to identify the extension number and must match either
an ephone tag (only for SCCP phones) or a similar new tag called the
provision-tag (applicable to both SIP and SCCP phones).
For SCCP phones, you
must decide on which tag you want to use before you configure your ephone and
ephone-dn entries.
The advantage of
using the provision-tag is that you can make it easier for the installation
technician to assign extension numbers because you can configure the tag to
match the primary extension number or some other unique identifier for the
phone, such as a jack number. We recommend you to configure provision-tag same
as the primary extension number.
The disadvantage is
that you configure an additional keyword for each ephone entry, as shown in the
following example:
ephone 1
provision-tag 9001
mac-address 02EA.EAEA.0001
button 1:1
voice register pool 1
provision-tag 1001
mac-address 02EA.EAEA.0001
number 1 dn 101
For SCCP phones, if
you decide to use the ephone tag, it requires less configuration. However, the
installation technician enters an arbitrary tag number instead of the actual
extension number when configuring a phone. This restriction is because the
number of ephone tags that you can configure is limited by your license. For
example, if you use the ephone tag and you have a 100-user license, the
installation technician cannot enter 9001 for the tag because you can configure
only ephone 1 to ephone 100.
Note that each
ephone entry that you configure must also include a temporary MAC address. As
shown in the above example, this address should begin with 02EA.EAEA and can
end with any unique number. We strongly recommend that you can configure this
unique number to match the ephone tag for SCCP phones.
For SCCP phones, you
do not have to configure any ephone entries for the extension number that are
randomly assigned. The auto assign feature automatically creates an ephone
entry for each new phone when it registers. The auto assign feature then
automatically assigns an ephone-dn entry if there is an available ephone-dn
that has one of the tag numbers specified by the
auto assign
command. The resulting ephone pool configurations have the actual MAC address
of the phone and a button with the first available ephone-dn designated for the
auto assign feature. For more information, see
Configure Temporary Extension Numbers for SCCP Phones That Use Extension Assigner.
For SIP phones, you
do not have to configure voice register pool or voice register dn. You need to
configure auto-register command for automatic registration of SIP phones on
Cisco Unified CME. For more information, see
Configure Temporary Extension Numbers for SCCP Phones That Use Extension Assigner.
Note
|
For manually
registered phones, ephone (or voice register pool) and ephone-dn (or voice
register dn) are manually created.
|
As shown in the
following example, you configure at least one ephone-dn for a temporary
extension and specify which ephone-dns the autoassign feature will assign to
the temporary ephone entries:
telephony-service
auto assign 101 to 105
ephone-dn 101
number 0001
When the
installation technician assigns an extension number to a phone, the temporary
MAC address is replaced by the actual MAC address and the ephone entry created
by the auto register feature is deleted. The number of ephone-dns that you
configure for the auto assign feature determines how many phones you can plug
in at one time and get an automatically assigned extension. If you define four
ephone-dns for auto assign and you plug in five phones, one phone will not get
a temporary extension number until you assign an extension to one of the other
four phones and reset the fifth phone. You are permitted to set the max-ephone
value higher than the number of users and phones supported by your Cisco
Unified CME phone licenses for the purpose of enrolling licensed phones using
Extension Assigner.
In addition to
configuring one ephone-dn for each temporary extension number that is assigned
automatically, you also must configure an ephone-dn entry for each extension
number that is assigned by the installation technician. For more details on
configuring extension numbers that technicians can assign to SCCP phones, see
Configure Extension Numbers That Installation Technicians Can Assign to SCCP Phones.
For SIP Phones, the
temporary MAC address is replaced by the actual MAC address and voice register
pool entry created by the auto-register feature is deleted when the
installation technician assigns an extension number to a phone. The number of
voice register dns that you configure for the auto assign feature determines
how many phones you can plug in at one time and get an automatically assigned
extension. If you define four voice register dns for auto assign and you plug
in five phones, one phone will not get a temporary extension number until you
assign an extension to one of the other four phones and reset the fifth phone.
You are permitted to set the max-pool value higher than the number of users and
phones supported by your Cisco Unified CME phone licenses for the purpose of
enrolling licensed phones using Extension Assigner. For more details on
configuring extension numbers that technicians can assign to SIP phones, see
Configure Extension Numbers That Installation Technicians Can Assign to SIP Phones.
Note
|
For SIP Phones,
you need not create temporary dn if auto registration is used.
|
To complete the
configuration, as shown in the following example, you must:
- Specify whether to use the
ephone or the provision-tag number to identify the extension number to assign
to the phone. Set this when the feature is enabled with the new
extension-assigner tag-type
command provided with this feature.
- Configure an ephone-dn for
each temporary extension number that is assigned automatically.
- Configure an ephone-dn or
voice register dn for each extension number that you want the installation
technician to assign to a phone.
- Configure an ephone or
voice register pool with a temporary MAC address for each phone that is
assigned an extension number by the installation technician. Optionally, this
ephone definition can include the new provision-tag. For SIP phones, it is
necessary to have provision-tag information under voice register pool. For more
information, see
Configure Ephones with Temporary MAC Addresses.
telephony-service
extension-assigner tag-type provision-tag
auto assign 101 to 105
ephone-dn 1 dual-line
number 6001
ephone-dn 101
number 0001
label Temp-Line-not assigned yet
ephone 1
provision-tag 6001
mac-address 02EA.EAEA.0001
button 1:1
***********************************
voice register pool 1
provision-tag 1001
mac-address 02EA.EAEA.0001
number 1 dn 101
Because you must
configure two ephone-dns or voice register dns for each extension number that
you want to assign, you may exceed your max-dn setting. You are permitted to
set the max-dn value higher than the number allowed by your license for the
purpose of enrolling licensed phones using extension assigner.
Assuming that your
max-dn setting is set high enough, your max-ephone or max-pool setting
determines how many phones you can plug in at one time. For example, if your
max-ephone or max-pool setting is ten more than the number of phones to which
you want to assign extension numbers, then you can plug in ten phones at a
time. If you plug in eleven phones, one phone will not register or get a
temporary extension number until you assign an extension to one of the first
ten phones and reset the eleventh phone.
After you have
configured your ephone or voice register pool, and ephone-dn or voice register
dn entries, you can complete your router configuration by optionally
configuring the router to automatically save your configuration. If the router
configuration is not saved, any extension assignments made by the installation
technician will be lost when the router is restarted. The alternative to this
optional procedure is to have the installation technician connect to the router
and enter the
write memory
command to save the router configuration.
The final task of
the system administrator is to document the information that the installation
technician needs to assign extension numbers to the new phones. You can also
use this documentation as a guide when you configure Cisco Unified CME to
implement this feature. This information includes:
- How many phones the
installation technician can plug in at one time
- Which extension number to
dial to access the extension assigner application
- Whether the number is
dialed automatically when a phone goes off hook
- What password to enter to
access the application
- Which tag numbers to enter
to assign an extension to each phone
Note
|
Because this
feature is implemented using a Tcl script and audio files, you must place the
script and associated audio prompt files in the correct directory. Do not edit
this script; just configure Cisco Unified CME to load the appropriate script.
|
Feedback