<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:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" 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=iso-8859-1">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Tahoma","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@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:10.0pt;font-family:"Tahoma","sans-serif";
color:#1F497D'>If the calling number shows up correctly for the called party
(an obvious first step), the called party will need to get in contact with
their telephony provider/CNAM vendor to get the calling name fixed. It’s
possible that because your client (the calling party) ported their number, the
called party’s CNAM source reflects no information because the line was disconnected.
The called party’s CNAM source is obviously not getting directory listing
directly or indirectly from Teliax.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:#1F497D'>It may be helpful to speak to Teliax and find out where they
sell/provide their directory listings. Somehow the called party’s CNAM
source needs to get that information from Teliax, either directly, or more
likely, via one or more intermediate parties that aggregates the data. TARGUSinfo
(http://targusinfo.com/solutions/identification/caller_name/default.aspx), for
example, collects from over 90 sources (http://targusinfo.com/solutions/identification/caller_name/faq/).<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:#1F497D'>I’ve heard that Vonage Canada does not sell/provide their
directory listings, so you’ll never obtain a name-like calling number
unless your CNAM provider collects the data from other sources, and they do (e.g.
department store credit cards applications). <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:#1F497D'>Frank<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<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"'> Barry D. Hassler
[mailto:barry.hassler@gmail.com] <br>
<b>Sent:</b> Tuesday, July 07, 2009 3:54 PM<br>
<b>To:</b> frnkblk@iname.com; Asterisk Users Mailing List - Non-Commercial
Discussion<br>
<b>Subject:</b> Re: [asterisk-users] Caller ID (name) - where does it come
from?<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>This is all excellent
information. My primary issue is for calls that are placed FROM my client's
PBX, via VOIP provider (Teliax). The recipients of those calls are the ones
that are not getting the proper CNAM information as the call comes in. <br>
<br>
We just recently ported the client's POTS lines to VOIP, and with the exception
of this issue, all is working well. But, my client is really unhappy that their
callerID NAME isn't showing up.<o:p></o:p></p>
<div>
<p class=MsoNormal>On Tue, Jul 7, 2009 at 3:42 PM, Frank Bulk <<a
href="mailto:frnkblk@iname.com">frnkblk@iname.com</a>> wrote:<o:p></o:p></p>
<p class=MsoNormal>There's a bit of oversimplification going on here -- it's
not "a ...<br>
database". Different CNAM providers have different databases which
are<br>
populated from many sources. Most of the data probably matches, but not
all<br>
of it.<br>
<br>
If the Calling Name is incorrect, the person who received the call will have<br>
to check with their telephony provider (or, if they do their own CNAM<br>
lookups, with their CNAM provider) to get the name for the calling party<br>
fixed up (this presumes that the calling party has already verified with<br>
their own telephony provider that their name is correctly listed). But<br>
that's not all of it, either, because the next time the CNAM provider<br>
refreshes their records, the local fix could be overridden (I'm not sure if<br>
any CNAM providers have the capability to ignore old/bad data for a record,<br>
but perhaps so). Ideally the CNAM provider shares with the calling party<br>
which database the CNAM provider is using for the calling party, so that the<br>
calling party can try to get it fixed directly with the database provider<br>
(if that's even possible).<br>
<br>
In short, it's a mess.<br>
<br>
But because accuracy rates are one of the elements that CNAM providers<br>
compete on, these usually do get cleaned up.<br>
<span style='color:#888888'><br>
Frank</span><o:p></o:p></p>
<div>
<p class=MsoNormal><br>
-----Original Message-----<br>
From: <a href="mailto:asterisk-users-bounces@lists.digium.com">asterisk-users-bounces@lists.digium.com</a><br>
[mailto:<a href="mailto:asterisk-users-bounces@lists.digium.com">asterisk-users-bounces@lists.digium.com</a>]
On Behalf Of Karl Fife<br>
Sent: Tuesday, July 07, 2009 1:27 PM<br>
To: Asterisk Users Mailing List - Non-Commercial Discussion<o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal>Subject: Re: [asterisk-users] Caller ID (name) - where does
it come from?<br>
<br>
The Caller ID name, "CNAM" is a separate database owned and maintained<br>
"cooperatively" by the bell operating companies.<br>
<br>
Your ITSP is not doing these CNAM lookups for you because they would have to<br>
<br>
pay the BOC's for the 'dips' into the CNAM database. CNAM is a little
cash<br>
cow that the BOC's are quick to protect. As such CNAM dips may not be<br>
cached or re-sold as a term service that you must agree to with your CNAM<br>
provider.<br>
<br>
As far as solving your CNAM problem, you would need to either choose an ITSP<br>
<br>
that will provide you with CNAM data on a per-call basis, OR you need to do<br>
CNAM dips yourself as I (and many others) do. Beware that some ITSP's<br>
provide "best-effort" name data culled from various sources.
It's not<br>
always terrible but it's not 'coke' it's more like 'dollar store' cola. :-)<br>
<br>
As a call comes in to your dial plan you can populate the CALLERID(name)<br>
channel variable using the CURL function in your dialplan as so:<br>
exten =><br>
s,n,Set(CALLERID(name)=${CURL(<a
href="http://cnam1.edicentral.net/getcnam?q=C&f=S&dn" target="_blank">http://cnam1.edicentral.net/getcnam?q=C&f=S&dn</a><br>
=${CALLERID(num)})})<br>
<br>
AND let's not forget the completely separate issue with getting your<br>
ITSP-provisioned number ENTERED INTO the CNAM database in the first place,<br>
so people see "Karl Fife" rather than the "city, state" or
worse, some<br>
string of arcane LATA information. There's a solution to this problem too<br>
but I digress...<br>
<br>
I've posted my personal notes below from about 18 months ago when I was<br>
searchign for CNAM providers:<br>
<br>
-Karl<br>
<br>
CNAM PROVIDRES:<br>
<br>
Metrostat.com<br>
about 1.5¢ per dip,<br>
$30 minimum deposit, refundable<br>
CNAM service not well documented on web site<br>
A registerd CLEC<br>
<br>
Got Name - Out of business?<br>
1.5¢ per dip. no minimums, no setup<br>
<br>
ClearReach Networks<br>
.67¢ per dip $200 monthly minimum, resell ok, significant setup fees<br>
<br>
<a href="http://411xml.com" target="_blank">411xml.com</a><br>
more expensive than ClearReach.<br>
<br>
----- Original Message -----<br>
From: Barry D. Hassler<br>
To: Asterisk Users Mailing List - Non-Commercial Discussion<br>
Sent: Tuesday, July 07, 2009 12:40 PM<br>
Subject: [asterisk-users] Caller ID (name) - where does it come from?<br>
<br>
Hi Folks, having an issue with outbound calls through a VOIP provider. Calls<br>
<br>
get sent out with the CallerID(number), but where does callerID(name) come<br>
from? Apparently not from provider, as we are seeing different (sometime<br>
missing) names on inbound calls, different than what we have configured.<br>
Apparently this comes from some telco database somewhere? Numbers were<br>
ported from a wired-telco.<br>
<br>
--<br>
Barry D. Hassler<br>
President, HCST<br>
<br>
<a href="http://www.hcst.net/%0A937-427-9000" target="_blank">http://www.hcst.net/<br>
937-427-9000</a><br>
<br>
_______________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com"
target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users"
target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
<br>
<br>
_______________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com"
target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users"
target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
<br>
<br>
_______________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com"
target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users"
target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=MsoNormal><br>
<br clear=all>
<br>
-- <br>
Barry D. Hassler<br>
President, HCST<br>
<br>
<a href="http://www.hcst.net/">http://www.hcst.net/</a><br>
937-427-9000<o:p></o:p></p>
</div>
</body>
</html>