cme documentation final
DESCRIPTION
qweTRANSCRIPT
CALL MANAGER EXPRESS DOCUMENTATION
Cisco Unified Communications Manager ExpressOverview
Call Manager is a dedicated server or servers that were a custom fit for medium to large businesses deploying thousands of phones at a single site or multiple locations. Although Call Manager (now known as Cisco Unified Communications Manager) provided a cost-effective solution for these larger businesses, the startup price was far beyond the range that was affordable by small businesses.
As the Call Manager product line developed, Cisco released a product known as Survivable Remote Site Telephony (SRST), which allowed a router to act as a failover device for Cisco IP phones if their Call Manager server was unreachable. SRST was so fantastic, Cisco eventually turned it into a standalone solution (rather than just a failover solution) that could support a small office environment. The product was initially named IOS Telephony Service (ITS), which then became Call Manager Express, which then became the Unified Communications Manager Express (CME) product used today.
Contents
PLATFORM LIMITATIONS...........................................................................................................6
IOS SUPPORT....................................................................................................................................7
------IOS versions.................................................................................................................................7
------IOS supporting CME..................................................................................................................7
------Minimum IOS version to support CME....................................................................................7
------Cisco Unified CME and Cisco IOS Software Version Compatibility Matrix.......................7
LICENSING AND MODELS FOR CISCO CME
------Licenses ......................................................................................................................................10
------CME software Files....................................................................................................................10
INSTALLATION OF CME...............................................................................................................11
BASIC LOAD FILES FOR IP PHONES.........................................................................................12
------Sccp firmware format................................................................................................................12
------SIP firmware format.................................................................................................................12
------Types of files................................................................................................................................12
------Flash contents..............................................................................................................................13
ENABLING THE GUI.......................................................................................................................14
------Prerequisites for Enabling the GUI........................................................................................14
------Restrictions for enabling the GUI.............................................................................................14
------Processes for enabling GUI.......................................................................................................14
------Enabling the HTTP Server........................................................................................................15
------Enabling GUI access for system................................................................................................16
------Accessing the Cisco Unified CME GUI....................................................................................16
CONFIGURING THE CISCO UNIFIED CME SYSTEM LEVEL FUNCTIONS....................18
------Maximum Phones and Directory Numbers.............................................................................18
------Firmware load files......................................................................................................................19
------Source IP address information...................................................................................................19
------Generated configuration files.....................................................................................................20
UNDERSTANDING AND CONFIGURING EPHONE-DN’s USING CLI...................................21
------Configuring ephone-dn's.............................................................................................................21
------Creating an ephone......................................................................................................................22
------Associating Ephones and Ephone-DNs......................................................................................23
------Separators used with button Command....................................................................................24
------Naming and labelling of ephones...............................................................................................26
CONFIGURING CME THROUGH GUI.........................................................................................27
CME LAB TOPOLOGY....................................................................................................................28
CONFIGURATIONS..........................................................................................................................29
------Router IOS Upgradation............................................................................................................29
------Router configuration...................................................................................................................30
------Switch configuration...................................................................................................................30
------PC configurations........................................................................................................................30
------IP Phone Configuration..............................................................................................................31
------Enabling the GUI........................................................................................................................31
CONFIGURING FEATURES USING CLI......................................................................................32
------Call forwarding............................................................................................................................32
------Configuring Call Transfer..........................................................................................................32
------Configuring Call Pickup.............................................................................................................33
------Configuring Intercom.................................................................................................................34
------Configuring Paging.....................................................................................................................35
------Configuring After-Hours Call Blocking...................................................................................37
------Configuring normal ring, feature ring and monitoring..........................................................38
------Configuring shared line.............................................................................................................38
------Configuring huntstop................................................................................................................40
------Configuring Overlay..................................................................................................................40
------Configuring overlay with no call waiting.................................................................................41
------Configuring overlay with x separator......................................................................................41
------Configuring call park.................................................................................................................42
------Configuring music on hold........................................................................................................43
------Configuring conferencing..........................................................................................................44
------Configuring Ad hoc conferencing.............................................................................................44
------Configuring Meet-me conferencing..........................................................................................44
RUNNING CONFIGURATION OF ROUTER..............................................................................51RUNNING CONFIGURATION OF SWITCH..............................................................................56
PLATFORM LIMITATIONS
Depending on the platform used, Cisco Unified CME can scale to support an environmentof up to 240 IP phones.
PLATFORM Maximum number of phones
Cisco 1861 Integrated Services Router 8
Cisco IAD2430 Integrated Access Device 24
Cisco 2801 Integrated Services Router 24
Cisco 3250 Ruggedize Services Router 10
Cisco 3270 Ruggedize Services Router 50
Cisco 2811 Integrated Services Router 35
Cisco 2821 Integrated Services Router 50
Cisco 2851 Integrated Services Router 100
Cisco 3725 Multiservice Access Router 144
Cisco 3745 Multiservice Access Router 192
Cisco 3825 Integrated Services Router 175
Cisco 3845 Integrated Services Router 250
IOS SUPPORT
IOS versions
1. IP Base2. IP Voice3. SP Services4. Enterprise Base5. Enterprise Services6. Advanced Security7. Advanced IP services.8. Advanced Enterprise Services
IOS supporting CME
1. IP Voice 2. SP Services 3. Enterprise Services 4. Advanced IP services. 5. Advanced Enterprise Services
Minimum IOS version to support CME – 12.3(4)T
Cisco Unified CME and Cisco IOS Software Version Compatibility Matrix
Cisco IOS Release Cisco Unified CME Version Cisco Unified CME GUI Version
15.0(1)XA 8.0 8.0.0.0
12.4(24)T 7.1 7.1.1.0
12.4(22)YB 7.1 7.1.0.0
12.4(22)T 7.0(1) 7.0.0.1
12.4(20)T1 7.07.0.0.1
Cisco IOS Release Cisco Unified CME Version Cisco Unified CME GUI Version
12.4(20)T 7.0 7.0.0.0
12.4(15)XZ 4.3 4.3.0.0
12.4(15)T7 4.1 - Recommended Version 4.1.0.2
12.4(15)T 4.1 4.1.0.2
12.4(11)XJ 4.14.0.3.0
12.4(11)T 4.0(2) 4.0.3.1.a
12.4(4)XC4 4.0(3) 4.0.3.0
12.4(9)T 4.0(0) 4.0.0.1
12.4(6)T 3.4 3.4.0.1
12.4(4)XC 4.0(1) 4.0.0.0
12.4(4)T 3.4 3.4.0.0
12.4(3) 3.3 3.3.0.3a
12.4(1) 3.3 3.3.0.0a
12.3(14)T 3.3 3.3.0.0
12.3(11)XL 3.2.1 3.2.1.1
12.3(11)T 3.2 3.2.0.0
12.3(8)T3 3.1 3.1.0.1
Cisco IOS Release Cisco Unified CME Version Cisco Unified CME GUI Version
12.3(8)T 3.1 3.1.0.0
12.3(4)T 3.0 N/A
Memory requirement and other specifications of CME versions.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/requirements/guide/33matrix.htm
Licensing and Models for Cisco Unified CME
To legally operate a Cisco Unified CME system, you must purchase three types of licenses:
IOS license: The CME router must be licensed to run a version of Cisco IOS that is capable of supporting the CME software.
Feature license: The feature license (also known as seat license) grants the CME router the ability to support a specific number of IP phones. These licenses are sold in incremental blocks
Phone user licenses: You must purchase one phone user license for each Cisco IP phone supported by the CME system.
CME software is a series of files which includes
Basic files: The core files needed to run CME. This file set includes the firmwarefiles that the Cisco IP phones need to operate.
GUI files: The files required to power the CME web-based management utility.
XML template: The file that dictates the structure of the CME web-based managementutility. Editing this file allows you to create different levels of administrators
MOH file: Audio files used for Music on Hold
Script files: Various Tool Command Language (Tcl) script files to provide moreadvanced functionality to CME (such as auto-attendant and automatic call distributor[ACD] functions).
Miscellaneous files: Additional files that allow you to have custom ring tones or differentbackgrounds on select models of Cisco IP phones.
INSTALLATION
Performing a full installation of the Cisco Unified CME software adds around 150 files tothe flash memory of your router. If you were to download each of these files manuallyand copy them one by one, it could be an all-day process just to get the CME files inplace. To save you some pain, Cisco has introduced the archive command in the IOSsyntax, which allows you to extract a group of files to flash all at once. To perform an installation of the CME files on your router, you must first download the appropriate files from the Cisco website.
For example a GUI file will look like “ cme-gui-4.1.0.2.tar ”, a cme basic file look like “ cme-basic-4.3.0.0.tar.
To install the above mentioned files, obtain the full TAR file from Cisco and place the file on your TFTP server.
Command for installing CME files into flash memory.archive tar /xtract tftp://ip -address/cme-full-4.3.0.0.tar flash:
Basic load files for IP phones
IP phone SCCP load SIP load
7906, 7911 11.8-53s.loads Sip11.8-5-3s.loads
7940, 7960 P00308010200.loads P0s3.8-12-00.loads
7941 Sccp41.8-5-3s.loads Sip41.8-5-3s.loads
IP phone SCCP load SIP load
7942,7962 Sccp42.8-5-3s.loads Sip42.8-5-3s.loads
7961 Sccp41.8-5-3s.loads Sip41.8-5-3s.loads
Sccp firmware format:
P003xxyyzzwwX indicates the major versiony indicates the major sub versionz indicates the maintenance versionw indicates the sub version0 indicates SCCP
SIP firmware format:
P0s3-x-y-zzX indicates the major versiony indicates the minor versionz indicates the sub versions indicates SIP
The cme-basic file comes in zip(called as tar file in ios) format. The tar file should be extracted using the command“ archive tar /xtract tftp://ip -address/cme-full-4.3.0.0.tar flash: “
The zipped file contains
.sbn file – signed binary files supporting image authentication and increased system security
.bin file – unsigned binary file without image authentication
. sb2 file – The signed application image is identified by this extension
.loads file- this contains the application image
0s79xx.txt – It contains universal application header image
CTLSEP mac file: This is the first file requested in the universal application loader. It contains the information about the servers to which the phone is attempting to connect and whether the server connection will be secure or non secure.
XML template file: It contains the XML template for CME
MOH file: The file contains the music on hold.
.zup: This file is used analog telephone adapters.
Flash contents:
The contents in the flash can be displayed using the command “show flash”. For example, the flash contents of 2801 router with cme version 3 are as follows
c2801-spservicesk9-mz.124-3h.binsdmconfig-2801.cfgsdm.tares.tarcommon.tarhome.shtmlhome.tarsecuredesktop-ios-3.1.1.45-k9.pkgSslclient-win-1.1.3.173.pkgcme-full.3.3.0.3a.tarmusiconhold.au
ENABLING THE GUI
Prerequisites for Enabling the GUI:
1. GUI files must be copied into flash memory on the router.
2. To use a phone user account in the Cisco Unified CME GUI to configure speed dials on a
phone that is enabled for Extension Mobility, Cisco Unified CME GUI 4.2.1 or a later version must be installed on the Cisco router. .
Restrictions for enabling the GUI:
Cisco Unified CME GUI files are version-specific; GUI files for one version of Cisco Unified CME are not compatible with any other version of Cisco Unified CME.
Extension Mobility options in Cisco Unified CME GUI 4.2.1 and later versions cannot be accessed from the System Administrator or Customer Administrator login screens.
The password of the system administrator cannot be changed through the GUI. Only the password of a customer administrator or a phone user can be changed through the GUI.
The user name parameter of any authentication credential must be unique.
Do not use the same value for a user name when you configure any two or more authentication credentials in Cisco Unified CME.
The Cisco Unified CME GUI uses HTTP to transfer information from the router to the PC of an administrator or phone user.
The main processes for enabling GUI:
Enabling the HTTP Server (required) Enabling GUI Access for the System Administrator (required)
Accessing the Cisco Unified CME GUI (required)
Creating a Customized XML File for Customer Administrator GUI (optional)
Enabling GUI Access for Customer Administrators (optional)
Enabling GUI Access for Phone Users (optional)
Troubleshooting the Cisco Unified CME GUI (optional)
E nabling the HTTP Server
DETAILED STEPS
Enabling GUI access for system
DETAILED STEPS
ACCESSING THE CISCO UNIFIED CME GUI
Accessing the Cisco Unified CME GUI
Restrictions
• The Cisco Unified CME GUI requires Microsoft Internet Explorer 5.5 or a later version. Other browsers are not supported.
• Extension Mobility options in Cisco Unified CME GUI 4.2.1 and later versions cannot be accessed from the System Administrator or Customer Administrator login screens.
STEPS INVOLVED:
Step 1:
Go to the following URL:
http://router_ipaddress/ccme.html
where router_ipaddress is the IP address of your Cisco Unified CME router.
For example http://10.10.10.176/ccme.html
Step 2:
Enter your user name and password at the login screen.
The Cisco Unified CME system evaluates your privilege level and presents the appropriate window.
Users with Cisco IOS software privilege level 15 also have system-administrator-level
privileges in the Cisco Unified CME GUI after being authenticated locally or remotely through AAA. The ip http authentication command that is configured on the Cisco Unified CME router determines where authentication occurs.
Step 3
After you login and are authenticated, the system displays one of the following home pages, based on your user level:
• System administrator home page.
• Customer administrator sees a reduced version of the options available on the system administrator page, according to the XML configuration file that the system administrator created.
• Phone user home page.
Configuring the Cisco Unified CME System-Level Functions
Four key system-level functions need to be specified in order for the CME router tobegin supporting IP phones:
Maximum phones and directory numbers Firmware load files Source IP address information
Generated configuration files
Maximum Phones and Directory Numbers
Cisco Unified CME router needs to know the number of phones and directory numbers it will be supporting.
By, default, Maximum Phones and Directory Numbers values are set to zero, so the router will not support any VoIP devices.
Provisioning CME Phone and Directory Number Support
Firmware load files
The telephony service should be made aware of the firmware files it should use for the various models of Cisco IP phones. The “load ?” command on the CME router displays all supported Cisco IP phone models. You need to enter a unique load command for each IP phone model you are using in your Cisco Unified CME system.
The cme-basic files(which is in flash memory) will contain the phone load files. We can choose
appropriate load file based on the type of the phone used.
Specifying firmware loads for Cisco IP phones
Source IP address information
Cisco Unified CME router can respond to the Cisco IP phones only when it knows the source IP address to use when communicating.
This is specified using the command “ip source-address” from the telephony service configuration mode.
If the CME router supports IP phones on multiple VLANs the IP phones can also use a loop back interface as the source IP address.
The CME router can provide service to IP phones even if the Fast Ethernet interface were to go offline using the Loop back interface.
Once you create the loop back interface, you can change the ip source-address to use the new loop back interface for communicating with the IP phones.
Generated configuration files
It focuses on generating configuration files for the Cisco IP phones.
The IP phone uses its configuration file to determine which IP address to use when contacting the CME router. The firmware file contains the IP phone’s extension number (if it has one), and many other configuration items.
This output represents the Cisco Unified CME router updating the configuration files that are sent to the IP phones.
This process occurs any time a change is made to the CME router that would affect the IP phone boot process.
The show telephony-service tftp-bindings command shows all the files the CME service itself is serving to the IP phones via TFTP.
The Cisco Unified CME router has been configured with the correct firmware information only for the Cisco 7940, 7960, 7970, and 7971 IP Phone models, so the XMLDefault.cnf.xml file displays only these firmware images
Understanding and Configuring Ephone-Dn’s using CLI
An ephone-dn in its simplest form is just a directory number that can be assigned to oneor more buttons on one or more Cisco IP phones. You can configure each ephone-dn youcreate as either a single- or dual-line mode ephone-dn. Here’s the difference:
Single-line ephone-dn: In single-line mode, the ephone-dn is only able to make orreceive one call at a time. If a call arrives on an ephone-dn where there is already anactive call, the caller will receive a busy signal.
Dual-line ephone-dn: In dual-line mode, the ephone-dn is able to handle two simultaneouscalls. This is useful for supporting features like call waiting, conference calling,and consultative transfers.
Configuring ephone-dn's
The number syntax also supports a secondary number value. For example, you could enter
CME_Voice(config)#ephone-dn 2 dual-line CME_Voice(config-ephone-dn)#number 1001 secondary 4805551001
This allows the ephone-dn to answer for multiple phone numbers.
Creating an ephone
CME_Voice(config)# ephone ? <1-24> Ethernet phone tag CME_Voice(config)# ephone 1
After creating the ephone, we need to logically link it to the physical IP phone it represents.
The CME router uses the MAC address of a Cisco IP phone for this purpose.There are three ways to find the MAC address of a Cisco IP phone
1. On the box of the Cisco IP phone:
2. On the back of the Cisco IP phone:
3. From the Settings menu of the Cisco IP phone:
Assigning a MAC address to an ephone CME_Voice(config)# ephone 1 CME_Voice(config-ephone)# mac-address 0014.1c48.e71a
Verifying Ephone registration status.
Tip : If you ever see a phone’s status shown as DECEASED in the show ephone output,the CME router has lost connectivity with the IP phone through a TCP keepalive failure.The UNREGISTERED status indicates the CME router closed the connection to the IPphone in a normal manner.
Associating Ephones and Ephone-DNs
Linking ephones and ephone-dns is probably the most confusing section of the CMEconfiguration because there are so many options. You can assign ephone-dns by usingthe button command from ephone configuration mode. The basic syntax of this commandis as follows:
button <physical button> <separator> <ephone-dn>
You can assign multiple lines to a phone by either entering multiple button commands.
The show ephone command is also useful for verifying button assignments.
Notice the last two lines of this show output. You are now able to verify the ephone-dnsassigned to the ephone. As an added benefit, the output displays the actual extension aswell. Notice the first button shows CH1 and CH2 as IDLE while the second button justshows CH1 as IDLE. This is because ephone-dn 2 was configured with the dual-line syntax,which allows two active channels.
Separators used with button Command
For example,
a company might want to create four DNs for their three IP phones to meetthese requirements:n IP phone 1 (normal employee)n Line 1: directory number 1010 (normal ring)n Line 2: directory number 1015 (feature ring)n IP phone 2 (normal employee)n Line 1: directory number 1011 (normal ring)n Line 2: directory number 1015 (feature ring)n IP phone 3 (receptionist)n Line 1: directory number 1012 (normal ring)n Line 2: directory number 1010 (monitor phone 1 status)n Line 3: directory number 1011 (monitor phone 2 status)n Line 4: directory number 1015 (feature ring)
The configuration in Example 5.12 will accomplish this scenario.
Naming and labelling of ephones
Naming directory numbers
CME_Voice(config)# ephone-dn 20CME_Voice(config-ephone-dn)#number 1000CME_Voice(config-ephone-dn)# name BellmanCME_Voice(config-ephone-dn)# exit
NOTE: The name can be assigned only after providing the number to that particular dn.
Labels.
The label syntax allows you to assign a logical name to the speed-dial.Label will show up next to the line button on the phone.
Configuring labels
CME_Voice(config)# ephone-dn 20CME_Voice(config-ephone-dn)#number 1000CME_Voice(config-ephone-dn)# label managerCME_Voice(config-ephone-dn)# exit
CONFIGURING CME THROUGH GUI
Prior to being able to configure CME features using CME GUI, the system administrator first needs to configure the following to allow gui access.
config terminal telephony-service web system name <NAME> password <PASSWORD>
First step is is to enter the mac address of the ip phone which we wish to add through CLI.
Access the Gui using
http://router_ipaddress/ccme.html
In this screen we can configure ip phones based on our needs.
CME LAB
TOPOLOGY
CONFIGURATIONS
Router used was 2801 with d-ram 256mb and flash 64mb.
Router IOS was upgraded to version 12.4(3h).
Upgradation process.
Install a TFTP Server A Trival File Transfer Protocol (TFTP) server application must be downloaded and installed on a TCP/IP-ready workstation or PC.The TFTP application must be configured to operate as a TFTP server as opposed to a TFTP client.A console session is established to the pc with tftp server. The router must be able to ping the tftp server. Copy the IOS bin file to the router flash.
Commands:
router# copy tftp flash Address or name of remote host []? 10.77.59.19 Source filename []? c2801-spservicesk9-mz.124.3h.binDestination filename [c2801-spservicesk9-mz.124.3h.bin]?yErase flash: before copying?y
The copying process takes several minutes; the time differs from network to network.After copying , flash will contain the IOS image file. Reload the router.
commandsrouter#reload System configuration has been modified. Save? [yes/no]: y Building configuration... [OK] Proceed with reload? [confirm]y
After reloading verify that the router is running with proper IOS image.
router#show version 00:22:25: %SYS-5-CONFIG_I: Configured from console by console Cisco Internetwork Operating System Software
IOS (tm) C2600 Software (2801), Version 12.4(3h), RELEASE SOFTWARE (fc1) Copyright (c) 1986-2002 by cisco Systems, Inc. Compiled Mon 25-Mar-02 20:33 by kellythw Image text-base: 0x80008088, data-base: 0x80828788 ROM: System Bootstrap, Version 11.3(2)XA4, RELEASE SOFTWARE (fc1) r1 uptime is 22 minutes System returned to ROM by reload System image file is "flash:c2801-spservicesk9-mz.124.3h.bin".
This IOS includes Call Manager Express 3.3 .
cme-full- 3.3.0.3a.tar was downloaded and copied to the flash via tftp server.
Commandsrouter#archive tar /xtract tftp://10.77.59.19/cme-full-3.3.0.0.tar flash:
ROUTER CONFIGURATION
1.Create 2 sub-interface for fa0/0 one for data vlan and other for voice vlan and assign the ip addresses.2.Apply Dot1.q encapsulation for both sub-interfaces.3.Create a loop back interface and assign ip address in case the fa0/0 interface fails.4.Configure the vty and enable passwords .5.Enable the telephony service.6.Load the Ip Phone 7940 load file from the flash.(load file for the Ip phone will be present in the extracted content of 3.3.0.3a.tar.7.Set the maximum
Switch configuration
1.Create a voice vlan and assign ports for the same.2.Create data vlan under native vlan .2.Set the Port connecting to the router as trunk and rest of the ports as access ports.3.Assign ip address for the native vlan.4.Assign the default gateways for data and voice vlans.5.Configure the vty and enable passwords .
PC configurations.1.Assign the ip address for the PC and set the default gateway same as for data vlan.
Ip Phone Configuration1,Power the Ip Phones using the adapter and connect it to the voice vlan ports(f0/0 – 10).2.Erase the current configurations of the Ip phones. For doing this press the settings button ->
network configurations ->use the unlock code '**#'->erase configurations ->save.3.Set the ip address,subnet mask,default router, tftp server under the network configuration settings. These configurations should be in the voice vlan network.4.Create the cnf files in the router and reboot the Ip Phones.
Enabling the GUIEnable the GUI in the router as mentioned earlier in the document.(page-11).
After enabling the GUI we can access the cme gui by opening a web-browser andGo to the following URL: http://192.168.1.1/ccme.html
Enter the user name and password which u have set during the gui enabling process.After you login and are authenticated the system displays System administrator home page. Enter the IP Phone Mac address through CLI and do the rest of the configurations as shown in the screen shots.
CONFIGURATION FEATURES USING CLI
Configuring Ephone-Dn’s
Features
1.Call forwarding
Forwarding calls from the command line gives you more options than does forwardingcalls from the IP phone.
CommandsCME_Voice(config)# ephone-dn 1CME_Voice(config-ephone-dn)# call-forward ?all forward all callsbusy forward call on busymax-length max number of digits allowed for CFwdAll from IP phonenight-service forward call on activated night-servicenoan forward call on no-answerCME_Voice(config-ephone-dn)# call-forward busy 1003CME_Voice(config-ephone-dn)# call-forward noan 2000 ?timeout Ringing no answer timeout durationCME_Voice(config-ephone-dn)# call-forward noan 2000 timeout ?<3-60000> Ringing no answer timeout duration in secondsCME_Voice(config-ephone-dn)# call-forward noan 2000 timeout 25
These options allow you to forward calls that are busy or not answering (noan) to a differentextension.
2.Configuring Call Transfer
There are two transfer methods available:
Consult: Consult transfer allows you to speak with the other party before transferringthe call. After you dial the number to which you would like to transfer the call,you can wait for the other party to answer and speak with them before transferringthe call. Pressing the Transfer soft key a second time transfers the call, dropping youout of the conversation. Consult transfers require a second line (or dual-line configuration).This is the default transfer mode in CME.n Blind: Blind transfer immediately transfers the call after you have dialed the number(you do not hit the Transfer softkey a second time). Blind transfers can work in a single-line configuration.
Commands
CME_Voice(config)# telephony-service
CME_Voice(config-telephony)# transfer-system full-consult
3.Configuring Call PickupCall pickup allows you to answer another ringing phone in the organization from your
local phone. This is accomplished by pushing the PickUp softkey on the IP phone whileanother phone is ringing. The call automatically transfers to the local phone, where youcan answer it. Of course, the organization is large and there could be many ringingphones at the same time, so call pickup gives you the opportunity to divide the phonesinto groups. Based on the softkey used, the users can answer other ringing phones in their own group or enter other group numbers to answer the ringing phones in that group.
The configuration of call pickup is incredibly simple: just design your groups of phonesand assign the ephone-dns to the groups.
Commands
CME_Voice(config)# ephone-dn 1CME_Voice(config-ephone-dn)# pickup-group 10CME_Voice(config-ephone-dn)# ephone-dn 2CME_Voice(config-ephone-dn)# pickup-group 10CME_Voice(config-ephone-dn)# ephone-dn 3CME_Voice(config-ephone-dn)# pickup-group 11CME_Voice(config-ephone-dn)# ephone-dn 4CME_Voice(config-ephone-dn)# pickup-group 11CME_Voice(config-ephone-dn)# ephone-dn 5
CME permits three methods to answer other ringingphones:Directed pickup: You can pick up another ringing phone directly by pressing thePickUp softkey and dialing the DN of the ringing phone. CME then transfers the calland immediately answers it at your local phone.
Local group pickup: You can pick up another ringing phone in the same call pickupgroup as your phone by pressing the GPickUp button and entering an asterisk (*)when you hear the second dial tone.
Other group pickup: You can pick up a ringing phone in another group by pressingthe GPickUp button and entering the other group number when you hear the seconddial tone.
4.Configuring Intercom
Intercom configurations are common in traditional phone systems. This feature allows an
administrative assistant and executive to work closely together by having a speakerphone“tether” between them.The way intercom deployments work is through a speed-dial and auto-answerspeed-dial configuration. If the administrative assistant presses the button configured asan intercom, it speed dials the executive’s phone, which auto-answers the call on mutedspeakerphone. To establish two-way communication, the executive deactivates mute (bypressing the Mute button).
Commands
CME_Voice(config)# ephone-dn 9CME_Voice(config-ephone-dn)# number A100CME_Voice(config-ephone-dn)# intercom A101 label “Manager”CME_Voice(config-ephone-dn)# exitCME_Voice(config)# ephone-dn 10CME_Voice(config-ephone-dn)# number A101CME_Voice(config-ephone-dn)# intercom A100 label “Assistant”CME_Voice(config-ephone-dn)# exitCME_Voice(config)# ephone 3CME_Voice(config-ephone)# button 1:9CME_Voice(config-ephone)# restartrestarting 0014.1C48.E71ACME_Voice(config-ephone)# exitCME_Voice(config)# ephone 4CME_Voice(config-ephone)# button 1:10CME_Voice(config-ephone)# restart
Notice the number assigned to ephone-dn 9 is A100. You cannot dial this number froma Cisco IP phone keypad, but you can assign it to a speed-dial button. The intercomcommand acts like a speed-dial button on the ephone-dn.
There are three other arguments you can use with the intercomcommand to tune the functionality:n barge-in: Automatically places an existing call on hold and causes the intercom toimmediately answer.n no-auto-answer: Causes the phone to ring rather than auto-answer on speakerphone.
no-mute: Causes the intercom to answer with unmuted speakerphone rather thanmuted. While this is beneficial to allow immediate two-way conversation, you alsorun the risk of one side barging into existing conversations or background noise.
5.Configuring Paging
Paging is similar to the intercom concept; however, it provides only a one-way automatic
path for communication. This is useful to allow broadcast messages, such as emergencynotifications or to notify employees of holding calls.The CME paging system works by designating an ephone-dn as a paging number. Calls tothe DN of this ephone-dn will broadcast to the IP phones that you have assigned to thispaging group.
The three paging configurations are unicast paging, multicast paging, and multiple-grouppaging.
Example for unicast, single-group paging.
CME_Voice(config)# ephone-dn 13CME_Voice(config-ephone-dn)# number 5555CME_Voice(config-ephone-dn)# pagingCME_Voice(config-ephone-dn)# exitCME_Voice(config)# ephone 1CME_Voice(config-ephone)# paging-dn 10CME_Voice(config-ephone)# exitCME_Voice(config)# ephone 2CME_Voice(config-ephone)# paging-dn 10
Configuring Multiple-Group Paging
CME_Voice(config)# ephone-dn 13CME_Voice(config-ephone-dn)# number 5555CME_Voice(config-ephone-dn)# pagingCME_Voice(config-ephone-dn)# exitCME_Voice(config)# ephone-dn 15CME_Voice(config-ephone-dn)# number 5556CME_Voice(config-ephone-dn)# pagingCME_Voice(config-ephone-dn)# exitCME_Voice(config)# ephone-dn 14CME_Voice(config-ephone-dn)# number 5557CME_Voice(config-ephone-dn)# paging group 13,15CME_Voice(config-ephone-dn)# exitCME_Voice(config)# ephone 1CME_Voice(config-ephone)# paging-dn 13CME_Voice(config-ephone)# exitCME_Voice(config)# ephone 2CME_Voice(config-ephone)# paging-dn 13CME_Voice(config-ephone)# exitCME_Voice(config)# ephone 3CME_Voice(config-ephone)# paging-dn 15CME_Voice(config-ephone)# exitCME_Voice(config)# ephone 4CME_Voice(config-ephone)# paging-dn 15
With the configuration shown in the example, a call to DN 5555 will page ephones 1and 2, a call to DN 5556 will page ephones 3 and 4, and a call to DN 5557 will page allephones. You do not need to assign any ephones to paging-dn 14 because this ephone-dnrepresents a group of both paging-dns 13and 15
6. Configuring After-Hours Call Blocking
In the traditional telephony realm, there have been many recorded incidents of unauthorized
phone calls being placed after-hours, when most, if not all, staff has left for theevening. To prevent this, you can implement after-hours call blocking on CME.Of course, there are exceptions. You may want to have some phones completelyexempt from the policy, or give users a “back door” around the restrictions if theyare working late and need to make business-related calls that CME would typicallyrestrict. The after-hours call blocking configuration on CME provides for both of thesescenarios. You have the option to completely exempt certain IP phones from the afterhoursrestrictions or to provide users with a PIN they can enter into the IP phone. If theyenter the PIN correctly, CME exempts the IP phone from the after-hours policy for aconfigurable amount of time.
After-hours call blocking has three major steps of configuration:Step 1. Define days and/or hours of the day that your company considers off-hours.Step 2. Specify patterns that you would like to block during the times specified inStep 1.Step 3. Create exemptions to the policy, if needed.
Commands
CME_Voice(config)# telephony-serviceCME_Voice(config-telephony)# after-hours ?block define after-hours block patterndate define month and dayday define day in weekCME_Voice(config-telephony)# after-hours day mon 17:00 8:00CME_Voice(config-telephony)# after-hours date ?MONTH Month (Jan, Feb, Mar, etc)CME_Voice(config-telephony)# after-hours date dec ?<1-31> day of month in dateCME_Voice(config-telephony)# after-hours date dec 25 ?hh:mm Time to start (hh:mm)CME_Voice(config-telephony)# after-hours date dec 25 00:00 ?hh:mm Time to stop (hh:mm)CME_Voice(config-telephony)# after-hours date dec 25 00:00 00:00
Configuring after hour exemptions:
CME_Voice(config)# ephone 1CME_Voice(config-ephone)# pin ?WORD A sequence of digits - representing personal identificationCME_Voice(config-ephone)# pin 1234CME_Voice(config-ephone)# exit
Configuring normal ring, feature ring and monitoring
For example,
If a company need to create four DNs for their three IP phones to meetthese requirements:IP phone 1 (normal employee)Line 1: directory number 1000 (normal ring)Line 2: directory number 1001(feature ring)IP phone 2 (normal employee)Line 1: directory number 1002(normal ring)Line 2: directory number 1003 (feature ring)IP phone 3 (receptionist)Line 2: directory number 1000 (monitor phone 1 status)Line 3: directory number 1002(monitor phone 2 status)
CME_Voice(config)# ephone-dn 1 dual-lineCME_Voice(config-ephone-dn)# number 1000CME_Voice(config)# ephone-dn 2 dual-lineCME_Voice(config-ephone-dn)# number 1001CME_Voice(config)# ephone-dn 3 dual-lineCME_Voice(config-ephone-dn)# number 1002CME_Voice(config)# ephone-dn 4 dual-lineCME_Voice(config-ephone-dn)# number 1003CME_Voice(config)# ephone 1CME_Voice(config-ephone)# button 1:1 2f2CME_Voice(config-ephone)# exitCME_Voice(config)# ephone 2CME_Voice(config-ephone)# button 1:3 2f4CME_Voice(config-ephone)# exitCME_Voice(config)# ephone 3CME_Voice(config-ephone)# button 1m1CME_Voice(config-ephone)# button 2m3CME_Voice(config-ephone)# exit
Configuring shared line
CME_Voice(config)# ephone-dn 5 dual-lineCME_Voice(config-ephone-dn)# number 8000CME_Voice(config)# ephone-dn 6 dual-lineCME_Voice(config-ephone-dn)# number 8000CME_Voice(config)# ephone 3CME_Voice(config-ephone)# button 2:5CME_Voice(config-ephone)# restartCME_Voice(config-ephone)# exitCME_Voice(config)# ephone 5
CME_Voice(config-ephone)# button 1:6CME_Voice(config-ephone)# restartCME_Voice(config-ephone)# exit
If a call comes, either the phone 3 or 5 rings. If phone 3 is answered by one person, the person sitting in front of phone 5 can make a call, as the dn number assigned is different.
Disadvantage: Incoming calls do pose a problem. When the CME router receives a call for 8000, it now sees two equal cost paths to get there (ephone-dn 5and ephone-dn 6). So how is itgoing to handle this dilemma? Just pick one completely at random. So, sometimes ephone3 will get the call and sometimes ephone 9 will get the call. However, most people would like morecontrol over how the call flows than a random line selection. You can achieve control over which ephone receives the call by using the preference and huntstop commands.
The preference command dictates which ephone-dn is more preferredthan the other by assigning a value from 0–10, where the lower preference numbersare better. Example:CME_Voice(config)# ephone-dn 5 dual-lineCME_Voice(config-ephone-dn)# number 8000CME_Voice(config-ephone-dn)# preference 0CME_Voice(config)# ephone-dn 6 dual-lineCME_Voice(config-ephone-dn)# number 8000CME_Voice(config-ephone-dn)# preference 1
DisadvantageEphone-dn 5 would always receive incoming calls for the DN 8000.
Each of the ephone-dns are configured withthe dual-line syntax. This enables them to place calls on hold and make an additional call,transfer a call, start a conference call, or receive calls via call waiting. Because ephone-dn 5 was configured as a lower preference than ephone-dn 6, the first call to DN 8000 would go to ephone-dn 5. If a second call came in to DN 8000 while ephone-dn 5 was still on the active call, the call would be received via call waiting on ephone-dn 5 rather than rolling over to ephone-dn 6.
That doesn’t seem efficient, does it? This is where the huntstop command comes in handy.
The huntstop command has two forms: huntstop and huntstop channel. The name of thiscommand describes its function. It stops the CME router from hunting for other matchesto the destination pattern. Simply entering huntstop tells the CME router, “stop huntingfor other matches with this ephone-dn.” Entering huntstop channel says to the router,“stop hunting for other matches with one channel of this ephone-dn.”
Configuring huntstop
CME_Voice(config)# ephone-dn 5 dual-lineCME_Voice(config-ephone-dn)# number 8000
CME_Voice(config-ephone-dn)# preference 0CME_Voice(config-ephone-dn)# huntstop channelCME_Voice(config-ephone-dn)# no huntstopCME_Voice(config)# ephone-dn 6 dual-lineCME_Voice(config-ephone-dn)# number 8000CME_Voice(config-ephone-dn)# huntstop channelCME_Voice(config-ephone-dn)# preference 1
The configuration of ephone-dn 5 uses the huntstop channel command followedby the no huntstop command. This may seem counterintuitive at first, but follow thelogic: if you use only the huntstop channel command, the router will simply stop huntingif the first channel of ephone-dn 5 is in use. Additional calls to DN 8000 will resultin a busy signal. By combining the huntstop channel command with the no huntstopcommand, you are telling the CME router, “Stop hunting for other channels on ephonedn5, but don’t stop hunting completely! Look for other ephone-dns with this DN.” Thisresults in ephone-dn 6 receiving a call to DN 8000 if ephone-dn 5 is currently activeon a call. If both ephone-dns 5 and 6 are on an active call, an incoming call to DN8000 will receive a busy signal.
Overlay:
Consider there are five employees in an organization’s technical support group who receive calls on DN 8000. The configuration mentioned above will accomplish this objective (if there were an additional three ephone-dns added with DN 8000 for the other employees), but the tech support employees who have the preference 0 and 1 ephone-dns assigned to their IP phone will get lots of calls while the tech support employees with the preference 2, 3, and 4 ephone-dns will only get calls if the first twoare busy. A better system will have all the IP phones ring when on a call to DN 8000,and whichever tech support employee answers the call first will take the call.
There are three kinds of overlay separator.o separator: Overlay line with no call waitingc separator: Overlay line with call waitingx separator: Overlay line with line rollover to other lines on Cisco IP phone
Configuring overlay with no call waiting
CME_Voice(config)# ephone-dn 5CME_Voice(config-ephone-dn)# number 8000
CME_Voice(config-ephone-dn)# preference 0CME_Voice(config-ephone-dn)# no huntstopCME_Voice(config)# ephone-dn 6CME_Voice(config-ephone-dn)# number 8000CME_Voice(config-ephone-dn)# preference 1CME_Voice(config-ephone-dn)# exitCME_Voice(config)# ephone 3CME_Voice(config-ephone)# button 1o5,6CME_Voice(config-ephone)# exitCME_Voice(config)# ephone 5CME_Voice(config-ephone)# button 1o5,6CME_Voice(config-ephone)# exitCME_Voice(config)# telephony-serviceCME_Voice(config-telephony)# restart all
An incoming call to DN 8000 would now ring both ephones 3 and 5 because ephone-dns5 and 6 are overlayed on button 1. The first call that comes in to DN 8000 willcause both ephones 3 and 5 to ring. Whichever phone answers the call will take responsibilityfor it and the CME router will flag the ephone as “busy” (in a call). If a second callcomes in while the first call is still active, the ephone that did not answer the first call willring. The ephone that is still active on the first call will not hear a call waiting beep whilethe line is ringing. If you wanted to have call waiting active for the overlay lines, youcould change the button command syntax to button 1c5,6 for both phones. If youhave changed to a c button separator, the phone currently on an active call would hear acall waiting beep. This is not the call waiting beep of ephone-dn 5 (which received thefirst call) but the call waiting beep of ephone-dn 6(which is receiving the second call).
Configuring overlay with x separator
CME_Voice(config)# ephone 3CME_Voice(config-ephone)# button 1c5,6CME_Voice(config-ephone)# button 2x1CME_Voice(config-ephone)# restart
The x separator does not link button 2 of the IP phone to ephone-dn 1; rather, it allowsbutton 2 to be an overflow of button 1.
Configuring call park:
Typically, when you place a call on hold, you can retrieve the call only from the originalphone where you placed the call on hold. Shared-line systems bend the rules a little byallowing you to retrieve the call from any phone with the same shared line assignment.The call park feature takes this one step further by allowing you to retrieve the call fromany phone in the organization. Call park “parks” the caller on hold at an extension ratherthan on a specific line. Any IP phone that is able to dial the park extension number canretrieve the call.
CME_Voice(config)# ephone-dn 11CME_Voice(config-ephone-dn)# number 100CME_Voice(config-ephone-dn)# name EljayCME_Voice(config-ephone-dn)# park-slotCME_Voice(config-ephone-dn)# park-slot timeout ?<0-65535> Specify the park timeout (seconds) before the call is returned to thenumber it was parked fromCME_Voice(config-ephone-dn)# park-slot timeout 60 ?limit Set call park timeout count limitCME_Voice(config-ephone-dn)# park-slot timeout 60 limit ?<1-65535> Specify the number of park timeout cycles before the call isdisconnectedCME_Voice(config-ephone-dn)# park-slot timeout 60 limit 10 ?notify Define additional extension number to notify for park timeoutrecall recall transfer back to originator phone after timeouttransfer Transfer to originator or specified destination after timeout limitexceeded<cr>CME_Voice(config-ephone-dn)# park-slot timeout 60 limit 10 recall ?alternate Transfer to alternate target if original target is busyretry Set recall/transfer retry interval if target is in use<cr>CME_Voice(config-ephone-dn)# park-slot timeout 60 limit 10 recall
Configuring music on hold:
CME has the ability to stream Music on Hold (MoH) from specified WAV or AU audio files that you copy to the flash memory of the router.
CME can stream the MoH using G.711 or G.729 codecs.
Restrictions of music on hold.
• IP phones do not support multicast at 224.x.x.x addresses.
• Cisco Unified CME 3.3 and earlier versions do not support MOH for local Cisco Unified CME phones that are on hold with other Cisco Unified CME phones; these parties hear a periodic repeating tone instead.
• Cisco Unified CME 4.0 and later versions support MOH for internal calls only if the multicast moh command is used to enable the flow of packets to the subnet on which the phones are located.
• Internal extensions that are connected through a Cisco VG224 Analog Voice Gateway or through a WAN (remote extensions) do not hear MOH on internal calls.
• Multicast MOH is not supported on a phone if the phone is configured with the mtp command or the paging-dn command with the unicast keyword.
Configuration:
CME_Voice(config)# telephony-serviceCME_Voice(config-telephony)# multicast moh ?CME_Voice(config-telephony)# multicast moh 239.1.1.55 ?port Define media port for multicast mohCME_Voice(config-telephony)# multicast moh 239.1.1.55 port ?<2000-65535> Specify the RTP port: 2000 - 65535CME_Voice(config-telephony)# multicast moh 239.1.1.55 port 2123
The configuration mentioned is for enabling the default music on hold.
Configuring conferencing
There are two types of conferencing
1. Ad-hoc conferencing2. Meet me conferencing
Ad hoc conferencing
The maximum number of simultaneous conferences is platform-specific to the type of Cisco Unified CME router, and each individual Cisco Unified IP phone can host a maximum of one conference at a time. You cannot create a second conference on a phone if you already have an existing conference on hold.
Configuring Ad hoc conferencing:
Router> enable
Router# configure terminal
Router(config)# ephone 1
Router(config-ephone)# keep-conference endcall/ drop-last/ local-only
Router(config)# end
keep-conference—(No keywords used) The conference initiator can press the EndCall soft key to end the conference and disconnect all parties or hang up to leave the conference and keep the other two parties connected. The conference initiator can also use the Confrn soft key (IP phone) or hookflash (analog phone) to break up the conference but stay connected to both parties.
• drop-last—The action of the Confrn soft key is changed; the conference initiator can press the Confrn soft key (IP phone) or hookflash (analog phone) to drop the last party.
• endcall—The action of the EndCall soft key is changed; the conference initiator can hang up or press the EndCall soft key to leave the conference and keep the other two parties connected.
• local-only—The conference initiator can hang up to end the conference and leave the other two parties connected only if one of the remaining parties is local to the Cisco Unified CME system (an internal extension).
Meet-Me Conferencing in Cisco Unified CME 4.1 and Later versions In Cisco Unified CME 4.1 and later versions, meet-me conferences consist of at least three partiesdialing a meet-me conference number predetermined by a system administrator. For example, the conference is created when the conference creator at extension 1215 presses the MeetMe soft key and hears a confirmation tone, then dials the meet-me conference number 1500. Extension 1225 and extension 1235 join the meet-me conference by dialing 1500. Extensions 1215, 1225, and 1235 are now parties in a meet-me conference on extension 1500.
Configuring Maximum Parties:
You can configure the maximum number of conference parties to be lower than the actual maximum of 32 for meet-me conferences.
Meet-Me Conferencing in Cisco CME 3.2 to Cisco Unified CME 4.0
Unlike the built-in Cisco Unified CME conference feature, a meet-me conference does not have a three-party limit. Meet-me Conferencing in Cisco CME 3.2 to Cisco Unified CME 4.0 requires Cisco Unity Express auto-attendant to transfer callers to the correct Meet-Me bridge and a dual T-1/E-1 VWIC card for providing DSP resources.
SCCP: Configuring Multi-Party Ad Hoc and Meet-Me Conferencing in Cisco Unified CME 4.1 and Later Versions Restrictions
• The maximum number of meet-me conference parties is 32 for one DSP using the G.711 codec and 16 for the G.729 codec.
• A participant cannot join more than one conference at the same time.
E nabling DSP Farm Services for a Voice Card
To enable DSP farm services for a voice card to support multi-party ad hoc and meet-me conferences, perform the following steps.
SUMMARY STEPS
1. enable2. configure terminal 3. voice-card slot 4. dsp services dspfarm 5. exit
Router> enable Router# configure terminal Router(config)# voice-card 0Router(config-voicecard)# dsp services dspfarm Router(config-voicecard)# exit
SCCP: Configuring Join and Leave Tones
To configure tones to be played when parties join and leave multi-party ad hoc conferences and meet-me conferences, perform the following steps for each tone to be configured.
SUMMARY STEPS
1. enable
2. configure terminal 3. voice class custom-cptone cptone-name 4. dualtone conference 5. frequency frequency-1 [frequency-2]6. cadence {cycle-1-on-time cycle-1-off-time [cycle-2-on-time cycle-2-off-time] [cycle-3-on-time
cycle-3-off-time] [cycle-4-on-time cycle-4-off-time] | continuous} 7. end
Router> enable Router# configure terminal Router(config)# voice class custom-cptone jointone Router(cfg-cptone)# dualtone conference Router(cfg-cp-dualtone)# frequency 600 900 Router(cfg-cp-dualtone)# cadence 300 150 300 100 300 50 Router(cfg-cp-dualtone)# exit
SCCP: Configuring SCCP for Cisco Unified CME
To enable SCCP on Cisco Unified CME to support multi-party ad hoc and meet-me conferences, perform the following steps:
SUMMARY STEPS
1. enable2. configure terminal 3. sccp local interface-type interface-number [port port-number] 4. sccp ccm {ip-address | dns} identifier identifier-number [port port-number] [version
version-number] 5. sccp ccm group group-number6. bind interface interface-type interface-number7. exit8. sccp 9. exit
Router> enable Router# configure terminal Router(config)# sccp local FastEthernet0/0.2Router(config)# sccp ccm 192.168.3.1 identifier 100 version 7.0 Router(config)# sccp ccm group 123 Router(config-sccp-cm)# bind interface fastethernet 0/0.2Router(config-sccp-cm)# exit Router(config)# sccp Router(config)# sccp
S CCP: Configuring the DSP Farm
To configure the DSP farm profile for multi-party ad hoc and meet-me conferencing, perform the following steps.
Note: The DSP farm can be on the same router as the Cisco Unified CME or on a different router.
SUMMARY STEPS
1. enable2. configure terminal 3. dspfarm profile profile-identifier conference 4. codec {codec-type | pass-through} 5. conference-join custom-cptone cptone-name 6. conference-leave custom-cptone cptone-name 7. maximum conference-party max-parties 8. maximum sessions number 9. associate application sccp 10. end
Router> enable Router# configure terminal Router(config)# dspfarm profile 1 conference Router(config-dspfarm-profile)# codec g711ulaw Router(config-dspfarm-profile)# conference-join custom-cptone jointone Router(config-dspfarm-profile)# conference-leave custom-cptone leavetone Router(config-dspfarm-profile)# maximum conference-party 8Router(config-dspfarm-profile)# maximum sessions 1Router(config-dspfarm-profile)# associate application sccp Router(config-dspfarm-profile)# end
SCCP: Associating Cisco Unified CME with a DSP Farm Profile
To associate a DSP farm profile with a group of Cisco Unified CME routers that control DSP services, perform the following steps.
SUMMARY STEPS
1. enable2. configure terminal 3. sccp ccm group group-number 4. associate ccm identifier-number priority priority-number 5. associate profile profile-identifier register device-name6. end
Router> enable Router# configure terminalRouter(config)# sccp ccm group 1 Router(config-sccp-ccm)# associate ccm 100 priority 1 Router(config-sccp-ccm)# associate profile 1 register confdsp1 Router(config-sccp-ccm)# end
E nabling Multi-Party Ad Hoc and Meet-Me Conferencing
To allow hardware-based multi-party ad hoc conferences with more than three parties and meet-me conferences, perform the following steps.
SUMMARY STEPS
1. enable2. configure terminal 3. telephony-service 4. conference hardware 5. transfer-system full-consult 6. sdspfarm units number 7. sdspfarm tag number device-name 8. sdspfarm conference mute-on mute-on-digits mute-off mute-off-digits 9. end
Router> enable Router# configure terminalRouter(config)# telephony-service Router(config-telephony)# conference hardware Router(config-telephony)# transfer-system full-consult Router(config-telephony)# sdspfarm units 3 Router(config-telephony)# sdspfarm tag 2 confdsp1 Router(config-telephony)# sdspfarm conference mute-on 111 mute-off 222 Router(config-telephony)# end
SCCP: Configuring Multi-Party Ad Hoc Conferencing and Meet-Me Numbers
To configure extension numbers for hardware-based multi-party ad hoc and meet-me ad hoc conferencing, based on the maximum number of conference participants you configure, perform the following steps. Ad hoc conferences require four extensions per conference, regardless of how many extensions are actually used by the conference parties.
NOTE: Ensure that you configure enough directory numbers to accommodate the anticipated number of conferences. The maximum number of parties in a multi-party ad hoc conference on an IP phone is eight; the maximum on an analog phone is three.
SUMMARY STEPS
1. enable2. configure terminal 3. ephone-dn dn-tag [dual-line] 4. number number [secondary number] [no-reg [both | primary]] 5. conference {ad-hoc | meetme} 6. preference preference-order [secondary secondary-order] 7. no huntstop [channel]
8. end
Router> enable Router# configure terminalRouter(config)# ephone-dn 7 octo-line Router(config-ephone-dn)# number 1111Router(config-ephone-dn)# conference meetme Router(config-ephone-dn)# preference 1 Router(config-ephone-dn)# no huntstop Router(config-ephone-dn)# no huntstop
SCCP: Configuring Conferencing Options for a Phone
Prerequisites • The RmLstC, ConfList, Join, and Select functions and soft keys are supported for hardware-based conferencing only and require the appropriate DSP farm configuration.
Restrictions • The ConfList (including the Remove, Update, and Exit soft keys within the ConfList function) and RmLstC soft keys do not work on a Cisco Unified IP Phone 7902, 7935, and 7936. • The RmLstC, ConfList, Join, and Select functions and soft keys are not supported for software-based conferencing. SUMMARY STEPS
1. enable 2.2. configure terminal 3. ephone-template template-tag 4. conference add-mode [creator] 5. conference drop-mode [creator | local] (• creator—The active conference terminates when
the creator hangs up. local—The active conference terminates when the last local party in the conference hangs up or drops out of the conference. )
6. conference admin 7. softkeys connected {[Acct] [ConfList] [Confrn] [Endcall] [Flash] [HLog] [Hold] [Join]
[LiveRcd] [Park] [RmLstC] [Select] [TrnsfVM] [Trnsfer]} 8. softkeys hold {[Join] [Newcall] [Resume] [Select]} 9. softkeys idle {[Cfwdall] [ConfList] [Dnd] [Gpickup] [HLog] [Join] [Login] [Newcall]
[Pickup] [Redial] [RmLstC]} 10. softkeys seized {[CallBack] [Cfwdall] [Endcall] [Gpickup] [HLog] [MeetMe] [Pickup]
[Redial]} 11. exit 12. ephone phone-tag 13. ephone-template template-tag 14. end
Router> enable Router# configure terminal Router(config)# ephone-template 1 Router(config-ephone-template)# conference add-mode creator
Router(config-ephone-template)# conference drop-mode creator Router(config-ephone-template)# conference admin Router(config-ephone-template)# softkeys connected Hold Trnsfer Park Endcall Confrn ConfList Join Select RmLstC Router(config-ephone-template)# softkeys hold Join Newcall Resume Select Router(config-ephone-template)# softkeys idle ConfList Gpickup Join Login Newcall Pickup Redial RmLstC Router(config-ephone-template)# softkeys seized Redial Endcall Cfwdall Pickup Gpickup Callback Meetme Router(config-ephone-template)# exit Router(config)#ephone 3Router(config-ephone)# ephone-template 1 Router(config-ephone)# exit
RUNNING CONFIGURATION OF ROUTER
PSTNRTR#show runBuilding configuration...
Current configuration : 2835 bytes!version 12.4service timestamps debug datetime msecservice timestamps log datetime msecno service password-encryption!hostname PSTNRTR!boot-start-markerboot-end-marker!enable password cisco!no aaa new-model!resource policy!no network-clock-participate wic 1no network-clock-participate wic 2mmi polling-interval 60no mmi auto-configureno mmi pvcmmi snmp-timeout 180ip subnet-zeroip cef!!!!!voice-card 0!!!!!!!!!!!!!
!!!controller E1 0/1/0!controller E1 0/1/1!controller T1 0/2/0 framing esf linecode b8zs!controller T1 0/2/1 framing esf linecode b8zs!!!interface Loopback0 ip address 192.168.2.1 255.255.255.0!interface FastEthernet0/0 no ip address duplex auto speed auto!interface FastEthernet0/0.1 encapsulation dot1Q 1 native ip address 192.168.1.1 255.255.255.0 no snmp trap link-status!interface FastEthernet0/0.2 encapsulation dot1Q 99 ip address 192.168.3.1 255.255.255.0 no snmp trap link-status!interface FastEthernet0/1 no ip address shutdown duplex auto speed auto!interface FastEthernet0/1.1 encapsulation dot1Q 1 native no snmp trap link-status!interface FastEthernet0/1.2 encapsulation dot1Q 99 no snmp trap link-status!
ip classless!!ip http serverno ip http secure-serverip http path flash:!disable-eadi!!!control-plane!!!!!!!!telephony-service load 7960-7940 P00307020200 max-ephones 10 max-dn 15 ip source-address 192.168.3.1 port 2000 create cnf-files version-stamp Jan 01 2002 00:00:00 max-conferences 4 gain -6 moh music-on-hold.au web admin system name eljay secret 5 $1$oLCy$arooMMAZIh4lUrUQwdOMQ. dn-webedit time-webedit transfer-system full-consult!!ephone-dn 1 number 1000 pickup-group 10 label 1000 name Jithin!!ephone-dn 2 number 1001 pickup-group 10 name Jithin 2!!ephone-dn 3 number 1002
pickup-group 11 name Deepu 2!!ephone-dn 4 number 1003 pickup-group 11 name Deepu!!ephone-dn 5 number 8000 no huntstop!!ephone-dn 6 number 8000 preference 1!!ephone-dn 8 number 5000 pickup-group 10!!ephone-dn 9 number A100 intercom A101 barge-in label "Manager"!!ephone-dn 10 number A101 intercom A100 label "'assistant'"!!ephone-dn 11 dual-line number 8000!!ephone-dn 13 number 5556 paging!!ephone-dn 14 number 5557 paging paging group 15,13!
!ephone-dn 15 number 5555 paging!!ephone 1 mac-address 0023.3322.8F13 paging-dn 15 button 1:1 2:2!!!ephone 2 mac-address 0007.EBBA.553D paging-dn 15 button 1:4 2:3!!!ephone 3 mac-address 0018.180E.313D paging-dn 13 button 1:9 2o5,6!!!ephone 4 mac-address 0016.C81F.EB0F paging-dn 13 button 1:10 2:8!!!ephone 5 mac-address 000F.2321.C772 button 1o5,6!!!line con 0line aux 0line vty 0 4 password cisco login!end
SWITCH CONFIGURATIONS
Switch#show runBuilding configuration...
Current configuration : 2387 bytes!version 12.1no service padservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname Switch!enable secret 5 $1$i7WI$rdGwf2EhUIu.Nh8v8frku1!ip subnet-zero!ip ssh time-out 120ip ssh authentication-retries 3!spanning-tree mode pvstno spanning-tree optimize bpdu transmissionspanning-tree extend system-id!!!!interface FastEthernet0/1 switchport access vlan 99 switchport mode access!interface FastEthernet0/2 switchport access vlan 99 switchport mode access!interface FastEthernet0/3 switchport access vlan 99 switchport mode access!interface FastEthernet0/4 switchport access vlan 99 switchport mode access!interface FastEthernet0/5 switchport access vlan 99 switchport mode access!interface FastEthernet0/6
switchport access vlan 99 switchport mode access!interface FastEthernet0/7 switchport access vlan 99 switchport mode access!interface FastEthernet0/8 switchport access vlan 99 switchport mode access!interface FastEthernet0/9 switchport access vlan 99 switchport mode access!interface FastEthernet0/10 switchport access vlan 99 switchport mode access!interface FastEthernet0/11 switchport access vlan 33 switchport mode access!interface FastEthernet0/12 switchport access vlan 33 switchport mode access!interface FastEthernet0/13 switchport access vlan 33 switchport mode access!interface FastEthernet0/14 switchport access vlan 33 switchport mode access!interface FastEthernet0/15 switchport access vlan 33 switchport mode access!interface FastEthernet0/16 switchport access vlan 33 switchport mode access!interface FastEthernet0/17 switchport access vlan 33 switchport mode access!interface FastEthernet0/18 switchport access vlan 33
switchport mode access!interface FastEthernet0/19 switchport access vlan 33 switchport mode access!interface FastEthernet0/20 switchport access vlan 33 switchport mode access!interface FastEthernet0/21!interface FastEthernet0/22 switchport mode access!interface FastEthernet0/23 switchport mode trunk!interface FastEthernet0/24!interface Vlan1 ip address 192.168.1.3 255.255.255.0 no ip route-cache!interface Vlan99 no ip address no ip route-cache shutdown!ip default-gateway 192.168.1.1ip http server!line con 0line vty 0 4 password cisco loginline vty 5 15 login!!end
Switch#
REFERENCES
