Have any of you noticed an increase in customer complaints of malformed caller ID? 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. 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. 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. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com
Ran into this issue a long time ago, make sure you're passing callerID strictly in E.164 format On our end, it was only really an issue when calling into some rural telecom companies and the virgin islands. On Thu, Apr 22, 2021 at 5:05 PM Mike Hammett <voiceops at ics-il.net> wrote:
Have any of you noticed an increase in customer complaints of malformed caller ID?
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.
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.
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.
----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com
Midwest Internet Exchange http://www.midwest-ix.com
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
The first thing I thought of was Least Cost Routing to a rural area. My telco is rural. We see issues like that now and then. Setup the same call over and over again and you will probably get a handful of different CID/CNAM results at the recipient end. Not saying this is your issue, but it is something we have experienced over the past decade or so. For those not familiar, here is a quick overview from the FFC: https://www.fcc.gov/general/rural-call-completion-problems-long-distance-or-...
I finally got a number! It's suburban Chicago Sprint (now T-Mobile). I guess that kind of throws the rural carrier idea out the window. 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. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com ----- Original Message ----- From: "Mike Hammett" <voiceops at ics-il.net> To: "VoiceOps" <voiceops at voiceops.org> Sent: Thursday, April 22, 2021 4:01:02 PM Subject: [VoiceOps] Malformed Caller ID Have any of you noticed an increase in customer complaints of malformed caller ID? 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. 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. 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. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
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 +8157563626 instead of +18157563626 and a cell phone will show that as "Japan". ________________________________ From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of Mike Hammett <voiceops at ics-il.net> Sent: Thursday, April 22, 2021 6:38 PM To: VoiceOps Subject: Re: [VoiceOps] Malformed Caller ID I finally got a number! It's suburban Chicago Sprint (now T-Mobile). I guess that kind of throws the rural carrier idea out the window. 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. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com ________________________________ From: "Mike Hammett" <voiceops at ics-il.net> To: "VoiceOps" <voiceops at voiceops.org> Sent: Thursday, April 22, 2021 4:01:02 PM Subject: [VoiceOps] Malformed Caller ID Have any of you noticed an increase in customer complaints of malformed caller ID? 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. 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. 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. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest Internet Exchange http://www.midwest-ix.com _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
participants (4)
-
g.sandoval＠chasedatacorp.com -
mjohnston＠wiktel.com -
ptimmins＠clearrate.com -
voiceops＠ics-il.net