[cisco-voip] Call Forward All doesn't like Line CSS when using the line/device approach

[Lelio Fulgenzi]

It was my understanding that these changes were made in order to accommodate the device/line approach in the forwarding scenarios. Right now, in 4.1(3), the forwarding CSS is applied independent of the line or device CSS. 

There is a service parameter in v7.1(5x) (see below) that determines how the forwarding is handled. This can be overridden by the local line settings. 

Two comments: 


    • I don't understand why they wouldn't extend this to all forwarding scenarios, e.g. CFBusy. If I want to CFBusy a line to an off-net number, I still need to keep my "combined" CSS and apply it accordingly. Seems like providing a solution half way. :( I am of course assumming that it doesn't apply, since the docs only refer to it applying to CFA and the others do not have secondary CSS fields. 
    • I recall being told that if you have two shared DNs on different sets that have different device CSS's, i.e. to pick local trunks, and no forwarding CSS is configured, the phone that is registered first basically controls which trunks forwarded calls are sent across. I wonder how that comes into play here. 



CFA CSS Activation Policy: Required Field 

This parameter determines the calling search space that is used when Call Forward All (CFA) is activated through the CFwdAll softkey on the phone. Valid values include: 
With Configured CSS - the primary and secondary CFA Calling Search Space is used. Note that the primary CSS and secondary CSS on line page will not be updated when activating CFA on a phone. 
With Activating Device/Line CSS - the primary and secondary CFA Calling Search Space will be updated with primary line Calling Search Space and activating Device Calling Search Space. Note that the primary CSS and secondary CSS on line page will be updated when activating CFA on a phone, where primaryCSS = lineCSS, and secondaryCSS=device CSS. Special cases include the following: 

1. if lineCSS=null, then primaryCSS=null, and secondaryCSS=device CSS 
2. if deviceCSS=null, then secondaryCSS=null, and primaryCSS = lineCSS 
3. if lineCSS=deviceCSS, then primaryCSS=lineCSS, secondaryCSS=null. 






--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 



From: "Scott Voll" <svoll.voip at gmail.com> 
To: "Jason Aarons (US)" <jason.aarons at us.didata.com> 
Cc: "cisco-voip (cisco-voip at puck.nether.net)" <cisco-voip at puck.nether.net> 
Sent: Wednesday, November 24, 2010 10:33:04 AM 
Subject: Re: [cisco-voip] Call Forward All doesn't like Line CSS when using the line/device approach 


Call Forward all has two CSS; Primary and secondary. But it doesn't look like the two are able to use the device / line approach with the two CSS's. Is this a bug or is this working by design? CM 7.1.5su2 


Scott 


On Tue, Nov 23, 2010 at 6:32 PM, Jason Aarons (US) < jason.aarons at us.didata.com > wrote: 






Original request was to all CfwdAll to go to another internal phone (no cell phones or pstn) via CfwdAll 7704587807 





CallManager 8.03a under Device > Phone > Line DN=770551212, go to line settings then down about halfway the Forward All > Calling Search Space then setting it to LINE-LONGDISTANCE-CSS or any other LINE-X doesn’t work. Has to use DEVICE-CSS or create something new. What does the book say about this CFwdAll and the Line/Device approach? I recall Dialed Number Analzer also doesn’t like Line/Device approach, doesn’t process the Device-CSS. 



Is there a bug id for this? 



Numbers changed to protect the innocent. 







Disclaimer: This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you. 
_______________________________________________ 
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/20101124/c556344d/attachment.html>