Cisco Unified Communications Manager Express System Administrator Guide - Creating Phone Configurations Using Extension Assigner [Cisco Unified Communications Manager Express]

Table Of Contents

Creating Phone Configurations Using Extension Assigner

Contents

Prerequisites for Extension Assigner

Restrictions for Extension Assigner

Information About Extension Assigner

Extension Assigner Overview

Procedures for System Administrators

Procedures for Installation Technicians

Files Included in this Release

Extension Assigner Synchronization

SCCP: How to Configure Extension Assigner

Configuring Extension Assigner

Determining Which Extension Numbers to Assign to the New Phones and Plan Your Configuration

Downloading the Tcl Script

Configuring the Tcl Script

Specifying the Extension for Accessing Extension Assigner Application

Configuring Provision-Tags for the Extension Assigner Feature

Configuring Temporary Extension Numbers for Phones That Use Extension Assigner

Configuring Extension Numbers That Installation Technicians Can Assign to Phones

Configuring Ephones with Temporary MAC Addresses

Configuring the Router to Automatically Save Your Configuration

Provide the Installation Technician with the Required Information

Configuring Extension Assigner Synchronization

Configuring the XML Interface for the Secondary Backup Router

Configuring Extension Assigner Synchronization on the Primary Router

Assigning Extension Numbers Onsite by Using Extension Assigner

Assigning New Extension Numbers

Unassigning an Extension Number

Reassigning the Current Extension Number

Verifying Extension Assigner

Configuration Examples for Extension Assigner

Extension Assigner: Example

Extension Assigner Synchronization: Example

Additional References

Related Documents

Technical Assistance

Feature Information for Extension Assigner

Creating Phone Configurations Using Extension Assigner

Last Updated: January 9, 2008

This chapter describes the Extension Assigner feature in Cisco Unified Communications Manager Express (Cisco Unified CME).

Finding Feature Information in This Module

Your Cisco Unified CME version may not support the feature documented in this module. For a list of the versions in which this feature is supported, see the "Feature Information for Extension Assigner" section.

Contents

•Prerequisites for Extension Assigner

•Restrictions for Extension Assigner

•Information About Extension Assigner

•SCCP: How to Configure Extension Assigner

•Configuration Examples for Extension Assigner

•Additional References

•Feature Information for Extension Assigner

Prerequisites for Extension Assigner

•Cisco Unified CME 4.0(3) or a later version.

•For Extension Assigner Synchronization, Cisco Unified CME 4.2(1) or a later version.

•The auto-register-phone command must be enabled (default).

•DHCP must be configured. For configuration information, see the "Defining Network Parameters" section on page 77.

•You have a valid Cisco.com account.

•You have access to a TFTP server for downloading files.

Restrictions for Extension Assigner

•The number of phones that you install cannot exceed the maximum number of phones supported by the router chassis. To find the maximum number of phones for a particular router and Cisco Unified CME version, see the appropriate Cisco Unified CME Supported Firmware, Platforms, Memory, and Voice Products for your Cisco IOS release.

•This feature is not supported for SIP endpoints in Cisco Unified CME.

•For Extension Assigner Synchronization, automatic synchronization only applies to configuration changes made by Cisco Unified CME Extension Assigner.

Information About Extension Assigner

To use extension assigner, you should understand the following concepts:

•Extension Assigner Overview

•Files Included in this Release

•Extension Assigner Synchronization

Extension Assigner Overview

This feature enables installation technicians to assign extension numbers to Cisco Unified CME phones without administrative access to the server, typically during the installation of new phones or the replacement of broken phones. However, before an installation technician can use this feature, the system administrator must first configure Cisco Unified CME to allow specific extensions to be assigned. The system administrator must also provide the installation technician with the information necessary for assigning extension numbers to phones. The installation technician can then assign extension numbers to phones with access to only the phones themselves and with no further intervention from the administrator.

To configure this feature, tasks must be performed on the Cisco router by an administrator and onsite by installation technicians. .

Procedures for System Administrators

Before an installation technician can assign new extension numbers to phones, you must complete the following tasks:

1. Determine which extension numbers will be assigned to the new phones and plan your configuration.

2. Download the appropriate Tcl script and associated audio prompt files and place them in the correct directory.

3. 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.

–Configure ephone-dns with the extension numbers that the installation technician can assign to phones.

–Configure ephones 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.

