<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p>That sounds exactly like you're sending stuff that should be E.164 formatted out as 10 digit national. I looked up DeKalb IL and the first two digits of your area code are "81". Which is the country code for Japan. So your calls are being interpreted as
+<span><span class="LrzXr zdqRlf kno-fv"><span data-dtype="d3ifr" data-local-attribute="d3ph"><span>8157563626</span></span></span></span> instead of +1<span><span class="LrzXr zdqRlf kno-fv"><span data-dtype="d3ifr" data-local-attribute="d3ph"><span>8157563626</span></span></span></span>
and a cell phone will show that as "Japan".<br>
</p>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> VoiceOps <voiceops-bounces@voiceops.org> on behalf of Mike Hammett <voiceops@ics-il.net><br>
<b>Sent:</b> Thursday, April 22, 2021 6:38 PM<br>
<b>To:</b> VoiceOps<br>
<b>Subject:</b> Re: [VoiceOps] Malformed Caller ID</font>
<div> </div>
</div>
<div>
<div style="font-family:arial,helvetica,sans-serif; font-size:10pt; color:#000000">
I finally got a number! It's suburban Chicago Sprint (now T-Mobile).
<div><br>
</div>
<div>I guess that kind of throws the rural carrier idea out the window.</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>Apparently a non-zero number of people are expecting caller ID name to work on their mobile devices, but there are clearly caveats to that.<br>
<br>
<div><span name="x"></span><br>
<br>
-----<br>
Mike Hammett<br>
Intelligent Computing Solutions<br>
http://www.ics-il.com<br>
<br>
<br>
<br>
Midwest Internet Exchange<br>
http://www.midwest-ix.com<br>
<br>
<span name="x"></span><br>
</div>
<br>
<hr id="zwchr">
<div style="color:#000; font-weight:normal; font-style:normal; text-decoration:none; font-family:Helvetica,Arial,sans-serif; font-size:12pt">
<b>From: </b>"Mike Hammett" <voiceops@ics-il.net><br>
<b>To: </b>"VoiceOps" <voiceops@voiceops.org><br>
<b>Sent: </b>Thursday, April 22, 2021 4:01:02 PM<br>
<b>Subject: </b>[VoiceOps] Malformed Caller ID<br>
<br>
<div style="font-family:arial,helvetica,sans-serif; font-size:10pt; color:#000000">
Have any of you noticed an increase in customer complaints of malformed caller ID?
<div><br>
</div>
<div>We do a test call out as the customer, whether it's to one of our cell phones or one of the incumbent's POTS lines. Everything shows up as expected. The number is formatted correctly. The Caller ID name is formatted correctly.</div>
<div><br>
</div>
<div><br>
</div>
<div>However, we're getting customer complaints that the caller ID is saying Japan (we have nothing to do with Japan), United States, blank, or some other combination. We're just not able to confirm that.</div>
<div><br>
</div>
<div>Of course customers are reluctant to tell us what the numbers are of the remote parties having these issues, so we can't really look for common denominators.<br>
<br>
<div><span></span><br>
<br>
-----<br>
Mike Hammett<br>
Intelligent Computing Solutions<br>
http://www.ics-il.com<br>
<br>
<br>
<br>
Midwest Internet Exchange<br>
http://www.midwest-ix.com<br>
<br>
<span></span><br>
</div>
<br>
</div>
</div>
<br>
_______________________________________________<br>
VoiceOps mailing list<br>
VoiceOps@voiceops.org<br>
https://puck.nether.net/mailman/listinfo/voiceops<br>
</div>
<br>
</div>
</div>
</div>
</div>
</div>
</body>
</html>