For those of us that only work in the SMB space, the only practical achievable certification is: UC Express, which as you state, is end of life, so cannot be obtained. UC Advanced is also EOL. Due to this, and a number of lacking configuration options which seem to become more and more restrictive with each CCA/Software pack release, we have dropped the product portfolio entirely for new customers. The latest one we have is that you now can't use an AA to transfer to a BACD when using a SIP trunk. This is basic stuff, but apparently 'unsupported'. I have voiced my disapproval of this strategy at the highest level, to no avail, however it seems the UC540/560 must be destined for EOL themselves in the near future. ... View more

Except you can't get the specialisation, as the certification has expired and has not been replaced. ... View more

Firstly, let me preface this by saying the Cisco no longer provide ANY CLI support to UC540/UC560 products, as support has fully transitioned to the SBSC, who only support GUI via CCA latest versions, as per the brave new world of Cisco Small Business Support Centre Policy. I will leave the politics and conjecture on that matter alone for the moment... In reality, 3 digit dial-plan's have got be the simplest CME configuration to setup, with the slight exception in regard to some issues you can run into with DTMF. DON'T TRY THIS AT HOME (as you will be without support from Cisco if you do any CLI configuration), but in theory, see the following example: Let's imagine you are in Sydney on a UC560 and have a UC540 in Brisbane. All UC boxes need to be IP addressed accordingly. This will not work if you have all of your systems configured for the default Voice IP range of 10.1.1.1 / CUE 10.1.10.1 for example. Once you have configured your Voice VLANs on each system with distinct IP ranges (this is key), and have setup your routing table so you can route around quite happily, you configure dial-peers for 3 digit dialling as follows: dial-peer voice 9300 voip description ** VoIP Trunk to Brisbane Office Extension Range destination-pattern [3].. session target ipv4:10.1.4.1 dtmf-relay h245-alphanumeric codec g711ulaw no vad ! The above config will send any call destined for the 300-399 range to terminate on the Brisbane UC540's Voice VLAN IP address. ! It's also best to setup a specific dial-peer for your CUE voicemail at the remote site, forcing SIP, and we've had good success with dtmf-relay rtp-nte in this scenario: dial-peer voice 9390 voip description ** CUE at BNE Voicemail Pilot Number ** destination-pattern 390 b2bua session protocol sipv2 session target ipv4:10.1.14.1 dtmf-relay rtp-nte codec g711ulaw no vad There's no reason you couldn't force all calls to go over SIP and force rtp-nte on a single dial-peer, if your Unity voicemail is in the same extension range. That might look like this: dial-peer voice 9300 voip description ** VoIP Trunk to Brisbane Office Extension Range destination-pattern [3].. b2bua session protocol sipv2 session target ipv4:10.1.14.1 dtmf-relay rtp-nte codec g711ulaw no vad That's it. You're done. You apply a similar reverse configuration on the other sites, and you have 3-digit internal dialling. Apparently we are stupid for requesting such a thing, and Cisco have absolutely no interest in including it in CCA. I am pleased to see we aren't the only people who want this functionality. You can also get clever and setup toll bypass (don't tell your Telco, they get upset ) by something like the following: dial-peer voice 9301 voip description ** BNE Pattern via VOIP ** destination-pattern 007........ session target ipv4:10.1.4.1 dtmf-relay h245-alphanumeric codec g711ulaw no vad ! The above will send any calls destined for a 07 number to that site to dial out as a local call saving on STD/IDD charges. Note we use 0 as our outside line access digit, so replace the first digit in the destination-pattern to match yours. I hope this gives you an idea about how you might do this in theory (but not practice) just in case you wanted to do this in your customer lab environment. Also, best keep your dial-peers up in the high ranges. We've used the 9000 range which seems to steer well clear of CCA (at least until the next release when it may all change). Note: None of the above config is supported by Cisco, and we provide it as-is with no warranty either express or implied. Cheers, Scott ... View more