If I follow the thread, you want to hide the extension number and calling party name for extension 67129 from any internal extension that this phone dials.
The translation pattern you describe in the first post doesn't accomplish this task. You need to use translation patterns that 67129 dials. Not the other way around. In 6.1, Transformation Patterns (which may be what you were thinking of) won't address your need either.
You can test the following out:
Create a Translation Pattern:
Pattern:
Partition: one that your phone can dial directly (e.g. 67130)
CSS: one that points to another phone line on your cluster
In the translation pattern, make sure that "Calling Line ID Presentation" and "Calling Name Presentation" under the "Calling Party Transformations" section are both set to Restricted.
Using the example numbers. From 67129 dial 1#. The call should be presented to extension 67130 as "Private". You will not see the 67129 on the LCD nor will it show in Missed/Received calls.
That tests the "theory", the bigger problem is introducing this type of routing into your particular dial plan so that it can be leveraged by more than one extension. Duplicating patterns and other DP objects to simply block CLID from one phone may not be the wisest move.
So, what you could do is create a translation pattern that is a "feature code" of sorts. That would allow users to "block" CLID by their choosing. You could create a translation like:
*68XXXXX
Then *68 is the "block my CLID" feature access code followed by 5 digits (assuming you have a uniform dial plan). Just make sure your Restrict the calling party fields (both of them).
You could still use COR configurations to only allow certain folks access to this feature code.
Regards,
Bill
(http://www.netcraftsmen.net/resources/blogs/blogger/William%20Bell/)
