[cisco-voip] CUCM 6.1 Forwarding

Wed Mar 12 17:39:00 EDT 2008

Sounds like a great opportunity for a TAC case to me.  If it is truly  
broken then this is how you get a bug filed to have it fixed.

-Ryan

On Mar 12, 2008, at 4:24 PM, Nick Griffin wrote:

Lelio, I'm catching what your tossing, but if you look under service  
parameters you will see what I'm referring to. This is right out of  
the 6.x srnd.

•With Activating Device/Line CSS

If you prefer to use the combination of the Directory Number Calling  
Search Space and Device Calling Search Space without explicitly  
configuring a Forward All Calling Search Space, select With  
Activating Device/Line CSS for the Calling Search Space Activation  
Policy. With this option, when Forward All is activated from the  
phone, the Forward All Calling Search Space and Secondary Calling  
Search Space for Forward All are automatically populated with the  
Directory Number Calling Search Space and Device Calling Search Space  
for the activating device. The two calling search spaces are  
concatenated, and the resulting calling search space is used to  
validate the number entered as a Call Forward All destination. For  
further details, see Building Classes of Service for Unified CM with  
the Line/Device Approach.

With this configuration (Calling Search Space Activation Policy set  
to With Activating Device/Line), if the Forward All Calling Search  
Space is set to None when forward-all is activated through the phone,  
the combination of Directory Number Calling Search Space and  
activating Device Calling Search Space is used to verify the forward- 
all attempt.

On Wed, Mar 12, 2008 at 2:51 PM, Lelio Fulgenzi <lelio at uoguelph.ca>  
wrote:
Not sure what you mean by "calling search space activation policy".

You have a choice, don't configure the two forwarding CSS fields and  
you get no forwarding, or you configure the two forwarding CSS fields  
(or at least one of them) and you get a restricted forwarding.

I think others are feeling the pain where they went ahead with their  
upgrade and people lost their forwarding b/c they left it blank.

Lelio
------------------------------------------------------------------------ 
--------
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Java-Clavis-Domus Theorem: The ability to keep your hands on the home  
keys is inversely
related to the amount of caffeine ingested in the last 30 minutes.
----- Original Message -----
From: Nick Griffin
To: Lelio Fulgenzi
Cc: cisco-voip at puck.nether.net
Sent: Wednesday, March 12, 2008 3:48 PM
Subject: Re: [cisco-voip] CUCM 6.1 Forwarding

Right, but I thought the point of the "Calling Search Space  
Activation Policy" was to over-ride this behavior. Can anyone confirm  
or deny ?

On Wed, Mar 12, 2008 at 2:36 PM, Lelio Fulgenzi <lelio at uoguelph.ca>  
wrote:
I think someone one the list mentioned this a while back. In pre 5/6  
if you had nothing configured on for forwarding CSS it used the  
device/line CSS, basically following what the rest of the phone had.  
With 5/6 you must specifically assign it something. I believe there  
are two forwarding CSS so you can use the device/line approach with  
forwarding as well.

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/ 
5_0_1/501cmrn.html#wp54174

Call Forwarding Enhancements

The Call Forward All (CFA) enhancement introduces a secondary Calling  
Search Space (CSS) for the Call Forward All field. The secondary CSS  
for CFA combines with the existing CSS for CFA to allow the support  
of alternate CSS system configuration.

When CFA is activated, only the primary and secondary CSS for CFA  
gets used to validate the CFA destination and redirect the call to  
the CFA destination. If these fields are empty, then null CSS gets  
used. The combination of the line CSS and device CSS no longer gets  
used when CSS for CFA is None. Only CSS fields that are configured in  
the primary CSS for CFA and the secondary CSS for CFA fields get used.

For more information, refer to Cisco CallManager Features and  
Services Guide 5.0.

Cisco CallManager Administration Configuration Tips

•You must configure either primary Forward All Calling Search Space  
or Secondary Forward All Calling Search Space or both for Call  
Forward All to work properly. The system uses these concatenated  
fields (Primary CFA CSS + Secondary CFA CSS) to validate the CFA  
destination and forward the call to the CFA destination.

Lelio
------------------------------------------------------------------------ 
--------
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Java-Clavis-Domus Theorem: The ability to keep your hands on the home  
keys is inversely
related to the amount of caffeine ingested in the last 30 minutes.
----- Original Message -----
From: Nick Griffin
To: cisco-voip at puck.nether.net
Sent: Wednesday, March 12, 2008 3:26 PM
Subject: [cisco-voip] CUCM 6.1 Forwarding

Whats the deal with the CFA on CUCM 5/6? I thought if you enabled the
service parameter "Calling Search Space Activation Policy" for "with
activating Device/Line CSS" It would use the settings from the device  
for
forwarding calls. I find I must set a CSS on the forwarding  
containing the
part I wish to reach. Am I missing something here? Thoughts appreciated.

My goal is to have a CFA that is the same for every site, with the  
ability
to call local, and use the appropriate GW set at the device. Thoughts
appreciated!

I'm grabbing a debug next. TIA

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080312/24e34730/attachment-0001.html 