Hi Elvind,

In our next major CCA v2.1, we are planning on moving most of the independent features like SIP trunk and voice features to their own menu items on the right hand navigation pane. This will eliminate many of the errors you are seeing with making non-user related changes of the UC500.

Best Regards,

Tomoo

Eivind,

Thank you for your post and saying:

" I also think it is wise to use CCA as much as possible, but it´s just not possible yet"

perhaps more to the point, having to use the CLI is fine - except that it interferes with CCA if you don't "follow the rules" and you get unexpected results that are a lot of work to reslove.

Perhaps if some debug tools were provided this would be less painful, such an error message that lets the user know what exactly CCA was reading before it had a problem - after all it just a CLI "shell" that reads and writes CLI commands.

Matthew

Here is one of the features on the UC520 that has been left out of CCA, but has been supported by all of the IOS releases on the UC520. It is the ability to create a shared extension number with multiple ephone-dns.

Here is how it is configured in CLI (use a dual-line and not a single-line or an octo-line):

!

! Notice the following:

! All of the ephone-dns below have the same number

! The first ephone-dn has preference set to 1, the second ephone-dn has preference set to 2, and so on

! All ephone-dns below are dual-line dns

! All ephone-dns below, including the last one, have huntstop channel set

! All ephone-dns, except for the last ephone-dn, has no huntstop set

! Call forward no answer is configured on all of the ephone-dns, including the last ephone-dn

! Call forward busy is only configured on the last ephone-dn

!

ephone-dn  30  dual-line
call-waiting ring
number 250 no-reg primary
label Group (250)
description 250
preference 1 secondary 1
call-forward noan 299 timeout 20
huntstop channel
no huntstop
ephone-dn  31  dual-line
call-waiting ring
number 250 no-reg primary
label Group (250)
description 250
preference 2 secondary 2
call-forward noan 299 timeout 20
huntstop channel
no huntstop
ephone-dn  32  dual-line
call-waiting ring
number 250 no-reg primary
label Group (250)
description 250
preference 3 secondary 3
call-forward noan 299 timeout 20
huntstop channel
no huntstop
ephone-dn  33  dual-line
call-waiting ring
number 250 no-reg primary
label Group (250)
description 250
preference 4 secondary 4
call-forward busy 299
call-forward noan 299 timeout 20
huntstop channel

!

!

!

! Adding the ephone-dns of the shared extension using separate line appearances

ephone 1

button 2:30 3:31 4:32 5:33

! Adding the ephone-dns of the shared extension using an overlay appearance with call waiting

ephone 2

button 2c30,31,32,33

The above configuration will work with the 4.2.x, 7.0.x, and 7.1.x releases on the UC520. Will CCA be supporting this in the future? I am aware of at least two alternatives supported by CCA:

• Shared octo-line - This requires the 7.0.0 release or later and is currently not supported on some of the phone models, such as the Cisco 7931G
• Parallel blast group - This requires the 7.0.0 release or later, but will work on all of the phones

Advantages of shared extensions with multiple ephone-dns:

• Known to work with the 7900 series phones, Cisco IP Communicator, and Cisco SPA525G phone. As far as I know, the above configuration should work on other phones, such as the Cisco 524G phone, but I have not tested the configuration with other models.
  
• Will work with the 4.2.x, 7.0.x, and 7.1.x release
• Supports night service call forwarding (parallel blast groups and hunt groups do not support night service call forwarding)