[cisco-voip] Restricting Outbound Caller Name

[Matthew Linsemier]

Wes,

Thanks for the reply... The circuit in question is a PRI, and while we have
several DID blocks on this, AT&T is telling us that it wasn't possible to
have different CNAM for individual DIDs on a PRI in Illinois.  I guess the
next ID so I could preserve sending the right number would be to disable
CNAM all together on that circuit (multitenant issues at this location).

Thanks,

Matt


On 6/11/09 3:33 PM, "Wes Sisk" <wsisk at cisco.com> wrote:

> 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).
> 
> 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.
> 
> /Wes
> 
> On Thursday, June 11, 2009 2:36:58 PM, Matthew Linsemier
> <mlinsemier at apassurance.com> <mailto:mlinsemier at apassurance.com>  wrote:
>>  Restricting Outbound Caller Name All,
>>  
>> 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?
>>  
>> We are running UCM 7.0(2) utilizing MGCP for gateway control.
>>  
>> Please advise,
>>  
>> Matt 
>> 
>>  
>> 
>>  
>> 
>> CONFIDENTIALITY STATEMENT
>> 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.
>>  
>> 
>>  
>> 
>>  
>> 
>> 
>> 
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>   
> 
> 


CONFIDENTIALITY STATEMENT
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090611/e129b67b/attachment.html>