157563626 and a cell phone will
show that as "Japan".
From: VoiceOps on behalf of Mike Hammett
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
that.
-
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
- Original Message -
From: "Mike Hammett"
To: "VoiceOps"
Sent: Thursday, April 22, 2021 4:01:02 PM
Subject: [VoiceOps] Malformed
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
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 wrote:
> Have any of you noticed an incre
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 form
