Voice system features may comprise of Paging groups, adhoc conferencing, intercom, after hours, call park and so on.
We will walk through the steps to configure above mentioned features of voice system in the subsequent sections below:
Launch CCA tool, to connect to community of devices and supply the user id and password and let CCA tool discover network and devices. Check the topology to ensure all phones are up. Unplug any lines that are connected to the FXO ports on the PODs.
Click on configureà Telephony à voice on the left navigation bar or click the phone icon on the top menu bar. All of the above options are configured from voice features tab. Before we go into depth of configuring these options we will understand the utility of each one of them.
Paging groups – We can setup voice system to provide audio paging functionality with the use of speakers of your IP phones to broadcast the paging audio output. This features works for IP phones having speakerphone mode available or enabled. Idle IP phones are used to output paging audio. IP phones can still be used to make or receive calls during paging. When the phone is used, it simply drops out of the page. We can create paging groups or zones that output paging audio only on specific groups of IP phones and also combine multiple paging groups to output audio paging to multiple paging groups at the same time.
We will use an example to illustrate how paging group can be setup using CCA tool as well as command line.
Router#Show running-config
ephone-dn 14
number 6112
name Sales
paging ip 239.1.1.1 port 2000
The paging-dn is set up with a pilot number of 6112. When you make a call to 6112, it is answered by the paging-dn. The audio stream from phone to the paging-dn is broadcast to all the phones in the paging group for ephone-dn 14 using IP Multicast on address 239.1.1.1 and port 2000.
Once we create a paging-dn, then we create a group of IP phones to include in said paging group. This can be done using the paging-dn command within the ephone command mode. Set the paging-dn command in the ephone command mode to select the tag number of the ephone-dn that you configured as a paging-dn
Paging on IP Phones
Router#Show running-config
ephone 12
mac-address 000d.1234.0efc
button 1:1 2:6
paging-dn 14
ephone 15
mac-address 000d.4132.f7e4
button 1:4 2:5
paging-dn 14
One paging group can contain n number of IP phones and there no limit on the number of paging-dns and corresponding paging groups we can create, but Each IP phone can belong directly to only a single paging group. We can enter only one paging-dn configuration per ephone.
Adhoc conferencing – An adhoc conference is an unscheduled conference. It happens when a 3rd party is added to any conversation by conference participants. The adhoc initiators can add/delete/drop participants from conference. Each DSP support maximum of 64 G.711 participants only (single mode), which means 8 conferences of 8 participants each
Each DSP can support a maximum of 16 G.711/G.729A/G.729 participants in mixed mode which means 2 conferences of 8 participants each.
Below example illustrates the sample configuration of adhoc conferencing:
Voice-card X
Dsp services farm
Sccp local FastEthernet0/0
Sccp ccm 192.168.10.1 identifier 100 version 4.0
Sccp enable SCCP
Sccp ccm group 1
Associate ccm 100 priority 1
Associate profile 1 register confprof1
Voice class custom-cptone jointone
Dualtone conference
Frequency 600 900
Cadence 300 150 300 100 300 50
Voice class custom-cptone leavetone
Dualtone conference
Frequency 400 800
Cadence 400 50 200 50 200 50
Dspfarm profile 1 conference
Codec g711ulaw
Conference-join custom-cptone jointone
Conference-leave custom-cptone leavetone
Maximum conference-participants 8
Maximum sessions 8
Associate application SCCP
No shut
Telephony-service
Conference hardware
Max-ephone 10
Max-dn 100
Ip source-address 192.168.10.1 port 2000
Dspfarm conference mute-on 111 mute-off 222
Dspfarm units 1
Dspfarm tag 1 confprof1
Transfer-system full-consult
Transfer-pattern….
Face standard
Ephone-template 1
Softkey hold
softkey idle Cfwdall ConfList Dnd
softkeys seized Endcall Redial Meetme Cfwdall Pickup
softkeys connected ConfList Confrn Endcall Hold Join Park RmLstC Select Trnsfer
ephone-dn 1 dual-line
number 101
ephone-dn 2 dual-line
number 102
ephone-dn 3 dual-line
number 103
ephone-dn 21 dual-line
description meet-me conference extension
number 8000 <Configure extension number >
conference meetme
no huntstop
ephone-dn 22 dual-line
description meet-me conference extension
number 8000
conference meetme
preference 1
no huntstop
ephone-dn 23 dual-line
description meet-me conference extension
number 8000
conference meetme
preference 2
no huntstop
ephone-dn 24 dual-line
description meet-me conference extension
number 8000
conference meetme
preference 3
ephone-dn 31 dual-line
description ad-hoc conference extension
number A000
conference ad-hoc
no huntstop
ephone-dn 32 dual-line
description meet-me conference extension
number A000
conference ad-hoc
preference 1
no huntstop
ephone-dn 33 dual-line
description meet-me conference extension
number A000
conference ad-hoc
preference 2
no huntstop
ephone-dn 34 dual-line
description meet-me conference extension
number A000
conference ad-hoc Enable ad-hoc extension
preference 3
ephone 1
conference drop-mode creator
conference add-mode creator
conference admin
ephone-template 1
mac-address 0002.FD3B.A5F1
button 1:1
ephone 2
ephone-template 1 <Apply ephone-template so that this ephone can use meet-me softkey>
mac-address 0002.FD3B.A5E1
button 1:2
ephone 3
ephone-template 1
mac-address 0002.FD3B.A5C1
button 1:3
In the above configuration, dspfarm profile specified maximum conference participants as 8, this means that a maximum of 8 people can participate in any one conference. Each ephone-dn can have 2 channels when configured as “dual-line”, thus 4 ephone-dns will need to be configured to support any conference with 8 parties.
Ephone-dns 21 – 24 are used for meet-me conference, and ephone-dns 31-34 are used for ad-hoc conferencing.
In case we need to have 16 participants in a conference, we have to configure 8 ephone-dns that are dual-line. In case we need to have 32 participants in a conference, we need to configure 16 ephone-dns that are dual-line.
Conference administrator can perform the following: dial in to any conference directly through the conference number, use the “ConfList” softkey to list conference parties, and remove any party from a conference.
Intercom –Cisco voice systems also support single-button push-to-talk and push-to-respond intercom lines. We can create an intercom arrangement between any two (multiline) IP phones that support speakerphone operation
To configure intercom assign a line button on each of the two phones to operate as an intercom line. Pressing the intercom line button selects the line and triggers the autodial function toward the second phone. The receiving phone receives the incoming intercom call on its intercom line. This line auto answers the call and activates the phone in speakerphone mode and sounds a beep.
Below example shows how to configure an intercom between two IP phones.
Router#Show running-config
ephone-dn 1 dual-line
number 1001
name John Smith
ephone-dn 2 dual-line
number 1002
name Jane Smith
ephone-dn 3
number 1111
intercom 1112 label Jane
ephone-dn 4
number 1112
intercom 1111 label John
ephone 12
mac-address 000d.1234.0efc
button 1:1 2:3
ephone 15
mac-address 000d.5678.0dcf
button 1:2 2:4
Above example shows two phones. John’s phone has button 1 as his primary extension line. Button 2 on John’s phone is an intercom line. This line is set to autodial Jane’s phone using the number 1111. The button is labeled “Jane” to show that pressing the button intercoms to Jane.
Jane’s phone is configured to match to John’s phone. Button 1 on Jane’s phone is her primary line. Button 2 is set to autodial John’s phone and shows the label “John” next to the button. The default configuration for an intercom line is that it Autoanswer with mute for any incoming call. Autoanswer can be disabled if required by using no-auto-answer command option.
After Hour – The UC500 series also provide Auto Attendant (AA) services. The standard automated attendant services allows self-service for callers by giving them option to reach faster the right person in shortest time without operator assistance 24 hours a day, 7 days per week, within option to go to operator at any time when further assistance is required.
To configure this service we need to first record the prompt and the upload auto attendant greeting and prompt file. Following command is used to upload greeting /prompt.
cue-3660# ccn copy url ftp://10.100.10.123/XYZ-corp_welcome.wav prompt XYZ-corp_welcome.wav
cue-3660# ccn copy url http://www.server.com/AAgreeting.wav prompt AAgreeting.wav
This command is equivalent to selecting the GUI options Voice Mail > Prompts > Upload from CCA tool.
Call Park – this feature allows creating park slots used as locations where calls will be held temporarily. We can create park slots using the ephone-dn command and by setting the ephone-dn to operate in park-slot mode. Calls parked in a call park slot hear Cisco voice system’s music on hold. We park calls by pressing the park softkey on IP phone when phone call is in connected /busy state. Call park softkey is displayed on phone only if you have created at least one park slot on Cisco voice system. Also, you may need to press the more softkey one or more times on IP phone to display the park softkey.
We can configure park slots to provide a call parked on hold reminder at programmed intervals. The call reminder goes to the phone that originally parked the call by default but we can also configure to park slots to send reminder to a specific phone number as well as to the park originator.
Router#Show running-config
ephone-dn 102
number 711
park-slot timeout 30 limit 20 notify 310 only
In above example we create a single park-slot instance with number 711. It sets the reminder interval to 30 seconds and configures 20 as the maximum number of reminders. Once the maximum number of reminders has been sent (after 20 * 30 = 600 seconds
We can use the ephone-dn secondary number to give your park slot two different extension numbers
Router#Show running-config
ephone-dn 102
number 711 secondary 700
no huntstop
park-slot timeout 30 limit 20 notify 310 only
ephone-dn 102
number 712 secondary 700
no huntstop
Park-slot timeout 30 limits 20 notify 310 only, in this configuration we allowed to use the directed park feature and transfer-park the call to 700. The IP phone display will show the park-slot (primary) number that actually received the call—as in this case, 711 or 712. We can take / pick up the call by using the specific park-slot number (711 or 712), or we can get the first parked call from either park slot by performing a pickup using the shared secondary number, 700.
This concludes our CCNA Voice session on configuring voice system parameters in UC500 series voice systems of cisco. In this lesson we learnt about various voice system features like call park, adhoc conferencing , after hours and so on and how to configure them using CLI.