<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
AT&T controls that display. You may express preferences but
AT&T is not obligated (frequently does not) follow it. The only
way to conceal calling name is to set the calling number to an
alternate number (assuming you have multiple DID's to your site and
have appropriate SS7 mapping - again depends on AT&T).<br>
<br>
If you owned all of the equipment (CM--PBX) you have performed the
correct steps. Since you don't you will need to make new friends in
those other organizations.<br>
<br>
/Wes<br>
<br>
On Thursday, June 11, 2009 2:36:58 PM, Matthew Linsemier
<a class="moz-txt-link-rfc2396E" href="mailto:mlinsemier@apassurance.com"><mlinsemier@apassurance.com></a> wrote:<br>
<blockquote cite="mid:C656C70A.82EC%25mlinsemier@apassurance.com"
type="cite">
<title>Restricting Outbound Caller Name</title>
<font face="Calibri, Verdana, Helvetica, Arial"><span
style="font-size: 11pt;">All,<br>
<br>
I have created a route pattern that is suppose to restrict Calling Name
Presentation when a phone in a specific partition dials out. However,
for some reason it seems that Telco (AT&T) is still sending the
Calling Name associated with that account even though “Calling Name
Presentation” is set to “restricted”. Should AT&T not be
respecting our UCM’s settings for sending this information? <br>
<br>
We are running UCM 7.0(2) utilizing MGCP for gateway control.<br>
<br>
Please advise,<br>
<br>
Matt</span></font>
<p><font color="#808080" face="Arial" size="1">
<hr></font></p>
<p><font color="#808080"><font face="Arial" size="1">CONFIDENTIALITY
STATEMENT<br>
This communication and any attachments are CONFIDENTIAL and may be
protected by one or more legal privileges. It is intended solely for
the use of the addressee identified above. If you are not the intended
recipient, any use, disclosure, copying or distribution of this
communication is UNAUTHORIZED. Neither this information block, the
typed name of the sender, nor anything else in this message is intended
to constitute an electronic signature unless a specific statement to
the contrary is included in this message. If you have received this
communication in error, please immediately contact me and delete this
communication from your computer. Thank you.</font> </font></p>
<p><font color="#808080">
<hr></font></p>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<br>
</body>
</html>