Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Cisco: VOIP

internal numbers ID masking

 

 

Cisco voip RSS feed   Index | Next | Previous | View Threaded


David.Grullon at co

Apr 4, 2006, 2:25 PM

Post #1 of 14 (2544 views)
Permalink
internal numbers ID masking

I am trying to mask a number internally, extension to extension.

Thanks
Dave


ealeatherman at gmail

Apr 4, 2006, 6:17 PM

Post #2 of 14 (2485 views)
Permalink
Re: internal numbers ID masking [In reply to]

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> wrote:
>
> I am trying to mask a number internally, extension to extension.
>
> *Thanks*
> *Dave*
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>


--
Ed Leatherman
IP Telephony Coordinator
West Virginia University
Telecommunications and Network Operations


ealeatherman at gmail

Apr 4, 2006, 6:19 PM

Post #3 of 14 (2483 views)
Permalink
Re: internal numbers ID masking [In reply to]

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> 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> wrote:
>
> > I am trying to mask a number internally, extension to extension.
> >
> > *Thanks*
> > *Dave*
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip [at] puck
> > 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


Andrew.Riley at alphawest

Apr 4, 2006, 6:23 PM

Post #4 of 14 (2494 views)
Permalink
Re: internal numbers ID masking [In reply to]

Theres a CCO doc that talks about this process for the Hospitality
industry that will do what you are asking.



_____

From: cisco-voip-bounces [at] puck
[mailto:cisco-voip-bounces [at] puck] On Behalf Of Ed Leatherman
Sent: Wednesday, 5 April 2006 11:18 AM
To: Grullon, David
Cc: cisco-voip [at] puck
Subject: Re: [cisco-voip] internal numbers ID masking



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> wrote:

I am trying to mask a number internally, extension to extension.

Thanks
Dave


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






--
Ed Leatherman
IP Telephony Coordinator
West Virginia University
Telecommunications and Network Operations


Andrew.Riley at alphawest

Apr 4, 2006, 6:42 PM

Post #5 of 14 (2493 views)
Permalink
Re: internal numbers ID masking [In reply to]

Bat the external phone number mask... might break AAR though



_____

From: cisco-voip-bounces [at] puck
[mailto:cisco-voip-bounces [at] puck] On Behalf Of Ed Leatherman
Sent: Wednesday, 5 April 2006 11:20 AM
To: Grullon, David
Cc: cisco-voip [at] puck
Subject: Re: [cisco-voip] internal numbers ID masking



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> 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
<mailto:David.Grullon [at] co> > wrote:

I am trying to mask a number internally, extension to extension.


Thanks
Dave


_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
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


kthorngr at cisco

Apr 4, 2006, 7:03 PM

Post #6 of 14 (2484 views)
Permalink
Re: internal numbers ID masking [In reply to]

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> 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> wrote:
>>>
>>> I am trying to mask a number internally, extension to extension.
>>>
>>> Thanks
>>> Dave
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip [at] puck
>>> 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
> https://puck.nether.net/mailman/listinfo/cisco-voip


lelio at uoguelph

Apr 4, 2006, 7:04 PM

Post #7 of 14 (2472 views)
Permalink
Re: internal numbers ID masking [In reply to]

This is what we are doing as well. I have not find any easier way. Perhaps the only thing I would change is marking the call as 'restricted' so you only have to use one setup. Calls are marked as "From Private".
----- Original Message -----
From: Ed Leatherman
To: Grullon, David
Cc: cisco-voip [at] puck
Sent: Tuesday, April 04, 2006 9:19 PM
Subject: Re: [cisco-voip] internal numbers ID masking


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> 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> wrote:
I am trying to mask a number internally, extension to extension.

Thanks
Dave


_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
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
https://puck.nether.net/mailman/listinfo/cisco-voip


lelio at uoguelph

Apr 4, 2006, 7:06 PM

Post #8 of 14 (2476 views)
Permalink
Re: internal numbers ID masking [In reply to]

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 ; 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> 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> wrote:


I am trying to mask a number internally, extension to extension.

Thanks
Dave

_______________________________________________
cisco-voip mailing list
cisco-voip [at] puck
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
https://puck.nether.net/mailman/listinfo/cisco-voip



------------------------------------------------------------------------------


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


kthorngr at cisco

Apr 5, 2006, 5:18 AM

