This feature enables routers to provide call-handling support for Cisco Unified IP phones if they lose connection to remote primary, secondary, or tertiary Cisco Unified Communications Manager installations or if the WAN connection is down.
When Cisco Unified SRST functionality is provided by Cisco Unified CME, provisioning of phones is automatic and most Cisco Unified CME features are available to the phones during periods of fallback, including hunt-groups, call park and access to Cisco Unity voice messaging services using SCCP protocol. The benefit is that Cisco Unified Communications Manager users will gain access to more features during fallback without any additional licensing costs.
A limited number of phone features are automatically detected at the time that call processing falls back to the Cisco Unified CME router in SRST mode, and an advantage of SRST fallback support using Cisco Unified CME is that you can choose to prebuild a Cisco Unified CME configuration that contains a number of extensions (ephone-dns) with additional features that you want them to have for some or all of your extensions. The configurations will contain ephone-dn configurations but will not identify which phones (which MAC addresses) will be associated with which ephone-dns (extension numbers).
From your example you have configured auto-provision to none, which essentially means that the DN numbers associated with the phone when fail-over occurs will not be added into the running configuration.
Therefore if you provision your ephone-dn and ephone then you will not have a problem when phones re-register as the ephones will already be tied to an ephone-dn. This unlike provisioning only DNs, as you may find in this instance that when the phone register they will be tied to the wrong number.
I specificially use CME SRST specifically for the huntgroup feature when operating in fallback. I provision all the ephone-dn and ephone information in order create the huntgroup members and appropriate distribution algorithm.
If you require only straight forward fallback, where phones simply require the ability to receive calls and make external calls, then CME SRST is not the option.
In this particular instance configure SRST 'call-manager-fallback'.
With auto-provision all, the ephone-dn's and ephones are created in the running configuration when they re-register. IP Phones will not fallback if you have not configured the SRST reference with CallManager and enabled SRST on the voice-gateway.
If you enable only CME/SRST without registering the gateway within CCM and without specifying a SRST reference for the device pool then you will have to configure the gateway for H323 and full CME, ensuring that you provision TFTP, ringtones, firmware, and both ephone(mac-addresses) and ephone-dn's.
As I have mentioned, SRST Auto-provision all ensure that the mac-addresses are created, and the ephone-dn associate with the mac is inserted into the running configuration.
Prior to this the phones are dependant on CCM for obtaining their firmware and configuration. In the event of SRST, the phones have already loaded their configuration and firmware from CCM, and therefore simply re-register with their existing configuration.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...