4. 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 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 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 number.

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 or a similar new tag called the provision-tag.

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.

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
If you decide to use the ephone tag, it will require less configuration. However, the installation technician will enter 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.

You do not have to configure any ephone entries for the extension number that are randomly assigned. The autoassign feature automatically creates an ephone entry for each new phone when it registers. The autoassign 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 configurations have the actual MAC address of the phone and a button with the first available ephone-dn designated for the autoassign feature.

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 autoregister feature is deleted. The number of ephone-dns that you configure for the autoassign 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 autoassign 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.

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 for each extension number that you want the installation technician to assign to a phone.

•Configure an ephone 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 more information, see the "Configuring Ephones with Temporary MAC Addresses" section.

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

Because you must configure two ephone-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 setting determines how many phones you can plug in at one time. For example, if your max-ephone setting is ten more than the number of phones to which you want to assign extension numbers, the 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 and ephone-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.

Procedures for Installation Technicians

This feature is implemented using a Tcl script and audio prompt files that enable the installation technician to assign an extension number to a new Cisco Unified CME phone by performing the following procedure The system administrator provides the installation technician with all of the information required to perform this procedure.

Step 1 Plug in a specified number of new phones.

Step 2 Wait for the phones to be assigned temporary, random extension numbers.

Step 3 Dial a specified number to access the extension assigner application.

Step 4 Enter a specified password.

Step 5 Enter a tag that identifies an extension number and enables the installation technician to perform one of the following tasks:

•Assign a new extension number to a phone.

•Unassign the current extension number.

•Reassign an extension number.

Files Included in this Release

The app-cme-ea-2.0.0.0.tar or later archive file provided for the extension assigner feature includes a readme file, a Tcl script, and several audio prompt files. If you want to replace the audio files with files that use a language other than English, do not change the name of the files. The Tcl script is written to use only the following list of the filenames:

•app-cme-ea-2.0.0.0.tcl (script)

•en_cme_tag_assign_phone.au (audio file)

•en_cme_tag_assigned_to_phone.au (audio file)

•en_cme_tag_assigned_to_phone_idle.au (audio file)

•en_cme_tag_assigned_to_phone_inuse.au (audio file)

•en_cme_tag_assigned_to_phone_unreg.au (audio file)

•en_cme_tag_available.au (audio file)

•en_cme_tag_extension.au (audio file)

•en_cme_tag_invalid.au (audio file)

•en_cme_tag_unassign_phone.au (audio file)

•en_cme_tag_action_cancelled.au (audio file)

•en_cme_tag_assign_failed.au (audio file)

•en_cme_tag_assign_success.au (audio file)

•en_cme_tag_contact_admin.au (audio file)

•en_cme_tag_disconnect.au (audio file)

•en_cme_tag_ephone_tagid.au (audio file)

•en_cme_tag_invalid_password.au (audio file)

•en_cme_tag_invalidoption.au (audio file)

•en_cme_tag_noentry.au (audio file)

•en_cme_tag_password.au (audio file)

•en_cme_tag_unassign_failed.au (audio file)

•en_cme_tag_unassign_success.au (audio file)

•en_eight.au (audio file)

•en_five.au (audio file)

•en_four.au (audio file)

•en_nine.au (audio file)

•en_one.au (audio file)

•en_seven.au (audio file)

•en_six.au (audio file)

•en_three.au (audio file)

•en_two.au (audio file)

•en_zero.au (audio file)

•readme.txt

Extension Assigner Synchronization

Extension Assigner Synchronization enables the secondary backup router to automatically receive any changes made by Extension Assigner to ephone mac-addresses in the primary router. The synchronization is performed using the Cisco Unified CME XML interface. The Cisco Unified CME XML client encapsulates the configuration changes into an ISexecCLI request and sends it to the secondary backup router using HTTP. The server on the secondary backup side processes the incoming XML request and calls the Cisco IOS CLI parser to perform the updates.

For configuration information, see the "Configuring Extension Assigner Synchronization" section.

SCCP: How to Configure Extension Assigner

This section contains the following tasks:

•Configuring Extension Assigner (required)

•Configuring Extension Assigner Synchronization (optional)

•Assigning Extension Numbers Onsite by Using Extension Assigner (required)

Configuring Extension Assigner

The following tasks are performed by an administrator or other personnel who is responsible for configuring Extension Assigner:

•Determining Which Extension Numbers to Assign to the New Phones and Plan Your Configuration

•Downloading the Tcl Script

•Configuring the Tcl Script