Post #9 of 14 (2498 views)
Permalink
Re: internal numbers ID masking [In reply to]

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 ; 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> 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> wrote:
>>>>>
>>>>> I am trying to mask a number internally, extension to extension.
>>>>>
>>>>> Thanks
>>>>> Dave
>>>>>
>>>>> _______________________________________________
>>>>> cisco-voip mailing list
>>>>> cisco-voip [at] puck
>>>>> 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
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip [at] puck
>> https://puck.nether.net/mailman/listinfo/cisco-voip


ealeatherman at gmail

Apr 5, 2006, 5:41 PM

Post #10 of 14 (2494 views)
Permalink
Re: internal numbers ID masking [In reply to]

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> 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 ; 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> 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> wrote:
> >>>>>
> >>>>> I am trying to mask a number internally, extension to extension.
> >>>>>
> >>>>> Thanks
> >>>>> Dave
> >>>>>
> >>>>> _______________________________________________
> >>>>> cisco-voip mailing list
> >>>>> cisco-voip [at] puck
> >>>>> 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
> >>> https://puck.nether.net/mailman/listinfo/cisco-voip
> >> _______________________________________________
> >> cisco-voip mailing list
> >> cisco-voip [at] puck
> >> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>


--
Ed Leatherman
IP Telephony Coordinator
West Virginia University
Telecommunications and Network Operations


ealeatherman at gmail

Sep 11, 2008, 12:09 PM

Post #11 of 14 (1912 views)
Permalink
Re: internal numbers ID masking [In reply to]

Sorry to revive an old thread, but running into a "new" snag in this, at
least something we hadn't considered before.

I set up internal caller-ID masks per below, normally everything is fine.
But we've discovered that if a secretary transfers a caller in to the person
who's number is supposed to be masked, their true number is displayed on the
calling party's IP Phone as the connected number. Don't ask me how we've
missed that one for the passed 4 years.

I've changed my translation pattern to restrict the "connected line id
presentation" which did the trick.. but it totally scewed up their voicemail
now. If a masked party calls someone and gets forwarded to voicemail, they
get Unity's opening greeting rather than the called person's mailbox. When i
look at the call viewer in unity, it looks like the forwarding number is
blank. What would the connected party line ID of the caller have to do with
the forwarding number?

CCM 5.1.3
Unity 4.2


On Wed, Apr 5, 2006 at 8:41 PM, Ed Leatherman <ealeatherman [at] gmail>wrote:

> 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> 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 ; 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> 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> wrote:
>> >>>>>
>> >>>>> I am trying to mask a number internally, extension to extension.
>> >>>>>
>> >>>>> Thanks
>> >>>>> Dave
>> >>>>>
>>
>
Ed Leatherman
Assistant Director, Voice Services
West Virginia University
Telecommunications and Network Operations


lelio at uoguelph

Sep 11, 2008, 12:15 PM

Post #12 of 14 (1908 views)
Permalink
Re: internal numbers ID masking [In reply to]

I set up translations that bypass the masking, like police and voicemail.

But that being said, I should look at our translations to see if I block connected party presentation!

Lelio
--------------------------------------------------------------------------------
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...seen on a Geek Squad patch cord: "While it is the same length, this 7' crossover cable
is not regulation issue for most competitive Manhattan double dutch leagues.
----- Original Message -----
From: Ed Leatherman
To: cisco-voip [at] puck
Sent: Thursday, September 11, 2008 3:09 PM
Subject: Re: [cisco-voip] internal numbers ID masking


Sorry to revive an old thread, but running into a "new" snag in this, at least something we hadn't considered before.

I set up internal caller-ID masks per below, normally everything is fine. But we've discovered that if a secretary transfers a caller in to the person who's number is supposed to be masked, their true number is displayed on the calling party's IP Phone as the connected number. Don't ask me how we've missed that one for the passed 4 years.

I've changed my translation pattern to restrict the "connected line id presentation" which did the trick.. but it totally scewed up their voicemail now. If a masked party calls someone and gets forwarded to voicemail, they get Unity's opening greeting rather than the called person's mailbox. When i look at the call viewer in unity, it looks like the forwarding number is blank. What would the connected party line ID of the caller have to do with the forwarding number?

CCM 5.1.3
Unity 4.2



On Wed, Apr 5, 2006 at 8:41 PM, Ed Leatherman <ealeatherman [at] gmail> wrote:

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> 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 ; 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> 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> wrote:
>>>>>
>>>>> I am trying to mask a number internally, extension to extension.
>>>>>
>>>>> Thanks
>>>>> Dave
>>>>>


