[cisco-voip] Call Forward All With Line/Device CSS

[Frank Arrasmith]

we have so many people with cellphones that are from out of area, that its
hard to block that sort of thing.  we get a pretty good LD rate and we back
bill to individual departments also.


On Tue, Apr 30, 2013 at 8:56 AM, Eric Pedersen
<PedersenE at bennettjones.com>wrote:

>  If you put your 911 patterns in a device-level CSS and the rest in a
> line-level CSS then you can apply the line CSS to the call forward
> settings. Aren't you concerned about people forwarding their phones to long
> distance numbers though? That's usually a concern too.****
>
> ** **
>
> ** **
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf
> Of *Frank Arrasmith
> *Sent:* 29 April 2013 7:03 PM
> *To:* cisco-voip at puck.nether.net
> *Subject:* [cisco-voip] Call Forward All With Line/Device CSS****
>
> ** **
>
> Hey all, ****
>
>  searched through my archives but couldn't find a solid answer on this.
> We are trying to streamline our build processes and one of the things we
> are considering is switching to "With Activating Device/Line CSS" so we
> don't have to build CFWD CSS's for each individual site.  My only concern
> would be someone forwarding a call to 911 by mistake, which we currently
> block on the CFWD-CSS.  Odds are it would be a pretty rare thing for
> someone to forward all to 911, but i wouldn't put it past a user to do it.
> I have seen them CFWD all to all kinds of weird stuff(particularly from a
> 7925 wi-fi phone they stick in their pocket) , so i figure its only a
> matter of time before they do it, and we would get a hefty fine for bogus
> 911 calls.  ****
>
> Does anybody have a better way to use the "Line/Device" CFWD-CSS but
> prevent calls to unwanted #'s,
>
> OR
>
> At least a quick way to find out if a particular DN was forwarded to a
> particular #(some kind of report)?. ****
>
> OR
>
>  Am i just being a little paranoid?  Other than the 911 forwarding, I
> think this feature is a no brainer, and would be one less thing to build
> and/or have a new engineer mess up, as the case may be.****
>
> The contents of this message may contain confidential and/or privileged
> subject matter. If this message has been received in error, please contact
> the sender and delete all copies. Like other forms of communication,
> e-mail communications may be vulnerable to interception by unauthorized
> parties. If you do not wish us to communicate with you by e-mail, please
> notify us at your earliest convenience. In the absence of such
> notification, your consent is assumed. Should you choose to allow us to
> communicate by e-mail, we will not take any additional security measures
> (such as encryption) unless specifically requested.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130430/c130128b/attachment.html>