Thanks, Ryan. I think that mirrors what I see.<br><br>I think my original question got lost in the discussion though. Can I present one name to internal destinations and a different one to external destinations?<br><br>Sean<br>
<br><div class="gmail_quote">On Mon, Mar 9, 2009 at 12:13 PM, Ryan Ratliff <span dir="ltr"><<a href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
What I've always told customers is that you can set the name going outbound but beyond that it's out of your control. The far end doesn't have to trust the name you send or even pass it along afaik.<br>
<br>
-Ryan<div><div></div><div class="h5"><br>
<br>
On Mar 9, 2009, at 1:03 PM, Sean Walberg wrote:<br>
<br>
My experience would dictate otherwise. Whatever I set as my Line Display gets shown to the person I call. I've also never submitted anything to my carriers about which name is attached to which phone number.<br>
<br>
Sean<br>
<br>
On Mon, Mar 9, 2009 at 11:57 AM, JASON BURWELL <<a href="mailto:JASON.BURWELL@foundersfcu.com" target="_blank">JASON.BURWELL@foundersfcu.com</a>> wrote:<br>
I have been looking in to this recently and have been told by several providers there is a national database that contains all Caller ID Name records. I am told when a incoming call hits the PSTN, the provider delivering the call to the called party takes the 10 digit number being sent and does a data dip to the national database for the name and sends that along with the number to the called party. Supposedly the provider that owns the DID controls what name is registered to what number. If no name is available in the database the city/state of the call is displayed based on NPA/NXX or "unknown caller" depending on the provider of the called party. I do not have all the details but have been told the same thing by technical people from several large carriers.<br>
<br>
Jason<br>
From: <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-" target="_blank">cisco-voip-</a><a href="mailto:bounces@puck.nether.net" target="_blank">bounces@puck.nether.net</a>] On Behalf Of Matthew Linsemier<br>
Sent: Monday, March 09, 2009 12:34 PM<br>
<br>
To: Sean Walberg<br>
Cc: <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
Subject: Re: [cisco-voip] Different outbound caller name for internal vs external calls<br>
<br>
That’s interesting to say the least as there are no other places (route groups, route lists, or route patterns) to change the calling name. Who is the provider?<br>
<br>
<br>
On 3/9/09 12:19 PM, "Sean Walberg" <<a href="mailto:sean@ertw.com" target="_blank">sean@ertw.com</a>> wrote:<br>
<br>
Maybe things are different here, but I'm able to change my Line Display field to whatever I want, and it shows up on the other end when I call.<br>
<br>
>From debug isdn q931, bold line obviously my doing:<br>
<br>
Bearer Capability i = 0x8090A2<br>
Standard = CCITT<br>
Transfer Capability = Speech<br>
Transfer Mode = Circuit<br>
Transfer Rate = 64 kbit/s<br>
Channel ID i = 0xA98394<br>
Exclusive, Channel 20<br>
Display i = 0xB1, 'Line Display'<br>
Calling Party Number i = 0x0081, 'MYNUMBER'<br>
Plan:Unknown, Type:Unknown<br>
Called Party Number i = 0x80, 'WHOICALLED'<br>
Plan:Unknown, Type:Unknown<br>
Mar 9 11:14:40.649 CDT: ISDN Se0/0/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0xFBF8<br>
Channel ID i = 0xA98394<br>
Exclusive, Channel 20<br>
<br>
<br>
I changed my line display field to "Line Display" and called home. The problem is that "Line Display" also show up if I call someone internally.<br>
<br>
Sean<br>
<br>
<br>
On Mon, Mar 9, 2009 at 11:03 AM, Matthew Linsemier <<a href="mailto:mlinsemier@apassurance.com" target="_blank">mlinsemier@apassurance.com</a>> wrote:<br>
External caller ID is controlled by the LEC so there isn’t really away to dynamically send different calling name based on number. Additionally, the LEC (at least AT&T) only allows you one calling name per circuit number, so it’s not that you could have multiple calling name associated with different DID ranges on a circuit.<br>
<br>
You can however have the LEC assign a static calling name, and then just use a route list, group, or pattern to swap out DID for 123-456-1000 in which your static assigned calling name would be displayed.<br>
<br>
Matt<br>
<br>
<br>
<br>
On 3/9/09 11:13 AM, "Sean Walberg" <<a href="mailto:sean@ertw.com" target="_blank">sean@ertw.com</a> <http://<a href="mailto:sean@ertw.com" target="_blank">sean@ertw.com</a>> > wrote:<br>
<br>
I've got Call Manager 6.1.2 with an IOS H.323 gateway and a PRI.<br>
<br>
One site would like to have caller id if they're calling another IP phone (Fred Smith, 1234), but a generic name/number if they call outside (MyCo, 123-456-1000).<br>
<br>
I know I can use the external number mask to take care of the number, but can the name be done? Is there a way to do it per phone? Some phones want no restrictions, some want "MyCo, 123-456-1000" and some others want "MyCo News Desk, 123-456-1100"<br>
<br>
Thanks,<br>
<br>
Sean<br>
<br>
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.<br>
<br>
<br>
<br>
<br>
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.<br>
<br>
<br>
<br>
<br>
<br>
-- <br>
Sean Walberg <<a href="mailto:sean@ertw.com" target="_blank">sean@ertw.com</a>> <a href="http://ertw.com/" target="_blank">http://ertw.com/</a><br></div></div>
_______________________________________________<br>
cisco-voip mailing list<div class="im"><br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
</div><div class="im"><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></div>
_______________________________________________<br>
cisco-voip mailing list<div class="im"><br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
</div><div><div></div><div class="h5"><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Sean Walberg <<a href="mailto:sean@ertw.com">sean@ertw.com</a>> <a href="http://ertw.com/">http://ertw.com/</a><br>