<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>Re: [cisco-voip] Different outbound caller name for internal vs
external calls</title>
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
span.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
        {page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Sometimes the LEC will allow you to set you’re CID (ATT
use to allow us). However, I don’t think there is a way to change your calling
name other than just changing it.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On
Behalf Of </b>Matthew Linsemier<br>
<b>Sent:</b> Monday, March 09, 2009 11:34 AM<br>
<b>To:</b> Sean Walberg<br>
<b>Cc:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] Different outbound caller name for internal vs
external calls<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif"'>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="sean@ertw.com">sean@ertw.com</a>>
wrote:</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>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>
<b> Display i = 0xB1, 'Line Display'<br>
</b> 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="mlinsemier@apassurance.com">mlinsemier@apassurance.com</a>> wrote:</span><o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif"'>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="sean@ertw.com">sean@ertw.com</a>
<<a href="http://sean@ertw.com">http://sean@ertw.com</a>> > wrote:</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>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</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:gray'><o:p> </o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:gray'>
<hr size=3 width="100%" align=center>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Arial","sans-serif";color:gray'>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.</span><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:gray'> <o:p></o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:gray'>
<hr size=3 width="100%" align=center>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:7.5pt;font-family:"Arial","sans-serif";color:gray'>
<hr size=2 width="100%" align=center>
</span></div>
<p><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:gray'>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.</span><span style='color:
gray'> </span><o:p></o:p></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='color:gray'>
<hr size=2 width="100%" align=center>
</span></div>
</div>
</body>
</html>