Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

Silver

Selectively blocking calling line ID

Is there a straightforward way to block the calling line ID for specific phones/lines?

One way I can see of doing this is to have copies of all existing route patterns with calling line ID set to "restricted", and place these route patterns in different partitions and define separate CSSs for lines which do not wish to present their CLID.

A translation pattern could be used to override this behaviour if CLID presentation is required (e.g. calling a line with anonymous call rejection enabled, for example).

The current route patterns allow CLID to be presented in conjunction with the "Use external phone number mask", so call centre agents present the number of the call centre. However, having a blank entry in the external phone number mask doesn't block caller line ID.

4 REPLIES
Bronze

Re: Selectively blocking calling line ID

External Phone number mask is the only way I know. on a per line basis.

In a H.323 ios gateway you can further manipulate clid using dial peers.

Silver

Re: Selectively blocking calling line ID

Is it possible to specify something in the External Phone Number Mask field which will effectively prevent the calling line ID from being displayed (rather than specify an alternative CLI)?

Re: Selectively blocking calling line ID

Normally you have to send *67 to the telco, so maybe a route pattern that allows 8.@, where you prepend *67 to the outbound call? They would normally dial 9.@, but to block outbound caller id you do 8.@

Blocks sending of name and phone number on outgoing individual call. Must be done for each call. (Free.)

To use: *67 (+ number being dialed)

Silver

Re: Selectively blocking calling line ID

I think I've found a solution to this which may be useful for other readers.

In our scenario we have a number of CSSs which dictate class of service.

For example CSS_COS_4 which contains partitions for internal and external route patterns.

This CSS is copied and any partitions containing external route patterns are removed; this CSS is CSS_COS_4_CLI_Withheld. Create a partition called P_COS_4_CLI_Manipulation, into which is placed a single translation pattern which matches 9.! No digit manipulation takes place; its destination Calling Search Space is set to the original CSS_COS_4 and the Calling Number Presentation Indicators are set to "Restricted". This has the effect of withholding CLI for all external calls. Perhaps, slightly surprisingly, the interdigit timeout doesn't come into play (confirmed with Dialed Number Analyzer) as it matches the route patterns in the destination calling search space (CSS_COS_4).

To allow the selective presentation of numbers, another translation pattern in the P_COS_4_CLI_Manipulation partition. This matches *1470.9! (simply because our PBX uses this format, but any other prefix could be used) and strips digits PreDot, but has the Called Number Presentation Indicators to "Default" (or "Allowed") and the destination CSS, CSS_COS_4 is again used to reach the external route patterns in the original class of services CSS.

This way, if a line is required to either present (or withhold) its number by default, then it's just a matter of selecting the correct CSS, CSS_COS_4 or CSS_COS_4_CLI_Withheld in this example, and the original CSSs remain unaffected.

Please rate useful posts.

197
Views
0
Helpful
4
Replies