You are using the default CFA CSS activation policy which is "With Configured CSS" by default. The other option is "With Activating Line/Device CSS". With your 2 screen shots, you'll see the user that has an issue does not have a CFA CSS set (i.e., ) which will not work with this configuration. The other does have a CFA CSS set so hence, no issues. You need to, at a minimum, set a CFA CSS on the line that cannot forward. This is outlined in the SRND and various other administration guides; however, for clarity here's a rundown of how these different settings would behave in everyday operation:
System Default:
With Configured CSS
Phone 1:
Line set to use system default.
When configured normally (i.e., both the primary and secondary CFA CSS are set OR at least the primary CSS is explicitly), forwarding works.
If the primary and secondary CSS configurations are removed, forwarding is broken and users always receive fast busy.
Phone 2:
Line set to use Activating Device/Line CSS.
Phone was set to forward from the phone via CFA softkey. Call forwarding works and the line level configuration is changed in CUCM so that the CFA CSS and secondary CSS are set correctly.
When the forwarding is removed, the line level settings remain intact (i.e., the forward initiated at the phone sets the CFA and secondary CSS for the phone in the DB).
Phone 3:
Line set to use Activating Device/Line CSS.
Phone was forwarded from CUCM Admin. Call forwarding is broken. The CFA CSS and secondary CSS remain unchanged (i.e., None).
Phone was forwarded from CCM User. Call forwarding is broken. The CFA CSS and secondary CSS remain unchanged (i.e., None).
Phone was set to forward from the phone via CFA softkey. Call forwarding works and the line level configuration is changed in CUCM so that the CFA CSS and secondary CSS are set correctly.
When the forwarding is removed, the line level settings remain intact (i.e., the forward initiated at the phone sets the CFA and secondary CSS for the phone in the DB).
Hailey
Please rate helpful posts!