Ed Leatherman
Assistant Director, Voice Services
West Virginia University
Telecommunications and Network Operations



------------------------------------------------------------------------------


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


ealeatherman at gmail

Sep 19, 2008, 10:52 AM

Post #13 of 14 (1847 views)
Permalink
Re: internal numbers ID masking [In reply to]

FYI after a case with TAC, they determined that it is working as directed.
So you can mask caller ID, but not connected party line information without
screwing up voicemail. It's "working as intended" and the only option is to
create a seperate voicemail profile mask for each phone that specifies the
extension number, and/or try to get a product enhancement request placed.

So if I want this to work at all I basically need 4000 individual voicemail
profiles for every line on my system. I don't recall any quick way to BAT
create those.

Not satisfactory but not sure at this point what I can even do about it. It
seems more like a bug than a new feature request, but I don't claim to
understand the inner workings of how connected line ID relates to the
forwarding number.

If I think of something else I'll pass it along though, i'm sure others
might run into this at some point.



On Thu, Sep 11, 2008 at 3:15 PM, Lelio Fulgenzi <lelio [at] uoguelph> wrote:

> I set up translations that bypass the masking, like police and voicemail.
>
> But that being said, I should look at our translations to see if I block
> connected party presentation!
>
> Lelio
>
> --------------------------------------------------------------------------------
> Lelio Fulgenzi, B.A.
> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> ...seen on a Geek Squad patch cord: "While it is the same length, this 7'
> crossover cable
> is not regulation issue for most competitive Manhattan double dutch
> leagues.
>
> ----- Original Message -----
> *From:* Ed Leatherman <ealeatherman [at] gmail>
> *To:* cisco-voip [at] puck
> *Sent:* Thursday, September 11, 2008 3:09 PM
> *Subject:* Re: [cisco-voip] internal numbers ID masking
>
> Sorry to revive an old thread, but running into a "new" snag in this, at
> least something we hadn't considered before.
>
> I set up internal caller-ID masks per below, normally everything is fine.
> But we've discovered that if a secretary transfers a caller in to the person
> who's number is supposed to be masked, their true number is displayed on the
> calling party's IP Phone as the connected number. Don't ask me how we've
> missed that one for the passed 4 years.
>
> I've changed my translation pattern to restrict the "connected line id
> presentation" which did the trick.. but it totally scewed up their voicemail
> now. If a masked party calls someone and gets forwarded to voicemail, they
> get Unity's opening greeting rather than the called person's mailbox. When i
> look at the call viewer in unity, it looks like the forwarding number is
> blank. What would the connected party line ID of the caller have to do with
> the forwarding number?
>
> CCM 5.1.3
> Unity 4.2
>
>
> On Wed, Apr 5, 2006 at 8:41 PM, Ed Leatherman <ealeatherman [at] gmail>wrote:
>
>> 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> 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 ; 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> 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>
>>> wrote:
>>> >>>>>
>>> >>>>> I am trying to mask a number internally, extension to extension.
>>> >>>>>
>>> >>>>> Thanks
>>> >>>>> Dave
>>> >>>>>
>>>
>>
> Ed Leatherman
> Assistant Director, Voice Services
> West Virginia University
> Telecommunications and Network Operations
>
> ------------------------------
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>


--
Ed Leatherman
Assistant Director, Voice Services
West Virginia University
Telecommunications and Network Operations


ealeatherman at gmail

Oct 6, 2008, 12:29 PM

Post #14 of 14 (1717 views)
Permalink
Re: internal numbers ID masking [In reply to]

Follow-up to this problem, in case anyone else runs into it.

TAC helped me come up with a work-around. while it doesn't completely fix
the issue it at least solves the specific users' problems that we were
having.

Phone A - Secretary, published number
Phone B - Executive, unpublished number, caller ID masked for on and offnet
calls

Specific problem.. callers desiring to speak with the executive would call
the published number (Phone A). If appropriate, secretary would transfer the
caller to the executives line on Phone B. If the caller is on an IP Phone,
once the call is connected, the caller can see the executives dn as the
"connected line ID" on their IP Phone screen. Any attempts to restrict
connected line ID with a translation pattern resulted in voicemail not
working correctly (the "forwarding number" gets cleared for a call if it
passes through a translation pattern that restricts the connected line ID).

