[cisco-voip] CUCM 6.1 Forwarding

Nick Griffin nick.jon.griffin at gmail.com
Wed Mar 12 15:48:40 EDT 2008


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 <nick.jon.griffin at gmail.com>
> *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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080312/14ce6978/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 43 bytes
Desc: not available
Url : https://puck.nether.net/pipermail/cisco-voip/attachments/20080312/14ce6978/attachment-0001.gif 


More information about the cisco-voip mailing list