•Specifying the Extension for Accessing Extension Assigner Application

•Configuring Provision-Tags for the Extension Assigner Feature

•Configuring Temporary Extension Numbers for Phones That Use Extension Assigner

•Configuring Extension Numbers That Installation Technicians Can Assign to Phones

•Configuring Ephones with Temporary MAC Addresses

•Configuring the Router to Automatically Save Your Configuration

•Provide the Installation Technician with the Required Information

Determining Which Extension Numbers to Assign to the New Phones and Plan Your Configuration

After you determine which extension number to assign to each phone, 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.

•Whether to use ephone-tag or the provision-tag number to identify the extension number to assign to the phone.

•How many temporary extension numbers to configure. This will determine how many temporary ephone-dns and temporary MAC addresses to configure.

•What specific tag numbers to use to identify the extension number to assign to the phone.

Downloading the Tcl Script

To download the Tcl script and audio prompt files for the extension assigner feature, perform the following steps.

For more information about how to use Tcl scripts, see the Cisco IOS Tcl IVR and Voice XML Application Guide for your Cisco IOS release.

Note Do not edit the Tcl script

SUMMARY STEPS

1. Go to the Cisco Unified CME software download website at http://www.cisco.com/pcgi-bin/tablebuild.pl/ip-iostsp.

2. Download the Cisco Unified CME extension assigner tar archive to a TFTP server or to the Cisco Unified CME system's flash memory.

3. enable

4. archive tar /xtract source-url destination-url

DETAILED STEPS

Command or Action

Purpose

Step 1

Go to the Cisco Unified CME software download website at http://www.cisco.com/pcgi-bin/tablebuild.pl/ip-iosts.

Gives you access to Cisco Unified CME software downloads.

Step 2

Download the Cisco Unified CME extension assigner tar archive to a TFTP server that is accessible to the Cisco Unified CME router.

Downloads the Cisco Unified CME extension assigner tar archive to a TFTP server that is accessible to the Cisco Unified CME router.

•This tar archive contains the extension assigner Tcl script and the default audio files that you need for the extension assigner service.

Step 3

enable
Example:

Router# enable

Enters global configuration mode.

Step 4

archive tar /xtract source-url destination-url
Example:

Router# archive tar /xtract tftp://192.168.1.1/app-cme-ea-2.0.0.0.tar flash:

Uncompresses the files in the archive file and copies them to a location that is accessible by the Cisco Unified CME router.

•source-url—URL of the source of the extension assigner TAR file. Valid URLs can refer to TFTP or HTTP servers or to flash memory.

•location—URL of the destination of the extension assigner TAR file, including its Tcl script and audio files. Valid URLs can refer to TFTP or HTTP servers or to flash memory.

Configuring the Tcl Script

To configure and load the Tcl script for the extension assigner feature and create the password that installation technicians enter to access the extension assigner application, perform the following steps.

For more information about how to use Tcl scripts, se the Cisco IOS Tcl IVR and Voice XML Application Guide for your Cisco IOS release.

Note To change the password, you must remove the existing extension assigner service and create a new service that defines a new password.

SUMMARY STEPS

1. enable

2. configure terminal

3. application

4. service service-name location

5. param ea-password password

6. paramspace english index number

7. paramspace english language en

8. paramspace english location location

9. paramspace english prefix en

10. end

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

application
Example:

Router(config)# application

Enters application configuration mode to configure packages and services.

Step 4

service service-name location
Example:

Router(config-app)# service EA tftp://10.1.1.100/app-cme-ea-2.0.0.0.tcl

Enters service parameter configuration mode to configure parameters for the call-queue service.

•service-name—Name of the extension assigner service. This arbitrary name is used to identify the service during configuration tasks.

•location—URL of the Tcl script for the extension assigner service. Valid URLs can refer to TFTP or HTTP servers or to flash memory.

Step 5

param ea-password password
Example:

Router(config-app-param)# param ea-password 1234

Sets the password that installation technicians enter to access the extension assigner application.

•password—Numerical password that installation technicians enter to access the extension assigner application. Length: 2 to 10 digits.

Step 6

paramspace english index number
Example:

Router(config-app-param)# paramspace english index 0

Defines the category of audio files that are used for dynamic prompts by an IVR application.

•For Extension Assigner, language must be English.

•number—Category group of the audio files (from 0 to 4). For example, audio files representing the days and months can be category 1, audio files representing units of currency can be category 2, and audio files representing units of time—seconds, minutes, and hours—can be category 3. Range is from 0 to 4; 0 means all categories.

