[cisco-voip] internal numbers ID masking
Ed Leatherman
ealeatherman at gmail.com
Wed Apr 5 20:41:42 EDT 2006
I never noticed the "Restricted" setting on there (or didnt realize what it
was for). A lot of the users request that their secretaries numbers show up
instead.. but for the ones that just what "Private" that would be quite a
bit easier to just reuse one. Thanks!
On 4/5/06, Kevin Thorngren <kthorngr at cisco.com> wrote:
>
> Right, I missed Ed's statement of "and of course, all masked as
> something different" :-) As Lelio mentioned the easiest way is to
> Restrict the Calling Line ID and Calling Name (if appropriate) in the
> Translation Pattern. There is no easy mechanism to change the Caller
> ID on a phone by phone basis. One could write a script to query a DB
> and mask the Caller ID based on the source of the call. This way only
> the DB would need to be updated. To make it seamless all internal
> calls should be intercepted by this script but it could be built so
> only those phones that need to mask the Caller ID are intercepted.
> Building a system that would be robust enough to handle the call volume
> might be a challenge and potentially costly.
>
> I would agree that having the ability to restrict the Caller ID info
> from the phone would be best. Interesting changes would be the ability
> to restrict the ID and Name and also an Internal Phone Number Mask.
> Not sure if either of these are on the roadmap.
>
> Kevin
> On Apr 4, 2006, at 10:06 PM, Lelio Fulgenzi wrote:
>
> > It's basically a new partition (and everything else) for every
> > modified mask you want.
> >
> > It would be very handy to have this on a per phone basis.
> >> ----- Original Message -----
> >> From: Kevin Thorngren
> >> To: Ed Leatherman
> >> Cc: cisco-voip at puck.nether.net ; Grullon,David
> >> Sent: Tuesday, April 04, 2006 10:03 PM
> >> Subject: Re: [cisco-voip] internal numbers ID masking
> >>
> >> Out of curiosity - why do you create a new Partition, CSS and
> >> Translation Pattern for each phone that wants to hide the Caller ID?
> >>
> >> Kevin
> >> On Apr 4, 2006, at 9:19 PM, Ed Leatherman wrote:
> >>
> >>> If someone knows a better/cleaner way to do this, I would be
> >>> ecstatic to hear it. this is a big pain in the rear for us, so many
> >>> professors and doctors want their caller ID masked from everyone
> >>> (and of course, all masked as something different)
> >>>
> >>> On 4/4/06, Ed Leatherman <ealeatherman at gmail.com> wrote:This is
> >>> something I wish was easier to do with callmanager. Here is what we
> >>> do..
> >>>>
> >>>> -Make a new partition, we call it MaskCLIDAs<number>
> >>>> -Make a new Calling search space, we call it Device_MaskAs<number>
> >>>> -Put the MaskCLIDAs<Number> partition as the first entry in the new
> >>>> CSS, and then put any additional partitions you would need to call
> >>>> (outbound partitions etc)
> >>>> -Make a Translation pattern that will match all your internal
> >>>> extensions, and use it to modify the calling party number to
> >>>> whatever you like. Make sure you set the new calling search space
> >>>> as something that can call your internal numbers. The new
> >>>> translation pattern should be in your new partition.
> >>>> -Configure the phone with the new CSS
> >>>>
> >>>> basically you want interal callers to hit that new translation
> >>>> pattern when they call another internal number, so that it modifies
> >>>> the calling party number and then proceeds as normal with the call.
> >>>> Otherwise it places outside calls as normal.
> >>>>
> >>>> Does that help? As you can imagine if you do this alot, you get
> >>>> alot of partition/CSS/translation pattern clutter on callmanager.
> >>>>
> >>>> One thing to be careful of is to make sure your masked phones can
> >>>> still call everything they need to (call pickup groups tripped us
> >>>> up on this) with the new CSS. And also make sure they still cannot
> >>>> call things they shouldnt :)
> >>>>
> >>>> On 4/4/06, Grullon, David < David.Grullon at co.galveston.tx.us> wrote:
> >>>>>
> >>>>> I am trying to mask a number internally, extension to extension.
> >>>>>
> >>>>> Thanks
> >>>>> Dave
> >>>>>
> >>>>> _______________________________________________
> >>>>> cisco-voip mailing list
> >>>>> cisco-voip at puck.nether.net
> >>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Ed Leatherman
> >>>> IP Telephony Coordinator
> >>>> West Virginia University
> >>>> Telecommunications and Network Operations
> >>>
> >>>
> >>> --
> >>> Ed Leatherman
> >>> IP Telephony Coordinator
> >>> West Virginia University
> >>> Telecommunications and Network
> >>> Operations_______________________________________________
> >>> 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
>
>
--
Ed Leatherman
IP Telephony Coordinator
West Virginia University
Telecommunications and Network Operations
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20060405/d371823a/attachment-0001.html
More information about the cisco-voip
mailing list