just to add to the info from Rob there has always been a kind of loop prevention system embedded, CUCM will only allow 12 hops before returning reorder.
my guess is you have the partition from your own phone with higher preference than the one from the manager in the CSS. if that's the case it'w WAD, on your scenario CUCM won't even go thru the 12 hops as it already knows it's looped.
I don't think you are getting the "loop detected" message in the display because this is not detected as a "loop".
What this mechanism is trying to prevent is this;
I decide to go fo Coffee, so I try to Call Forward my phone DN 5555 to Gonz @ 4444. Meanwhile Gonz @ 4444 has left for a meeting so he has Call Forwarded to Java @ 3333. Java is attending the same meeting so he has set Call Forward to me @ 5555.
When I attempt to Call Forward in this scenario (because of the existing CFWD's that Gonz and Java have set) I will receive the "Loop Detected" message on my phone display.
Here are the notes for Call Forward Loop Detection. Please note the line *** below;
Call Forward All Loop Prevention and Breakout
Cisco Unified Communications Manager prevents Call Forward All activation on the phone when a Call Forward All loop is identified. For example, Cisco Unified Communications Manager identifies a call forward loop when the user presses the CFA softkey on the phone with directory number 1000 and enters 1001 as the CFA destination, and 1001 has forwarded all calls to directory number 1002, which has forwarded all calls to directory number 1003, which has forwarded all calls to 1000. In this case, Cisco Unified Communications Manager identifies that a loop occurs and prevents CFA activation on the phone with directory number 1000.
Call Forward All loops do not impact call processing because Cisco Unified Communications Manager supports CFA loop breakout, which ensures that if a CFA loop is identified, the call goes through the entire forwarding chain, breaks out of the Call Forward All loop, and completes as expected, even if CFNA, CFB, or other forwarding options are configured along with CFA for one of the directory numbers in the forwarding chain. For example, the user for the phone with directory number 1000 forwards all calls to directory number 1001, which has forwarded all calls to directory number 1002, which has forwarded all calls to directory number 1000, thus creating a CFA loop. In addition, directory number 1002 has configured CFNA to directory number 1004. The user at the phone with directory number 1003 calls directory number 1000, which forwards to 1001, which forwards to 1002. Cisco Unified Communications Manager identifies a CFA loop, and the call, which breaks out of the loop, tries to connect to directory number 1002. If the No Answer Ring Duration timer expires before the user for the phone with directory number 1002 answers the call, Cisco Unified Communications Manager forwards the call to directory number 1004.
For a single call, Cisco Unified Communications Manager may identify multiple Call Forward All loops and attempts to connect the call after each loop is identified.
If Call Forward All activation occurs in Cisco Unified Communications Manager Administration or the Cisco Unified Communications Manager User Options, Cisco Unified Communications Manager does not prevent the CFA loop.
***If the same directory number exists in different partitions, for example, directory number 1000 exists in partitions 1 and 2, Cisco Unified Communications Manager allows the CFA activation on the phone.
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: firstname.lastname@example.org 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 ...