Workaround for us was:
Apply a translation pattern to the secretary's CSS such that if he/she calls
or transfers to the executive's line, it restricts BOTH the connected line
ID and the connected name presentation. For some reason, this only works if
both of those settings are restricted. Then, create a voicemail profile
specifically for the executive's directory number that specifices the line
number as the number mask, and apply it to the executive's line. This isn't
very scalable and only works if you have some control over who will be
transfering to the executive. But it seems to work out for us at least.

If the executive calls out somewhere and gets transfered to another IP
phone, the connected line ID will still be displayed. Fixing this situation
would seem to require an individual voicemail profile for every unique DN on
the phone system. Yuck.

According to the developers via TAC, the connected line id restriction
settings are working as intended, and if we want it to function with Unity
we'll have to put in a feature request through our account team. Still seems
like a flaw to me, but i'm going to at least let my account folks know about
the problem and see what our chances are for getting the "feature" added
some day. I need to review the feature requests out on CIPTUG's system also
to see if there is a request like this already in place so I can throw some
more votes at it.

Ed

On Fri, Sep 19, 2008 at 1:52 PM, Ed Leatherman <ealeatherman [at] gmail>wrote:

> FYI after a case with TAC, they determined that it is working as directed.
> So you can mask caller ID, but not connected party line information without
> screwing up voicemail. It's "working as intended" and the only option is to
> create a seperate voicemail profile mask for each phone that specifies the
> extension number, and/or try to get a product enhancement request placed.
>
> So if I want this to work at all I basically need 4000 individual voicemail
> profiles for every line on my system. I don't recall any quick way to BAT
> create those.
>
> Not satisfactory but not sure at this point what I can even do about it. It
> seems more like a bug than a new feature request, but I don't claim to
> understand the inner workings of how connected line ID relates to the
> forwarding number.
>
> If I think of something else I'll pass it along though, i'm sure others
> might run into this at some point.
>
>
>
>
> On Thu, Sep 11, 2008 at 3:15 PM, Lelio Fulgenzi <lelio [at] uoguelph> wrote:
>
>> I set up translations that bypass the masking, like police and
>> voicemail.
>>
>> But that being said, I should look at our translations to see if I block
>> connected party presentation!
>>
>> Lelio
>>
>> --------------------------------------------------------------------------------
>> Lelio Fulgenzi, B.A.
>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> ...seen on a Geek Squad patch cord: "While it is the same length, this 7'
>> crossover cable
>> is not regulation issue for most competitive Manhattan double dutch
>> leagues.
>>
>> ----- Original Message -----
>> *From:* Ed Leatherman <ealeatherman [at] gmail>
>> *To:* cisco-voip [at] puck
>> *Sent:* Thursday, September 11, 2008 3:09 PM
>> *Subject:* Re: [cisco-voip] internal numbers ID masking
>>
>> Sorry to revive an old thread, but running into a "new" snag in this, at
>> least something we hadn't considered before.
>>
>> I set up internal caller-ID masks per below, normally everything is fine.
>> But we've discovered that if a secretary transfers a caller in to the person
>> who's number is supposed to be masked, their true number is displayed on the
>> calling party's IP Phone as the connected number. Don't ask me how we've
>> missed that one for the passed 4 years.
>>
>> I've changed my translation pattern to restrict the "connected line id
>> presentation" which did the trick.. but it totally scewed up their voicemail
>> now. If a masked party calls someone and gets forwarded to voicemail, they
>> get Unity's opening greeting rather than the called person's mailbox. When i
>> look at the call viewer in unity, it looks like the forwarding number is
>> blank. What would the connected party line ID of the caller have to do with
>> the forwarding number?
>>
>> CCM 5.1.3
>> Unity 4.2
>>
>>
>> On Wed, Apr 5, 2006 at 8:41 PM, Ed Leatherman <ealeatherman [at] gmail>wrote:
>>
>>> 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> 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 ; 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> 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>
>>>> wrote:
>>>> >>>>>
>>>> >>>>> I am trying to mask a number internally, extension to extension.
>>>> >>>>>
>>>> >>>>> Thanks
>>>> >>>>> Dave
>>>> >>>>>
>>>>
>>>
>> Ed Leatherman
>> Assistant Director, Voice Services
>> West Virginia University
>> Telecommunications and Network Operations
>>
>> ------------------------------
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip [at] puck
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>
>
> --
> Ed Leatherman
> Assistant Director, Voice Services
> West Virginia University
> Telecommunications and Network Operations
>



--
Ed Leatherman
Assistant Director, Voice Services
West Virginia University
Telecommunications and Network Operations

Cisco voip RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.