after some testing i've verified (within reason) that tw only falls back to genericname if the cpn is invalid. sounds like some engineer somewhere thought "wow, it would be cool if we did this!"<br><br>valid cpn & genericname = "milosz" -> tw caller id = cpn cnam entry<br>
invalid cpn & genericname = "milosz" -> tw caller id = "milosz"<br>invalid cpn & genericname = null -> tw caller id = "0"<br><br><div class="gmail_quote">On Thu, Feb 4, 2010 at 9:59 AM, David Birnbaum <span dir="ltr"><<a href="mailto:davidb@pins.net">davidb@pins.net</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;">It sure sounds like it. TWTC is "cheating", I suppose, and depriving the rightful owner of that number of their CNAM revenue (should you take the carrier view of things).<br>
<br>
Regardless of what the "best" answer is, in the US all carriers are supposed to deliver CNAM by dipping the central database, paying the owning carrier, and delivering the result to their subscriber. But that's really a discussion for another thread.<br>
<br>
Cheers,<br>
<br>
David.<br>
<br>
-----<div><div></div><div class="h5"><br>
<br>
On Wed, 3 Feb 2010, milosz wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
not sure whether what you are saying can apply here, since this is a case of a call from a<br>
non-tw pri to their residential tw voip phone. doesn't that necessarily mean that tw is not<br>
doing a CNAM dip on the call?<br>
<br>
maybe genericname gets sent if CNAM turns up unknown/invalid?<br>
<br>
On Wed, Feb 3, 2010 at 12:34 PM, David Birnbaum <<a href="mailto:davidb@pins.net" target="_blank">davidb@pins.net</a>> wrote:<br>
That's a mistake/misconfiguration. I believe Canada sends CNAME inband, but in the<br>
US, it probably just means somebody is using a client-profile PRI for a carrier<br>
circuit, doing toll-bypass, or playing other games. We have seen this type of<br>
misconfiguration on smaller VoIP carriers.<br>
<br>
Time Warner may carry CNAM internal on their network so they can save the money on<br>
CNAM dips, but obviously that won't go far.<br>
<br>
Cheers,<br>
<br>
David.<br>
<br>
-----<br>
<br>
On Wed, 3 Feb 2010, Carlos Alvarez wrote:<br>
<br>
Time Warner does transmit the name info that you send. We have a TWTC PRI<br>
and I've seen the same thing when calling another number on their network. It<br>
has even happened to numbers on other networks, though now I can't remember<br>
which ones. One of their engineers confirmed that they do this on purpose,<br>
but also couldn't tell me which other networks accept this from them.<br>
<br>
<br>
On 2/3/10 9:24 AM, milosz wrote:<br>
hi all,<br>
<br>
has anyone heard of a US residential carrier transmitting the<br>
callername<br>
parameter from the IAM instead of doing a normal CNAM lookup? i<br>
have<br>
some users--for whom the pbx is (intentionally) set up to<br>
transmit an<br>
invalid cpn--who are claiming that when they call their home<br>
phones from<br>
the office, their internal (sip) caller name appears on the<br>
caller id<br>
along with the invalid cpn, which makes no sense from a CNAM<br>
lookup<br>
standpoint. the only thing i could think of (other than they are<br>
nuts/lying) is that their gateway is transmitting the sip<br>
callername in<br>
the IAM and the carrier is passing that along instead of doing a<br>
lookup.<br>
the btn is the same for all users so that can be ruled out.<br>
<br>
they are all on cablevision or time warner.<br>
<br>
thanks,<br>
<br>
milosz<br>
<br>
<br>
<br>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
<br>
<br>
--<br>
Carlos Alvarez<br>
TelEvolve<br>
602-889-3003<br>
<br>
Advanced phone services simplified<br>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
<br>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
<br>
<br>
<br>
</blockquote>
</div></div></blockquote></div><br>