Step 7

paramspace english language en
Example:

Router(config-app-param)# paramspace english language en

Defines the language of audio files that are used for dynamic prompts by an IVR application.

•For the Extension Assigner, language must be English and prefix is en.

Step 8

paramspace english location location
Example:

Router(config-app-param)# paramspace english location tftp://10.1.1.100/app-cme-ea-2.0.0.0.tcl

Defines the location of audio files that are used for dynamic prompts by an IVR application.

•For the Extension Assigner, language must be English.

•location—URL of the Tcl script for the extension assigner service. Valid URLs can refer to TFTP or HTTP servers or to flash memory.

Step 9

paramspace english prefix en
Example:

Router(config-app-param)# paramspace english prefix en

Defines the prefix of audio files that are used for dynamic prompts by an IVR application.

•For the Extension Assigner, language must be English and prefix is en.

Step 10

end
Example:

Router(config-app-param)# end

Returns to privileged EXEC mode.

Specifying the Extension for Accessing Extension Assigner Application

To specify the extension number that installation technicians must dial to access the extension assigner application during onsite installation, perform the following steps.

SUMMARY STEPS

1. enable

2. configure terminal

3. dial-peer voice tag voip

4. service service-name outbound

5. destination-pattern string

6. session target ipv4:destination-address

7. dtmf-relay h245-alphanumeric

8. codec g711ulaw

9. no vad

10. end

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

dial-peer voice tag voip
Example:

Router(config)# dial-peer voice 5999 voip

Enters dial-peer configuration mode.

•tag—Number used during configuration tasks to identify this dial peer.

Step 4

service service-name outbound
Example:

Router(config-dial-peer)# service EA outbound

Loads and configures the extension assigner application on a dial peer.

•service-name—Name must match the name that you used to load the extension assigner Tcl script in the "Configuring the Tcl Script" section.

•outbound—Required for Extension Assigner.

Step 5

destination-pattern string
Example:

Router(config-dial-peer)# destination pattern 5999

Specifies either the prefix or the full E.164 telephone number (depending on the dial plan) for a dial peer.

•string—Number that the installation technician calls when assigning an extension number to a phone.

Step 6

session target ipv4:destination-address
Example:

Router(config-dial-peer)# session target ipv4:172.16.200.200

Designates a network-specific address to receive calls from a VoIP dial peer.

•destination—IP address for the Cisco Unified CME interface on this router.

Step 7

dtmf-relay h245-alphanumeric
Example:

Router(config-dial-peer)# dtmf-relay h245-alphanumeric

Specifies the H.245 alphanumeric method for relaying dual tone multifrequency (DTMF) tones between telephony interfaces and an H.323 network.

Step 8

codec codec
Example:

Router(config-dial-peer)# codec g711ulaw

Specifies the voice coder rate of speech for a dial peer.

•codec—Option that represents the correct voice decoder rate.

Step 9

no vad
Example:

Router(config-dial-peer)# no vad

Disables voice activity detection (VAD) for the calls using a particular dial peer.

•Required fro Extension Assigner.

Step 10

end
Example:

Router(config-dial-peer)# end

Returns to privileged EXEC mode.

Configuring Provision-Tags for the Extension Assigner Feature

To modify Extension Assigner to use provision-tags, perform the following steps. By default, the extension assigner is enabled and uses ephone tags.

SUMMARY STEPS

1. enable

2. configure terminal

3. telephony-service

4. extension-assigner tag-type {ephone-tag | provision-tag}

5. end

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

telephony-service
Example:

Router(config)# telephony-service

Enters telephony-service configuration mode.

Step 4

extension-assigner tag-type {ephone-tag | provision-tag}
Example:

Router(config-telephony)# extension-assigner tag-type provision-tag

Specifies tag type to use to identify extension numbers for Extension Assigner.

•ephone-tag—Specifies that extension assigner use the ephone tag to identify the extension number that is assigned to a phone. The installation technician enters this number to assign an extension number to a phone.

•provision-tag—Specifies that extension assigner use the provision-tag to identify the extension number that is assigned to a phone. The installation technician enters this number to assign an extension number to a phone.

Step 5

end
Example:

Router(config-telephony)# end

Returns to privileged EXEC mode.

Configuring Temporary Extension Numbers for Phones That Use Extension Assigner

