Solved: Call Forward CSS

ouhakheme · ‎09-11-2007

Hey guys --

I just installed CM 6.0 last week and I have a question concerning the CSS on the Call Forward options..

Before 6.0, I have been installing 4.1(3) (never 5.x) and in 4.1(3) I never set the CSS on the call forwarding options without any problems.

Now in 6.0 it seems that if I don't set a CSS on the option (for example CFA) the user cannot forward their phones anywhere.

I understand the concept, and was always a bit confused as to why I didn't need one in 4.1, but I also want to make sure that I'm not going crazy. Has this option changed?

Please let me know.

Thanks,

Ohamien

Rob Huffman · ‎09-11-2007

Hi Ohamien,

You are right on the money here (no you are not going crazy :) The Call Forward CSS behaviour changed in the release of CCM 5.x Here is a description;

Cisco CallManager release 5.0 supports a secondary Calling Search Space (CSS) for Call Forward All (CFA) field. The secondary CSS for CFA combines with the existing CSS for CFA to allow the support of the alternate CSS system configuration. When CFA is activated, only the primary and secondary CSS for CFA get used to validate the CFA destination and redirect the call to the CFA destination. If these fields are empty, the null CSS gets used. The combination of the line CSS and device CSS no longer gets used when the CSS for CFA is None. Only the CSS fields that are configured in the primary CSS for CFA and secondary CSS for CFA fields get used. If CFA is activated from the phone, the CFA destination gets validated by using the CSS for CFA and the secondary CSS for CFA and the CFA destination gets written to the database. In previous releases, if the CSS for CFA is empty, the CFA destination got validated against the combination of the line CSS and device CSS of the phone. In this release, when the CFA is activated, the CFA destination always gets validated against the CSS for CFA and the secondary CSS for CFA.

From this 5.0 doc;

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_administration_guide_chapter09186a008053226d.html#wp1098821

Hope this helps!

Rob

View solution in original post

Rob Huffman · ‎09-11-2007

Hi Ohamien,

You are right on the money here (no you are not going crazy :) The Call Forward CSS behaviour changed in the release of CCM 5.x Here is a description;

Cisco CallManager release 5.0 supports a secondary Calling Search Space (CSS) for Call Forward All (CFA) field. The secondary CSS for CFA combines with the existing CSS for CFA to allow the support of the alternate CSS system configuration. When CFA is activated, only the primary and secondary CSS for CFA get used to validate the CFA destination and redirect the call to the CFA destination. If these fields are empty, the null CSS gets used. The combination of the line CSS and device CSS no longer gets used when the CSS for CFA is None. Only the CSS fields that are configured in the primary CSS for CFA and secondary CSS for CFA fields get used. If CFA is activated from the phone, the CFA destination gets validated by using the CSS for CFA and the secondary CSS for CFA and the CFA destination gets written to the database. In previous releases, if the CSS for CFA is empty, the CFA destination got validated against the combination of the line CSS and device CSS of the phone. In this release, when the CFA is activated, the CFA destination always gets validated against the CSS for CFA and the secondary CSS for CFA.

From this 5.0 doc;

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_administration_guide_chapter09186a008053226d.html#wp1098821

Hope this helps!

Rob

ouhakheme · ‎09-11-2007

Beautiful, you're the man Rob.

Thanks for confirming that I'm not crazy!

Ohamien

Majdi Harb · ‎09-11-2007

Hi Ohamein

CUCM 6.0, In the Directory Number Configuration window, in the Call Forward and Call Pickup Setting section, a new option specifies Calling Search Space Activation Policy.

Three possible values exist for this option:

?Use System Default

?With Configured CSS

?With Activating Device/Line CSS

please see this link to get more details on this new enhancement in CUCM 6.0.

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/6_0_1/601acmrn_2.html#wp45143

hth

/majdi