<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Caller ID names and 4.x</TITLE>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2769" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>I'm not sure if I've mentioned this before, my apologies if I
have. We ran into this problem a while back and my research found out some
interesting things. In the US, I believe it is up to the called party's provider
to do the directory lookup and provide the calling name/number ID. In Canada,
however, it is up to the calling party provider to send the calling name/number
ID. What caused us the problem was that our new digital PRI service does not
have the switch parameter enabled for our provider to populate so we send no
calling name whatsoever. What compounded the issue was that we had a number of
franchises on campus that listed themselves in the directory with our main
number. Typically the last person to list in the directory with a number is the
one that is displayed in the US, so we were having calls appear as coming from a
local hamburger chain!</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>As other's have mentioned, what has likely happened, is there
is a DID with a person's name in the directory that is being caught
somewhere.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>For those Canadians out there with Bell PRI service, I've put
a feature request into CIPTUG - so please vote! ;)</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Lelio</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV>--------------------------------------------------------------------------------<BR>Lelio
Fulgenzi, B.A.<BR>Network Analyst (CCS) * University of Guelph * Guelph, Ontario
N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<BR>"I had a coffee and Coke at lunch today...and now, I've got more jitter than
an<BR>IP phone on a long haul 10base2
connection"
LFJ</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=PRuttman@foley.com href="mailto:PRuttman@foley.com">Ruttman, Peter
G.</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> Wednesday, December 14, 2005 9:52
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> [cisco-voip] Caller ID names and
4.x</DIV>
<DIV><BR></DIV><!-- Converted from text/rtf format -->
<P><FONT face=Arial>We have two separate clusters (4.02 and 4.13) both that
have issues where we mask our outbound caller id numbers with our main
number. For the name we would like it to be the name of our
company. For these two offices we get occasional reports that a person
that was once with our company or is still with the company is showing up on
the caller ID for people receiving calls from us. In the case of the
retired person that person is not even listed on our Callmanager. He
also only seems to show up when the call ends up at certain carriers like
Vonage. </FONT></P>
<P><FONT face=Arial>Does Callmanager control anything with caller ID
name?</FONT> </P>
<P><FONT face=Arial>Pete</FONT> </P><BR>The preceding email message may be
confidential or protected by the attorney-client privilege. It is not intended
for transmission to, or receipt by, any unauthorized persons. If you have
received this message in error, please (i) do not read it, (ii) reply to the
sender that you received the message in error, and (iii) erase or destroy the
message. Legal advice contained in the preceding message is solely for the
benefit of the Foley & Lardner LLP client(s) represented by the Firm in
the particular matter that is the subject of this message, and may not be
relied upon by any other party. <BR><BR><BR>Internal Revenue Service
regulations require that certain types of written advice include a disclaimer.
To the extent the preceding message contains advice relating to a Federal tax
issue, unless expressly stated otherwise the advice is not intended or written
to be used, and it cannot be used by the recipient or any other taxpayer, for
the purpose of avoiding Federal tax penalties, and was not written to support
the promotion or marketing of any transaction or matter discussed herein.<BR>
<P>
<HR>
<P></P>_______________________________________________<BR>cisco-voip mailing
list<BR>cisco-voip@puck.nether.net<BR>https://puck.nether.net/mailman/listinfo/cisco-voip<BR></BLOCKQUOTE></BODY></HTML>