UC500.com

Before I was configuring UC520's, I was familiar with the Linksys One system. The Linksys One system had what was called a group (in the 2.0 or 2.1 releases), or a simultaneous ring group (in the 2.2 release). A group extension in Linksys One is an extension that rings on one or more phones, is separate from any personal extensions, contains one or more users, and can have a voicemail box associated with the group extension. Cisco Unified Communications Manager Express and Cisco Unity Express, which is included on the UC520 and available on other routers, has capabilities equivalent to a group in Linksys One. Cisco Configuration Assistant is not currently capable of configuring this feature, but it can be configured on the UC520 through the command line interface.

Here is how you configure a group line that contains 4 line appearances on a UC520:

! First appearance of a group line
ephone-dn 30 dual-line
number 250 no-reg primary
label Agents (250)
description Agents
name Agents
preference 1 secondary 1
call-forward noan 299 timeout 20
corlist incoming user-domestic
huntstop channel
no huntstop
translation-profile incoming CallBlocking
! Second appearance of a group line
ephone-dn 31 dual-line
number 250 no-reg primary
label Agents (250)
description Agents
name Agents
preference 2 secondary 2
call-forward noan 299 timeout 20
corlist incoming user-domestic
huntstop channel
no huntstop
translation-profile incoming CallBlocking
! Third appearance of a group line
ephone-dn 32 dual-line
number 250 no-reg primary
label Agents (250)
description Agents
name Agents
preference 3 secondary 3
call-forward noan 299 timeout 20
corlist incoming user-domestic
huntstop channel
no huntstop
translation-profile incoming CallBlocking
! Fourth appearance of a group line
ephone-dn 33 dual-line
number 250 no-reg primary
label Agents (250)
description Agents
name Agents
preference 4 secondary 4
call-forward noan 299 timeout 20
call-forward busy 299
corlist incoming user-domestic
huntstop channel
translation-profile incoming CallBlocking

Notice the following:
- no huntstop is used in all appearances except for the last appearance
- huntstop channel is configured for all of the above line appearances
- preference 1 secondary 1 is used for the first appearance, preference 2 secondary 2 is used for the second appearance, and so on
- call-forward noan is used on all of the appearances
- call-forward busy is used only on the last appearance
- These appearances are configured as dual-line appearances with huntstop channel enabled so that conferencing and consultative transfer work correctly
- The destination for call-forward noan and call-forward busy are set to 299 (which will forward the calls to the general delivery mailbox for this extension). You can set the destination for call-forward noan and call-forward busy to the auto attendant extension, another group extension, an extension at another site, an individual user extension, or an external phone number.

You need to add the group line appearances to the each phone in the group. You can configure it in one of two ways:

• Each appearance using one button
• One button used for all appearances of the line

To add group line appearances to a phone, where each appearance uses one button, you do the following in the configuration for each phone that is configured in this manner:
ephone <number of ephone>
button 2:<ephone-dn number of first appearance>
button 3:<ephone-dn number of second appearance>
button 4:<ephone-dn number of third appearance>
...

Example:
ephone 1
button 2:30
button 3:31
button 4:32
button 5:33

To add group line appearances, where all appearances for that group use one button, you do the following in the configuration for each phone that is configured in this manner:
ephone <number of ephone>
button 2o<ephone-dn number of each appearance, in order from the first appearance to the last appearance, separated from a comma>

Example:
ephone 2
button 2o30,31,32,33

To configure a general delivery mailbox for the above extension:
1. Create a new CUE group. This can be created through either the command line interface or by using the CUE Web GUI.
2. Grant the Manage Prompts permission to the new CUE group, either though the command line interface or the CUE Web GUI.
3. Create a general delivery mailbox for the new CUE group, either through the command line interface or the CUE Web GUI.
4. Set the extension of the new group to the extension created in the previous step. This will associate the extension with the general delivery mailbox.
5. Add the appropriate users to the newly created CUE group. This will enable them to retrieve messages in the general delivery mailbox that was created.

You have now created a group line or a shared line, and optionally a general delivery mailbox associated with a shared line.

With SIP Trunking, CCA does not let you have the main number ring at a destination other than the auto attendant. However, you can work around this by making these changes from the command line interface.

To get the main number to ring a shared line instead of the auto attendant:
1. You should see a dial-peer that looks like the following below, and has a destination-pattern that ends with a $. The dial-peer should look like the following:
dial-peer voice 2003 voip
description ** cue auto attendant PSTN number **
translation-profile outgoing AA_Profile
destination-pattern 19725105000$
b2bua
session protocol sipv2
session target ipv4:10.1.10.1
dtmf-relay sip-notify
codec g711ulaw
no vad

This dial-peer needs to be deleted by going into configuration mode, and then executing the no dial-peer voice 2003 command.

2. You should see another dial-peer that looks like the following below, and has a destination pattern that ends with a $. The dial-peer should look like the following:
dial-peer voice 2005 voip
description Auto Attendant from VoIP
translation-profile outgoing AA_Profile
destination-pattern 19725105000$
b2bua
session protocol sipv2
session target ipv4:10.1.10.1
dtmf-relay sip-notify
codec g711ulaw
no vad

This dial-peer also needs to be deleted, by going into configuration mode, and then executing the no dial-peer voice 2005 command.

3. You should see a dial-peer that looks like the following:
dial-peer voice 1008 voip
description ** AA from SIP Trunk **
translation-profile incoming AA_Profile
voice-class codec 1
voice-class sip dtmf-relay force rtp-nte
session protocol sipv2
session target sip-server
incoming called-number 19725105000
dtmf-relay rtp-nte
ip qos dscp cs5 media
ip qos dscp cs4 signaling
no vad

You should not delete this dial peer. Notice that the main number is in the incoming called-number line. You will modify a voice translation rule to get the main number to ring a shared line. Notice the translation-profile incoming AA_Profile line. This is the translation profile used to route the main number to the correct destination.

4. Here is what the AA_Profile voice translation profile looks like:
voice translation-profile AA_Profile
translate called 2001

Notice the translate called 2001 line. This rule tells the UC520 to translate the called number of an incoming call, using voice translation rule 2001, or routes incoming calls to the correct destination.

5. Here is what voice translation rule 2001 looks like:
voice translation-rule 2001
rule 1 /19725105000/ /298/

6. We need to change voice translation-rule 2001. This will make the main number ring the shared lines instead of the auto attendant. We do this by going into configuration mode and executing the following commands:
voice translation-rule 2001
rule 1 /19725105000/ /250/

7. After executing the above commands, the main number will now ring the shared lines first.