<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1458" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>North America has <STRONG>Vertical Service
Codes</STRONG> which are listed <A
href="http://www.nanpa.com/number_resource_info/vsc_assignments.html">here</A>.
These are two digit codes prefixed by a * for touch tone or 11 for pulse. In
this case, it would be *67, Calling Number Delivery Blocking. </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>In this case, you could create a translation
pattern or route pattern, that would capture 9*67.@ and send it out to the PSTN
with 'Calling Party Presentation' set to restricted with a Pre-Dot drop. I
haven't tested this yet, but I don't see why it wouldn't work. The only thing
you wouldn't get is the familiar 'triple tone' that signifies to the calling
party that your request has been activated.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>To block <STRONG>all</STRONG> calls, you can simply
choose to set the "Calling Party Presentation" to restricted on either your
route patterns, route list or gateways. With the last always taking precedent
over the first. You will always have to supply a valid DN for outgoing calls
though, the PSTN wants to see that, and it is always transmitted, it's just the
presentation bit that gets set to restricted. This is of course, for tracking
who called who. The end caller will never see the number though.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=david_ready@mobileinnovations.com.au
href="mailto:david_ready@mobileinnovations.com.au">READY, David</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=cisco-voip@puck.nether.net
href="mailto:'cisco-voip@puck.nether.net'">'cisco-voip@puck.nether.net'</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, August 17, 2004 8:12
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> [cisco-voip] Re: How to Block
Caller-ID on 2600/5300 with T1/E1</DIV>
<DIV><BR></DIV>On Tue, Aug 17, 2004 at 12:10:36PM +0200, Arnd Vehling
wrote:<BR>> Hi,<BR>> <BR>> does anyone know how to block the
caller-id transmission<BR>> per default for all outgoing calls over an T1
Interface<BR>> on a cisco 2600/5300?<BR>> <BR>> When "googling"
cisco.com i only see a "caller-id" command<BR>> for analog ports but no
hint on how to block outgoing<BR>> caller-id on T1/E1
ports.<BR><BR>Hi,<BR><BR>Another way of doing it is....... In Australia we can
dial a 1831 (turn CLI<BR>off on that call only) and 1832 (send CLI on this
call only) prefix before<BR>the outgoing number to block/unblock CLI. I know
our fine-feathered fellow<BR>members of the 'coalition of willing' [USA] don't
like to follow most<BR>international standards [wink] but if your carrier/s
have something similir<BR>you could prefix 1831 to all outgoing calls and your
carrier's switch will<BR>make all calls
private.<BR><BR>David<BR>_______________________________________________<BR>cisco-voip
mailing list<BR><A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR></BLOCKQUOTE></BODY></HTML>