To create ephone-dsn to use as a temporary extension numbers for phones to which an extension number will be assigned by Extension Assigner, perform the following steps for each temporary number to be created.

Tip The readme file that is included with the script contains some sample entries for this procedure that you can edit to fit your needs.

SUMMARY STEPS

1. enable

2. configure terminal

3. ephone-dn dn-tag [dual-line]

4. number number [secondary number] [no-reg [both | primary]]

5. trunk digit-string [timeout seconds]

6. name name

7. exit

8. telephony-service

9. auto assign dn-tag to dn-tag

10. end

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

ephone-dn dn-tag [dual-line]
Example:

Router(config)# ephone-dn 90

Enters ephone-dn configuration mode, creates an ephone-dn, and optionally assigns it dual-line status.

Note We recommend that you use single-line mode for your temporary extension numbers.

Step 4

number number [secondary number] [no-reg [both | primary]]
Example:

Router(config-ephone-dn)# number 9000

Configures a valid extension number for this ephone-dn instance.

Step 5

trunk digit-string [timeout seconds]
Example:

Router(config-ephone-dn)# trunk 5999

(Optional) Configures extension number to be automatically dialed for accessing the extension assigner application.

•digit-string—Must match the number that you configured in the "Specifying the Extension for Accessing Extension Assigner Application" section.

Step 6

name name
Example:

Router(config-ephone-dn)# name hardware

(Optional) Associates a name with this ephone-dn instance. This name is used for caller-ID displays and in the local directory listings.

•Must follow the name order that is specified with the directory command.

Step 7

exit
Example:

Router(config-ephone-dn)# exit

Exits ephone-dn configuration mode

Step 8

telephony-service
Example:

Router(config)# telephony-service

Enters telephony-service configuration mode.

Step 9

auto assign dn-tag to dn-tag
Example:

Router(config-telephony)# auto assign 90 to 99

Automatically assigns ephone-dn tags to Cisco Unified IP phones as they register for service with a Cisco Unified CME router.

•Must match the tags that you configured in earlier step.

Step 10

end
Example:

Router(config-telephony)# end

Returns to privileged EXEC mode.

Configuring Extension Numbers That Installation Technicians Can Assign to Phones

To create ephone-dns for an extension numbers that the installation technicians can assign to phones, perform the following steps for each directory number to be created.

Tip The readme file provided with this feature contains sample entries that you can edit to fit your needs.

SUMMARY STEPS

1. enable

2. configure terminal

3. ephone-dn dn-tag [dual-line]

4. number number [secondary number] [no-reg [both | primary]]

5. name name

6. end

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

ephone-dn dn-tag [dual-line]
Example:

Router(config)# ephone-dn 20

Enters ephone-dn configuration mode, creates an ephone-dn, and optionally assigns it dual-line status.

Note To change an ephone-dn from dual-line to single-line mode or the reverse, first delete the ephone-dn and then recreate it.

Step 4

number number [secondary number] [no-reg [both | primary]]
Example:

Router(config-ephone-dn)# number 20

Configures a valid extension number for this ephone-dn instance.

Step 5

name name
Example:

Router(config-ephone-dn)# name hardware

(Optional) Associates a name with this ephone-dn instance. This name is used for caller-ID displays and in the local directory listings.

•Must follow the name order that is specified with the directory command.

Step 6

end
Example:

Router(config-ephone-dn)# end

Returns to privileged EXEC mode.

Configuring Ephones with Temporary MAC Addresses

To create an ephone configuration with temporary a MAC address for a Cisco Unified CME phone to which you want the installation technician to assign extension numbers, perform the following steps for each phone.

Prerequisites

•The max-ephone command must be configured for a value equal to at least one greater than the number of phones to which you want to assign extension numbers to allow the autoregister feature to automatically create at least one ephone for your temporary extension numbers.

Note You are permitted to set the max-ephone value higher than the number of users supported by your Cisco Unified CME licenses for the purpose of enrolling licensed phones using Extension Assigner.

Restrictions

•Max-ephone setting determines how many phones you can plug in at one time. For example, if your max-ephone setting is ten more than the number of phones to which you want to assign extension numbers, the 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.

•For Cisco VG224 analog voice gateways with extension assigner, a minimum of 24 temporary ephones is required.

Tip The readme file provided with this feature contains some sample entries for this procedure that you can edit to fit your needs.

SUMMARY STEPS

1. enable

2. configure terminal

3. ephone phone-tag

4.